Salesforce Platform UX Designer Practice Exam

Correct: A — An expert review. An expert review (heuristic evaluation) is an independent audit in which a designer applies established usability principles and heuristics to find a site's strengths and weaknesses — no end users required, which matches the constraint.

Why not the others: an A/B test (B) needs live users and traffic to compare variants, not an independent audit; a persona workshop (C) is a generative discovery activity for understanding users, not an audit of an existing site's usability.

Correct: A — Personas. Personas are research-based fictional characters that represent user types, giving the team a shared reference for user goals and behaviors. Salesforce also defines specific platform UX personas the exam expects you to recognize.

Why not the others: wireframes (B) are low-fidelity layout sketches, not representations of users; style tiles (C) are visual-design artifacts for brand and tone, not user models.

Correct: A — 4.5:1. WCAG requires at least a 4.5:1 contrast ratio for normal-size text (the minimum drops to 3:1 for large text, roughly 24px or 19px bold). Accessibility contrast is a frequently tested UX Fundamentals detail.

Why not the others: 1.5:1 (B) and 2:1 (C) fall well below the AA threshold and would fail contrast requirements, making text hard to read for low-vision users.

Correct: A — Let users pause, stop, or disable the animation. The most important accessibility safeguard for motion is giving users control to turn it off — large or mismatched movement can trigger dizziness, nausea, or seizures. The SLDS carousel's pause button is the canonical example.

Why not the others: larger and faster motion (B) increases the risk of discomfort; multiple simultaneous autoplaying animations (C) are exactly the disorienting pattern accessibility guidance warns against.

Correct: A — Inclusive design. Inclusive design considers the full range of human diversity — ability, language, culture, context — from the outset so the experience works equitably for as many people as possible. It's a core human-centered design principle on the exam.

Why not the others: retrofitting after launch (B) treats inclusion as an afterthought and usually leaves gaps; designing only for the majority persona (C) is the opposite of inclusive practice and excludes real users.

Correct: A — Path. Path is a declarative feature that guides users through the stages of a process (like opportunity stages) on the record page, surfacing key fields and guidance for success at each step — all configured without code.

Why not the others: an Apex trigger (B) is code, not a declarative UX feature; a validation rule (C) enforces data entry constraints but doesn't guide a user visually through stages.

Correct: A — Branding sets with audience targeting. Branding sets are collections of branding attributes (logos, fonts, colors, images) that can be applied per audience using audience targeting, giving each group a distinct, consistent look without separate sites or custom themes.

Why not the others: hard-coded CSS per audience (B) abandons the declarative, maintainable approach; a separate site per audience (C) is heavy, duplicative, and unnecessary when branding sets exist.

Correct: A — Tree testing. Tree testing evaluates findability in an information architecture by asking users to locate items within a text-only hierarchy, isolating navigation and labels from visual design. It's a core testing technique on the exam.

Why not the others: contrast checking (B) is an accessibility/visual check, not a navigation test; sprint planning (C) is an agile ceremony, not a usability method.

Correct: A — Framework-agnostic sets of semantic HTML, CSS, and accessibility attributes. Blueprints are the key to SLDS being implementation-agnostic: they provide the markup, styling, and accessibility guidance to build a component in whatever web technology you choose.

Why not the others: Apex classes (B) are server-side code, unrelated to SLDS blueprints; static image mockups (C) contain no code and aren't what blueprints are — blueprints are buildable specifications.

Correct: A — Consistency at scale through reusable, documented, accessible components. A design system provides a shared library of components, patterns, and guidelines so designers and developers build consistent, accessible experiences quickly across teams and products.

Why not the others: a design system doesn't remove the need for user testing (B) — testing validates that the assembled experience works; and it promotes consistency, not forced uniqueness-per-app (C), which would defeat its purpose.