Free Practice Questions for Salesforce User-Experience-Designer Exam

The best place on the SLDS website for the designer to find accessible HTML and CSS used to create components along with implementation guidelines is the Component Blueprints1. Component Blueprints are framework-agnostic, accessible HTML and CSS that provide the basic structure and style for Lightning components1. The designer can use the Component Blueprints to create custom Lightning Web Components that are consistent with the Lightning Design System. Design Tokens (B) are not the best place to find HTML and CSS, as they are variables that store design attributes, such as colors, fonts, and spacing2. Development Tools © are not the best place to find implementation guidelines, as they are tools and resources that help developers build and test Lightning components, such as VS Code extensions, LWC recipes, and Playground3. References:

Component Blueprints | Salesforce Lightning Design System

Design Tokens | Salesforce Lightning Design System

Development Tools | Salesforce Lightning Design System

To ensure new Salesforce users are given the appropriate onboarding experience, a UX Designer should use the following two on-App Guidance customizations:

Specify prompt scheduling: This allows the designer to control when and how often the prompts appear to the users, based on criteria such as start and end dates, frequency, and snooze duration. This way, the designer can tailor the onboarding experience to the users’ needs and preferences, and avoid overwhelming or annoying them with too many or irrelevant prompts.

Set prompt permissions: This allows the designer to target the prompts to specific user groups, based on profiles and permissions. This way, the designer can ensure that the prompts are relevant and useful to the users, and avoid showing them information that they do not need or have access to.

A wireframe prototype is a low-fidelity representation of the content and structure of a new feature, without any visual design or branding elements. It is used to test the usability and functionality of the feature with the user, and to gather feedback and iterate on the design. A wireframe prototype can be created using tools like Sketch, Figma, or Adobe XD, and can be interactive or static. References:

[Salesforce Certified User Experience Designer Exam Guide], Section 2.2: Design and test prototypes

[UX Designer Certification Prep: Prototyping], Unit 2: Wireframes and Prototypes

[Prepare for Your UX Designer Credential], Trailmix: Prototyping

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 provides UI components, icons, fonts, colors, and more that follow the best practices and accessibility standards of Salesforce. One of the features of SLDS is the ability to create custom themes that reflect the brand identity and personality of a company or an app. Custom themes can be implemented using design tokens, which are variables that store the values of the UI elements, such as colors, sizes, spacing, fonts, etc. Design tokens can be overridden or customized to change the appearance of the UI components without modifying the CSS or HTML code. To implement the company colors in all UI components, such as buttons and icons, using a custom theme, the UX designer should use the design tokens prefixed with “brand”, such as $brand-primary, $brand-secondary, $brand-accessible, etc. These design tokens control the color scheme of the UI components and can be assigned the values of the company colors. For example, to change the color of the primary button to the company’s blue color, the UX designer can use the following design token:

$brand-primary: #0070d2;

 A standard person account object is the best option for representing the bank’s customers within its Salesforce instance. A person account is a type of account that represents an individual rather than a company. Person accounts are a hybrid of the account and contact objects, combining their characteristics into one. They allow the bank to store information that applies to humans, such as first and last names, email, phone, address, etc. When a person account is created, a contact is automatically created and associated with the account. Person accounts are the Salesforce official model for representing an individual and can be used alongside business accounts for B2B and B2C activities. In Financial Services Cloud, person accounts can be used for a simplified, customizable user experience1. A person account can also have related opportunities, which are potential sales or revenue-generating events. This way, the financial advisor can access a customer’s record and see all potential business opportunities related to each individual customer2.

The other options are not suitable for the bank’s scenario. A standard lead object is a prospect or potential customer who has expressed interest in the bank’s products or services, but has not yet qualified as a sales opportunity. A lead can be converted into an account, a contact, and an opportunity when it is ready to be pursued3. However, the bank does not need to use leads to track its customers, as they are already existing customers who have accounts with the bank. A standard opportunity object is a sales or revenue-generating event that is related to an account. An opportunity can have multiple stages, products, amounts, and probabilities of closing. An opportunity can also be linked to a campaign, which is a marketing initiative to generate leads or contacts4. However, the bank cannot use opportunities alone to represent its customers, as they are not standalone objects, but rather depend on accounts. A standard account object is a company or organization that the bank does business with. An account can have multiple contacts, which are the people who work at the account and interact with the bank. An account can also have related opportunities, cases, activities, and other records5. However, the bank does not have any corporate or business customers at this time, so using standard accounts would not reflect the nature of its individual customers.

A usability study is a method of evaluating how easy and intuitive a product or service is to use by observing real users performing specific tasks. It can help identify usability issues, user needs, and user satisfaction. One of the first steps when planning a usability study is to define the goals of the study, which are the questions that the UX designer wants to answer or the hypotheses that they want to test. The goals of the study will guide the selection of the participants, the tasks, the metrics, and the methods of the study. For example, if the goal of the study is to find out how users navigate the Experience Cloud site, the UX designer might choose to use a task-based usability test with eye-tracking and think-aloud techniques. References:

: User Experience Designer Certification Prep: Module 4: Analyze User Research Data

: User Experience Designer Certification Prep: Module 6: Validate User Interfaces

 The best Salesforce solutions for Cloud Kicks to deliver consistently branded content at every touchpoint are Distributed Marketing and Journey Builder. Distributed Marketing allows individual agents to send personalized and compliant messages to their customers, using pre-approved templates and content created by the corporate marketing team1. Journey Builder enables the marketing team to design and automate customer journeys across channels and devices, using data and analytics to optimize the customer experience2. Email Builder and Customer 360 (B) are not sufficient to ensure consistent branding and communication, as they only cover email marketing and customer data integration, respectively. Service Cloud and Letterhead © are also not the best solutions, as they only focus on customer service and email formatting, respectively. References:

Distributed Marketing | Salesforce

Journey Builder | Salesforce

The Path’s Guidance for Success sections can include the following two elements:

Images and Links: Images and links can be used to provide visual cues and additional resources for the sales representatives. For example, an image of a checklist or a link to a best practice document can help the reps complete the required tasks at each stage. Images and links can be added using the rich text editor in the Path Settings page.

Rich Text: Rich text can be used to provide text-based guidance, such as tips, reminders, instructions, or motivational messages. For example, a rich text guidance can tell the reps what information they need to gather from the customer or what actions they need to take to move the opportunity forward. Rich text can be formatted using the rich text editor in the Path Settings page. References:

: Set Up a Path

: Considerations and Guidelines for Creating Paths

: Optimize Sales Processes with Path in Salesforce

The two elements that can be used in the Path's Guidance for Success section are Images and Links and Rich Text. Images and Links can be used to provide visual elements to the Guidance for Success section, while Rich Text can be used to provide text-based explanations and instructions. In addition, a Progress Indicator can be used to show the user's progress through the Path.

Images and Links can be used to provide visual elements to the Guidance for Success section. For example, if the user needs to read an article, a link to the article can be included, as well as an image of the article cover. Similarly, if the user needs to view a video, a link to the video and an image of the video can be included.

Rich Text can be used to provide text-based explanations and instructions. This can include explanations of what the user should be doing at each stage of the Path, as well as any other helpful information.

Finally, a Progress Indicator can be used to show the user's progress through the Path. This can help the user understand where they are in the Path and how far they have left to go.

The discovery phase is a crucial stage in any UX design project, as it helps to understand the user needs, business goals, and technical constraints of the problem1. The discovery phase 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 phase are artifacts that synthesize and communicate the findings and insights from the research. Some of the practices that should be considered for planning out the strategy for an upcoming discovery phase are:

Gather insight from end users: One of the main objectives of the discovery phase is to empathize with the end users and understand their goals, motivations, pain points, behaviors, and preferences. This can be done by conducting user research, such as interviews, surveys, focus groups, or usability tests, to collect qualitative and quantitative data from the target audience3. Gathering insight from end users helps to validate the assumptions and hypotheses about the problem and the solution, as well as to identify the user requirements and expectations for the design.

Establish the research plan and timeline: Before conducting any user research, it is important to establish a clear and realistic research plan and timeline. The research plan should define the research objectives, questions, methods, participants, and deliverables. The research timeline should specify the duration, frequency, and sequence of the research activities, as well as the deadlines and milestones for the deliverables4. Establishing the research plan and timeline helps to ensure that the discovery phase is well-organized, efficient, and effective, as well as to communicate the expectations and responsibilities to the stakeholders and the team members.

Understand the problem before moving to solutions: Another key practice for the discovery phase is to focus on understanding the problem before jumping to solutions. This means defining the problem statement, the scope, and the constraints of the project, as well as identifying the root causes, the symptoms, and the impacts of the problem. Understanding the problem before moving to solutions helps to avoid wasting time and resources on creating solutions that do not address the real needs and pain points of the users, or that are not feasible or viable for the business or the technology.

The other two options, considering platform-based before custom solutions and determining user acceptance criteria, are not practices that should be considered for planning out the strategy for an upcoming discovery phase. Considering platform-based before custom solutions is a practice that belongs to the design phase, not the discovery phase, as it involves choosing the best solution option based on the user research findings and the design principles5. Determining user acceptance criteria is a practice that belongs to the testing phase, not the discovery phase, as it involves defining the criteria that the solution must meet to be accepted by the users and the stakeholders6.

The best onboarding design practice for Cloud Kicks would be to identify the message, audience, and purpose for content. This would help them tailor the content to the different needs and preferences of their employees, and provide them with the most relevant and useful information. Providing written help documentation as the single source of truth for learning about new features (A) might not be engaging or effective for all users, especially those who prefer visual or interactive learning. Creating pop-ups to give users a full visualization of a product © might be intrusive or overwhelming for some users, and might not explain the benefits or features of the product clearly. Identifying the message, audience, and purpose for content (B) is a key step in creating user-centered onboarding design, as it helps to define the goals, scope, and tone of the content, and to align it with the user’s needs, expectations, and motivations. References:

[UX Designer Certification Prep: Onboarding Design]

[UX Designer Certification Prep: Content Strategy]

[Salesforce Certified User Experience Designer Exam Guide]