Salesforce Updated Plat-UX-101 Exam Questions and Answers by herbie

The correct answer is B. 44 pixels wide x 44 pixels tall, which is the minimum target size identified by the study guide for interactive mobile elements. Touch interfaces require larger interaction targets than pointer-based desktop interfaces because users interact with them using fingers rather than a precise mouse cursor. A sufficiently large target makes buttons, links, icons, and other controls easier to activate accurately while reducing accidental selection of neighboring elements. The 44 × 44 pixel minimum therefore supports both usability and accessibility. The requirement is particularly important for users with limited dexterity, motor impairments, tremors, or users interacting with a mobile device while moving. Small targets can create repeated selection errors even for users without disabilities. Option A, 24 × 24 pixels, can be visually appropriate for some icons, but an icon's visual dimensions do not necessarily represent an adequate interactive touch area. Option C, 64 × 64 pixels, would certainly provide a large target but exceeds the minimum being tested. A UX Designer should distinguish between the visual size of an icon and its effective clickable or tappable area. A small-looking icon can still be enclosed within a larger interactive target.

Study Guide reference/topics: Mobile UX, touch targets, accessibility, interactive controls, UX Fundamentals.

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

The uploaded study guide identifies C. Configure the Experience Builder Theme panel as the correct answer.

The scenario specifically asks how a branding and marketing team should customize an external customer support site's theme to align with the company's style guide. The study-guide answer favors the standard declarative capability available in Experience Builder.

Option A introduces an external or company stylesheet, while option B introduces custom CSS. Both approaches add custom styling logic that is unnecessary when the branding requirement can be handled through the platform's built-in theme configuration.

The Theme panel is therefore the appropriate first step because it allows designers to modify the supported presentation properties of the Experience Cloud site without immediately resorting to custom code.

This also aligns with a recurring pattern throughout the study guide: when a Salesforce declarative capability satisfies a UX requirement, use that capability before introducing custom development. This generally produces a more consistent and maintainable experience.

For the branding team, the practical implication is that the company's style-guide requirements should first be translated into the configuration options available through Experience Builder's theme controls.

Study Guide reference/topics: Experience Builder, themes, branding, style-guide implementation, Declarative Design.

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

The uploaded study guide identifies B. Grid System as the correct SLDS resource for responsive design.

A responsive interface needs its layout to adapt as the available screen width changes. The Grid System is the resource selected by the guide because it provides the structural mechanism for arranging interface content into flexible rows and columns.

This directly addresses page-level responsiveness: content can be organized so that it uses available horizontal space appropriately and can be repositioned or wrapped as the viewport changes.

Option A, Design Tokens, addresses reusable design values. Tokens can support consistency for properties such as spacing, color, or other design attributes, but the question specifically asks what the designer should use for responsive layout design.

Option C, Component Blueprints, provides structural guidance for individual SLDS components rather than serving as the primary layout system for responsive page organization.

The key study-guide distinction is therefore between component styling/resources and layout architecture. When the issue is adapting page composition to different screen sizes, the Grid System provides the relevant SLDS mechanism.

This makes the grid an essential foundation for designing Salesforce interfaces that remain organized and usable across varying viewport dimensions.

Study Guide reference/topics: SLDS Grid System, responsive design, rows and columns, adaptive layouts, Salesforce Lightning Design System.

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

The correct answer is A. Apply brand fonts and colors, as stated in the study guide. Experience Builder includes declarative branding capabilities specifically intended to implement company identity without custom front-end development. Salesforce documentation explains that prebuilt Experience Builder themes can be customized using colors, fonts, and images, while branding sets allow these attributes to be managed for different audiences or requirements. This exactly matches Cloud Kicks' requirement to implement its existing brand style guide while avoiding a custom solution. The UX Designer can configure supported theme and branding properties through Experience Builder rather than introducing custom CSS.

Option B may fundamentally change the site's structure, component availability, or overall design architecture. Choosing a different template solely to apply branding is unnecessary when the existing theme supports declarative branding controls. Option C violates the explicit requirement to avoid custom solutions. Global CSS introduces additional maintenance and can create problems when Salesforce changes underlying platform markup or component styling.

The preferred UX architecture is therefore to exhaust supported configuration capabilities before introducing code. Using brand fonts and colors maintains consistency with the company's style guide while preserving compatibility with Salesforce's theme framework and reducing technical debt.

Study Guide reference/topics: Salesforce Themes and Branding, Experience Builder, branding sets, themes, fonts, colors, Declarative Design.

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