A large retail B2C customer wants to build a 360 view of its customer for its call center agents. The customer interaction is currently maintained in the following system:
1. Salesforce CRM
2. Custom billing solution
3. Customer Master Data management (MDM)
4. Contract Management system
5. Marketing solution
What should a data architect recommend that would help upgrade uniquely identify customer across multiple systems:

• A.Create a customer data base and use this id in all systems.
• B.Create a custom object that will serve as a cross reference for the customer id.
• C.Store the salesforce id in all the solutions to identify the customer.
• D.Create a custom field as external id to maintain the customer Id from the MDM solution.

Comment: *

Name: *

Email: *

Verification: *

During the implementation of Salesforce, a customer has the following requirements for Sales Orders:
1. Sales Order information needs to be shown to users in Salesforce.
2. Sales Orders are maintained in the on-premises enterprise resource planning (ERP).
3. Sales Order information has more than 150 million records.
4. Sales Orders will not be updated in Salesforce.
What should a data architect recommend for maintaining Sales Orders in salesforce?

• A.Us custom objects to maintain Sales Orders in Salesforce.
• B.Use external objects to maintain Sales Order in Salesforce.
• C.Use custom big objects to maintain Sales Orders in Salesforce.
• D.Use Standard order object to maintain Sale Orders in Salesforce

Comment: *

Name: *

Email: *

Verification: *

UC is building a salesforce application to track contacts and their respective conferences that they have attended with the following requirements:
1. Contacts will be stored in the standard contact object.
2. Conferences will be stored in a custom conference__c object.
3. Each contact may attend multiple conferences and each conference may be related to multiple contacts.
How should a data architect model the relationship between the contact and conference objects?

• A.Create a master detail relationship field on the Conference object.
• B.Implement a Contact Conference junction object with master detail relationship to both contact and conference__c.
• C.Create a master detail relationship field on the Contact object.
• D.Create a lookup relationship field on contact object.

Comment: *

Name: *

Email: *

Verification: *

UC has multiple SF orgs that are distributed across regional branches. Each branch stores local customer data inside its org's Account and Contact objects. This creates a scenario where UC is unable to view customers across all orgs.
UC has an initiative to create a 360-degree view of the customer, as UC would like to see Account and Contact data from all orgs in one place.
What should a data architect suggest to achieve this 360-degree view of the customer?

• A.Use an ETL tool to migrate gap Accounts and Contacts into each org.
• B.Build a bidirectional integration between all orgs.
• C.Use Salesforce Connect's cross-org adapter.
• D.Consolidate the data from each org into a centralized datastore

Comment: *

Name: *

Email: *

Verification: *