Salesforce Data Architect Salesforce Certified Data Architect Exam Practice Test

Page: 1 / 14
Total 257 questions
Question 1

Universal Containers (UC) has several custom Visualforce applications have been developed in which users are able to edit Opportunity records. UC struggles with data completeness on their Opportunity records and has decided to make certain fields required that have not been in the past. The newly required fields are dependent on the Stage of the Opportunity, such that certain fields are only required once an Opportunity advances to later stages. There are two fields. What is the simplest approach to handle this new requirement?



Answer : B

Using a validation rule for each field that takes the Stage into consideration is the simplest approach to handle this new requirement. A validation rule can enforce the field requirements based on the logic and criteria that you define, and display an error message when users try to save a record that does not meet the requirements. Updating the Opportunity page layout to mark these fields as required will not work because page layouts do not support conditional field requirements. Updating these Opportunity field definitions in Setup to be required will not work because it will apply to all stages and records.Writing an Apex trigger that checks each field when records are saved is not the simplest approach because it requires coding and testing


Question 2

UC has a requirement to migrate 100 million order records from a legacy ERP application into the salesforce platform. UC does not have any requirements around reporting on the migrated data.

What should a data architect recommend to reduce the performance degradation of the platform?



Answer : D

Implementing a custom big object to store the data is the best recommendation to reduce the performance degradation of the platform, as it allows storing large volumes of data that do not need real-time access or reporting. Custom big objects can be defined using metadata API or developer console, and support up to 1 billion records per object. Creating a custom object or using the standard order object would consume a lot of storage space and impact the performance of queries and reports. Using a standard big object defined by salesforce would not be applicable for order records, as standard big objects are predefined for specific use cases such as audit trails or field history.


Question 3

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?



Answer : D

The best way to implement the storage of master key within Salesforce is to store it on the contact object as an external ID field for referential imports. This way, the data architect can use the master key as a unique identifier to match records from different systems and avoid duplicates. The other options are not feasible because they either require additional storage or do not support referential imports.


Question 4

All accounts and opportunities are created in Salesforce. Salesforce is integrated with three systems:

* An ERP system feeds order data into Salesforce and updates both Account and Opportunity records.

* An accounting system feeds invoice data into Salesforce and updates both Account and Opportunity records.

* A commission system feeds commission data into Salesforce and updates both Account and Opportunity records.

How should the architect determine which of these systems is the system of record?



Answer : D

Option D is correct because data flows should be reviewed with the business users to determine the system of record per object or field1.The system of record is the authoritative source of data for a given entity or attribute2. It may vary depending on the business context and requirements.Option A is not correct because account and opportunity data originates in Salesforce, but it may not be the system of record for all attributes or objects if they are updated by other systems2.Option B is not correct because whatever system updates the attribute or object may not be the system of record for that field or object if there are conflicting or overlapping updates from other systems2.Option C is not correct because whatever integration data flow runs last may not determine which system is the system of record if there are different business rules or logic applied by different systems2.


Question 5

NTO would like to retrieve their SF orgs meta data programmatically for backup within a various external. Which API is the best fit for accomplishing this task?



Answer : A

The best API for retrieving Salesforce org metadata programmatically is the Metadata API. The Metadata API provides access to the metadata that defines the structure and configuration of an org, such as custom objects, fields, workflows, security settings, etc. It also supports deploying, retrieving, creating, updating, and deleting metadata components. The Metadata API can be used with various tools, such as Ant, Workbench, or IDEs.


Question 6

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?



Answer : C

Implementing a Master Data Management strategy to reconcile Leads, Accounts, and Contacts is the approach that the architect should suggest so that the requirements are met for UC. A Master Data Management strategy can provide a consistent and unified view of data across multiple systems, by defining and enforcing rules for data quality, governance, and integration. A Master Data Management strategy can also handle complex scenarios where different systems have different systems of record for different entities or fields, and where data can be modified in different systems with different values. A Master Data Management strategy can also provide a consolidated data store that links referenced records across systems and enables cross-system reporting and analysis.The other options are not suitable or sufficient for meeting the requirements, as they would either not provide a consolidated data store, not handle different systems of record, or not allow data modification in different system


Question 7

Universal Containers (UC) is implementing a formal, cross -business -unit data governance program As part of the program, UC will implement a team to make decisions on enterprise -wide data governance. Which two roles are appropriate as members of this team? Choose 2 answers



Answer : A, B

Analytics/BI Owners and Data Domain Stewards are appropriate roles as members of a team that makes decisions on enterprise-wide data governance. Analytics/BI Owners are responsible for defining the business requirements and metrics for data analysis and reporting, and Data Domain Stewards are responsible for defining and enforcing the data quality standards and rules for specific data domains. Salesforce Administrators and Operational Data Users are not suitable roles for this team, as they are more focused on the operational aspects of data management, such as configuration, maintenance, and usage.


Page:    1 / 14   
Total 257 questions