Last Updated On : 17-Nov-2026


Salesforce Certified Platform App Builder - Plat-Admn-202 Practice Test

Prepare with our free Salesforce Certified Platform App Builder - Plat-Admn-202 sample questions and pass with confidence. Our Platform-App-Builder practice test is designed to help you succeed on exam day.

349 Questions
Salesforce 2026

The Platform App Builder at Universal Containers recently launched a project management app to better track expansion projects with ever-changing timelines. The app has provided increased visibility of project status, but the app builder finds that users are back-dating their projects, which is preventing stakeholders from having real-time insight into integral timeline updates.

How should the app builder solve this?

A. Implement field tracking on all key date fields to review with stakeholders.

B. Prevent users from editing date fields once the record has been created.

C. Auto-populate key dates using formula fields based on the project start date and average project timelines.

D. Use a validation rule to prevent users from entering dates that are in the past.

D.   Use a validation rule to prevent users from entering dates that are in the past.

Explanation:

The issue is that users are entering past dates, which prevents stakeholders from receiving real-time timeline updates. A validation rule can evaluate the entered date before saving and block any date earlier than today, directly enforcing accurate project timeline data.

✔️ Correct Option:

D. Use a validation rule to prevent users from entering dates that are in the past.
A validation rule runs when a user saves a record and displays an error without saving invalid data. For each key project date field, the App Builder can use an error condition such as Key_Date__c < TODAY(), with an error message such as “Project date must be today or later.” Salesforce’s own example confirms that SampleDate < TODAY() prevents users from entering a past date. This preserves real-time visibility while still allowing current and future dates.

❌ Incorrect Options:

A. Implement field tracking on all key date fields to review with stakeholders.
Field tracking records historical changes to fields, which helps with auditing and reporting. However, it does not prevent users from back-dating projects or entering invalid timeline dates; the incorrect data can still be saved and then reviewed later.

B. Prevent users from editing date fields once the record has been created.
Making date fields read-only after creation would stop legitimate timeline updates as projects progress. The requirement is to prevent back-dating, not to prevent all future edits to project dates, so this approach is too restrictive.

C. Auto-populate key dates using formula fields based on the project start date and average project timelines. Formula fields calculate values automatically and are read-only; they cannot capture user-entered, project-specific dates. They also do not prevent a user from entering a past start date, so they do not solve the back-dating issue.

🔧 Reference:
→ Salesforce Help — TODAY
— Confirms that the validation formula SampleDate < TODAY() prevents users from changing a date to a past date.

→ Salesforce Help — Validation Rules
— Confirms that validation rules verify user-entered data before saving and block invalid records with an error message.

DreamHouse Realty wants to import its property records from an external system into Salesforce. The app builder will use an external ID field to house the property ID from the external System. Which two field types are allowed as an external ID? Choose 2 answers

A. Phone field

B. URL field

C. Text field

D. Number field

C.   Text field
D.   Number field

Explanation

This question tests which custom field types Salesforce allows to be marked as an External ID. An External ID holds the identifier from an outside system, so records can be matched during imports and upserts. It checks whether you know the limited list of field types that support this attribute.

✅ C. Text field
A Text field can be marked as an External ID, so it suits property IDs that contain letters, numbers, or both. The external system’s identifier can be stored exactly as it appears. Salesforce indexes the field, which allows imports and integrations to match existing property records with upsert, instead of relying on Salesforce record IDs. This makes repeated data loads reliable.

✅ D. Number field
A Number field can also be marked as an External ID, which works when the external system uses purely numeric property IDs. The numeric value from the external system is stored in the field and used to identify each record. Salesforce indexes it, so upserts can match property records by that value during imports and future integrations. This meets the import requirement.

❌ A. Phone field
Phone fields are designed to store telephone numbers with formatting, and they are not among the field types that support the External ID attribute. Only Text, Number, Email, and Auto Number fields can be used. A Phone field therefore cannot hold the property ID for upsert matching during the import.

❌ B. URL field
URL fields store web addresses and open them as clickable links. They do not support the External ID attribute, which is limited to Text, Number, Email, and Auto Number fields. A URL field cannot be indexed as an external key for upserts, so it cannot house the property ID from the external system.

Reference
🔗 How Many External ID Fields Can I Create Per Object in Salesforce - Salesforce Help → confirms that External ID fields must be custom text, number, or email fields, and that they are indexed for upsert matching.

At Universal Containers, each admin and developer uses a separate Developer Pro sandbox. Configuration and code are migrated to a Partial Copy sandbox for combination and initial testing. Once approved, the configuration and code are then migrated to a Full Copy sandbox for final load and regression testing before going to production.

When should the Full Copy sandbox be refreshed?

A. After a new user is added to production

B. After each push from the Partial Copy sandbox

C. After each major release to production

D. After User Acceptance Testing (UAT) is complete

C.   After each major release to production

Explanation:

This question tests an app builder's understanding of sandbox lifecycle management and deployment environments within the Application Lifecycle Management (ALM) framework. A Full Copy sandbox serves as an exact replica of the production environment, including metadata and data. To ensure that future development, regression testing, and user acceptance testing remain accurate, the Full sandbox must reflect the latest state of production after changes are deployed.

Correct Option:

Option C: After each major release to production
Refreshing the Full Copy sandbox immediately after a major release ensures that all newly deployed configuration, code, and live data changes in production are synchronized back down to the staging environment. This provides a clean, accurate baseline for the next development cycle and prevents environmental drift between production and downstream testing sandboxes.

Incorrect options:

Option A: After a new user is added to production
Adding a single user to production is a minor administrative task that does not warrant a sandbox refresh. Refreshing a Full sandbox frequently for simple data additions disrupts active testing activities and consumes unnecessary administrative resources.

Option B: After each push from the Partial Copy sandbox
Pushing changes from a Partial Copy sandbox to a Full Copy sandbox is part of the deployment and testing pipeline. Refreshing the Full sandbox at this point would overwrite the newly pushed changes and destroy the environment required for final load and regression testing.

Option D: After User Acceptance Testing (UAT) is complete
Completing User Acceptance Testing (UAT) is a prerequisite for deploying changes to production. Refreshing the Full sandbox before the release takes place in production would wipe out the tested metadata before it can be validated or deployed live.

Reference:
→ Salesforce Help - Refresh Your Sandbox confirms best practices for sandbox refresh schedules following production releases.

Universal Containers wants to match Opportunity data from Salesforce to records in a financial database.

What is required to configure an indirect lookup relationship in Salesforce between the Salesforce Opportunity records and those in a financial database?

A. TEXT(Id)

B. CASESAFEID(Id)

C. External ID

D. Salesforce Record ID

C.   External ID

Explanation:

This question tests how Salesforce connects records to matching records in an external system using an indirect lookup relationship. The external object uses a field containing the external system’s identifier, while the corresponding Salesforce field must be marked as an External ID. Salesforce uses these matching values to associate the external records with the appropriate Salesforce records.

🟢 Correct Option: C. External ID
An indirect lookup relationship connects an external object to a Salesforce standard or custom object by matching identifier values rather than Salesforce record IDs. The target field on the Salesforce Opportunity object must be a custom field marked as both External ID and Unique. The external financial database must provide matching values so Salesforce can associate the corresponding records correctly.

🔴 Incorrect Options:

A. TEXT(Id)
The TEXT() function converts a value into text, but it does not configure an indirect lookup relationship or establish the required matching field attributes. A custom External ID field is needed on the Salesforce parent object.

B. CASESAFEID(Id)
The CASESAFEID() function converts a Salesforce record ID into its 18-character case-safe format. This is useful when working with Salesforce record IDs, but an indirect lookup relationship matches external identifier values instead.

D. Salesforce Record ID
A Salesforce Record ID is used for standard lookup relationships when the external data contains the corresponding Salesforce identifier. Indirect lookup relationships are intended for situations where records are matched using an external identifier instead.

🔧 Reference
⇒ Salesforce Help: Indirect Lookup Relationship Fields on External Objects
Explains that the Salesforce parent object must have a custom field marked as both External ID and Unique to establish an indirect lookup relationship.

⇒ Salesforce Help: External Object Relationships
Compares lookup relationship types and explains how indirect lookups match external records with Salesforce records.

Universal Containers wants to control the visibility of a specific section of a Lightning page based on the device type used by the user.

What should a Platform App Builder recommend?

A. Configure different Record Types.

B. Create a Lightning Web Component.

C. Edit the Page Layout.

D. Use Dynamic Forms.

D.   Use Dynamic Forms.

Explanation:

This question tests the ability to control the visibility of a section on a Lightning record page based on the device type the user is using. Traditional page layouts and record types cannot achieve device-based visibility. Salesforce's Dynamic Forms feature allows administrators to set component visibility rules directly in the Lightning App Builder, and the filter conditions support the Device context (such as desktop or phone) . This enables the same Lightning page to display different sections for different devices, meeting the requirement of showing or hiding specific sections based on device type.

✔️ Correct Option:

D. Use Dynamic Forms.
Salesforce officially added support for field-level device visibility in Dynamic Forms starting from the Winter '25 release. On Dynamic Forms-enabled pages, you can select a field or section in the Lightning App Builder and create visibility rules using the Device context in the properties panel, restricting it to display only on specific devices such as desktop or phone . Trailhead also confirms that visibility rules can determine whether components appear on the page based on device form factor . This is currently the most direct and declarative method to achieve device-based section visibility.

❌ Incorrect options:

A. Configure different Record Types.
Record Types control page layout assignments and picklist values, and their assignment logic is based on user profile and record type, completely unrelated to the device type used by the user. No matter how many record types are created, the same user will see the same page layout on both desktop and mobile. Therefore, this option cannot meet the device-based visibility requirement.

B. Create a Lightning Web Component.
While LWC can technically detect device type through code and conditionally render content, this requires custom development and is not the best practice for a Platform App Builder. Additionally, wrapping an entire section in a custom component just to control visibility adds unnecessary maintenance cost and complexity. Dynamic Forms is a declarative, ready-to-use standard feature and should be prioritized.

C. Edit the Page Layout.
Page Layouts are a legacy configuration method that supports only static field arrangements and do not have conditional visibility rules. Page Layouts cannot dynamically show or hide sections based on device type, nor can they perceive the user's device at runtime. This option fundamentally lacks the capabilities required by the question.

🔧 Reference:
→ Salesforce Help: Set Field Visibility by Device in Dynamic Forms — Confirms that Dynamic Forms supports visibility rule filters using the Device context to display fields only on specific devices.

→ Trailhead: Enhancing Dynamic Pages with Visibility Rules — Confirms that visibility rules can determine whether components appear based on device form factor (device type).

Platform-App-Builder Exam Questions - Home Previous
Page 8 out of 70 Pages