Universal Computers (UC) is looking to expand its delivery capabilities through a network of distributors that use a Partner Community license. UC employees currently can view all delivery records through the organization-wide default (OWD) setting of Public Read Only.
Which approach would an architect recommend to limit the records a distributor can see?

• A.Remove Read permission from the distributor profile.
• B.Create an ownership-based sharing rule to grant access to the distributor.
• C.Set the External OWD to Private for the Delivery object.
• D.Create a criteria-based sharing rule to grant access to the distributor

Comment: *

Name: *

Email: *

Verification: *

Besides their own team accounts, sales managers at Universal Containers need to have READ access to all accounts of the same segment in other countries. Role hierarchy was implemented accordingly (based on countries), but a sales manager in the US is complaining that he cannot view account records of the same segment in Canad What should be done to grant access in a proper way?

• A.Create an owner-based sharing rule to grant access to account records that have the same segment to all sales manager roles.
• B.Change the role hierarchy and put all of the sales managers in the US and Canada in the same role.
• C.Create criteria-based sharing rules to grant access to account records that have the same segment to all sales manager roles.
• D.Create a public group and include all accounts of the same segment and grant access through a permission set.

Comment: *

Name: *

Email: *

Verification: *

For the Universal Containers Commercial and Consumer support departments, having access to Activities for Contacts with which they interact is important. Commercial support users should not see Consumer Accounts/Contacts and Consumer support users should not see Commercial Accounts/Contacts. Assuming the Organization-Wide Default for Activities is set to "Controlled by Parent" what is the minimum level of Sharing access a support user would need to Accounts/Contacts to view associated Activities?

• A.The users need no access to Accounts/Contacts with the proper Activity Sharing Rules and Profile Permissions for the Accounts Tab.
• B.Private Account/Contact Sharing Default with a Sharing Rule for each department set to Private access to Accounts/Contacts.
• C.Private Account/Contact Sharing Default with a Sharing Rule for each department set to Public Read/Write access to Accounts/Contacts.
• D.Private Account/Contact Sharing Default with a Sharing Rule for each department set to Public Read only access to Accounts/Contacts.

Comment: *

Name: *

Email: *

Verification: *

Universal Containers has just deployed a change to its role hierarchy. A manager is reporting that their staff can now see Accounts that they do not own and should not have access to. How should the Architect troubleshoot?

• A.While logged in as the one of the Staff members, navigate to their user record and inspect their profile and role membership.
• B.While logged in as the one of the Staff members, navigate to a sample account and use the Sharing button to determine who has access.
• C.While logged in as the System Administrator, use the Field Accessibility Viewer to view a matrix of who has access to Accounts.
• D.While logged in as the System Administrator, use the Field Accessibility Viewer to view a matrix of who has access to Accounts.

Comment: *

Name: *

Email: *

Verification: *

Universal Containers has selected a small and diverse group of users to review Inactive accounts. Given the Private sharing model, a public group was created and made available to this group of users. A sharing rule was created to make inactive Accounts visible to the public group. However some of these users are reporting they don't see any of the Accounts that were shared with the public group.
what is the underlying Issue for these users?

• A.The users are In profiles that have no access to the Account object.
• B.The page layout assigned to these mart to different than the Account owner
• C.The users have a permission set that only allow Accounts in "Active' status.
• D.The Accounts ire owned by users higher In the role hierarchy.

Comment: *

Name: *

Email: *

Verification: *