Salesforce Certified User Experience Designer Practice Test - Questions Answers, Page 11

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

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

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.Reference:

: 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/).

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.Reference: : UX Designer Certification Prep: Designing with Service Cloud | Trailhead : Service Cloud Basics | Salesforce Help

The discovery process is a crucial phase in any UX design project, as it helps to understand the user needs, business goals, and technical constraints of the problem1.The discovery process 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 process are artifacts that synthesize and communicate the findings and insights from the research. Some of the common outputs of the discovery process are:

User personas: These are fictional representations of the target users, based on real data and insights, that describe their goals, motivations, pain points, behaviors, and preferences3. User personas help to empathize with the users and design solutions that meet their needs and expectations.

Journey maps: These are visualizations of the user's end-to-end experience with a product or service, from the initial trigger to the final outcome4. Journey maps help to identify the user's actions, thoughts, emotions, pain points, and opportunities for improvement at each stage of the journey.

High-level wireframes: These are low-fidelity sketches or diagrams that show the basic layout, structure, and functionality of the website or app. High-level wireframes help to define the information architecture, navigation, and content hierarchy of the solution, as well as test the usability and feasibility of the design concepts.

These three outputs are essential for planning out the website redesign using Experience Cloud, as they help to define the user requirements, the user flow, and the user interface of the solution. The other two options, interactive prototypes and high-fidelity mock-ups, are not outputs of the discovery process, but rather of the design and testing phases. Interactive prototypes are clickable simulations of the website or app that allow users to interact with the functionality and features of the solution. High-fidelity mock-ups are realistic and detailed representations of the website or app that show the final look and feel of the solution, including the colors, fonts, images, and icons. These two outputs are created after the discovery process, based on the feedback and validation from the user testing sessions.

For the UX Designer at Cloud Kicks, thethree outputs of the discovery process that should be prepared are User Personas, Journey Maps, and High-Level Wireframes. User Personas are fictional characters that represent a target audience for the website, and are used to help guide the website design. Journey Maps are diagrams that illustrate the user's experience as they navigate the website, and provide insights into how the user interacts with the website. High-Level Wireframes are simple sketches of the website layout, and are used to organize the website's content and design elements. Interactive Prototypes and High-Fidelity Mock-ups are not necessary outputs of the discovery process, as they are more detailed representations of the design that come later in the design process. For more information, see the Salesforce Experience Cloud documentation (https://help.salesforce.com/articleView?id=experience_cloud_overview.htm&type=5).

An empathy map is a tool that helps to synthesize what CK knows about the users and share this insight with the rest of the organization. An empathy map is a visual representation of the user's perspective, based on their thoughts, feelings, actions, and needs. It helps to create a shared understanding of the user's goals, pain points, motivations, and emotions. An empathy map can also help to identify gaps in the user research and generate new ideas for design solutions.Reference:

:Creating a Customer Empathy Map Using The 5 Senses

:Why Empathy Is Crucial to Business Success

:Use Empathy Maps to build better software

Asking the user to think aloud during a user task has the following benefits12:

A) No special equipment needed. Thinking aloud is a simple and low-cost method that does not require any special equipment or software. The user only needs a microphone or a phone to record their voice, and the tester only needs a way to listen and observe the user's actions.

D) Flexibility. Thinking aloud is a flexible method that can be applied to various types of tasks, products, and platforms. It can also be conducted remotely or in-person, synchronously or asynchronously, moderated or unmoderated, depending on the needs and preferences of the tester and the user.

E) Raw stream of thought. Thinking aloud provides a raw and rich stream of data that reveals the user's thoughts, feelings, expectations, assumptions, motivations, and frustrations as they interact with the product. It can help the tester to understand the user's mental model, decision-making process, and satisfaction level.

A top-of-page validation is a type of validation rule that displays an error message at the top of the page when a user tries to save a record that does not meet certain criteria. A field validation is a type of validation rule that displays an error message next to a specific field when a user tries to save a record that does not meet certain criteria. The advantage of using field validations over top-of-page validations is that they provide more clarity and guidance to the user about which fields need to be corrected and why. They also reduce the cognitive load and the scrolling effort for the user, as they can see the error message right next to the field they are editing. Therefore, to help the Client Service team at Cloud Kicks efficiently find the correct fields when editing an order record, the UX designer should replace the top-of-page validation with two field validations, assigning the respective fields that are required to validate and save the order changes.Reference:

: User Experience Designer Certification Prep: Module 5: Design User Interfaces

: User Experience Designer Certification Prep: Module 7: Implement User Interfaces

: Validation Rules

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.Reference: : In-App Guidance | Salesforce Help : UX Designer Certification Prep: Designing with In-App Guidance | Trailhead

Responsive design is a web design approach that aims to make web pages adapt to different screen sizes and resolutions, ensuring good usability and user experience across all devices. Some of the best practices for responsive design are:

Specify breakpoint sizes: Breakpoints are the points at which the layout of a web page changes based on the width of the viewport. For example, a web page may have a two-column layout on a desktop, a single-column layout on a tablet, and a stacked layout on a mobile phone. Specifying breakpoint sizes helps to create a fluid and flexible layout that responds to the device capabilities and user preferences. Breakpoints can be specified using media queries in CSS, which allow applying different styles depending on the media features, such as width, height, orientation, resolution, etc. For example:

@media (max-width: 600px) { /* Styles for screens that are 600px or smaller */ }

@media (min-width: 601px) and (max-width: 900px) { /* Styles for screens that are between 601px and 900px */ }

@media (min-width: 901px) { /* Styles for screens that are 901px or larger */ }

Minimize page weight: Page weight is the amount of data that a web page transfers to load on a browser. It includes the size of the HTML, CSS, JavaScript, images, fonts, and other resources that make up the web page. Minimizing page weight helps to improve the performance, speed, and user satisfaction of a web page, especially on mobile devices that may have limited bandwidth, battery, and processing power. Some of the ways to minimize page weight are:

Optimize images: Images are often the largest contributors to page weight, so it is important to optimize them for the web. This means choosing the right format, size, resolution, and compression level for each image, as well as using responsive images techniques, such as the srcset and sizes attributes, to deliver the most appropriate image for each device and screen size.

Implement caching: Caching is a technique that stores a copy of a web page or its resources on the browser or the server, so that they can be reused without having to be downloaded again. This reduces the amount of data that needs to be transferred and improves the loading time of a web page. Caching can be implemented using HTTP headers, such as Cache-Control and Expires, or using service workers, which are scripts that run in the background and intercept network requests.

Minify and concatenate files: Minification is a process that removes unnecessary characters, such as whitespace, comments, and formatting, from the code files, such as HTML, CSS, and JavaScript, to reduce their size. Concatenation is a process that combines multiple code files into one, to reduce the number of HTTP requests that the browser needs to make. Both minification and concatenation can help to reduce the page weight and improve the performance of a web page.

Use a content delivery network (CDN): A CDN is a network of servers that are distributed across different locations and regions, and that store and deliver copies of a web page or its resources to the users. A CDN can help to reduce the page weight and improve the speed of a web page by serving the content from the nearest server to the user, reducing the latency and bandwidth consumption.

The other two options, using separate URLs per device and utilizing pop-up windows, are not considered responsive design best practices, as they can create usability and accessibility issues for the users. Using separate URLs per device means creating different versions of a web page for different devices, such as example.com for desktop, m.example.com for mobile, and t.example.com for tablet. This approach can lead to inconsistent and fragmented user experiences, as well as duplicate content and SEO problems. Utilizing pop-up windows means creating new browser windows that open on top of the current web page, usually to display advertisements, notifications, or forms. This approach can be annoying and intrusive for the users, as well as difficult to close or navigate on small screens.