User-Experience-Designer Practice Test

Explanation:

Human-centered design is a practice where designers focus on people and their context, and seek to understand and solve the right problems for them. Human-centered design involves the following elements1:

Empathy. Designers need to genuinely care about the people they design for, and build empathy by immersing themselves in the community that will use their products or services. Creativity. Designers need to find creative ways to solve users’ problems, and generate multiple ideas and prototypes that can be tested and refined.

Business needs. Designers need to make their products or services commercially successful, and align them with the goals and values of the organization.

To incorporate human-centered design across its organization, Cloud Kicks should adopt the following two practices:

Observing user behavior. Designers should conduct user research and communicate with their users regularly, to understand their needs, motivations, challenges, and goals. Observing user behavior can help designers to identify the pain points and opportunities for improvement, and to validate their assumptions and hypotheses.

Putting oneself in the situation of the end user. Designers should empathize with their users, and try to see the world from their perspective. Putting oneself in the situation of the end user can help designers to create products or services that are relevant, useful, and desirable for them. The following two practices are not aligned with human-centered design, and should be avoided:

Including innovative ideas to showcase technology. Designers should not prioritize technology over people, and should not include features or functions that are not necessary or beneficial for the users. Including innovative ideas to showcase technology can lead to products or services that are complex, confusing, or frustrating for the users.

Creating requirements based on business leaders’ priorities. Designers should not ignore the voice of the users, and should not create products or services that only satisfy the business needs. Creating requirements based on business leaders’ priorities can lead to products or services that are irrelevant, useless, or undesirable for the users.

References: Human-Centered Design: An Introduction, Practices, and Principles - Shopify

Explanation:

The accessibility guideline of distinguishable means that the information and user interface components must be presented to users in ways that are perceptible. This includes using sufficient contrast between text and background colors, providing text alternatives for non-text content, and making it easier for users to see and hear content. When choosing a color for the text and the background of the buttons, the UX Designer should consider the contrast ratio between them, which should be at least 4.5:1 for normal text and 3:1 for large text. This will ensure that the buttons are visible and readable for users with different visual abilities.

References:

[1]: Web Content Accessibility Guidelines (WCAG) 2.1, Principle 1: Perceivable

[2]: Web Content Accessibility Guidelines (WCAG) 2.1, Success Criterion 1.4.3 Contrast

(Minimum)

Explanation:

An Empathy Map is a tool used in UX design to synthesize and articulate what a design team knows about a user group. It helps in creating a shared understanding of user needs within an organization. The key features of an Empathy Map include:

User Insights:It captures what users say, think, do, and feel, providing a holistic view of their experiences and perspectives. This helps in understanding users at a deeper level. Shared Understanding:By visualizing user attitudes and behaviors, an Empathy Map facilitates a common understanding among team members and stakeholders, ensuring that design decisions are aligned with user needs.

An Executive Summary (option A) provides a high-level overview of project objectives and outcomes but does not delve into user-centric insights. Prioritizing a Backlog (option C) is more about organizing and prioritizing tasks and features rather than synthesizing user research findings.

References:For guidelines on creating and using Empathy Maps, UX design resources such as the Nielsen Norman Group and the Interaction Design Foundation offer articles and guides on this andother UX research synthesis tools. These resources explain how to effectively use Empathy Maps to gain insights into user needs and foster empathy within design teams.

Explanation:

The best option to simplify working with SLDS in Lightning Components is to install SLDS Validator extension for VS Code. This extension (salesforcedx-vscode-slds) scans the markup of the components, validates it against the SLDS documentation, and provides suggestions onhow to improve the code1. It also offers syntax highlighting, code completion, and context awareness for SLDS tokens and utility classes1. By using this extension, the development team can avoid CSS conflicts, follow SLDS best practices, and create consistent and accessible components2.

Installing SLDS creator from AppExchange is not a valid option, as there is no such app available on the AppExchange. The AppExchange is a marketplace for Salesforce apps, components, and consulting services, not for VS Code extensions3.

Installing Lightning Design System Plugin for Sketch is also not a valid option, as it is not related to VS Code or Lightning Components. Sketch is a design tool that allows users to create wireframes, mockups, and prototypes4. The Lightning Design System Plugin for Sketch is a plugin that provides SLDS components, icons, and styles for Sketch users. It can help designers to create consistent and compatible designs, but it cannot help developers to work with SLDS in VS Code.

References:

SLDS Validator - Visual Studio Marketplace

SLDS Validator for VS Code - Lightning Design System

AppExchange: Salesforce’s Leading Enterprise Cloud Marketplace

Sketch — The digital design toolkit

[Lightning Design System Plugin for Sketch]

Explanation:

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