Consider a database for a car dealership. A car has a make, model, year, color, and vehicle identification number (VIN). A salesperson has a name and a social security number (SSN), and is responsible for trying to sell zero or more cars. A car dealership has an inventory of cars and a group of salespeople. It needs to keep track of which car(s) each salesperson is trying to sell. More than one salesperson can be assigned to any given car, but a car does not necessarily have any salespeople assigned to it. The schemas for this database are below. Cars: Salespeople: Selling: The name and type of each attribute are given, and "PK" indicates the attribute is part of the primary key. For the "Selling" schema, { SSN, VIN } is the primary key. Problem 1a) Create and fill in instance tables for each of these schemas such that they represent the information described below. Some of the information is not specified, and you will need to make up values with appropriate types that fit the relational model. Only make up data if it is needed based on the existing information. You do not need to make up real VINs or SSNs, as long as the number you pick has the right type. For example, 0 is considered a valid VIN, because it is an integer. None of your fields should be empty or null. Cars: - Red Toyota Tacoma, 2008 - Green Toyota Tacoma, 1999 - White Tesla Model 3, 2018 - Blue Subaru WRX, 2016 - Red Ford F150, 2006 Salespeople: - Arnold, trying to sell all Toyotas - Jessica, trying to sell all red cars - Steve, trying to sell the Tesla Problem 1b) If the primary key of the "Selling" schema was just \{SSN\}, briefly describe how this would change the car dealership. Note that the instances you created in part a) may not be compatible with this change. Problem 1c) If the primary key of the "Selling" schema was just \{VIN\}, briefly describe how this would change the car dealership. Note that the instances you created in part a) may not be compatible with this change