Universal Containers is creating a new B2C service offering for consumers to ship goods across continents. This is in addition to their well-established B2B offering. Their current Salesforce org uses the standard Account object to track B2B customers. They are expecting to have over 50,000,000 consumers over the next five years across their 50 business regions. B2C customers will be individuals. Household data is not required to be stored. What is the recommended data model for consumer account data to be stored in Salesforce?

• A.Create a new picklist value for B2C customers on the Account Type field.
• B.Use 50 umbrella Accounts for each region, with customers as associated Contacts.
• C.Use the Account object with Person Accounts and a new B2C page layout.
• D.Use the Account object with a newly created Record Type for B2C customers.

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

Comment: *

Name: *

Email: *

Verification: *

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 SF.
UC is concerned about SF storage limits but would still like Sales cloud to have access to the data.
Which design patterns should a data architect select to satisfy the requirement?

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

Comment: *

Name: *

Email: *

Verification: *

Universal Containers is migrating individual customers (B2C) data from legacy systems to Salesforce. There are millions of customers stored as account and contacts in the legacy database.
Which object model should a data architect configure within Salesforce?

• A.Leverage standard account and contact object in Salesforce
• B.Leverage custom person account object in Salesforce
• C.Leverage person account object in Salesforce
• D.Leverage custom account and contact object in Salesforce

Comment: *

Name: *

Email: *

Verification: *

Universal Containers has millions of cases and are running out storage. Some user groups need to have access to historical cases for up to seven years.
Which two solutions should a data architect recommend in order to minimize performance and storage issues?
(Choose two.)

• A.Leverage big object to archive case data and Lightning components to show archived data
• B.Export data out of Salesforce and store in flat files on external system
• C.Create a custom object to store case history and run reports on it
• D.Leverage on-premise data archival and build integration to view archived data

Comment: *

Name: *

Email: *

Verification: *