
[2026] Pass Salesforce Plat-UX-101 Premium Files Test Engine pdf - Free Dumps Collection
New 2026 Realistic Plat-UX-101 Dumps Test Engine Exam Questions in here
NEW QUESTION # 12
Cloud Kicks (CK) wants to better deliver products to its customers. CK's UX Designer has an innovative solution but is struggling to get the team to visualize where and why it fits into what the customer does.
Which technique should be used?
- A. Personas
- B. High-fidelity Prototype
- C. Storyboards
Answer: C
Explanation:
A storyboard is a visual representation of a user's journey with a product or service. It shows how the user interacts with the product or service in a specific context, what their goals and pain points are, and how the product or service solves their problems or meets their needs.A storyboard typically consists of a series of sketches or illustrations that depict the user's actions, thoughts, and emotions at each step of the journey1.
A storyboard is the most suitable technique for CK's UX Designer to use in this case, because it can help them communicate their innovative solution to the team and show where and why it fits into what the customer does. A storyboard can also help the UX Designer to validate their assumptions, test their ideas, and get feedback from the team and the customers.A storyboard can also inspire the team to generate more ideas and solutions, and align them with the user's perspective2.
Personas are fictional characters that represent the potential users of a product or service. They are based on user research and data, and they describe the user's demographics, behaviors, motivations, goals, and frustrations. Personas are useful for understanding the user's needs and expectations, and for designing products or services that cater to them. However, personas alone are not enough to show how the user interacts with the product or service in a specific context, or how the product or service solves their problems or meets their needs.Personas need to be complemented with other techniques, such as scenarios, user stories, or storyboards, to illustrate the user's journey3.
A high-fidelity prototype is a realistic and interactive simulation of a product or service. It mimics the look, feel, and functionality of the final product or service, and it can be used for testing and evaluation purposes. A high-fidelity prototype is useful for demonstrating the features and benefits of a product or service, and for getting feedback from the users and stakeholders. However, a high-fidelity prototype is not the best technique for showing where and why a product or service fits into what the customer does, as it focuses more on the details and specifics of the product or service, rather than the context and situation of the user. A high-fidelity prototype is also more time-consuming and resource-intensive to create than a storyboard, and it may not be necessary at the early stages of the design process.
NEW QUESTION # 13
A UX Designer is limited to one standard Order record page layout in Sales Cloud. It is shared between internal and external users.
Which page layout feature should be used to control the visibility between users?
- A. Audience Targeting
- B. Field-Level Security
- C. Dynamic Forms
Answer: A
Explanation:
Audience targeting is a page layout feature that allows admins to create different versions of a Lightning page for different audiences, such as user profiles, roles, or permissions. Audience targeting can be used to control the visibility of the entire page or specific components on the page, such as tabs, fields, or sections.Audience targeting can help create personalized and relevant experiences for different types of users, and reduce the need for multiple page layouts1.
Audience targeting is the most suitable feature for the UX Designer to use in this case, because it can help them customize the Order record page layout for internal and external users, without creating separate page layouts. For example, the UX Designer can use audience targeting to show or hide certain fields, sections, or tabs based on the user's profile or permission set. This way, the UX Designer can ensure that each user sees only the information that is relevant and appropriate for them.
Field-level security is a feature that allows admins to restrict the access and editability of fields for different users, based on their profiles or permission sets. Field-level security can help protect sensitive or confidential data, and enforce data quality and integrity. However, field-level security does not affect the visibility of fields on the page layout, only the access and editability.Field-level security also does not apply to other components on the page, such as tabs or sections2.
Dynamic forms is a feature that allows admins to add, group, and reorder fields and sections on a Lightning page using the Lightning App Builder. Dynamic forms can help create flexible and dynamic page layouts that can adapt to different contexts and scenarios. Dynamic forms also support visibility rules, which can be used to show or hide fields or sections based on filters or conditions. However, dynamic forms are not available for all standard objects, and they do not support audience targeting.Dynamic forms also do not affect the visibility of other components on the page, such as tabs34.
NEW QUESTION # 14
A UX Designer needs to declutter the Highlights panel for a custom object's Lightning page. The team that uses this object explained there are too many action buttons; only specific actions are used for each status of the record.
Which Lightning Record Page feature should be used to solve this problem?
- A. A Dynamic Actions
- B. Audiences
- C. Dynamic Forms
Answer: A
Explanation:
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.Reference:
Salesforce Dynamic Actions - Overview & Deep Dive Tutorial
Create Dynamic Actions in Lightning App Builder - Salesforce
Add Visibility Rules for Dynamic Pages - Trailhead
NEW QUESTION # 15
Cloud Kicks marketing development representatives need to process incoming leads. Understanding the typical lead to opportunity is essential to the design.
Which three new records would typically be created when they convert a lead?
Choose 3 answers
- A. Converted Lead
- B. Account
- C. Activity
- D. Contact
- E. Opportunity
Answer: B,D,E
Explanation:
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.Reference:
Converting Leads
Lead Conversion in Salesforce
NEW QUESTION # 16
A UX Designer has recently released a feature on experience Cloud and wants to know if the feature was successful and track usability over time.
Which research methodology should be used?
- A. Quantitative
- B. Qualification
- C. Quantizing
- D. Qualitative
Answer: A
Explanation:
Quantitative research methodology should be used to measure the success and usability of a feature on Experience Cloud. Quantitative research involves collecting and analyzing numerical data that can be measured, compared, or statistically tested. Quantitative research can help answer questions such as:
How many users are using the feature?
How often are they using it?
How long does it take them to complete a task with the feature?
How satisfied are they with the feature?
How does the feature affect key performance indicators, such as conversion rates, retention rates, or revenue?
Quantitative research methods can include surveys, analytics, A/B testing, usability testing, and benchmarking. These methods can provide objective and reliable data that can be used to evaluate the impact and effectiveness of a feature on Experience Cloud.
Qualitative research methodology, on the other hand, involves collecting and analyzing non-numerical data that can reveal users' attitudes, behaviors, motivations, and preferences. Qualitative research can help answer questions such as:
Why are users using or not using the feature?
What are their pain points, needs, and goals with the feature?
How do they feel about the feature?
What are their expectations and feedback for the feature?
How does the feature fit into their context and workflow?
Qualitative research methods can include interviews, focus groups, observations, diary studies, and card sorting. These methods can provide rich and detailed insights that can be used to understand the user experience and identify opportunities for improvement.
Both quantitative and qualitative research methods are valuable for UX design, but they serve different purposes and answer different types of questions. In this case, the UX designer wants to know if the feature was successful and track usability over time, which are questions that can be best answered by quantitative research methods.
NEW QUESTION # 17
A UX Designer at Cloud Kicks is planning out the company's website redesign using Experience Cloud and will help guide discovery.
Which three outputs of the discovery process should be prepare
Choose 3 answers
- A. User Personas
- B. High-Fidelity Mock-ups
- C. High-Level Wireframes
- D. Journey Maps
- E. interactive Prototypes
Answer: A,C,D
Explanation:
The discovery process is a crucial phase in any UX design project, as it helps to understand the user needs, business goals, and technical constraints of the problem1.The discovery process 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 process are artifacts that synthesize and communicate the findings and insights from the research. Some of the common outputs of the discovery process are:
User personas: These are fictional representations of the target users, based on real data and insights, that describe their goals, motivations, pain points, behaviors, and preferences3. User personas help to empathize with the users and design solutions that meet their needs and expectations.
Journey maps: These are visualizations of the user's end-to-end experience with a product or service, from the initial trigger to the final outcome4. Journey maps help to identify the user's actions, thoughts, emotions, pain points, and opportunities for improvement at each stage of the journey.
High-level wireframes: These are low-fidelity sketches or diagrams that show the basic layout, structure, and functionality of the website or app. High-level wireframes help to define the information architecture, navigation, and content hierarchy of the solution, as well as test the usability and feasibility of the design concepts.
These three outputs are essential for planning out the website redesign using Experience Cloud, as they help to define the user requirements, the user flow, and the user interface of the solution. The other two options, interactive prototypes and high-fidelity mock-ups, are not outputs of the discovery process, but rather of the design and testing phases. Interactive prototypes are clickable simulations of the website or app that allow users to interact with the functionality and features of the solution. High-fidelity mock-ups are realistic and detailed representations of the website or app that show the final look and feel of the solution, including the colors, fonts, images, and icons. These two outputs are created after the discovery process, based on the feedback and validation from the user testing sessions.
For the UX Designer at Cloud Kicks, thethree outputs of the discovery process that should be prepared are User Personas, Journey Maps, and High-Level Wireframes. User Personas are fictional characters that represent a target audience for the website, and are used to help guide the website design. Journey Maps are diagrams that illustrate the user's experience as they navigate the website, and provide insights into how the user interacts with the website. High-Level Wireframes are simple sketches of the website layout, and are used to organize the website's content and design elements. Interactive Prototypes and High-Fidelity Mock-ups are not necessary outputs of the discovery process, as they are more detailed representations of the design that come later in the design process. For more information, see the Salesforce Experience Cloud documentation (https://help.salesforce.com/articleView?id=experience_cloud_overview.htm&type=5).
NEW QUESTION # 18
A UX Designeris analyzing their Experience Cloud site, enabled for Knowledge articles, and is using the Featured Topic component to display content.
Which UI configuration should be used to further individualize each featured topic?
- A. Add a description displayed onmouse hover further description each topic.
- B. Select and upload SVG Icons that represent each featured topic.
- C. Add a description under the topic label further describing each topic.
- D. Select and upload images that represent each featured topic.
Answer: D
Explanation:
The UI configuration that should be used to further individualize each featured topic is toselect and upload images that represent each featured topic. This option allows the UX Designer to customize the appearance of the Featured Topic component and make it more visually appealing and engaging for the users. The images can help to convey the meaning and relevance of each topic and attract the users' attention. The images can also create a consistent and branded look for the Experience Cloud site.
1: Featured Topic Component
2: Customize the Featured Topic Component
This allows users to easily distinguish between different topics and quickly scan for relevant topics. Salesforce documentation on the Featured Topics component states that "You can add a description for each featured topic, which appears in the user interface below the topic label" [1].
[1]https://help.salesforce.com/articleView?id=knowledge_articles_sites_featured_topic.htm&type=5
NEW QUESTION # 19
Cloud Kicks (CK) has a new Portal landing page built with Experience Builder. Upon review, CK does not think the company's brand experience is translated into the user experience; however, CK does confirm the Theme was set up correctly.
Which additional UX elements should be reviewed to influence the brand experience?
- A. Visual Design, Harmony, and Responsiveness
- B. Shapes, Interaction Design, and Typography
- C. Visual, Content, and Interaction Design
Answer: C
Explanation:
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]
NEW QUESTION # 20
An organization must be digitally accessible to enable social opportunity.
What are three core principles of Web Content Accessibility Guidelines (WCAG)?
Choose 3 answers
- A. Abundant
- B. Operable
- C. Delightful
- D. Robust
- E. Understandable
Answer: B,D,E
Explanation:
These are three of the four core principles of Web Content Accessibility Guidelines (WCAG), which provide a set of standards and best practices for making web content accessible to people with disabilities. The fourth principle isPerceivable, which means that the information and user interface components must be presented in ways that users can perceive. The principles are further divided into 13 guidelines and three levels of conformance (A, AA, and AAA).Reference:
[Web Content Accessibility Guidelines (WCAG) Overview]
[WCAG 2.1 at a Glance]
NEW QUESTION # 21
A UX Designer is using the human-centered design approach to redesign a portal that medical staff use to report on patient demographics.
Which activity should come first in the process?
- A. Observing the medical staffwhile they use their existing portal
- B. Writing technical requirements for how the portal should function
- C. Designing a mockup of how the new portal will look
- D. Estimating the cost to complete development of the portal
Answer: A
Explanation:
The human-centered design approach is a problem-solving technique that puts real people at the center of the development process, enabling designers to create products and services that resonate and are tailored to the audience's needs.The human-centered design approach typically involves four stages: clarify, ideate, develop, and implement1. The first stage, clarify, is dedicated to collecting data and observing the users to clarify the problem and how to solve it. Rather than developing products based on assumptions, designers conduct user research and assess user needs to determine what the users want. The clarify stage requires empathy-the capability of understanding another person's experiences and emotions.Designers need to consider the users' perspectives and ask questions to determine what products they're currently using, why and how they're using them, and the challenges they're trying to solve2.
Therefore, the activity that should come first in the human-centered design process is observing the medical staff while they use their existing portal. This activity will help the UX designer to understand the context, the goals, the pain points, and the preferences of the medical staff, as well as to identify the opportunities for improvement and innovation. The other activities, such as estimating the cost, writing technical requirements, and designing a mockup, belong to the later stages of the human-centered design process, after the problem and the user needs have been clearly defined.
The first activity inthe process when using a human-centered design approach to redesign a portal that medical staff use to report on patient demographics should be observing the medical staff while they use their existing portal. This is a critical step in the process, as ithelps to identify user needs, preferences, and behaviors so that the design of the new portal can be tailored to meet their specific needs.
Observing the medical staff while they use the portal will help to identify any existing problems and highlightareas where the portal can be improved. This can include issues with usability, functionality, and accessibility. Additionally, observing how the medical staff interact with the portal can help to identify any potential areas of improvement and uncover anyhidden requirements or user needs.
NEW QUESTION # 22
Cloud Kicks wants its Salesforce app to represent company branding and comply with Web Content Accessibility Guidelines (WCAG) 2.1.
What should they consider about themes and branding?
- A. There is a default WCAG complaint Salesforce color theme; only brand color can be updated.
- B. Salesforce automatically updates the selected brand color to make it accessible; this should overridden to select the colors manually.
- C. The color palette is auto-generated based on the brand color to be WCAG compliant.
Answer: C
Explanation:
Themes and branding allow Salesforce app developers to customize the look and feel of their apps to match their company's branding and accessibility standards. One of the features of themes and branding is the ability to select a brand color, which is the primary color used for buttons, links, and highlights. Salesforce automatically generates a color palette based on the brand color, which includes accessible colors that meet the WCAG 2.1 contrast ratio guidelines. This ensures that the app is visually appealing and accessible to users with different color vision abilities. Developers can also customize other aspects of the theme, such as the logo, page background, and default font.[Themes and Branding Basics], [Accessibility in Salesforce]
NEW QUESTION # 23
A UX Designer is going to create a custom app for a new team of service agents.
Which three parts of the user interface could be customized?
Choose 3 answers
- A. Tabs within the apps's navigation bar
- B. Details to be shown in the records highlights panels
- C. Page layouts of the records
- D. Opportunity lead scoring
- E. Relationship between standard objects
Answer: A,B,C
Explanation:
To create a custom app for a new team of service agents, a UX Designer could customize the following parts of the user interface:
Tabs within the app's navigation bar: This allows the UX Designer to select which tabs are visible and accessible for the app users, such as Accounts, Contacts, Cases, etc. It can help the UX Designer to tailor the app to the specific needs and tasks of the service agents.
Page layouts of the records: This enables the UX Designer to control how the fields and related lists are arranged and displayed on the record detail pages, such as the Case page layout. It can help the UX Designer to optimize the information architecture and usability of the record pages for the service agents.
Details to be shown in the records highlights panels: This allows the UX Designer to choose which fields and actions are shown in the highlights panel at the top of the record pages, such as the Case Number, Status, Priority, etc. It can help the UX Designer to emphasize the most important and relevant information and actions for the service agents.
1: Tabs within the app's navigation bar
2: Page layouts of the records
3: Details to be shown in the records highlights panels
NEW QUESTION # 24
After conducting user interviews, a UX Designer finds that an equal amount of users prefer to use the Comfy density setting as the Compact density setting while viewing record details.
Which approach should be avoided by developers when building custom components to make sure their components take advantage of this setting?
- A. Using existing Lightning Components such as the card or page header
- B. Using the varSpacingMedium design token in CSS to set spacing
- C. Using REM_based spacing values when styling components.
Answer: C
Explanation:
When developers are building custom components in Salesforce and need to ensure that these components adapt to user preferences for density settings (Comfy or Compact), they should avoid using REM-based spacing values. This is because REM-based spacing does not automatically adjust based on the density setting chosen by the user, leading to a lack of consistency with the rest of the Salesforce UI, which does adapt to these settings. Instead, developers should:
A) Use the varSpacingMedium design token in CSS, as Salesforce Lightning Design System (SLDS) design tokens are context-aware and can adjust their values based on the density setting, ensuring a consistent user experience across different user preferences.
C) Use existing Lightning Components such as the card or page header, which are pre-built to adapt to density settings, ensuring that custom components align with the overall Salesforce UI and respect user settings for density.
Reference:Salesforce Lightning Design System (SLDS) documentation provides guidelines on using design tokens and building responsive components that respect user settings like density preferences. You can find more information on the official Salesforce Developers website or the SLDS documentation section.
NEW QUESTION # 25
A UX designer is creating a customer support site in experience builder that will internationalized across the 12 different countries Which two designs considerations should bemade when planning for the site
- A. colors may have different cultural meanings in different countries, changing the intent of UI elements
- B. colors may have different contrast ratios in some countries and need adjusted contrast for proper visibility by users
- C. Country flags used as links to adjust languages provide an ideal way to switch between locals orlanguages for users
- D. Country may read text is a different direction (right to left) vs (left to right) and layouts will need to be adjusted
Answer: A,D
Explanation:
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.
Preparing a Global Design: Internationalization (i18n) Guide
Internationalization - Globalization | Microsoft Learn
Localization vs. Internationalization - World Wide Web Consortium (W3C)
NEW QUESTION # 26
Cloud Kicks (CK) is going mobile and wants to ensure its Salesforce app aligns with company branding.
Which element could be customized in the Salesforce app to match CK's branding?
- A. Brand color and loading page logo
- B. Search bar layout and loading page background
- C. Background image and focus link color
Answer: A
Explanation:
The Salesforce app allows administrators to customize the brand color and the loading page logo to match the company's branding. The brand color affects the key user interface elements such as the header, buttons, and search bar. The loading page logo is the image that appears after a mobile user logs in. These elements can be customized from Setup by entering Salesforce Branding in the Quick Find box, then selecting Salesforce Branding. The other elements, such as the search bar layout, the background image, and the focus link color, are not customizable in the Salesforce app.Reference:
Customize Salesforce Mobile App Branding
How Salesforce App Branding Works
NEW QUESTION # 27
Which goal would be important in undertaking a Consequence Scanning exercise before launching a new product?
- A. Identify the best angle for positive launch press coverage.
- B. Encourage team well-being through collaboration.
- C. Reframe the product objectives from multiple, diverse perspectives.
Answer: C
Explanation:
Consequence scanning is a practice that helps teams to consider the potential consequences of their product or service on people, communities, and the planet1.It is an agile tool that fits within an iterative development cycle and allows teams to identify and mitigate risks, as well as focus on positive outcomes2. One of the goals of consequence scanning is to reframe the product objectives from multiple, diverse perspectives.This means that the team can explore how different stakeholders, such as users, organisations, or society, might be affected by the product or service, both intentionally and unintentionally2.By doing so, the team can ensure that the product or service aligns with their values and culture, and that they are aware of the trade-offs and implications of their decisions2.Reframing the product objectives from multiple, diverse perspectives can also help the team to discover new opportunities, generate innovative solutions, and increase user satisfaction and trust3.
Encouraging team well-being through collaboration and identifying the best angle for positive launch press coverage are not the primary goals of consequence scanning, although they might be beneficial side effects.Consequence scanning is not a PR exercise, but a way to ensure responsible innovation and ethical design2.While consequence scanning can foster team collaboration and communication, it is not a team-building activity, but a way to share knowledge and expertise and raise concerns in a dedicated format2.Reference:
Consequence scanning: How to mitigate risks in your service
Consequence Scanning - an agile practice for responsible innovators
What is consequence scanning?
NEW QUESTION # 28
Cloud kicks is planning its einstein Bot implementation and has identified common issues the Bot can resolve. CK has determined that extensive technical planning is needed for bot effectiveness and customer satisfaction
- A. voice and tone planning
- B. deboarding planning
- C. user interface planning
- D. Training and support for planning
Answer: C
Explanation:
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 analyticsEinstein Bots Project Planning | Salesforce Trailhead
NEW QUESTION # 29
Which two steps should a UX Designer take to create and deliver responsible andtransparent AI technology? Choose 2 answers
- A. Document model cards to clarify intended context and use cases.
- B. Provide clear explanations of AI predictions or recommendations.
- C. Design AI that is seamless enough so the user does not notice.
- D. Collect as much data from the user as possible for a catered experience.
Answer: A,B
Explanation:
A UX Designer should take the following steps to create and deliver responsible and transparent AI technology12:
C) Document model cards to clarify intended context and use cases.Model cards are standardized documents that provide essential information about a machine learning model, such as its purpose, performance, limitations, and ethical considerations3.Model cards can help UX Designers to communicate the design choices and trade-offs of their AI systems, and to ensure that they are aligned with the user needs and expectations4.
D) Provide clear explanations of AI predictions or recommendations.Explanations are user-facing descriptions of how and why an AI system produces a certain output, such as a prediction, a recommendation, or a decision5.Explanations can help UX Designers to increase the transparency and trustworthiness of their AI systems, and to empower users to understand, control, and evaluate the AI outcomes6.
C) Document model cards to clarify intended context and use cases.
Model cards are documents that describe the intended use, performance, and limitations of AI models. They help ensure that the AI technology is being used responsibly and transparently, as they provide clear information about the model's context, data, and assumptions. This can help reduce the risk of unintended consequences and build trust with users.
D) Provide clear explanations of AI predictions or recommendations.
Clear explanations of AI predictions or recommendations help build trust with users and increase understanding of how the AI technology works. By providing an understandable explanation of how a prediction or recommendation was made, users can gain a better understanding of the technology and how it is intended to be used. This can also help reduce the risk of unintended consequences and improve accountability.
NEW QUESTION # 30
Cloud kicks has identified that its users are having difficulty figuring out where to look on a web page due to the number of design elements.
Which threeconsiderations should be made to improve the visual hierarchy of the page?
Choose 3 answers
- A. Scale using relative size to signal importance
- B. Grouping proximity and common regions
- C. Continuity keep all typeface the same size
- D. Color and contract, saturation between the elements
- E. Proportion, keep allelement a similar size
Answer: A,B,D
Explanation:
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.
NEW QUESTION # 31
A UX Designer wants to plan and communicate the intended page layouts of a community portal.
Which tool should they use?
- A. Personas
- B. Process Flows
- C. Wireframes
- D. Journey Mapping
Answer: C
Explanation:
The tool that the UX Designer should use to plan and communicate the intended page layouts of a community portal iswireframes. Wireframes are low-fidelity sketches or diagrams that show the basic structure, content, and functionality of a web page or app screen. Wireframes help the UX Designer to visualize the layout of the portal, arrange the elements according to their importance and relevance, and communicate the design concept to the stakeholders and developers.Wireframes are one of the learning objectives for the Salesforce User Experience Designer certification1.[Wireframes - Lightning Design System]
https://careerfoundry.com/en/blog/ux-design/website-app-wireframe-examples/
NEW QUESTION # 32
A developer is creating a Lightning Web Component (LWC) and wants to make sure the visual experience is consistent with Cloud Kicks' branding. The developer asks their UX Designer about the Salesforce Lightning Design System (SLDS) stylinghooks.
How should the designer describe them?
- A. They use standard CSS properties to directly style HTML elements.
- B. They use custom CSS properties to easily style base and custom components.
- C. They use custom CSS properties to directly style HTML elements.
- D. They use standard CSS properties to easily style base and custom components.
Answer: B
Explanation:
Styling hooks are CSS custom properties that allow developers to customize the appearance of base and custom components in a consistent and supported way. They work with web components and shadow DOM, which provide encapsulation and modularity for LWC. Styling hooks use the--sldsnamespace and follow a naming convention that reflects the component, category, property, attribute, and state of the element being styled. For example,--slds-c-button-brand-color-background-hoveris a styling hook for the button component, brand category, color background property, and hover state. Styling hooks can be declared in the CSS file of the LWC or in a global CSS file that affects all components on the page. Styling hooks are not standard CSS properties, but custom ones that are defined by SLDS and applied to the components using thevar()function.Reference:
Styling Hooks - Lightning Design System
SLDS Styling Hooks | Lightning Web Components Developer Guide | Salesforce Developers
-dxp Styling Hooks | LWR Sites for Experience Cloud | Salesforce Developers The Salesforce Lightning Design System (SLDS) styling hooks use standard CSS properties to easily style base and custom components. Salesforce documentation states that "SLDS styling hooks are CSS classes that give you access to the same styling used in the Salesforce Lightning Design System. They make it easy to style base and custom components with the same look and feel" [1].
[1] https://developer.salesforce.com/docs/component-library/documentation/lwc/lwc.use_slds_styling_hooks
NEW QUESTION # 33
A UX Designer atCloud Kicks is having difficulty getting its developers to see why the design changes would improve the user experience.
How should the designer help mitigate pushback from developers?
- A. Ask a manager or superior to doit.
- B. Let them know the designer is the expert.
- C. Invite them to user testing.
- D. Hand them a printout of the design
Answer: C
Explanation:
Inviting developers to user testing is a good way to help them see the value of the design changes and understand the user needs and pain points. User testing is a method of evaluating a product or service by observing how real users interact with it and collecting feedback. By witnessing the user testing sessions, developers can see how the design changes improve the user experience, such as increasing usability, satisfaction, engagement, or conversion. User testing can also help developers empathize with the users and collaborate better with the designer.Reference:
[User Testing]
NEW QUESTION # 34
Financial advisor should be able to access a customer's record in Sales Cloud and see all potential business opportunities related to each individual customer. The bank does not have any corporate or business customers at this time.
How should a UX Designer suggest the bank represent its customers within its Salesforce instance?
- A. Standard Opportunity object.
- B. Standard Person Account Object
- C. Standard Lead Object
- D. Standard Account object.
Answer: B
Explanation:
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.
Convert Salesforce Business Accounts to Person Accounts, In Financial Services Cloud, Person Accounts can be used for a simplified, customizable user experience.
Person Accounts - Salesforce, Person Accounts Sales Cloud Basics Content Close Select Filters Product Area Feature Impact Edition Developer Edition Enterprise Edition Essentials Edition Professional Edition Unlimited Edition Experience Salesforce Classic Mobile Lightning Experience Done 632 Results Configure Access to Thanks Badges Set Up WDC Configure Thanks in the Chatter Publisher and Salesforce Mobile App... Build a Culture of Recognition with WDC Manage WDC Enable or Disable WDC Settings WDC Editions and Permissions Skills Limitations Skills Customization Recommended WDC Profiles Recommended WDC Permission Sets Enable WDC Features Configure WDC Assign WDC Only User Licenses Assign WDC Licenses Configure WDC Features Assign a WDC Administrator Create a Support Case Considerations for Setting Up WDC Thanks and Skills Features Assign Publisher Layout to Profiles Assign WDC User Feature Licenses Assign WDC Profiles Assign WDC Permission Sets Endorse a Skill Via Record Detail Pages Add a Skill Via Record Detail Pages Remove a Skill Via Record Detail Pages Schedule Reminders to Update Opportunities View a List of the Accounts or Opportunities in Your Territories Things to Know About Enterprise Territory Management Territory Type Priority Optimizing Your Territory Model Continuously Designing Territory Models Territory Model Managing Territories Enterprise Territory Management Concepts Planning and Managing Territories Territory Model State Territory Type Territory Hierarchy Bird's-Eye View of Planning and Managing Territories Report on Territories with Assigned Users Report on Territories Without Assigned Accounts Run Assignment Rules for a Territory Reporting on Territories Report on Users Not Assigned to Territories Report on Summarizable Account Fields by Territory Enterprise Territory Management Identify Territory Users by Territory Role Territory Run the Opportunity Territory Assignment Filter Preview Territory Assignments for Accounts Report on Accounts Assigned to Territories Manage Territories with Enterprise Territory Management View and Manage Assignment Rules at the Territory Model Level Enterprise Territory Management: What's Different or Not Available... Show Your Reps Other Users Assigned to Their Leads' Territories Enable Features for Enterprise Territory Management Maintain Enterprise Territory Management Find Out Which Territories an Assignment Rule Applies To Enable Enterprise Territory Management Report on the Accounts and Opportunities in Your Territories Explore Your Company's Territory Model Identify Users in Territories Assigned to Accounts Enable Filter-Based Opportunity Territory Assignment Identify an Account's Sales Territories Disable Enterprise Territory Management How Account Assignment Rules Work How Do Permissions for Territories Affect Feature and Data Access? Requirements for Assigning Opportunities to Territories Manually Assigning Opportunities to Territories Manually Delete a Territory Model Create a Territory Model Record Preparing Sales Management for Territory Reporting Setting Up and Managing Territory Assignments Define Default User Access for Territory Records Account | Object Reference for the Salesforce Platform | Salesforce ..., Account | Object Reference for the Salesforce Platform | Salesforce Developers Object Reference for the Salesforce Platform English Pages Winter '24 (API version 59.0) Summer '23 (API version 58.0) Spring '23 (API version 57.0) Winter '23 (API version 56.0) Summer '22 (API version 55.0) Spring '22 (API version 54.0) Winter '22 (API version 53.0) Summer '21 (API version 52.0) Spring '21 (API version 51.0) Winter '21 (API version 50.0) Summer '20 (API version 49.0) Spring '20 (API version 48.0) Winter '20 (API version 47.0) Summer '19 (API version 46.0) Spring '19 (API version 45.0) Winter '19 (API version 44.0) Summer '18 (API version 43.0) Spring '18 (API version 42.0) Winter '18 (API version 41.0) Summer '17 (API version 40.0) Spring '17 (API version 39.0) Winter '17 (API version 38.0) Summer '16 (API version 37.0) Spring '16 (API version 36.0) Winter '16 (API version 35.0) Summer '15 (API version 34.0) Spring '15 (API version 33.0) Winter '15 (API version 32.0) Summer '14 (API version 31.0) Spring '14 (API version 30.0) j Overview of Salesforce Objects and Fields Reference Associated Objects (Feed, History, OwnerSharingRule, Share, and ChangeEvent Objects) Custom Objects Object Interfaces Standard Objects AcceptedEventRelation Account AccountBrand AccountContactRelation AccountCleanInfo AccountContactRole AccountInsight AccountOwnerSharingRule AccountPartner AccountRelationship AccountRelationshipShareRule AccountShare AccountTag AccountTeamMember AccountTerritoryAssignmentRule AccountTerritoryAssignmentRuleItem AccountTerritorySharingRule AccountUserTerritory2View ActionCadence ActionCadenceRule ActionCadenceRuleCondition ActionCadenceStep ActionCadenceStepTracker ActionCadenceStepVariant ActionCadenceTracker ActionCdncStpMonthlyMetric ActionLinkGroupTemplate ActionLinkTemplate ActionPlan ActionPlanItem ActionPlanTemplate ActionPlanTemplateItem ActionPlanTemplateItemValue ActionPlanTemplateVersion ActiveFeatureLicenseMetric ActivePermSetLicenseMetric ActiveProfileMetric ActiveScratchOrg ActivityHistory ActivityMetric ActivityUsrConnectionStatus AdAvailabilityDimensions AdAvailabilityJob AdAvailabilityViewConfig AdBuyServerAccount AdCreativeSizeType AdDigitalAvailability AdditionalNumber Address AdLinearAvailability AdOpportunity AdOrderItem AdOrderItemCreativeSizeType AdOrderLineAdTarget AdPageLayoutType AdProductTargetCategory AdQuote AdQuoteLine AdQuoteLineCreativeSizeType AdQuoteLineAdTarget AdServer AdServerAccount AdServerUser AdSpaceCreativeSizeType AdSpaceGroupMember AdSpaceSpecification AdSpecMediaPrintIssue AdTargetCategory AdTargetCategorySegment AgentWork AgentWorkSkill AIApplication AIApplicationConfig AIInsightAction AIInsightFeedback AIInsightReason AIInsightValue AiModelLanguage AIRecordInsight AllowedEmailDomain AlternativePaymentMethod AnalyticsLicensedAsset Announcement ApexClass ApexComponent ApexLog ApexPage ApexPageInfo ApexTestQueueItem ApexTestResult ApexTestResultLimits ApexTestRunResult ApexTestSuite ApexTrigger ApexTypeImplementor AppAnalyticsQueryRequest AppDefinition AppExtension ApplicationFormTemplate AppMenuItem AppointmentAssignmentPolicy AppointmentScheduleAggr Lead | Object Reference for the Salesforce Platform | Salesforce ..., Lead | Object Reference for the Salesforce Platform | Salesforce Developers Object Reference for the Salesforce Platform English Pages Winter '24 (API version 59.0) Summer '23 (API version 58.0) Spring '23 (API version 57.0) Winter '23 (API version 56.0) Summer '22 (API version 55.0) Spring '22 (API version 54.0) Winter '22 (API version 53.0) Summer '21 (API version 52.0) Spring '21 (API version 51.0) Winter '21 (API version 50.0) Summer '20 (API version 49.0) Spring '20 (API version 48.0) Winter '20 (API version 47.0) Summer '19 (API version 46.0) Spring '19 (API version 45.0) Winter '19 (API version 44.0) Summer '18 (API version 43.0) Spring '18 (API version 42.0) Winter '18 (API version 41.0) Summer '17 (API version 40.0) Spring '17 (API version 39.0) Winter '17 (API version 38.0) Summer '16 (API version 37.0) Spring '16 (API version
NEW QUESTION # 35
A UX Designer needs to create a visual representation of a user's series of steps to achieve a meaningful goal.
Which UX design method should be used?
- A. User Flow
- B. Site Map
- C. User Persona
- D. Lightning Flow
Answer: A
Explanation:
A user flow is a UX design method that creates a visual representation of a user's series of steps to achieve a meaningful goal. A user flow shows the path that a user takes from their entry point to their final action, such as signing up, purchasing, or completing a task. A user flow helps designers understand and optimize the user experience, as well as identify pain points, gaps, and opportunities for improvement. A user flow can take various forms, such as diagrams, wireframes, or prototypes, depending on the level of detail and fidelity required.Reference:
What Are User Flows In UX Design? [Full Beginner's Guide] - CareerFoundry What is a User Flow in UX Design? - updated 2023 | IxDF User Flows in UX Design: Definition, Benefits, and Best Practices
NEW QUESTION # 36
......
Updated Official licence for Plat-UX-101 Certified by Plat-UX-101 Dumps PDF: https://dumpstorrent.actualpdf.com/Plat-UX-101-real-questions.html
