Platform-App-Builder Salesforce Certified Platform App Builder (Plat-Admn-202) Free Practice Exam Questions (2026 Updated)

The correct answer is D. Universal Containers wants the real-time value of the Account’s Support Level picklist to appear on related Case records. The best declarative solution is a cross-object formula field on Case that references the related Account field.

Because Support Level is a picklist, the formula should use the TEXT() function to return the picklist value as text. Salesforce documentation states that cross-object formulas can reference fields from related objects, and Salesforce’s TEXT function supports picklist values in formulas.

Example formula concept:

TEXT(Account.Support_Level__c)

Why others are incorrect:

A is incorrect because the formula must be on Case, not Account.

B is incorrect because Case already relates to Account; a new lookup alone does not display the value.

C is incorrect because roll-up summary fields summarize child records; they do not copy/display a parent picklist value on child Case records.

===========

A Text field configured as External ID and Unique satisfies both requirements. Existing Invoice Numbers can be migrated directly from the external system without changing their values, while the Unique attribute prevents duplicate Invoice Numbers from being stored later. Salesforce defines an External ID as a field containing an identifier from a system outside Salesforce and supports Text fields as External IDs. Salesforce also states that marking the field Unique prevents duplicate values and makes it suitable for record matching and future data operations. An Auto Number field would generate Salesforce-controlled values and therefore would not preserve externally assigned Invoice Numbers. Maintaining separate legacy and Salesforce numbering fields is unnecessary when one field can preserve the external identifier and enforce uniqueness. Salesforce

================

The correct answer is B. Validation Rule.

DreamHouse Realty wants to prevent an Opportunity from entering the Qualified stage unless Expected_Close_Date__c is populated. A validation rule is the correct tool because Salesforce validation rules check whether record data meets specified criteria before the user can save the record.

A validation rule could check:

Stage = Qualified

AND

Expected_Close_Date__c is blank

If both are true, Salesforce blocks the save and displays an error message.

A. Page Layout can make a field visible or required on a layout, but it cannot conditionally require the field only when Stage equals Qualified.

C. Activity History is unrelated.

D. Record Type controls business processes and layouts but does not enforce this condition by itself.

===========

The Custom Error element allows a record-triggered flow to prevent the triggering database change and present a targeted error directly to the user. Salesforce supports displaying the message either at the record-page level or as an inline error on a specific field, which exactly meets the requirement to place the error on the Opportunity Stage field. When the Custom Error element executes, Salesforce rolls back the record change until the user corrects the problem. A Screen element is not valid for providing this experience inside a background record-triggered flow. An Assignment on a fault path merely stores values and does not automatically surface a validation-style error. Ending the flow also does not prevent the record from being saved. Therefore, the Custom Error element is the correct declarative equivalent to validation-style feedback. Salesforce

================

The correct answer is C.

The Lightning record page already supports both mobile and desktop, but the downloaded custom component is not visible on mobile. That points to the component itself, not the page activation. Lightning components must be configured to support the required form factors. Salesforce developer documentation explains that components can be configured for desktop form factor Large, phone form factor Small, or both.

So, if the AppExchange component was built only for desktop pages or only supports the large form factor, users cannot view it in the Salesforce mobile app.

A and D are incorrect because the issue is not page activation if the page already supports mobile and desktop. B is incorrect because the scenario states the record page supports both mobile app and desktop.

===========

The correct answer is B.

Salesforce supports roll-up summary fields for summarizing related records, including scenarios involving Account and related Opportunity values. However, Salesforce documentation states that if Advanced Currency Management is enabled, currency roll-up summary fields are invalid when they are on Accounts and summarize Opportunity values.

Because the VP wants to aggregate Opportunity Amount values on Account, the app builder cannot create that roll-up summary field if Advanced Currency Management is enabled.

Why not others:

A is not the stated Salesforce limitation.

C is wrong because roll-up summary fields are available on Account in supported scenarios.

D is wrong because currency fields can be used in roll-up summaries generally; the issue is specifically Advanced Currency Management with Account-to-Opportunity currency rollups.

The correct answer is C. Flow.

This requirement needs automation that can do multiple things: update the To Be Installed checkbox when a Lift is sold, then notify an external system the next day using an outbound message. Salesforce states that Flow Builder is the optimal tool for triggered automation because it combines workflow and process automation capabilities in one point-and-click tool. Record-triggered flows can run when records are created, updated, or deleted, and can update records, send notifications, initiate processes, and maintain data consistency.

The “next day” timing points to a scheduled path in a record-triggered flow. Salesforce explains that scheduled paths delay automation for minutes, hours, days, or months after the triggering record change. Salesforce also documents outbound messages as a Flow Builder core action for record-triggered flows, used to send a SOAP message to a designated endpoint.

Approval Process is for approvals, Validation Rule only prevents invalid data, and Assignment Rule is for assigning records such as leads or cases. None of those tools can meet the full requirement.

A Data 360-triggered flow is designed to start when specified conditions are met on a Data 360 Data Model Object rather than on a standard Salesforce database record. Salesforce documentation describes this flow type as automation that responds to changes occurring in a DMO or calculated insight and uses Data 360 data actions/events to initiate the flow. The app builder can select the loyalty DMO, define a condition such as Tier = Diamond, and then execute the required Salesforce actions when that data changes. A Salesforce record-triggered flow would require a Salesforce record change, which the question explicitly excludes. A schedule-triggered flow would introduce polling rather than near-real-time behavior, and a template-triggered prompt flow is intended for Prompt Builder. Therefore, Data 360-triggered flow is the appropriate architecture. Salesforce

================

Salesforce provides parent implicit access between certain standard objects. When a user receives access to a child Opportunity, Case, or Contact through ownership or sharing, Salesforce automatically provides that user with Read Only access to the associated parent Account. Sales Rep B therefore receives access to the Account because Rep B was manually granted access to the related Opportunity. No separate Account sharing operation is required. Salesforce specifically states that access to a child Opportunity can grant implicit Read Only access to its parent Account even when Account organization-wide defaults are Private. Territory membership is therefore not required for this particular access path. An Account Team could independently provide access, but the scenario does not state Rep B was added to one. The documented parent implicit-access mechanism directly explains the behavior. Salesforce

================

The intended answer is D , because the validation must check two error conditions before allowing the Opportunity to be saved as Closed Won :

Scheduled_Ship_Date__c is blank.

Scheduled_Ship_Date__c is more than 14 days after CloseDate .

Salesforce validation rules fire when the formula evaluates to True . Salesforce’s formula documentation confirms that ISPICKVAL(picklist_field, text_literal) is the correct syntax for comparing a picklist field such as StageName . Salesforce validation examples also show date arithmetic such as subtracting one date from another to check whether a date exceeds a required range.

The option text appears corrupted, but the correct exam concept is a validation rule that blocks Closed Won if the Scheduled Ship Date is blank or more than 14 days after the Close Date.

===========

The correct answer is D. Accordion.

For an object with 100+ fields, the app builder should avoid one large monolithic Record Detail area. Salesforce Trailhead explains that Dynamic Forms breaks the Record Detail component into individual field and section components, which can be placed in separate tabs and accordion sections.

Salesforce also states that moving lower-priority fields into tabs or accordion sections can improve page performance because the content is not visible when the page first loads.

A. Highlights panel is for key record fields and actions at the top of the page. B. Record detail would keep fields together in one large block. C. Field section groups fields, but the better component for breaking a large page into collapsible organized areas is Accordion.

===========

With Account organization-wide defaults set to Private, users cannot automatically see records owned by peers at the same role-hierarchy level. Salesforce sharing rules provide an exception to restrictive organization-wide defaults and can grant additional record access to selected users, roles, or public groups. If User A belongs to a public group targeted by an Account sharing rule, User A can receive access to User C ' s Account while User B does not. Being at the same role level as User C does not provide upward hierarchy access. “View All Fields” concerns field visibility and does not grant access to otherwise inaccessible records. Login access policies concern when or where users can authenticate, not access to one particular Account. Therefore, membership in a public group used by a sharing rule explains the different record visibility.

================

The correct answer is B. Create both customer and dealer as accounts, add each rep as a contact to the corresponding account and create an account hierarchy.

Customers and dealers are both separate business entities, and separate bills are sent to each. In Salesforce, business entities are best represented as Accounts, while the single individual at each business should be stored as a Contact under the correct Account. Salesforce account hierarchy is used to show parent-child relationships between related accounts.

Why not D? Account Teams represent internal Salesforce users working on an account, not external customer/dealer representation.

The correct answer is B. The deployed permission set will only contain changes related to the change set.

When permission sets are included in change sets, the deployment carries permission settings related to the components included in the change set. The existing permission set in production is not completely overwritten as a whole object, and field-level security changes can be included when the relevant fields are part of the deployment. Salesforce documents permission sets and profile settings as access settings that can be included with change sets.

A is incorrect because the whole permission set is not simply wiped and replaced.

C is incorrect because field-level security can be deployed when included properly.

D is close in plain language, but the more accurate exam answer is that the deployed permission set contains only changes related to the change set.

===========

The correct answer is D. For use on the utility bar.

For a custom Lightning web component to appear as an available component in the utility bar, it must be exposed in its metadata configuration with the lightning__UtilityBar target. Salesforce developer documentation states that lightning__UtilityBar enables a component to be used as a utility item in an app’s utility bar, and the component must be exposed with the appropriate target.

B. For use in Lightning App Builder is broader and not enough by itself for utility-bar availability. C. For use on record pages exposes the component for record pages, not the utility bar. A. For use in App Manager is not the correct component target wording.

===========

The verified answer is B because Salesforce explicitly states that Formula fields are read-only and cannot be converted to another data type . Consequently, the existing formula field cannot simply be converted into an editable Text field, which eliminates A and D. The app builder should create a new Text field on Opportunity, extract or otherwise capture the current calculated Specialty__c values, and load those values into the new field. Sales representatives can then independently edit the new Opportunity value without changes to Account automatically recalculating it. Option C creates the editable field but fails to preserve the existing calculated values unless they are migrated.

Change sets can be exchanged only between deployment-connected organizations, such as a production org and its own sandboxes. UMS Logistics is a separate production organization and has no deployment relationship with the UMS source environment, so an outbound change set cannot be sent there. Salesforce documents unmanaged packages as a mechanism for packaging metadata components in a source org, uploading the package, obtaining an installation URL, and installing those components into another Salesforce organization. A managed package is intended primarily for distributed applications requiring namespace and provider-controlled versioning, such as commercial AppExchange solutions, and is unnecessary for this evaluation transfer. A sandbox likewise cannot be refreshed from an unrelated organization ' s Developer sandbox. Therefore, the appropriate deployment vehicle is an unmanaged package installed through its generated URL.

Use a Component visibility filter. The issue is not object access or field access. The Contact Lightning record page is shared, but one component should be hidden for users with the Marketing profile. Salesforce Lightning App Builder supports visibility filters on Lightning page components, so the app builder can conditionally show or hide that component based on user/profile criteria.

Why not the others? AppExchange is unrelated. Detail page layouts control field layout, not visibility of a Lightning page component. Field-level security controls field access, not whether a large component appears on a Lightning record page.

===========

Use a Record-Triggered Flow optimized for Actions and Related Records.

Submitting a record for approval is an action in Flow. Salesforce provides a Submit for Approval action, and after-save record-triggered flows are used when the automation needs to perform actions or work with related records after Salesforce saves the triggering record.

Option A is wrong because Fast Field Updates is the before-save path, mainly for updating fields on the triggering record. It is not the right optimization for submitting an approval request. Option B still requires a custom button and manual user action. Option C is unrelated because this requirement is based on an Opportunity record change, not a platform event.

===========