Problem #1 (20 pts) The following relational schemas are for a database tracking auto loans and their payments. For each of the relations, (i) identify its current highest normal form, (ii) state the reason why the relation is in the identified normal form, and (iii) convert the relation into the 3NF if necessary. When stating the reason for the relation's highest normal form, you should be able to provide at least one example of non-full functional dependencies that cause the relation to be in that normal form (this only applies when a relation is in the 1NF or the 2NF). (1) LOANS(LoanID, Loan Type, ClientID, ClientFName, ClientLName, PaymentAccountID) (2) PAYMENT_DETAILS(ClientID, LoanID, PaymentAmount, DueDate, ReceiptDate, PaymenAccountID, PaymentRoutingNumber) Functional Dependencies: (ClientID, LoanID) PaymentAmount, DueDate, ReceiptDate LoanID LoanID, Loan Type, ClientID, ClientFName, ClientLName, PaymentAccountID, PaymentRoutingNumber ClientID ClientFName, ClientLName Problem #1 (20 pts) The following relational schemas are for a database tracking auto loans and their payments. For each of the relations, (i) identify its current highest normal form, (ii) state the reason why the relation is in the identified normal form, and (iii) convert the relation into the 3NF if necessary. When stating the reason for the relation's highest normal form, you should be able to provide at least one example of non-full functional dependencies that cause the relation to be in that normal form (this only applies when a relation is in the 1NF or the 2NF). (1) LOANS(LoanID, Loan Type, ClientID, ClientFName, ClientLName, PaymentAccountID) (2) PAYMENT_DETAILS(ClientID, LoanID, PaymentAmount, DueDate, ReceiptDate, PaymenAccountID, PaymentRoutingNumber) Functional Dependencies: (ClientID, LoanID) PaymentAmount, DueDate, ReceiptDate LoanID LoanID, Loan Type, ClientID, ClientFName, ClientLName, PaymentAccountID, PaymentRoutingNumber ClientID ClientFName, ClientLName