Plat-UX-101 Exam Dumps - Salesforce Designers Questions and Answers

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 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. Cross-Functional Map, as stated in the uploaded study guide.

The requirement is not simply to document the sequence of a process. Cloud Kicks specifically wants to explain the relationship between process steps and the business teams responsible for or involved in those steps.

A Cross-Functional Map is suited to that requirement because it organizes process activities according to the different roles, groups, or organizational functions involved. This allows stakeholders to see both the sequence of work and how responsibility moves across functional boundaries.

Option B, a Detailed Process Map, can document individual steps in significant depth, but the question emphasizes the relationship between those steps and different teams.

Option C, a Journey Map, represents an experience from the user's perspective, typically emphasizing stages, touchpoints, pain points, and opportunities. That is valuable for understanding the user's experience but does not primarily map organizational ownership across business functions.

The Discovery value of a cross-functional representation is that it can reveal handoffs, dependencies, duplicated effort, and organizational boundaries that may contribute to friction in the process.

Study Guide reference/topics: Cross-Functional Map, process mapping, business teams, responsibilities, Discovery.

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

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 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 correct answer is C. Dynamic Actions, as explicitly stated in the uploaded study guide. Dynamic Actions allow actions displayed on a Lightning record page to vary according to specified conditions. This is exactly what Cloud Kicks needs because users only require particular actions at particular record statuses.

Instead of displaying every available action at all times, the designer can configure visibility rules so that relevant actions appear contextually. This reduces visual clutter in the Highlights panel and helps users focus on actions that make sense at the current stage of the workflow.

Option A, Audiences, is primarily used to tailor Experience Cloud or Lightning content for particular user groups or contexts. It does not directly solve conditional record-action visibility based on record state.

Option B, Dynamic Forms, controls field and field-section placement and visibility. Dynamic Forms can simplify a record page by displaying relevant fields conditionally, but the requirement here specifically concerns action buttons, making Dynamic Actions the correct capability.

From a UX standpoint, contextual actions support recognition over recall and reduce decision fatigue. Users should not have to mentally filter a long list of irrelevant commands before locating the action they need.

Study Guide reference/topics: Dynamic Actions, Highlights Panel, Lightning Record Pages, conditional visibility, 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 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 B. Have users sort the cards based on similar categories or groups, as confirmed by the study guide. Card sorting is a UX research method used to understand how users naturally categorize and mentally organize information. Salesforce Trailhead specifically describes card sorting as suitable for grouping things into categories, giving navigation-menu items as an example. For an Experience Cloud site's navigation structure, the designer can represent pages, tasks, topics, or content items as cards and ask representative users to organize them into groups that make sense to them. Depending on the research design, participants may also label those groups. The resulting patterns help inform the site's information architecture, including menu categories, grouping, hierarchy, and terminology.

Option A describes a comparative evaluation of alternative menu designs and is closer to usability comparison or A/B-style testing than card sorting. Option C imposes an arbitrary alphabetical structure instead of investigating users' mental models and expectations.

The core Discovery principle is that information architecture should reflect how users understand the domain rather than how the organization's internal structure happens to be arranged. Card sorting therefore converts user-generated grouping patterns into evidence for designing more intuitive navigation.

Study Guide reference/topics: Discovery research, card sorting, information architecture, navigation, mental models.

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

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.

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