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

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

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

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

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

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

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

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

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

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

The study guide identifies C. Wireframes as the correct artifact for quickly planning and communicating intended page layouts.

The key requirements in the question are speed, planning, and communication of layout. A wireframe is appropriate because it allows the UX Designer to represent the structure of the page—such as major content areas, navigation, controls, and information hierarchy—without committing to polished visual treatment.

Option A, UI Mockups, generally represents a more visually developed expression of the interface. That level of detail is unnecessary when the immediate objective is to communicate page organization.

Option B, High-fidelity Prototypes, goes further by representing a much more complete and realistic version of the experience. Using that level of fidelity during early structural planning would introduce detail beyond what the question requires.

The guide is therefore testing the designer's ability to select the correct artifact according to the stage and purpose of the design activity. When the problem is primarily structural, the lightest-weight artifact that communicates that structure is preferable.

Wireframes allow stakeholders to discuss page composition and hierarchy before significant effort is invested in final appearance or interaction details.

Study Guide reference/topics: Wireframes, page layouts, fidelity, UX artifacts, UX Fundamentals.

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

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

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

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

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

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

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

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

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

The correct answer is A. 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 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 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 correct answer is C. Lookup, as explicitly shown in the study guide. A Lookup relationship is Salesforce's flexible mechanism for linking records between objects where one record can be associated with another without imposing the stronger dependency characteristics of a Master-Detail relationship. This makes it appropriate for common many-to-one relationships, where many child-side records may reference one record on another object.

The key distinction is relationship strength. A Master-Detail relationship creates a tightly coupled dependency. The detail record depends strongly on the master, and the relationship can affect ownership, sharing, roll-up summaries, and deletion behavior. It should therefore be used only when those stronger semantics are actually required.

A Hierarchical relationship is a specialized relationship available for the User object and is intended to create user-to-user hierarchy relationships. It is not the general-purpose solution for linking arbitrary business objects.

For a UX Designer, data-model decisions matter because they affect how related information is displayed, edited, navigated, and maintained in the user experience. Choosing the correct relationship type allows the designer and administrator to support the intended business interaction without introducing unnecessary data dependencies.

Therefore, for the generic one-to-many or many-to-one relationship described, Lookup is the appropriate choice.

Study Guide reference/topics: Salesforce data model, Lookup relationships, object relationships, Declarative Design.

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

The correct answer is B. Acquiescence Bias, as keyed in the uploaded study guide.

The scenario concerns survey responses that could become positively skewed. The study guide identifies acquiescence bias as the response bias the UX Designer should watch for in that situation.

Acquiescence bias refers to the tendency of respondents to agree with statements or provide affirmative responses rather than expressing their actual position with complete independence. In a survey about purchasing behavior, this can produce an artificially positive result if the questions are framed in a way that invites agreement.

Option A, Objectivity Bias, is not the response bias selected by the study guide for this scenario.

Option C, Recency Bias, concerns disproportionate influence from more recent experiences or information rather than a tendency to provide agreeable or positive responses.

The practical research lesson is that survey questions must be designed so they do not encourage respondents toward a favorable answer. Neutral wording and balanced response structures help the designer obtain a more accurate picture of user behavior.

Accordingly, the source identifies Acquiescence Bias as the primary concern when avoiding positively skewed survey results.

Study Guide reference/topics: Acquiescence Bias, surveys, response bias, research validity, Testing.

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

The correct answer is A. Distributed Marketing and Journey Builder, as provided by the study guide. The requirement is not simply to create branded emails. Cloud Kicks needs to ensure that communications delivered by individual agents remain aligned with organization-wide branding and communication standards across customer touchpoints.

The study guide therefore pairs Distributed Marketing with Journey Builder. This combination supports centrally governed marketing content and coordinated customer communications while still enabling distributed teams or individual users to participate in customer engagement.

Option B includes Email Builder and Customer 360, but that pairing does not directly address the stated requirement for centrally controlled, consistently branded agent communications across a coordinated journey.

Option C combines Service Cloud and Letterhead. Letterheads can contribute to email presentation, but they do not provide the broader orchestration and distributed-brand-governance capability described.

The UX issue is consistency. Customers should experience a coherent brand voice and presentation regardless of which employee initiates a communication. Inconsistent messages can weaken trust and create a fragmented customer experience.

The study-guide solution therefore favors tools that support centralized communication design combined with distributed execution, preserving consistent branding while supporting operational flexibility.

Study Guide reference/topics: Distributed Marketing, Journey Builder, brand consistency, customer communications, Declarative Design.

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

The study guide identifies C. The color palette is auto-generated based on the brand color to be WCAG compliant as the correct answer. Salesforce's current theming architecture reinforces this principle. Administrators define a primary brand color, and Salesforce generates complementary palette values for the interface. With SLDS 2 themes, Salesforce specifically generates accent, container-accent, and border-accent colors that meet applicable WCAG color-contrast requirements. Salesforce explicitly discourages overriding those generated accessible colors because manually selected replacements may no longer provide adequate contrast. This is important because a company brand color selected in isolation does not guarantee accessible text, controls, borders, or component states. A design system must derive related colors with sufficient perceptual separation and contrast across the interface.

Option A reverses the recommended practice: accessible generated values should generally not be overridden merely for visual preference. Option B is too restrictive; Salesforce branding supports considerably more customization than changing only a single brand color.

The UX principle is to preserve organizational identity while allowing the design system to generate accessible supporting values. This makes branding scalable across components without requiring designers to manually calculate every UI color combination.

Study Guide reference/topics: Themes and Branding, WCAG, accessible color palettes, brand colors, Declarative Design.

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