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

A company needs to evaluate all open Cases related to an Account when that Account ' s status changes to " Critical " . The flow must loop through the retrieved Cases, change their Priority to " High " , and then update all modified records in a single database operation.

Which combination of Flow elements must the company use inside the loop to store the changes before updating the database?

A. A Decision element and an Update Records element

B. An Assignment element and a Collection Filter element

C. An Assignment element and a collection variable

D. A Loop element and a Get Records element

C.   An Assignment element and a collection variable

Explanation:

The question tests Flow bulkification: modify each Case inside a Loop without performing a database update for every record. The correct pattern is to change the Case Priority with an Assignment element, add the modified Case to a collection variable, and update the entire collection once after the Loop.

✔️ Correct Option:

C. An Assignment element and a collection variable.
✔️ Inside the Loop, the Assignment element changes the current Case’s Priority to “High” in the loop variable. A second Assignment adds that modified Case to a record collection variable. After the Loop completes, a single Update Records element can use the collection to update all Cases in one database operation. This avoids repeated DML operations and keeps the flow within governor limits.

❌ Incorrect Options:

A. A Decision element and an Update Records element.
❌ A Decision element can evaluate conditions, but it does not store modified records. Placing an Update Records element inside the Loop performs a separate database update for each Case, which is not the required single bulk operation and consumes more DML limits.

B. An Assignment element and a Collection Filter element.
❌ The Assignment element can modify the Case, but a Collection Filter creates a new filtered collection based on criteria; it does not add the modified current loop record to a target collection. It is used to filter existing collections, not to stage records for a bulk update.

D. A Loop element and a Get Records element.
❌ The Loop and Get Records elements are needed to retrieve and iterate through the Cases, but they do not store the modified Priority value for bulk update. Also, placing Get Records inside a Loop causes repeated queries and is not the bulkified pattern required.

🔧 Reference:
→ Salesforce Help — Loop Element
— Confirms that changes made in a Loop should be added to a record collection variable, then updated once after the Loop.

→ Salesforce Help — Update Records Element
— Confirms that using a record collection variable updates multiple records in one operation and reduces DML requests.

DreamHouse Realty (DR) employees started using company-owned airplanes for work travel after Ursa Major Solar was acquire DR executives Want to automate the submission travel request forms to enforce the internal policy. How should an app builder automate travel requests based on these criteria?

A. Assignment rule

B. Validation rule

C. Apex

D. Approval process

D.   Approval process

Explanation:

This question tests your knowledge of declarative automation tools and business process management in Salesforce. When organizations need to enforce internal policies by routing business requests—such as travel authorizations—through a structured chain of review and sign-off, a dedicated workflow tool is required. Salesforce provides native functionality to automate multi-step submissions, track status changes, and lock records during review. Selecting the right automation feature ensures compliance and streamlines operational requests without needing custom code.

Correct Option:

Option D:
An approval process is the correct choice because it is specifically designed to automate the submission, routing, and review of records like travel request forms based on strict internal corporate policies. It enables administrators to define entry criteria, specify sequential approval steps, assign appropriate managers, and automate actions such as locking the record or updating field values upon final approval or rejection. This completely satisfies the executive business requirement efficiently using native declarative configuration tools.

Incorrect options:

Option A:
Assignment rules are used automatically to route incoming leads or cases to specific users or queues based on defined criteria. They do not manage multi-step review workflows, record locking, or formal submission processes required for executive policy enforcement.

Option B:
Validation rules evaluate data entered into fields and block record creation or updates when criteria are met. While they enforce data format or field requirements, they cannot manage multi-tiered review routing, approval chains, or submission workflows.

Option C:
Apex is a strongly typed, object-oriented programming language used for writing custom business logic. While Apex can handle complex custom requirements, using code for standard request routing violates best practices since approval processes provide a native, declarative solution.

Reference:
→ Refer to Approval Processes Overview on official Salesforce documentation, which confirms how approval processes automate the submission and review of records to enforce internal business policies.

When an Opportunity Stage is changed to Closed Lost , users need to complete the Reason Lost field. How should a Platform App Builder configure this requirement?

A. Use the page layout editor to require the Reason Lost field.

B. Make the Reason Lost field required using Dynamic Forms without filter criteria.

C. Use a field-level requirement to require users to complete Reason Lost.

D. Create a validation rule to enforce the conditional requirement.

D.   Create a validation rule to enforce the conditional requirement.

Explanation:

The question tests conditional field validation in Salesforce. The Reason Lost field should be mandatory only when an Opportunity's Stage is set to Closed Lost. A validation rule can check the Stage and prevent users from saving the record when Reason Lost is blank.

🟢 Correct Option: D. Create a validation rule to enforce the conditional requirement.
A validation rule can check whether the Opportunity Stage equals Closed Lost and the Reason Lost field is blank. If both conditions are true, Salesforce displays an error message and prevents the record from being saved. This ensures users provide a reason when an Opportunity is lost without requiring the field for other stages. The rule enforces the requirement consistently across supported record editing methods.

🔴 Incorrect Options:

A. Use the page layout editor to require the Reason Lost field.
Making the field universally required on the page layout forces users to complete it for every Opportunity, regardless of Stage. This does not meet the conditional requirement.

B. Make the Reason Lost field required using Dynamic Forms without filter criteria.
Making the field required without visibility or condition criteria applies the requirement regardless of the Opportunity Stage. Dynamic Forms alone would not enforce the intended conditional requirement.

C. Use a field-level requirement to require users to complete Reason Lost.
Marking the field as universally required in its field definition makes it mandatory for all Opportunities. It cannot make the requirement conditional on the Stage value.

🔧 Reference:
⇒ Salesforce Help: Create a Validation Rule
Salesforce Help explains how validation rules evaluate conditions and prevent records from being saved when specified criteria are met.

⇒ Salesforce Help: Formula Operators and Functions
Salesforce Help documents formula functions and operators used to check field values and determine when a validation rule should trigger.

A Platform App Builder is troubleshooting user visibility issues and needs to identify why a user is unable to experience record page Field Sections on their mobile device.

Which action should the app builder take?

A. Migrate back to standard Page Layouts for mobile users while maintaining Dynamic Forms for desktop users.

B. Add additional Field Section components to simplify the mobile layout.

C. Enable Dynamic Forms and Dynamic Highlights Panel on Mobile in Salesforce Mobile App Setup.

D. Use visibility rules to optimize for mobile use.

C.   Enable Dynamic Forms and Dynamic Highlights Panel on Mobile in Salesforce Mobile App Setup.

Explanation:

This question tests the ability to troubleshoot why Dynamic Forms field sections are not appearing on a mobile device. Dynamic Forms is enabled for desktop by default, but for mobile users to see the same Field Section components on their devices, a separate org-level setting must be activated. Without this setting, mobile users continue to see the legacy Record Detail (Mobile) component or page layout instead of the Dynamic Forms sections configured in Lightning App Builder . The app builder must enable the mobile-specific setting in Salesforce Mobile App Setup.

✔️ Correct Option:

C. Enable Dynamic Forms and Dynamic Highlights Panel on Mobile in Salesforce Mobile App Setup.
Salesforce documentation confirms that Dynamic Forms on Mobile must be explicitly enabled from Setup by navigating to Salesforce Mobile App and activating the "Dynamic Forms and Dynamic Highlights Panel on Mobile" setting . Once enabled, Lightning record pages that have been upgraded to Dynamic Forms display the configured Field Sections on mobile devices without further page-level configuration . This directly resolves the visibility issue described in the scenario.

❌ Incorrect options:

A. Migrate back to standard Page Layouts for mobile users while maintaining Dynamic Forms for desktop users.
This abandons the Dynamic Forms implementation entirely for mobile rather than fixing the configuration. The goal is to deliver the Field Sections to mobile users, not revert to page layouts. Migrating back does not address the missing setting and creates unnecessary maintenance overhead.

B. Add additional Field Section components to simplify the mobile layout.
Adding more components does not resolve the underlying issue. If Dynamic Forms on Mobile is not enabled, no Field Section components—new or existing—will appear on mobile devices. The problem is a missing org setting, not insufficient component configuration.

D. Use visibility rules to optimize for mobile use.
Visibility rules control when fields or sections display based on criteria, but they cannot make Dynamic Forms appear on mobile if the mobile feature itself is disabled. Visibility rules operate within the Dynamic Forms framework; they do not enable the framework on mobile devices.

🔧 Reference:
→ Salesforce Help: Dynamic Forms on Mobile Is Enabled by Default in New Orgs — Confirms the setting location is Salesforce Mobile App Setup and that it controls mobile Dynamic Forms availability .

→ Salesforce Help: Give Your Mobile Users the Dynamic Forms Experience (Beta) — Confirms that enabling the mobile setting is required for Field Sections to render on mobile devices .

Universal Containers has two types of applicants: Hourly and Salary. There are separate record types for each. While all members of the human resources (HR) department need to be able to view all applicant records, only the hiring manager and VP of HR should be able to create Salary applicant records.

What should the Platform App Builder recommend to meet this requirement?

A. Remove the Create permission for the Salary applicant object for everyone except the hiring manager and VP of HR.

B. Update the organization-wide default to Private and create a sharing rule for the role of recruiting manager.

C. Configure the Hourly record type as the default and instruct non-management users to accept the default record type.

D. Create a permission set containing the Salary record type and assign it to the appropriate users.

D.   Create a permission set containing the Salary record type and assign it to the appropriate users.

Explanation

This question tests how to control which users can create records of a specific record type while all HR users keep visibility into every applicant record. Record type availability decides which types a user can select when creating a record. The Platform App Builder must find the option that limits Salary record creation without affecting Hourly applicants or record visibility.

✅ D. Create a permission set containing the Salary record type and assign it to the appropriate users.
A permission set can grant record type access in addition to what a user’s profile provides. The Platform App Builder keeps only the Hourly record type in the HR profile, then creates a permission set that adds the Salary record type and assigns it to the hiring manager and VP of HR. Only those users can create Salary applicants, while all HR users can still view every record.

❌ A. Remove the Create permission for the Salary applicant object for everyone except the hiring manager and VP of HR.
Salary and Hourly are record types on a single applicant object, not separate objects, so there is no Salary-specific Create permission. Object permissions apply to every record type. Removing Create from most users would also stop them from creating Hourly applicants, which the requirement does not ask for.

❌ B. Update the organization-wide default to Private and create a sharing rule for the role of recruiting manager.
Setting the organization-wide default to Private would limit record visibility, which conflicts with the need for all HR members to view every applicant record. Sharing rules extend record access, such as read or edit, and do not control which users can create records of a particular record type.

❌ C. Configure the Hourly record type as the default and instruct non-management users to accept the default record type.
A default record type only sets the preselected value when a user creates a record. It does not remove the Salary option. Any user who has access to the Salary record type can still select it, and relying on instructions is not an enforced control, so the requirement is not met.

🔧 Reference
🔗 Permissions and Access Settings – Salesforce Developer Documentation → confirms that record type assignments can be managed in both profiles and permission sets, with profiles for default record types and permission sets for additional assignments.

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