Universal Containers (UC) has multi -level account hierarchies that represent departments within their major Accounts. Users are creating duplicate Contacts across multiple departments. UC wants to clean the data so as to have a single Contact across departments. What two solutions should UC implement to cleanse their data? Choose 2 answers

• A.Use Data.com to standardize Contact address information to help identify duplicates.
• B.Make use of a third -party tool to help merge duplicate Contacts across Accounts.
• C.Use Workflow rules to standardize Contact information to identify and prevent duplicates.
• D.Make use of the Merge Contacts feature of Salesforce to merge duplicates for an Account.

Comment: *

Name: *

Email: *

Verification: *

The invoicing system at Universal Containers requires that attachments associated with the Invoice _c custom object be classified by Types (i.e., "Receipt," "Invoice PDF," etc.) so that reporting can be done on invoices showing the number of attachments grouped by Type. What approach should be taken to categorize the attachments to meet these requirements?

• A.Add additional options to the standard ContentType picklist field for the Attachment object.
• B.Create a custom object related to the Invoice object with a picklist field for the Type.
• C.Add a ContentType picklist field to the Attachment layout and create additional picklist options.
• D.Create a custom picklist field for the Type on the standard Attachment object with the values.

Comment: *

Name: *

Email: *

Verification: *

Universal Containers (UC) is using Salesforce Sales & Service Cloud for B2C sales and customer service but they are experiencing a lot of duplicate customers in the system.
Which are two recommended approaches for UC to avoid duplicate data and increase the level of data quality?

• A.Use a data wharehouse.
• B.Use Data.com Clean
• C.Use an Enterprise Service Bus.
• D.Use Duplicate Management.

Comment: *

Name: *

Email: *

Verification: *

Universal Containers (UC) owns a complex Salesforce org with many Apex classes, triggers, and automated processes that will modify records if available. UC has identified that, in its current development state, UC runs change of encountering race condition on the same record.
What should a data architect recommend to guarantee that records are not being updated at the same time?

• A.Disable classes or triggers that have the potential to obtain the same record.
• B.Migrate programmatic logic to processes and flows.
• C.Embed the keywords FOR UPDATE after SOQL statements.
• D.Refactor or optimize classes and trigger for maximum CPU performance.

Comment: *

Name: *

Email: *

Verification: *

UC has one SF org (Org A) and recently acquired a secondary company with its own Salesforce org (Org B). UC has decided to keep the orgs running separately but would like to bidirectionally share opportunities between the orgs in near-real time.
Which 3 options should a data architect recommend to share data between Org A and Org B?
Choose 3 answers.

• A.Install a 3rd party AppExchange tool to handle the data sharing
• B.Leverage Heroku Connect and Heroku Postgres to bidirectionally sync Opportunities.
• C.Leverage middleware tools to bidirectionally send Opportunity data across orgs.
• D.Develop an Apex class that pushes opportunity data between orgs daily via the Apex schedule.
• E.Use Salesforce Connect and the cross-org adapter to visualize Opportunities into external objects

Comment: *

Name: *

Email: *

Verification: *