Salesforce Plat-UX-101 Dumps

The study guide identifies A. Formula Field, Static Resource, and Object Page Layout as the correct combination. The scenario requires the record detail page to show a custom visual indicator that changes according to the current membership level. The tools selected in the guide support that requirement declaratively.

A Static Resource can hold the image assets required for the membership indicators. A Formula Field can determine which visual representation should be shown according to the data stored on the record. The resulting field can then be positioned on the relevant Object Page Layout so that users see the membership indicator as part of the record experience.

Option B refers to an Image Field and Dynamic Forms, but that combination is not the platform approach selected by the study guide for deriving the displayed image from membership-level logic.

Option C introduces Lightning components and SLDS icons. That could imply a more customized implementation, while the guide favors the simpler declarative combination of formula, resource, and layout configuration.

The UX value is immediate recognition: a visual membership indicator can communicate status faster than requiring users to interpret raw field values.

Study Guide reference/topics: Formula Fields, Static Resources, page layouts, visual status indicators, Declarative Design.

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

The correct answer is C. A/B Testing, as explicitly identified in the study guide.

The UX Designer already has two interface variants and a clearly measurable outcome: the number of completed contact forms. That is precisely the type of comparison the study guide associates with A/B Testing.

In an A/B test, different groups of users encounter different versions of an interface. The team then compares a predefined behavioral metric between those variants. Here, the metric is straightforward: which landing-page design produces the greater number or rate of form completions.

Option A, Eyetracking, would provide information about where users direct their visual attention. It could reveal whether they notice the form or other content, but it does not directly answer which version produces more completed forms at scale.

Option B, Field Studies, investigate users in their real environment and are useful for contextual understanding. They are not the most direct method for statistically comparing two high-traffic landing-page variants.

The presence of several thousand visitors strengthens the suitability of A/B Testing because the designer has sufficient traffic to compare observable behavioral outcomes between alternatives.

Study Guide reference/topics: A/B Testing, comparative testing, conversion measurement, behavioral metrics, Testing.

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

The uploaded UX Designer study guide identifies B. Optimize for color contrast-ratio and screen-reading technology as the correct answer.

The research finding is specifically that the solution does not adequately account for users with visual impairments. The study guide therefore directs the UX Designer toward accessibility improvements that affect how information can be perceived visually and through assistive technology.

Improving color contrast supports users who may have difficulty distinguishing foreground content from its background. Supporting screen-reading technology allows users who cannot rely on visual presentation to access the interface through an alternative presentation of its structure and content.

Option A proposes a separate version of the portal. The study guide does not recommend segregating visually impaired users into a different experience; instead, accessibility should be incorporated into the main design.

Option C concerns HIPAA requirements and does not address the visual-accessibility problem described.

The key UX principle is that accessibility should be integrated into the product experience. The correct response is therefore to improve the existing design so that it works with relevant accessibility needs and assistive technologies.

Study Guide reference/topics: Accessibility, color contrast, screen readers, visually impaired users, UX Fundamentals.

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

The correct answer is C. Component Blueprints, as identified by the uploaded study guide.

The question emphasizes consistency with the look and feel of Lightning Experience across components that will appear repeatedly on different pages. The study guide therefore points to SLDS Component Blueprints as the relevant resource.

A Component Blueprint provides the documented structure and styling pattern for implementing an interface component according to SLDS conventions. Using a standard blueprint helps prevent different developers or teams from creating visually inconsistent versions of the same interaction.

Option A, Experience Lightning Components, is not the SLDS resource identified by the guide for this purpose.

Option B, Lightning Component Builder, is likewise not the design-system resource referenced in the answer key.

The important distinction is between a design-system specification and an application-building tool. A blueprint establishes how a component should be structured and presented so that custom implementations remain aligned with Salesforce's established design language.

When components are reused on many pages, that consistency becomes especially important because variations in spacing, states, structure, or interaction patterns can create an uneven user experience.

Study Guide reference/topics: Component Blueprints, reusable UI, Lightning Experience consistency, SLDS.

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

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 correct answer is B. Recognize exclusion. Learn from diversity. Solve for one, extend to many. The uploaded study guide explicitly identifies these as the inclusive-design action-oriented principles. Recognize exclusion means designers actively identify where products, processes, assumptions, or environmental conditions prevent certain people from participating effectively. Exclusion should be treated as a design problem rather than simply as an edge case.

Learn from diversity means incorporating perspectives and lived experiences from people with different capabilities, backgrounds, circumstances, and interaction needs. A team composed of people with similar experiences can easily overlook barriers that are obvious to users outside that group.

Solve for one, extend to many recognizes that addressing a specific exclusion can produce benefits for a much broader population. For example, interface improvements created for users with permanent motor limitations may also benefit someone temporarily injured or a user operating a device with one hand.

Option A incorrectly frames inclusive design around imperfection and “one size fits one.” Option C incorrectly substitutes learning from experts for learning from diverse users.

The central principle is that inclusive design deliberately examines exclusion and uses human diversity as a source of innovation rather than treating accessibility requirements as isolated exceptions.

Study Guide reference/topics: Inclusive design, exclusion, diversity, human-centered design, Human-Centered Design.

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

The study guide identifies B. Tabs within the app's navigation bar as the customizable app-specific user-interface element.

A custom Lightning application is intended to provide a navigation environment tailored to the users and tasks associated with that app. The navigation bar is therefore an important configuration surface because it determines which tabs and destinations users can access directly while working within the application.

For a new team of service agents, selecting the appropriate navigation tabs can expose the objects and resources they need frequently while avoiding irrelevant destinations. This supports task efficiency and reduces unnecessary navigation.

Option A refers specifically to utility items for a mobile view. That is not the app-specific customization identified by the study guide in this scenario.

Option C refers to changing icons for custom objects. The question asks which part of the user interface specific to the app can be customized, and the answer key points instead to the navigation structure.

The UX principle is that an application should reflect the workflow of its intended audience. Configuring its navigation tabs allows the designer or administrator to prioritize the Salesforce destinations most relevant to those service agents.

Study Guide reference/topics: Lightning apps, navigation bar, tabs, service-agent UX, Declarative Design.

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

The uploaded study guide identifies B. Personalize the navigation bar as the correct solution.

The problem affects only a small subset of sales users. They frequently use a particular object, but that object is not currently included in the Lightning application's standard navigation. Creating an entirely separate application would therefore be disproportionate to the size of the audience.

Personalizing the navigation bar directly addresses the usability problem by allowing the relevant users to place the object within their own accessible navigation structure. This reduces unnecessary searching or indirect navigation while avoiding organization-wide configuration solely for a small group.

Option A, creating a Dashboard action, does not solve the fundamental problem that these users need routine navigation to an object.

Option C, placing the object's related list on the Home page, would attempt to surface data in a different context rather than providing straightforward navigation to the object itself.

The guide's solution reflects a broader UX principle of appropriate personalization. When a need is specific to a limited group and does not justify a separate application, individual navigation customization can improve efficiency without increasing administrative complexity for everyone else.

Study Guide reference/topics: Lightning navigation, personalization, object access, end-user efficiency, Declarative Design.

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

The uploaded study guide identifies C. Heroku, Visualforce, Android as the correct set of platforms on which SLDS resources can be used.

The question is testing the portability of the Salesforce Lightning Design System beyond a single Salesforce interface. SLDS provides design resources that can help designers create visual and interaction consistency across different environments associated with Salesforce solutions.

The study guide specifically selects Heroku, Visualforce, and Android. This illustrates the broader purpose of a design system: reusable design principles, patterns, component guidance, and styling resources can support consistency across multiple implementation contexts.

Option A includes Azure, Visual Studio, and .NET, which are not the combination identified by the guide.

Option B includes AWS, Aura, and iOS. Although Aura is part of the Salesforce ecosystem, the complete three-item set is not the answer specified by the study guide.

The important UX lesson is that a design system is not merely a collection of styles for one page type. It provides a common design language that can be applied across experiences so that users encounter recognizable patterns, visual hierarchy, interaction behavior, and brand treatment.

Study Guide reference/topics: SLDS resources, cross-platform consistency, Heroku, Visualforce, Android, Salesforce Lightning Design System.

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

The correct answer is A. Cross-Functional Map, as stated in the uploaded study guide.

The requirement is not simply to document the sequence of a process. Cloud Kicks specifically wants to explain the relationship between process steps and the business teams responsible for or involved in those steps.

A Cross-Functional Map is suited to that requirement because it organizes process activities according to the different roles, groups, or organizational functions involved. This allows stakeholders to see both the sequence of work and how responsibility moves across functional boundaries.

Option B, a Detailed Process Map, can document individual steps in significant depth, but the question emphasizes the relationship between those steps and different teams.

Option C, a Journey Map, represents an experience from the user's perspective, typically emphasizing stages, touchpoints, pain points, and opportunities. That is valuable for understanding the user's experience but does not primarily map organizational ownership across business functions.

The Discovery value of a cross-functional representation is that it can reveal handoffs, dependencies, duplicated effort, and organizational boundaries that may contribute to friction in the process.

Study Guide reference/topics: Cross-Functional Map, process mapping, business teams, responsibilities, Discovery.

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

The correct answer is A. Remove low value list views from public view, as identified in the uploaded study guide.

The problem is not primarily record access. It is that users have too many list views to choose from, making relevant views harder to locate. The study guide therefore addresses the source of the clutter directly by removing low-value views from public visibility.

Option B changes Sharing Rules, which affect which records users are permitted to access. That does not directly reduce the number of available list-view definitions and therefore does not solve the navigation problem stated in the question.

Option C would allow users to manage public list views, but that shifts administrative complexity to users rather than simplifying the experience for them.

The UX principle is reduction of unnecessary choice. When many low-value options are presented alongside useful ones, users must spend additional effort scanning and deciding which view to use. Removing low-value public views makes the remaining choices more meaningful.

The study-guide answer therefore improves the experience by simplifying the list-view environment itself rather than changing security or delegating additional management responsibility to users.

Study Guide reference/topics: List Views, information reduction, user efficiency, Salesforce configuration, Declarative Design.

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

The correct answer is A. Create a custom Theme in Themes and Branding, selecting logo, brand colors, and images, exactly as stated in the uploaded study guide.

The requirement is to make Lightning Experience conform to the company's existing design guidelines using declarative configuration. The study guide therefore directs the UX Designer to the standard Themes and Branding capability rather than to custom development.

A custom theme allows the organization to apply important brand assets such as the company logo, brand colors, and imagery so that the Salesforce environment presents a recognizable visual identity.

Option B is insufficient because selecting whichever built-in theme happens to be closest does not guarantee compliance with Cloud Kicks' actual design guidelines.

Option C refers to a different branding mechanism and includes font-type configuration, but it is not the declarative approach keyed by the study guide for the current Lightning Experience scenario.

The broader UX principle is to implement branding through supported Salesforce configuration whenever those tools satisfy the requirement. This preserves consistency and avoids unnecessary custom styling while still aligning the environment with company identity.

Study Guide reference/topics: Themes and Branding, Lightning Experience, brand colors, logos, Declarative Design.

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

The correct answer is C. Expert Review, as explicitly identified in the uploaded study guide.

The key wording is that Cloud Kicks wants to independently audit the current website for possible usability issues. An Expert Review fits that purpose because a UX professional examines the existing interface and identifies usability concerns based on established UX knowledge and evaluation criteria.

Option A, Task Analysis, focuses on understanding the activities, steps, and requirements involved in users completing a task. It can be highly valuable during research, but it is not primarily an independent audit of an existing interface.

Option B, User Shadowing, is an observational research method in which designers observe users working in their real context. That requires direct user involvement and therefore does not match the request for an independent audit.

The distinction is between expert inspection and user research. Both can identify important problems, but the scenario specifically asks for a designer-led evaluation of the current site.

An Expert Review can therefore provide Cloud Kicks with an initial inventory of usability issues that can later inform redesign priorities and, where appropriate, further user testing.

Study Guide reference/topics: Expert Review, usability audit, Experience Cloud, evaluation methods, Testing.

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

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.

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

The correct answer is B. Personas, as identified in the uploaded UX Designer study guide.

A persona is a research-based representation of an archetypical user. It consolidates recurring characteristics such as goals, behaviors, common tasks, motivations, and pain points into a form that designers and stakeholders can use throughout the design process.

This is especially relevant when Cloud Kicks is designing for both internal and external audiences. Different user groups can have substantially different objectives and interaction patterns, so documenting representative personas helps prevent the team from designing around assumptions or around a single generic “user.”

Option A, Storyboards, illustrate scenarios or sequences of activity. They are useful for showing how a person interacts with a solution over time, but they do not primarily document the archetypical characteristics of the user.

Option C, User Stories, capture requirements from a user's perspective, typically describing what a user wants to accomplish and why. They support backlog definition but are not a full representation of the user's characteristics and pain points.

The study-guide distinction is therefore straightforward: personas describe who the user is; user stories describe what the user needs; storyboards show an experience unfolding over time.

Study Guide reference/topics: Personas, archetypes, user goals, tasks, pain points, Discovery.

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

The correct answer is B. Field-Level Security, as explicitly identified in the study guide. The important constraint is that Cloud Kicks has one standard Order page layout shared by different types of users. The requirement is therefore not to create separate layouts, but to control which fields are visible to internal versus external users.

The study guide selects Field-Level Security because it governs whether particular users can see or interact with specific fields even when the same page layout is shared. This makes it suitable for restricting sensitive or irrelevant information without duplicating the overall record-page structure.

Option A, Audience Targeting, is associated with presenting Experience Cloud or component content to different audiences, but it is not the field-visibility mechanism selected in this study-guide scenario. Option C, Dynamic Forms, can conditionally control field and section presentation on supported record pages, but the answer key specifically identifies Field-Level Security for the shared-layout visibility requirement.

From a UX standpoint, limiting users to the fields that are relevant and permitted for their role reduces unnecessary information exposure and keeps the shared record experience focused while preserving the organization's security model.

Study Guide reference/topics: Field-Level Security, shared page layouts, user-specific visibility, Sales Cloud, Declarative Design.

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

The correct answer is A. Personalized Navigation Tabs, as stated in the uploaded study guide. The requirement specifically concerns the Salesforce mobile app and giving employees quick access to apps, objects, and other frequently used Salesforce items. Personalized Navigation Tabs provide the navigation mechanism identified by the guide for this purpose.

The design objective is straightforward: frequently accessed resources should be easily reachable from the user's primary navigation rather than forcing repeated searching or unnecessary movement through unrelated areas. Personalization also allows the navigation experience to reflect what individual users access most often.

Option B, Console Navigation, is intended for console-style working environments where users handle multiple records and related information within a workspace. It does not match the mobile quick-access requirement described here.

Option C, Utility Bar, provides persistent access to selected productivity utilities within supported Lightning applications, but it is not the mobile navigation feature specified by the answer key.

This question reinforces a recurring UX Designer principle: select Salesforce navigation features according to the user's working context. For mobile users who need fast access to apps, objects, and commonly used items, the guide specifies Personalized Navigation Tabs.

Study Guide reference/topics: Salesforce mobile app, Personalized Navigation Tabs, navigation, productivity, Declarative Design.

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

The correct answer is A. Be specific about the issues testers encountered, as stated in the uploaded study guide.

Usability findings become actionable when stakeholders understand exactly what happened, where it happened, and how it affected the participant's ability to complete the task. Specific descriptions therefore provide a stronger basis for design and development decisions than vague observations such as “users found the page confusing.”

Option B recommends excluding issues merely because they were already known. Existing problems encountered again during testing can still be meaningful evidence about their impact on users, so selectively omitting them would weaken the representation of the session.

Option C proposes identifying participants by name. The study guide does not support that approach; participant identities are not necessary for communicating the usability problem itself.

The broader testing principle is to translate observations into precise findings that the product team can understand and act upon. A specific finding connects the observed problem to the relevant part of the experience rather than leaving stakeholders to interpret ambiguous research notes.

Accordingly, the study guide prioritizes clear, concrete reporting of encountered issues.

Study Guide reference/topics: Usability Testing, reporting findings, research observations, actionable UX findings, Testing.

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

The correct answer is A. Typography, Color, Imagery. The study guide explicitly identifies these three elements as the visual-design tools that translate style and branding guidelines into the interface.

Typography determines how written content is visually expressed through type choices, hierarchy, scale, and treatment. Color communicates brand identity and can establish hierarchy, emphasis, and consistency across the experience. Imagery reinforces visual identity through photography, illustrations, icons, or other graphical assets.

Options B and C contain useful UX artifacts, but they perform different functions. Wireframes communicate layout and information hierarchy; personas represent user archetypes; blueprints define component structures; sketching supports early ideation; and storyboards communicate an experience or scenario. None of those groups directly represents the core visual-language elements used to implement a brand style.

The study-guide distinction is therefore between design process artifacts and visual design attributes. When the requirement is to translate an organization's branding or style guide into an interface, typography, color, and imagery provide the direct visual mechanisms through which that identity becomes perceptible to users.

Study Guide reference/topics: Visual Design, Branding, Typography, Color, Imagery, UX Fundamentals.

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

The correct answer is A. Observing user behavior, as explicitly identified by the uploaded study guide.

Human-centered design begins with understanding the people for whom a product, service, or process is being designed. Observing actual user behavior allows designers to understand what users really do, including their workflows, difficulties, workarounds, and environmental constraints. This provides evidence that may not emerge if the team relies only on assumptions or internal business objectives.

Option B places company OKRs at the center of requirements definition. Business objectives are important constraints, but they do not substitute for understanding users when adopting a human-centered approach.

Option C places rapid prototyping before ideation. Prototyping is useful for making ideas tangible and testing them, but the team first needs to understand users and generate potential solutions.

The study-guide distinction is therefore between evidence about people and organization-centered or prematurely solution-centered activities. Observing users gives the organization direct insight into needs and behavior and helps ensure subsequent design decisions are grounded in real experiences rather than assumptions.

Study Guide reference/topics: Human-Centered Design, user observation, behavioral research, user needs.

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

The uploaded study guide identifies A. Marketing Cloud Personalization as the correct Salesforce capability for boosting B2C website engagement.

The requirement is specifically to improve business-to-consumer engagement on the website. Within the study guide's framing, Marketing Cloud Personalization is the capability aligned to tailoring digital experiences based on customer context and behavior.

Personalization can make an experience more relevant by changing which content, recommendations, or interactions are presented according to what is known about the user or their current context. Greater relevance can reduce the amount of irrelevant material a consumer must navigate and can increase meaningful engagement with the site.

Option B, Experience Cloud, is used for building external digital experiences and communities, but the question specifically asks which capability should boost B2C engagement through personalization.

Option C, Marketing Cloud Account Engagement, is not the answer selected for this B2C website scenario.

The UX distinction is between merely providing an external site and adapting that site's experience to the consumer. In the answer key, Personalization is the Salesforce capability that most directly addresses this objective.

Study Guide reference/topics: Marketing Cloud Personalization, B2C engagement, personalized experiences, website UX, Declarative Design.

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

The correct answer is C. At least 4.5:1, which the uploaded UX Designer study guide identifies as the WCAG Level AA threshold for normal text. Color contrast measures the luminance difference between foreground text and its background. Adequate contrast is essential for users with low vision, color-vision deficiencies, age-related vision changes, or users working under difficult viewing conditions.

For normal-sized text, the Level AA requirement represented in the study guide is a minimum ratio of 4.5:1. This means the text color and background color must be sufficiently different in luminance for content to remain readable.

Option A, 7.0:1, corresponds to a more stringent accessibility threshold and is not the Level AA minimum requested in this question.

Option B, 3.0:1, is insufficient for ordinary text under the criterion being tested. Lower ratios may apply in other accessibility contexts, but they do not satisfy this specific normal-text Level AA requirement.

For a UX Designer, the practical lesson is that branding cannot be evaluated independently from accessibility. A visually appealing colored background is unacceptable if it reduces text readability below the required contrast level.

Study Guide reference/topics: WCAG Level AA, color contrast, accessibility, readable text, UX Fundamentals.

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

The correct answer is B. Accordion, according to the uploaded UX Designer study guide.

An Accordion component is designed specifically to divide content into sections that users can expand and collapse. This directly matches the requirement to organize a substantial amount of information while preventing all sections from occupying screen space simultaneously.

The UX value is progressive disclosure. Users can initially see the section headings and open only the information relevant to their current task. This reduces visual overload and makes content-heavy experiences easier to scan.

Option A, Lightning Toggle, represents a control for switching a state or setting between alternatives. It is not a structural component for organizing multiple groups of content.

Option C, Dynamic Actions Bar, relates to presenting contextual actions rather than organizing information into collapsible content regions.

The study-guide answer therefore maps the interaction requirement directly to the appropriate Lightning component. When information can be logically divided into discrete sections and users do not need to view every section simultaneously, an Accordion provides an efficient presentation model.

A UX Designer should still use meaningful section labels so users can predict the contents of each collapsed area without repeatedly opening sections to discover what they contain.

Study Guide reference/topics: Accordion, collapsible content, progressive disclosure, information organization, SLDS.

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

The correct answer is B. Docked prompt using In-App Guidance, as specified in the uploaded study guide.

The requirement is to inform users that a new feature has become available and provide a short explanatory video in the context of their Salesforce experience. In-App Guidance is specifically intended for contextual onboarding, feature announcements, adoption support, and targeted instructional content.

A Docked Prompt is appropriate because it can remain visible while allowing the user to continue interacting with the application. It provides enough space for explanatory content without necessarily blocking the entire workflow.

Option A, using the Utility Bar, would place the video in a persistent productivity area, but that does not provide the same contextual announcement mechanism for a newly enabled feature.

Option C requires a custom component even though Salesforce provides an out-of-the-box onboarding capability suited to this requirement. Introducing custom development would add unnecessary implementation and maintenance effort.

The study-guide principle is to use contextual, declarative guidance when users need timely help or feature education. Rather than forcing users to search external documentation, guidance can be delivered directly within their working environment.

Study Guide reference/topics: In-App Guidance, Docked Prompts, onboarding, feature adoption, Declarative Design.

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

The correct answer is C. `slds--size-1-of-2`, which the uploaded study guide explicitly identifies as the class that does not follow the expected SLDS convention. SLDS uses a structured naming system derived from Block-Element-Modifier (BEM) conventions. Salesforce documentation describes a block as the primary component, an element as a constituent part represented with a double underscore, and a modifier as a variation or state.

Current Salesforce guidance is particularly relevant here. Modern SLDS notation uses the single underscore for modifier syntax. For example, `slds-avatar_circle` correctly represents the circular avatar variant. `slds-box` is itself a valid SLDS utility/component class. Salesforce also confirms that older double-dash modifier syntax has been deprecated in favor of the single-underscore convention. Option C is malformed because the separator appears immediately after the `slds` namespace: `slds--size-1-of-2`. Even historical sizing syntax would have been structured around the size class, such as `slds-size--1-of-2`, rather than `slds--size-1-of-2`. Modern notation uses forms such as `slds-size_1-of-2`. Therefore, C clearly violates the expected SLDS class structure.

Study Guide reference/topics: SLDS, BEM naming, CSS classes, modifiers, Lightning Web Components.

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

The correct answer is A. Use the theme editor to adjust fonts, text case, colors, and site logo. The study guide explicitly selects this option for an Experience Builder implementation that must remain within out-of-the-box styling and component capabilities.

The important constraint is that the UX Designer cannot depend on custom styling or custom components. The Theme Editor is therefore the appropriate declarative mechanism because it allows the visual identity of the site to be adapted while remaining inside the standard Experience Builder framework.

Fonts, capitalization treatment, colors, and the site logo are all fundamental brand-expression elements. Adjusting these values allows the Experience Cloud site to reflect the organization's established visual identity without creating a separate custom presentation layer.

Option B affects footer content rather than the overall branded experience. Social-media links can be useful, but their presence does not establish the site's primary visual language.

Option C concerns page variations based on user behavior. That is a personalization technique rather than the direct brand-configuration solution requested.

The study-guide principle is therefore to use supported declarative theme controls first when the requirement is brand customization without custom development.

Study Guide reference/topics: Experience Builder, Theme Editor, branding, out-of-the-box configuration, Declarative Design.

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

The correct answer is A. Trailhead modules. The study guide explicitly identifies Trailhead modules as the content that can be assigned to learners through Learning Paths in this onboarding scenario.

The question is testing the distinction between Salesforce learning content that can be incorporated directly into an employee learning assignment and other forms of Trailhead achievement or assessment. Within the guide's framing, Learning Paths is being used as an onboarding mechanism, so the appropriate assigned resource is a structured Trailhead module.

Modules are suited to an onboarding context because they represent defined learning content around a subject area. The requirement is not merely to give employees an environment in which to experiment or to require a larger credential-oriented achievement. Instead, Cloud Kicks wants to assign learning material as part of a managed learning experience.

Option B, hands-on challenges, describes a specific assessment/activity format rather than the assignment type selected by the guide. Option C, Superbadges, represents a broader accomplishment and is not the answer keyed for Learning Paths here.

Therefore, when the objective is to assign structured onboarding learning through Learning Paths, the study guide points to Trailhead modules.

Study Guide reference/topics: Learning Paths, employee onboarding, Trailhead modules, assigned learning, Declarative Design.

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

The study guide identifies C. Personalize the Navigation bar as the correct recommendation.

The question focuses specifically on an individual sales representative who wants more intuitive access to regularly used content. Personalized navigation directly addresses that need by allowing the user's frequently accessed destinations to be easier to reach within their normal Salesforce workflow.

Option A, customizing the Home page theme, changes visual presentation rather than improving direct access to regularly used content.

Option B, setting up Quick Links in the Utility bar, may appear plausible as a shortcut mechanism, but it is not the personalization approach selected by the source. The study guide consistently associates Navigation bar personalization with adapting frequently accessed Salesforce items to an individual user's working pattern.

The UX principle is to reduce unnecessary navigation for high-frequency tasks. When users repeatedly access the same objects or destinations, allowing those resources to be represented directly in their navigation reduces search effort and supports faster task completion.

Thus, according to the guide, the appropriate user-level personalization is to personalize the Navigation bar.

Study Guide reference/topics: Personalized Navigation, frequently used content, Salesforce user experience, Declarative Design.

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

The uploaded study guide identifies A. Reducing friction for users in achieving their goals as the correct benefit of inclusive design.

Inclusive design considers a wider range of user needs, abilities, contexts, and potential barriers. When those barriers are addressed, the resulting experience becomes easier for more people to understand and operate. The study guide therefore expresses the benefit in terms of reduced friction.

Option B contradicts the inclusive-design objective because designing exclusively for one user type risks excluding users whose circumstances or abilities differ from the assumed norm.

Option C also misrepresents inclusive design. The objective is not to simplify the experience to a generic lowest common denominator. Rather, the designer should identify barriers and create solutions that allow a broader range of people to participate successfully.

This answer is consistent with the inclusive-design principles earlier in the guide: recognize exclusion, learn from diversity, and solve for one in ways that can extend to many. When exclusion is reduced, users encounter fewer obstacles while trying to complete their intended tasks.

The practical outcome is therefore not only accessibility in a narrow sense, but a smoother and more usable experience across a broader population.

Study Guide reference/topics: Inclusive Design, reducing friction, user goals, exclusion, Human-Centered Design.

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

The uploaded study guide identifies C. There are different writing directions (right to left vs. left to right) and layouts need to be adjusted accordingly as the correct internationalization consideration.

The site will be used across twelve countries, so the UX Designer must plan beyond simple text translation. Different languages can follow different writing directions, and that affects the structure and flow of the entire interface.

A right-to-left language may require layout adjustments to navigation, alignment, component sequencing, and the general reading flow so that the experience remains natural for the intended audience.

Option A is problematic because a country and a language are not equivalent concepts. A country can contain multiple languages, and the same language can be used across multiple countries. The study guide therefore does not select flags as the ideal language-switching mechanism.

Option B suggests that users in different countries inherently perceive color contrast differently. That is not the internationalization consideration keyed by the guide.

The broader HCD lesson is that internationalization must account for the structural characteristics of language and culture, not simply replace words. Layout direction is therefore a fundamental design requirement when supporting both left-to-right and right-to-left writing systems.

Study Guide reference/topics: Internationalization, right-to-left layouts, Experience Builder, global UX, Human-Centered Design.

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

The uploaded UX Designer study guide identifies A. Specifying breakpoint sizes as the responsive design best practice.

Responsive design must account for changes in available screen width. Breakpoints provide defined thresholds at which the layout can adapt so that content remains usable and appropriately structured across different screen sizes.

The study guide therefore selects specifying breakpoint sizes as the practice that directly supports responsive behavior.

Option B, using interaction models, is not the responsive-layout mechanism described in this question. Interaction models can define how users work with an interface, but they do not themselves establish when the visual layout should change in response to screen dimensions.

Option C, creating a separate mobile-specific site, is not the best practice identified by the guide. The responsive approach is intended to allow one experience to adapt according to available space rather than requiring an entirely separate site merely because the device is smaller.

The important distinction is between adaptive layout behavior and maintaining separate experiences. Breakpoints allow the design to respond systematically as the viewport changes.

For the UX Designer, the practical objective is to define when content should resize, reorganize, wrap, or otherwise change presentation so that the experience remains usable across device dimensions.

Study Guide reference/topics: Responsive Design, breakpoints, screen sizes, adaptive layouts, UX Fundamentals.

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

The uploaded study guide identifies A. Allow the user to explore the application without specific questions regarding which tasks to perform as the correct way to reduce confirmation bias.

Confirmation bias occurs when researchers consciously or unconsciously seek evidence that supports what they already believe. In this scenario, Cloud Kicks already knows that the application is not performing as expected, so directing users toward suspected problems could influence what researchers observe.

Allowing participants to explore without narrowly steering them toward predefined tasks gives the team a better opportunity to discover what users naturally notice, attempt, and struggle with.

Option C explicitly asks researchers to confirm an existing hypothesis, making it the opposite of the desired approach.

Option B uses open-ended questions, which can be useful in research, but the study guide does not select it as the strongest response in this scenario.

The core Human-Centered Design lesson is to allow evidence from users to challenge the team's assumptions. Researchers should avoid constructing sessions in a way that merely validates what they already expect to find.

This makes exploratory observation particularly valuable when the cause of a performance or usability problem is uncertain.

Study Guide reference/topics: Confirmation Bias, user feedback, research neutrality, Human-Centered Design.

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

The uploaded study guide specifies B. Page headers as the correct answer. A corporate logo is a persistent identity element normally associated with the site's header or theme-level branding area. In an Experience Cloud site, the logo should therefore be implemented within the portion of the experience responsible for global page identity rather than unrelated content channels.

Salesforce's Experience Builder documentation confirms that images can be uploaded and selected for areas including the header and logo, with those assets stored for reuse within the site's asset library. This aligns directly with the purpose of a prominent site-wide brand logo.

Visualforce pages would only be appropriate where a specific custom Visualforce implementation requires its own markup. Updating separate Visualforce pages would also risk inconsistent branding across the experience. Email templates control outbound email presentation and have no role in displaying the primary logo in the Digital Experience site's interface.

From a UX standpoint, common branding elements should be located at the appropriate global or reusable presentation level. This provides consistency, maintainability, and predictable placement across pages.

Accordingly, the page header is the correct target for prominently incorporating the updated company logo.

Study Guide reference/topics: Experience Cloud branding, page headers, logo placement, reusable site elements, Declarative Design.

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

The correct answer is B. Set field-level error message to display on the page. The study guide presents this scenario and identifies B as the answer. The validation rule already determines whether the phone number satisfies the required formatting and length conditions. From a UX perspective, the next objective is to communicate the validation failure at the location where the user must correct it. A field-level error message places the feedback adjacent to the phone field, reducing the user's effort to determine what went wrong and where corrective action is required.

Option A, In-App Guidance, is better suited to onboarding, contextual instruction, feature adoption, or process coaching. It is unnecessarily indirect for a deterministic input-validation error.

Option C, making the field required, only ensures that some value is entered. A required-field setting does not validate whether the phone number contains the correct number of digits or follows the required formatting pattern.

The UX principle being tested is effective error prevention and recovery. When a user enters invalid information, the interface should provide specific, contextual, and actionable feedback instead of forcing the user to search for the affected field.

Study Guide reference/topics: Validation Rules, field-level errors, error prevention, form usability, Declarative Design.

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

The correct answer is A. Divergent and convergent, exactly as identified in the uploaded study guide. Design thinking deliberately alternates between divergent thinking and convergent thinking. Divergence expands the problem or solution space. During this mode, the team deliberately generates numerous possibilities, considers alternative perspectives, challenges assumptions, and avoids eliminating unusual concepts too early.

Convergence performs the opposite function. The team evaluates the possibilities against user needs, constraints, evidence, business requirements, feasibility, and other decision criteria. Weak alternatives are discarded or combined, allowing the team to narrow a large set of possibilities into one or more promising directions.

Both modes are necessary. Converging too early can produce predictable solutions because the team accepts the first workable idea. Remaining indefinitely in divergence creates many concepts without a mechanism for deciding what should actually be developed.

Option B combines delivery-related qualities but does not describe the creative problem-solving cycle. Option C describes desirable characteristics of a solution rather than a recognized thinking framework.

For new customer services, the UX Designer should first open the solution space through divergence and then focus it through convergence, repeating that cycle as research, prototyping, and testing generate new evidence.

Study Guide reference/topics: Design thinking, divergent thinking, convergent thinking, ideation, Human-Centered Design.

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

The correct answer is C. Desirable, Feasible, Viable, exactly as identified in the study guide. These three criteria represent a foundational human-centered design framework. Salesforce Trailhead explains that human-centered design historically seeks solutions that are desirable, feasible, and viable. A desirable solution addresses something people genuinely need; a feasible solution can realistically be created with available technology and capabilities; and a viable solution fits the organization's business model and objectives. Successful UX design therefore requires more than satisfying the user in isolation. A proposed Salesforce experience could be highly desirable to sales representatives but technologically impractical. Likewise, a technically feasible solution that users do not need provides little value. A solution can satisfy both users and technology constraints yet still fail if it cannot support organizational objectives or sustainable operations.

V2MOM is Salesforce's organizational alignment framework covering Vision, Values, Methods, Obstacles, and Measures; it is not the conceptual product-design balance described here. Agile is an iterative delivery methodology rather than the three-dimensional HCD evaluation model.

For the redesigned sales processes, Cloud Kicks should therefore seek the intersection where user needs, implementation capability, and business sustainability are simultaneously satisfied.

Study Guide reference/topics: Human-Centered Design, desirability, feasibility, viability, design thinking.

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

The uploaded UX Designer study guide identifies C. Determine the change in scope and impact of each enhancement request as the correct answer.

User acceptance testing has produced enhancement requests, but the next step should not be to implement them immediately. The study guide first requires the team to evaluate how each requested change affects the existing solution.

Assessing scope and impact allows the team to understand whether an enhancement is minor or substantial, what parts of the solution it could affect, and how it may change the originally planned work.

Option A moves directly into prioritization. Prioritization can be useful, but the guide's answer indicates that the requests first need to be understood in terms of their impact and scope before deciding how to implement them.

Option B suggests developing all requests in a sandbox. That assumes all requests should proceed to development, which is premature before their implications have been analyzed.

The testing principle represented here is controlled response to feedback. UAT findings may reveal valid improvements, but each change should be assessed systematically before implementation so that the team understands what the enhancement means for the overall solution.

Study Guide reference/topics: User Acceptance Testing, enhancement requests, scope analysis, impact analysis, Testing.

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

The correct answer is C. `title`, as specified in the uploaded study guide.

The accessibility problem is that the icon has no visible descriptive label. The study guide therefore identifies the `title` attribute as the mechanism that supplies a descriptive text value for the icon within the SLDS Component Blueprint context.

Option A, `href`, identifies a referenced resource or destination and does not provide the descriptive label required by the scenario.

Option B, `class`, is used to associate styling or behavior with the element. It does not communicate the icon's meaning to users who cannot rely solely on its visual appearance.

The accessibility requirement is important because an icon's graphic form may not be perceivable or self-explanatory to every user. When a visible text label is absent, an appropriate textual description must still communicate the purpose represented by the icon.

The guide's answer therefore reinforces a broader SLDS accessibility principle: visual indicators should not depend exclusively on their appearance. Designers must account for users who interact through assistive technologies or who cannot interpret an unlabeled icon visually.

Study Guide reference/topics: SLDS Component Blueprints, accessibility, icon labels, `title` attribute, Salesforce Lightning Design System.

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

The correct answer is A. Provide clear explanations of AI predictions or recommendations. The study guide explicitly keys this response as the action associated with responsible and transparent AI.

The wording of the question places emphasis on transparency. A transparent AI experience should help the person interacting with the system understand what the AI is presenting rather than simply exposing an unexplained prediction or recommendation.

Option A directly addresses that requirement by communicating an explanation alongside the AI output. In UX terms, this gives the user more context for interpreting the system's recommendation and makes the interaction less opaque.

Option B emphasizes collecting a maximum amount of user data. Regardless of whether additional data might support personalization, that choice does not directly satisfy the transparency requirement being tested in the guide.

Option C describes an internal demonstration or education session. That could inform employees about AI, but it does not make the actual user-facing AI prediction or recommendation more understandable.

The guide therefore distinguishes between organizational activity around AI and transparency within the user experience itself. The appropriate design step is to make AI-generated outcomes understandable to the person receiving them.

Study Guide reference/topics: Responsible AI, transparency, explainability, AI recommendations, Human-Centered Design.

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

The correct answer is A. Component Blueprints, exactly as identified in the study guide. The key phrases are accessible HTML and CSS and implementation guidelines. Component Blueprints are the SLDS resource the study guide associates with these needs. They provide the structural patterns required to build components that visually and semantically align with the Salesforce Lightning Design System.

This is especially important when a UX Designer and developer are implementing a custom Lightning Web Component rather than relying entirely on an existing base component. Starting from a documented blueprint helps maintain consistency with established Salesforce component structure.

Option B, Design Tokens, serves another purpose. Tokens represent reusable design values such as spacing, sizing, or color. They support visual consistency but do not provide complete component markup and implementation patterns.

Option C, Development Tools, may support implementation workflow, but it does not represent the specific SLDS location described in the question.

The study-guide distinction is therefore precise: when a designer requires the HTML/CSS structure and implementation guidance for an SLDS component, the appropriate reference is the Component Blueprint.

This also reinforces the design-system objective of reducing custom reinvention and promoting consistent, accessible interface construction.

Study Guide reference/topics: SLDS Component Blueprints, accessible markup, component implementation, LWC, Salesforce Lightning Design System.

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

Responsible AI requires users to understand how an AI-supported experience reaches or communicates consequential outputs. Therefore, providing clear explanations of predictions and recommendations directly supports transparency and explainability. The uploaded study guide explicitly identifies A as the correct response. Salesforce's AI guidance similarly treats explainability as fundamental to useful predictive experiences. Salesforce describes predictive outputs as not merely providing an outcome but also enabling users to understand factors contributing to that outcome and take appropriate action. This supports the UX principle that AI should not behave as an opaque decision mechanism.

Option B is incorrect because responsible data practices do not advocate indiscriminate data collection. Data collection should be purposeful and proportionate to the intended experience. Collecting more data simply because it is available creates privacy, bias, and governance concerns. Option C may support organizational education, but an internal demonstration does not make the actual user-facing AI interaction transparent.

The strongest UX solution is therefore to expose understandable reasoning or contextual explanations around AI-generated predictions and recommendations.

Study Guide reference/topics: Responsible AI, transparency, explainability, trustworthy user experiences, Human-Centered Design.

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

The correct answer is C. Brand color and loading page logo, which is explicitly identified in the study guide. Salesforce provides native branding controls for the Salesforce mobile application. Official Salesforce Help states that administrators can customize the application's brand color, loading-page background color, and loading-page logo to align the mobile experience with company identity. The brand color influences important user-interface elements such as the header, buttons, and search bar. Salesforce can also derive contrasting colors for supporting interface elements based on the selected brand color. The loading-page logo gives organizations a recognizable branded identity during the application startup experience.

Option A is incorrect because although branding can influence the color treatment of interface elements, Salesforce does not provide branding configuration for redesigning the search bar layout itself. Option B similarly describes settings that are not the standard mobile-branding controls specified by Salesforce.

This distinction is important for a UX Designer because declarative Salesforce configuration should be used before custom development. When the requirement can be satisfied through Salesforce's supported branding settings, those controls provide greater maintainability and platform consistency.

Thus, brand color and loading-page logo are valid customizable elements for CK's mobile branding.

Study Guide reference/topics: Salesforce mobile branding, brand color, loading-page logo, Declarative Design.

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

The study guide explicitly identifies C. Become familiar with the Salesforce Lightning Design System (SLDS) component blueprints as the correct first step.

Before designing a new Lightning component, the UX Designer should understand the established Salesforce patterns applicable to that type of interface. SLDS Component Blueprints provide the structural and visual reference for Salesforce-style components and therefore give the designer a foundation before introducing custom decisions.

Option A begins with design tokens. Tokens are useful for consistent values such as spacing, sizing, or visual attributes, but importing them before understanding the component pattern would start at too low a level. The designer first needs to understand the component architecture and behavior.

Option B focuses on AppExchange packages. AppExchange can provide complete applications and extensions, but reviewing packages is not the first design step identified in this scenario.

The underlying principle is design-system-first thinking. Before creating a new component, designers should understand how Salesforce already represents similar controls and interactions. This reduces inconsistency and makes it easier for developers and users to recognize established Lightning patterns.

Study Guide reference/topics: SLDS Component Blueprints, component design, Lightning, design-system consistency, Salesforce Lightning Design System.

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

The correct answer is C. Allows the user to share a raw stream of thought, as explicitly identified in the uploaded study guide.

The think-aloud technique asks users to verbalize what they are thinking while they interact with an interface or attempt a task. The value described by the study guide is that this provides researchers with access to the participant's immediate thought process.

Rather than observing only whether the user succeeds or fails, the researcher can hear what the user expects, what they find confusing, what assumptions they are making, and why they choose a particular path.

Option A is incorrect because asking someone to continuously verbalize thoughts does not necessarily create a more natural situation. It is a deliberate research technique.

Option B is also incorrect. Think-aloud does not eliminate bias from user behavior; instead, it provides additional qualitative information about the user's reasoning.

The important distinction is between observable behavior and expressed reasoning. A user may hesitate or select the wrong option, but the think-aloud stream can reveal why that behavior occurred.

The study guide therefore treats think-aloud as a way to obtain richer qualitative evidence during user testing.

Study Guide reference/topics: Think-Aloud Protocol, user testing, qualitative research, user reasoning, Testing.

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

The correct answer is B. Neutral button for "Cancel" and "Back"; Brand button for "Continue". This is the configuration identified by the uploaded UX Designer study guide. Button hierarchy communicates the relative importance of available actions. In this scenario, Continue advances the user through the primary three-step process, making it the principal action within the modal. It should therefore receive the visually prominent Brand treatment. Back and Cancel are secondary actions. Back reverses navigation within the flow, while Cancel exits or abandons the current interaction. Giving both actions the same visual prominence as Continue would weaken the action hierarchy and increase the possibility of users selecting the wrong control. Option A incorrectly emphasizes Cancel alongside Continue. Option C makes all three controls primary, effectively eliminating visual prioritization entirely. The SLDS design principle is that visual emphasis should correspond to action priority. A modal or flow should normally provide an obvious primary action while secondary navigation or dismissal controls use less prominent styling. This improves scanability, predictability, and task completion. Therefore, using a Brand button for Continue and Neutral buttons for Back and Cancel provides a clear and consistent interaction hierarchy.

Study Guide reference/topics: SLDS buttons, Brand button, Neutral button, action hierarchy, modal design.

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

The study guide identifies C. Menu tabs can be Visualforce and Lightning pages as the correct administrative capability for Salesforce mobile navigation setup.

The question is testing what administrators can include when configuring the navigation experience available to mobile Salesforce users. According to the answer key, navigation entries can include supported Visualforce and Lightning pages, giving administrators a mechanism to expose relevant application destinations through the mobile navigation structure.

Option A states that menu tabs can be based on different user types. Although user access can influence what users ultimately see within Salesforce, that is not the navigation capability selected by the study guide in this question.

Option B claims visibility can be based on user location. The guide does not identify geographic location as the relevant administrative mechanism for setting up mobile navigation tabs.

The broader declarative-design principle is that mobile users should have direct navigation to the Salesforce resources relevant to their workflows. Administrators can configure supported page types as destinations without requiring users to reach them through indirect navigation paths.

This allows the Salesforce mobile experience to incorporate both Lightning-based and Visualforce-based functionality where appropriate.

Study Guide reference/topics: Salesforce mobile navigation, menu tabs, Visualforce pages, Lightning pages, Declarative Design.

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

The uploaded study guide identifies B. Prioritizing engagement over number of impressions as the strategy aligned with Relationship Design.

The distinction in the question is between depth of relationship and simple exposure metrics. Relationship Design is represented here by emphasizing meaningful engagement rather than merely maximizing how many times people see a message, product, or interaction.

An impression is fundamentally an exposure measure. A high number of impressions can demonstrate reach, but it does not necessarily indicate that users have developed a useful, valuable, or sustained relationship with the organization.

Engagement, by contrast, reflects active interaction. The study guide therefore associates it more closely with a relationship-oriented strategy.

Option A reverses the more meaningful emphasis by prioritizing outputs over outcomes. Relationship-oriented design is concerned with the value or effect created through an experience, not simply the volume of produced artifacts or activities.

Option C likewise emphasizes broadcasting product benefits rather than understanding customers. That framing moves away from the user-centered and relational orientation represented by the question.

Therefore, Cloud Kicks' strategy should focus on quality of engagement, treating meaningful interaction as more valuable than simple visibility or impression volume.

Study Guide reference/topics: Relationship Design, engagement, customer relationships, outcomes, Human-Centered Design.

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

The uploaded study guide identifies C. User Flow as the correct UX method.

The key phrase is “series of steps to achieve a meaningful goal.” A User Flow represents how a user progresses through actions, decisions, screens, or states while attempting to complete a task. It therefore makes the relationship between individual steps and the final objective visible.

Option A, a User Persona, represents the user rather than the sequence of actions the user performs. Personas capture characteristics, needs, goals, behaviors, or pain points, but they do not primarily visualize task progression.

Option B, a Wireframe, represents the structure of an individual page or screen. Wireframes are useful for determining information hierarchy and interface layout, but they do not inherently document the complete sequence a user follows from one interaction to another.

The study-guide distinction is consequently straightforward: persona = who the user is; wireframe = how a screen is structured; user flow = how the user moves through steps toward a goal.

User flows help designers identify unnecessary steps, decision points, and transitions before detailed interface design is finalized.

Study Guide reference/topics: User Flow, task sequence, user goals, UX artifacts, UX Fundamentals.

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

The uploaded study guide identifies C. Work together on setting up UX indicators as the correct response.

The problem is fundamentally one of alignment: developers do not yet see the value produced by the proposed design changes. Establishing UX indicators collaboratively creates measurable criteria that both design and development teams can use to evaluate whether the changes improve the experience.

The emphasis on working together is important. Rather than asking developers to accept a design argument based purely on the designer's authority, both groups agree on evidence that can demonstrate improvement.

Option A relies on research notes from previous projects. Those findings may not directly correspond to the current problem, users, or implementation context.

Option B attempts to resolve resistance hierarchically by persuading a development lead and relying on that person to convince the rest of the team. That may secure compliance, but it does not create shared understanding of the UX objective.

The study-guide answer therefore favors a measurable and collaborative approach. UX indicators can turn subjective disagreement into a discussion around observable outcomes, helping multidisciplinary teams evaluate whether the design actually produces the intended improvement.

Study Guide reference/topics: UX indicators, design-development collaboration, measuring UX, stakeholder alignment, UX Fundamentals.

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

The study guide identifies B. Update the Home page with access to commonly used reports as the appropriate improvement.

The user interviews reveal an important behavioral pattern: accessing commonly used reports is a frequent daily task, but users currently depend on Global Search to locate them repeatedly. The guide's solution is to surface those high-value resources more directly on the Home page.

This reduces the repeated effort involved in searching for something users already know they need every day. The Home page can therefore act as a task-oriented starting point that provides immediate access to frequently used information.

Option A proposes a separate navigation tab for every report. That could overcrowd navigation and turn individual reports into permanent top-level destinations.

Option C uses Global Actions, but those controls are primarily action-oriented rather than the report-access mechanism identified by the study guide.

The UX principle is to use research findings to reduce unnecessary interaction. If interviews show that a resource is accessed constantly, the interface should make that resource more directly available rather than forcing users to rediscover it through search every time.

Study Guide reference/topics: Home page design, reports, user interviews, frequent tasks, Declarative Design.

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