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

At Northern Trail Outfitters (NTO), a Platform App Builder built a new commission calculation flow and supporting components in a Developer sandbox. Before the change reaches production, the project lead requires sales operations users to validate the calculation against real Opportunity data. NTO has a Full sandbox available.

Which deployment plan should the app builder use?

A. Deploy the components from the Developer sandbox to production using a change set with the Validate Only option, then conduct User Acceptance Testing (UAT) in production.

B. Refresh the Developer sandbox from production to bring in real Opportunity data, conduct User Acceptance Testing (UAT) in the Developer sandbox, then deploy to production.

C. Deploy the components from the Developer sandbox directly to production, then have sales operations users validate in production.

D. Deploy the components from the Developer sandbox to the Full sandbox, conduct User Acceptance Testing (UAT) in the Full sandbox, then deploy to production.

D.   Deploy the components from the Developer sandbox to the Full sandbox, conduct User Acceptance Testing (UAT) in the Full sandbox, then deploy to production.

Explanation:

This question tests the standard Salesforce release lifecycle and the correct use of sandbox types. The requirement is clear: sales operations users must validate the commission flow against real Opportunity data before it reaches production. A Developer sandbox contains only configuration metadata and no production data, so UAT cannot happen there. The Full sandbox is a complete replica of production, including all data, and is explicitly intended for QA and UAT at the end of the development lifecycle . The correct path is to promote the metadata to the Full sandbox for validation, then deploy to production.

✔️ Correct Option:

D. Deploy the components from the Developer sandbox to the Full sandbox, conduct User Acceptance Testing (UAT) in the Full sandbox, then deploy to production.
Salesforce documentation confirms that Full sandboxes include a copy of production data and are used for user acceptance testing before release . Deploying the flow to the Full sandbox allows sales operations to test against real Opportunity records without risking production. Once UAT passes, the validated components can be deployed to production. This follows the standard org development model: develop in Developer sandbox, stage and test in Full sandbox, then release.

❌ Incorrect options:

A. Deploy the components from the Developer sandbox to production using a change set with the Validate Only option, then conduct User Acceptance Testing (UAT) in production.
Validate Only checks deployment readiness and Apex test coverage; it does not create a usable environment for UAT . Conducting UAT in production violates the core purpose of sandbox testing and exposes live data to untested automation. This option skips the required testing environment entirely.

B. Refresh the Developer sandbox from production to bring in real Opportunity data, conduct User Acceptance Testing (UAT) in the Developer sandbox, then deploy to production.
Developer sandboxes have strict data storage limits and are not designed to hold production data volumes . Even after a refresh, a Developer sandbox copies configuration metadata only—not production records. It cannot support realistic UAT against real Opportunity data. The Full sandbox exists precisely for this purpose.

C. Deploy the components from the Developer sandbox directly to production, then have sales operations users validate in production.
This bypasses all pre-production testing and exposes production users and data to an untested commission flow. If the flow miscalculates commissions against live Opportunity data, financial errors could occur. Salesforce's development model requires staging and validation before production deployment .

🔧 Reference:
→ Salesforce Help: Sandbox Types and Templates — Confirms Full Sandbox is a replica of production including all data, used for staging and performance testing.

→ Salesforce Developers: Build and Release Your App with Metadata API — Confirms the release flow: develop in Developer sandbox, stage and run regression tests in Full sandbox, then deploy to production.

Universal Containers wants to collect information from a user and use that input to update a related Account record.

Which combination of flow elements should the Platform App Builder use to meet this requirement?

A. Autolaunched flow with a Screen element and an Update Records element

B. Record-triggered flow with a Screen element and a Create Records element

C. Schedule-triggered flow with an Assignment element and a Create Records element

D. Screen flow with Screen elements and an Update Records element

D.   Screen flow with Screen elements and an Update Records element

Explanation:

The requirement is to gather information interactively from a user and then use that input to update a related Account record. This needs a flow type that supports user-facing screens for data collection, combined with a data element that can modify existing records. Only Screen Flows allow interactive Screen elements. After the user submits the information, an Update Records element can apply the collected values to the related Account.

✅ Correct Option:

D. Screen flow with Screen elements and an Update Records element.
A Screen Flow is designed for user interaction. Screen elements collect the required input from the user. The Update Records element then uses that input (typically stored in variables) to identify and modify the related Account record. This combination fully satisfies both the interactive data-collection need and the requirement to update an existing related record.

❌ Incorrect options:

A. Autolaunched flow with a Screen element and an Update Records element.
Autolaunched flows run in the background without a user interface. They do not support interactive Screen elements for collecting input from a user. Adding a Screen element is not valid in this flow type.

B. Record-triggered flow with a Screen element and a Create Records element.
Record-triggered flows run automatically when a record is created or updated and do not support interactive Screen elements for user input. In addition, Create Records would insert a new record rather than update an existing related Account.

C. Schedule-triggered flow with an Assignment element and a Create Records element.
Schedule-triggered flows run on a time-based schedule with no user interaction. They cannot collect information from a user via screens. The combination also uses Create Records instead of updating an existing Account.

🔧 Reference:
→ Salesforce Help: Getting Started with Screen Flows – Explains that Screen Flows use Screen elements to collect user input and can include data elements such as Update Records to process that input.

Universal Containers has configured a record-triggered flow that fails with an error stating that the maximum number of SOQL queries has been exceeded. While reviewing the interview path in Flow Debugger, the Platform App Builder notices that the exact same Get Records element is being executed repeatedly for every record in the transaction.

How should the app builder change the flow to fix this error?

A. Change the flow trigger from After-Save to Before-Save.

B. Move the Get Records element outside of the Loop element.

C. Connect a Fault Path to a custom Screen element.

D. Change the Loop element to an Assignment element.

B.   Move the Get Records element outside of the Loop element.

Explanation:

The flow exceeds the SOQL query governor limit because a Get Records element is inside a Loop and executes once for every record processed. In a record-triggered flow, Salesforce can bulkify queries across multiple flow interviews, but it does not consolidate repeated queries within the same flow’s loop logic.

✔️ Correct Option:

B. Move the Get Records element outside of the Loop element.
Placing Get Records before the Loop retrieves all required records once and stores them in a record collection variable. The Loop can then process the already-retrieved collection without issuing a new SOQL query on every iteration. If the query needs to match records from the Loop source, the App Builder should collect the relevant IDs before the Loop and use a single Get Records with the In operator. This bulkifies the query and prevents the transaction from exceeding the 100-SOQL-query limit.

❌ Incorrect Options:

A. Change the flow trigger from After-Save to Before-Save.
Changing the trigger timing does not fix a query repeated inside a Loop. A Before-Save flow is useful for updating fields on the triggering record without an extra Update Records operation, but the Get Records element would still execute once per Loop iteration and continue consuming SOQL queries.

C. Connect a Fault Path to a custom Screen element.
A Fault Path handles errors after they occur; it does not prevent the SOQL limit from being exceeded. Also, record-triggered flows are not interactive and cannot display a Screen element to the user. Salesforce also states that a transaction rolls back when a governor limit is exceeded, even if a fault path exists.

D. Change the Loop element to an Assignment element.
An Assignment element sets or changes variable values; it cannot iterate through a collection of records. Replacing the Loop would remove the ability to process each record and would not retrieve the required related data. The correct pattern is to query once before the Loop, then use the Loop to process the resulting collection.

🔧 Reference:
→ Salesforce Help — Break Up Your Record Details with Dynamic Forms — Confirms that Dynamic Forms uses visibility rules to show or hide fields and sections based on record data, user details, and device type.

→ Salesforce Help — Per-Transaction Flow Limits — Confirms the 100-SOQL-query per-transaction limit and that exceeding it rolls back the transaction.

Universal Containers uses a Private sharing model on Accounts. User A and User B both own Accounts of their own and have been sent a link to a new Account record owned by User C. User A can open and view the record, but User B receives an insufficient privileges error. User A and User B have the same role in the role hierarchy as User C.

Why does User A have access, but User B does not?

A. User A and User B have different login access policies.

B. User B has a scoping rule that restricts Account access.

C. User A has View All Fields permission on the Account object.

D. User A is in a public group that has access through a sharing rule.

D.   User A is in a public group that has access through a sharing rule.

Explanation

This question tests how record access works when the Account sharing model is Private. Users in the same role do not see each other’s records, because the role hierarchy only opens access upward to managers. When one peer can open a record and another cannot, the difference must come from an extra sharing mechanism, such as a sharing rule.

✅ D. User A is in a public group that has access through a sharing rule.
In a Private model, users with the same role do not see each other’s records, because the role hierarchy only grants access upward. Since both users sit at the same level as User C, the difference must come from another sharing mechanism. User A belongs to a public group that a sharing rule opens to these Accounts, which explains the access.

❌ A. User A and User B have different login access policies.
Login access policies let administrators or support log in as a user. They control who can sign in on a user’s behalf, not who can open Account records. Record access comes from ownership, the role hierarchy, and sharing rules, so this cannot explain why only User A can view the record.

❌ B. User B has a scoping rule that restricts Account access.
Scoping rules narrow which records a user sees in views such as list views and search, but they do not grant or revoke access to a record. Record access here depends on ownership, the hierarchy, and sharing rules, so a scoping rule is not the reason User B is blocked.

❌ C. User A has View All Fields permission on the Account object.
View All Fields lets a user see every field on records they can access, including fields hidden by field level security. It does not grant access to the records. Record visibility in a Private model comes from ownership, the hierarchy, or sharing, so this permission cannot explain why User A can open it.

Reference
🔗 Sharing Rules - Salesforce Help → confirms that sharing rules give users in public groups, roles, or territories access beyond the organization wide default.

Universal Containers wants to build an onboarding process for new customers that includes multi-user interactions with multiple steps across different days.

Which automation tool should Universal Containers use?

A. Entitlement process

B. Flow Orchestration

C. Custom Lightning Web Component

D. Screen flow

B.   Flow Orchestration

Explanation:

This question tests an app builder's capability to select the appropriate Salesforce automation solution for complex, multi-step business processes. The key requirement involves coordinating multi-user interactions that span multiple steps across different days. Administrators must evaluate declarative automation capabilities against custom code solutions to determine which tool natively supports multi-stage workflows, task assignments to various users, and time-based progression.

Correct Option:

Option B: Flow Orchestration
Flow Orchestration (formerly Orchestrator) is explicitly designed to automate complex business processes that require multiple steps, multiple users, and time-delayed stages. It allows administrators to combine existing flows into unified stages and steps, assigning work items to specific users or queues over an extended timeframe. This natively satisfies all requirements for a multi-user, multi-day onboarding process without requiring programmatic customization.

Incorrect options:

Option A: Entitlement process
Entitlement processes are designed to manage customer support service levels (SLAs), such as resolution times for support cases or milestones. They track support obligations rather than orchestrating multi-step, multi-user operational workflows across different days for customer onboarding.

Option C: Custom Lightning Web Component
While a custom Lightning Web Component (LWC) can present programmatic UI components, using code to manage long-running, multi-step, multi-user orchestration introduces unnecessary development and maintenance overhead. Declarative features like Flow Orchestration should always be prioritized over custom code.

Option D: Screen flow
A screen flow guides a single user through a synchronous UI wizard in a single session. It cannot natively orchestrate complex, multi-day workflows that assign work items asynchronously to multiple different users across separate stages of a lifecycle.

Reference:
→ Salesforce Help - Flow Orchestration confirms that Flow Orchestration orchestrates multi-step, multi-user processes across stages over time.

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