Free Salesforce Certified Platform User Experience Designer User-Experience-Designer Exam Questions

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 additional UX elements that should be reviewed to influence the brand experience are visual, content, and interaction design.These elements are essential for creating a consistent, engaging, and memorable user experience that reflects the company's brand identity and values12.

Visual design refers to the use of colors, shapes, typography, images, icons, and other graphical elements to create a visual hierarchy, contrast, balance, and harmony on the page13.Visual design affects the user's perception, emotion, and attention, and can communicate the brand's personality, tone, and message13.For example, Cloud Kicks can use their logo, color scheme, and font to create a recognizable and distinctive visual identity for their portal landing page4.

Content design refers to the creation, organization, and presentation of text, audio, video, and other media to convey the brand's value proposition, story, and information to the user15.Content design affects the user's understanding, interest, and trust, and can communicate the brand's purpose, benefits, and voice15. For example, Cloud Kicks can use clear, concise, and compelling headlines, subheadings, and body text to highlight their products, services, and customer testimonials on their portal landing page.

Interaction design refers to the design of the user interface elements, such as buttons, links, menus, forms, and sliders, that enable the user to interact with the page and perform tasks1.Interaction design affects the user's behavior, satisfaction, and feedback, and can communicate the brand's functionality, usability, and responsiveness1. For example, Cloud Kicks can use intuitive, consistent, and accessible navigation, search, and filtering options to help the user find what they are looking for on their portal landing page.

By reviewing and improving these UX elements, Cloud Kicks can ensure that their portal landing page delivers a positive and coherent brand experience to their users, and that their brand identity is translated into the user experience.

The 5 Elements of User Experience Design

How to Create a Brand Experience That Works With Your UX

Visual Design Basics

Use Branding Sets in Experience Builder

Content Design: What It Is and Why It Matters

[How to Write Effective Web Content for Your Experience Cloud Site]

[Interaction Design Basics]

[Designing User Interfaces for Experience Cloud Sites]

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

Component Blueprints | Salesforce Lightning Design System

Design Tokens | Salesforce Lightning Design System

Development Tools | Salesforce Lightning Design System

The best approach to enable partners to quickly browse and see their opportunities segmented by key attributes is to configure a pre-filtered opportunity list view for each key attribute with the partner group. This way, the partners can easily access the list views that show only the opportunities that match the criteria, such as closing within 2 weeks or valued at more than $100,000. Creating a custom Lightning Web Component using a data table for each key attribute (A) might be too complex and time-consuming, and it might not be compatible with the Experience Builder. Allowing each user to create a filter for each key attribute and link to the opportunities list view (B) might be too tedious and inconsistent, and it might not provide a quick and easy way to browse the opportunities.Configuring a pre-filtered opportunity list view for each key attribute with the partner group is a simple and effective solution that leverages the existing functionality of the Experience Builder and the list view component12.Reference:

List View Component | Salesforce Experience Cloud

Create and Edit List Views | Salesforce Help

To track and measure the adoption of the new process, CK should use the following Salesforce tools:

User Engagement Dashboard and Report: This tool provides insights into how users are interacting with Salesforce, such as the number of logins, page views, actions, and time spent. It can help CK identify which users are adopting the new process and which ones need more training or support.

Salesforce Surveys for user Satisfaction: This tool allows CK to create and send surveys to its customer service representatives to collect feedback on the new process, such as their satisfaction, challenges, and suggestions. It can help CK measure the impact of the new process on the user experience and satisfaction.

Chatter polls: This tool enables CK to create and post simple polls on Chatter to gather quick opinions or preferences from its customer service representatives. It can help CK engage with its users and get their input on the new process.

: User Engagement Dashboard and Report

: Salesforce Surveys for user Satisfaction

: Chatter polls

When designing the experience for a 'Case Solver' user persona, especially in the context of Cloud Kicks' Service Cloud instance, the activities to consider should revolve around the primary responsibilities and tasks of this role. For a Case Solver, these would include:

Troubleshooting customer issues: This involves identifying, analyzing, and solving problems reported by customers. The design should facilitate easy access to relevant information, tools for effective problem-solving, and a seamless workflow for diagnosing issues.

Logging activities: Keeping a detailed record of interactions, solutions provided, and any follow-up actions is crucial. The user interface should support efficient logging and tracking of activities to ensure accountability and facilitate continuous improvement in customer service.

While training other agents and editing knowledge articles (option B) and viewing the status of cases and analyzing campaign metrics (option C) are important in certain contexts, they do not directly align with the core activities of a Case Solver persona focused on direct customer support and problem resolution.

Reference: Salesforce's own documentation, such as the Salesforce Service Cloud User Guide, provides insights into designing user experiences for specific roles within the platform. It offers best practices and recommendations for optimizing the interface and workflows for various user personas, including those involved in case management and customer support.

In-app feedback is a method of collecting user feedback within the context of the product or service, without interrupting the user's workflow. It allows the UX designer to gather insights from a specific set of users at scale and measure their satisfaction, preferences, and pain points. In-app feedback can be implemented using various techniques, such as ratings, reviews, comments, suggestions, polls, or pop-ups .Reference:

: User Experience Designer Certification Prep: Module 3: Conduct User Research

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

The SLDS utility that provides the most flexible system to meet the requirements of designing a responsive page isGrid. Grid is a utility that allows you to create a layout using a series of rows and columns that house your content. Grid uses a 12-column structure that can be adjusted based on breakpoints, which are predefined screen sizes that trigger a change in the layout. Grid also supports nesting, alignment, ordering, and offsetting of the columns.By using Grid, you can create a responsive page that can adapt to different screen resolutions and devices12Reference: [Grid - Lightning Design System], [Mastering Salesforce Lightning Design System Grids and Lightning Layouts]

https://www.lightningdesignsystem.com/utilities/grid/

https://developer.salesforce.com/blogs/developer-relations/2017/04/mastering-salesforce-lightning-design-system-grids-lightning-layouts

A page header is a component that appears at the top of every page on a Digital Experience site, and usually contains the site logo, the site name, the navigation menu, and other elements that provide a consistent and recognizable look and feel for the site.A UX Designer can code the page header to update the logo for Cloud Kicks by using the Experience Builder or the Developer Console1. The Experience Builder is a point-and-click tool that allows creating and customizing the page header using predefined templates, themes, and components.The Developer Console is a code editor that allows creating and editing the page header using HTML, CSS, JavaScript, and Lightning components2. Both tools provide the option to upload and insert the new logo image file into the page header, and to adjust its size, position, and alignment.

The other two options, Visualforce pages and email templates, are not the places where the UX Designer needs to code to update the logo for Cloud Kicks.Visualforce pages are web pages that can be used to create custom user interfaces for Digital Experience sites, but they do not affect the page header, which is a separate component that can be added to any page3. Email templates are predefined layouts and content that can be used to send emails to the site users, but they do not have any impact on the site appearance or functionality.

The three inclusive design action-oriented principles are:

Recognize exclusion: Identify and understand the barriers that prevent people from accessing or using a product or experience. Exclusion can be caused by ability, context, or personal factors.

Learn from diversity: Seek out and learn from the perspectives of people who have a range of experiences, backgrounds, and identities. Diversity can be a source of inspiration and innovation.

Solve for one, extend to many: Design solutions that address the needs of a specific person or group, and then generalize them to benefit a wider audience. Solving for one can reveal hidden opportunities and create more inclusive outcomes.Reference:Explore Inclusive Design,Inclusive Design

These three features allow fields to be available when viewing a record in Salesforce.

Ahighlights paneldisplays key fields at the top of a record page in Lightning Experience. It can be customized to show the most important information for each object.

Acompact layoutdetermines which fields appear in the highlights panel, the list view hover, and the Salesforce app. It can be assigned to different record types and profiles.

Alist viewdisplays a set of records that meet specified filter criteria. It can be sorted and filtered by different fields, and users can select which fields to display in the list view.

[Customize the Highlights Panel]

[Create and Assign Compact Layouts]

[Create and Customize List Views]

The best way to ensure the end-user experience when designing a new page layout for a custom object in Salesforce is to group similar fields using sections. Sections are UI components that allow you to organize fields into logical groups and provide headings and descriptions for each group. Sections help to improve the readability, scannability, and usability of the page layout by reducing the visual clutter and providing a clear structure and hierarchy for the information. Sections also help to align the page layout with the user's mental model and expectations, as well as the business processes and workflows. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Salesforce Design System]

Including all potentially useful fields is not a good way to ensure the end-user experience when designing a new page layout for a custom object in Salesforce, because it can create a crowded and overwhelming interface that is hard to navigate and understand. It can also increase the cognitive load and the scrolling effort for the user, as well as the maintenance cost for the designer. It is better to include only the essential and relevant fields that the user needs to perform their tasks and goals, and use other methods such as related lists, tabs, or modals to display additional information. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Salesforce Design System]

Making field labels and API names identical is not a good way to ensure the end-user experience when designing a new page layout for a custom object in Salesforce, because it can create confusion and inconsistency for the user and the developer. Field labels are the text that appear on the user interface to identify the fields, while API names are the unique identifiers that are used by the system and the code to reference the fields. Field labels and API names should be different, because they have different purposes and audiences. Field labels should be clear, concise, and descriptive, using natural language and proper capitalization, punctuation, and spacing. API names should be concise, unique, and consistent, using underscores and camel case to separate words. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Salesforce Design System]

Marking all fields as required is not a good way to ensure the end-user experience when designing a new page layout for a custom object in Salesforce, because it can create frustration and annoyance for the user, as well as increase the error rate and the abandonment rate. Required fields are fields that the user must fill in before they can save or submit the record. Required fields should be used sparingly and only for the fields that are absolutely necessary for the system or the business logic. Marking all fields as required can make the user feel pressured and constrained, and force them to enter irrelevant or inaccurate data. It can also make the user miss the truly important fields, or give up on completing the record altogether. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Salesforce Design System]Reference:[UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Salesforce Design System]

To provide more intuitive access to regularly used content, a sales representative can use the following two recommendations:

Personalize the Navigation bar: The Navigation bar is the horizontal menu at the top of the Lightning Experience page that allows users to switch between different items, such as apps, objects, or utilities. Users can personalize the Navigation bar by adding, removing, or rearranging items according to their preferences and needs. For example, a sales representative can add the Accounts, Opportunities, and Reports items to the Navigation bar for quick access. To personalize the Navigation bar, users can click on the pencil icon next to the app name and use the Edit option.

Create shortcuts Favorites: Favorites are bookmarks that users can create to save links to frequently accessed pages, records, reports, dashboards, or groups in Salesforce. Users can create favorites by clicking on the star icon in the header of any page. Users can also organize their favorites into folders and access them from any device. To view or manage favorites, users can click on the Favorites icon in the header. Favorites can help users save time and navigate Salesforce more efficiently.

Dynamic Forms is a feature that allows users to customize the layout of a record detail page by placing fields and sections anywhere on the page, and applying visibility rules to show or hide them based on certain criteria. Dynamic Forms can help service agents to create user-centric, intuitive, and dynamic layouts that display only the relevant fields and sections for the reservation process. Dynamic Forms can also improve page load times and reduce the need for multiple page layouts and record types.Dynamic Forms is currently available for custom objects and some standard objects in Lightning Experience12.Reference:

Dynamic Forms

Get Started with Dynamic Forms

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