Free Salesforce Plat-UX-101 Practice Exam with Questions & Answers | Set: 2

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. Empathy Map. The uploaded UX Designer study guide identifies the Empathy Map as the appropriate tool for synthesizing knowledge about users after personas have already been established.

An empathy map provides a structured way for a design team to consolidate what it knows about a user or persona. It commonly captures what users think, feel, say, and do, helping stakeholders develop a shared understanding of user motivations, concerns, behaviors, and needs. This makes it particularly useful after research findings have been gathered and personas are already available.

Option A, an Executive Summary, can communicate high-level findings to stakeholders, but it is primarily a reporting artifact. It does not organize user-centered observations in the same structured, empathy-oriented format.

Option C, Prioritize Backlog, belongs to planning and delivery. Backlog prioritization helps determine which work should be implemented first, but it does not synthesize user understanding.

The critical distinction is between understanding users and prioritizing solutions. At this stage, Cloud Kicks needs to create organizational alignment around what is known about its users. An Empathy Map supports that objective directly.

Study Guide reference/topics: Empathy Maps, personas, research synthesis, shared user understanding, Discovery.

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

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 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. Community Manager. The uploaded study guide explicitly associates a user who moderates forums, enforces community standards, and supports members with the Community Manager persona. Persona identification is important during UX discovery because different user archetypes have different goals, responsibilities, pain points, and workflow expectations. A Community Manager typically focuses on maintaining the health and quality of an online community. Their activities commonly include monitoring member participation, moderating discussions, responding to inappropriate content, applying community policies, encouraging engagement, and assisting members.

A Site Admin is more closely associated with administration and configuration responsibilities, such as site settings, access, technical configuration, or platform maintenance. Although a Site Admin can support an Experience Cloud environment, the activities described in the question are primarily community-governance activities rather than system-administration activities.

A Support Manager would normally focus on support operations, service teams, escalations, case management, agent performance, or customer-service delivery rather than ongoing forum moderation and community-policy enforcement.

From a UX perspective, correctly identifying the persona helps the designer build navigation, moderation tools, dashboards, workflows, and information architecture around the user's real operational responsibilities.

Study Guide reference/topics: Personas, user research, Experience Cloud users, role identification, Discovery.

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

The correct answer is C. Key fields to complete before next Path stage, which the uploaded study guide confirms. Salesforce Path provides stage-oriented guidance for processes such as opportunities. Its major UX value comes from showing users where they are within the process and surfacing the information most relevant to each stage. Salesforce documentation states that a Path can expose up to five key fields per step, helping users focus on important information, together with contextual Guidance for Success. This makes key fields especially useful for onboarding. A new sales representative does not need to memorize every field or requirement associated with the opportunity lifecycle. Instead, the interface progressively surfaces the important information at the relevant stage, reducing cognitive load and reinforcing the intended business process.

Option A is not a standard defining capability of Path. Path does not primarily exist to supply integrated approval-automation buttons. Option B refers to a separate component and does not represent the core stage-specific onboarding functionality being tested.

One nuance is important: Path highlights key fields but does not inherently make those fields mandatory solely because they appear there; validation rules may be required when true enforcement is needed.

Study Guide reference/topics: Salesforce Path, key fields, onboarding, Guidance for Success, process guidance.

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

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 study guide identifies A. Visibility of system status as the correct answer. The visual indicators communicate important information about the current state and requirements of the interface before the user attempts submission. By clearly showing which fields are required, the system makes its expectations visible rather than forcing users to discover them only after making an error.

Option B, User Control and Freedom, concerns providing users with mechanisms to recover from or reverse unwanted actions, such as canceling, backing out, or undoing operations. That is not the main issue here.

Option C, Error diagnosis and recovery, relates to helping users understand and recover from errors once they occur. Required-field indicators can help prevent such errors, but in this study-guide question the emphasis is on making necessary status and requirements visibly apparent.

Consistent patterns are especially important. If required fields are indicated differently on different screens, users must repeatedly relearn the interface. A shared pattern creates predictable behavior and enables faster form completion.

Therefore, the visual indicator acts as continuous system communication: users can immediately perceive what the form expects from them before attempting to complete the process.

Study Guide reference/topics: Usability Heuristics, visibility of system status, required fields, form design, 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. 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.

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