ExamGecko
Ask Question

Salesforce Certified User Experience Designer Practice Test - Questions Answers, Page 6

List of questions

Question 51

Report
Export
Collapse

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

Country may read text is a different direction (right to left) vs (left to right) and layouts will need to be adjusted
Country may read text is a different direction (right to left) vs (left to right) and layouts will need to be adjusted
Country flags used as links to adjust languages provide an ideal way to switch between locals orlanguages for users
Country flags used as links to adjust languages provide an ideal way to switch between locals orlanguages for users
colors may have different contrast ratios in some countries and need adjusted contrast for proper visibility by users
colors may have different contrast ratios in some countries and need adjusted contrast for proper visibility by users
colors may have different cultural meanings in different countries, changing the intent of UI elements
colors may have different cultural meanings in different countries, changing the intent of UI elements
Suggested 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)

asked 23/09/2024
ML MASANE
46 questions

Question 52

Report
Export
Collapse

Cloud kicks wants to incorporates human-centered design across its organization

Which two practices should beadopted

Including innovative ideas to showcase technology
Including innovative ideas to showcase technology
observing user behavior
observing user behavior
putting oneself in the situation of the end-user
putting oneself in the situation of the end-user
creating requirements based on business leaders priorities
creating requirements based on business leaders priorities
Suggested answer: B, C

Explanation:

Human-centered design is a process that starts with the people you are designing for and ends with new solutions that are tailor-made to suit their needs. It involves understanding the problem from the perspective of the end-users, empathizing with their needs and preferences, and creating solutions that are desirable, feasible, and viable. To incorporate human-centered design across an organization, two practices that should be adopted are:

Observing user behavior: This involves watching how users interact with a product or service, what they do, say, think, and feel. Observing user behavior can help identify pain points, needs, goals, motivations, and emotions that drive user behavior. It can also reveal insights that users may not be able to articulate or may not be aware of themselves. Observing user behavior can be done through methods such as user interviews, contextual inquiry, usability testing, and analytics.

Putting oneself in the situation of the end-user: This involves imagining or experiencing what the user goes through when using a product or service, and how they perceive and respond to it. Putting oneself in the situation of the end-user can help build empathy, understand the user's context and environment, and generate ideas that address the user's needs and expectations. Putting oneself in the situation of the end-user can be done through methods such as personas, scenarios, journey maps, and empathy maps.

: [What is Human-Centered Design?]

: [Human-Centered Design: The Definitive Guide]

: [UX Research: What is User Behavior?]

: [Observing the User Experience: A Practitioner's Guide to User Research]

: [UX Research Methods: Observation]

: [Empathy in Design Thinking]

: [UX Research Methods: Empathy]

asked 23/09/2024
Arno Rodenhuis
49 questions

Question 53

Report
Export
Collapse

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

Training and support for planning
Training and support for planning
user interface planning
user interface planning
deboarding planning
deboarding planning
voice and tone planning
voice and tone planning
Suggested answer: B

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 analyticsReference:Einstein Bots Project Planning | Salesforce Trailhead

asked 23/09/2024
Anil Dehriya
35 questions

Question 54

Report
Export
Collapse

A UX designer wants to quickly mock up salesforce user interface experiences using a collection of prebuilt components. The designers neededsalesforce lighting design systems(SLDS) resources for their designs and prototypes such as base components tokens and designs patterns

Which tool or installation should best support their needs?

Lighting design systems zip
Lighting design systems zip
sketch plugin
sketch plugin
lightingdesign systems unmanaged package
lightingdesign systems unmanaged package
SLDS validator
SLDS validator
Suggested answer: B

Explanation:

A sketch plugin is a tool that allows the UX designer to quickly mock up Salesforce user interface experiences using the Lightning Design System (SLDS) resources, such as base components, tokens, and design patterns. The sketch plugin is a free plugin for Sketch, a design toolkit that helps create wireframes, mockups, sample screens, and more. With the sketch plugin, the designer can search and drag the prebuilt components from the plugin into the canvas, and export the mockups as pdf, jpeg, or png files. The sketch plugin also supports synonyms and variants for the components, making it easier to find and use the desired elements.The sketch plugin can be downloaded from the SLDS website1or from the AppExchange2.Reference:

[Create Quick Salesforce UI Mockups: Lightning Design System Plugin for Sketch]1

[Lightning Design System Sketch Plugin]2

asked 23/09/2024
Nitharsan Balanavaneethan
45 questions

Question 55

Report
Export
Collapse

Universal Containers (UC) uses a custom lightning component with an Apex class to display shipment information (custom object, private OWD). UC sales managers are complaining about two important points:

Shipment records that belong to their teams can be seen by other users.

Shipment amount should be visible only by managers, but sales reps are able to view it.Which two features did the development team miss that is causing the problems?

Choose 2 answers.

Use runAs in test class to enforce user permissions and field-level permissions.
Use runAs in test class to enforce user permissions and field-level permissions.
Use With Sharing keyword in Apex classes to enforce sharing rules evaluation.
Use With Sharing keyword in Apex classes to enforce sharing rules evaluation.
Use isSharable keyword in Apex classes to assurerecord visibility.
Use isSharable keyword in Apex classes to assurerecord visibility.
Use isAccessible() method in Apex classes to check field accessibility
Use isAccessible() method in Apex classes to check field accessibility
Suggested answer: B, D

Explanation:

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

asked 23/09/2024
Jenny Silva
42 questions

Question 56

Report
Export
Collapse

Universal Containers (UC) has implemented Service Cloud. There is a flag field on the case object that marks a case as(Sensitive). UC requested that this flag can be viewed by all users who have access to the case but only be edited by the assigned case assessor. The case assessor is a lookup field on the case object. How can an architect achieve this requirement?

Permission Set.
Permission Set.
Object Permissions.
Object Permissions.
Custom Lightning Component.
Custom Lightning Component.
Field-level security
Field-level security
Suggested answer: C

Explanation:

The best way to achieve the requirement of having a flag field on the case object that marks a case as sensitive and can be viewed by all users who have access to the case but only be edited by the assigned case assessor is to create a custom Lightning component. A custom Lightning component can use the Lightning Data Service to access the case record and its fields, and apply conditional rendering and editing logic based on the user's role and the case assessor field. This way, the flag field can be displayed to all users who can view the case, but only be editable by the user who is the case assessor. This solution also follows the principle of designing for performance and scalability, which is one of the learning objectives for the Salesforce User Experience Designer certification.Reference: [Create Custom, Reusable Lightning Components], [Lightning Data Service Basics], [Design for Performance and Scalability]

: https://trailhead.salesforce.com/en/content/learn/modules/lex_dev_lc_basics/lex_dev_lc_basics_intro : https://trailhead.salesforce.com/en/content/learn/modules/lightning_data_service/lightning_data_service_intro : https://trailhead.salesforce.com/en/content/learn/modules/ux-designer-certification-prep/design-for-performance-and-scalability

asked 23/09/2024
Kofi Amedorme
44 questions

Question 57

Report
Export
Collapse

Universal Containers (UC) operates worldwide with offices in more than 100 regions in 10 different countries role hierarchy to control data visibility. In the new fiscal year, UC is planned to reorganize the roles and reassign accounts owners. Which two points should an architect consider in this situation?

Which two point should an Architect consider in this situation?

Choose 2 answers

Using a temporary parking lot account to improve performance.
Using a temporary parking lot account to improve performance.
Changing complex role hierarchy can cause a high level of sharing recalculation.
Changing complex role hierarchy can cause a high level of sharing recalculation.
Restricting the organization-sharing configurations to private.
Restricting the organization-sharing configurations to private.
Replacing Account records ownerships massively can cause data skew.
Replacing Account records ownerships massively can cause data skew.
Suggested answer: B, D

Explanation:

Changing the role hierarchy and reassigning account owners can have a significant impact on the data visibility and performance of Salesforce. An architect should consider the following points in this situation:

Changing complex role hierarchy can cause a high level of sharing recalculation.Depending on the sharing settings, roles can control the level of visibility that users have into the Salesforce data. Users at any given role level can view, edit, and report on all data owned by or shared with users below them in the role hierarchy, unless the sharing model for an object specifies otherwise. When the role hierarchy is changed, Salesforce must recalculate the sharing rules and group membership for all the affected users and records, which can take a long time and consume a lot of system resources.Therefore, changing a complex role hierarchy should be done carefully and preferably during off-peak hours1.

Replacing account records ownerships massively can cause data skew.Data skew occurs when more than 10,000 child records are related to the same parent record, or more than 10,000 records of any object are owned by a single user. This can cause performance issues, such as locking, timeouts, and failures, when updating or sharing those records. When account owners are reassigned massively, it can create or worsen data skew, especially if the accounts have many child records, such as contacts and opportunities.Therefore, replacing account records ownerships massively should be avoided or minimized23.

: [Design Your Data Model Unit | Salesforce Trailhead]

: [Data Skew in Salesforce - Why it Matters | Salesforce Ben]

: [Ownership Data Skew | Designing Record Access for Enterprise Scale | Salesforce Developers]

asked 23/09/2024
jateen chibabhai
41 questions

Question 58

Report
Export
Collapse

Sales managers want their team members to help each other close Opportunities. The Opportunity and Account organization-wide defaults are private. To grant Opportunity access tosales reps on the same team, owner ship-based sharing rules were created for each team.

What is the side effect of this approach?

All sales reps will have Read access to Accounts for all Opportunities.
All sales reps will have Read access to Accounts for all Opportunities.
Sales Reps on the same team will have Edit access to the Accounts for Opportunities owned by then team members.
Sales Reps on the same team will have Edit access to the Accounts for Opportunities owned by then team members.
Sales reps on the same team will have Read access to the Accounts for Opportunities owned by their team members.
Sales reps on the same team will have Read access to the Accounts for Opportunities owned by their team members.
All sales reps will have Read access to all Accounts.
All sales reps will have Read access to all Accounts.
Suggested answer: C

Explanation:

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

asked 23/09/2024
ALEXANDRE NGUYEN
36 questions

Question 59

Report
Export
Collapse

Universal Containers' organization wide-defaults model is private for the Account object. A sales repeats to opportunity records.

Which level of access will the sales rep have to the related account record?

No access
No access
Read/Create/Edit access
Read/Create/Edit access
Read/Create access
Read/Create access
Read-only access
Read-only access
Suggested answer: D

Explanation:

A sales rep who owns an opportunity record will have read-only access to the related account record, if the organization-wide default for the Account object is private. This is because the opportunity owner is automatically granted read-only access to the account that the opportunity is associated with, regardless of who owns the account. This is called implicit sharing, and it is a built-in feature of Salesforce to ensure that users can access the data they need to do their work. However, the opportunity owner will not be able to create, edit, or delete the account record, unless they have other sharing mechanisms that grant them higher access, such as role hierarchy, sharing rules, manual sharing, or View All or Modify All permissions.Reference:

[Salesforce Certified User Experience Designer Exam Guide], Section 3.1: Design and implement solutions that meet user needs

[Control Access to Records Unit | Salesforce Trailhead]1, Unit 2: Implicit Sharing

[Work with Related Lists on Records in Lightning Experience - Salesforce]2, Related List Cards

asked 23/09/2024
Thanh Phan
37 questions

Question 60

Report
Export
Collapse

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

Grouping proximity and common regions
Grouping proximity and common regions
Scale using relative size to signal importance
Scale using relative size to signal importance
Continuity keep all typeface the same size
Continuity keep all typeface the same size
Proportion, keep allelement a similar size
Proportion, keep allelement a similar size
Color and contract, saturation between the elements
Color and contract, saturation between the elements
Suggested answer: A, B, E

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.

: Visual Hierarchy

: Gestalt Principles

asked 23/09/2024
Adam Bednar
38 questions
Total 211 questions
Go to page: of 22
Search

Related questions