User-Experience-Designer Salesforce Certified Platform User Experience Designer (Plat-UX-101) Free Practice Exam Questions (2025 Updated)

To customize the theme in the external customer support site to match the style guide requirements, the recommended next step is to configure the Experience Builder Theme panel. The Theme panel allows the designer to customize the look and feel of the site by setting the logo, colors, fonts, and other branding elements. The designer can also create custom themes and assign them to different pages or audiences. The Theme panel is the preferred way to apply consistent branding across the site without writing any code or overriding any styles. References: : Theme Panel | Salesforce Help : UX Designer Certification Prep: Designing with Experience Builder | Trailhead

The one token and one utility class that should be suggested to the developers to ensure custom components respect the density settings are:

varSpacingMedium. This is a design token that defines the medium spacing value for the vertical and horizontal spacing between elements. This token can be used to adjust the spacing according to the density setting of the user. For example, if the user prefers the Comply density setting, the token value will be 16px, and if the user prefers the Compact density setting, the token value will be 8px.

slds-p-around_medium. This is a utility class that applies the medium padding value to all sides of an element. This class can be used to add padding to the custom component according to the density setting of the user. For example, if the user prefers the Comply density setting, the class will apply 16px of padding, and if the user prefers the Compact density setting, the class will apply 8px of padding.

 The best option for improving the user experience of looking for and viewing commonly used reports is to update the Home page with access to commonly used reports. This way, the user can quickly access the reports they need without having to use the global search bar every time. This also follows the principle of designing for the user’s goals and tasks, which is one of the learning objectives for the Salesforce User Experience Designer certification. References: [Design for the User’s Goals and Tasks], [Change or Add Report Chart and Dashboard Components to Home Page]

https://trailhead.salesforce.com/en/content/learn/modules/ux-designer-certification-prep/design-for-the-users-goals-and-tasks :  1

To document user goals, common tasks, and pain points for a new service experience, the tool that a UX Designer should use is user personas. User personas are fictional representations of the target users, based on real data and research. User personas help the designer to understand the needs, motivations, behaviors, and expectations of the users, as well as their challenges and frustrations. User personas can also help the designer to prioritize features, create scenarios, and design solutions that are relevant and meaningful for the users. References: : UX Designer Certification Prep: Designing for User Research | Trailhead : User Personas | Salesforce Developer Guide

 The Salesforce Lightning Design System (SLDS) is a collection of resources that help you create user interfaces that are consistent with the Salesforce Lightning principles, design language, and best practices. The SLDS resources that could be used to make custom applications look, act, and sound like Salesforce are:

Blueprints and tokens: Blueprints are ready-to-use HTML and CSS UI elements that provide the foundation for Salesforce experience development. Tokens are visual design values and attributes that ensure branding and UI consistency at scale. By using blueprints and tokens, you can create custom components that follow the SLDS design standards and patterns.

Guidelines for voice and tone: Voice and tone guidelines help you write clear, concise, and consistent content that reflects the Salesforce brand personality and values. By using voice and tone guidelines, you can create custom applications that communicate effectively and respectfully with your users.

The SLDS resources that are not relevant to make custom applications look, act, and sound like Salesforce are:

Full functional components: Full functional components are pre-built Lightning components that provide out-of-the-box functionality and interactivity. They are not part of the SLDS, but rather part of the Lightning Component Library. You can use full functional components to speed up your development process, but they are not necessary to make custom applications look, act, and sound like Salesforce.

In-App Guidance: In-App Guidance is a feature that allows you to create and deliver contextual help and training to your users within your application. It is not part of the SLDS, but rather part of the Salesforce Platform. You can use In-App Guidance to enhance your user experience and adoption, but it is not essential to make custom applications look, act, and sound like Salesforce.

The Path component is a Salesforce Lightning Design System (SLDS) component that can be used to represent stages for opportunities within the sales process. The Path component displays the stages as a horizontal bar with icons and labels, and highlights the current stage with a blue background. The Path component also allows users to move opportunities to different stages, view and edit key fields for each stage, and access guidance and tips for each stage. The Path component can be added to any object that has a picklist field with values that represent stages, such as the Stage field on the Opportunity object12. References:

Path Component

Set Up a Path for Your Sales Team

 To create a unique experience for each audience that includes colors, images, and typography, the recommended out-of-the-box design approach is to use branding sets and assign them to each audience using audience targeting. Branding sets are collections of branding attributes, such as logos, fonts, colors, and images, that can be applied to a site or a page to customize its look and feel. Audience targeting is a feature that allows the designer to deliver different content and experiences to different groups of users based on criteria such as profile, location, or behavior. By creating branding sets and assigning them to each audience using audience targeting, the designer can easily create a unique and consistent experience for each audience without creating separate sites or custom themes. References: : Branding Sets | Salesforce Help : Audience Targeting | Salesforce Help : UX Designer Certification Prep: Designing with Experience Builder | Trailhead

The best approach for Cloud Kicks to create a unique look and feel for each audience is to create branding sets and assign them to each audience using audience targeting. With this approach, the same website can be used for both audiences, whilethe look and feel of each page can be tailored to each audience.

Branding sets allow you to create unique designs and apply them to specific audiences. You can create unique colors, images, and typography for each audience and then target them to the appropriate audiences using the audience targeting feature. This will ensure that each audience has a unique look and feel that meets their needs.

Designing perceivable content means that the content should be presented in a way that can be convertible between different formats, so that users with different sensory abilities can access it. For example, providing text alternatives for images and videos, captions and transcripts for audio, and audio descriptions for visual content. This way, users who are blind, deaf, or have low vision or hearing can perceive the content using assistive technologies, such as screen readers, braille keyboards, or captions. The content should not only be presented in a visual format (A) or an audio format (B), as that would exclude users who cannot see or hear the content. The content should be adaptable to different formats and devices, and follow the Web Content Accessibility Guidelines (WCAG) principle of perceivability12. References:

Perceivable - Accessibility | MDN

What Is Perceivability in Web Accessibility? WCAG Principles Explained

 A Community Manager is a Salesforce persona who is responsible for creating, managing, and moderating online communities that connect customers, partners, and employees. They spend most of their time engaging with community members, enforcing community standards, and providing member support. A Community Manager aligns with the user who performs similar tasks in moderating forums. References: : Salesforce Personas : Community Manager Roles and Responsibilities

Card sorting is a UX research method where participants group ideas or information into different categories, based on what feels natural to them. Card sorting is ideal for the early stages of a website project, when the UX designer needs to understand how users organize and label content. Card sorting can help the UX designer to suggest a suitable architecture for the internal community, based on the employees’ mental model and expectations. Card sorting can also reveal any gaps or overlaps in the content, and provide insights for naming the categories and subcategories. References: Card Sorting / Tree Testing | Bentley University, Tree Testing vs. Card Sorting: Which is Right for You? | Maze

Quantitative research methodology should be used to measure the success and usability of a feature on Experience Cloud. Quantitative research involves collecting and analyzing numerical data that can be measured, compared, or statistically tested. Quantitative research can help answer questions such as:

How many users are using the feature?

How often are they using it?

How long does it take them to complete a task with the feature?

How satisfied are they with the feature?

How does the feature affect key performance indicators, such as conversion rates, retention rates, or revenue?

Quantitative research methods can include surveys, analytics, A/B testing, usability testing, and benchmarking. These methods can provide objective and reliable data that can be used to evaluate the impact and effectiveness of a feature on Experience Cloud.

Qualitative research methodology, on the other hand, involves collecting and analyzing non-numerical data that can reveal users’ attitudes, behaviors, motivations, and preferences. Qualitative research can help answer questions such as:

Why are users using or not using the feature?

What are their pain points, needs, and goals with the feature?

How do they feel about the feature?

What are their expectations and feedback for the feature?

How does the feature fit into their context and workflow?

Qualitative research methods can include interviews, focus groups, observations, diary studies, and card sorting. These methods can provide rich and detailed insights that can be used to understand the user experience and identify opportunities for improvement.

Both quantitative and qualitative research methods are valuable for UX design, but they serve different purposes and answer different types of questions. In this case, the UX designer wants to know if the feature was successful and track usability over time, which are questions that can be best answered by quantitative research methods.

A grid system is a set of columns and rows that help to organize and align the layout and content of a web page. The Salesforce Lightning Design System (SLDS) provides a responsive grid system that adapts to different screen sizes and devices. The SLDS grid system is based on the CSS Flexbox layout module, which allows for flexible and dynamic positioning of elements. The SLDS grid system consists of the following components1:

Containers: These are the outermost elements that wrap the grid. They have a fixed width that changes according to the breakpoints defined by the SLDS. Breakpoints are the points at which the layout changes based on the screen size. The SLDS has four breakpoints: small, medium, large, and x-large2.

Grids: These are the direct children of the containers. They are the main elements that define the grid structure. They have a display property of flex, which enables the flexbox layout. They can also have modifiers that control the alignment, direction, and wrapping of the grid items3.

Grid items: These are the direct children of the grids. They are the elements that contain the actual content of the page. They have a flex property that determines how much space they take up in the grid. They can also have modifiers that control the order, offset, and visibility of the grid items4.

A UX Designer should use the SLDS grid system to design responsively within the SLDS, as it provides a consistent and flexible way to create layouts that work across different devices and screen sizes. The SLDS grid system also follows the SLDS design principles and best practices, such as clarity, efficiency, consistency, and beauty5.

The three standard Salesforce objects that should be used in this experience are:

Lead: A lead is a person who has shown interest in the company’s products or services, but has not yet been qualified as a potential customer. Leads can be captured from various sources, such as web forms, referrals, events, or marketing campaigns. Leads can store information such as name, email, phone, company, and status. Leads can be converted into accounts, contacts, and opportunities when they are ready to buy.

Contact: A contact is a person who is associated with an account and has a role in a sales process. Contacts can store information such as name, email, phone, title, and address. Contacts can be related to multiple accounts, opportunities, cases, activities, and other objects. Contacts can be used to track the communication and interaction history with the customers.

Opportunity: An opportunity is a sales deal that is in progress or has been closed. Opportunities can store information such as name, amount, stage, probability, close date, and owner. Opportunities can be linked to accounts, contacts, products, price books, quotes, contracts, and other objects. Opportunities can be used to forecast revenue, manage sales pipeline, and track sales performance.

 Tiles are standard components that display records or objects as a collection of boxes that contain a photo and additional information1. Tiles are suitable for Cloud Kicks (CK) to display contact information, including avatar, name, and title, for people who are related to a customer on a Record page, as they provide a compact and visual way to show the relevant data. Tiles also allow users to interact with the records by clicking or tapping on them1. Tiles can be customized to fit the available space and layout of the Record page2. References: Components - Salesforce Lightning Component Library, Tiles - Lightning Design System

 Interactive cards are compact components that can displayinformation such as avatars, names, and titles in an organized way. Additionally, Interactive Cards are designed to be responsive and can be used to display information on smaller screens, such as mobile devices, without taking up too much space. This makes them ideal for CK's use case, as they can display all of the required information within the limited title space. For more information, see the Salesforce Lightning Design System documentation (https://lightningdesignsystem.com/components/cards/#interactive-cards).

Consequence Scanning is a workshop method that helps teams to identify and mitigate the potential positive and negative impacts of their products or services on users, society, and the environment. When conducting a Consequence Scanning workshop, two important considerations are:

Consider design ramifications to prevent misuse and protect communities: This means that teams should think beyond the intended use cases and benefits of their products or services, and also consider the possible unintended or harmful consequences that may arise from their design choices. For example, teams should ask themselves how their products or services could be misused, abused, or exploited by malicious actors, or how they could affect vulnerable or marginalized groups, or how they could contribute to environmental or social issues. By considering these design ramifications, teams can proactively address and mitigate the ethical risks and challenges that may emerge from their products or services, and protect the well-being and interests of their users and communities.

Bring together a cross-function group with varied experiences: This means that teams should involve diverse and relevant stakeholders in the Consequence Scanning workshop, such as product managers, designers, developers, researchers, testers, marketers, legal experts, ethicists, users, or representatives from affected communities. By bringing together a cross-function group with varied experiences, perspectives, and backgrounds, teams can gain a more holistic and comprehensive understanding of the potential impacts of their products or services, and avoid blind spots, biases, or assumptions that may limit their vision or judgment. A cross-function group can also foster more creative and collaborative problem-solving, and generate more inclusive and responsible solutions.

Two resources that can help a UX Designer to explore sample code for Lightning components and see how changing the code affects the visual appearance in real time, without deploying any code to a Salesforce org, are:

Lightning Design System Website. The Lightning Design System website is a resource that provides design guidelines, UI components, and code samples for building Lightning applications. The website also features a live code editor that allows the designer to edit and preview the code for Lightning web components and Aura components, and see the changes reflected in the browser instantly. The live code editor also provides syntax highlighting, auto-completion, and error checking features. The designer can use the Lightning Design System website to experiment with different code snippets and learn how to apply the design principles and best practices for Lightning components. Lightning Design System Website, [UX Designer Certification Prep: Salesforce Design System]

Local Development Server. The Local Development Server is a resource that allows the designer to build, run, and test Lightning web components without deploying them to a Salesforce org. The Local Development Server is a CLI plug-in that creates a local web server that serves the Lightning web components from the local file system. The designer can use the Local Development Server to edit the code for Lightning web components in their preferred code editor, such as Visual Studio Code, and see the changes updated in the browser automatically. The Local Development Server also supports hot reloading, which preserves the component state and the browser session during code changes. The designer can use the Local Development Server to speed up the development and testing process and to debug the code for Lightning web components. Local Development Server, [UX Designer Certification Prep: User Testing and Evaluation]

The Lightning Web Component Recipes App and the Developer Center’s Lightning Component Library are not resources that can help a UX Designer to explore sample code for Lightning components and see how changing the code affects the visual appearance in real time, without deploying any code to a Salesforce org. The Lightning Web Component Recipes App is a sample application that showcases the functionality and best practices for Lightning web components. The Developer Center’s Lightning Component Library is a reference guide that provides documentation and examples for Lightning web components and Aura components. However, neither of these resources allow the designer to edit and preview the code in real time, as they require the code to be deployed to a Salesforce org or a scratch org first. Lightning Web Component Recipes App, Developer Center’s Lightning Component Library, [UX Designer Certification Prep: User Testing and Evaluation] References: Lightning Design System Website, Local Development Server, Lightning Web Component Recipes App, Developer Center’s Lightning Component Library, [UX Designer Certification Prep: Salesforce Design System], [UX Designer Certification Prep: User Testing and Evaluation]

 The two Salesforce features that should be suggested to improve the end-user experience are:

Favorite the often-used object. This feature allows the users to bookmark the object’s tab and access it quickly from the Favorites menu in the header. This way, the users do not have to search for the object in the App Launcher or switch to a different app to use it.

Personalize the navigation bar. This feature allows the users to customize the navigation bar in their Lightning app by adding, removing, or reordering the items. This way, the users can add the object they often use to their navigation bar and access it easily from any page in the app.

 Styling hooks are CSS custom properties that allow developers to customize the appearance of base and custom components in a consistent and supported way. They work with web components and shadow DOM, which provide encapsulation and modularity for LWC. Styling hooks use the --slds namespace and follow a naming convention that reflects the component, category, property, attribute, and state of the element being styled. For example, --slds-c-button-brand-color-background-hover is a styling hook for the button component, brand category, color background property, and hover state. Styling hooks can be declared in the CSS file of the LWC or in a global CSS file that affects all components on the page. Styling hooks are not standard CSS properties, but custom ones that are defined by SLDS and applied to the components using the var() function. References:

Styling Hooks - Lightning Design System

SLDS Styling Hooks | Lightning Web Components Developer Guide | Salesforce Developers

–dxp Styling Hooks | LWR Sites for Experience Cloud | Salesforce Developers

The Salesforce Lightning Design System (SLDS) styling hooks use standard CSS properties to easily style base and custom components. Salesforce documentation states that “SLDS styling hooks are CSS classes that give you access to the same styling used in the Salesforce Lightning Design System. They make it easy to style base and custom components with the same look and feel” [1].

[1] https://developer.salesforce.com/docs/component-library/documentation/lwc/lwc.use_slds_styling_hooks

The best option to simplify working with SLDS in Lightning Components is to install SLDS Validator extension for VS Code. This extension (salesforcedx-vscode-slds) scans the markup of the components, validates it against the SLDS documentation, and provides suggestions on how to improve the code1. It also offers syntax highlighting, code completion, and context awareness for SLDS tokens and utility classes1. By using this extension, the development team can avoid CSS conflicts, follow SLDS best practices, and create consistent and accessible components2.

Installing SLDS creator from AppExchange is not a valid option, as there is no such app available on the AppExchange. The AppExchange is a marketplace for Salesforce apps, components, and consulting services, not for VS Code extensions3.

Installing Lightning Design System Plugin for Sketch is also not a valid option, as it is not related to VS Code or Lightning Components. Sketch is a design tool that allows users to create wireframes, mockups, and prototypes4. The Lightning Design System Plugin for Sketch is a plugin that provides SLDS components, icons, and styles for Sketch users. It can help designers to create consistent and compatible designs, but it cannot help developers to work with SLDS in VS Code.