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

Cloud Kicks' new design solutions would be described by the conceptual approach of desirable, feasible, and viable. This approach is based on the human-centered design (HCD) methodology, which aims to create solutions that meet the needs, preferences, and expectations of the users or customers, while also being technically possible and economically sustainable. HCD is a creative problem-solving process that starts with identifying the user's problems and ends with creating solutions that address them. The desirable, feasible, and viable framework helps designers evaluate their solutions according to these three criteria:

Desirable: A solution that people want or need, that solves a real problem for them, and that provides a meaningful and relevant experience.

Feasible: A solution that can be created with new or existing technology, that is within the scope and capabilities of the organization, and that can be tested and validated.

Viable: A solution that fits the organization's business model, that generates value for the stakeholders, and that is sustainable in the long term.

By applying this framework, Cloud Kicks can ensure that its new design solutions for its sales processes in Salesforce are not only user-friendly, but also technically sound and profitable. This can help Cloud Kicks achieve its business goals, while also delivering more satisfying and delightful customer experiences.

Explore Human-Centered Design

IDEO's Desirability, Viability, Feasibility Framework: A Practical Guide

The Salesforce app allows administrators to customize the brand color and the loading page logo to match the company's branding. The brand color affects the key user interface elements such as the header, buttons, and search bar. The loading page logo is the image that appears after a mobile user logs in. These elements can be customized from Setup by entering Salesforce Branding in the Quick Find box, then selecting Salesforce Branding. The other elements, such as the search bar layout, the background image, and the focus link color, are not customizable in the Salesforce app.Reference:

Customize Salesforce Mobile App Branding

How Salesforce App Branding Works

Card sorting is a UX research method used to discover how people understand and categorize information. In a card sort, participants group ideas or information written on cards into different categories in a way that makes sense to them. The designer can use virtual cards, pieces of paper, or an online card sorting tool. Card sorting can help the designer to:

Assess the information architecture (IA) of a website or homepage

Learn how people understand different concepts or ideas, and how they feel about them

Understand where users expect certain content to be found

Get inspiration for labeling and grouping content or ideas

In this case, the designer wants to understand the structure and layout of the navigation menu for the Experience Cloud site. The designer can use card sorting to learn how users would group and label the pages or features of the site, and what categories or subcategories they would expect to see in the navigation menu. This can help the designer to create a user-friendly and intuitive IA that matches the users' mental models and expectations.

To conduct a card sorting activity, the designer should:

Define the goal and scope of the card sort

Choose the type of card sort (open, closed, or hybrid)

Choose the format of the card sort (moderated or unmoderated)

Select the cards and categories to use

Recruit and screen the participants

Run the card sort sessions

Analyze and interpret the results

Apply the findings to the design

The correct answer is B, have users sort the cards based on similar categories or groups. This is the main task of a card sorting activity, where users are asked to group the cards (representing the pages or features of the site) into categories or groups that make sense to them. The designer can then analyze the results to see how users organize and label the information, and use that to inform the design of the navigation menu.

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.Reference:WCAG 2 Overview,Understanding the Web Content Accessibility Guidelines

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.Reference:Add Style to Your Experience Builder Site with Themes,Use Branding Sets in Experience Builder

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

[1]: Salesforce Lightning Design System - Introduction

[2]: Salesforce Lightning Design System - Naming Con

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

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.Reference: [Field-Level Error Messages], [Validation Rules], [In-App Guidance]

: A lookup relationship is a type of relationship that links two objects together, but the relationship is not required. This means that the child object can exist independently of the parent object. A lookup relationship can be either one-to-many or many-to-one, depending on the cardinality of the objects involved. For example, a contact can have a lookup relationship to an account, which means that a contact can belong to one account, but an account can have many contacts. Alternatively, a custom object can have a lookup relationship to a user, which means that a custom object can belong to many users, but a user can have only one custom object record.Reference:Trailhead: Data Modeling,Trailhead: Salesforce User Experience Designer Certification Prep,Salesforce Help: Define Lookup Relationships