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.
Salesforce 2026
Universal Containers needs automation that runs every Sunday at 2:00 a.m. The automation sets a custom
checkbox field, Inactive__c , to True on every Account whose standard Last Activity Date is more than 90
days in the past. The automation must evaluate all Account records and repeat on this schedule every week.
Which flow design should the Platform App Builder use?
A. A record-triggered flow on Account with a scheduled path set to run 90 days after each Account ' s Last Activity Date
B. An autolaunched flow that an app builder schedules to run every Sunday at 2:00 a.m.
C. A schedule-triggered flow on Account, set to a Weekly frequency with a Sunday 2:00 a.m. start time, with entry conditions selecting Accounts whose Last Activity Date is more than 90 days old
D. A schedule-triggered flow on Account, set to a Once frequency for the upcoming Sunday at 2:00 a.m., with entry conditions selecting Accounts whose Last Activity Date is more than 90 days old
Explanation
This question tests how to automate a recurring, bulk update on a fixed schedule. The automation must run every Sunday at 2:00 a.m., evaluate all Account records, and set a checkbox on those inactive for more than 90 days. The Platform App Builder must choose the flow type and frequency that repeat weekly and process many records at once.
✅ C. A schedule-triggered flow on Account, set to a Weekly frequency with a Sunday 2:00 a.m. start time, with entry conditions selecting Accounts whose Last Activity Date is more than 90 days old
A schedule-triggered flow runs at a set time and can repeat daily or weekly. Setting a Weekly frequency with a Sunday 2:00 a.m. start makes it recur automatically. Entry conditions on the Account object filter Accounts with Last Activity Date older than 90 days, and the flow then updates Inactive__c on every matching record in one run.
❌ A. A record-triggered flow on Account with a scheduled path set to run 90 days after each Account’s Last Activity Date
A scheduled path starts only after a record is created or updated and runs once, relative to that record’s date field. It does not re-evaluate all Accounts on a fixed weekly cycle. It also cannot run every Sunday at 2:00 a.m., so it does not meet the schedule requirement.
❌ B. An autolaunched flow that an app builder schedules to run every Sunday at 2:00 a.m.
An autolaunched flow has no built-in schedule settings and must be started by something else, such as Apex, another flow, or a process. An app builder cannot simply schedule it to repeat weekly from the flow itself. A schedule-triggered flow provides the start time, frequency, and record filtering needed here.
❌ D. A schedule-triggered flow on Account, set to a Once frequency for the upcoming Sunday at 2:00 a.m., with entry conditions selecting Accounts whose Last Activity Date is more than 90 days old
A Once frequency runs the flow a single time at the chosen date and time, then does not run again. The requirement says the automation must repeat every week. Only the Weekly frequency keeps the evaluation recurring, so this option fails despite the correct entry conditions.
🔧 Reference
🔗 Schedule a Flow – Salesforce Trailhead → confirms that schedule-triggered flows can run once, daily, or weekly, process many records at one time, and use a Start element object with criteria to select records.
Cloud Kicks (CK) needs to capture the tier for each Loyalty_Member__c record. CK has three fixed tier
values: Standard, Plus, and Elite.
The team wants to prevent users from entering inconsistent values and wants to filter and group Loyalty
Member reports by Tier.
Which field type should the Platform App Builder use?
A. A picklist field with the three values defined
B. A multi-select picklist field with the three values defined
C. A text field with no formatting constraints
D. A formula field that only allows three values
Explanation:
The requirement is to store one fixed loyalty tier per member, prevent inconsistent entry, and support report filtering and grouping. A single-select picklist with defined values is the appropriate field type.
✔️ Correct Option:
A. A picklist field with the three values defined.
✔️ A single-select picklist lets users choose only one tier—Standard, Plus, or Elite—for each Loyalty Member record. Defining the values prevents inconsistent or free-text entries, especially when the picklist is restricted. Picklist fields also support filtering and grouping in reports, allowing CK to analyze Loyalty Members by each individual tier.
❌ Incorrect Options:
B. A multi-select picklist field with the three values defined.
❌ A multi-select picklist allows users to select more than one tier, which does not match the requirement for one tier per Loyalty Member. It also stores selections as a semicolon-delimited string and has limitations when grouping or summarizing by individual values in reports.
C. A text field with no formatting constraints.
❌ A free-text field permits values such as “standard,” “STANDARD,” “Std,” or misspellings, so it cannot prevent inconsistent data entry. It can be filtered in reports, but it does not provide a controlled value set for reliable grouping and reporting by tier.
D. A formula field that only allows three values.
❌ Formula fields are calculated automatically and are read-only; users cannot select or enter a tier value on the record. A formula cannot act as the source field for capturing user-entered Loyalty Member tier data.
🔧 Reference:
→
Salesforce Help — Picklist Limitations
— Confirms that restricted picklists limit values to admin-defined entries and that multi-select picklists have reporting and grouping limitations.
→
Salesforce Help — Build a Formula Field
— Confirms that formula fields are automatically calculated and read-only on record detail pages.
A Platform App Builder created a change set for new fields and updated page layouts in a sandbox. After
deploying the change set to production, the page layout appears to be missing three fields that were previously
showing on the production layout.
What is causing this to happen?
A. The validation failed and the deployment was rolled back.
B. The newly deployed page layout overwrote the existing one in production when deployed.
C. The permissions to the fields were not included in the change set and therefore removed.
D. The page layout assignment needs to be updated after deployment.
Explanation:
This question tests your understanding of how change sets handle metadata components during deployments in Salesforce. When a page layout is included in an outbound change set and deployed to production, it performs a complete overwrite of the existing page layout component in the target environment. If the version of the page layout in the sandbox did not contain the three fields that were added or modified directly in production after the sandbox was created or refreshed, deploying the change set replaces the production layout with the sandbox version, effectively removing those three fields from view.
Correct Option:
Option B:
The newly deployed page layout overwrote the existing one in production when deployed. Because change set deployments for page layouts replace the target metadata entirely rather than merging changes incrementally, any customizations or field additions present solely in the production layout are overwritten by the incoming sandbox layout version.
Incorrect options:
Option A:
If validation failed, the entire deployment would have been blocked and rolled back, meaning no changes would have been applied to production at all, and the original layout would remain completely intact.
Option C:
Field-level security and profile permissions are deployed separately (if included in the change set) and do not automatically remove fields from a page layout component itself. The disappearance of fields from the layout UI stems from the layout file being overwritten, not from permission changes.
Option D:
Page layout assignment determines which profiles or record types are mapped to a specific layout. Changing assignments affects who sees a layout, not which fields are rendered inside the layout itself.
Reference:
→ Refer to Change Sets Overview and Component Behavior on official Salesforce documentation, which details how components overwrite existing targets during change set deployments.
Universal Containers is building a Screen Flow to enhance the user experience for creating new Opportunity
records and related Opportunity Products. If Opportunity Product creation fails, both the Opportunity and
Opportunity Product creation must be rolled back.
The current configuration is:
Screen Flow Start # Opportunity Screen # Create Opportunity # Opportunity Product Screen # Create
Opportunity Product # End
What change must the Platform App Builder make?
A. Add a Fault Path to Create Opportunity Product and Roll Back Records.
B. Move Create Opportunity after Opportunity Product Screen, then add a Fault Path to Create Opportunity Product and Roll Back Records.
C. Move Create Opportunity before Opportunity Screen, then add a Fault Path to Create Opportunity and Roll Back Records.
D. Add Delete Records after Create Opportunity Products.
Explanation:
The question tests error handling and transaction rollback in Salesforce Screen Flows. If creating an Opportunity Product fails, the flow must undo the earlier Opportunity creation as well. A fault path with a Roll Back Records element allows the flow to reverse pending record changes when the product creation fails.
🟢 Correct Option: B. Move Create Opportunity after Opportunity Product Screen, then add a Fault Path to Create Opportunity Product and Roll Back Records.
Screen elements create transaction boundaries, so the Opportunity created before the Opportunity Product Screen may already be committed and cannot be rolled back by a later fault path. Moving Create Opportunity after the final screen ensures both record creation operations occur in the same transaction. If product creation fails, the fault path invokes Roll Back Records to undo the pending Opportunity and Opportunity Product changes together.
🔴 Incorrect Options:
A. Add a Fault Path to Create Opportunity Product and Roll Back Records.
A fault path can handle product creation errors, but the Opportunity was created before another Screen element. That screen introduces a transaction boundary, so the earlier Opportunity creation may already be committed and cannot be rolled back with the product creation.
C. Move Create Opportunity before Opportunity Screen, then add a Fault Path to Create Opportunity and Roll Back Records.
This configuration does not address failures during Opportunity Product creation. The fault path on Create Opportunity handles errors from that element, not errors occurring later when the product is created.
D. Add Delete Records after Create Opportunity Products.
A Delete Records element placed after product creation cannot handle a failure that prevents the flow from reaching that element. Deleting records also does not provide the required atomic rollback of both record creations.
🔧 Reference:
⇒ Salesforce Help: Roll Back Records Element
Salesforce Help explains how the Roll Back Records element undoes pending record changes in the current transaction.
⇒ Salesforce Help: Flow Transaction Control
Salesforce Help explains how flow transactions are handled and why record creation must occur in the same transaction for the intended rollback behavior.
Universal Containers (UC) utilizes two custom picklist fields Called sales_Organization_c and Pricing_Tier _ Which validation rule should an app builder use to ensure Pricing Tier_c is required for customers with a Sales Organization__c value of Canada?
A. AND (ISPICKVAL (Sales Organization_c, ' Canada ' ), ISBLANK (TEXT (Pricing_Tier
B. IF (ISNULL(Sales_Organization_c= ' Canada ' , ISBLANK (TEXT (Pricing_Tier_c)), TRUI
C. ISPICKVAL (Sales Organization_c, ' Canada ' ) & ISNULL (Pricing_Tier_c)
D. OR (ISPICKVAL (Sales Organization_c, ' Canada ' ), ISBLANK (TEXT (Pricing_Tier_c));
Explanation:
This question tests the ability to construct a conditional validation rule that makes one picklist field required based on the value of another picklist field. The requirement is precise: Pricing_Tier__c must be mandatory only when Sales_Organization__c equals "Canada." To achieve this, the rule must combine two conditions using the AND function: the Sales Organization must be Canada, and the Pricing Tier must be blank. When both conditions are true, the validation rule fires and blocks the save .
✔️ Correct Option:
A. AND (ISPICKVAL (Sales Organization_c, ' Canada ' ), ISBLANK (TEXT (Pricing_Tier
This formula correctly uses ISPICKVAL to evaluate whether the picklist value is "Canada" and ISBLANK(TEXT(...)) to check if the Pricing Tier picklist is empty . The AND function ensures the error triggers only when both conditions are met simultaneously. This is the standard Salesforce pattern for conditionally requiring a picklist field, as confirmed by official documentation examples using the same structure .
❌ Incorrect options:
B. IF (ISNULL(Sales_Organization_c= ' Canada ' , ISBLANK (TEXT (Pricing_Tier_c)), TRUI
This syntax is malformed and does not follow Salesforce formula conventions. ISNULL is used for checking null values, not for comparing picklist values. The structure of the IF function is also incorrect, with mismatched parentheses and an incomplete logical flow. It cannot evaluate the condition properly.
C. ISPICKVAL (Sales Organization_c, ' Canada ' ) & ISNULL (Pricing_Tier_c)
The single ampersand (&) is the string concatenation operator in Salesforce, not a logical AND. Using it here would concatenate the results of the two functions into a text string rather than evaluating them as a logical condition. The rule would not behave as intended. Additionally, ISNULL is not the correct function for checking blank picklist fields; ISBLANK(TEXT(...)) is required.
D. OR (ISPICKVAL (Sales Organization_c, ' Canada ' ), ISBLANK (TEXT (Pricing_Tier_c));
The OR function triggers the validation error if either condition is true. This means the rule would fire whenever Sales Organization is Canada, regardless of whether Pricing Tier is filled—or whenever Pricing Tier is blank, regardless of the Sales Organization value. This does not meet the requirement of making the field required only for Canada, as it would block saves incorrectly in other scenarios.
🔧 Reference:
→ Salesforce Help: Require a Text Field to be populated when the ‘Other’ option is selected in a picklist — Demonstrates the exact AND(ISPICKVAL(...), ISBLANK(...)) pattern for conditionally requiring a field based on a picklist value.
→ Salesforce Help: ISPICKVAL — Confirms the correct syntax and usage of ISPICKVAL for evaluating picklist field values in formulas.
| Platform-App-Builder Exam Questions - Home | Previous |
| Page 3 out of 70 Pages |