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

Human-centered design is a process that starts with the people you are designing for and ends with new solutions that are tailor-made to suit their needs. It involves understanding the problem from the perspective of the end-users, empathizing with their needs and preferences, and creating solutions that are desirable, feasible, and viable. To incorporate human-centered design across an organization, two practices that should be adopted are:

Observing user behavior: This involves watching how users interact with a product or service, what they do, say, think, and feel. Observing user behavior can help identify pain points, needs, goals, motivations, and emotions that drive user behavior. It can also reveal insights that users may not be able to articulate or may not be aware of themselves. Observing user behavior can be done through methods such as user interviews, contextual inquiry, usability testing, and analytics.

Putting oneself in the situation of the end-user: This involves imagining or experiencing what the user goes through when using a product or service, and how they perceive and respond to it. Putting oneself in the situation of the end-user can help build empathy, understand the user's context and environment, and generate ideas that address the user's needs and expectations. Putting oneself in the situation of the end-user can be done through methods such as personas, scenarios, journey maps, and empathy maps.

: [What is Human-Centered Design?]

: [Human-Centered Design: The Definitive Guide]

: [UX Research: What is User Behavior?]

: [Observing the User Experience: A Practitioner's Guide to User Research]

: [UX Research Methods: Observation]

: [Empathy in Design Thinking]

: [UX Research Methods: Empathy]

User interface planning is an essential part of the Einstein Bot implementation process, as it involves designing the bot's appearance, behavior, and interactions with the customers. User interface planning can affect the bot's effectiveness and customer satisfaction, as it can influence the clarity, efficiency, consistency, and beauty of the bot's experience.User interface planning includes1:

Choosing a bot avatar and name that match the brand and tone of the company

Configuring the bot greeting and fallback messages that set the expectations and boundaries of the bot's capabilities

Designing the bot dialogues and menus that guide the customers through the conversation and provide relevant options and information

Testing and iterating the bot user interface based on user feedback and analyticsReference:Einstein Bots Project Planning | Salesforce Trailhead

A sketch plugin is a tool that allows the UX designer to quickly mock up Salesforce user interface experiences using the Lightning Design System (SLDS) resources, such as base components, tokens, and design patterns. The sketch plugin is a free plugin for Sketch, a design toolkit that helps create wireframes, mockups, sample screens, and more. With the sketch plugin, the designer can search and drag the prebuilt components from the plugin into the canvas, and export the mockups as pdf, jpeg, or png files. The sketch plugin also supports synonyms and variants for the components, making it easier to find and use the desired elements.The sketch plugin can be downloaded from the SLDS website1or from the AppExchange2.Reference:

[Create Quick Salesforce UI Mockups: Lightning Design System Plugin for Sketch]1

[Lightning Design System Sketch Plugin]2

The development team missed two features that are causing the problems:

TheWith Sharingkeyword in Apex classes to enforce sharing rules evaluation. This keyword allows the Apex class to run in the context of the current user and respect the organization's sharing rules. Without this keyword, the Apex class runs in system mode and ignores the sharing rules, which can result in unauthorized access to records that belong to other users .

TheisAccessible()method in Apex classes to check field accessibility. This method returns true if the current user has read access to the specified field, and false otherwise. Without this method, the Apex class does not check the field-level security settings and can display fields that should be hidden from the user, such as the shipment amount .

: Using the with sharing or without sharing Keywords

: Enforcing Sharing Rules in Apex

: Schema.DescribeFieldResult Class

: Enforcing CRUD and FLS

The best way to achieve the requirement of having a flag field on the case object that marks a case as sensitive and can be viewed by all users who have access to the case but only be edited by the assigned case assessor is to create a custom Lightning component. A custom Lightning component can use the Lightning Data Service to access the case record and its fields, and apply conditional rendering and editing logic based on the user's role and the case assessor field. This way, the flag field can be displayed to all users who can view the case, but only be editable by the user who is the case assessor. This solution also follows the principle of designing for performance and scalability, which is one of the learning objectives for the Salesforce User Experience Designer certification.Reference: [Create Custom, Reusable Lightning Components], [Lightning Data Service Basics], [Design for Performance and Scalability]

: https://trailhead.salesforce.com/en/content/learn/modules/lex_dev_lc_basics/lex_dev_lc_basics_intro : https://trailhead.salesforce.com/en/content/learn/modules/lightning_data_service/lightning_data_service_intro : https://trailhead.salesforce.com/en/content/learn/modules/ux-designer-certification-prep/design-for-performance-and-scalability

Changing the role hierarchy and reassigning account owners can have a significant impact on the data visibility and performance of Salesforce. An architect should consider the following points in this situation:

Changing complex role hierarchy can cause a high level of sharing recalculation.Depending on the sharing settings, roles can control the level of visibility that users have into the Salesforce data. Users at any given role level can view, edit, and report on all data owned by or shared with users below them in the role hierarchy, unless the sharing model for an object specifies otherwise. When the role hierarchy is changed, Salesforce must recalculate the sharing rules and group membership for all the affected users and records, which can take a long time and consume a lot of system resources.Therefore, changing a complex role hierarchy should be done carefully and preferably during off-peak hours1.

Replacing account records ownerships massively can cause data skew.Data skew occurs when more than 10,000 child records are related to the same parent record, or more than 10,000 records of any object are owned by a single user. This can cause performance issues, such as locking, timeouts, and failures, when updating or sharing those records. When account owners are reassigned massively, it can create or worsen data skew, especially if the accounts have many child records, such as contacts and opportunities.Therefore, replacing account records ownerships massively should be avoided or minimized23.

: [Design Your Data Model Unit | Salesforce Trailhead]

: [Data Skew in Salesforce - Why it Matters | Salesforce Ben]

: [Ownership Data Skew | Designing Record Access for Enterprise Scale | Salesforce Developers]

When the organization-wide default for Accounts is private, users can only access the accounts they own or are explicitly shared with them.However, when the organization-wide default for Opportunities is private, users can access the opportunities they own, are explicitly shared with them, or are associated with accounts they can access1. Therefore, when ownership-based sharing rules are created for each team to grant access to opportunities owned by their team members, the sales reps on the same team will also have Read access to the accounts for those opportunities.This is because the sharing rules for opportunities automatically grant access to the parent accounts2.However, the sales reps will not have Edit access to the accounts, unless the sharing rules specify Full Access for the opportunities3. The sales reps will also not have access to all accounts or all opportunities, only those that are owned by their team members or themselves.Reference:Sharing Records Owned by High-Volume Portal Users | Salesforce Security Guide,Sharing Rules | Salesforce Security Guide,Create Owner-Based Sharing Rules | Salesforce Security Guide

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

[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

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.

: Visual Hierarchy

: Gestalt Principles