As part of addressing general data protection regulation (GDPR) requirements, UC plans to implement a data classification policy for all its internal systems that stores customer information including salesforce.
What should a data architect recommend so that UC can easily classify consumer information maintained in salesforce under both standard and custom objects?

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?

Universal Containers (UC) maintains a collection of several million Account records that represent business in the United Sates. As a logistics company, this list is one of the most valuable and important components of UC's business, and the accuracy of shipping addresses is paramount. Recently it has been noticed that too many of the addresses of these businesses are inaccurate, or the businesses don't exist. Which two scalable strategies should UC consider to improve the quality of their Account addresses?

UC is building a salesforce application to track contacts and their respective conferences that they have attended with the following requirements:
1. Contacts will be stored in the standard contact object.
2. Conferences will be stored in a custom conference__c object.
3. Each contact may attend multiple conferences and each conference may be related to multiple contacts.
How should a data architect model the relationship between the contact and conference objects?

An Architect needs to document the data architecture for a multi-system, enterprise Salesforce implementation.
Which two key artifacts should the Architect use? (Choose two.)