Data Architecture & Management Designer Set 2

Data Architecture & Management Designer Set 2 1) Universal Containers wants their Shipment custom object to always relate to a Container, a Sender, and a Receiver (all separate custom objects). If a Shipment is currently associated with a Container, Sender, or Receiver, deletion of those records should not be allowed. They also want separate sharing models on each custom object. What approach should an architect take to fulfill these requirements? a. Create a required Lookup relationship to each of the three parent records. b. Create two Master -Detail and one Lookup relationship to the parent records. c. Create a Master -Detail relationship to each of the three parent records. d. Use a VLOOKUP formula field to associate the Shipment to each parent record. 2) Universal Containers (UC) is planning to move away from legacy CRM to Salesforce. As part of one-time data migration, UC will need to keep the original date when a contact was created in the legacy system. How should an Architect design the data migration solution to meet this requirement? a. After the data is migrated, perform an update on all records to set the original date in a standard CreatedDate field. e. Create a new field on Contact object to capture the Created Date. Hide the standard CreatedDate field using Field -Level Security. f. Enable "Set Audit Fields" and assign the permission to the user loading the data for the duration of the migration. g. Write an Apex trigger on the Contact object, before insert event to set the original value in a standard CreatedDate field.