UC has a variety of systems across its technology landscape, including SF, legacy enterprise resource planning (ERP) applications and homegrown CRM tools. UC has decided that they would like to consolidate all customer, opportunity and order data into Salesforce as part of its master data management (MDM) strategy.
What are the 3 key steps that a data architect should take when merging data from multiple systems into Salesforce? Choose 3 answers:

• A.Install a 3rd party AppExchange tool to handle the merger
• B.Analyze each system's data model and perform gap analysis
• C.Utilize an ETL tool to merge, transform and de-duplicate data.
• D.Create new fields to store additional values from all the systems.
• E.Work with Stakeholders to define record and field survivorship rules

Comment: *

Name: *

Email: *

Verification: *

Universal Container (UC) has accumulated data over years and has never deleted data from its Salesforce org.
UC is now exceeding the storage allocations in the org. UC is now looking for option to delete unused from the org.
Which three recommendations should a data architect make is order to reduce the number of records from the org?
Choose 3 answers

• A.Archive the records in enterprise data warehouse (EDW) before deleting from Salesforce.
• B.Use Rest API to permanently delete records from the Salesforce org.
• C.Identify records in objects that have not been modified or used In last 3 years.
• D.Use hard delete in batch Apex to permanently delete records from Salesforce.
• E.Use hard delete in Bulk API to permanently delete records from Salesforce.

Comment: *

Name: *

Email: *

Verification: *

Universal Container (UC) stores 10 million rows of inventory data in a cloud database, As part of creating a connected experience in Salesforce, UC would like to this inventory data to Sales Cloud without a import. UC has asked its data architect to determine if Salesforce Connect is needed.
Which three consideration should the data architect make when evaluating the need for Salesforce Connect?

• A.You need to expose data via a virtual private connection.
• B.You have a large amount of data that you don't want to copy into your Salesforce org.
• C.You want real-time access to the latest data, from other systems.
• D.You have a large amount of data and would like to copy subsets of it into Salesforce.
• E.You need to small amounts of external data at any one time.

Comment: *

Name: *

Email: *

Verification: *

NTO has multiple systems across its enterprise landscape including salesforce, with disparate version the customer records.
In salesforce, the customer is represented by the contact object.
NTO utilizes an MDM solution with these attributes:
1. The MDM solution keeps track of customer master with a master key.
2. The master key is a map to the record ID's from each external system that customer data is stored within.
3. The MDM solution provides de-duplication features, so it acts as the single source of truth.
How should a data architect implement the storage of master key within salesforce?

• A.Create an external object to store the master key with a lookup field to contact.
• B.Store the master key on the contact object as an external ID (Field for referential imports)
• C.Create a custom object to store the master key with a lookup field to contact.
• D.Store the master key in Heroku postgres and use Heroku connect for synchronization.

Comment: *

Name: *

Email: *

Verification: *

DreamHouse Realty has a data model as shown in the image. The Project object has a private sharing model, and it has Roll-Up summary fields to calculate the number of resources assigned to the project, total hours for the project, and the number of work items associated to the project.
There will be a large amount of time entry records to be loaded regularly from an external system into Salesforce.

What should the Architect consider in this situation?

• A.Load all data after deferring sharing calculations.
• B.Calculate summary values instead of Roll-Up by using triggers.
• C.Load all data using external IDs to link to parent records.
• D.Calculate summary values instead of Roll-Up by using workflow.

Comment: *

Name: *

Email: *

Verification: *