QUESTION: 57

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.
Changing complex role hierarchy can cause a high level of sharing recalculation.
Restricting the organization-sharing configurations to private.
Replacing Account records ownerships massively can cause data skew.

Answer(s): 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 hours.
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 minimized.

Reference:

: [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]

Reveal Solution Next Question

QUESTION: 58

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.
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.
All sales reps will have Read access to all Accounts.

Answer(s): 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 access. 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 accounts. However, the sales reps will not have Edit access to the accounts, unless the sharing rules specify Full Access for the opportunities. 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

Reveal Solution Next Question

QUESTION: 59

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
Read/Create/Edit access
Read/Create access
Read-only access

Answer(s): 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

Reveal Solution Next Question

QUESTION: 60

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
Scale using relative size to signal importance
Continuity keep all typeface the same size
Proportion, keep allelement a similar size
Color and contract, saturation between the elements

Answer(s): 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.

Reference:

: Visual Hierarchy
: Gestalt Principles

Reveal Solution Next Question

Free USER-EXPERIENCE-DESIGNER Exam Braindumps (page: 15)

QUESTION: 57

Explanation:

Reference:

QUESTION: 58

Explanation:

Reference:

QUESTION: 59

Explanation:

Reference:

QUESTION: 60

Explanation:

Reference: