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

To create visual consistency with regard to alignments, grids, spacing, and typography, the part of the Salesforce Lightning Design System (SLDS) that should be used is utility classes. Utility classes are CSS classes that provide common styling properties, such as margins, paddings, borders, colors, fonts, and text alignments. Utility classes can be applied to any HTML element to quickly and easily adjust its appearance and layout. Utility classes follow the BEM (Block Element Modifier) naming convention, which makes them easy to read and understand. Utility classes can help the designer to create visual consistency across the Lightning components and pages, without writing custom CSS or overriding the component blueprints. References: : Utility Classes | Lightning Design System : UX Designer Certification Prep: Designing with Lightning Design System | Trailhead

A heuristic evaluation is a usability inspection method that involves having evaluators examine a user interface and assess its compliance with established usability principles (or “heuristics”). These heuristics are guidelines or rules of thumb that help identify common usability problems. During a heuristic evaluation, evaluators inspect the interface and identify potential usability issues based on the heuristics. The evaluators then report their findings to the designers or developers, who can use this feedback to improve the interface. Heuristic evaluation is a cost-effective and efficient way to identify usability problems early in the design process. It can be done quickly and does not require large groups of participants. It is particularly useful for identifying problems that may not be detected through user testing or surveys1.

A heuristic evaluation is the most suitable method for determining the portal’s compliance with recognized standard usability principles, such as Nielsen’s 10 heuristics for user interface design2. These heuristics cover aspects such as visibility of system status, match between system and the real world, user control and freedom, consistency and standards, error prevention, recognition rather than recall, flexibility and efficiency of use, aesthetic and minimalist design, help users recognize, diagnose, and recover from errors, and help and documentation. By applying these heuristics to the portal, the UX team can identify and prioritize the usability problems that need to be fixed.

An intuitive review is a less formal and less rigorous method of usability inspection, where an evaluator relies on their own intuition and experience to judge the usability of an interface. An intuitive review does not follow a set of predefined heuristics or criteria, and it is more subjective and prone to bias. An intuitive review can be useful for getting a quick overview of the interface, but it is not as reliable or comprehensive as a heuristic evaluation3.

User testing is a usability evaluation method that involves observing and collecting data from actual or potential users as they perform tasks with the interface. User testing can provide valuable insights into how users interact with the interface, what difficulties they encounter, and what their preferences and expectations are. User testing can also measure the effectiveness, efficiency, and satisfaction of the interface. However, user testing is not the best method for determining the compliance with standard usability principles, as it does not directly assess the interface against the heuristics. User testing is also more time-consuming, resource-intensive, and complex to conduct than heuristic evaluation4.

The Salesforce Lightning Design System (SLDS) is a collection of design guidelines, resources, and tools that help create consistent, beautiful, and accessible user experiences across the Salesforce platform1. Component blueprints are one of the key resources that the SLDS provides. They are framework-agnostic, accessible HTML and CSS code snippets that can be used to create UI elements such as buttons, cards, menus, and more2. A UX Designer who is asked to design a new application built on Salesforce should become familiar with the SLDS component blueprints as their first step, because they can help them to3:

Understand the structure, behavior, and appearance of the standard Salesforce components and how they can be customized or extended.

Follow the SLDS design principles and best practices, such as clarity, efficiency, consistency, and beauty.

Ensure that the application is responsive, adaptive, and compatible with different devices and screen sizes.

Leverage the SLDS design tokens, icons, and utilities to create a coherent and scalable visual language.

Reduce the development time and effort by reusing the existing code and avoiding duplication.

The other options are not the best first steps for a UX Designer who is asked to design a new application built on Salesforce. Creating branding sets for each audience using Experience Builder is a later step that involves applying the visual identity and style of the application to different user segments and channels4. Finding and reviewing relevant AppExchange packages is a research step that can help to identify existing solutions or features that can be integrated or adapted to the application5. Designing a series of custom web components for the app is a development step that can be done after defining the requirements, wireframes, and prototypes of the application.

 Screen flow is a Salesforce functionality that allows the UX Designer to create interactive workflows for the users with just a few clicks. With screen flow, the UX Designer can create step-by-step workflows that include screens for data entry, decision points based on user input, and automated actions based on their responses. Screen flow can make the user experience more engaging by presenting the users with what they need, when they need it, and using their input to guide them and automate their tasks. Screen flow can also be customized and embedded in various ways, such as on a Lightning page, a button, a utility bar, or an Experience Cloud page123

Lightning Survey is a Salesforce functionality that allows the UX Designer to create and distribute surveys to collect feedback from customers, employees, or partners. Lightning Survey is not suitable for creating complex processes or workflows, but rather for measuring satisfaction, loyalty, or engagement4

Process Builder is a Salesforce functionality that allows the UX Designer to create and automate business processes without code. Process Builder can perform actions based on criteria, such as updating records, sending emails, or invoking flows. Process Builder is not suitable for creating interactive workflows with screens, but rather for automating background tasks5

The best onboarding design practice for Cloud Kicks would be to identify the message, audience, and purpose for content. This would help them tailor the content to the different needs and preferences of their employees, and provide them with the most relevant and useful information. Providing written help documentation as the single source of truth for learning about new features (A) might not be engaging or effective for all users, especially those who prefer visual or interactive learning. Creating pop-ups to give users a full visualization of a product © might be intrusive or overwhelming for some users, and might not explain the benefits or features of the product clearly. Identifying the message, audience, and purpose for content (B) is a key step in creating user-centered onboarding design, as it helps to define the goals, scope, and tone of the content, and to align it with the user’s needs, expectations, and motivations. References:

[UX Designer Certification Prep: Onboarding Design]

[UX Designer Certification Prep: Content Strategy]

[Salesforce Certified User Experience Designer Exam Guide]

The alternative (alt) text is a short block of text that describes the content and function of an image or other non-text element on a web page. The alt text is read aloud by screen readers and other assistive technologies to provide access to people who cannot see the image. The alt text also helps with search engine optimization and displays on the page if the image fails to load1.

When designing a custom component that includes a clickable icon in a Lookup field, the alt text should be concise, descriptive, and meaningful. The alt text should convey the purpose and action of the icon, rather than its appearance or format. Therefore, the best option for the alt text of the icon is “Search button”, as it describes what the icon does and how the user can interact with it. The other options are not suitable for the alt text, as they either include unnecessary words, such as “image of” or “photo of”, or omit important information, such as “button”. For example, the option “Image of a search button” is redundant, as the screen reader will already announce that the element is an image. The option “Search” is incomplete, as it does not indicate that the element is a button that can be clicked. The option “Image of a magnifying glass” is irrelevant, as it describes the appearance of the icon, rather than its function.

A formula field is a custom field that calculates a value based on a formula expression. A formula field can display text, numbers, dates, or images. A formula field can use the IMAGE function to display an image from a URL. A formula field can be added to an object page layout to show the image on the record detail page1.

A static resource is a file or a collection of files that can be uploaded to Salesforce and referenced in a formula field, a Visualforce page, a Lightning component, or a web tab. A static resource can store images, style sheets, JavaScript, or other files. A static resource can be used to store the custom image that Cloud Kicks wants to display on the record detail page2.

An object page layout is a configuration of fields, buttons, related lists, and other components on a record detail page. An object page layout can be customized to show different information for different users, based on their profiles or record types. An object page layout can be used to add the formula field that displays the custom image to the record detail page3.

These platform tools can be used to achieve the requirement of adding a custom image to a record detail page, making it easier for Cloud Kicks to visually identify its current membership level. For example, the formula field can use the IMAGE function to display the custom image from the static resource, based on the value of another field that indicates the membership level. The object page layout can then include the formula field on the record detail page for the relevant users.

Image field is a custom field that allows users to upload and display images on a record. Image field can be used to show images on a record detail page, but it is not suitable for Cloud Kicks’ requirement, because it does not allow the image to be determined by a formula expression. Image field requires the user to manually upload the image for each record, which is not efficient or consistent4.

Dynamic form is a feature that allows admins to add, group, and reorder fields and sections on a Lightning record page using the Lightning App Builder. Dynamic form can be used to create flexible and dynamic page layouts that can adapt to different contexts and scenarios. Dynamic form also supports visibility rules, which can be used to show or hide fields or sections based on filters or conditions. However, dynamic form is not a platform tool that can be used to display a custom image on a record detail page, as it does not affect the content or functionality of the fields. Dynamic form can only be used to configure the layout of the fields, not the values or images of the fields5.

Lightning components are reusable units of user interface that can be used to build Lightning pages and applications. Lightning components can be built using HTML, CSS, JavaScript, and Apex. Lightning components can display data, images, icons, charts, buttons, or other elements on a Lightning page. SLDS icons are icons from the Salesforce Lightning Design System that can be used in Lightning components to represent actions, objects, or concepts. Compact layouts are page layouts that show a record’s key fields at a glance in the highlights panel, the list view, the Related tab, and other places. Compact layouts can be used to customize which fields are displayed in these places6.

Lightning components, SLDS icons, and compact layouts are platform tools that can be used to display images on a Lightning page, but they are not the best option for Cloud Kicks’ requirement, because they are more complex and require more development skills than a formula field, a static resource, and an object page layout. Lightning components also require more maintenance and testing than formula fields. SLDS icons are predefined icons that may not match the custom image that Cloud Kicks wants to display. Compact layouts are not relevant for displaying images on a record detail page, as they only affect the highlights panel and other places6.

These three features allow fields to be available when viewing a record in Salesforce.

A highlights panel displays key fields at the top of a record page in Lightning Experience. It can be customized to show the most important information for each object.

A compact layout determines which fields appear in the highlights panel, the list view hover, and the Salesforce app. It can be assigned to different record types and profiles.

A list view displays a set of records that meet specified filter criteria. It can be sorted and filtered by different fields, and users can select which fields to display in the list view.

The Salesforce Lightning Design System (SLDS) is a collection of design guidelines, components, and resources that enable developers and designers to build consistent, high-quality, and responsive user interfaces across the Salesforce platform. The SLDS provides UI kits and plugins for popular design and prototyping tools, such as Sketch, Adobe XD, and Figma, that allow designers to quickly create mockups and wireframes using the SLDS components and styles. By leveraging the SLDS, the designer can accelerate the visual design process and ensure alignment with the Salesforce brand and best practices. References:

[Salesforce Lightning Design System]

[UI Kits and Plugins]

[UX Designer Certification Prep: Visual Design]

 A diary study is a research methodology that involves asking participants to record their thoughts, feelings, behaviors, and activities over a period of time, usually in response to prompts or questions from the researcher1. A diary study is suitable for Cloud Kicks (CK) to conduct discovery phase research to understand more about the customers’ purchasing habits, as it will allow them to remotely observe customers’ buying patterns over the course of a 2-month period. A diary study will also provide rich and contextual data on the customers’ needs, preferences, motivations, and pain points, as well as the factors that influence their purchasing decisions1. References: Salesforce User Experience Designer Exam Guide, Diary Studies: How to Conduct from Start-to-Finish

The users can improve their end-user experience by favoriting the often used object and personalizing the navigation bar. Favoriting the object allows the users to access it quickly from the Favorites menu in the header. Personalizing the navigation bar allows the users to add, remove, or reorder the items that they use frequently. These features do not require the administrator to create a new app or modify the existing one, and they can be customized by the users themselves according to their preferences and needs. References:

[Salesforce Certified User Experience Designer Exam Guide], Section 3.1: Design and implement solutions that meet user needs

[UX Designer Certification Prep: User-Centered Design], Unit 4: Design for User Needs

[Prepare for Your UX Designer Credential], Trailmix: User-Centered Design

[Salesforce Help: Favorites in Lightning Experience]

[Salesforce Help: Personalize Your Navigation Bar]

According to the Web Content Accessibility Guidelines (WCAG), which are the leading international standards for accessible web design, perceivable content is content that can be presented to users in ways they can perceive. This means that the content should be available to the senses (vision, touch, and hearing) either through the browser or through assistive technologies like screen readers, screen enlargers, and others1. Therefore, the content should only be visible is the correct answer, as it implies that the content can be seen by users who rely on vision to access the web. The other options are incorrect, as they suggest that the content is not perceivable to all users.

 To implement a brand style guide using out-of-the box Experience Builder features, the best option is to apply brand fonts and colors. This can be done by using themes and branding sets in Experience Builder. Themes are collections of information that define the visual flow of a site, such as colors, fonts, and spacing. Branding sets are groups of assets that can be applied to a theme, such as logos, images, and icons. By using themes and branding sets, CK can customize the look and feel of their site without coding or using a different template. References: Add Style to Your Experience Builder Site with Themes, Use Branding Sets in Experience Builder

 The best way to apply branding to a Salesforce org using Lightning Experience is to create a custom theme in Themes and Branding. Themes and Branding is a feature that allows the administrator to customize the look and feel of Salesforce to match the branding of the organization. The administrator can add logos, default images, and colors to the theme. The administrator can also choose one of the built-in Salesforce themes, or create their own custom themes with just a few clicks. To create a custom theme, from Setup, enter Themes and Branding in the Quick Find box, then select Themes and Branding. Click New Theme and upload the logo, brand colors, and images that follow the company design guidelines. The administrator can also preview and activate the theme for the entire org 1. References: [Brand Your Org in Lightning Experience] (https://help.salesforce.com/s/articleView?id=sf.brand_your_org_in_lightning_experience.htm &language=en_US&type=5)

The three inclusive design action-oriented principles are:

Recognize exclusion: Identify and understand the barriers that prevent people from accessing or using a product or experience. Exclusion can be caused by ability, context, or personal factors.

Learn from diversity: Seek out and learn from the perspectives of people who have a range of experiences, backgrounds, and identities. Diversity can be a source of inspiration and innovation.

Solve for one, extend to many: Design solutions that address the needs of a specific person or group, and then generalize them to benefit a wider audience. Solving for one can reveal hidden opportunities and create more inclusive outcomes. References: Explore Inclusive Design, Inclusive Design

The Salesforce Lightning Design System (SLDS) reflects the patterns and components that underpin the Salesforce product. These patterns and components provide a unified language and consistent look and feel when designing apps and products within the Salesforce ecosystem. The Lightning Experience UI, which SLDS represents, was crafted using four core design principles. We encourage you to keep them in mind as you develop your applications. They are1:

Clarity — Eliminate ambiguity. Enable people to see, understand, and act with confidence.

Efficiency — Streamline and optimize workflows. Intelligently anticipate needs to help people work better, smarter, and faster.

Consistency — Create familiarity and strengthen intuition by applying the same solution to the same problem.

Beauty — Demonstrate respect for people’s time and attention through thoughtful and elegant craftsmanship. References: Introduction to the Salesforce Lightning Design System

The Salesforce Lightning Design System (SLDS) provides component blueprints that will ensure consistency for Cloud Kicks’ functional components. Component blueprints are ready-to-use HTML and CSS UI elements that provide the foundation for Salesforce experience development. They follow the design guidelines, accessibility standards, and best practices of Lightning Experience. They also include variants, states, and modifiers to handle different use cases and scenarios. By using component blueprints, Cloud Kicks can create functional components that are consistent with the look and feel of Lightning Experience without writing custom code or CSS. References:

Component Blueprints

Introduction to the Salesforce Lightning Design System

 When the organization-wide default for Accounts is private, users can only access the accounts they own or are explicitly shared with them. However, when the organization-wide default for Opportunities is private, users can access the opportunities they own, are explicitly shared with them, or are associated with accounts they can access1. Therefore, when ownership-based sharing rules are created for each team to grant access to opportunities owned by their team members, the sales reps on the same team will also have Read access to the accounts for those opportunities. This is because the sharing rules for opportunities automatically grant access to the parent accounts2. However, the sales reps will not have Edit access to the accounts, unless the sharing rules specify Full Access for the opportunities3. The sales reps will also not have access to all accounts or all opportunities, only those that are owned by their team members or themselves. References: Sharing Records Owned by High-Volume Portal Users | Salesforce Security Guide, Sharing Rules | Salesforce Security Guide, Create Owner-Based Sharing Rules | Salesforce Security Guide

The SLDS Validator extension for VS Code is a tool that simplifies working with the Salesforce Lightning Design System (SLDS) in Aura and Lightning components. It provides code completion, syntax highlighting, and validation with recommended tokens and utility classes. It also scans the markup and validates it against a database of guidelines, tips, and best practices extracted from the SLDS documentation. It offers suggestions on how to improve the code and avoid conflicts with SLDS12. References: SLDS Validator - Visual Studio Marketplace, SLDS Validator for VS Code - Lightning Design System