A sales rep at Universal Containers was added to an opportunity team with Read/Write permissions. Which action is she allowed to perform in the opportunity?
A. Add/remove members in the opportunity team.
B. Replace opportunity owner.
C. Update opportunity stage.
Universal Containers (UC) has 200 distributors that use Partner Community Licenses. Partners cannot see each other's data, but UC is also trying to give more visibility to certain individuals at a distributor. Which scalable solution would an architect recommend that will give users in the partner manager role access to all Case and Container records owned by other partner managers and partner users (but not the partner executive) at the same distributor?
A. Create Sharing sets.
B. Create a permission set granting the View All permission to Case and Container records.
C. Give Super User permission to the partner manager users.
D. Create ownership-based sharing rules for your distributors.
Which are two valid use cases for programmatic sharing? Choose 2 answers.
A. An external system manages user record access.
B. Frequent user ownership changes based on re-alignments.
C. Native sharing functionality does not meet requirements.
D. Setting user ownership for standard and custom objects.
Explanation:
Programmatic sharing is a way to use Apex code to create or delete sharing rules for records. Programmatic sharing is useful when2:
An external system manages user record access and you need to synchronize the access settings in Salesforce.
The native sharing functionality does not meet your complex or dynamic sharing requirements.
Universal Containers, a global corporation of 50,000 users, has a 24x7 call center operated by 20,000 users that includes employees and contractors. Their sales organization is 10,000 strong and they started processing about 100,000 updates to opportunity custom fields called Priority and NextStep. They also started processing 20,000 updates to a highly nested territory hierarchy. There was a third mass update on a Next Step field on the Action Plan custom object that has Case as a lookup field. Users started seeing a Group membership lock error in the system. What is a probable cause for this error?
A. Lock contention due to system-initiated sharing rule recalculation
B. Lock contention on Case records because of Action Plan custom object updates.
C. Lock contention on Territory object because of Territory object updates.
D. Lock contention on Account records because of Opportunity object updates.
Explanation:
The probable cause for this error is lock contention due to system-initiated sharing rule recalculation. When there are mass updates to fields that affect sharing rules, such as territory or role fields, Salesforce automatically recalculates the sharing rules to reflect the changes. This can cause lock contention on group membership records, which store the users and groups that have access to records through sharing rules. The other options are not likely to cause this error.
Universal Containers uses 75,000 distributors that have close to 1 million total users. Distributors need opportunities assigned to the distributor for delivery. What license recommendation will meet distributor needs?
A. Sales Cloud
B. Customer Community Plus
C. Partner Community
D. Customer Community
Explanation:
The license recommendation that will meet distributor needs is Partner Community. Partner Community licenses are designed for users who are not employees of UC, but are part of their partner ecosystem, such as distributors, resellers, or suppliers. Partner Community users can access standard CRM objects such as accounts, contacts, leads, opportunities, cases, and campaigns. They can also collaborate with other partners and UC employees using Chatter and Communities. Sales Cloud licenses are for internal sales users who need full access to standard CRM and custom objects. Customer Community Plus licenses are for high-volume customers who need access to standard CRM objects and custom objects, but not opportunities. Customer Community licenses are for low-volume customers who need access only to custom objects and a subset of standard CRM objects.
At Universal Containers there is a team of auditors distributed through the organization that all need access to high-value Opportunities. With a private sharing model, which two option should an architect recommend when designing a solution for this requirement? Choose 2 answers
A. Put the auditors as the highest level of the role hierarchy.
B. Add the auditors to the default Opportunity Team.
C. Create a criteria-based sharing rule to give access to the public group for high-value Opportunities. <br>
D. Create a public group and assign the Auditors to the group. <br>
Explanation:
Creating a criteria-based sharing rule to give access to the public group for high-value opportunities and creating a public group and assigning the auditors to the group are the best options to give access to high-value opportunities to a team of auditors distributed through the organization. Option A is incorrect, since putting the auditors as the highest level of the role hierarchy would give them access to all opportunities, not just high-value ones. Option B is incorrect, since adding the auditors to the default opportunity team would require manual configuration and maintenance.
Universal Containers has a customer that meets criteria for two Enterprise territory Management territories (Portugal and Southern Europe). What is necessary to assign opportunities to a territory for this account?
A. Create a criteria-based sharing rule on the Opportunity to assign It to a territory.
B. Create a Process Builder Process that updates the Territory field on the Opportunity
C. The territory with the highest Territory Type Priority is automatically assigned to the Opportunity
D. Create an Apex class that implement. Filter-Based Opportunity Territory Assignment
Explanation:
To assign opportunities to a territory for an account that meets criteria for two Enterprise Territory Management territories, the territory with the highest Territory Type Priority is automatically assigned to the opportunity. This is how Salesforce resolves conflicts when an account matches multiple territories. Creating a criteria-based sharing rule or a Process Builder process will not work, as they do not affect the territory assignment. Creating an Apex class that implements Filter-Based Opportunity Territory Assignment will not work, as it is only applicable for accounts that do not match any territory
The System Administrator at Universal Containers has created two list views called ListV1 and ListV2. One group of users should only see ListV1 and the second group of users should only see ListV2. Two public groups were created to restrict visibility to the respective list views. However, users in both groups are able to see both list views. What system permission in their profile enabled the users to see all list views?
A. Manage Custom List Views
B. Manage Private List Views
C. Manage Public List Views
D. Manage Custom Permissions <br>
Explanation:
The system permission in their profile that enabled the users to see all list views is manage public list views. This permission allows users to create, edit, and delete public list views, as well as view all list views shared with them or with their groups. To restrict visibility to the respective list views, the system administrator should remove this permission from the users’ profiles and assign it only to those who need to manage public list views.
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 to sales reps on the same team, owner ship-based sharing rules were created for each team. What is the side effect of this approach?
A. All sales reps will have Read access to Accounts for all Opportunities.
B. Sales Reps on the same team will have Edit access to the Accounts for Opportunities owned by then team members.
C. Sales reps on the same team will have Read access to the Accounts for Opportunities owned by their team members.
D. All sales reps will have Read access to all Accounts.
Explanation:
The side effect of this approach is that sales reps on the same team will have read access to the accounts for opportunities owned by their team members. This is because owner-based sharing rules grant access to both the parent and child records of the same object. For example, if a sharing rule grants access to opportunities owned by a certain role, it also grants access to the accounts associated with those opportunities. All sales reps will not have read access to accounts for all opportunities, as the sharing rules are based on ownership. Sales reps on the same team will not have edit access to the accounts for opportunities owned by their team members, as owner-based sharing rules only grant read or read/write access to child records, not parent records. All sales reps will not have read access to all accounts, as the account organization-wide default is private.
Sales Operations at Universal Container (UC) wants to create the opens to fiber appropriates for center. In which two ways can UC hide list that are not relevant to an individual use since there will be Choose 2 answers.
A. Share the list views with the appropriate queue.
B. Share the list views with the appropriate individual users.
C. Share the list views with the appropriate public group.
D. Share the list views with the appropriate role in the role hierarchy
Explanation:
Sharing the list views with the appropriate public group and sharing the list views with the appropriate role in the role hierarchy are two ways that UC can hide lists that are not relevant to an individual user. List view sharing allows users to share list views with other users based on public groups, roles, subordinates, or individual users. This way, users can only see list views that are relevant to them and their work. Option A is incorrect, since sharing list views with a queue is not possible. Option B is incorrect, since sharing list views with individual users would be tedious and inefficient.
| Page 1 out of 7 Pages |
Copyright © - All Rights Reserved