Pass the Salesforce Salesforce Designers User-Experience-Designer Questions and answers with CertsForce

The conceptual approach of desirable, feasible, and viable describes how to evaluate design solutions based on three criteria:

Desirable: The solution meets the needs and wants of the users and stakeholders.

Feasible: The solution can be implemented with the available resources and technology.

Viable: The solution can generate value and sustain itself in the market and environment. By incorporating human-centered design, CK is aiming to create design solutions that are desirable for its Sales team and customers, feasible with the Salesforce platform and tools, and viable for its business goals and strategy. References:

[1]: UX Designer Certification Prep: Design Thinking, Unit 3: Ideate

[2]: UX Designer Certification Prep: Design Thinking, Unit 4: Prototype and Test

 T-shirt sizing is a methodology that can be used to roughly estimate the work required for each item in a sprint backlog. It involves assigning a size category (such as XS, S, M, L, XL) to each item based on its complexity, effort, and uncertainty. T-shirt sizing is a relative estimation technique that allows the team to compare items and prioritize them accordingly. It is also a quick and easy way to get a high-level overview of the scope of work without getting into too much detail. References:

[UX Designer Certification Prep: Agile UX]

[Agile Estimation Techniques: A True Estimation in an Agile Project]

These two design considerations should be made when planning for a customer support site in experience builder that will be internationalized across 12 different countries. They are related to the principles of internationalization and localization, which are the processes of designing and adapting a product or service to meet the needs and preferences of users in different cultures, languages, and regions. By taking these considerations into account, a UX designer can create a site that is consistent, usable, and appealing for a global audience.

Country may read text in a different direction (right to left) vs (left to right) and layouts will need to be adjusted: This consideration is related to the principle of bidirectionality, which is the ability of a product or service to support both left-to-right (LTR) and right-to-left (RTL) languages, such as Arabic, Hebrew, Persian, and Urdu. These languages have different writing systems, text alignment, and reading order than LTR languages, such as English, French, Spanish, and German. Therefore, a UX designer needs to adjust the layouts of the site to accommodate both LTR and RTL languages, such as by using flexible grids, mirroring elements, and avoiding fixed positions. This way, the site can provide a natural and intuitive reading experience for users in different countries.

Colors may have different cultural meanings in different countries, changing the intent of UI elements: This consideration is related to the principle of cultural sensitivity, which is the awareness and respect of the cultural differences and preferences of users in different countries. Colors are one of the most important aspects of visual design, as they can convey emotions, moods, messages, and actions. However, colors can also have different cultural meanings and associations in different countries, which can affect how users perceive and interact with the site. For example, red can mean danger, passion, or luck, depending on the country. Therefore, a UX designer needs to choose colors that are appropriate and consistent with the intended meaning and purpose of the UI elements, such as buttons, icons, labels, and alerts. This way, the site can avoid confusion, misunderstanding, or offense for users in different countries.

Visibility of system status is the usability heuristic that is being used in this case. Visibility of system status means that the system should always keep users informed about what is going on, through appropriate feedback within reasonable time1. One way to apply this heuristic is to use visual indicators to let users know which form fields are required, such as asterisks, labels, or colors. This helps users to understand the expectations and requirements of the system, and to avoid errors or confusion. By providing clear and timely feedback, the system enhances the user experience and satisfaction. References: Learn About User Experience Design Unit | Salesforce Trailhead, [10 Usability Heuristics for User Interface Design], Salesforce User Experience (UX) Designer Certification Guide & Tips

To document user goals, common tasks, and pain points for a new service experience, the tool that a UX Designer should use is user personas. User personas are fictional representations of the target users, based on real data and research. User personas help the designer to understand the needs, motivations, behaviors, and expectations of the users, as well as their challenges and frustrations. User personas can also help the designer to prioritize features, create scenarios, and design solutions that are relevant and meaningful for the users. References: : UX Designer Certification Prep: Designing for User Research | Trailhead : User Personas | Salesforce Developer Guide

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.

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.

Accordions are collapsible sections that can be used to separate different content areas. By using accordions, users can quickly navigate through the page and easily find thecontent that they need. The use of accordions also ensures that screen readers can access the content within each section, reducing the need for additional navigation. Additionally, a Lightning Console layout can be used to organize components, but this layout is optimized for customer service agents and not necessarily for screen reader users. Placing components in adjacent tabs or stacking them on the same page can make the page difficult to navigate and can make it difficult for screen readers to understand the page. For more information, see the Salesforce Accessibility Guide (https://help.salesforce.com/articleView?id=accessibility_overview.htm &type=5).

 According to the Salesforce Lightning Design System, accordions are a good way to organize components on a page for screen reader-assisted accessibility. Accordions allow users to expand and collapse sections of content, which can help reduce cognitive load and scrolling. Accordions also provide a clear heading structure and keyboard navigation for each section1. The other options are not recommended for screen reader-assisted accessibility, as they can create confusion, clutter, or inefficiency for users who rely on auditory feedback. For example, switching to a Lightning Console layout can make it harder for users to navigate between tabs and subtabs2. Placing components in adjacent tabs can also increase the number of keystrokes and commands needed to access the information3. Stacking components on the same page can create a long and overwhelming page that requires excessive scrolling and reading4.

When a lead is converted in Salesforce, three new records are typically created: a contact, an account, and an opportunity. A contact is a person who is associated with an account and has a role in a sales process. An account is a company or organization that is a potential or existing customer. An opportunity is a sales deal that is in progress or has been closed. These records are linked together and use the information from the lead record. The lead record becomes read-only and is marked as converted. References:

Converting Leads

Lead Conversion in Salesforce

The design that the UX Designer at Cloud Kicks should use to make the website size and content adapt to the screen size, platform and orientation is responsive. Responsive web design is a web design approach that uses HTML and CSS to automatically resize, hide, shrink, or enlarge, a website, to make it look good on all devices (desktops, tablets, and phones) 1. Responsive web design is not a program or a JavaScript, but a set of best practices that include using media queries, flexible grids, fluid images, and breakpoints to create a layout that can respond to any device being used to view the content 2. Responsive web design is one of the learning objectives for the Salesforce User Experience Designer certification 3. References: [Responsive Web Design Introduction], [Responsive design - Learn web development], [Salesforce Certified User Experience Designer Exam Guide] https://www.w3schools.com/html/html_responsive.asp

https://www.w3schools.com/Css/css_rwd_intro.asp

To optimize the relationship between two objects in Salesforce, such as Container and Container Bids, where there is a need for a tight relationship and cascading delete functionality, a Master-Detail relationship is most suitable. This type of relationship has the following characteristics:

Cascading Delete: When a record in the master (or parent) object is deleted, all related detail (or child) records are automatically deleted. This ensures data integrity and aligns with the requirement that Container Bids should be deleted when their associated Container is deleted.

Tight Coupling: A Master-Detail relationship creates a strong linkage between the two objects, where the detail (child) record's existence is dependent on the master (parent) record. This is appropriate for scenarios where the child record should not exist without its parent.

Options B (Hierarchical Lookup) and C (Many-to-one Lookup) do not provide the same level of dependency and cascading delete functionality inherent in a Master-Detail relationship.