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

The correct answer is C.

To show Component records as a related list on Product, the app builder should create a relationship field on the child object, Component, pointing to the parent object, Product. Salesforce documentation explains that when a lookup relationship is defined, the lookup field is added on one object and a related list can be shown on the associated object’s page layout.

A is unnecessary unless the requirement is many-to-many. B is incorrect because a roll-up summary does not create a related list. D is incorrect because the relationship field direction is wrong; the field should be on Component, not Product.

===========

The correct answer is B. User will be presented with a “Record Lock” notification.

When a record is submitted for approval, Salesforce locks the record to prevent users from editing it during the approval process. Salesforce documentation states that records submitted for approval are locked, and by default only admins can edit locked records unless editability settings allow otherwise.

The employee submitted the Opportunity for approval, so the employee cannot simply edit the Description field after submission. The expected user experience is a locked-record message.

===========

A Lightning Component tab is the native mechanism for exposing a standalone Lightning component as a navigation item. Salesforce instructs administrators to create a custom Lightning Component tab for the component and then add that tab to the desired Lightning app through App Manager ' s Navigation Items configuration. Salesforce also identifies Lightning component tabs as supported navigation-bar items. The Utility Bar is designed for persistent productivity utilities displayed while users remain on another page, not for a component that must function as a primary navigation destination. A dashboard adds unnecessary indirection, and a Web Tab is designed for external web content rather than directly surfacing a Salesforce Lightning component. Therefore, creating a Lightning Component tab and adding it to the Sales Operations application ' s navigation menu is the correct solution.

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

The correct answers are A. Dynamic Actions and C. Approval Process.

An Approval Process is required because sales managers must provide formal sign off when an Opportunity discount meets the defined criteria. Salesforce approval processes define the criteria a record must meet, the steps required for approval, and who must approve it.

Dynamic Actions are also needed because Universal Containers wants the sign-off action available quickly from the Opportunity record page. Dynamic Actions let app builders control which actions appear on Lightning record pages based on conditions.

Why others are incorrect:

Schema Builder is for data model design, not approval/sign-off UI behavior.

Validation Rule can block invalid data, but it does not provide manager approval or sign-off.

===========

The correct answer is B. Verify there is an Apex test that provides test coverage for the flow.

For deploying an active autolaunched flow to production, Salesforce requires flow test coverage. Salesforce documentation states that before deploying a process or autolaunched flow as active, the org must meet flow test coverage requirements, and Apex tests must cover active processes and active autolaunched flows.

A is not the main deployment consideration for making the flow active in production.

C is incorrect because Salesforce does not require 100% flow test coverage.

D is incorrect for this scenario because the requirement is to deploy it already active, not manually activate it after deployment.

===========

The correct answer is A. A hyperlink to the parent Account of the parent Opportunity.

A formula field can use cross-object references to parent records, and Salesforce states that cross-object formulas can reference fields from objects up to 10 relationships away. Since Opportunity Product relates to Opportunity, and Opportunity relates to Account, a formula on Opportunity Product can reference the parent Opportunity’s Account.

Salesforce also supports the HYPERLINK() formula function, which creates a clickable link from specified link text to a specified URL. So a formula field can be configured to create a hyperlink to the Account record related to the parent Opportunity.

B is incorrect because formula field data types do not include Rich Text Area as a formula return type.

C is incorrect because Salesforce restricts formulas from using long text area, encrypted, or Description fields.

D is not the best verified answer because large cross-object concatenations can run into formula relationship, size, or complexity limits, while the clearly supported Platform App Builder use case here is the cross-object HYPERLINK formula.

===========

The correct answer is A. Account Object .

Roll-up summary fields are created on the parent object , because the summary value is displayed on the parent record. Here, the KPI values need to appear for each Account , and they summarize related Opportunity records. Therefore, the app builder should go to the Account object in Object Manager and create roll-up summary fields there.

For this requirement, the app builder would create separate roll-up summary fields on Account, such as:

Count of open Opportunities

Count of won Opportunities

Salesforce documentation describes roll-up summary fields as fields that calculate values from related records, such as records in a related list.

C. Opportunity Object is incorrect because Opportunity is the child/related record being counted.

D. Lightning App Builder is incorrect because Lightning App Builder controls page layout/components, not the creation of roll-up fields.

B. Lightning Object Creator is used to create objects from spreadsheets, not build rollups.

===========

The correct answer is C. Configure Campaign Hierarchies and Campaign statistics.

To understand return on investment for an advertising buy, Universal Containers should use Salesforce Campaigns, especially Campaign Hierarchies and campaign reporting/statistics. Salesforce campaign hierarchy documentation explains that child campaign metrics roll up to the parent campaign, and Salesforce campaign reports can include campaign-hierarchy statistics for aggregate values.

The private security model does not require changing the whole org to public. The business need is marketing ROI tracking, so Campaigns are the correct feature.

A is incorrect because an opportunity pipeline report does not directly track advertising campaign ROI.

B is incorrect because Account Hierarchies and roll-up summaries are not the standard solution for campaign ROI.

D is incorrect because changing to a public security model is unnecessary and weakens data security.

===========

The requirement specifies detailed descriptions that can include pictures and links. Salesforce Rich Text Area fields support:

Multiple lines of text

Inline images

Hyperlinks

Formatting (bold, italic, lists)

Salesforce documentation confirms that Rich Text Area fields are the standard choice when storing formatted content on a record. (Salesforce Help)

D. Long Text Area supports only plain text, not images or links.

C. URL is for a single web address only.

B. Lightning Web Component is for custom UI elements, not a field type.

===========

The correct answer is D. Roll-up summary field.

Cloud Kicks wants to display a count of related Opportunities on the Account record where the Opportunities are Closed Won and have a Close Date within the last year. A roll-up summary field is the correct declarative feature because it calculates values from related records, including counts, sums, minimums, and maximums. Salesforce documentation confirms that roll-up summary fields calculate values from related records and can display values on the parent record.

The app builder can create a roll-up summary field on Account with filter criteria such as:

Stage = Closed Won

Close Date = Last 365 Days / Last Year

Why others are incorrect:

Activity timeline displays activities, not Opportunity counts.

Formula field cannot count multiple child Opportunity records.

Validation rule blocks invalid saves; it does not calculate related record totals.

===========

The correct answer is A. Path.

Sales managers want reps to see recommendations, sales strategies, and key fields at each step of the Opportunity sales process. Salesforce Path is designed for exactly this. Path can highlight key fields and provide customized Guidance for Success for each stage of a process.

For Opportunities, Path can show reps which fields matter at each sales stage and provide stage-specific guidance such as qualification tips, sales strategy, or next-step recommendations.

C. Approval Process is for record approval routing.

D. Global Action is for creating or updating records quickly, not guiding users through sales stages.

B is not the correct Salesforce feature for this requirement.

===========

The correct answer is B. Actions & Recommendations component.

The Actions & Recommendations component is used to give agents a guided to-do list/checklist on a record page. Salesforce documentation describes it as a component that can show flows, quick actions, and recommendations so agents can complete required steps consistently. This matches the requirement to provide service agents with checklist items when servicing a Case.

Why others are incorrect:

A “Business component” is not the standard Salesforce feature for this.

Activity Timeline shows activities, not a required checklist.

Highlights Panel shows key fields and actions, not guided service steps.

===========

The actions described require an after-save record-triggered flow because the automation must create additional Salesforce records and invoke a notification action after the triggering Case is saved. Salesforce explains that after-save flows handle actions dependent on a successfully saved record, including creating records, updating related records, sending emails, and other actions. The Send Custom Notification core action is also directly available in Flow Builder. A before-save flow is optimized for changing or validating fields on the triggering record and does not support this full set of post-save operations. A Screen Flow would unnecessarily require user interaction, while a platform event-triggered flow requires a platform event rather than a Case record change. Therefore, Actions and Related Records after save is the appropriate architecture.

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

The Automation Lightning App ' s Monitor tab is Salesforce ' s centralized interface for examining failed and paused flow interviews. Salesforce states that the Monitor tab displays failed interviews, their error information, and details needed to determine why execution failed. From the failed interview details, an administrator can open the run in debug mode and inspect the execution information without requiring the user to reproduce the issue. This directly satisfies the requirement to troubleshoot intermittent production failures from historical flow runs. Option A focuses primarily on paused interviews and is not the current comprehensive monitoring experience. Apex Replay Debugger is intended for Apex debugging rather than declarative Flow execution. Running the flow manually as another user creates a new test execution rather than analyzing the specific production failures that already occurred.

The correct answer is C. Flow.

The requirement is to automatically delete rejected Quote records. Salesforce Flow is the correct declarative automation tool because Flow can identify records and delete them using the Delete Records element.

Why not the others:

Approval Process routes records for approval. Einstein Next Best Action recommends actions. Validation Rule prevents bad saves. None of those tools is designed to delete rejected child records automatically.

===========

The correct bulk-safe Flow pattern is to modify each current Case with an Assignment element and add the modified record to a record collection variable. After the Loop finishes, one Update Records element should update the complete collection. Salesforce explicitly warns against putting Get Records, Create Records, Update Records, or Delete Records elements inside loops because repeated SOQL or DML operations can quickly exceed governor limits. Trailhead ' s recommended pattern is to retrieve records before the loop, use assignments while iterating, store changed records in a collection, and perform one database update after the loop. A Collection Filter does not replace the collection used to stage modified records. An Update Records element inside the loop defeats the stated requirement for one database operation. Therefore, Assignment plus a collection variable is the correct architecture.

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

The correct answers are B. Apex and C. AppExchange.

Cloud Kicks needs to count related Case records on Account based on open and closed status. Standard roll-up summary fields work only in supported roll-up relationships, mainly master-detail relationships. Salesforce documentation states that lookup relationships do not support roll-up summary fields.

Because Cases are related to Accounts through a lookup-style relationship, native roll-up summary fields are not the best available option in this answer set. The app builder can meet the requirement by using:

Apex — Apex triggers can run before or after record changes such as insert, update, or delete, allowing custom logic to recalculate the open and closed Case counts on the Account.

AppExchange — AppExchange roll-up tools, such as lookup roll-up packages, can summarize records across lookup relationships without building custom code.

Why others are incorrect:

Validation Rule prevents invalid data entry; it does not calculate related record counts.

Approval Process routes records for approval; it does not summarize Case counts.

===========

The correct answer is D. The Owner field on the Master record.

In a master-detail relationship, the detail record does not have independent ownership. Salesforce documentation states that the Owner field on the detail object isn’t available and is automatically set to the owner of the related master record.

Sharing is also controlled by the parent/master record. Salesforce Help explains that when a custom object is on the detail side of a master-detail relationship, its organization-wide default is set to Controlled by Parent.

A and C are incorrect because the detail record does not maintain independent ownership in a master-detail relationship. B is incorrect because ownership is not determined by a default owner setting on the parent object; it comes from the actual Owner field on the master record.

===========

Agentforce is Salesforce ' s platform for autonomous AI agents that can understand requests, reason over context, retrieve business information, determine appropriate next steps, and execute actions. Salesforce describes Agentforce agents as autonomous and proactive applications capable of taking action with or without continuous human intervention. Agents can use Salesforce CRM data and invoke flows, Apex, APIs, prompts, and other configured actions to complete business tasks. This directly matches the requirement for end-to-end customer service handling. Case Assignment Rules only route Cases. Experience Cloud with Live Chat provides customer interaction channels but does not independently reason and execute complete workflows. Einstein Bots provide conversational automation but do not represent the current autonomous agent architecture described in the scenario. Agentforce is therefore the verified answer.

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