Pass the Salesforce Designers Plat-UX-101 Questions and answers with Dumpstech

The correct artifact is a journey map, and the uploaded study guide explicitly identifies B as the answer. A journey map documents an experience from the user's perspective across its stages and touchpoints. Salesforce Trailhead explains that journey maps can capture actions, thoughts, feelings, touchpoints, contextual factors, and opportunities. Critically, the artifact highlights where friction or pain occurs and where improvements could produce the greatest impact. Salesforce's UX artifact guidance similarly states that journey maps help identify process optimizations, pain points, and potential solutions. That directly corresponds to the scenario. The UX Designer needs to understand the call center's existing experience before proposing a Salesforce solution. Observation supplies empirical information about how agents currently perform complaint logging; the journey map then organizes those findings around activities, problems, and opportunities. A business process diagram is useful for documenting process mechanics and decision paths but normally provides less emphasis on the user's emotional and experiential context. A prototype would be premature because it represents a proposed solution rather than documenting the current-state experience. The Discovery principle is therefore: understand and visualize the existing user journey before designing the future solution.

Study Guide reference/topics: Discovery research, journey mapping, current-state analysis, pain points, opportunities.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The 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 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 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 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 study guide identifies A. Run the Salesforce Optimizer App to identify fields not in use as the correct answer. The scenario presents two related UX problems: the Contact page contains too many irrelevant fields, and users experience long page-load times. The selected approach begins by identifying which configuration elements are no longer providing value.

Using Salesforce Optimizer gives the organization evidence about unnecessary or underused configuration so that administrators can make informed decisions about simplifying the experience. This is stronger than merely relocating unused information.

Option B does not actually solve the underlying problem. Moving unused fields to another section still leaves those fields in the interface and can retain unnecessary page complexity.

Option C, In-App Guidance, could help explain where important fields are located, but it would layer guidance on top of an already cluttered experience rather than addressing the clutter itself.

The UX implication is that unnecessary interface elements should be evaluated and removed rather than simply documented or rearranged. A cleaner Contact experience can make relevant sales information easier to find while reducing the amount of configuration presented on the page.

Study Guide reference/topics: Salesforce Optimizer, page simplification, unused fields, Sales Cloud UX, Declarative 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 study guide selects B. Economic growth, greater market share, and less employee turnover as the business outcomes representing the value of diversity, inclusion, and equality in design.

The option is internally consistent because each listed outcome is positive from an organizational perspective: business growth, broader market reach, and improved employee retention.

Option A includes lower market share, which conflicts with the positive business-value framing of the question. Even though inclusive recruitment is itself presented positively, the overall combination is not the one identified by the study guide.

Option C includes more employee turnover, which similarly represents an undesirable organizational outcome and therefore does not align with the intended value proposition.

The question is not asking only about ethical design principles; it is asking how those principles can be framed in terms of business outcomes. The guide therefore connects diversity, inclusion, and equality with both organizational sustainability and market performance.

For the UX Designer, the implication is that inclusive design considerations can be communicated to stakeholders not only as design responsibilities but also through outcomes meaningful to the organization.

Study Guide reference/topics: Diversity, inclusion, equality, business outcomes, inclusive design, Human-Centered Design.

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