# Free Salesforce Platform User Experience Designer Practice Questions

*Last updated September 2026 · https://www.certifyforce.com/salesforce-ux-designer-practice-exam/free-questions*

18 free Platform User Experience Designer practice questions from the CertifyForce bank of 300 reviewed questions, spread across the 6 official exam sections in proportion to their weight. Each has the correct answer, an explanation, and the official documentation it was verified against.

## Discovery (13%)

### Question 1

While presenting a Salesforce-based redesign to Cumulus Financial executives, the UX designer hears, "We need more time to decide on this proposal." Which response best addresses this concern?

- A. Phase the implementation and costs so the vision feels less overwhelming
- B. Show the cost of waiting compared with the early quick wins the project would deliver
- C. Demonstrate the larger market opportunity to justify the expense
- D. Share the full financial model spreadsheet so executives can review every assumption

**Correct answer:** B. Show the cost of waiting compared with the early quick wins the project would deliver

**Explanation:** When executives say they need time to decide, the recommended business case response is to show the cost of waiting compared with the early quick wins. Phasing the implementation and costs, along with proving impact on day one, answers the objection that the vision is overwhelming. Demonstrating the larger market opportunity answers the objection that the proposal is too expensive. Pasting a huge spreadsheet is discouraged; instead, summarize the business-value headlines, market opportunity, key levers, and benefits versus costs.

**Sources:** [Build Your Business Case and Roadmap (Innovation Solution)](https://trailhead.salesforce.com/content/learn/modules/innovation_solution/innovation_solution_build_business)

### Question 2

Before creating a detailed process map of Cloud Kicks' custom-shoe ordering process, the UX designer wants a high-level view of the suppliers, inputs, major steps, outputs, and customers so she can define the scope. Which diagram should the designer create?

- A. A value stream map
- B. A detailed process map
- C. A SIPOC map
- D. A capability model

**Correct answer:** C. A SIPOC map

**Explanation:** A SIPOC map shows the Suppliers, Inputs, Process, Outputs, and Customers of a process and is ideal for identifying its key points and defining the scope of a complex process before creating a more detailed map. A value stream map visualizes the flow of material and information to measure inputs and outputs or identify waste. A detailed process map is the drill-down flowchart with every step and decision point, which comes after scoping. A capability model lists high-level process areas across the business to show context, not the suppliers, inputs, and outputs of one process.

**Sources:** [Speak the Process Mapping Language](https://trailhead.salesforce.com/content/learn/modules/process-mapping-for-business-analysts/speak-the-process-mapping-language)

## UX Fundamentals (16%)

### Question 3

For a new custom component, a developer at Ursa Major Solar proposes a one-of-a-kind button style for the Submit Quote action so the page feels fresh. What should the UX designer recommend?

- A. Approve the unique style, because novel controls make an interface feel more engaging
- B. Reuse the design system button in the variant that fits the action's importance
- C. Replace the button with an unlabeled icon so the action takes up less space on the page
- D. Style every button on the page with the brand variant so that the new action blends in

**Correct answer:** B. Reuse the design system button in the variant that fits the action's importance

**Explanation:** Systems design favors reusing existing patterns: when an element looks like a button, users expect it to behave like the other buttons in the app. This recognizable cue is called an affordance, and it lets users know what to do without instructions. Choosing an existing button variant also respects the button hierarchy, so the button's visual weight reflects how important or common the action is. A one-off style breaks the patterns users have learned and slows them down. An unlabeled icon relies on users guessing its meaning, and giving every button the brand variant erases the hierarchy that highlights the primary action.

**Sources:** [Apply Systems Design Principles (Systems Design with SLDS)](https://trailhead.salesforce.com/content/learn/modules/systems-design-with-slds/apply-systems-design-principles), [Review User Experience Fundamentals (UX Designer Cert Prep)](https://trailhead.salesforce.com/content/learn/modules/ux-designer-certification-prep/review-user-experience-fundamentals)

### Question 4

Cloud Kicks set its brand color in Salesforce Branding for the Salesforce mobile app. The header, buttons, and search bar now use the brand color, but users report that edit and create windows opened from the action bar still have white headers. What explains this?

- A. Headers on overlays and dialogs are always white to signal that the user is performing an action
- B. Users lack Read permission on Documents, so the brand color isn't loading
- C. Users must close the app and log in again before branding changes appear
- D. The brand color was entered as a hexadecimal code instead of being chosen from the color picker

**Correct answer:** A. Headers on overlays and dialogs are always white to signal that the user is performing an action

**Explanation:** Headers on overlays, popups, and dialogs, such as edit and create windows or windows opened from the action bar, aren't affected by the brand color and are always white, giving users a visual indicator that they are performing an action rather than simply viewing information. Missing Read permission on Documents would keep users from seeing custom branding at all, yet the header and buttons already show the brand color. Users do need to close the app and log in again to see branding changes, but the branded header shows they already have. Entering a valid hexadecimal code and using the color picker are both supported ways to set the brand color.

**Sources:** [Customize Salesforce Mobile App Branding](https://help.salesforce.com/s/articleView?id=sf.salesforce_app_customize_branding.htm&language=en_US&type=5), [Review User Experience Fundamentals (UX Designer Cert Prep)](https://trailhead.salesforce.com/content/learn/modules/ux-designer-certification-prep/review-user-experience-fundamentals)

### Question 5

Ursa Major Solar's custom Installation object has a single record type. The designer created two compact layouts so that installers and sales reps, who have different profiles, see different fields in the mobile record header. What should the designer consider?

- A. One primary compact layout applies to all users; others can be assigned only per record type
- B. Each compact layout can be assigned to a different profile on the Compact Layout Assignment page
- C. Each Lightning app can use its own compact layout, so assign one to each group's app
- D. Users can choose which compact layout they see from the settings in the Salesforce mobile app

**Correct answer:** A. One primary compact layout applies to all users; others can be assigned only per record type

**Explanation:** Unlike page layouts, which can be assigned per profile, one primary compact layout applies to all users of an object. The only way to vary it is the Record Type Overrides section, which assigns specific compact layouts to different record types. Compact Layout Assignment has no profile option, compact layouts aren't assigned per Lightning app, and mobile users can't pick a compact layout themselves.

**Sources:** [Customize Compact Layouts (Salesforce Mobile App Customization)](https://trailhead.salesforce.com/content/learn/modules/salesforce1_mobile_app/salesforce1_mobile_app_compact_layouts), [Review User Experience Fundamentals (UX Designer Cert Prep)](https://trailhead.salesforce.com/content/learn/modules/ux-designer-certification-prep/review-user-experience-fundamentals)

## Human-Centered Design (12%)

### Question 6

At the end of a Cloud Kicks journey mapping workshop, the top-voted opportunity would auto-enroll shoppers in paid add-ons they must opt out of, boosting this quarter's revenue but likely eroding trust. What should the UX designer recommend?

- A. Prioritize it, because dot voting reflects the group's consensus
- B. Eliminate it, because it trades a short-term gain for the long-term customer relationship
- C. Move it to the parking lot and revisit it at the next workshop
- D. Keep it, but limit the auto-enrollment to new customers

**Correct answer:** B. Eliminate it, because it trades a short-term gain for the long-term customer relationship

**Explanation:** The Journey Mapping module tells teams to eliminate opportunities that represent short-term gains at the expense of longer-term relationships because they're ultimately bad for the business, and it asks voters to weigh the moments that matter most to the customer. Dot votes inform prioritization but do not override that guidance. The parking lot is for capturing ideas that come up during synthesis, not for deferring a harmful opportunity. Limiting the tactic to new customers still erodes trust, just with a different group.

**Sources:** [Journey Mapping: Run a Journey Mapping Workshop](https://trailhead.salesforce.com/content/learn/modules/journey-mapping/run-a-journey-mapping-workshop)

### Question 7

Bloomington Caregivers added captions to training videos for deaf and hard-of-hearing caregivers. Soon, caregivers in noisy environments and those learning a new language also rely on the captions. Which inclusive design principle does this illustrate?

- A. Recognize exclusion
- B. Universal design
- C. Design for the average user
- D. Solve for one, extend to many

**Correct answer:** D. Solve for one, extend to many

**Explanation:** Solve for one, extend to many describes starting with a specific need and finding that the solution benefits many more people; the module's example is closed captioning, created for the deaf and hard-of-hearing community and later used by people who can't turn up the sound or are learning a new language. Recognize exclusion is the principle of noticing where our own biases shut people out, which comes before a solution exists. Universal design aims for one solution for everyone from the outset rather than solving for a specific need first. Designing for the average user is an exclusion habit, not a principle.

**Sources:** [Inclusive Design: Explore Inclusive Design](https://trailhead.salesforce.com/content/learn/modules/inclusive-design/explore-inclusive-design), [Inclusive Design: Shift to Product Inclusion](https://trailhead.salesforce.com/content/learn/modules/inclusive-design/shift-to-product-inclusion)

## Declarative Design (27%)

### Question 8

Ursa Major Solar's designer changes the fields and their order on the Contact compact layout. Which two places in Lightning Experience reflect the change? Choose 2 answers.

- A. The highlights panel at the top of a contact record
- B. The columns of the Contacts related list on account records
- C. The columns shown in contact list views
- D. The expanded lookup card that appears when hovering over a contact link
- E. The columns shown in global search results for contacts

**Correct answers:** A. The highlights panel at the top of a contact record; D. The expanded lookup card that appears when hovering over a contact link

**Explanation:** Compact layouts control which fields appear in a record's highlights panel and in the expanded lookup card shown when users hover over a link, and they also drive how records display in the Salesforce mobile app. Related list columns are configured in the related list properties of the parent object's page layout, not in the compact layout. List view columns are chosen in each list view's fields-to-display settings. Global search result columns come from the object's search layouts.

**Sources:** [Customize Record Highlights with Compact Layouts (Trailhead)](https://trailhead.salesforce.com/content/learn/modules/lex_customization/lex_customization_compact_layouts), [Lightning Experience Customization (Trailhead module)](https://trailhead.salesforce.com/en/content/learn/modules/lex_customization)

### Question 9

Cloud Kicks has a Visualforce shipping-cost calculator. Reps want to open it in a docked panel from any page in the Sales app while keeping the current record in view. What should the UX designer recommend?

- A. Add the Visualforce page as a utility item on the app's Utility Items tab in App Manager
- B. Rebuild the calculator as a Lightning web component configured for the utility bar
- C. Add the Visualforce page to the app's navigation bar as a Visualforce tab
- D. Add the Visualforce page to the utility bar from the Lightning App Builder instead of App Manager

**Correct answer:** B. Rebuild the calculator as a Lightning web component configured for the utility bar

**Explanation:** Utilities are built from Lightning components, and the utility bar doesn't support Visualforce pages or components, so the calculator must be rebuilt as a Lightning component configured for the utility bar. For the same reason, the Visualforce page can't be added on the Utility Items tab, and switching to the Lightning App Builder doesn't lift the restriction. A Visualforce tab in the navigation bar is supported, but opening it navigates reps away from the record instead of opening a docked panel.

**Sources:** [Add a Utility Bar to Lightning Apps](https://help.salesforce.com/s/articleView?id=platform.apps_lightning_utilities.htm&language=en_US&type=5)

### Question 10

Universal Containers wants its logo and corporate colors to appear across Lightning Experience for all internal users, including the global header and navigation bar. What should the UX designer recommend?

- A. Set a primary color and image on each Lightning app in App Manager
- B. Upload the logo in the My Domain login page settings
- C. Configure Salesforce Branding for the Salesforce mobile app
- D. Create and activate a custom theme in Themes and Branding

**Correct answer:** D. Create and activate a custom theme in Themes and Branding

**Explanation:** A custom theme in Themes and Branding sets the org's brand image and brand-based colors, which show up in places such as page backgrounds, the global header, the navigation bar, tabs, and buttons for everyone in the org. App-level branding applies only within each app and would have to be repeated for every app. My Domain branding customizes the login page, not Lightning Experience after login. Salesforce mobile app branding affects the mobile app only, and Lightning Experience themes don't apply to native mobile apps.

**Sources:** [Explore Other Enhancements (Trailhead)](https://trailhead.salesforce.com/content/learn/modules/lex_migration_whatsnew/lex_migration_whatsnew_more), [Create a Custom Theme](https://help.salesforce.com/s/articleView?id=xcloud.brand_create_custom_theme.htm&language=en_US&type=5)

### Question 11

Cloud Kicks relates a custom Invoice object to Account with a lookup relationship. Sales managers want each Account page to show the total amount of its invoices. Which two statements should the UX designer consider? Choose 2 answers.

- A. A formula field on Account can sum the amounts of related invoices
- B. A roll-up summary field on Account requires Invoice to be the detail in a master-detail relationship
- C. Converting the relationship to master-detail keeps each invoice's owner and sharing rules
- D. The roll-up summary field should be created on the Invoice object
- E. The lookup can be converted to master-detail only if every invoice has an account value

**Correct answers:** B. A roll-up summary field on Account requires Invoice to be the detail in a master-detail relationship; E. The lookup can be converted to master-detail only if every invoice has an account value

**Explanation:** Roll-up summary fields are created on the master object and calculate values from detail records related through a master-detail relationship, so the Invoice lookup must become master-detail first. A lookup can be converted to master-detail only when the lookup field contains a value on every record. A formula field can reference parent fields but can't aggregate multiple child records. After conversion the detail no longer has its own owner and its sharing becomes Controlled by Parent, so invoice-level owners and sharing rules don't survive. The roll-up field belongs on Account, the master, not on Invoice.

**Sources:** [Roll-Up Summary Field](https://help.salesforce.com/s/articleView?id=platform.fields_about_roll_up_summary_fields.htm&type=5), [Considerations for Object Relationships](https://help.salesforce.com/s/articleView?id=platform.relationships_considerations.htm&type=5)

### Question 12

Universal Containers field technicians update three fields on a custom Service Visit record from their phones after each visit, but editing the full record means scrolling past dozens of fields. What should the UX designer recommend?

- A. An Update a Record quick action whose action layout contains only the three fields
- B. A global create action added to the global publisher layout
- C. A new compact layout that contains the three fields
- D. A validation rule that requires the three fields before saving

**Correct answer:** A. An Update a Record quick action whose action layout contains only the three fields

**Explanation:** Update a Record actions let users change the current record, and the action layout can be trimmed to only the essential fields, so technicians tap one action in the mobile action bar and edit just what they need. Global create actions create new records with no relationship to the current record, so they can't update the visit. A compact layout controls which fields are displayed in the record's highlights, not an editable form. A validation rule enforces entry but doesn't reduce the scrolling; it adds friction instead.

**Sources:** [Quick Actions](https://help.salesforce.com/s/articleView?id=platform.actions_overview.htm&type=5), [Empower Your Users with Quick Actions (Trailhead)](https://trailhead.salesforce.com/content/learn/modules/lex_customization/lex_customization_actions)

## Testing (11%)

### Question 13

Cloud Kicks is testing a role-playing prototype of an in-store community event to learn whether customers value connecting with other runners. Which two feedback approaches should the UX designer plan? Choose 2 answers.

- A. Ask what customers think about connecting with other runners at the event
- B. Time how long each participant takes to complete the event sign-up task
- C. Watch for behavior cues, such as engaged versus distracted participants
- D. Ask participants to rate how easy the prototype's screens are to use
- E. Wait to collect any feedback until a high-fidelity version is available

**Correct answers:** A. Ask what customers think about connecting with other runners at the event; C. Watch for behavior cues, such as engaged versus distracted participants

**Explanation:** Questions for participants should reflect the level of refinement the prototype is in: when prototyping a question about community, the team shouldn't ask for feedback on ease of use or task completion, but about the concept itself. Behavior cues that can be observed during the interaction, such as engaged versus distracted behavior or workarounds, also signal whether the team is heading in the right direction. Timing a sign-up task and rating screen usability are task-completion and ease-of-use measures that don't fit a role-play of an abstract concept. Waiting for high fidelity defeats the purpose of fast, cheap prototypes that answer questions early.

**Sources:** [Get to Know Different Kinds of Prototyping (Strategy Design Prototyping)](https://trailhead.salesforce.com/content/learn/modules/design-strategy-prototyping/get-to-know-different-kinds-of-prototyping), [Refresh Your Design Testing Skills (UX Designer Cert Prep)](https://trailhead.salesforce.com/content/learn/modules/ux-designer-certification-prep/refresh-your-design-testing-skills)

### Question 14

Universal Containers tested a new custom component using only VoiceOver on macOS and found no issues. Which two actions should the UX designer recommend to strengthen accessibility testing? Choose 2 answers.

- A. Verify that the Tab key reaches every piece of text content in the component.
- B. Treat the VoiceOver results as also covering keyboard testing.
- C. Test with additional screen readers, such as NVDA or JAWS on Windows.
- D. Rely on the component's Lighthouse accessibility score instead of assistive technology.
- E. Run keyboard testing, ideally before screen reader testing.

**Correct answers:** C. Test with additional screen readers, such as NVDA or JAWS on Windows.; E. Run keyboard testing, ideally before screen reader testing.

**Explanation:** Salesforce recommends testing with multiple screen readers, because testing only with VoiceOver can miss issues that JAWS or NVDA would catch, and it advises keyboard testing before screen reader testing to highlight issues a screen reader might not catch. Screen reader users navigate non-interactive content with their own shortcuts, so the Tab key should not reach every piece of text. Keyboard testing and screen reader testing are not the same, so one does not cover the other. An automated score cannot replace manual testing with assistive technology.

**Sources:** [Testing for Web Accessibility](https://trailhead.salesforce.com/content/learn/modules/testing-for-web-accessibility), [Test for Accessibility](https://trailhead.salesforce.com/content/learn/modules/testing-for-web-accessibility/test-for-accessibility-1)

## Salesforce Lightning Design System (SLDS) (21%)

### Question 15

A custom component that Northern Trail Outfitters built from an SLDS blueprint looks different from the blueprint in the SLDS documentation. How should the UX designer use the browser inspector to find the cause?

- A. Remove every .slds- class from the component and restyle it from scratch with custom CSS
- B. Add !important to the blueprint's classes in the component so they win over any other rule
- C. Find the .slds- classes, toggle off unprefixed overrides one by one, and verify token values
- D. Activate the Salesforce Cosmos theme so the component is restyled with the latest SLDS version

**Correct answer:** C. Find the .slds- classes, toggle off unprefixed overrides one by one, and verify token values

**Explanation:** Trailhead's troubleshooting process is to look for SLDS classes (all start with the slds- prefix), check for CSS overrides (classes without the SLDS prefix), turn overrides off one by one to see whether the UI changes, and verify that the tokens in use match the values on the SLDS token page and blueprint. Removing every SLDS class throws away the blueprint and creates a harder-to-maintain one-off. Adding !important is a last-resort practice that hides the real conflict instead of finding it. Cosmos is an opt-in theme for SLDS 2 and doesn't diagnose a custom CSS override in an SLDS 1 component.

**Sources:** [Explore Salesforce Lightning Design System (UX Designer Cert Prep)](https://trailhead.salesforce.com/content/learn/modules/ux-designer-certification-prep/explore-salesforce-lightning-design-system), [Understand SLDS Best Practices (Lightning Design System Development for Designers)](https://trailhead.salesforce.com/content/learn/modules/lightning-design-system-development-for-designers/understand-slds-best-practices)

### Question 16

In a design review for a Northern Trail Outfitters app, the UX designer notes: "Replace vague labels so users can act with confidence" and "Cut unnecessary steps from the approval workflow." Which two SLDS design principles do these notes apply? Choose 2 answers.

- A. Clarity
- B. Beauty
- C. Efficiency
- D. Consistency
- E. Scalability

**Correct answers:** A. Clarity; C. Efficiency

**Explanation:** Removing ambiguity so people can see, understand, and act with confidence is the Clarity principle, and streamlining and optimizing workflows is the Efficiency principle. Beauty is about respecting people's time and attention through elegant craftsmanship, which neither note addresses. Consistency is also an SLDS principle, but it's about applying the same solution to the same problem. Scalability describes a good design system and is a focus of systems design, but it isn't one of the four SLDS design principles.

**Sources:** [SLDS 1 Design Guidelines: Design Principles](https://v1.lightningdesignsystem.com/guidelines/overview/), [Learn About Design Systems (Lightning Design System Basics)](https://trailhead.salesforce.com/content/learn/modules/lightning-design-system-basics/learn-about-design-systems), [Lightning Design System Basics](https://trailhead.salesforce.com/content/learn/modules/lightning-design-system-basics)

### Question 17

Get Cloudy Consulting's client has dozens of existing Visualforce pages built with standard components such as `apex:pageBlock` and `apex:inputField`. The client wants them to look closer to Lightning Experience with minimal rework. What should the UX designer recommend?

- A. Rebuild every page from scratch with SLDS blueprint markup
- B. Set `lightningStylesheets="true"` on each page's `apex:page` tag
- C. Write custom CSS that targets the HTML rendered by the standard Visualforce components
- D. Leave the pages unchanged, because Visualforce pages can't take on Lightning Experience styling

**Correct answer:** B. Set `lightningStylesheets="true"` on each page's `apex:page` tag

**Explanation:** Setting lightningStylesheets="true" in the apex:page tag styles most commonly used standard Visualforce components to match Lightning Experience when the page is viewed in Lightning Experience or the Salesforce mobile app, while Salesforce Classic keeps Classic styling. Rebuilding pages with all-new SLDS markup gives the closest match but is far more work than the client wants. Custom CSS that targets the HTML rendered by standard components depends on internal implementation details that can change without notice, so Salesforce discourages it. Visualforce pages can adopt Lightning Experience styling through this attribute or the SLDS stylesheets.

**Sources:** [Style Existing Visualforce Pages with Lightning Experience Stylesheets (Visualforce Developer Guide)](https://developer.salesforce.com/docs/atlas.en-us.pages.meta/pages/vf_dev_best_practices_slds_lightningstylesheets.htm), [Understand Important Visual Design Considerations (Visualforce & Lightning Experience)](https://trailhead.salesforce.com/content/learn/modules/lex_dev_visualforce/lex_dev_visualforce_design), [Explore Salesforce Lightning Design System (UX Designer Cert Prep)](https://trailhead.salesforce.com/content/learn/modules/ux-designer-certification-prep/explore-salesforce-lightning-design-system)

### Question 18

A Universal Containers custom component has a View All Orders control that opens the orders page and a Merge control that combines duplicate records on the same page. Which three recommendations follow SLDS button guidance? Choose 3 answers.

- A. Use a link for View All Orders, because it navigates to another place
- B. Use a button for Merge, because it performs an action on the page
- C. If an `<a>` element must perform an action, add `role="button"` and handle the Space key
- D. Use buttons for both controls, because screen readers announce links and buttons alike
- E. Rely on the destructive button color alone to warn users that Merge is risky

**Correct answers:** A. Use a link for View All Orders, because it navigates to another place; B. Use a button for Merge, because it performs an action on the page; C. If an `<a>` element must perform an action, add `role="button"` and handle the Space key

**Explanation:** SLDS says to use a link when navigating to another place, such as a 'view all' page, and a button when performing an action, such as submit, merge, or upload. The distinction matters to screen reader users, who need to know whether they'll navigate somewhere or something will happen on the page, so using buttons for both controls hides the navigation. If an `<a>` element absolutely must be used for an action, SLDS requires adding `role="button"` and a JavaScript handler for the Space key, because buttons respond to both Enter and Space but links don't. Color alone doesn't convey a button's meaning, so the button text must communicate the same warning the destructive color implies.

**Sources:** [SLDS 1 Component Blueprints: Buttons](https://v1.lightningdesignsystem.com/components/buttons/), [Explore Salesforce Lightning Design System (UX Designer Cert Prep)](https://trailhead.salesforce.com/content/learn/modules/ux-designer-certification-prep/explore-salesforce-lightning-design-system)

## Related pages

- [Salesforce Platform User Experience Designer practice exam](https://www.certifyforce.com/salesforce-ux-designer-practice-exam)
- [Practice exam packs](https://www.certifyforce.com/practice-exams)
- [Official Platform User Experience Designer exam guide](https://help.salesforce.com/s/articleView?id=005298974&language=en_US&type=1)