Salesforce User-Experience-Designer Salesforce Certified User Experience Designer (SU24) Exam Practice Test

Accordions are collapsible sections that can be used to separate different content areas. By using accordions, users can quickly navigate through the page and easily find thecontent that they need. The use of accordions also ensures that screen readers can access the content within each section, reducing the need for additional navigation. Additionally, a Lightning Console layout can be used to organize components, but this layout is optimized for customer service agents and not necessarily for screen reader users. Placing components in adjacent tabs or stacking them on the same page can make the page difficult to navigate and can make it difficult for screen readers to understand the page. For more information, see the Salesforce Accessibility Guide (https://help.salesforce.com/articleView?id=accessibility_overview.htm &type=5).

 According to the Salesforce Lightning Design System, accordions are a good way to organize components on a page for screen reader-assisted accessibility. Accordions allow users to expand and collapse sections of content, which can help reduce cognitive load and scrolling. Accordions also provide a clear heading structure and keyboard navigation for each section1. The other options are not recommended for screen reader-assisted accessibility, as they can create confusion, clutter, or inefficiency for users who rely on auditory feedback. For example, switching to a Lightning Console layout can make it harder for users to navigate between tabs and subtabs2. Placing components in adjacent tabs can also increase the number of keystrokes and commands needed to access the information3. Stacking components on the same page can create a long and overwhelming page that requires excessive scrolling and reading4.

References: Accordions - Lightning Design System, Lightning Console Apps - Salesforce Help, Tabs - Lightning Design System, Accessibility Standards - Salesforce Help

 Two best practices that should be considered when using a custom Lightning component to fulfill a specific business requirement are:

• Find the closest Salesforce Lightning Design System (SLDS) Blueprint to help inform the custom Lightning component. The SLDS is a collection of design guidelines, UI components, and code samples that help you create consistent and beautiful user interfaces for Lightning applications. The SLDS Blueprints are examples of common UI patterns and components that are built with the SLDS and follow the design principles and best practices. The Blueprints can help you inform the custom Lightning component by providing inspiration, guidance, and code snippets that you can modify and reuse. The Blueprints can also help you ensure that the custom Lightning component is compatible and consistent with the rest of the Lightning application and the Salesforce platform. [UX Designer Certification Prep: Salesforce Design System], Lightning Design System Website
• Exhaust the list of available base Lightning components in the Component Library. The base Lightning components are a set of pre-built UI components that you can use to create custom Lightning components. The base Lightning components are built with the SLDS and provide the functionality and interactivity that you need for common UI elements, such as buttons, icons, forms, tables, charts, and more. The base Lightning components also handle the accessibility, security, and performance aspects for you, so you don’t have to worry about them. The Component Library is a reference guide that provides documentation and examples for the base Lightning components, as well as other Lightning web components and Aura components. The Component Library can help you explore the list of available base Lightning components and see how they work and how to use them. The Component Library can also help you avoid reinventing the wheel and save time and effort by using the base Lightning components as much as possible, and only creating custom Lightning components when there is no suitable base Lightning component for your requirement. [UX Designer Certification Prep: User Testing and Evaluation], Developer Center’s Lightning Component Library

Prioritizing Aura markup even if there is a Lightning Web Component (LWC) available, and creating HTML markup and linking the SLDS stylesheet via static resource are not best practices that should be considered when using a custom Lightning component to fulfill a specific business requirement. These practices can lead to suboptimal performance, maintainability, and compatibility issues for the custom Lightning component. Aura markup is the older syntax for creating Aura components, which are the predecessor of Lightning web components. Lightning web components are the newer and faster way of creating custom UI components for Lightning applications, using modern web standards and best practices. Lightning web components also have better interoperability and compatibility with Aura components and other web components, as well as with the base Lightning components and the SLDS. Therefore, it is recommended to use Lightning web components over Aura components whenever possible, and to use LWC markup instead of Aura markup for creating custom Lightning components. [UX Designer Certification Prep: User Testing and Evaluation], Lightning Web Components Developer Guide

Creating HTML markup and linking the SLDS stylesheet via static resource is also not a recommended practice for creating custom Lightning components, because it can create unnecessary complexity and duplication for the custom Lightning component. A static resource is a file or a collection of files that can be referenced by a Lightning component, such as images, style sheets, JavaScript libraries, or fonts. However, linking the SLDS stylesheet via static resource means that you have to manually download and upload the SLDS files to your org, and update them whenever there is a new version of the SLDS. This can create maintenance and compatibility issues for the custom Lightning component, as

An App Builder styling property is a feature that allows a Lightning web component to expose CSS properties that can be set by an administrator in the Lightning App Builder. This way, the administrator can customize the look and feel of the component depending on the context and use case. For example, a component can have a styling property for the background color, the font size, or the border radius. The administrator can then change these values in the App Builder without modifying the code of the component. References:

• [Create App Builder Styling Properties]

The Salesforce Navigation Setup mode allows the administrator to customize the navigation menu and navigation bar of the Salesforce mobile app using the Mobile Only app. The administrator can select the Lightning pages, Visualforce pages, Lightning components, and other productivity items that they want to appear in the navigation menu and navigation bar. The administrator can also reorder the navigation items and create tabs for them. To customize navigation items, in the Quick Find box, enter Navigation, and select Salesforce Navigation 1. Visualforce pages and Lightning pages can be included in the navigation menu and navigation bar of the Salesforce mobile app, as long as they have tabs created for them. To create a tab, from Setup, enter Tabs in the Quick Find box, and select Tabs 1. References: [Customize the Mobile Only Navigation Menu in the Salesforce Mobile App] (https://help.salesforce.com/s/articleView?id=sf.salesforce_app_customize_nav_menu.htm &language=en_US&type=5)

CK’s customers can engage in the following three ways using the out-of-box functionality of Experience Cloud:

• Endorsement of skills and expertise: Customers can endorse each other’s skills and expertise on their profiles, which helps to build trust and credibility within the community.
• Join affinity groups: Customers can join groups based on their interests, preferences, or needs, which allows them to connect with like-minded people and share relevant information.
• Recognize peers with badges: Customers can recognize each other’s contributions and achievements by awarding badges, which helps to motivate and appreciate the community members. References:
• : Endorse Skills and Expertise
• : Create and Manage Groups
• : Award Badges to Recognize Members

Personalized Navigation Tabs are a navigational feature that allows the users to customize the navigation bar of the Salesforce mobile app with the items that they use most frequently. Users can add, remove, and reorder the tabs in the navigation bar, and access them with a single tap. Users can also mark their favorite items with a star icon, and access them from the Favorites tab. Personalized Navigation Tabs can help Cloud Kicks (CK) employees to quickly access the apps, objects, and other items that they need in the Salesforce mobile app12

• Console Navigation is a navigational feature that allows the users to work with multiple records and objects on a single screen in the Salesforce desktop app. Console Navigation is not available in the Salesforce mobile app, and it is not suitable for providing quick access to apps, objects, and other items3
• Utility Bar is a navigational feature that allows the users to access common productivity tools, such as notes, history, or macros, from a fixed footer at the bottom of the Salesforce desktop app. Utility Bar is not available in the Salesforce mobile app, and it is not suitable for providing quick access to apps, objects, and other items4

References:

• Personalize Your Navigation Bar in the Salesforce Mobile App - Salesforce Help
• Personalize Your Navigation Bar in the Salesforce Mobile App Unit | Salesforce Trailhead
• Console Navigation - Salesforce Help
• Utility Bar - Salesforce Help

 A UX designer’s role is not only to design solutions, but also to facilitate collaboration and communication among stakeholders and users. A clear, consistent sales process is essential for Salesforce adoption, as it defines the steps and actions that sales representatives need to take to close deals. Without a common understanding of the sales process, the UX designer cannot design a Salesforce solution that meets the needs and expectations of the users and the business. Therefore, the designer should conduct a workshop with stakeholders to align on the current state and build consensus on the desired future state. A workshop is an interactive session where the designer can use various techniques, such as journey mapping, persona creation, user stories, and prioritization, to elicit the pain points, goals, and requirements of the stakeholders and users. A workshop can also help the designer to establish trust and rapport with the participants, and to gain their buy-in and feedback for the proposed solution12. References: Salesforce Adoption Strategies | Salesforce Trailhead, 6 Guiding Principles to Maximize Your Salesforce Adoption | Salesforce Admins

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.

References:

• Grid - Lightning Design System, Grid - Lightning Design System Grid HTML/CSS: Dev Ready Responsive Terms of Service Privacy Responsible Disclosure Trust Cookies Settings Your Privacy Choices © Copyright 2015-present Salesforce, Inc. All rights reserved. Various trademarks held by their respective owners.
• Breakpoints - Lightning Design System, Breakpoints - Lightning Design System Breakpoints HTML/CSS: Dev Ready Responsive Terms of Service Privacy Responsible Disclosure Trust Cookies Settings Your Privacy Choices © Copyright 2015-present Salesforce, Inc. All rights reserved. Various trademarks held by their respective owners.
• Grid - Lightning Design System, Grid - Lightning Design System Grid HTML/CSS: Dev Ready Responsive Terms of Service Privacy Responsible Disclosure Trust Cookies Settings Your Privacy Choices © Copyright 2015-present Salesforce, Inc. All rights reserved. Various trademarks held by their respective owners.
• Grid - Lightning Design System, Grid - Lightning Design System Grid HTML/CSS: Dev Ready Responsive Terms of Service Privacy Responsible Disclosure Trust Cookies Settings Your Privacy Choices © Copyright 2015-present Salesforce, Inc. All rights reserved. Various trademarks held by their respective owners.
• Design Principles - Lightning Design System, Design Principles - Lightning Design System Design Principles HTML/CSS: Dev Ready Responsive Terms of Service Privacy Responsible Disclosure Trust Cookies Settings Your Privacy Choices © Copyright 2015-present Salesforce, Inc. All rights reserved. Various trademarks held by their respective owners.

 An Enablement Site is a custom-branded site that allows users to access learning content, such as modules, trails, and trailmixes, from Trailhead. It also allows admins to create and assign custom modules that are specific to their organization’s needs and goals. An Enablement Site can be used to gamify the learning experience by adding badges, points, and leaderboards. An Enablement Site can also provide analytics and reports on the learners’ progress and performance. Therefore, an Enablement Site is the best option for Cloud Kicks to create a gamified learning content for its internal users and leadership, as well as a custom product training. References:

• [Trailhead: Enablement Site Basics]
• [Trailhead: Create Custom Modules for Your Enablement Site]
• [Trailhead: Gamify Your Enablement Site]

Inclusive design and accessible design are both important aspects of creating products and services that are usable and enjoyable for everyone, regardless of their abilities, preferences, or contexts. However, they are not the same thing. Inclusive design is a methodology that involves designing with and for people who have a range of diverse needs and experiences. Inclusive design aims to create solutions that are not only accessible, but also equitable, respectful, and empowering for all users12. Accessible design is based on guidelines that help ensure that products and services can be perceived, understood, operated, and interacted with by people with disabilities. Accessible design follows standards such as the Web Content Accessibility Guidelines (WCAG), which provide technical specifications and best practices for making web content accessible34. Inclusive design and accessible design are not mutually exclusive, but rather complementary. Inclusive design can help inform accessible design by providing insights and feedback from diverse users and stakeholders. Accessible design can help support inclusive design by providing a baseline of quality and compliance for products and services. By applying both inclusive design and accessible design, UX designers can create more inclusive, accessible, and delightful experiences for everyone. References: Inclusive Design & Accessibility – Salesforce Designer – Medium, Product Accessibility and Inclusive Design - Salesforce.com, Learn the Elements of an Accessible Webpage Unit | Salesforce Trailhead, How Can Tech Be More Inclusive? Salesforce’s New VP of Accessibility & Inclusive Design Offers Answers - Salesforce News, [Designing for Web Accessibility Unit | Salesforce Trailhead]

The best way to store the information of Cloud Kicks’ storage facilities in Salesforce is to use objects to represent storage facilities and fields to store facility details. This is because objects and fields in Salesforce are analogous to database tables and columns, respectively1. Each object contains a set of fields that store data values, and each record is an instance of an object1. Therefore, if Cloud Kicks wants to store the same information that they have in their Excel sheet, they can create a custom object called Storage Facility, and add fields for each detail that they want to track, such as location, capacity, inventory, and so on. Then, they can create records for each storage facility and populate the fields with the corresponding data. This way, they can store and manage their data in a structured and consistent way, and leverage the features and benefits of Salesforce, such as reports, dashboards, automation, and security23.

Using objects to represent facility details and fields to store storage facilities is not a valid option, as it does not make sense to use objects as data values. Objects are meant to represent entities or concepts, not attributes or properties1. Using objects to represent both storage facilities and facility details is also not a good option, as it would create unnecessary complexity and redundancy in the data model. Objects can be related to each other through various types of relationships, such as lookup, master-detail, or many-to-many4. However, in this case, there is no need to create a separate object for each facility detail, as they are not independent entities, but rather characteristics of the storage facilities. Creating a separate object for each detail would also require creating more fields, records, and relationships, which would increase the maintenance and storage costs, and reduce the performance and usability of the system5. References:

• Learn All About Objects and Fields in Salesforce - Forcetalks
• Mastering Salesforce CRM Administration - Packt Subscription
• Overview of Salesforce Objects and Fields
• Object Reference for the Salesforce Platform
• Understand Custom & Standard Objects Unit | Salesforce Trailhead

Themes and branding allow Salesforce app developers to customize the look and feel of their apps to match their company’s branding and accessibility standards. One of the features of themes and branding is the ability to select a brand color, which is the primary color used for buttons, links, and highlights. Salesforce automatically generates a color palette based on the brand color, which includes accessible colors that meet the WCAG 2.1 contrast ratio guidelines. This ensures that the app is visually appealing and accessible to users with different color vision abilities. Developers can also customize other aspects of the theme, such as the logo, page background, and default font. References: [Themes and Branding Basics], [Accessibility in Salesforce]

 A service-blueprinting workshop is a process that involves mapping out the flow of a service, identifying the touchpoints, actors, processes, and systems that are involved, and highlighting the pain points and opportunities for improvement. A service-blueprinting workshop is a collaborative and creative way to redesign services with stakeholders, as it allows them to see the big picture, empathize with the users, and co-create solutions. A service-blueprinting workshop is suitable for Cloud Kicks (CK) after they have finished conducting research and synthesizing the findings, as it will help them address the issues uncovered in the study and design better service experiences for their customers. References: Service Design Service Blueprints, How to create a service blueprinting facilitation guide, Workshop exercise: Service Blueprint

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

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]

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.

References:

• Standard Objects
• Leads and Opportunities
• Contacts

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.

References: Everything you need to know to write effective alt text and Write helpful Alt Text to describe images

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

According to the Web Content Accessibility Guidelines (WCAG) 2.1, the minimum color contrast ratio for normal text is 4.5:11. This means that the difference in brightness (luminance) between the text color and the background color should be at least 4.5 times. This ensures that the text is readable by people with moderately low vision, color deficiencies, or contrast sensitivity1. The contrast ratio can be calculated using the formula:

L2​+0.05L1​+0.05​

where L1​ is the relative luminance of the lighter color and L2​ is the relative luminance of the darker color2. The relative luminance is a value between 0 and 1, where 0 is black and 1 is white2. The contrast ratio can range from 1:1 (white on white) to 21:1 (black on white)2.

The contrast ratio requirement for normal text is lower for larger text or bold text, as they are easier to read at lower contrast. For large text (18 point or 14 point bold), the minimum contrast ratio is 3:11. For graphics and user interface components, such as form input borders, the minimum contrast ratio is also 3:13. For level AAA conformance, the minimum contrast ratio for normal text is 7:1 and for large text is 4.5:11.

To evaluate the color contrast ratio of a site, there are various tools available, such as the Contrast Checker or the Contrast Ratio tool. These tools allow users to enter the text color and the background color and see the contrast ratio and whether it meets the WCAG guidelines. They also provide suggestions for improving the contrast ratio if needed.

References:

• Understanding Success Criterion 1.4.3: Contrast (Minimum)
• Contrast Ratio - WCAG Color Contrast Checker
• WebAIM: Contrast Checker
• WCAG: Accessible colour and contrast ratios
• Contrast ratio - WCAG WG

Einstein Bots and Automated Invitations are two Salesforce features that can boost engagement on Cloud Kicks’ website. Einstein Bots are chatbots that can provide automated and personalized responses to customers’ questions and requests on the website. They can also escalate complex cases to human agents, collect feedback, and provide recommendations. Einstein Bots can help Cloud Kicks to improve customer satisfaction, reduce wait times, and increase conversions 1. Automated Invitations are pop-up messages that invite website visitors to start a chat or video call with a service agent. They can be triggered by various criteria, such as time spent on the website, page visited, or customer profile. Automated Invitations can help Cloud Kicks to proactively engage with potential customers, offer assistance, and generate leads 2. References: [Einstein Bots Basics] (https://ascendix.com/blog/salesforce-sales-engagement/), [Set Up Automated Chat Invitations] (https://bing.com/search?q=Salesforce+features+to+boost+engagement)

 A responsive user interface is a type of user interface that adapts to different screen sizes, resolutions, orientations, and devices, such as desktops, laptops, tablets, and smartphones. It uses flexible layouts, grids, images, and media queries to optimize the user experience and ensure usability, accessibility, and performance across different devices. A responsive user interface can help Cloud Kicks create a site for its customers to manage events regardless of the device they are using, as it can provide a consistent and seamless experience that meets the user needs and expectations. A responsive user interface can also reduce the development and maintenance costs and efforts, as it can use the same code base and content for different devices, rather than creating separate versions for each device. References:

• : User Experience Designer Certification Prep: Module 5: Design User Interfaces
• : User Experience Designer Certification Prep: Module 7: Implement User Interfaces
• : What is Responsive Web Design?

To create a site for its customers to manage events regardless of the device they are using, Cloud Kicks should use the best practice of creating a responsive user interface. A responsive user interface is one that adapts to the screen size and orientation of the device, providing an optimal viewing and interaction experience for the user. A responsive user interface can use the same code base and content for different devices, reducing the development and maintenance costs and ensuring consistency and accessibility. A responsive user interface can also leverage the features and capabilities of the device, such as touch, gestures, camera, etc., to enhance the user experience.

References:

• : Responsive User Interface

A usability study is a method of evaluating how easy and intuitive a product or service is to use by observing real users performing specific tasks. It can help identify usability issues, user needs, and user satisfaction. One of the first steps when planning a usability study is to define the goals of the study, which are the questions that the UX designer wants to answer or the hypotheses that they want to test. The goals of the study will guide the selection of the participants, the tasks, the metrics, and the methods of the study. For example, if the goal of the study is to find out how users navigate the Experience Cloud site, the UX designer might choose to use a task-based usability test with eye-tracking and think-aloud techniques. References:

• : User Experience Designer Certification Prep: Module 4: Analyze User Research Data
• : User Experience Designer Certification Prep: Module 6: Validate User Interfaces

Adding section headers to a form can improve its readability by breaking it into logical chunks and providing context for the users. Section headers can also help users scan the form and find the information they need faster. Section headers can also reduce the cognitive load and increase the completion rate of the form . References:

• : Salesforce Certified User Experience Designer Exam Guide, Section 3.2: Design for readability and clarity
• : UX Designer Certification Prep: Design for Readability and Clarity, Unit 2: Design for Readability and Clarity

This allows users to quickly scan the form and identify the relevant fields, reducing the cognitive load and improving the overall user experience. Salesforce documentation statesthat “by grouping related fields into sections, you can make your forms easier to read and understand” [1].

[1] https://help.salesforce.com/articleView?id=forms_design_best_practices.htm &type=5

The approach that is being followed by the UX Designer is the Human-Centered Design. This is a creative design approach that focuses on understanding the end-user’s needs, problems, and context, and then creating solutions that are desirable, feasible, and viable for them. The Human-Centered Design process typically involves four phases: empathize, define, ideate, and prototype.

References:

• : Human-Centered Design
• : Empathize, Define, Ideate, Prototype

 Inviting developers to user testing is a good way to help them see the value of the design changes and understand the user needs and pain points. User testing is a method of evaluating a product or service by observing how real users interact with it and collecting feedback. By witnessing the user testing sessions, developers can see how the design changes improve the user experience, such as increasing usability, satisfaction, engagement, or conversion. User testing can also help developers empathize with the users and collaborate better with the designer. References:

• [User Testing]

The Web Content Accessibility Guidelines (WCAG) are a set of standards that aim to make web content more accessible to people with disabilities. The WCAG are organized by four principles, which state that content must be:

• Perceivable: Users must be able to perceive the information and user interface components in ways they can sense, such as through sight, hearing, or touch.
• Operable: Users must be able to interact with the user interface components and navigate the content using various input methods, such as keyboard, mouse, voice, or gesture.
• Understandable: Users must be able to comprehend the information and the operation of the user interface, which means that the content must be clear, consistent, and predictable.
• Robust: Users must be able to access the content using a wide range of technologies, including different browsers, devices, and assistive tools, which means that the content must be compatible with current and future web standards. References: WCAG 2 Overview, Understanding the Web Content Accessibility Guidelines

Typography, color, and imagery are visual design elements that can be used to create a consistent and recognizable corporate style and branding. Typography refers to the choice and use of fonts, sizes, weights, and spacing to convey meaning and hierarchy. Color refers to the selection and application of hues, shades, tints, and tones to create contrast, harmony, and mood. Imagery refers to the use of photos, illustrations, icons, and graphics to communicate messages, concepts, and emotions.

References:

• [Salesforce Certified User Experience Designer Exam Guide], Section 2.3: Demonstrate knowledge of visual design principles and best practices.
• [UX Designer Certification Prep: Visual Design], Unit 2: Typography, Color, and Imagery.

 To restyle a Lightning Experience model to meet brand guidelines, the designer should use design tokens and find the appropriate component blueprint. Design tokens are variables that store visual design attributes, such as colors, fonts, and spacing. They allow the designer to customize the appearance of Lightning components without writing any code. Component blueprints are design specifications for Lightning components that provide guidance on how to use them, what properties they support, and how they behave in different scenarios. They help the designer to choose the right component for the model and apply the brand guidelines consistently. References: : Design Tokens | Salesforce Developer Guide : Component Blueprints | Lightning Design System : UX Designer Certification Prep: Designing with Lightning Components | Trailhead

 A style guide is a document that defines the visual identity and branding of a company, such as the logo, color palette, typography, iconography, imagery, and tone of voice. It helps ensure consistency and coherence across different platforms and channels, and communicates the company’s values and personality. When implementing a company’s brand on Salesforce, the style guide should be the source of truth for consistency, as it provides the guidelines and rules for applying the brand elements to the user interface. A style guide can also include a pattern library, which is a collection of reusable UI components and design patterns that follow the style guide. A design principle is a statement that expresses the core values and goals of a design process, and guides the decision making and evaluation of a design solution. The Salesforce Lightning Design System (SLDS) is a set of design guidelines and resources for creating consistent and beautiful user experiences on the Salesforce platform. It can be used as a reference and a foundation for customizing the UI according to the company’s style guide. References:

• : User Experience Designer Certification Prep: Module 5: Design User Interfaces
• : User Experience Designer Certification Prep: Module 7: Implement User Interfaces
• : What is a Style Guide and Why Every UX Designer Needs One
• : What is a Pattern Library and Why Should You Use One?

The Salesforce Lightning Design System (SLDS) is a comprehensive library of design patterns, components, and guidelines that enable developers and designers to create consistentuser interfaces on the Salesforce platform. It includes a comprehensive library of user interface components, guidelines for design consistency and accessibility, and detailed usage instructions. Using the Salesforce Lightning Design System ensures that all design elements and interactions on Salesforce use the same set of standards and patterns, resulting in a consistent and unified user experience. For more information, see the Salesforce Lightning Design System page (https://www.lightningdesignsystem.com/).

The discovery phase is a crucial stage in any UX design project, as it helps to understand the user needs, business goals, and technical constraints of the problem1. The discovery phase typically involves various research methods, such as interviews, surveys, observations, and analytics, to gather data and insights about the users and the context of use2. The outputs of the discovery phase are artifacts that synthesize and communicate the findings and insights from the research. Some of the practices that should be considered for planning out the strategy for an upcoming discovery phase are:

• Gather insight from end users: One of the main objectives of the discovery phase is to empathize with the end users and understand their goals, motivations, pain points, behaviors, and preferences. This can be done by conducting user research, such as interviews, surveys, focus groups, or usability tests, to collect qualitative and quantitative data from the target audience3. Gathering insight from end users helps to validate the assumptions and hypotheses about the problem and the solution, as well as to identify the user requirements and expectations for the design.
• Establish the research plan and timeline: Before conducting any user research, it is important to establish a clear and realistic research plan and timeline. The research plan should define the research objectives, questions, methods, participants, and deliverables. The research timeline should specify the duration, frequency, and sequence of the research activities, as well as the deadlines and milestones for the deliverables4. Establishing the research plan and timeline helps to ensure that the discovery phase is well-organized, efficient, and effective, as well as to communicate the expectations and responsibilities to the stakeholders and the team members.
• Understand the problem before moving to solutions: Another key practice for the discovery phase is to focus on understanding the problem before jumping to solutions. This means defining the problem statement, the scope, and the constraints of the project, as well as identifying the root causes, the symptoms, and the impacts of the problem. Understanding the problem before moving to solutions helps to avoid wasting time and resources on creating solutions that do not address the real needs and pain points of the users, or that are not feasible or viable for the business or the technology.

The other two options, considering platform-based before custom solutions and determining user acceptance criteria, are not practices that should be considered for planning out the strategy for an upcoming discovery phase. Considering platform-based before custom solutions is a practice that belongs to the design phase, not the discovery phase, as it involves choosing the best solution option based on the user research findings and the design principles5. Determining user acceptance criteria is a practice that belongs to the testing phase, not the discovery phase, as it involves defining the criteria that the solution must meet to be accepted by the users and the stakeholders6.

References: UX Discovery Process: A Complete Guide, UX Research Methods: How to Uncover Valuable Insight about your Users, User Research: What It Is and Why You Should Do It, How to Create a UX Research Plan, Platform-Based vs. Custom Solutions: Which One to Choose?, User Acceptance Testing (UAT): A Complete Guide

For Cloud Kicks' upcoming discovery phase, the three practices that should be considered are:

A. Understand the Problem Before Moving to Solutions: Establishing a clear understanding of theproblem and what the desired outcomes are before beginning the discovery phase is essential for successful project planning. This can be done by gathering data and insights from end users, conducting research, and understanding how the problem is currentlybeing addressed.

B. Gather Insight from End Users: Gathering insights from end users is a crucial step in the discovery phase. End users provide valuable feedback and insights into the problem and how a potential solution may work. This feedback can helpshape the overall project plan and help identify potential solutions.

C. Establish the Research Plan and Timeline: The research plan and timeline should be established before beginning the discovery phase. This should include a list of tasks to be completed, the resources needed, and a timeline for completion. This plan should be communicated to all stakeholders so everyone is aware of the project goals and timeline.

The best approach to improve the Sales team’s experience with Contact records in Sales Cloud is to run the Salesforce Optimizer App to identify fields not in use. The Salesforce Optimizer App is a free tool that scans the Salesforce org and provides a diagnostic report on the performance and health of the org1. It analyzes how the org uses various features, such as fields, triggers, layouts, profiles, reports, and more, and suggests customizations and improvements based on best practices1. By running the Salesforce Optimizer App, the Sales team can find out which fields are not being used or are redundant, and remove or hide them from the Contact record page. This way, they can simplify the page layout, reduce the page load time, and focus on the fields that are relevant to their sales activities2.

Moving all unused fields to a separate section at the bottom of the page is not a good option, as it does not solve the problem of having too many fields on the page. It would still affect the page load time and the user experience, as the users would have to scroll down to see the entire page. Moreover, it would not help the users to find the information they need, as the fields would not be organized in a logical or meaningful way3.

Implementing In-App Guidance to help users focus on the most important fields is also not a good option, as it does not address the root cause of the problem, which is having too many fields on the page. In-App Guidance is a feature that allows admins to create custom prompts and walkthroughs to guide users through tasks or processes on Salesforce Lightning pages4. It can be useful for user training, onboarding, or adoption, but it cannot replace the need for a clean and efficient page layout. In fact, having too many prompts or walkthroughs on the page can be distracting and annoying for the users, especially if they are not relevant or helpful4. References:

• Run the Salesforce Optimizer App
• Improve Your Implementation with Salesforce Optimizer
• Page Layouts
• In-App Guidance in Lightning Experience

 In-app feedback is a method of collecting user feedback within the context of the product or service, without interrupting the user’s workflow. It allows the UX designer to gather insights from a specific set of users at scale and measure their satisfaction, preferences, and pain points. In-app feedback can be implemented using various techniques, such as ratings, reviews, comments, suggestions, polls, or pop-ups . References:

• : User Experience Designer Certification Prep: Module 3: Conduct User Research
• : User Experience Designer Certification Prep: Module 4: Analyze User Research Data

 According to the Salesforce Design System guidelines for button usage, the brand button should be used for the primary action on a page or modal, such as “Save” or “Continue”. The neutral button should be used for secondary or tertiary actions, such as “Cancel” or “Back”. The brand button should have more visual weight and contrast than the neutral button, to indicate its importance and guide the user’s attention. Therefore, the best option for the Cloud Kicks custom component is to use a brand button for “Continue” and neutral buttons for “Cancel” and “Back”. References: Trailhead: Systems Design with SLDS, Salesforce Developers: Buttons, Lightning Design System: Buttons

 Diversity, inclusion, and equality in design are values that can lead to positive business outcomes, such as less employee turnover, greater market share, and economic growth. These values can help create a more inclusive and innovative workplace, where employees feel valued, respected, and engaged, and where customers feel understood, represented, and satisfied. Some of the benefits of these values are:

• Less employee turnover: Diversity, inclusion, and equality in design can reduce employee turnover by fostering a culture of belonging, trust, and collaboration, where employees can thrive and grow. According to a Salesforce report1, employees who feel a sense of belonging at work are 5.3 times more likely to feel empowered to perform their best work, and employees who feel their voice is heard at work are 4.6 times more likely to feel empowered to perform their best work. Moreover, employees who feel valued and included are more likely to stay loyal to their employer, reducing the costs and risks of hiring and training new staff.
• Greater market share: Diversity, inclusion, and equality in design can increase market share by expanding the customer base, enhancing the customer experience, and improving the brand reputation. According to a McKinsey report2, companies in the top quartile for ethnic and cultural diversity on executive teams were 36% more likely to experience above-average profitability than companies in the fourth quartile. Moreover, companies that design products and services that meet the needs and preferences of diverse customers can gain a competitive edge and increase customer loyalty and retention.
• Economic growth: Diversity, inclusion, and equality in design can contribute to economic growth by boosting productivity, innovation, and social impact. According to a World Bank report3, increasing women’s labor force participation and earnings could add $172 trillion to global wealth. Moreover, companies that leverage the diverse perspectives and experiences of their employees can generate more creative and effective solutions, and companies that support social causes and environmental sustainability can create positive change and attract more customers and investors.

References:

• [Our 2023 Annual Equality Update: Where We Are and Where We’re Going - Salesforce]1
• [Diversity wins: How inclusion matters | McKinsey]2
• [Women, Business and the Law 2020 | World Bank]3

To view the history of cases that a specific customer has submitted, the representative should go through the following hierarchy of information: All Accounts > Account Detail > Contact Detail > Case Related List. This is because cases are related to contacts, and contacts are related to accounts. By navigating from the account level to the contact level, the representative can see all the contacts associated with a specific account. Then, by selecting a contact, the representative can see the case related list, which shows all the cases that the contact has submitted or been involved in. This way, the representative can view the history of cases for a specific customer in a logical and efficient manner. References: : UX Designer Certification Prep: Designing with Service Cloud | Trailhead : Service Cloud Basics | Salesforce Help

A design thinking approach is a human-centered method for solving complex problems and creating innovative solutions. It involves understanding the needs and desires of the users, generating and testing multiple ideas, and iterating on the feedback and results. A design thinking approach can be divided into two types of thinking: divergent and convergent. Divergent thinking is the process of generating many possible solutions to a problem without judging or filtering them. It encourages creativity, exploration, and experimentation. Convergent thinking is the process of evaluating, selecting, and refining the best solution to a problem. It involves analysis, logic, and criteria. Divergent and convergent thinking are complementary and cyclical. They help the designer to expand the solution space and then narrow it down to the most feasible and desirable option. By using both types of thinking, the designer can encourage more creative problem-solving and avoid premature convergence or fixation on a single idea. Therefore, the best approach combination for the UX Designer at Cloud Kicks is divergent and convergent thinking. References: Trailhead: Design Thinking, Trailhead: Salesforce User Experience Designer Certification Prep, Divergent and Convergent Design Thinking

The UI configuration that should be used to further individualize each featured topic is to select and upload images that represent each featured topic. This option allows the UX Designer to customize the appearance of the Featured Topic component and make it more visually appealing and engaging for the users. The images can help to convey the meaning and relevance of each topic and attract the users’ attention. The images can also create a consistent and branded look for the Experience Cloud site.

References:

• : Featured Topic Component
• : Customize the Featured Topic Component

This allows users to easily distinguish between different topics and quickly scan for relevant topics. Salesforce documentation on the Featured Topics component states that “You can add a description for each featured topic, which appears in the user interface below the topic label” [1].

[1] https://help.salesforce.com/articleView?id=knowledge_articles_sites_featured_topic.htm &type=5

Audience targeting is a page layout feature that allows admins to create different versions of a Lightning page for different audiences, such as user profiles, roles, or permissions. Audience targeting can be used to control the visibility of the entire page or specific components on the page, such as tabs, fields, or sections. Audience targeting can help create personalized and relevant experiences for different types of users, and reduce the need for multiple page layouts1.

Audience targeting is the most suitable feature for the UX Designer to use in this case, because it can help them customize the Order record page layout for internal and external users, without creating separate page layouts. For example, the UX Designer can use audience targeting to show or hide certain fields, sections, or tabs based on the user’s profile or permission set. This way, the UX Designer can ensure that each user sees only the information that is relevant and appropriate for them.

Field-level security is a feature that allows admins to restrict the access and editability of fields for different users, based on their profiles or permission sets. Field-level security can help protect sensitive or confidential data, and enforce data quality and integrity. However, field-level security does not affect the visibility of fields on the page layout, only the access and editability. Field-level security also does not apply to other components on the page, such as tabs or sections2.

Dynamic forms is a feature that allows admins to add, group, and reorder fields and sections on a Lightning page using the Lightning App Builder. Dynamic forms can help create flexible and dynamic page layouts that can adapt to different contexts and scenarios. Dynamic forms also support visibility rules, which can be used to show or hide fields or sections based on filters or conditions. However, dynamic forms are not available for all standard objects, and they do not support audience targeting. Dynamic forms also do not affect the visibility of other components on the page, such as tabs34.

References: 1: Audience Targeting for Lightning Pages 2: Field-Level Security | Salesforce Security Guide - Salesforce Developers 3: Dynamic Forms Tips and Considerations - Salesforce 4: Salesforce Dynamic Forms: Overview & Deep Dive Tutorial

CK can assign learning content to employees using In-App Learning functionality in the following two ways:

• Trailmixes: Trailmixes are custom learning paths that can include modules, projects, trails, and even external links. CK can create and assign trailmixes to learners based on their roles, goals, or interests. Learners can access trailmixes from the Learning Home or the Guidance Center in Salesforce.
• Modules/Badges: Modules are units of instruction that cover specific topics and skills. Badges are earned by completing modules or projects. CK can assign modules or badges to learners to help them learn specific features or functionalities in Salesforce. Learners can access modules or badges from the Learning Home or the Guidance Center in Salesforce. References:
• : In-App Guidance in Lightning Experience
• : Learn MOAR in Spring '21 with In-App Learning
• : Enable Users to Learn in the Flow of Work

An interactive prototype is a simulation of the final product that allows users to interact with it and test its functionality and usability. An interactive prototype can be created using tools such as Figma or Invision, and can be shared with stakeholders and users for feedback and validation. An interactive prototype can have several benefits for a UX designer, especially when planning to roll out a refreshed version of a mobile app with some new functionality for customers. Two of these benefits are12:

• To avoid added long-term cost from oversight-driven rework. An interactive prototype can help the UX designer to identify and fix any errors, bugs, or gaps in the design before the development stage. This can save time and money that would otherwise be spent on reworking the product after it is developed. An interactive prototype can also help the UX designer to ensure that the new functionality is aligned with the customer needs and expectations, and that it does not compromise the existing functionality or performance of the app.
• To enable iterative feedback from the users. An interactive prototype can provide a realistic and engaging user experience, and allow the users to explore the app and provide their opinions and suggestions. The UX designer can use the user feedback to iterate and improve the design, and to validate the assumptions and hypotheses. An interactive prototype can also help the UX designer to measure the user satisfaction and loyalty, and to test the app’s usability and accessibility.

The following two reasons are not valid for using an interactive prototype in this situation:

• To increase the speed of design compared to paper prototyping. An interactive prototype is not necessarily faster than a paper prototype, as it requires more time and effort to create and refine. A paper prototype is a low-fidelity prototype that uses sketches or drawings to represent the app’s layout and functionality. A paper prototype can be useful for generating and testing ideas quickly and cheaply, and for involving the users in the co-design process3.
• To eliminate the need for journey mapping during discovery. An interactive prototype is not a substitute for journey mapping, but a complement. Journey mapping is a UX research method that visualizes the user’s journey across the app, and identifies the touchpoints, actions, emotions, and pain points. Journey mapping can help the UX designer to understand the user’s context, goals, and needs, and to discover the opportunities for improvement. An interactive prototype can help the UX designer to test and validate the journey map, and to communicate the design vision to the stakeholders and users4. References: Interactive Prototypes Without Coding - Studio by UXPin, What is Interactive Prototypes? — updated 2023 | IxDF, Paper Prototyping as a Usability Testing Technique, Journey Mapping 101 | Nielsen Norman Group

A field-level error message is a message that appears next to a specific field when the user enters invalid data or omits required data. It helps the user to correct the error and proceed with the action. A field-level error message is more user-friendly than a validation rule, which displays a generic message at the top of the page and prevents the user from saving the record. A field-level error message can also provide guidance on the correct format and number of digits for the phone number field. Marking the field as required would not ensure that the user enters the phone number in the correct format and with the correct number of digits. Setting a prompt to display on the page using In-App Guidance would not prevent the user from entering invalid data or omitting required data. References: [Field-Level Error Messages], [Validation Rules], [In-App Guidance]

The tool that the UX Designer should use to plan and communicate the intended page layouts of a community portal is wireframes. Wireframes are low-fidelity sketches or diagrams that show the basic structure, content, and functionality of a web page or app screen. Wireframes help the UX Designer to visualize the layout of the portal, arrange the elements according to their importance and relevance, and communicate the design concept to the stakeholders and developers. Wireframes are one of the learning objectives for the Salesforce User Experience Designer certification 1. References: [Wireframes - Lightning Design System]

https://careerfoundry.com/en/blog/ux-design/website-app-wireframe-examples/

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 three considerations that should be made to improve the visual hierarchy of the page are:

• Grouping proximity and common regions. This principle states that elements that are close together or share a common boundary are perceived as belonging to the same group. This helps to create a sense of order and organization on the page and reduce the visual clutter.
• Scale using relative size to signal importance. This principle states that elements that are larger are perceived as more important or prominent than elements that are smaller. This helps to create a contrast and focus on the page and guide the user’s attention to the most relevant information.
• Color and contrast, saturation between the elements. This principle states that elements that have different colors or contrast levels are perceived as distinct or separate from each other. This helps to create a variety and interest on the page and highlight the differences or similarities between the elements.

References:

• : Visual Hierarchy
• : Gestalt Principles

The usability of accordion elements in a mobile environment could be improved by expanding the first section by default. This is because it can provide the user with a clear indication of what kind of content is hidden in the accordion, and encourage them to explore the rest of the sections1. Expanding the first section by default can also reduce the user’s cognitive load, as they do not have to make a decision on which section to open first2. Moreover, expanding the first section by default can improve the accessibility of the accordion, as it can help screen reader users to understand the structure and purpose of the widget3.

Using the Back browser button to collapse content is not a good option, as it can confuse the user and break the expected browser behavior. The Back button is meant to navigate to the previous page, not to collapse an accordion section4. Using the Back button to collapse content can also create navigation issues, as the user might lose their current page or state4.

Moving an expanded section to the top of the screen is also not a good option, as it can disrupt the user’s spatial memory and orientation. Moving an expanded section to the top of the screen can change the order and position of the accordion sections, which can make it harder for the user to find and access the section they want5. It can also create a jarring and inconsistent user experience, as the user might not expect the content to move around the screen5.

References:

• How to design the perfect accordion
• Accordions: Design guidelines
• Accessible Accordion - examples and best practices | Aditus
• Don’t Use The Back Button To Modify Data
• Usability of a mobile navigation consisting mostly of accordions?

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.

References: User Research Methods, Quantitative vs. Qualitative Usability Testing, 8 Essential Usability Testing Methods for UX Insights

A/B testing is a testing method that compares two versions of a user interface design to measure which one performs better in terms of a specific goal, such as form completions. A/B testing can help the UX Designer to evaluate the effectiveness of different design elements, such as layout, color, typography, copy, etc. A/B testing can also help the UX Designer to optimize the conversion rate of the landing page and increase the number of leads generated. References: [A/B Testing], [Optimize Your Landing Pages with A/B Testing]

According to the Salesforce Lightning Design System, the minimum touch screen target size for interactive elements on mobile devices is 44 pixels wide x 44 pixels tall. This size ensures that users can easily tap the elements without accidentally hitting the wrong ones or missing them entirely. The touch target size also takes into account the average finger size and the device resolution. Smaller touch targets may cause frustration and errors for users, especially those with low vision, motor impairments, or large fingers. References: : Salesforce Lightning Design System - Sizing : Salesforce Lightning Design System - Accessibility

Cloud Kicks (CK) can use the following three solutions to leverage the Salesforce Lightning Design System (SLDS) in its custom applications, without migrating to Lightning Experience:

• Lightning Stylesheets for Visualforce: This solution allows CK to apply the SLDS styles to its existing Visualforce pages, without having to rewrite the markup or use a static resource. By adding the attribute lightningStylesheets="true" to the  tag, CK can automatically transform the standard Visualforce components into their SLDS equivalents, and give the pages a consistent Lightning Experience look and feel12.
• Standard Design Tokens: This solution allows CK to use the SLDS design tokens, which are predefined variables that store the visual design attributes of the SLDS, such as colors, fonts, sizes, and spacing. By using the design tokens, CK can ensure that its custom applications follow the SLDS guidelines and remain consistent with the Lightning Experience theme. CK can access the design tokens through the Lightning Design System Scoping tool, or by downloading them as a static resource3 .
• Heroku: This solution allows CK to build and deploy its custom applications on Heroku, a cloud platform that supports various languages and frameworks, such as Node.js, Java, or PHP. By using Heroku, CK can leverage the SLDS resources, such as the base components, the tokens, and the design patterns, to create web applications that have a consistent Lightning Experience look and feel. CK can also use the Lightning Out feature to embed Lightning components into its Heroku applications, and use the Lightning Web Components framework to create reusable UI elements .

References:

• [Lightning Stylesheets for Visualforce | Salesforce Trailhead]1
• [Lightning Stylesheets for Visualforce | Salesforce Developers]2
• [Design Tokens | Lightning Design System]3
• [Using Design Tokens | Lightning Aura Components Developer Guide | Salesforce Developers]
• [Build Apps with Lightning Design System | Salesforce Trailhead]
• [Lightning Web Components | Salesforce Developers]

The best option for guiding sales users through a new process using floating or docked prompts is to use the Walkthrough App from AppExchange. This app allows admins to create and manage in-app guidance walkthroughs using clicks, not code. Walkthroughs are interactive tutorials that guide users through a series of steps on a Lightning page. Users can see the prompts, click the action buttons, and follow the instructions to complete the process. Admins can also track the engagement and completion of the walkthroughs using reports and dashboards. The Walkthrough App is compatible with the standard in-app guidance feature, and does not require a subscription to myTrailhead1 .

The other options are not suitable for this scenario because:

• In-App Guidance Prompts using myTrailhead: This option requires a subscription to myTrailhead, which is a customizable learning platform that allows admins to create their own content and branding. In-app guidance prompts are one of the features of myTrailhead, but they are not the same as walkthroughs. Prompts are single-step messages that appear on a Lightning page, while walkthroughs are multi-step tutorials that guide users through a process. Prompts can be used to provide tips, announcements, or links, but they cannot show users how to perform a task234.
• Custom build using Salesforce Flow: This option requires coding and development skills, which may not be available or feasible for the admin team. Salesforce Flow is a tool that allows admins to automate processes and tasks using clicks or code. Flows can be triggered by various events, such as buttons, actions, schedules, or record changes. Flows can also display screens to users, which can contain fields, text, images, or components. However, screens are not the same as prompts or walkthroughs. Screens are part of a flow logic, and they require user input to proceed to the next step. Screens cannot be customized to appear as floating or docked prompts, and they cannot guide users through a Lightning page56.
• Basic In-App Guidance Prompts: This option does not require a subscription to myTrailhead, but it also does not provide the functionality of walkthroughs. Basic in-app guidance prompts are the same as the ones mentioned in the first option, but without the customization and branding of myTrailhead. Basic prompts can be created and managed using clicks, not code, and they can be filtered by profiles and permissions. However, basic prompts are still single-step messages that appear on a Lightning page, and they cannot show users how to perform a task23.

References:

• : [In-App Guidance Walkthroughs: Getting Started for Sales Users]
• : [In-App Guidance Dashboard: Walkthrough Engagement]
• : [In-App Guidance in Lightning Experience]
• : [Salesforce Flow | Salesforce Developer Center]
• : [Salesforce Flow Workflow Automation Tools - Salesforce.com]
• : [The Complete Guide to Salesforce Flow | Salesforce Ben]
• : [Trailhead | The fun way to learn]
• : [Editions & Pricing - myTrailhead- Salesforce]
• : [Salesforce introduces myTrailhead, a personal learning platform …]
• : [Trailhead | The fun way to learn Salesforce]
• : [Getting Started with myTrailhead - Salesforce]

The best way for the designer to illustrate the existing process, including the pain points and opportunities, is to observe the complaints process and create a journey map. A journey map is a visual representation of the customer’s or user’s experience with a product or service, from their perspective. It shows the steps, interactions, thoughts, feelings, touchpoints, context, and opportunities for improvement along the way. A journey map can help the designer to understand the current state of the complaints process, identify the pain points and gaps, and prioritize the areas for intervention. A journey map can also help to communicate the user’s needs and expectations to the stakeholders and developers, and align them on a common vision for the solution. References:

• : Start Your Journey Map Unit | Salesforce Trailhead
• : Add Journey Mapping to Your Solution Toolbox Unit | Salesforce Trailhead
• : Customer Journey Mapping Resources - Salesforce

 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

 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

References:

• Get Started with Screen Flows Unit | Salesforce Trailhead
• How to Create a Salesforce Screen Flow | Salesforce Ben
• 5 Ways to Get Started with Screen Flows - Salesforce Admins
• Create and Distribute Surveys with Salesforce Feedback Management
• Automate Your Business Processes with Process Builder

The designer should consider the traits similar to customer personas when selecting users for testing. Customer personas are fictional representations of the target users of a product or service, based on user research and data. Customer personas help the designer to understand the needs, goals, behaviors, and preferences of the users, as well as their pain points and challenges. Customer personas also help the designer to empathize with the users and design solutions that meet their expectations and requirements. [UX Designer Certification Prep: User Research], [UX Designer Certification Prep: User Roles and Personas]

When selecting users for testing, the designer should aim to recruit users who match the traits of the customer personas as closely as possible. This ensures that the users who participate in the testing are representative of the actual or potential users of the product or service, and that the feedback and insights gathered from the testing are valid and reliable. Selecting users who have traits similar to customer personas also helps the designer to evaluate the usability and user experience of the product or service from the user’s perspective, and to identify and prioritize the areas for improvement. [UX Designer Certification Prep: User Research], [UX Designer Certification Prep: User Testing and Evaluation]

Traits dissimilar to customer personas, traits similar to friends and family, and traits of the most common demographic and ability are not criteria that the designer should consider when selecting users for testing. These criteria can lead to biased or inaccurate results, as they do not reflect the diversity and complexity of the user population. Users who have traits dissimilar to customer personas may not have the same needs, goals, or expectations as the target users, and may provide feedback that is irrelevant or misleading. Users who have traits similar to friends and family may not be objective or honest in their feedback, and may have a different level of familiarity or expertise with the product or service than the target users. Users who have traits of the most common demographic and ability may not account for the variations and differences among the target users, and may exclude or marginalize the users who have special needs or preferences. [UX Designer Certification Prep: User Research], [UX Designer Certification Prep: User Testing and Evaluation] References: [UX Designer Certification Prep: User Research], [UX Designer Certification Prep: User Roles and Personas], [UX Designer Certification Prep: User Testing and Evaluation]

To let its users know when a new feature is enabled or available with a short video explaining the new feature, the recommended solution is to use a docked prompt using In-App Guidance. In-App Guidance is a feature that allows the designer to create prompts and walkthroughs that guide users through new or complex tasks in Salesforce. A docked prompt is a type of prompt that appears at the bottom of the screen and can contain text, images, or videos. A docked prompt can be used to announce a new feature and provide a short video tutorial on how to use it. The designer can also set the conditions for when and how often the prompt should appear, and track the user engagement with the prompt. References: : In-App Guidance | Salesforce Help : UX Designer Certification Prep: Designing with In-App Guidance | Trailhead

 Service design is a practice that aims to design and deliver holistic, human-centered, and value-driven solutions that consider the needs and expectations of not only the individual users, but also the stakeholders, the employees, the partners, and the society involved in the service. Service design focuses on more than just the user interface or the user experience, but also on the processes, systems, interactions, touchpoints, and channels that enable the service to be delivered and consumed. Service design can help create engaging, connected, and social value-driven solutions that improve the quality, efficiency, and sustainability of the service . References:

• : User Experience Designer Certification Prep: Module 1: Understand User Experience Design
• : What is Service Design?

Service Design is a design practice that focuses on providing better experiences to users by understanding the context of their needs and how they interact with systems, services, and products. Service Design goes beyond User Experience Design by focusing on more than just individual people, and instead considers the entire ecosystem, including connected and social value-driven solutions. Salesforce provides more information on Service Design here: https://www.salesforce.com/resources/service-design/.

The design should be optimized for color contrast-ratio and screen-reading technology, as these are the best practices for designing for visually impaired people12. Color contrast-ratio is the difference in brightness and color between the foreground and the background of a text or an image3. A high color contrast-ratio makes the text or the image more visible and readable for people with low vision or color blindness4. Screen-reading technology is a software that converts text and images on a screen into speech or braille output for people who are blind or have severe vision loss. A design that is compatible with screen-reading technology ensures that the content and functionality of the product are accessible and understandable for these users. References: Accessibility Standards - Salesforce Help, How to Configure Salesforce for your Blind and Low Vision Users - Salesforce Admins, Color Contrast Ratio - WebAIM, Color Contrast Checker - WebAIM, [Screen Readers - WebAIM], [Screen Reader User Survey #8 Results - WebAIM]

The correct answer is B. When designing for a visually impaired audience, it is important to optimize for color contrast-ratio and screen-reading technology. This will ensure that the design is accessible to those with visual impairments. Color contrast-ratio ensures that the text is easily readable, while screen-reading technology allows people with visual impairments to access the content on the website using a screen reader. Additionally, Salesforce has some great resources on designing for accessibility, such as their Accessibility Design Guide [1] and their Accessibility Best Practices [2].

[1] https://www.salesforce.com/content/dam/web/en_us/www/documents/salesforce-accessibility-design-guide.pdf  [2] https://developer.salesforce.com/docs/atlas.en-us.salesforce_accessibility_best_practices.meta/salesforce_accessibility_best_practices/accessibility_best_practices_intro.htm

Inclusive design is a design approach that aims to create products and services that are accessible and usable by as many people as possible, regardless of their abilities, preferences, or circumstances. Some of the benefits of inclusive design are :

• Extending access to more users: By considering the diverse needs and situations of users, inclusive design can expand the reach and impact of the product or service. For example, designing a website that is compatible with screen readers can benefit not only users who are blind or visually impaired, but also users who are in low-light environments or have low bandwidth.
• Reducing friction for users in achieving their goals: By removing unnecessary barriers and providing multiple ways of interaction, inclusive design can enhance the user experience and satisfaction. For example, designing a mobile app that supports voice input and output can benefit not only users who have difficulty typing or reading, but also users who are multitasking or have their hands busy. References: : [UX Designer Certification Prep: Designing for Accessibility and Inclusion | Trailhead] : [Inclusive Design | Salesforce Developer Guide]

Inclusive design is a practice of designing products, services, and experiences that are accessible and usable for as many people as possible, regardless of ability, age, gender, race, language, or culture. By incorporating inclusive design practices, you can extend access to more users and reduce friction for users in achieving their goals. Salesforce provides more information on the benefits of inclusive design here: https://www.salesforce.com/blog/2020/11/what-is-inclusive-design.html.

 A sales rep who owns an opportunity record will have read-only access to the related account record, if the organization-wide default for the Account object is private. This is because the opportunity owner is automatically granted read-only access to the account that the opportunity is associated with, regardless of who owns the account. This is called implicit sharing, and it is a built-in feature of Salesforce to ensure that users can access the data they need to do their work. However, the opportunity owner will not be able to create, edit, or delete the account record, unless they have other sharing mechanisms that grant them higher access, such as role hierarchy, sharing rules, manual sharing, or View All or Modify All permissions. References:

• [Salesforce Certified User Experience Designer Exam Guide], Section 3.1: Design and implement solutions that meet user needs
• [Control Access to Records Unit | Salesforce Trailhead]1, Unit 2: Implicit Sharing
• [Work with Related Lists on Records in Lightning Experience - Salesforce]2, Related List Cards