Plat-UX-101 Salesforce Certified Platform User Experience Designer Questions and Answers

The correct answer is A. Rich Text, images, and links, which is also the answer explicitly provided by the uploaded study guide. Salesforce Path is intended to guide users through stages of a business process. For each Path stage, an administrator can designate key fields and provide contextual Guidance for Success. Salesforce documentation describes this guidance as a place for information such as tips, links, questions, and company policy information that assists users in successfully completing that stage. This distinction is important. A Path already acts as a visual representation of progress through values such as Opportunity Stage. The Guidance for Success area supplements that progression with useful instructional material. Rich content and links can explain activities, remind representatives of procedures, provide supporting resources, or direct users toward relevant information. A Progress Indicator is therefore not the appropriate content element for Guidance for Success because Path itself visually represents progression. Merge fields are also not the expected answer in this configuration context. Consequently, rich instructional content provides the strongest fit for stage-specific coaching and supports Salesforce's declarative approach to improving process usability without developing a custom interface.

Study Guide reference/topics: Salesforce Path, Guidance for Success, key fields, contextual guidance, Declarative Design.

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

The uploaded study guide identifies A. Voice reflects personality, and tone is the way in which one speaks as the correct distinction.

Within the guide's framing, voice is the more persistent expression of identity or personality. It represents the recognizable character behind communication. Tone, by contrast, describes how that voice is expressed in a particular communication situation.

This distinction matters in UX content because an organization's fundamental personality can remain recognizable while its tone changes according to context. For example, an interface may require a different manner of expression when communicating success, explaining an error, or guiding a user through an important process, while still representing the same underlying brand personality.

Option B treats voice and tone as literal audio characteristics—frequency and pitch—which does not correspond to the communication-design meaning being tested.

Option C reverses the relationship identified by the study guide, assigning personality to tone rather than voice.

The UX principle is consistency without rigidity: voice provides identity; tone adapts the expression of that identity to the situation. Understanding this distinction helps designers maintain coherent interface content across different user states and interactions.

Study Guide reference/topics: Voice and Tone, content design, brand personality, UX communication, UX Fundamentals.

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

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 uploaded study guide identifies B. Only the body, footer, and header helper components can be styled using styling hooks as the correct answer.

The item tests an implementation constraint that matters when a UX Designer is attempting to align a Lightning modal with organizational branding. The guide distinguishes between the primary modal framework and its associated helper components.

According to the answer key, the relevant styling-hook support applies to the body, footer, and header helper components, rather than to the primary Lightning Modal component as described in option A.

Option C is too broad because the study guide does identify supported styling-hook usage within the modal's helper-component structure.

The UX implication is that brand requirements must be evaluated against the styling capabilities Salesforce actually exposes. A designer should not assume that every visual property of every base component can be overridden freely. Design-system components deliberately constrain customization so that accessibility, structure, and platform consistency can be maintained.

Therefore, when preparing specifications for a custom modal experience, the designer must account for the specific styling surfaces supported by the Lightning modal architecture rather than designing treatments that cannot be implemented through the available hooks.

Study Guide reference/topics: Lightning Modal, styling hooks, LWC, branding constraints, SLDS.

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

The study guide identifies A. Troubleshooting customer issues and logging activities as the correct activity set for the Case Solver persona.

Persona-based UX design requires the designer to align the interface with the user's primary responsibilities rather than with every activity that may exist somewhere within the organization. The name “Case Solver” itself points toward users whose principal work centers on resolving customer cases.

Option A directly reflects that operational role. Troubleshooting addresses the core problem-resolution responsibility, while logging activities supports documentation of the work performed while handling the customer issue. Those tasks therefore belong at the center of the Case Solver experience.

Option B shifts toward coaching, administration, or knowledge-management responsibilities. Those activities may exist within a service organization, but they are not the primary activities the study guide associates with the Case Solver persona.

Option C combines case-status visibility with campaign metrics. Campaign analysis belongs to a different business context and therefore does not form a coherent task set for this Service Cloud persona.

The design implication is that pages, actions, information hierarchy, and workflows should prioritize the activities users perform most frequently. For the Case Solver, the guide centers that experience on customer troubleshooting and activity logging.

Study Guide reference/topics: Personas, Case Solver, Service Cloud, task analysis, Discovery.

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

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 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 solution is C. Enablement Site to build and assign custom modules, exactly as specified in the uploaded study guide. An Enablement Site is appropriate because the requirement is broader than simply showing users contextual assistance. Cloud Kicks requires structured, custom product training that can be delivered as learning content to internal users and leadership. Salesforce's Enablement functionality supports publishing modules and assigning relevant learning content to users. Salesforce documentation specifically explains that administrators can assign modules published on an enablement site and that users can complete assigned content from within Salesforce. Option A addresses a narrower use case. In-App Guidance prompts are effective for contextual onboarding, feature announcements, and short instructional interventions within the user's workflow, but they are not a replacement for a structured custom learning curriculum.

Option B provides an environment where users can experiment, but a sandbox does not inherently provide organized learning modules, assignments, learning progression, or formal enablement content.

The UX requirement here is therefore solved by selecting the platform capability that supports repeatable, organized, assignable learning experiences, rather than merely contextual assistance or an experimentation environment.

Study Guide reference/topics: Enablement Sites, custom learning modules, onboarding, internal user education, Declarative Design.

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

The correct answer is B. Distinguishable, matching the uploaded study guide. Within WCAG's Perceivable principle, the distinguishable guidance focuses on making visual and auditory content sufficiently separable so that users can perceive important information. For text, buttons, and other interface elements, adequate color contrast is one of the central implementation requirements.

Salesforce's accessibility guidance explains that ordinary text should maintain sufficient contrast against its background and notes additional WCAG 2.1 contrast requirements for visual information needed to identify user-interface components and states, including button and input boundaries. Consequently, when a UX Designer selects foreground text and button-background colors, contrast and distinguishability must be evaluated rather than relying only on aesthetic brand preferences.

Adaptable concerns presenting information in ways that can be transformed or interpreted through different structures or presentation modes without losing meaning. Navigable addresses the user's ability to locate content, move through interfaces, understand focus, and determine their position. Neither directly describes the color-contrast requirement posed by the scenario.

Therefore, the UX Designer must ensure text and button treatments remain visually distinguishable, particularly for users with low vision or reduced color perception.

Study Guide reference/topics: WCAG, accessibility, distinguishable content, color contrast, Experience Builder, UX Fundamentals.

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

The correct answer is B. Experience Cloud, as stated in the uploaded UX Designer study guide. Experience Cloud is designed to create external-facing digital experiences that connect customers, partners, and other audiences with Salesforce data and processes. A B2B sales portal commonly needs authenticated external users to access CRM information, collaborate with the organization, view or manage opportunities, work with leads, or interact with other Salesforce records. That requirement aligns directly with Experience Cloud because the portal experience can be built around CRM-connected data while still presenting an external interface tailored to business partners or customers. Option A, Commerce Cloud, is primarily focused on digital commerce experiences and transactional storefront requirements. Although commerce can be relevant to B2B scenarios, the question specifically emphasizes creating a sales portal that integrates customer relationship management, which points to Experience Cloud. Option C, Sales Cloud, provides the CRM capabilities used by internal sales organizations, but it is not itself the external portal solution described in the scenario. From a UX architecture perspective, the correct platform should match both the target audience and the interaction context. Here, external B2B users require a portal tightly integrated with Salesforce CRM data and processes.

Study Guide reference/topics: Experience Cloud, B2B portal, CRM integration, external experiences, Declarative Design.

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

The study guide identifies C. Compact Layouts as the correct answer.

The requirement is straightforward: when a sales representative views an Opportunity record, the most important fields should be immediately available without requiring unnecessary navigation or custom development.

Compact Layouts are the standard Salesforce feature selected by the guide for surfacing key record information concisely. The UX objective is to ensure that users can quickly orient themselves to the record and access the information required for common decisions.

Option A, a custom Lightning Web Component, would introduce custom development even though the scenario can be addressed using standard Salesforce configuration. This would add implementation complexity without a demonstrated need.

Option B, Tabs, can help organize larger groups of page content, but they do not specifically solve the requirement to expose a concise group of high-value record fields.

The UX principle is prioritization of information. Not every field on an Opportunity carries equal importance during routine record viewing. A compact presentation allows the designer or administrator to surface the fields that users need most frequently while keeping the broader record available when required.

Study Guide reference/topics: Compact Layouts, key fields, Opportunity records, information prioritization, Declarative Design.

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

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.

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

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 correct answer is B. Responsive, exactly as keyed by the uploaded UX Designer study guide.

The defining requirement is that both the site's size and content should adjust according to screen size, platform, and orientation. The study guide classifies this behavior as responsive design.

Responsive design allows a single interface to reorganize itself according to the space and display conditions available. Elements may resize, wrap, move, or change their relative arrangement as the viewport changes. This helps preserve usability across desktops, tablets, mobile devices, and different device orientations.

Option A, Progressive, does not describe the responsive layout approach requested in this scenario.

Option C, Adaptive, is related to supporting different environments, but the study guide specifically identifies responsive design when the page should fluidly react to changing dimensions and orientation.

This connects with other responsive-design concepts in the UX Designer material, such as using SLDS grids and breakpoints. The objective is not to design an isolated interface for every possible device but to establish layout behavior that responds appropriately when available space changes.

Study Guide reference/topics: Responsive Design, screen size, orientation, cross-device UX, UX Fundamentals.

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

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 study guide identifies C. Invite employees from different departments and create a journey map together as the correct human-centered strategy. The scenario emphasizes both human-centered design and strengthening employee relationships. Option C directly involves employees from different departments in a collaborative design activity rather than treating them only as recipients of a finished concept or sources of isolated feedback.

Creating a journey map together provides a shared representation of the experience being designed. Cross-functional participants can contribute their knowledge of user activities, pain points, interactions, and organizational dependencies. The collaborative process also creates common understanding across departments whose perspectives may otherwise remain separated.

Option A concentrates initial design decisions within the design team and only introduces employees afterward. While feedback can still be useful, it provides less opportunity for meaningful co-creation. Option B can gather input at scale, but anonymous surveys are inherently less relational and collaborative than bringing people together around a shared design artifact. The study-guide answer therefore reflects a key human-centered principle: involve people directly in understanding and shaping the experience. Collaboration across departmental boundaries can improve both the design outcome and the shared organizational understanding surrounding the product.

Study Guide reference/topics: Human-Centered Design, collaborative design, journey mapping, stakeholder participation.

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

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 B. Page layouts or permissions can display only the fields needed for each audience. This is the answer provided by the study guide. The scenario describes different audiences that consume the same knowledge system but require different levels and presentations of information. Salesforce declarative configuration allows the organization to tailor the experience using layouts and permissions instead of duplicating content unnecessarily. Option B supports audience-specific presentation by controlling which fields are exposed and which content users are permitted to access. This reduces cognitive load for customers while allowing support representatives to retain access to more detailed operational information. Option A creates unnecessary content duplication. Maintaining separate versions of the same article for every audience can create governance problems, inconsistent updates, and additional editorial overhead. Option C incorrectly assumes that external topic organization must duplicate the organization's internal category structure. A user-centered external experience should organize information in ways meaningful to customers rather than simply mirroring internal information architecture. The broader UX principle is progressive and audience-appropriate disclosure. Users should see information relevant to their tasks and permissions without being overwhelmed by fields intended for other roles. Therefore, page-layout and permission controls provide the most maintainable declarative solution.

Study Guide reference/topics: Knowledge, audience-specific content, permissions, page layouts, Declarative Design.

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

The correct answer is C. Human Centered Design, as explicitly stated in the uploaded study guide.

Human-Centered Design begins by understanding people—their needs, motivations, constraints, environments, and pain points—and then develops solutions around that understanding. The wording of the question describes exactly this sequence: first identify end-user needs, then create solutions intended to satisfy those needs.

The important point is that the solution does not begin with technology, business process, or implementation convenience. It begins with the people who will ultimately use or experience the product or service.

Option A, User Experience Design, is closely related and often operates within a human-centered approach, but the study guide is testing the broader problem-solving philosophy that starts with human needs and iteratively develops solutions around them.

Option B, Communication Design, is more specifically concerned with how information, messages, and visual communication are structured and presented. It does not describe the broader end-to-end approach stated in the question.

The study-guide framing therefore positions Human-Centered Design as an approach that connects user understanding, problem definition, ideation, and solution creation around real human needs.

Study Guide reference/topics: Human-Centered Design, user needs, problem solving, solution design, Human-Centered Design.

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

The correct answer is C. Conduct a workshop with stakeholders to align on the current state and build consensus, as explicitly keyed in the study guide.

The discovery interviews have revealed that the fundamental problem is not simply poor adoption; Cloud Kicks lacks a clear and consistent sales process. Implementing user guidance before the organization agrees on the process would therefore attempt to teach users a workflow that is not yet defined.

Option A is premature. In-App Guidance may support adoption after a process is established, but it cannot resolve disagreement about what that process should be.

Option B gathers additional individual preferences, but the problem described is organizational alignment rather than a shortage of opinions. More isolated responses could actually increase ambiguity if different representatives prefer different approaches.

The study guide therefore favors a collaborative workshop. Bringing stakeholders together allows the team to make the current process visible, identify inconsistencies, establish shared understanding, and build consensus before designing the future experience.

The Discovery principle is clear: align on the problem and current state before implementing the solution.

Study Guide reference/topics: Discovery, stakeholder workshops, current-state alignment, consensus building, adoption strategy.

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

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 study guide identifies C. Configure a pre-filtered opportunity list view for each key attribute with the partner group as the correct answer. The requirement is for partners to quickly browse opportunities according to predetermined business criteria. The guide's selected solution is therefore a declarative one: create list views that are already filtered for the relevant opportunity attributes and expose those views to the appropriate partner audience.

This approach directly addresses both conditions stated in the scenario. One view can focus on opportunities closing within two weeks, while another can focus on opportunities valued above $100,000. Partners do not need to repeatedly construct their own filters or understand the underlying filtering logic.

Option A introduces a custom Lightning Web Component even though the requirement can be addressed using standard list-view functionality. That adds unnecessary implementation complexity.

Option B delegates filter creation to each partner, which conflicts with the requirement for a quick, standardized browsing experience.

The design principle reflected by the study guide is to prefer configured, reusable Salesforce functionality when it satisfies the user need. Pre-filtered list views reduce interaction effort and provide consistent segmentation across the partner experience.

Study Guide reference/topics: Experience Builder, opportunity list views, partner experience, filtering, Declarative Design.

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

The study guide identifies A. Perform common tasks without navigating away from the page as the correct use case for the Utility Bar.

The Utility Bar is intended to provide quick access to frequently needed productivity tools while users remain in the context of their current Salesforce work. That makes it especially valuable when sellers repeatedly perform auxiliary tasks and would otherwise need to navigate to another page or application area.

The UX benefit is reduced context switching. Keeping commonly used tools immediately available allows users to maintain focus on the record or workflow they are currently handling.

Option B refers to quick access to favorite records or items, but the study-guide scenario specifically associates the Utility Bar with performing common tasks without leaving the current page.

Option C is also inconsistent with the answer key. The Utility Bar is not presented here as a mobile-specific enhancement.

The broader UX principle is efficiency of interaction. High-frequency activities should be available in a persistent, convenient location when doing so reduces unnecessary navigation and interruption.

Therefore, when discovery shows sellers value productivity and immediate access to tools, the standard Utility Bar use case is to allow them to complete common supporting tasks while remaining on their current page.

Study Guide reference/topics: Utility Bar, productivity, task efficiency, Lightning applications, Declarative Design.

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

The correct answer is C. Objects to represent storage facilities and fields to store facility details, as stated in the uploaded study guide. The spreadsheet analogy maps directly to the Salesforce data model. In the spreadsheet, each row represents an individual storage facility, while each column represents an attribute of that facility.

In Salesforce, the collection of facilities should therefore be represented by an object. Each individual facility becomes a record of that object. Properties that describe the facility—such as location, capacity, facility type, or status—should be represented by fields on that object.

Option A reverses these concepts by treating facility details as objects and storage facilities as fields. This would not correctly model the entities represented by spreadsheet rows.

Option B creates separate objects for both facilities and their attributes even though the scenario describes the details simply as characteristics of each facility rather than separate related entities.

A useful conceptual mapping is:

Spreadsheet → Salesforce

Row → Record

Column → Field

Dataset/entity type → Object

Correct data modeling directly affects UX because well-structured objects and fields produce clearer forms, record pages, reports, filtering, and navigation. Therefore, storage facilities belong as object records, with their descriptive details represented as fields.

Study Guide reference/topics: Salesforce data model, objects, records, fields, spreadsheet migration, 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 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 study guide identifies B. Use Salesforce Flow to help complete fields required for case closure as the correct answer.

The support agents must work with information distributed across several Salesforce objects while resolving and closing cases. The study-guide solution is to use Salesforce Flow to guide the agent through the required information and process steps.

This approach reduces the amount of information the agent has to locate manually. Instead of expecting agents to navigate independently between records and remember every required field, a Flow can structure the activity around the case-closing task described in the question.

Option A would increase navigation overhead by opening additional windows. That approach can fragment the user's context instead of simplifying it.

Option C focuses on components completed by the customer, while the scenario is specifically concerned with making the support agent's experience more efficient.

The UX principle is task-oriented simplification. When users must collect or update information across multiple parts of Salesforce to complete a defined business process, a guided declarative experience can reduce cognitive load and unnecessary navigation.

The guide therefore favors Salesforce Flow as the mechanism for streamlining the case-closure process.

Study Guide reference/topics: Salesforce Flow, support-agent productivity, case closure, guided processes, Declarative Design.

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

The correct answer is A. Tabbing order is logical, as confirmed by the study guide. Keyboard accessibility testing evaluates whether users can navigate and operate an interface without relying on a mouse or other pointing device. One of the most important checks is whether pressing Tab and Shift+Tab moves focus through interactive controls in an order that is logical, predictable, and consistent with the visual and semantic structure of the page. For example, focus should generally move through navigation controls, form fields, buttons, and links in an understandable sequence. An unexpected jump to unrelated content can make the interface difficult or impossible to use for people who depend on keyboard navigation or assistive technologies. Option B is not a standard keyboard-navigation requirement. Keyboard actions do not need to provide audio feedback simply because they are accessible. Option C is also insufficient because accessibility cannot depend solely on a specific color to communicate interactivity or focus. Keyboard users require a perceivable focus state, but the question asks specifically what can be verified by testing the navigation sequence. Therefore, keyboard testing should verify that focus proceeds in a meaningful and usable tab order, enabling users to reach and operate interactive elements successfully.

Study Guide reference/topics: Accessibility testing, keyboard navigation, focus order, tab sequence, Testing.

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

The study guide identifies A. Master-Detail as the correct relationship type.

The decisive requirement is that a Container Bid must be tightly dependent on its associated Container. The question provides a specific behavior: if the parent Container is deleted, the related Container Bids should also be deleted automatically. That dependency aligns with the relationship behavior the study guide associates with Master-Detail.

A many-to-one Lookup would create an association between records, but the scenario explicitly calls for a stronger dependency rather than a loose reference. The UX Designer therefore needs to consider the underlying data model, not merely how related records appear on the page.

A Hierarchical Lookup is also not appropriate for this general object-to-object relationship. The question is centered on two business objects—Container and Container Bids—and on enforcing dependent lifecycle behavior between them.

The study-guide answer illustrates that data architecture affects usability. If dependent child records remain after their parent is deleted, users can encounter orphaned or misleading information. A correctly modeled Master-Detail relationship keeps the related data aligned with the business relationship represented in the interface.

Study Guide reference/topics: Master-Detail relationships, dependent records, Salesforce data modeling, related objects, Declarative Design.

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

The correct answer is C. Invite team members to observe usability sessions, as keyed in the uploaded study guide.

The problem is not that usability findings are unavailable; the Development team does not sufficiently value or accept them. Allowing developers to observe users directly provides first-hand evidence of where participants struggle, hesitate, misunderstand the interface, or encounter barriers.

Option A adds external best-practice articles to each finding. Those resources may support a recommendation, but they remain indirect evidence. They do not allow developers to witness actual users interacting with the team's product.

Option B focuses on how much effort the research team has invested. Research effort does not establish that a finding is valid or important. Acceptance should be based on user evidence rather than on the amount of work already spent collecting it.

The study guide therefore favors direct exposure to the research process. When team members observe usability sessions themselves, findings become less abstract and are harder to dismiss as merely the UX Designer's interpretation.

This also strengthens multidisciplinary ownership: usability becomes something the whole product team can observe and understand rather than a report delivered by one specialist group.

Study Guide reference/topics: Usability testing, observation, stakeholder buy-in, research acceptance, Testing.

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

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 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 correct answer is A. Design tokens prefixed with "brand", exactly as identified in the uploaded UX Designer study guide.

The question is testing how a design system propagates theme-level design decisions across multiple components. Rather than hard-coding individual color values into every button, icon, or component, SLDS uses named design values represented through design tokens.

The guide specifically identifies tokens prefixed with “brand” as the mechanism used to align components with a custom theme.

This approach improves both consistency and maintainability. If a theme changes, components referencing the appropriate brand token can inherit the updated design value instead of requiring developers to locate and replace numerous hard-coded values.

Option B, JavaScript libraries loaded from a static resource, is not the design-value mechanism described in the question.

Option C, CSS hexadecimal values, represents the opposite of a scalable design-system approach. Hard-coded values make global design changes harder and can cause components to become visually inconsistent over time.

The study-guide principle is that theme-driven interfaces should rely on reusable named design entities rather than duplicated literal values.

Study Guide reference/topics: Design Tokens, brand tokens, themes, component consistency, Salesforce Lightning Design System.

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

The study guide identifies A. Reframe the product objectives from multiple, diverse perspectives as the correct answer. Consequence Scanning is a responsible-design activity intended to help teams think beyond the immediate intended benefits of a product. Before launch, designers and stakeholders consider how the product could affect different people, communities, systems, and contexts, including outcomes that may not have been part of the original product requirements. Reframing objectives from multiple perspectives is therefore central to the exercise. A design team may initially view a feature primarily through business or technical goals; consequence-oriented analysis broadens the discussion by considering who may be excluded, harmed, disadvantaged, or affected unintentionally. Option B describes a potentially positive result of collaborative work, but improving team well-being is not the principal goal of Consequence Scanning. Option C concerns marketing and public relations rather than responsible product design. Within Human-Centered Design, this technique helps challenge assumptions and exposes downstream implications before they become embedded in a released product. The study-guide answer therefore emphasizes diversity of perspective as a mechanism for improving responsible design decisions.

Study Guide reference/topics: Consequence Scanning, responsible design, diverse perspectives, unintended consequences, Human-Centered Design.

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

The correct answer is B. Bring together a cross-functional group with varied experiences, as explicitly keyed in the uploaded UX Designer study guide.

Consequence Scanning is represented in the guide as an activity strengthened by diverse perspectives. Bringing together people from different functional areas and with different experiences increases the likelihood that the group will identify consequences that a homogeneous team might overlook.

Option A focuses on organizational OKRs. Those objectives may inform product planning, but they are not the consideration selected by the guide for a Consequence Scanning workshop.

Option C places inclusivity examination after the product has already been built. That timing weakens the preventive value of the exercise. The study-guide framing treats consequence-oriented thinking as something that should influence design decisions rather than merely audit them after implementation.

A cross-functional workshop can expose different technical, business, user, operational, and social perspectives. This is particularly important when evaluating possible intended and unintended outcomes.

The main Human-Centered Design lesson is that responsible design analysis improves when teams deliberately include viewpoints beyond the immediate product or design group.

Study Guide reference/topics: Consequence Scanning, cross-functional collaboration, diverse perspectives, responsible design, Human-Centered Design.

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

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. 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 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 C. Account Object as the correct answer.

The scenario requires Salesforce to represent existing individual customers in a way that allows financial advisors to open a customer record and see associated business opportunities. The study guide therefore selects the Account object rather than Case or Lead.

A Case represents a support or service issue rather than the customer entity itself, so it would not provide the correct foundation for representing the person whose opportunities need to be viewed. A Lead represents a prospective individual or organization before that prospect is converted into the established Salesforce customer structure. The scenario, however, refers to customers whose business opportunities must already be associated with their records.

The fact that the bank currently serves individuals rather than corporate customers does not change the study guide's selected Salesforce object. The essential UX and data-model requirement is to represent the customer using the object intended to anchor the relationship and associated opportunities.

Correct object selection directly affects the quality of the user experience because advisors need a coherent customer record from which related sales activity can be viewed.

Study Guide reference/topics: Salesforce objects, customer representation, Account records, Sales Cloud, Declarative Design.

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

The study guide identifies B. Storyboards as the correct technique. A storyboard visually communicates how a proposed solution fits into a user's broader context, activity, or journey. Rather than showing only the interface, it presents a sequence of situations or interactions that helps stakeholders understand where, when, and why a solution matters to the customer. That makes a storyboard particularly useful in this scenario. The UX Designer already has an innovative concept; the challenge is helping the team understand how that concept integrates with the customer's real-world behavior. Option A, Personas, describe archetypical users, including characteristics, goals, behaviors, and pain points. Personas help teams understand who they are designing for, but they are less suitable for communicating the chronological context of a particular proposed solution. Option C, a High-fidelity Prototype, demonstrates the detailed appearance and interaction of the product itself. It can validate interface behavior but may still fail to communicate how the solution fits into the customer's broader activity. Storyboards bridge that gap by presenting the solution as part of a narrative. In Human-Centered Design, this allows stakeholders to evaluate the design in terms of customer context instead of viewing it only as a technical feature.

Study Guide reference/topics: Storyboards, contextual design, customer journey, communicating solutions, Human-Centered Design.

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

The uploaded study guide identifies C. Usability Testing as the correct method.

The question asks whether the form is easy and intuitive to use. That is directly a usability question, so the most appropriate validation method is to observe representative call-center staff interacting with the form and determining whether they can complete the required tasks effectively.

Option A, Qualitative, describes a broad category of research rather than the specific testing method selected by the guide. Usability testing itself can generate qualitative observations, but the question asks what kind of testing should validate the interface.

Option B, Survey, collects self-reported responses from users. Surveys can capture satisfaction or preferences but do not directly demonstrate whether users can successfully understand and complete the form in practice.

Usability Testing is therefore the more targeted method because it evaluates the interface through actual task interaction. The designer can determine where users hesitate, misunderstand labels, enter information incorrectly, or encounter unnecessary friction.

The study-guide distinction is between asking users what they think and observing whether the interface actually works for them.

Study Guide reference/topics: Usability Testing, forms, task completion, ease of use, Testing.

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

The correct answer is A. App Builder property, as keyed in the uploaded Master Study Guide.

The key requirement is that administrators, rather than developers, should be able to change the component's functionality or styling depending on the page where the component is placed. An App Builder property provides the configuration surface identified by the guide for exposing component-level settings to administrators.

This enables a reusable custom Lightning Web Component to behave differently according to the configuration selected in Lightning App Builder. Instead of creating separate components for every page context, the component can expose configurable properties.

Option B, Styling hooks, addresses styling customization but does not satisfy the broader requirement to allow an administrator to change both functionality or styling through page-specific component configuration.

Option C, Audience page variations, concerns delivering page variations according to different audiences rather than configuring reusable properties of the component itself.

The design principle is configurable reuse: a well-designed custom component can expose meaningful settings so administrators can adapt it to multiple page contexts without modifying source code or duplicating the component.

Study Guide reference/topics: App Builder properties, Lightning Web Components, configurable components, administrator customization, Declarative Design.

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

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 study guide identifies A. Standard Person Account Object as the correct answer for representing the bank's individual customers.

The decisive detail is that the bank serves individual customers rather than corporate or business customers. The Person Account model is therefore the representation selected by the guide because it is intended for circumstances where the customer relationship centers on an individual person rather than a company.

The financial advisor must also be able to open that customer's Salesforce record and see associated potential business opportunities. The selected account model gives the solution a customer-centered record around which those sales relationships can be organized.

Option B, Lead, represents a different stage of the sales relationship. The scenario describes customers whose records advisors already need to access rather than merely prospective individuals awaiting conversion.

Option C, Opportunity, represents potential business or a sales transaction rather than the person who is the customer. Opportunities can be associated with the customer record, but they cannot substitute for it.

The underlying UX/data-model lesson is that the Salesforce entity should reflect the real-world subject users think about. For a bank serving individuals, the guide specifies the Person Account model.

Study Guide reference/topics: Person Accounts, individual customers, Sales Cloud, Salesforce data modeling, Declarative Design.

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

The correct answer is C. Expand the first section by default, exactly as keyed in the uploaded study guide.

An accordion is intended to reduce vertical complexity by grouping content into expandable and collapsible sections. On a mobile screen, however, presenting every section collapsed can introduce an additional interaction before users see any substantive content. Expanding the first section by default gives users an immediate entry point and demonstrates how the accordion behaves.

Option A is unsuitable because the browser Back control normally represents navigation history. Using it as the primary mechanism for collapsing accordion content would conflict with users' established expectations about browser behavior.

Option B would cause the interface to reposition content whenever a section is expanded. That can produce unexpected movement and interfere with the user's spatial understanding of the page.

Within the study guide's framing, option C provides the most predictable mobile experience: the user immediately sees useful content while retaining the ability to expand other sections when required.

This reflects a broader UX principle of minimizing unnecessary interaction while keeping content organized through progressive disclosure.

Study Guide reference/topics: Accordion usability, mobile UX, progressive disclosure, content organization, UX Fundamentals.

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

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 correct answer is B. Add a List View component to the home page configured to show a custom list view filtered to show assigned and open cases, as specified in the study guide.

The UX requirement is to make the relevant queued Cases immediately visible so that help desk users can begin resolving work quickly. The study guide selects a filtered List View component placed directly on the team's home page.

This approach reduces the amount of navigation required before users can identify actionable cases. By filtering the list to show the appropriate assigned and open records, the home page becomes a task-oriented starting point rather than merely a general landing page.

Option A refers to a Case Assignment component, while option C refers to a Case Inbox component. Neither is the approach identified by the answer key.

The important design consideration is that the team already has a predictable record-selection criterion: the Cases must be relevant to the help desk member and remain open. A configured list view can express those conditions declaratively.

The study guide therefore favors bringing the right Salesforce records directly into the user's work context through a standard filtered list-view experience.

Study Guide reference/topics: List View component, filtered Cases, home pages, help desk productivity, Declarative Design.

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