Green Book Publisher (GBP) wants to maintain data about its authors, the books, editorial staff, and their work for the books. Each author has a unique author ID, name, address, telephone number, unique email address. Abook has a unique ISBN, title, category, publication year, and publishing city. An author can write many books, and each book can be authored by many authors. An editorial staff member has a unique employee ID, employee name, title, and year hired. Some editorial staff members supervise others. Each book is usually edited by many editorial staff members. Each editorial staff member generally works for many books, but may not work for any book yet. Each time when an editorial staff member performs a specific editorial work for the book, the job type, start date, and end date are recorded. An editorial staff member can work for a book for multiple times with multiple start dates. The database with ve tables is described as follows. BOOK *ISBN BookTitle BookCategory lBookYear | BookCity AUTHOR *AuthorlD AuthorName AuthorAdd AuthorPhone AuthorEmail AUTHORSHIP *AuthorlD *ISBN AuthorOrder EDITSTAFF *EmployeelD EmployeeNa EmployeeTitl EmployeeYe SupervisorlD me e ar EDITINGJOB *EmployeeID *ISBN *StartDate EndDate I JobType Analyze each of the following (independent) situations and, state how you would use physical database design techniques to improve the database performance (specify "apply what technique to what table()/attribute() and/or which parts of the table()"). (1.25:5 points) A) There is a frequent need to be able to retrieve detailed data about an author together with detailed data about the authorship. B) The BOOK relation is accessed by an extraordinary large number of users concurrently during Christmas seasons. C) There is a critical need to quickly list the books that belongs to a particular category. D) There is a much more frequent and high priority need to access the records for the books published after year 2000