Platform App Builder · Domain 4 of 5

Platform App Builder Domain 4: User Interface

User Interface covers how to shape what users see: Lightning record pages, Dynamic Forms and component visibility, custom buttons, links and actions, when a custom Lightning web component is needed, and actions and layouts for mobile.

Exam weight
17%
Official objectives
5
Estimated questions estimate
~10
Suggested study time estimate
9–11 hrs

About 14 min read Reviewed October 2026

Overview

User Interface holds 17% of the Platform App Builder exam, unchanged in the Summer '26 update, and now contains five objectives. They cover the user interface customization options available, custom buttons, links and actions, the declarative ways to add Lightning components to an app, the programmatic options for custom Lightning components, and choosing global and object-specific actions and layouts for the Salesforce mobile app. That last objective moved here from Salesforce Fundamentals.

The section is about delivering the right screen to the right user with the least custom work. Lightning App Builder, Dynamic Forms, Dynamic Actions and component visibility filters handle most needs without code. When they do not, an app builder should recognize that a developer must build a Lightning web component and know how it is then placed declaratively.

How it's tested

Questions describe who should see what on a page or in the mobile app and ask for the configuration with the least effort. Many offer page layouts, Dynamic Forms, record types and new Lightning pages as options. A smaller group asks when a requirement needs a custom Lightning web component.

  • Show it to some users

    Fields, components or buttons must appear only for certain profiles, devices or field values, and you choose visibility rules, Dynamic Forms, Dynamic Actions or page assignments.

  • Button, link or action

    A user needs a one-click way to create, update, navigate or launch a flow, and you choose a quick action, custom button, custom link or action type.

  • Mobile experience

    A field team works on phones, and you pick global or object-specific actions, compact layouts or mobile-friendly page configuration.

Reasoning it through

Sales managers want a discount approval panel to appear on Opportunity pages only when Discount__c is above 20%. A new page layout cannot react to a field value. Assigning a different Lightning page by profile also misses the condition. In Lightning App Builder, adding the component and setting a component visibility filter on Discount__c greater than 20 meets the requirement on the existing page.

Objectives 5

Official objectives from the Salesforce outline, in outline order.

4.1 Describe the user interface customization options.Lightning apps, record pages, Dynamic Forms, page layouts, compact layouts and list views.
What it means
Lightning Experience can be shaped at several levels. Lightning apps group tabs, utility items and branding for a set of users. Lightning record, home and app pages are built in Lightning App Builder and assigned by app, record type, profile and form factor. Page layouts control fields, related lists and buttons on the classic record detail, while Dynamic Forms place fields and sections directly on the Lightning page.
What to understand
Know what each option controls. Compact layouts decide the highlights panel fields and mobile record header. Record types assign different page layouts and picklist values. Dynamic Forms allow field-level visibility rules without multiple layouts. Path guides users through stages with key fields and guidance. List views, search layouts and themes also change the experience but not data security.
How it shows up
Questions ask which customization changes a specific part of the screen for a specific audience with minimal effort.
Common confusion
Thinking Dynamic Forms or page layouts restrict data access; they only control what is displayed.
4.2 Demonstrate the capabilities and use cases for custom buttons, links, and actions.Quick actions, custom buttons and links, and their placement.
What it means
Custom buttons and links open URLs, run JavaScript in Classic only, or launch Visualforce pages, and can be placed on detail pages or list views. Quick actions create, update or log records with prefilled values, launch screen flows, Lightning web components or Visualforce pages, and appear in the highlights panel, mobile action bar and feeds. Dynamic Actions show actions conditionally on Lightning pages.
What to understand
Know which to choose. Use a quick action to create a related record with defaults or update a record in a few clicks; use a flow action for guided multi-step input. Use a custom link for navigation that passes merge fields to another site. JavaScript buttons do not work in Lightning Experience, so replace them with quick actions or flows. Predefined field values reduce typing.
How it shows up
A user needs a one-click shortcut; you choose a quick action type, a flow action or a custom URL button.
Common confusion
Choosing a JavaScript custom button for Lightning Experience, where it is not supported.
4.3 Given a scenario, determine the declarative options available for incorporating Lightning components in an application.Lightning App Builder, standard and AgentExchange components, and visibility rules.
What it means
Lightning App Builder lets you drag standard components, custom components and components installed from AgentExchange onto app, home and record pages. You can set component properties, use templates, add tabs and accordions, and set component visibility filters based on fields, user attributes, permissions or device. Pages are activated as org default, app default, or by app, record type and profile.
What to understand
Know the activation hierarchy: an assignment for app, record type and profile overrides an app default, which overrides the org default. Know that component visibility filters can hide components for users or records without separate pages. Know that Lightning components can also be added to utility bars, Experience Cloud sites and flow screens declaratively once they exist.
How it shows up
Scenarios ask how to show a component or page only for certain users, record types or devices with minimal configuration.
Common confusion
Creating many separate Lightning pages when one page with visibility filters would meet the need.
4.4 Describe the programmatic customizations available for incorporating custom Lightning components in an application.When developers build Lightning web components and how they are exposed.
What it means
When standard components cannot meet a requirement, developers build Lightning web components, the current standards-based framework, or maintain older Aura components. A component's metadata configuration file sets targets such as record pages, app pages, flow screens, utility bar or quick actions, and exposes properties an admin can set in Lightning App Builder.
What to understand
An app builder does not write the code but must recognize when it is needed: highly interactive or custom-styled interfaces, complex client-side logic, or data views no standard component offers. Know that once a developer sets isExposed and the right targets, the component appears in Lightning App Builder like any standard component. Visualforce remains for legacy pages but is not the first choice for new Lightning work.
How it shows up
A requirement exceeds what standard components or Dynamic Forms can display; the answer involves a custom Lightning web component configured for the right target.
Common confusion
Choosing Visualforce for new Lightning Experience functionality when a Lightning web component is the recommended approach.
4.5 Given a set of requirements, determine the appropriate global, object-specific actions and layouts to optimize the Salesforce mobile user experience.Global and object-specific actions, compact layouts and mobile navigation.
What it means
Global actions are not tied to a record; they create records or log calls from anywhere, such as the mobile app's global actions menu, and the new records have no automatic relationship to a parent. Object-specific actions run in the context of a record and can create related records, update the record or log activity with that record linked. Compact layouts decide which fields show in the record header on mobile.
What to understand
Know where actions appear: in Lightning Experience and mobile, actions come from the page layout's mobile and Lightning actions section or from Dynamic Actions. Know that the mobile app uses the Lightning page with the phone form factor, so pages can be tailored to phones. Keep action layouts short and use predefined values so field users enter less data.
How it shows up
A mobile user needs to create a related record quickly from a parent; you choose an object-specific create action with predefined values.
Common confusion
Using a global action when the new record must be linked automatically to the record the user is viewing.

High-yield concepts

The terms, rules and formulas this domain turns into questions most often.

  • Lightning App Builder

    Point-and-click tool for building Lightning app, home and record pages.

    Remember
    The most specific activation wins when several assignments apply to a user.
    Tested as
    Central to most UI scenarios.
    Trap
    Forgetting that a more specific assignment overrides a default.

  • Dynamic Forms

    Places individual fields and sections on a Lightning record page with visibility rules.

    Remember
    Reduces the need for multiple page layouts.
    Tested as
    Answer when fields must appear conditionally.
    Trap
    Treating it as a security control.

  • Dynamic Actions

    Shows actions on Lightning pages based on conditions.

    Remember
    Conditions can use record fields, user attributes or device.
    Tested as
    Used when buttons should appear only in some situations.
    Trap
    Creating extra page layouts to vary buttons.

  • Component visibility filter

    Rule that shows or hides a component on a Lightning page.

    Remember
    Can use field values, permissions, user and device.
    Tested as
    Avoids building separate pages.
    Trap
    Cloning the page for each audience.

  • Compact layout

    Defines key fields in the highlights panel and mobile record header.

    Remember
    Assigned per record type.
    Tested as
    Mobile scenarios about header fields point here.
    Trap
    Editing the page layout to change the highlights panel.

  • Object-specific action

    Action in a record's context that creates related records or updates the record.

    Remember
    New records are linked to the source record automatically.
    Tested as
    Answer for create a related record from this record.
    Trap
    Choosing a global action and losing the relationship.

  • Global action

    Action available anywhere, not tied to a record.

    Remember
    Created records are not related to a parent automatically.
    Tested as
    Fits quick creation from the mobile home or utility bar.
    Trap
    Expecting it to prefill the parent record.

  • Predefined field values

    Default values set on a quick action's fields.

    Remember
    Reduce clicks and keep data consistent.
    Tested as
    Mobile and efficiency questions use them.
    Trap
    Hard-coding values with automation instead.

  • Lightning web component

    Standards-based custom component built by developers.

    Remember
    Must be exposed with targets to appear in Lightning App Builder.
    Tested as
    The answer when standard components cannot meet a UI need.
    Trap
    Assuming admins can build one declaratively.

  • Path

    Guidance component showing stages with key fields and tips.

    Remember
    Based on a picklist such as Stage or Status.
    Tested as
    Used when users need help moving records through a process.
    Trap
    Building a custom component for stage guidance.

Side by side

Concepts candidates mix up, compared on the point that decides the answer.

Controlling what users see on a record page

ConceptMeaningKey differenceCommon trap
Page layout Fields, related lists and buttons for a record type and profile. Static per assignment. Using many layouts where Dynamic Forms would do.
Dynamic Forms Fields placed on the Lightning page with conditions. Field visibility changes with record data. Calling it a security control.
Component visibility filter Shows or hides a whole component. Works on any component on the page. Cloning pages for each audience.
Lightning page assignment Which page a user gets by app, record type and profile. Changes the entire page, not one element. Ignoring that specific assignments override defaults.

Actions and buttons

ConceptMeaningKey differenceCommon trap
Object-specific action Acts in a record's context. Links new records to the parent. Using a global action instead.
Global action Acts from anywhere. No automatic parent relationship. Expecting it to update the current record.
Custom button or link URL, Visualforce or Classic JavaScript behavior. JavaScript buttons are unsupported in Lightning. Picking JavaScript buttons for Lightning users.
Flow action Quick action that launches a screen flow. Guided multi-step input and logic. Using a simple create action when branching is required.

Exam traps

Each trap is an answer that looks right. Learn the clue that should change your mind.

  1. Layout for conditional fields

    What candidates pick
    Create a second page layout with the extra fields.
    Why it looks right
    Page layouts are the familiar way to change fields.
    Why it's wrong
    Layouts cannot react to a field value on the same record type; Dynamic Forms visibility rules can.

    Clue to watch for Fields must appear only when another field has a certain value.

  2. Global action for related records

    What candidates pick
    Create a global action to log visits on accounts.
    Why it looks right
    It is easy to reach from anywhere in the mobile app.
    Why it's wrong
    Records created by a global action are not linked to the account automatically, so users must search for it.

    Clue to watch for The record must be related to the one being viewed.

  3. Code for visibility

    What candidates pick
    Ask a developer for a component that hides itself for some profiles.
    Why it looks right
    Code seems flexible.
    Why it's wrong
    Component visibility filters already handle profile, permission and field conditions without code.

    Clue to watch for The only need is to show or hide existing content.

  4. JavaScript button in Lightning

    What candidates pick
    Recreate a Classic JavaScript button.
    Why it looks right
    It worked in the old interface.
    Why it's wrong
    JavaScript buttons do not run in Lightning Experience; use a quick action, flow or Lightning web component.

    Clue to watch for Users are moving to Lightning Experience.

  5. Wrong page activation

    What candidates pick
    Set the page as org default for one sales team.
    Why it looks right
    Org default is the first activation option.
    Why it's wrong
    Org default affects everyone; an app, record type and profile assignment targets one team.

    Clue to watch for Only one profile or app should get the new page.

Answer framework

Use this order to pick a user interface solution with the least custom work.

  1. Identify the target: a whole page, a section of fields, a single component, an action, or the mobile header, since each has its own tool.
  2. For conditional display, try Dynamic Forms, Dynamic Actions or component visibility filters before creating new layouts or pages.
  3. For different pages per audience, use Lightning page activation by app, record type, profile and form factor rather than the org default.
  4. For user shortcuts, choose an object-specific action when the record context matters, a global action when it does not, and a flow action for guided steps.
  5. Only when standard components cannot meet the need, recommend a developer-built Lightning web component exposed to Lightning App Builder.

Practice question

Field technicians use the Salesforce mobile app. From a Work Site record, they must quickly create an Inspection that is automatically linked to that work site, with Status prefilled as Scheduled. What should an app builder configure?

Want more like this? The Platform App Builder practice test has questions for every domain.

Checklist

0 of 12

Tick each one you can do without notes. Your ticks stay in this browser.

Study strategy

Learn this section by clicking through it. In a playground, open an Account record page in Lightning App Builder, upgrade it to Dynamic Forms, and add a visibility rule that shows a section only for one Type value. Add a component with a filter on a permission, then activate the page for one app and profile and compare it with the org default. Configure Dynamic Actions so a button appears only when a checkbox is true.

Next, build actions. Create an object-specific create action with predefined values, a global log-a-call action, an update action, and a flow action for a screen flow, then test them on the mobile app or the phone preview. Edit a compact layout and watch the header change. Read the Lightning Web Components Basics module far enough to understand targets and exposure, since you only need to know when a component is needed and how admins place it. Close with timed questions that mix layouts, actions and mobile requirements.

FAQ

What percentage of the exam is User Interface?

User Interface is 17% of the Platform App Builder exam, about ten of 60 scored questions. The weight did not change in the Summer '26 update.

Which objective moved into User Interface?

Choosing global and object-specific actions and layouts for the Salesforce mobile experience now sits in this section instead of Salesforce Fundamentals.

Do I need to write Lightning web components?

No. You need to know when a custom component is required and how it becomes available in Lightning App Builder once a developer builds it.

What is the difference between Dynamic Forms and page layouts?

Page layouts define a fixed set of fields per assignment. Dynamic Forms put fields on the Lightning page and can show or hide them based on conditions.

Do Lightning page assignments override page layouts?

They work together. The Lightning page controls the overall components, and the record detail component still uses the assigned page layout unless Dynamic Forms is used.

Can visibility filters secure sensitive fields?

No. They only control display. Use field-level security to protect data, which is covered in Salesforce Fundamentals.

Other CRM & Business Applications certifications

Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.

Test your Domain 4 knowledge

Practice choosing between Dynamic Forms, visibility filters, quick actions and Lightning page assignments, then check how ready you are for the full exam.

Take the Platform App Builder practice test Check your Platform App Builder readiness

Keep going