a) Consider the following RECRUITEMENT relation with sample data. The primary keys are underlimed. University ABC uses a single relation RECRUITEMENT to store its recruitment data. For each recruiter in Univeraity ABC, the table lists the number of recruited students from a particular city. It also lists the population of the cities and state from where University ABC recruits students. There can be more than one city with the same name, but within one state each caty has a different name. Currently this table also lists the gtatus of the recruiter and the population of the State and City. The primary key of this relation is the componite key RecruiterID. City and State. University ABC uses a single relation RECRUITEMENT to store its recruitment data. For each recruiter in University ABC, the table liste the number of recruited students from a particular city. It also liste the population of the cities and state from where University ABC recruits students. There can be more than one city with the same name, but within one state each city has a different name. Currently this table also lists the status of the recruiter and the population of the State and City. The primary key of this relation is the composite key RecruiterID, City and State. i) List down the full functional dependencies (on the primary key), partial dependencies (if any), and transitive dependencies (if any) in the RECRUTTEMENT table. ii) Normalize RECRUITEMENT table to 3NF. Show each normalization step clearly. [5+15marke] b) Consider the following Book relation: BOOK (Book title, Author_name, Book_type, Liat price, Author affiliation, Publishor) Suppose the following dependencies exist: Book title Publishor, Book type Book, type List price Auther_name Author_affiliation Normalize the above BOOK table into 3NF. Show each normalization step cleurly. You are not required to assume any additional dependencies