Salesforce DATA-ARCHITECT Online Practice Questions and Exam Preparation

Salesforce DATA-ARCHITECT Online Questions & Answers

• Question 231:

  Universal Containers (UC) is in the process of selling half of its company. As part of this split, UC's main Salesforce org will be divided into two org:org A and org B, UC has delivered these requirements to its data architect

  1. The data model for Org B will drastically change with different objects, fields, and picklist values.

  2. Three million records will need to be migrated from org A to org B for compliance reasons.

  3. The migrate will need occur within the next two month, prior to be split.

  Which migrate strategy should a data architect use to successfully migrate the date?

  A. use as ETL tool to orchestrate the migration.
  B. Use Data Loader for export and Data Import Wizard for import
  C. Write a script to use the Bulk API
  D. Use the Salesforces CLI to query, export, and import
  A. use as ETL tool to orchestrate the migration.

  ---

  Explanation

  Using an ETL tool to orchestrate the migration is the best strategy for this scenario, as it can handle the data model changes, the large volume of records, and the tight timeline. Writing a script to use the Bulk API (option C) is also possible, but it would require more coding and testing effort. Using Data Loader and Data Import Wizard (option B) is not suitable for migrating three million records, as they have limitations on the batch size and the number of records per operation.

  Using Salesforce CLI (option D) is also not recommended for large data migration, as it is mainly designed for development and testing purposes

• Question 232:

  Universal Containers (UC) 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.

  What should the architect consider, knowing there will be a large amount of time entry records to be loaded regularly from an external system into Salesforce.

  com?

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

  ---

  Explanation

  Loading all data after deferring sharing calculations can improve the performance and avoid locking issues when loading a large amount of time entry records into Salesforce.com. This is because deferring sharing calculations can temporarily suspend the calculation of sharing rules until all the data is loaded, and then recalculate them in one operation

• Question 233:

  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?

  A. Update the Opportunity page layout to mark these fields as required.
  B. Use a validation rule for each field that takes the Stage into consideration.
  C. Update these Opportunity field definitions in Setup to be required.
  D. Write an Apex trigger that checks each field when records are saved.
  B. Use a validation rule for each field that takes the Stage into consideration.

  ---

  Explanation

  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 234:

  Universal Container has a Sales Cloud implementation for a sales team and an enterprise resource planning (ERP) as a customer master Sales team are complaining about duplicate account and data quality issues with account data.

  Which two solutions should a data architect recommend to resolve the complaints?

  A. Build a nightly batch job to de-dupe data, and merge account records.
  B. Integrate Salesforce with ERP, and make ERP as system of truth.
  C. Build a nightly sync job from ERP to Salesforce.
  D. Implement a de-dupe solution and establish account ownership in Salesforce
  B. Integrate Salesforce with ERP, and make ERP as system of truth.
  D. Implement a de-dupe solution and establish account ownership in Salesforce

  ---

  Explanation

  Integrating Salesforce with ERP and making ERP the system of truth (option B) and implementing a de-dupe solution and establishing account ownership in Salesforce (option D) are the two solutions that a data architect should recommend to resolve the complaints. Option B ensures that account data is consistent and accurate across both systems, while option D prevents duplicate records and clarifies who owns each account in Salesforce. Building a nightly batch job to de- dupe data and merge account records (option A) is not a good solution, as it does not address the root cause of the duplication and may result in data loss or conflicts. Building a nightly sync job from ERP to Salesforce (option C) is also not sufficient, as it does not prevent duplication or establish ownership in Salesforce.

• Question 235:

  Cloud Kicks is launching a Partner Community, which will allow users to register shipment requests that are then processed by Cloud Kicks employees. Shipment requests contain header information, and then a list of no more than 5 items being shipped.

  First, Cloud Kicks will introduce its community to 6,000 customers in North America, and then to 24,000 customers worldwide within the next two years. Cloud Kicks expects 12 shipment requests per week per customer, on average, and wants customers to be able to view up to three years of shipment requests and use Salesforce reports.

  What is the recommended solution for the Cloud Kicks Data Architect to address the requirements?

  A. Create an external custom object to track shipment requests and a child external object to track shipment items. External objects are stored off-platform in Heroku's Postgres database.
  B. Create an external custom object to track shipment requests with five lookup custom fields for each item being shipped. External objects are stored off-platform in Heroku's Postgres database.
  C. Create a custom object to track shipment requests and a child custom object to track shipment items. Implement an archiving process that moves data off-platform after three years.
  D. Create a custom object to track shipment requests with five lookup custom fields for each item being shipped Implement an archiving process that moves data off-platform after three years.
  C. Create a custom object to track shipment requests and a child custom object to track shipment items. Implement an archiving process that moves data off-platform after three years.

  ---

  Explanation

  The recommended solution for the Cloud Kicks Data Architect to address the requirements is to create a custom object to track shipment requests and a child custom object to track shipment items. Implement an archiving process that moves data off- platform after three years. This solution would allow Cloud Kicks to store and manage their shipment data on Salesforce, and use Salesforce reports to analyze it. However, since Cloud Kicks expects a large volume of data over time, they should implement an archiving process that moves data off-platform after three years to avoid hitting the Org data storage limit and maintain optimal performance3. External objects are not a good option for this scenario, because they are stored off-platform in an external system, such as Heroku's Postgres database, and they have limited functionality and performance compared to custom objects

• Question 236:

  Universal Containers (UC) has 1,000 accounts and 50,000 opportunities. UC has an enterprise security requirement to export all sales data outside of Salesforce on a weekly basis. The security requirement also calls for exporting key operational data that includes events such as file downloads, logins, logouts, etc.

  Which two recommended approaches would address the above requirement?

  A. Use Field Audit History to capture operational data and extract it to on-premise systems.
  B. Use Weekly Export to extract transactional data to on-premise systems.
  C. Use a custom built extract job to extract operational data to on-premise systems.
  D. Use Event Monitoring to extract event data to on-premise systems.
  B. Use Weekly Export to extract transactional data to on-premise systems.
  D. Use Event Monitoring to extract event data to on-premise systems.

  ---

  Explanation

  Using Weekly Export to extract transactional data to on-premise systems and using Event Monitoring to extract event data to on-premise systems are two recommended approaches that would address the security requirement of UC. Weekly Export is a built-in feature that allows UC to download a zip file of their Salesforce data on a weekly basis. Event Monitoring is a tool that allows UC to access detailed information about various events that occur in their Salesforce org, such as logins, logouts, file downloads, etc.

• Question 237:

  An Architect needs to document the data architecture for a multi-system, enterprise Salesforce implementation.

  Which two key artifacts should the Architect use? (Choose two.)

  A. User stories
  B. Data model
  C. Integration specification
  D. Non-functional requirements
  B. Data model
  C. Integration specification

  ---

  Explanation

  Option B is correct because data model is a key artifact that an architect should use to document the data architecture for a multi-system, enterprise Salesforce implementation1. Data model describes the structure and relationship of data entities within an organization2. Option C is correct because integration specification is another key artifact that an architect should use to document the data architecture for a multi-system, enterprise Salesforce implementation1. Integration specification defines the scope, requirements, design, testing, and deployment of integration solutions between Salesforce and other systems3. Option A is not correct because user stories are not key artifacts for documenting the data architecture, but agile development tools that capture the features and functionalities that users want from a system4. Option D is not correct because non- functional requirements are not key artifacts for documenting the data architecture, but quality attributes that specify how well a system performs its functions.

• Question 238:

  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?

  A. Have Salesforce poll the OMS nightly and bring in the desired Accounts and Contacts.
  B. Implement an integration tool to send OMS Accounts and Contacts to Salesforce.
  C. Implement a Master Data Management strategy to reconcile Leads, Accounts, and Contacts.
  D. Use the Streaming API to send Account and Contact data from Salesforce to the OMS.
  C. Implement a Master Data Management strategy to reconcile Leads, Accounts, and Contacts.

  ---

  Explanation

  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 239:

  Universal Containers (UC) management has identified a total of ten text fields on the Contact object as important to capture any changes made to these fields, such as who made the change, when they made the change, what is the old value, and what is the new value. UC needs to be able to report on these field data changes within Salesforce for the past 3 months. What are two approaches that will meet this requirement? Choose 2 answers

  A. Create a workflow to evaluate the rule when a record is created and use field update actions to store previous values for these ten fields in ten new fields.
  B. Write an Apex trigger on Contact after insert event and after update events and store the old values in another custom object.
  C. Turn on field Contact object history tracking for these ten fields, then create reports on contact history.
  D. Create a Contact report including these ten fields and Salesforce Id, then schedule the report to run once a day and send email to the admin.
  B. Write an Apex trigger on Contact after insert event and after update events and store the old values in another custom object.
  C. Turn on field Contact object history tracking for these ten fields, then create reports on contact history.

  ---

  Explanation

  To capture and report on any changes made to ten text fields on the Contact object for the past 3 months, the data architect should write an Apex trigger on Contact after insert and after update events and store the old values in another custom object, or turn on field Contact object history tracking for these ten fields and create reports on contact history. An Apex trigger can capture the old and new values of the fields, as well as the user and time of the change, and store them in a custom object that can be used for reporting. Field history tracking can also track the changes to the fields and store them in a history table that can be used for reporting. However, field history tracking only retains data for up to 18

  months or 24 months with an extension, so it may not be suitable for longer- term reporting needs. The other options are not feasible or effective for capturing and reporting on field data changes.

• Question 240:

  Which API should a data architect use if exporting 1million records from Salesforce?

  A. Bulk API
  B. REST API
  C. Streaming API
  D. SOAP API
  A. Bulk API

  ---

  Explanation

  Using Bulk API to export 1 million records from Salesforce is the best option. Bulk API is a RESTful API that allows you to perform asynchronous operations on large sets of data. You can use Bulk API to create, update, delete, or query millions of records in batches. Bulk API is optimized for performance and scalability, and it can handle complex data loading scenarios.