Based on the following information, answer the questions: (Please note that these are all subquestions from one question, so it obey Chegg's policy. Please answer carefully on ALL seven multiple choices. Thank you!)

You are working as a consultant for a rental car agency, and have been asked to design a database to manage rentals. You have been given the following requirements statement:

"We capture information on our customers. Customers are identified by a unique customer number. For each customer, we record first name, last name, birthdate, and address. We need to know a customers age to determine rental rates and eligibility, but we can figure that out once we know the birthdate. For the purpose of formatting mailings, we like to break the address out by street, city, state, and zip. A customer may sign a rental agreement, but we will record a prospective customer in our database before they ever sign an agreement. We never record a rental agreement without an associated customer. There will be at most one customer per agreement. There could be many agreements for a single customer. A rental agreement is identified by a unique agreement id, and for each agreement, we record a start date and an end date. A single agreement can cover multiple cars, and well never have an agreement unless it covers at least one car. We will record cars in our database before anybody has agreed to rent them. Over time, there could be many agreements per car. A car is uniquely identified by its VIN. For each car, we record the number of miles that are on it. Every rental agreement is always prepared by a single employee. The employee is uniquely identified by an EmployeeNumber, and we also record the employees last name. An employee could prepare many rental agreements, but some employees will never prepare any agreements. Every car represents exactly one model. Each model has a unique model id, and we will also capture its name and make. We cant have a car without an associated model, and we wont record a model in our database until we have at least one associated car. However, a model can have many associated cars. A customer may sponsor one or more alternate drivers, but doesnt have to sponsor any other drivers. For each alternative driver, we record a full name and a driver id. The driver id counts upward for each customer the first alternate driver for a given customer will be assigned a driver id of 1, the second will be assigned a driver id of 2, and so on. Every alternate driver will be associated with exactly one customer."

1. Which of the following best represents how Customer information should be captured on the ERD?

2. How does Customer participate in a relationship with RentalAgreement?

3. Which of the following best depicts the relationship between Customer and AlternateDriver? (Attributes are intentionally hidden for this question.)

4. Which of the following best depicts the relationship between RentalAgreement and Car?

5. Which of the following best depicts how AlternateDriver information should be captured on the ERD?

6. Which of the following does not show up in this ERD?

7. Which of the following entity pairs consists of entities that are not united by a direct relationship? (In other words, the two entities mentioned are not on either side of the same relationship line.)

Option A: Customer customerNumber PK firstName lastName address street city state zip birthDate /age Option B: Customer customerNumber PK firstName lastName address street city state zip birthDate age Option C: Customer customerNumber PKH firstName lastName address [1..4] birthDate age Option D: Customer customerNumber PK) firstName lastName addresS street city state zip birthDate age alternat eDriver [1 .*) a. There is a "0..1" drawn next to Customer There is a "1..*" drawn next to Customer C. There is a "O..*" drawn next to Customer There is a "1..1" drawn next to Customer b. d. Option A: Customer 1..1 Sponsors AlternateDriver Option B: Customer 0..1 Sponsors AlternateDriver Option C: Customer 1..1 Sponsors AlternateDriver Option D: Customer 1..1 Sponsors AlternateDriver Option A RentalAgreement agreementId PKH startDate endDate 0..1 Covers Car VIN PK miles Option B: RentalAgreement agreementId [PKH startDate endDate Covers Car VIN PK miles Option C: RentalAgreement agreementId [PKH startDate endDate Covers Car VIN PK miles Option D: RentalAgreement agreementId [PKH startDate endDate Covers 0..1 Car VIN PK miles a. Weak entity D. None of the other choices C. Composite attribute d. Multi-valued attribute a. Employee and RentalAgreement b. None of the other choices C. Model and Car Model and RentalAgreement