Get Cloud Consulting needs to integrate two different systems with customer records into the Salesforce Account object. So that no duplicate records are created in Salesforce, Master Data Management will be used.
An Architect needs to determine which system is the system of record on a field level.
What should the Architect do to achieve this goal?
Key stakeholders from both systems should collaborate with the Architect to determine which system is the system of record on a field level is what the Architect should do to achieve this goal of integrating two different systems with customer records into the Salesforce Account object using Master Data Management. The system of record is the authoritative source of truth for a given entity or field in a given context. Different systems may have different levels of accuracy, completeness, timeliness, or relevance for different fields. Therefore, it is important to involve key stakeholders from both systems who have knowledge and expertise about their data quality and business needs to decide which system should be the system of record for each field. The Architect should facilitate this collaboration and document the decisions and rationale for each field. The other options are not correct or feasible, as they would either delegate or abdicate the responsibility of determining the system of record, ignore or disregard the input from key stakeholders, or assume or impose a default system of record without considering the data quality and business needs.
UC is migrating data from legacy system to SF. UC would like to preserve the following information on records being migrated:
Date time stamps for created date and last modified date.
Ownership of records belonging to inactive users being migrated to Salesforce.
Which 2 solutions should a data architect recommends to preserve the date timestamps and ownership on records? Choose 2 answers.
The two solutions that a data architect should recommend to preserve the date timestamps and ownership on records being migrated are:
Cloud Kicks needs to purge detailed transactional records from Salesforce. The data should be aggregated at a summary level and available in Salesforce.
What are two automated approaches to fulfill this goal? (Choose two.)
UC is preparing to implement sales cloud and would like to its users to have read only access to an account record if they have access to its child opportunity record. How would a data architect implement this sharing requirement between objects?
Universal Containers (UC) is implementing Salesforce Sales Cloud and Service Cloud. As part of their implementation, they are planning to create a new custom object (Shipments), which will have a lookup relationship to Opportunities. When creating shipment records, Salesforce users need to manually input a customer reference, which is provided by customers, and will be stored in the Customer_Reference__c text custom field. Support agents will likely use this customer reference to search for Shipment records when resolving shipping issues. UC is expecting to have around 5 million shipment records created per year. What is the recommended solution to ensure that support agents using global search and reports can quickly find shipment records?
Trinidad
14 days agoJovita
2 months agoKerry
3 months agoCherry
4 months agoIlda
5 months agoArgelia
5 months agoVanesa
6 months agoBuck
6 months agoFloyd
7 months agoLashaunda
7 months agoAllene
7 months agoCarri
8 months agoLisha
8 months agoQuentin
8 months agoPearly
9 months agoMari
9 months agoBettina
9 months agoElenora
9 months agoAlease
10 months agoBrittni
10 months agoKatheryn
10 months agoMabel
11 months agoLuz
11 months agoCarey
11 months agoArgelia
12 months agoChauncey
12 months agoJosephine
1 years agoWilda
1 years agoRicarda
1 years agoHildegarde
1 years agoAbel
1 years agoadam zampa
1 years ago