The scenario is for a small life insurance agency and their need to keep track of clients, agents, insurers, and quotations.1) A Client is a customer, potential customer, or contact of the agency. We need to assign each client a number and save their last name, first name, birth date, gender, telephone number, email address, and the agent who brought the client into the agency. If a client is a “walk in” they are assigned to the first available agent. All clients must have one primary agent.2) An agent is a licensed individual with the state. Each agent has a nationally unique license number, last name, first name, telephone number, and email address. An agent must be the primary agent for at least one client but may not be primary for more than 500 clients. An agent must also be part of at least one quotation and may share in an unlimited number of quotes.3) The agency represents (does business with) many insurance companies (insurers). We will need to track each insurer with an agency assigned alphanumeric code, the insurer's name, telephone number, fax machine number, and email address. There may be insurers in the database that have no quotes but an insurer may give an unlimited number of quotations.4) When a client requests information about a policy a quotation is created. A quotation has a file number, the client number, date of the quotation, insurance company the quotation is requested from, and the final policy number of the client accepts the quote and purchases the policy. A quotation may be for only one client and insurer. A client may have an unlimited number of quotes.5) A quotation may be written by 1 to 5 agents. If the policy is finally purchased commissions will be split among the agents as they see fit, as long as it totals 100%. This sharing percentage must be decided at quotation time.Using the business rules above, complete the table by choosing the correct connectivity for each of the relationships:| Entity | Relationship | Connectivity | Entity ||--------|--------------|--------------|--------|| Client | requests | 1:M | Quote || Insurer| gives | 1:M | Quote || Agent | submits | 1:M | Quote || Agent | Assigned | 1:1 | Client | Title: Understanding Database Design: Entity-Relationship Diagram (ERD) Symbols and Example---## Introduction to Entity-Relationship DiagramsEntity-Relationship Diagrams (ERDs) are a critical component in database design, visually representing the structure of a database and the relationships between its entities. ERDs use various symbols to represent entities, attributes, keys, and relationships. Below is an explanation of common ERD symbols followed by an example applying these concepts.## ERD Symbols Key### Key Types- **Primary Key (PK)** - Symbol: PK, typically shown with a light blue fill. - Description: A unique identifier for records in a table.- **Foreign Key (FK)** - Symbol: FK, typically shown with a light green fill. - Description: A field in a table that links to the primary key of another table.- **Primary and Foreign Key (PK, FK)** - Symbol: PK, FK, typically shown with a pink fill. - Description: A field that acts as both a primary and foreign key.### Relationship Symbols- The diagram includes various relationship symbols which depict how entities are related to each other. These symbols can represent one-to-one, one-to-many, and many-to-many relationships and are illustrated via lines connecting entities.## Example ERD Explanation### Client Table- **Client_Number** (PK, light blue): Unique identifier for each client.- **Client_Last_Name** (Attribute, not a key, standard fill).- **Client_First_Name** (Attribute, not a key, standard fill).- **Client_Birth_Date** (Attribute, not a key, standard fill).- **Client_Gender** (Attribute, not a key, standard fill).- **Client_Telephone** (Attribute, not a key, standard fill).- **Client_Email** (Attribute, not a key, standard fill).- **Agent_License** (FK, pink): Links to another table.### Quote Table- **Quote_Number** (PK, light blue): Unique identifier for each quote.- **Client_Number** (FK, pink): Links to `Client_Number` in the Client table, representing a relationship.- **Quote_Date** (Attribute, not a key, standard fill).- **Insurer_Code** (Attribute, not a key, standard fill).- **Policy_Number** (Attribute, not a key, standard fill).###

The scenariO is for a small life insurance agency and their need to keep track of clients, agents, insurers, and quotations. 1) A Client is a customer, potential customer, or contact of the agency. We need to assign each client a number and save their last name, first name, birth date, gender, telephone number, email address and the agent who brought the client into the agency. If a client is a "walk in" they are assigned to the first available agent. All clients must have one primary agent. 2) An agent is a licensed individual with the state. Each agent has a nationally unique license number, last name, first name, telephone number, and email address. An agent must be the primary agent for at least one client but may not be primary for more than 500 clients. An agent must also be part of at least one quotation and may share in an unlimited number of quotes. 3) The agency represents (does business with) many insurance companies (insurers). We will need to track each insurer with an agency assigned alphanumeric code, the insurer's name, telephone number, fax machine number, and email address. There may be insurers in the database that have no quotes but an insurer may give an unlimited number of quotations. 4) When a client requests information about a policy a quotation is created. A quotation has a file number, the client number, date of the quotation, insurance company the quotation is requested from and the final policy number of the client accepts the quote and purchases the policy. A quotation may be for only one client and insurer. A client may have an unlimited number of quotes. 5) A quotation may be written by 1 to 5 agents. If the policy is finally purchased commissions will be split among the agents as they see fit, as long as it totals 100%. This sharing percentage must be decided at quotation time. Using the business rules above, complete the table by choosing the correct connectivity for each of the relationships: Entity Relationship Connectivity Entity Client requests 1:M V Quote Insurer gives 1:M V Quote Agent submits 1:M V Quote Agent Assigned 1:1 V Client