Question 76
A company uses Salesforce, a cloud-based ERP system, and an on-premise Order Management System (OMS). This company requires a solution that uses Salesforce as the system of record for Leads and the OMS as the system of record for Account and Contacts.
Additionally, the company wants Accounts and Contacts to be able to maintain their names in each system (i.e., ""Jane Doe""; in the OMS and ""Jannie Doe""' in Salesforce), but wants to have a consolidated data store which links referenced records across the systems.
Which suggestion should the Architect provide to the company to meet this goal?
Additionally, the company wants Accounts and Contacts to be able to maintain their names in each system (i.e., ""Jane Doe""; in the OMS and ""Jannie Doe""' in Salesforce), but wants to have a consolidated data store which links referenced records across the systems.
Which suggestion should the Architect provide to the company to meet this goal?
Question 77
Universal Containers has a large number of Opportunity fields (100) that they want to track field history on.
Which two actions should an architect perform in order to meet this requirement? Choose 2 answers
Which two actions should an architect perform in order to meet this requirement? Choose 2 answers
Question 78
Every year, Ursa Major Solar has more than 1 million orders. Each order contains an average of 10 line items. The Chief Executive Officer (CEO) needs the Sales Reps to see how much money each customer generates year-over-year. However, data storage is running low in Salesforce.
Which approach for data archiving is appropriate for this scenario?
Which approach for data archiving is appropriate for this scenario?
Question 79
Universal Containers (UC) is in the process of migrating lagacy inventory data from an enterprise resources planning (ERP) system into Sales Cloud with the following requirements:
Legacy inventory data will be stored in a custom child objects called Inventory_c.
Inventory data should be related to the standard Account object.
The Inventory_c object should Inhent the same sharing rules as the Account object.
Anytime an Account record is deleted in Salesforce, the related Inventory_c record(s) should be deleted as well.
What type of relationship field should a data architect recommend in this scenario?
Legacy inventory data will be stored in a custom child objects called Inventory_c.
Inventory data should be related to the standard Account object.
The Inventory_c object should Inhent the same sharing rules as the Account object.
Anytime an Account record is deleted in Salesforce, the related Inventory_c record(s) should be deleted as well.
What type of relationship field should a data architect recommend in this scenario?
Question 80
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?
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?