UX-DESIGNER Practice Questions

A Customer Journey Map is a visualization of the process that a person goes through to accomplish a goal. It's used for understanding and addressing customer needs and pain points. It is the perfect artifact for this scenario as it maps out the user's experience across multiple touchpoints and channels over time, highlighting their actions, thoughts, and feelings at each stage.

This statement is false. A/B testing is a quantitative research method. It is used to compare two versions of a design (A and B) to see which one performs better based on a specific metric (e.g., click-through rate, conversion rate). It tells you 'what' users do and which design is more effective, but it does not explain the 'why' behind their choices. Qualitative methods like user interviews are needed to understand the 'why'.

The .slds-button_neutral variant is used for secondary actions. It provides a less prominent visual treatment than the primary .slds-button_brand variant, which is reserved for the most important action on the page. This helps create a clear visual hierarchy and guides the user toward the primary task.

An Empty State (or zero-data state) is what a user sees when there is no data to display in a list, table, or chart. Best practices for empty states involve using them as an opportunity to educate, guide, and prompt action rather than showing a blank screen. This includes a clear message, relevant imagery, and a call-to-action.

The 'Header and Right Sidebar' template provides the exact structure described and visualized in the diagram: a main header region, a large primary column on the left (typically 2/3 width), and a narrower sidebar region on the right (typically 1/3 width). This is the standard template for creating pages with a main content area and a supplementary sidebar.

This is the optimal solution. Dynamic Forms directly address the need for a modular, context-aware interface by allowing fields and sections to be placed as individual components. Component Visibility rules can then be applied to these sections based on user profiles to meet the security/visibility requirement. Finally, the Path component is the standard declarative feature for guiding users through a process like onboarding.

Design tokens (e.g., var(--slds-g-color-brand-base-1)) are variables in the SLDS that store visual design attributes. Using them ensures the component automatically inherits branding from the Salesforce theme.

Styling hooks (CSS custom properties) expose specific styling points of a component, allowing administrators or developers to override them easily for branding purposes without altering the component's core CSS.

Using the standard SLDS class for a button ensures it inherits all the base styling, accessibility attributes, and interaction states consistent with the rest of the Salesforce UI.

The Tabs component is the ideal declarative solution for this problem. It breaks a large amount of information into logical, manageable chunks, reducing the initial cognitive load. By placing content in non-active tabs, it can also improve the perceived page load time, as the content within those tabs may not render until they are clicked. This directly addresses both user complaints.

This statement is false. Inclusive design does not mean creating one identical experience for all. It means creating comparable or equivalent experiences that allow users with different abilities and in different contexts to achieve the same goal. The focus is on providing an equitable outcome, not an identical interface.

The SLDS Grid system is specifically designed for creating flexible, responsive layouts. By using classes like slds-grid, slds-wrap, and responsive sizing utilities like slds-size_1-of-1, slds-medium-size_1-of-2, and slds-large-size_1-of-3 on the slds-col elements, a designer can declaratively define the exact wrapping and stacking behavior across different breakpoints (mobile, tablet, desktop).