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
Northern Trail Outfitters wants to change a master-detail Relationship on Account to a lookup relationship with a custom object Park. The app builder tries to reconfigure this but is unable to do so. What could be causing this?
The correct answer is D.
Salesforce allows converting a master-detail relationship to a lookup relationship only when there are no roll-up summary fields on the master object that summarize the detail records. Salesforce documentation states that after a roll-up summary field exists on an object, the object's master-detail relationship can't be converted into a lookup relationship.
In this case, if Account has roll-up summary fields based on related Park records, Salesforce blocks the conversion.
A is incorrect because a flow using Account does not normally prevent converting the relationship. B is incorrect because formulas on Park referencing Account are not the primary restriction. C is incorrect because custom objects do not need at least one master-detail relationship for reporting.
Universal Containers wants to create a custom checkbox formula field on The Opportunity object. This formula should evaluate to true if the following conditions Are met: Stage is set to Negotiation/Review Close Date is less than 1 week away Which formula meets these requirements?
The formula must evaluate true when:
Stage = Negotiation/Review
Close Date < 1 week from today
Salesforce formula functions used:
ISPICKVAL() for picklist equality checks
AND() to combine multiple conditions
CloseDate < TODAY() + 7 to check the Close Date is within one week
Correct formula:
AND(
ISPICKVAL(StageName, 'Negotiation/Review'),
CloseDate < TODAY() + 7
)
Options A, C, D use invalid syntax (missing quotation marks, incorrect function structure).
Salesforce Help confirms correct syntax for picklist comparison and date arithmetic in formula fields. (Salesforce Help)
This formula evaluates true only when both conditions are simultaneously met.
A new field is being created on a custom object. However, the app builder does not want the field to up on pre-existing custom report Types. What should the app builder do on the custom field setup to fulfill this requirement?
The correct answer is D. Deselect auto add to custom report type.
When creating a new custom field, Salesforce provides an Auto Add option that can automatically add the new field to applicable existing custom report types. If the app builder does not want the new field to appear on pre-existing custom report types, they should deselect the Auto add to custom report type option during field creation. Salesforce release documentation confirms that Auto Add automatically adds custom fields to custom report types based on that object.
Why the other options are incorrect:
Removing the field from page layouts only affects record-page visibility, not report type availability.
Changing profile visibility or read-only access affects field security, not whether the field is added to the custom report type layout.
Cloud Kicks has a custom object with a private sharing setting. The business wants to share individual records with specific people or departments on a case-by-case basis. Which three options does the business user have to manually share individual records? Choose 3 answers
The correct answers are C. Users, D. Public Groups, and E. Roles and Subordinates.
Manual sharing is used when the org-wide default is private and users need to share individual records on a case-by-case basis. Salesforce documentation confirms that manual sharing allows users to share individual records with other users, public groups, and roles.
A public group can include users, roles, and roles with subordinates, which makes it useful when sharing records with departments or groups of people.
A . Permission Set Groups is incorrect because permission set groups grant permissions, not manual record-level sharing.
B . Private Groups is not the standard manual-sharing option tested here.
Sales managers at Cloud Kicks would like to standardize what information sales reps are gathering. Sales reps want recommendations, sales strategies and to know what key fields need to be completed at each step of the sales process on the opportunity record. Which feature should an app builder use to provide this functionality?
The correct answer is A. Path.
Sales managers want reps to see recommendations, sales strategies, and key fields at each step of the Opportunity sales process. Salesforce Path is designed for exactly this. Path can highlight key fields and provide customized Guidance for Success for each stage of a process.
For Opportunities, Path can show reps which fields matter at each sales stage and provide stage-specific guidance such as qualification tips, sales strategy, or next-step recommendations.
C . Approval Process is for record approval routing.
D . Global Action is for creating or updating records quickly, not guiding users through sales stages.
B is not the correct Salesforce feature for this requirement.
Universal Containers has several new fields they've requested for the Opportunity Product object. What should an app builder be able to configure using a formula field?
The correct answer is A. A hyperlink to the parent Account of the parent Opportunity.
A formula field can use cross-object references to parent records, and Salesforce states that cross-object formulas can reference fields from objects up to 10 relationships away. Since Opportunity Product relates to Opportunity, and Opportunity relates to Account, a formula on Opportunity Product can reference the parent Opportunity's Account.
Salesforce also supports the HYPERLINK() formula function, which creates a clickable link from specified link text to a specified URL. So a formula field can be configured to create a hyperlink to the Account record related to the parent Opportunity.
B is incorrect because formula field data types do not include Rich Text Area as a formula return type.
C is incorrect because Salesforce restricts formulas from using long text area, encrypted, or Description fields.
D is not the best verified answer because large cross-object concatenations can run into formula relationship, size, or complexity limits, while the clearly supported Platform App Builder use case here is the cross-object HYPERLINK formula.
A sales manager has noticed that reps continue to input contacts Directly in their phone instead of adding them to Salesforce. What should an app builder recommend to ensure the data makes it into Salesforce?
The correct answer is A. Allow Salesforce to import Contacts from mobile device Contact lists.
Salesforce supports importing contacts from a mobile device contact list into Salesforce from the Salesforce mobile app using Import from Device. Salesforce also notes that users need the permission Allow Salesforce to import Contacts from mobile device Contact lists to use this feature.
Why others are incorrect:
B only notifies users; it does not move phone contacts into Salesforce.
C helps users create/edit records offline in Salesforce, but it does not import contacts already entered in the phone's contact list.
D is for account-contact relationship modeling, not mobile contact capture.
Exam domains verified against: Official Salesforce Plat-Admn-202 exam guide, last checked October 2026.
Identify the line between what declarative customization can do and when you need to code, and spot use cases for AppExchange solutions. Master access controls for objects, records, and fields, then pick the right sharing model for each business scenario.
Choose the right data model for your use case and understand how relationship types affect sharing, reporting, and the UI. Learn when to change field types, use the Schema Builder, and import or export data including external sources.
Sample question from this domain above: Q1
Build formula fields and validation rules to enforce business rules, then use roll-up summaries and approval processes to automate workflows. Match the right automation tool to each scenario and avoid building broken automations.
Customize pages and layouts with buttons, links, and actions, then add Lightning components both declaratively and programmatically. Know which tool suits each UI challenge, from dynamic forms to Lightning App Builder.
Manage the app lifecycle across sandboxes and environments using change sets, packages, and deployment tools. Understand sandbox types, package approaches, and troubleshooting when things go wrong in deployments.
Common questions about the exam itself
