Key details for this exam, checked against the published exam outline
Each question shows the correct answer and an explanation of why it is right
Universal Containers (UC) is implementing Salesforce and will be using Salesforce to track customer complaints, provide white papers on products, and provide subscription-based support.
Which license type will UC users need to fulfill UC's requirements?
Service Cloud License (option C) is the license type that UC users need to fulfill UC's requirements, as it allows them to track customer complaints, provide white papers on products, and provide subscription-based support. Sales Cloud License (option A) is mainly for managing sales processes and leads, Lightning Platform Starter License (option B) is for building custom apps and workflows, and Salesforce License (option D) is a generic term that does not specify a particular license type.
Universal Containers (UC) has an open sharing model for its Salesforce users to allow all its Salesforce internal users to edit all contacts, regardless of who owns the contact. However, UC management wants to allow only the owner of a contact record to delete that contact. If a user does not own the contact, then the user should not be allowed to delete the record. How should the architect approach the project so that the requirements are met?
To allow only the owner of a contact record to delete that contact, the data architect should create a ''before delete'' trigger to check if the current user is not the owner. The trigger can use the UserInfo.getUserId() method to get the current user's ID and compare it with the OwnerId field of the contact record. If they are not equal, the trigger can add an error to the record and prevent it from being deleted. The other options are not suitable for meeting the requirements, as they would either restrict the edit access or delete access for all users, regardless of ownership.
NTO has a loyalty program to reward repeat customers. The following conditions exists:
1. Reward levels are earned based on the amount spent during the previous 12 months.
2. The program will track every item a customer has bought and grant them points for discount.
3. The program generates 100 million records each month.
NTO customer support would like to see a summary of a customer's recent transaction and reward level(s) they have attained.
Which solution should the data architect use to provide the information within the salesforce for the customer support agents?
According to theGet Started with Big Objectsunit on Trailhead, one of the use cases for custom big objects is to store and manage loyalty program data for customers. The unit states that ''From loyalty programs to transactions, order, and billing information, use a custom big object to keep track of every detail.'' Therefore, a custom big object can be used to capture the reward program data and display it on the contact record. Additionally, according to theBig Objects Implementation Guide, big objects can handle massive amounts of data (up to billions of records) and can be updated nightly from external systems using Bulk API or batch Apex. Therefore, a custom big object can meet the requirements of NTO's loyalty program scenario.
A custom pricing engine for a Salesforce customer has to be decided by factors with the following hierarchy:
State in which the customer is located
City in which the customer is located if available
Zip code in which the customer is located if available
Changes to this information should have minimum code changes
What should a data architect recommend to maintain this information for the custom pricing engine that is to be built in Salesforce?
According to theGet Started with Custom Metadata Typesunit on Trailhead, one of the use cases for custom metadata types is to define custom charges for an accounting app. The unit states that ''Say that your org uses a standard accounting app. You can create a custom metadata type that defines custom charges, like duties and VAT rates. Then you can write some Apex code that calculates the total amount due for each invoice by using the metadata from your custom metadata type.'' Therefore, a similar approach can be used to maintain the pricing criteria for a custom pricing engine in Salesforce.
For a production cutover, a large number of Account records will be loaded into Salesforce from a legacy system. The legacy system does not have enough information to determine the Ownership for these Accounts upon initial load. Which two recommended options assign Account ownership to mitigate potential performance problems?
The two recommended options to assign Account ownership to mitigate potential performance problems are to let a ''system user'' own all the Account records without assigning any role to this user in Role Hierarchy, or to let a ''system user'' own the Account records and assign this user to the lowest-level role in the Role Hierarchy.This is because these options would reduce the number of sharing calculations and rules that need to be applied to the Account records, and improve the performance and scalability of the system34. The other options are not recommended, as they would increase the sharing complexity and overhead, and potentially expose sensitive data to unauthorized users.
Based on government regulations, a Salesforce customer plans to implement the following in Salesforce for compliance:
Access to customer information based on record ownership
Ability for customers to request removal of their information from Salesforce
Prevent users from accessing Salesforce from outside company network (virtual private network, or VPN)
What should a data architect recommend to address these requirements?
IP restrictions can be used to prevent users from accessing Salesforce from outside the company network or VPN. According tothis article, sharing settings can be used to control access to customer information based on record ownership. According tothis article, custom Apex can be used to support customer requests for removal of their information from Salesforce.
Exam domains verified against: Official Salesforce Plat-Arch-201 exam guide, last checked September 2026.
Design scalable data models using objects, fields, relationships and features while applying current security and sharing models. Compare big objects versus standard/custom objects and identify techniques to avoid data skew from record locking and excessive parent-child relationships.
Implement MDM solutions by consolidating data from multiple sources and establishing golden records and systems of truth. Recommend data survivorship rules, thresholds and weights while leveraging external reference data and canonical modeling techniques.
Sample question from this domain above: Q2
Select appropriate license types to leverage standard and custom objects effectively. Design solutions to ensure consistent data persistence and represent a single customer view across multiple Salesforce instances.
Sample question from this domain above: Q4
Design GDPR-compliant data models and establish enterprise governance programs. Identify, classify and protect personal and sensitive information using appropriate technical and organizational approaches.
Scale data models for large data volumes and optimize solution performance. Design archiving and purging plans and decide when to use virtualized data alternatives.
Sample question from this domain above: Q3
Ensure high data quality at load time and improve performance when migrating large data volumes into Salesforce. Compare techniques and considerations for exporting data from Salesforce.
Common questions about the exam itself
