Salesforce Salesforce Certifications DATA-ARCHITECT Questions & Answers

• Question 61:

  UC is trying to switch from legacy CRM to salesforce and wants to keep legacy CRM and salesforce in place till all the functionality is deployed in salesforce. The want to keep data in synch b/w Salesforce, legacy CRM and SAP.

  What is the recommendation? Choose 2 answers

  A. Integrate legacy CRM to salesforce and keep data in synch till new functionality is in place

  B. Do not integrate legacy CRM to Salesforce, but integrate salesforce to SAP

  C. Integrate SAP with Salesforce, SAP to legacy CRM but not legacy CRM to Salesforce

  D. Suggest MDM solution and link MDM to salesforce and SAP

  Correct Answer: CD

  Explanation: Integrate SAP with Salesforce, SAP to legacy CRM but not legacy CRM to Salesforce. This is a good recommendation because it allows both Salesforce and the legacy CRM to interact with the ERP system, which can be the source of truth for some data entities. However, it avoids creating a direct connection between Salesforce and the legacy CRM, which can cause data duplication and synchronization issues. Suggest MDM solution and link MDM to salesforce and SAP. This is another good recommendation because it can help manage the data lifecycle and quality across multiple systems, as well as provide a single view of the customer data

• Question 62:

  Two million Opportunities need to be loaded in different batches into Salesforce using the Bulk API in parallel mode.

  What should an Architect consider when loading the Opportunity records?

  A. Use the Name field values to sort batches.

  B. Order batches by Auto-number field.

  C. Create indexes on Opportunity object text fields.

  D. Group batches by the AccountId field.

  Correct Answer: D

  Explanation: Grouping batches by the AccountId field can improve the performance and avoid locking issues when loading Opportunity records using the Bulk API in parallel mode1. This is because the AccountId field is indexed and can be used to distribute the records evenly across batches

• Question 63:

  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. Migrate and persist the data in SF to take advantage of native functionality.

  B. Use SF Connect to virtualize the data in SF and avoid storage limits.

  C. Develop a bidirectional integration between the on-premise system and Salesforce.

  D. Build a UI for the on-premise system and iframe it in Salesforce

  Correct Answer: B

  The best design pattern to satisfy the requirement of accessing order data from an on- premise database with REST API access without consuming SF storage limits is to use SF Connect to virtualize the data in SF and avoid storage limits. SF Connect is an integration tool that allows users to access and integrate data from external sources using external objects. External objects are similar to custom objects, except that the data resides in another system and is accessed in real time via web service callouts. SF Connect supports various adapters to connect to different types of external data sources, such as OData, cross-org, or Apex custom adapter11. Migrate and persist the data in SF to take advantage of native functionality is not a good option because it would consume SF storage limits and require data synchronization between systems. Develop a bidirectional integration between the on-premise system and Salesforce is not a good option because it would be complex and costly to implement and maintain, and it would also consume SF storage limits. Build a UI for the on-premise system and iframe it in Salesforce is not a good option because it would not provide a seamless user experience and it would not allow users to search, report, or perform actions on the external data.

• Question 64:

  Salesforce is being deployed in Ursa Major Solar's disparate, multi-system ERP environment. Ursa major Solar wants to maintain data synchronization between systems.

  Which two techniques should be used to achieve this goal? (Choose two.)

  A. Integrate Salesforce with the ERP environment.

  B. Utilize workbench to update files within systems.

  C. Utilize an MDM strategy to outline a single source of truth.

  D. Build synchronization reports and dashboards.

  Correct Answer: AC

  Explanation: Option A is correct because integrating Salesforce with the ERP environment is a technique to maintain data synchronization between systems1. Option C is correct because utilizing an MDM strategy to outline a single source of truth is another technique to ensure data quality and consistency across systems2. Option B is not correct because utilizing workbench to update files within systems is not a technique to maintain data synchronization, but a tool to perform data manipulation tasks3. Option D is not correct because building synchronization reports and dashboards is not a technique to maintain data synchronization, but a way to monitor and analyze data4.

• Question 65:

  Universal Containers (UC) has implemented Salesforce, UC is running out of storage and needs to have an archiving solution, UC would like to maintain two years of data in Saleforce and archive older data out of Salesforce.

  Which solution should a data architect recommend as an archiving solution?

  A. Use a third-party backup solution to backup all data off platform.

  B. Build a batch join move all records off platform, and delete all records from Salesforce.

  C. Build a batch join to move two-year-old records off platform, and delete records from Salesforce.

  D. Build a batch job to move all restore off platform, and delete old records from Salesforce.

  Correct Answer: C

  Explanation: The data architect should recommend building a batch job to move two-year- old records off platform, and delete records from Salesforce as an archiving solution. A batch job is a process that runs in the background and performs operations on large volumes of data in Salesforce. By building a batch job that moves two-year-old records off platform to an external storage system, such as Amazon S3 or Google Cloud Storage, and deletes them from Salesforce, the data architect can reduce the storage consumption and improve the performance of Salesforce org. Option A is incorrect because using a third- party backup solution to backup all data off platform will not free up any storage space in Salesforce, unless the data is also deleted from Salesforce after backup. Option B is incorrect because building a batch job to move all records off platform, and delete all records from Salesforce will result in losing all the current data in Salesforce, which may not be desirable or feasible. Option D is incorrect because building a batch job to move all restore off platform, and delete old records from Salesforce does not make sense, as restore implies restoring data back to Salesforce, not moving it off platform.

• Question 66:

  Universal Containers wants to implement a data -quality process to monitor the data that users are manually entering into the system through the Salesforce UI. Which approach should the architect recommend?

  A. Allow users to import their data using the Salesforce Import tools.

  B. Utilize a 3rd -party solution from the AppExchange for data uploads.

  C. Utilize an app from the AppExchange to create data -quality dashboards.

  D. Use Apex to validate the format of phone numbers and postal codes.

  Correct Answer: C

  Explanation: Utilizing an app from the AppExchange to create data-quality dashboards is the approach that the architect should recommend for UC to implement a data-quality process to monitor the data that users are manually entering into the system through the Salesforce UI. An app from the AppExchange can provide ready-made or customizable dashboards that can display various metrics and indicators of data quality, such as completeness, accuracy, consistency, timeliness, etc. These dashboards can help UC to measure and evaluate their data quality performance and identify any areas that need improvement or attention. The other options are not relevant or effective for implementing a data-quality process, as they would either not address the issue of manual data entry, not provide data-quality monitoring, or not leverage the benefits of Salesforce.

• Question 67:

  Universal Containers has successfully migrated 50 million records into five different objects multiple times in a full copy sandbox. The Integration Engineer wants to re-run the test again a month before it goes live into Production. What is the recommended approach to re-run the test?

  A. Truncate all 5 objects quickly and re-run the data migration test.

  B. Refresh the full copy sandbox and re-run the data migration test.

  C. Hard delete all 5 objects' data and re-run the data migration test.

  D. Truncate all 5 objects and hard delete before running the migration test.

  Correct Answer: B

  Explanation: The recommended approach to re-run the test is to refresh the full copy sandbox and re-run the data migration test. A full copy sandbox is a replica of the production Org, including all data, metadata, and attachments. Refreshing a full copy sandbox means creating a new copy of the production Org and replacing the existing sandbox. This would ensure that the test is run on a clean and up-to-date environment, without any leftover data or configuration from previous tests. Truncating or hard deleting objects would not be sufficient, because they would not remove all the data or metadata from the sandbox, and they could also affect other dependent objects or processes.

• Question 68:

  Universal Containers (UC) is implementing a Salesforce project with large volumes of data and daily transactions. The solution includes both real-time web service integrations and Visualforce mash -ups with back -end systems. The Salesforce Full sandbox used by the project integrates with full-scale back -end testing systems. What two types of performance testing are appropriate for this project?

  Choose 2 answers

  A. Pre -go -live automated page -load testing against the Salesforce Full sandbox.

  B. Post go -live automated page -load testing against the Salesforce Production org.

  C. Pre -go -live unit testing in the Salesforce Full sandbox.

  D. Stress testing against the web services hosted by the integration middleware.

  Correct Answer: AD

  Explanation: Pre-go-live automated page-load testing against the Salesforce Full sandbox can help identify and resolve any performance bottlenecks or issues before deploying the solution to production. The Full sandbox is an ideal environment for performance testing as it replicates the production org in terms of data, metadata, and integrations. Stress testing against the web services hosted by the integration middleware can also help evaluate the scalability and reliability of the integration solution under high load conditions.

• Question 69:

  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 a custom object to store the master key with a lookup field to contact.

  C. Create an external 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)

  Correct Answer: D

  Explanation: 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 70:

  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?

  A. Account and opportunity data originates in Salesforce, and therefore Salesforce is the system of record.

  B. Whatever system updates the attribute or object should be the system of record for that field or object.

  C. Whatever integration data flow runs last will, by default, determine which system is the system of record.

  D. Data flows should be reviewed with the business users to determine the system of record per object or field.

  Correct Answer: D

  Explanation: 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.