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

The correct answer is C. Card Sorting, as stated in the uploaded study guide.

The question emphasizes two related needs: understanding employees' mental model and creating an information architecture that matches user expectations. Card sorting is directly suited to this because participants organize items into categories according to how they naturally perceive relationships between them.

The results reveal how users group concepts, which labels make sense to them, and how content or functions might be organized within navigation. That makes the method particularly useful before finalizing the structure of a new community.

Option A, Cognitive Walkthrough, evaluates whether users can successfully progress through an existing or proposed interaction based on their expected knowledge and goals. It does not primarily generate an information architecture.

Option B, Mind Mapping, can help organize ideas or concepts but is not the user-research technique selected by the guide for uncovering how users classify information.

The study-guide principle is that information architecture should reflect the way users mentally organize the domain rather than merely mirror an internal organizational structure. Card sorting supplies evidence for designing that structure.

Study Guide reference/topics: Card Sorting, information architecture, mental models, user expectations, Discovery.

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

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 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 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 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 uploaded study guide identifies C. Provide links to external resources, such as training videos or a company dictionary as the correct Help Menu customization.

The scenario asks specifically about customizing the Salesforce Help Menu so sales users can efficiently find assistance for important functions and processes. Providing links to relevant training videos, internal definitions, or other curated resources allows support material to be available from a centralized help location within the users' working environment.

Option A proposes a site map, which organizes content structurally but is not the Help Menu customization selected by the guide.

Option B refers to a docked prompt. Docked prompts belong to In-App Guidance and can be appropriate for contextual announcements or onboarding, but the question specifically asks how to customize the Help Menu.

The distinction is between proactive contextual prompts and a centralized collection of help resources. For recurring reference material, the study guide points to Help Menu links that connect users directly to supporting resources.

This can improve productivity because users do not have to independently locate training material every time they need clarification.

Study Guide reference/topics: Salesforce Help Menu, In-App Guidance, training resources, user enablement, Declarative Design.

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

The correct answer is C. Account, Contact, Opportunity, according to the uploaded study guide.

The question tests the Salesforce data-model transition associated with converting a Lead. The study guide identifies the resulting business records as Account, Contact, and Opportunity.

Conceptually, each record represents a different part of the emerging customer relationship. The Account represents the customer or organization context, the Contact represents the individual person involved, and the Opportunity represents potential sales business being pursued.

Option A includes an Order. An Order represents a later transactional concept and is not one of the three records identified by the guide as the typical outcome of lead conversion.

Option B refers to a “Converted Lead” and Activity, but the guide does not identify those as the three resulting records in the standard lead-to-opportunity flow being tested.

For a UX Designer, understanding this record lifecycle matters because a user interface should align with what happens to users' data as they advance a sales process. Navigation, record context, and process guidance all depend on understanding how a Lead transitions into the customer and opportunity records sales users subsequently work with.

Study Guide reference/topics: Lead Conversion, Account, Contact, Opportunity, Sales process, Declarative 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 B. Heuristic Evaluation, exactly as provided by the study guide. A heuristic evaluation is a structured expert-review technique in which an interface is examined against recognized usability principles or heuristics. It is therefore the most appropriate method when the explicit objective is to assess whether an existing portal conforms to standard usability principles. Evaluators systematically review the experience for issues such as poor feedback, inconsistent behavior, confusing terminology, weak error handling, excessive memory demands, or lack of user control. Findings can then be categorized and prioritized for remediation. Option A, “Intuitive Review,” is not the formal evaluation method referenced by the study guide. A UX professional may informally assess an experience, but that does not provide the same systematic framework as a heuristic evaluation. Option C, User Testing, involves representative users performing realistic tasks while researchers observe behavior. It is valuable for identifying real-world usability problems, but the question specifically asks about compliance with established principles, not observation of task performance. The distinction is important: heuristic evaluation is an expert inspection method, while usability testing is an empirical user-research method. For this Experience Cloud portal, a heuristic evaluation provides the appropriate structured mechanism for reviewing usability against recognized standards.

Study Guide reference/topics: Heuristic Evaluation, usability inspection, expert review, usability principles, Testing.

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

The uploaded study guide identifies A. Group similar fields using sections as the correct page-layout practice.

A record page can contain many fields, and users need to understand the information quickly rather than scan an undifferentiated collection of inputs and values. Grouping related fields into meaningful sections creates structure and makes the page easier to navigate.

Option B recommends including every field that might potentially be useful. That approach increases visual clutter and places additional cognitive demands on users because they must repeatedly distinguish important information from peripheral information.

Option C concerns making field labels identical to API names. API names exist primarily for technical implementation purposes and do not define the organization or usability of the user-facing page layout.

The study-guide answer therefore focuses on information organization. Related content should be presented together so users can predict where information belongs and locate it more efficiently.

For example, fields concerning customer information, reservation details, scheduling, or status can be grouped according to their functional relationship rather than presented as one continuous list.

The result is a clearer visual hierarchy and a more efficient Salesforce record experience.

Study Guide reference/topics: Page layouts, field sections, information organization, visual hierarchy, Declarative Design.

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