Universal Containers (UC) has three systems: Salesforce, a cloud -based ERP system, and an on -premise Order Management System (OMS). An architect has been tasked with creating a solution that uses Salesforce as the system of record for Leads and the OMS as the system of record for Account and Contacts. UC wants Accounts and Contacts to be able to maintain their names in each system (i.e., "John Doe" in the OMS and "Johnny Doe" in Salesforce), but wants to have a consolidated data store which links referenced records across the systems. What approach should an architect suggest so the requirements are met?

• A.Have Salesforce poll the OMS nightly and bring in the desired Accounts and Contacts.
• B.Use the Streaming API to send Account and Contact data from Salesforce to the OMS.
• C.Implement a Master Data Management strategy to reconcile Leads, Accounts, and Contacts.
• D.Implement an integration tool to send OMS Accounts and Contacts to Salesforce.

Comment: *

Name: *

Email: *

Verification: *

Universal Containers (UC) has migrated its back-office data into an on-premise database with REST API access. UC recently implemented Sales Cloud for its sales organization, but users are complaining about a lack of order data inside Salesforce.
UC is concerned about Salesforce storage limits but would still like Sales Cloud to have access to the data.
Which design pattern should a data architect select to satisfy the requirement?

• A.Build a UI for the on-premise system and iframe it in Salesforce
• B.Develop a bidirectional integration between the on-premise system and Salesforce
• C.Use Salesforce Connect to virtualize the data in Salesforce and avoid storage limits
• D.Migrate and persist the data in Salesforce to take advantage of native functionality

Comment: *

Name: *

Email: *

Verification: *

A manager at Cloud Kicks is importing Leads into Salesforce and needs to avoid creating duplicate records.
Which two approaches should the manager take to achieve this goal? (Choose two.)

• A.Run the Salesforce Lead Mass de-duplication tool.
• B.Implement Salesforce Matching and Duplicate Rules.
• C.Create a Workflow Rule to check for duplicate records.
• D.Acquire an AppExchange Lead de-duplication application.

Comment: *

Name: *

Email: *

Verification: *

Universal Containers (UC) is migrating from an on-premise homegrown customer relationship management (CRM) system- During analysis, UC users highlight a pain point that there are multiple versions of many customers.
What should the data architect do for a successful migration to mitigate the pain point?

• A.Store the data in a staging database, and de-duplicate identical records.
• B.Hire an intern manually de-duplicate the records after migrating to Salesforce.
• C.Migrate the data as is, and use Salesforce's de-duplicating feature.
• D.Have the users manually clean the data in the old system prior to migration.

Comment: *

Name: *

Email: *

Verification: *

A large Automobile company has implemented SF for its Sales Associates. Leads flow from its website to SF using a batch integration in SF. The Batch job connects the leads to Accounts in SF. Customer visiting their retail stores are also created in SF as Accounts.
The company has noticed a large number of duplicate accounts in SF. On analysis, it was found that certain customers could interact with its website and also visit the store. The Sales associates use Global Search to search for customers in Salesforce before they create the customers.
Which scalable option should a data Architect choose to implement to avoid duplicates?

• A.Customize Account creation process to search if customer exists before creating an Account.
• B.Implement a MDM solution to validate the customer information before creating Accounts in SF.
• C.Create duplicate rules in SF to validate duplicates during the account creation process
• D.Build Custom search based on fields on Accounts which can be matched with customer when they visit the store

Comment: *

Name: *

Email: *

Verification: *