Plat-UX-101 Exam Dumps - Salesforce Certified Platform User Experience Designer

The uploaded study guide gives B. Tangible as the correct answer. The question wording and capitalization are preserved from the source.

Within the accessibility-oriented terminology used elsewhere in the guide, Robust and Perceivable are recognized accessibility principles. “Tangible” is not presented as part of that principle set, so it is the item that does not belong.

Perceivable concerns ensuring that information and interface content can be presented in ways users can perceive. Earlier material in the same guide links perceivability to providing content in formats that can be transformed or accessed in different ways.

Robust also appears in the guide's WCAG-focused material, where it is listed alongside Understandable and Operable.

Option B, Tangible, therefore differs from the terminology used by the guide for digital-accessibility design requirements.

This item is written very briefly in the source, so its intended distinction is best understood by comparing the terminology against the accessibility principles established elsewhere in the same question bank rather than expanding it into a different framework.

For this supplied study guide, the keyed answer is unambiguously B.

Study Guide reference/topics: Accessibility principles, Robust, Perceivable, UX Fundamentals.

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

The study guide identifies C. Components Library on developer.salesforce.com as the correct answer. The key requirement is to locate a centralized resource containing Lightning component code, documentation, and specifications so the implementation team can work efficiently. The Components Library is designed for that purpose: it gives designers and developers access to component references, supported attributes, implementation details, examples, and behavioral expectations. Option A, Salesforce Extensions for VS Code, is a development-tooling environment. It helps developers work with Salesforce metadata and code, but it is not the primary reference library for exploring Lightning component specifications. Option B, Design Tokens, provides reusable design values such as spacing, colors, and other design attributes. Tokens help maintain visual consistency, but they do not function as a comprehensive component reference. From a UX implementation perspective, using documented Lightning components reduces unnecessary custom development and helps ensure that components behave consistently with Salesforce interaction patterns. It also improves implementation speed because teams can begin with an established component rather than inventing a new one.

Study Guide reference/topics: Lightning Components, LWC implementation, component documentation, SLDS, reusable UI architecture.

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