A customer is facing locking issued when importing large data volumes of order records that are children in a master-detail relationship with the Account object. What is the recommended way to avoid locking issues during import?

• A. Import Order records and Account records separately and populate AccountID in orders using batch Apex.
• B. Change the relationship to Lookup and update the relationship to master-detail after import.
• C. Import Account records first followed by order records after sorting order by OrderID.
• D. Import Account records first followed by order records after sorting orders by AccountID.

What is an advantage of using Custom metadata type over Custom setting?

• A. Custom metadata types are available for reporting.
• B. Custom metadata records are deployable using packages.
• C. Custom metadata records are not copied from production to sandbox.
• D. Custom metadata records are editable in Apex.

Northern Trail Outfitters (NTO) plans to maintain contact preferences for customers and employees. NTO has implemented the following:
1. Customers are Person Accounts for their retail business.
2. Customers are represented as Contacts for their commercial business.
3. Employees are maintained as Users.
4. Prospects are maintained as Leads.
NTO needs to implement a standard communication preference management model for Person Accounts, Contacts, Users, and Leads.
Which option should the data architect recommend NTO to satisfy this requirement?

• A. Create case for contact preferences, and use this to validate the preferences for Lead, Person Accounts, and Users.
• B. Use Individual objects to maintain the preferences with relationships to Lead, Person Account, and Users.
• C. Create a custom object to maintain preferences and build relationships to Lead, Person Account, and Users.
• D. Create custom fields for contact preferences in Lead, Person Account, and Users objects.

An architect has been asked by a client to develop a solution that will integrate data and resolve duplicates and discrepancies between Salesforce and one or more external systems. What two factors should the architect take into consideration when deciding whether or not to use a Master Data Management system to achieve this solution?
Choose 2 answers

• A. Whether the system of record changes for different tables.
• B. The number of systems that are integrating with each other.
• C. Whether or not Salesforce replaced a legacy CRM.
• D. Whether the systems are cloud -based or on -premise.

Universal Containers (UC) has a multi-level master-detail relationship for opportunities, a custom opportunity line item object, and a custom discount request. UC has opportunity as master and custom line item object as detail in master-detail relationship. UC also has a custom line item object as master and a custom discount request object as detail in another master-detail relationship. UC has a requirement to show all sums of discounts across line items at an opportunity level. What is the recommended solution to address these requirements?

• A. Remove the master-detail relationships and rely completely on workflow/triggers to summarize the discount amount.
• B. Roll-up discount request amount at the line-item-level and line-item-level summary discount at the opportunity level.
• C. Use roll-up for the line-item-level summary and a trigger for the opportunity amount summary, as only one level roll-up is allowed.
• D. Update the master-detail relationships to lookup relationships in order to allow the discount amount to roll up.