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

 The Salesforce Lightning Design System (SLDS) is a collection of resources that help you create user interfaces that are consistent with the Salesforce Lightning principles, design language, and best practices. The SLDS resources that could be used to make custom applications look, act, and sound like Salesforce are:

Blueprints and tokens: Blueprints are ready-to-use HTML and CSS UI elements that provide the foundation for Salesforce experience development. Tokens are visual design values and attributes that ensure branding and UI consistency at scale. By using blueprints and tokens, you can create custom components that follow the SLDS design standards and patterns.

Guidelines for voice and tone: Voice and tone guidelines help you write clear, concise, and consistent content that reflects the Salesforce brand personality and values. By using voice and tone guidelines, you can create custom applications that communicate effectively and respectfully with your users.

The SLDS resources that are not relevant to make custom applications look, act, and sound like Salesforce are:

Full functional components: Full functional components are pre-built Lightning components that provide out-of-the-box functionality and interactivity. They are not part of the SLDS, but rather part of the Lightning Component Library. You can use full functional components to speed up your development process, but they are not necessary to make custom applications look, act, and sound like Salesforce.

In-App Guidance: In-App Guidance is a feature that allows you to create and deliver contextual help and training to your users within your application. It is not part of the SLDS, but rather part of the Salesforce Platform. You can use In-App Guidance to enhance your user experience and adoption, but it is not essential to make custom applications look, act, and sound like Salesforce.

A Salesforce Console application is designed to optimize the user experience for service representatives who work on multiple records and tasks at the same time. The console navigation features allow the user to access multiple records and related information in a single screen, without switching back and forth between tabs or windows. The features that are relevant to the designer recommendation are:

More than one detail item can be open at a time. This allows the user to work on multiple records simultaneously and switch between them easily.

Multiple subtabs can be beneath a single parent record. This allows the user to view and access related information, such as activities, emails, notes, and attachments, without leaving the parent record.

A split list of records and individual record detail can be seen on the same screen. This allows the user to browse through a list of records, such as a queue or a report, and see the details of the selected record on the same screen.

The feature that is not relevant to the designer recommendation is:

Service representatives with lower resolution monitors will have a better user experience. This is not true, because a Salesforce Console application requires a minimum screen resolution of 1024 x 768 pixels to display properly. Users with lower resolution monitors may experience scrolling issues or truncated information.

 According to the Salesforce documentation, the number of dynamic dashboards that an organization can have depends on the edition of Salesforce that they are using. A dynamic dashboard is a dashboard that runs using the security settings of the user viewing the dashboard, so that each user sees the data according to their own access level. Dynamic dashboards are useful for sharing one common set of dashboard components to users with different levels of access, without having to create separate dashboards for each user or role. The documentation states that:

Enterprise Edition can use up to 5 dynamic dashboards

Unlimited and Performance Edition can use up to 10 dynamic dashboards

Developer Edition can use up to 3 dynamic dashboards

Additional dynamic dashboards may be available for purchase

Therefore, since Cloud Kicks has an Unlimited Edition Salesforce org, they can create up to 10 different dynamic dashboards1 References: Taking Advantage of Dynamic Dashboards | Salesforce Developers

Dynamic Actions are a feature that allows the UX Designer to customize the actions that appear on the Highlights panel of a Lightning record page based on criteria such as record status, user profile, or field value. This way, the UX Designer can declutter the Highlights panel and show only the relevant actions for each record. Dynamic Actions can be configured in the Lightning App Builder instead of the page layout editor, which gives more flexibility and control to the UX Designer. References:

Salesforce Dynamic Actions – Overview & Deep Dive Tutorial

Create Dynamic Actions in Lightning App Builder - Salesforce

Add Visibility Rules for Dynamic Pages - Trailhead

The designer should describe SLDS styling hooks as custom CSS properties that can easily style base and custom components. Styling hooks are placeholders in the SLDS style sheet that allow developers to customize the look and feel of their Lightning components by using the corresponding CSS custom properties. For example, the developer can change the background color of a button by setting the value of the --slds-c-button-brand-color-background custom property. Styling hooks are especially useful when working with web components and shadow DOM, as they enable component-level customizations without affecting the global styles. Styling hooks also provide consistency and performance benefits, as they leverage the SLDS design tokens and the native browser support for CSS custom properties. References:

: Styling Hooks - Lightning Design System

: SLDS Styling Hooks | Lightning Web Components Developer Guide | Salesforce Developers

: SLDS Styling hooks in Lightning web components - Forcetrails

The designer should describe the Salesforce Lightning Design System (SLDS) styling hooks as using standard CSS properties to easily style base and custom components. SLDS styling hooks allow developers to quickly and easily apply CSS classes to HTML elements, enabling consistent styling across both base and custom components. This allows developers to quickly and easily apply branding and styling to their Lightning Web Components, without needing to write custom CSS. For more information about SLDS styling hooks, please see the following Salesforce documentation: https://developer.salesforce.com/docs/component-library/documentation/lwc/lwc.use_slds_styles_hooks

When the Service team at Cloud Kicks faces difficulty due to an overload of list views, the most effective way to improve their experience is by decluttering the list views to make relevant ones easier to find. This can be achieved by:

Streamlining the List Views: Removing less frequently used or irrelevant list views from the public view helps in reducing clutter and focusing on the most pertinent information. This streamlining process makes navigation more intuitive and efficient for the service team members.

Options B (Updating Sharing Rules) and C (Allowing users to manage public list views) might help in managing access to records and customization, but they do not directly address the issue of having too many list views, which is the primary concern impacting the team's ability to find relevant information quickly.

The Salesforce Lightning Design System (SLDS) reflects the patterns and components that underpin the Salesforce product. These patterns and components provide a unified language and consistent look and feel when designing apps and products within the Salesforce ecosystem. The Lightning Experience UI, which SLDS represents, was crafted using four core design principles. We encourage you to keep them in mind as you develop your applications. They are1:

Clarity — Eliminate ambiguity. Enable people to see, understand, and act with confidence.

Efficiency — Streamline and optimize workflows. Intelligently anticipate needs to help people work better, smarter, and faster.

Consistency — Create familiarity and strengthen intuition by applying the same solution to the same problem.

Beauty — Demonstrate respect for people’s time and attention through thoughtful and elegant craftsmanship. References: Introduction to the Salesforce Lightning Design System

The best place for the team to explore Lightning component code, documentation, and specifications is the Components Library on developer.salesforce.com1. The Components Library is the Lightning components developer reference, where the team can find code samples, SDKs, tools, metadata coverage information, and a developer guide for Lightning Web Components1. The team can also use the live code environment to code their first Lightning web component and see the results in real time2. Salesforce Extensions for VS Code (A) is a powerful tool for developing Lightning components, but it is not a source of code, documentation, and specifications. Design Tokens on SLDS website (B) are a way to store and maintain consistent design attributes across different platforms, but they are not specific to Lightning Web Components. References:

Components Library on developer.salesforce.com

Get Started Coding | Lightning Web Components Developer Guide

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.

A/B testing is a testing method that compares two versions of a user interface design to measure which one performs better in terms of a specific goal, such as form completions. A/B testing can help the UX Designer to evaluate the effectiveness of different design elements, such as layout, color, typography, copy, etc. A/B testing can also help the UX Designer to optimize the conversion rate of the landing page and increase the number of leads generated. References: [A/B Testing], [Optimize Your Landing Pages with A/B Testing]