Salesforce Salesforce Certified Platform Data Architect (Plat-Arch-201) Data-Architect Exam Dumps: Updated Questions & Answers (October 2025)

The two solutions that a data architect should recommend to preserve the date timestamps and ownership on records being migrated are:

Enable update records with Inactive Owners Permission: This permission allows users to update record owner and sharing-based records with inactive owners. This can help preserve the original ownership of records that belong to users who are no longer active in Salesforce8.

Enable Set Audit fields upon Record Creation Permission: This permission allows users to set audit fields (such as Created By or Last Modified By) when they create a record via API importing tools like Data Loader. This can help preserve the original date timestamps of records that were created or modified in another system9.

Log a case with SF to update these fields is not a good solution because it is not necessary or feasible to ask Salesforce support to update these fields manually or programmatically. Enable modify all and view all permission is not a good solution because it does not affect the ability to preserve the date timestamps and ownership on records, but rather grants users access to all records regardless of sharing settings

According to this article, person accounts are designed to store information about individual people by combining certain account and contact fields into a single record. This is suitable for a large B2C retailer that needs to model the consumer account structure in Salesforce.

A data dictionary is a document that describes the structure, format, and meaning of data entities and attributes. A common technique to build a data dictionary is to use an entity relationship diagram (ERD), which shows the logical relationships between objects and fields in a graphical way. Another technique is to use the Salesforce Metadata API, which allows you to retrieve and deploy the metadata that defines your Salesforce org

Enabling granular locking allows concurrent sharing rule calculations and group membership updates to run without locking each other1. This can help resolve the group membership locking issues that UC is experiencing.

According to the official Salesforce guide1, assigning leads to a single dummy user can cause performance issues and data skew, especially if the dummy user owns more than 10,000 records. Data skew occurs when a single user or a small number of users own a disproportionately large number of records, which can affect query performance and sharing calculations. Option B is the correct answer because it suggests creating multiple dummy users and assigning leads to them, which can distribute the load and reduce data skew. Option A is incorrect because assigning the dummy user to the last role in the role hierarchy does not affect the performance or data skew issues. Option C is incorrect because assigning the dummy user to the highest role in the role hierarchy can worsen the performance and data skew issues, as it will grant access to more users and records. Option D is incorrect because periodically deleting leads can cause data loss and does not address the root cause of the problem.

Creating a custom lookup field on the standard Product to reference the parent record in the hierarchy is the correct way to modify the standard Product object model to support a hierarchical data structure. This allows UC to create a self-relationship on the Product object and define parent-child relationships among products.

Salesforce Connect is a feature that allows users to access data from external sources and multiple Salesforce orgs, using either clicks or code. Salesforce Connect can provide read-only access to customer records across all NTO orgs, without replicating or storing the data in Salesforce.

Virtualizing the remaining set of data with salesforce connect and external objects is the best way to meet the requirements with minimal effort, as it allows salesforce to access data stored in Heroku Postgres without storing it in salesforce. This reduces the storage limitations and avoids data duplication. Heroku connect can bi-directionally sync data between systems, but it requires more configuration and maintenance. Making callouts to Heroku Postgres and persisting the data in salesforce may not be feasible for 1 billion records. Migrating the data to big objects may incur additional costs and require custom code to use async SOQL

single-select restricted picklist with defined choices can be a way to configure customer type. The article states that picklists are fields that allow users to select one or more predefined values from a list, and restricted picklists ensure that users can only select from the defined values. This can help to limit the choices for customer type and ensure data quality.

The correct answer is C, implement shield platform encryption to encrypt standard and custom fields. Shield platform encryption is a feature that allows you to encrypt sensitive data at rest in Salesforce without affecting its functionality. You can encrypt both standard and custom fields using shield platform encryption. Using Apex Crypto Class, implementing classic encryption, or exporting data out of Salesforce are not recommended solutions, as they will either limit your functionality, require custom code, or compromise your data security.