Praxis Academy
Home › Platform App Builder › User Interface

Platform App Builder practice questions: User Interface

User Interface is 17% of the Salesforce Certified Platform App Builder exam. It covers Lightning App Builder, quick actions, navigation and the mobile app. Try these 13 free questions, then open each answer to see why every option is right or wrong.

01

A services manager needs the team to set case priority in a consistent way. Which feature should the Platform App Builder use to achieve this?

  1. In App Guidance
  2. Path
  3. Flow
  4. Next Best Action
Show answer

Answer: B

A. In App GuidanceIncorrect. In-App Guidance displays prompts and walkthroughs, but it is not tied to individual picklist values, so it cannot coach per priority.
B. Path ✓Correct. Path is built on a picklist like Case Priority and shows Key Fields and Guidance for Success per value, so all reps follow the same instructions.
C. FlowIncorrect. A screen flow is a heavier custom build for one picklist and does not offer in-place guidance the way Path does.
D. Next Best ActionIncorrect. Next Best Action surfaces recommendations from strategies; it does not standardize how a field gets filled in.

Why: The goal is to coach reps directly on the record so they all choose the same Case Priority value in the same circumstances. Path is built on a picklist field such as Priority, and for each value an admin can add Key Fields and Guidance for Success. Every rep sees identical instructions at the moment of choosing, which keeps priority entry consistent. Reference: Guide Users with Path

02

A biotech firm uses a Lightning record page that is enabled for both desktop and the mobile app. The Platform App Builder installed a custom Lightning component from AgentExchange, yet users cannot see the component on their mobile devices. What is causing the problem?

  1. The component was built for Desktop Pages.
  2. The component has to be activated.
  3. The record page template cannot support mobile devices.
  4. The record page has to be activated.
Show answer

Answer: A

A. The component was built for Desktop Pages. ✓Correct. The component's configuration can restrict it to the desktop form factor, so it never renders on mobile even though the page supports mobile.
B. The component has to be activated.Incorrect. Components on a page do not need a separate mobile activation.
C. The record page template cannot support mobile devices.Incorrect. The scenario states that the record page supports both mobile and desktop.
D. The record page has to be activated.Incorrect. The page is clearly active, because it appears on desktop.

Why: The page already supports both form factors, and the component displays on desktop, so the issue lies with the component itself. A Lightning component's configuration declares which form factors it supports, and a developer can limit it to desktop only. If so, Lightning App Builder will not render it on mobile regardless of how the page is set up. Reference: Custom Lightning Page Components

03

A biotech company is implementing Salesforce for the first time. Leadership wants the sales team and the marketing team to see different navigation menus in the Salesforce mobile app. Which approach can the Platform App Builder use to meet this need?

  1. Create public groups for sales and marketing and build a mobile navigation menu for each group.
  2. Create sales and marketing apps and assign each app to the matching profiles.
  3. Create sales and marketing roles and assign a custom home page layout to each role.
  4. Create mobile navigation menus for the sales and marketing profiles.
Show answer

Answer: B

A. Create public groups for sales and marketing and build a mobile navigation menu for each group.Incorrect. Mobile navigation menus are not configured per public group.
B. Create sales and marketing apps and assign each app to the matching profiles. ✓Correct. Mobile navigation is defined per Lightning app, so separate Sales and Marketing apps assigned to the right profiles give each team its own menu.
C. Create sales and marketing roles and assign a custom home page layout to each role.Incorrect. Home page layouts affect the Home page, not the mobile navigation menu.
D. Create mobile navigation menus for the sales and marketing profiles.Incorrect. Navigation menus belong to the app, not directly to profiles.

Why: In the mobile app, the navigation menu comes from the Lightning app a user is in, not from the profile directly. Building separate Sales and Marketing apps, each with its own navigation items, and assigning each app to the right profiles gives every team its own menu. Users then land in the app meant for them on mobile. Reference: Create Lightning Apps

04

A biotech business wants to streamline how users create opportunity records related to an Account. Many of the fields can be filled in from the Account record. Other fields need the user to enter them. What should the Platform App Builder configure to meet this requirement?

  1. Quick action on the Account object
  2. Assignment rule fired by an Account update
  3. Quick action on the Opportunity object
  4. Assignment rule fired by an Opportunity update
Show answer

Answer: A

A. Quick action on the Account object ✓Correct. A Create a Record action on Account can predefine opportunity fields from the account and leave the rest for the user to complete.
B. Assignment rule fired by an Account updateIncorrect. Assignment rules set record owners; they neither create records nor pre-fill fields.
C. Quick action on the Opportunity objectIncorrect. An Opportunity action does not run in the account's context, so it cannot pull account values.
D. Assignment rule fired by an Opportunity updateIncorrect. Assignment rules set record owners; they neither create records nor pre-fill fields.

Why: Users should create an Opportunity from its Account, with some fields pre-filled from the Account and others typed in. A Create a Record quick action on Account runs in the Account's context, so Predefined Field Values can carry Account data onto the new Opportunity. The action layout can also include editable fields for the values the user must supply. Reference: Create Object-Specific Quick Actions

05

The finance team at a biotech company requires each Expense_Report__c record to be approved by the employee's manager first and then, when the total exceeds $5,000, by the chief financial officer (CFO). They want one declarative process that sends the request to each approver in order, records every response, and updates the Expense Report's Status field once final approval is given. Which Salesforce feature should the Platform App Builder use?

  1. A record-triggered flow with a Decision element that sends the Expense Report down different paths based on its amount.
  2. A validation rule on Expense_Report__c that prevents saving until a custom Approved_By__c field has a value.
  3. A flow approval process with sequential approval steps for the manager and the CFO.
  4. A screen flow, launched from the Expense Report record page, that asks the manager and the CFO to enter their decision.
Show answer

Answer: C

A. A record-triggered flow with a Decision element that sends the Expense Report down different paths based on its amount.Incorrect. A Decision can branch, but a record-triggered flow cannot send a record to a person, wait for an answer and then continue.
B. A validation rule on Expense_Report__c that prevents saving until a custom Approved_By__c field has a value.Incorrect. A validation rule only stops saves; it neither routes records for approval nor tracks approvers.
C. A flow approval process with sequential approval steps for the manager and the CFO. ✓Correct. Sequential approval steps (manager, then CFO when the amount is over $5,000) track each response and run final approval or rejection actions.
D. A screen flow, launched from the Expense Report record page, that asks the manager and the CFO to enter their decision.Incorrect. A screen flow depends on each person launching it by hand and does not track an approval chain.

Why: The company needs a multi-step, declarative approval: manager first, then the CFO only for amounts above $5,000, with each response tracked and Status updated at the end. An approval process supports sequential steps, each with its own approver and entry criteria, records every approver's response, and runs final approval or rejection actions such as field updates. No custom logic is needed to track state across approvers. Reference: Set Up an Approval Process

06

To let users set the record sort order and hide actions on a related list, which Lightning component should the Platform App Builder choose?

  1. Related Lists
  2. Related List - Single
  3. Related List Quick Links
  4. Dynamic Related List - Single
Show answer

Answer: D

A. Related ListsIncorrect. The Related Lists component displays all related lists but cannot set sort order or hide actions per list.
B. Related List - SingleIncorrect. Related List - Single is the basic version without custom sort order or action hiding.
C. Related List Quick LinksIncorrect. Related List Quick Links provides links to related lists, not configurable list details.
D. Dynamic Related List - Single ✓Correct. Dynamic Related List - Single supports custom sort order, filters and hidden actions.

Why: Lightning App Builder offers several related list components, but only one lets the admin set a custom record sort order and hide specific actions. Dynamic Related List - Single provides that fine-grained control, along with filters. It is the component to use when sorting, filtering and action visibility are all required. Reference: Create Dynamic Related Lists in Lightning App Builder

07

A business user at a biotech company wants to edit an Account directly while on an opportunity record. What should the Platform App Builder build so the user can make these changes?

  1. Formula fields that display the Account fields
  2. An update record action with a details component
  3. An update record item with a related record component
  4. Opportunity fields updated by a process
Show answer

Answer: C

A. Formula fields that display the Account fieldsIncorrect. Formula fields are read-only, so users cannot edit the account through them.
B. An update record action with a details componentIncorrect. The Details component shows the current record's fields, not the account's.
C. An update record item with a related record component ✓Correct. A Related Record component on the opportunity page, paired with an update action, lets users edit Account fields without leaving the record.
D. Opportunity fields updated by a processIncorrect. Automation that updates opportunity fields does not let the user edit the account directly.

Why: The user is on an Opportunity but needs to edit fields stored on its Account, without leaving the page. The Related Record component shows and edits a related record's fields on the current record's Lightning page, using an update action to define the fields. Changes save straight to the Account record. Reference: Related Record Component

08

An app builder wants to add a custom component to the utility bar, but the component does not appear as an option. How must the component be tagged?

  1. For use in App Manager.
  2. For use in Lightning App Builder.
  3. For use on record pages.
  4. For use on the utility bar.
Show answer

Answer: D

A. For use in App Manager.Incorrect. App Manager is not a component target.
B. For use in Lightning App Builder.Incorrect. Availability in Lightning App Builder alone does not make it available on the utility bar.
C. For use on record pages.Incorrect. Targeting record pages does not make the component available on the utility bar.
D. For use on the utility bar. ✓Correct. The component needs the utility bar target (for example, lightning__UtilityBar) to appear as a utility item.

Why: Custom Lightning components only appear in contexts declared in their configuration; for an LWC this is the targets section of the .js-meta.xml file. To be selectable as a utility item, the component must be tagged for the utility bar, specifically the lightning__UtilityBar target. Reference: lightning__UtilityBar Target

09

A user has the permissions needed for inline editing, yet cannot inline edit records in a particular list view. What should the app builder check first?

  1. Whether another user has locked the selected list view
  2. Whether the list view's sharing settings exclude the user
  3. Whether the user built a chart on the list view
  4. Whether the list view includes records of more than one record type
Show answer

Answer: D

A. Whether another user has locked the selected list viewIncorrect. List views cannot be locked by another user.
B. Whether the list view's sharing settings exclude the userIncorrect. The scenario states the user already has the necessary access.
C. Whether the user built a chart on the list viewIncorrect. A list view chart has no effect on inline editing.
D. Whether the list view includes records of more than one record type ✓Correct. Inline editing requires the list view to be filtered down to one record type.

Why: Because the user's permissions are already confirmed, the cause must lie in how the list view is configured. Inline editing in a list view only works when the view is limited to a single record type. If the view shows records from several record types, inline editing is turned off for the whole list. Adding a Record Type filter to the list view restores the pencil icon. Reference: Considerations for Inline Editing in a List View in Lightning Experience | Salesforce Help

10

An app builder used the Lightning Object Creator to build a new object with its fields and loaded all of its data. The next step is configuring the Lightning Record Page. Which component must be on the page so that every field from the page layout is visible?

  1. Highlights Panel
  2. Recommendations
  3. Record Detail
  4. Path
Show answer

Answer: C

A. Highlights PanelIncorrect. The Highlights Panel displays only a handful of compact layout fields.
B. RecommendationsIncorrect. Recommendations displays Next Best Action suggestions.
C. Record Detail ✓Correct. Record Detail displays the fields exactly as arranged on the object's page layout.
D. PathIncorrect. Path displays stage progress, not the full set of fields.

Why: The Record Detail component renders the page layout assigned to the user's profile and record type, including all of its sections and fields, directly on the Lightning Record Page. Highlights Panel, Recommendations and Path each present only a small slice of information. Reference: Create and Configure Lightning Experience Record Pages | Salesforce Help

11

A manufacturer wants users who are viewing a Contract tied to an Account to be able to open the pricing guidelines document easily. What should an app builder use to give quick access to the document?

  1. A custom detail page link on the Contract object
  2. A Quick Action on the Account object
  3. A custom detail page link on the Account object
  4. A Quick Action on the Contracts object
Show answer

Answer: A

A. A custom detail page link on the Contract object ✓Correct. A detail page link on Contract opens the document in one click while the user is on the contract.
B. A Quick Action on the Account objectIncorrect. Quick actions create or update records, and this one sits on the wrong object.
C. A custom detail page link on the Account objectIncorrect. Users viewing a Contract are not on the Account page.
D. A Quick Action on the Contracts objectIncorrect. Quick actions handle record creation or updates, not links to documents.

Why: Custom links (detail page links) are the declarative way to send users to a URL or to a file stored in Salesforce. Since users need the document while looking at a Contract, the link belongs on the Contract object's page layout. Quick actions create or update records; they are not meant for opening a reference document. Reference: Custom Links Example: Linking to Documents | Salesforce Help

12

A staffing agency's Candidate object has a Previous Experience checkbox and a Years of Previous Experience number field. Recruiters want the number field to appear only when Previous Experience is checked. What should the app builder use?

  1. Build two page layouts and a process that switches layouts when Previous Experience is checked.
  2. Set up a field dependency between Previous Experience and Years of Previous Experience.
  3. Use Dynamic Forms to show Years of Previous Experience when Previous Experience is checked.
  4. Add a Visualforce component to the candidate page layout that conditionally shows the fields.
Show answer

Answer: C

A. Build two page layouts and a process that switches layouts when Previous Experience is checked.Incorrect. Switching layouts through automation is a clumsy, outdated workaround.
B. Set up a field dependency between Previous Experience and Years of Previous Experience.Incorrect. Field dependencies restrict picklist values and cannot show or hide a number field.
C. Use Dynamic Forms to show Years of Previous Experience when Previous Experience is checked. ✓Correct. A Dynamic Forms visibility rule displays Years of Previous Experience only when the checkbox is checked.
D. Add a Visualforce component to the candidate page layout that conditionally shows the fields.Incorrect. Visualforce means code, while a declarative feature already handles this.

Why: Dynamic Forms lets an app builder place individual fields on the Lightning Record Page and give each one a visibility rule. The Years of Previous Experience field can be set to appear only when the Previous Experience checkbox is true, with no code. Field dependencies filter picklist values; they cannot hide a number field. Reference: Dynamic Forms Tips and Considerations | Salesforce Help

13

While troubleshooting, a Platform App Builder must figure out why a user does not see the record page's Field Sections on a mobile device. What should the app builder do?

  1. Return to standard Page Layouts for mobile users and keep Dynamic Forms for desktop users.
  2. Add more Field Section components to streamline the Mobile layout.
  3. Turn on Dynamic Forms and Dynamic Highlights on Mobile in Salesforce Mobile App Studio.
  4. Apply visibility rules to tune the page for Mobile.
Show answer

Answer: C

A. Return to standard Page Layouts for mobile users and keep Dynamic Forms for desktop users.Incorrect. Reverting to page layouts abandons Dynamic Forms rather than fixing the mobile setting.
B. Add more Field Section components to streamline the Mobile layout.Incorrect. Extra Field Sections still will not render on mobile.
C. Turn on Dynamic Forms and Dynamic Highlights on Mobile in Salesforce Mobile App Studio. ✓Correct. Enabling Dynamic Forms and Dynamic Highlights for mobile in Salesforce Mobile App Studio makes Field Sections appear in the mobile app.
D. Apply visibility rules to tune the page for Mobile.Incorrect. Visibility rules do nothing while Dynamic Forms is disabled on mobile.

Why: Dynamic Forms components, Field Sections included, do not appear in the Salesforce mobile app by default. A separate setting in Salesforce Mobile App Studio must be enabled to render Dynamic Forms and Dynamic Highlights on mobile. Until it is turned on, mobile users see the assigned page layout instead. Reference: Dynamic Forms on Mobile

Find out if you're ready to pass

Take the free Platform App Builder diagnostic: 20 questions, no account needed. Then unlock all 241 questions, full practice exams and the study guide.

Start the free diagnosticSee plans

Other sections of this exam