User-Experience-Designer Exam Dumps - Salesforce Certified Platform User Experience Designer (Plat-UX-101)

Voice is the overall personality of the design, while tone is the way that personality is expressed. Voice represents the core characteristics of a design, such as the values, attitude, and emotions it conveys. Tone is how those characteristics are expressed in the design, suchas the language, visuals, and other elements. For example, a design with a friendly voice might be expressed through warm colors, friendly imagery, and casual language. Salesforce has some great resources on voice and tone such as [1] and [2].

[1] https://www.salesforce.com/blog/2017/11/voice-tone-brand-personality.html [2]  https://www.salesforce.com/blog/2018/10/voice-tone-brand-personality-ux.html

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

The SLDS BEM naming convention consists of three parts: block, element, and modifier. A block is a standalone component that can be reused across projects, such as a button, a card, or a modal. An element is a part of a block that has no standalone meaning, such as a label, an icon, or a header. A modifier is a flag that changes the appearance or behavior of a block or an element, such as size, color, or state. The modifier is separated from the block or element by two hyphens (–), and can have a value separated by a single hyphen (-), such as .slds-button–brand or .slds-button–neutral. The class .slds–size-l-of-2 does not follow thisconvention because it has no block or element name before the modifier. It should be something like .slds-grid–size-l-of-2 or .slds-col–size-l-of-2. References:

• [1]: Salesforce Lightning Design System - Introduction
• [2]: Salesforce Lightning Design System - Naming Con

 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 insightsfrom 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

A heuristic evaluation is a method of inspecting the usability of an interface by comparing it to a set of general principles or heuristics. It can help identify potential problems and areas for improvement in the design. A heuristic evaluation is usually done before creating any prototypes, as it can provide insights and guidance for the design process. A low-fidelity prototype is a rough sketch or mockup of an interface that can be used to test and validate design ideas with users. It is usually created after conducting some research and analysis of the user needs and goals. A design template is a pre-made layout or structure that can be used to create an interface. It can help save time and ensure consistency in the design, but it may not suit the specific needs and preferences of the users or the business. A design template is usually applied after defining the content and functionality of the interface. References:

• [Heuristic Evaluation]: This is a Trailhead module that explains what a heuristic evaluation is, how to conduct one, and how to use the results to improve the design of an interface.
• [Low-Fidelity Prototyping]: This is a Trailhead module that covers the benefits and best practices of creating and testing low-fidelity prototypes with users.
• [Design Templates]: This is a Trailhead module that introduces the concept of design templates and how to use them in Experience Cloud.

Q Tabs are a type of SLDS component that can be used to organize and consolidate content on a record page. Q Tabs are a variant of the Tabs component that are designed for use in the Lightning App Builder. Q Tabs allow users to switch between different views of related information within the same context. Q Tabs can also be nested to create subtabs within a tab. Q Tabs can help UX designers to create content-rich record pages that are easy to navigate and consume. Q Tabs can also help to reduce clutter and scrolling on a record page by grouping related content into tabs. Q Tabs can be customized with different icons, labels, and badges to indicate the type and status of the content in each tab. Q Tabs can also be configured to load content dynamically or on demand, which can improve the performance and user experience of the record page. References: Q Tabs Component Blueprint | Lightning Design System, Tabs Component Blueprint | Lightning Design System, Tabs | Lightning Web Components Developer Guide | Salesforce Developers

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?

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