Available in 1, 3, 6 and 12 Months Free Updates Plans
PDF: $15 $60

Test Engine: $20 $80

PDF + Engine: $25 $99

Sharing-and-Visibility-Architect Practice Test


Page 16 out of 48 Pages

Topic 1: Exam Pool A

Universal Containers (UC) has a custom object to track the internal net promoter score (NPS) for all .. How can UC ensure that NPS records cannot be accessed by an individual employee's manager?


A. Create a criteria-based sharing rule to remove access toManager role and above in the Role


B. Remove Create, Read, Edit and Delete from Manager Profiles and Permission sets


C. Use Apex Sharing to remove NPS object share records for Manager profiles


D. Set organization wide default to Private and uncheck the Access Using Hierarchies option for the NPS object





D.
  Set organization wide default to Private and uncheck the Access Using Hierarchies option for the NPS object

Explanation: Setting the organization-wide default to Private and unchecking the Access Using Hierarchies option for the NPS object will prevent the managers from accessing the NPS records of their subordinates. This is because the access using hierarchies option allows users above the owner in the role hierarchy to have the same level of access as the owner.

Universal Containers would like to control access to records and objects according to the following business requirements:• Sales users can view all Account records but only edit their own records.

  • Sales managers view all Account records but only edit records of the team.
  • Service users can view all Account records that are not marked with a RecordType of Prospect.
Which organization-wide default configuration should a Salesforce architect recommend to fulfill these requirements?


A. Public Read Write


B. Private


C. Public tad Only


D. Public Read/Transfer





C.
  Public tad Only

Explanation: Public Read Only is the best organization-wide default configuration to fulfill the requirements. PublicRead Only means that all users can view all records, but onlythe owners and those above them in the role hierarchy can edit them3. This matches the requirements for sales users and sales managers. For service users, a record type-based sharing rule can be created to restrict their access to accounts with a RecordType of Prospect. Public Read Write, Private, and Public Read/Transfer are not suitable configurations for the requirements.

Universal Containers (UC) delivers training and courses to students and companies. UC is implementing a Salesforce Customer Community for its students granting them a Customer Community license. As part of the community requirements, UC asked to give students access to cases that are related to their account in the UCcommunity. What is the optimum sharing technique that can achieve the requirements?


A. Create a sharing rule to share cases with the students


B. Create a share group to share cases with the students


C. Create a sharing set to share cases with the students


D. Use Apex sharing to share cases with the students





C.
  Create a sharing set to share cases with the students

Explanation: A sharing set is the best way to share cases with community users based on a common account. Sharing sets are available for Customer Community licenses and can grant access to related records using predefined criteria. Option A is incorrect, since sharing rules are not available for community users. Option B is incorrect, since there is no such thing as a share group in Salesforce. Option D is incorrect, since Apex sharing is complex and requires code maintenance.

Universal Containers uses person accounts to represent retail customers and business accounts to represent commercial customers. The Retail Sales team should not have access to commercial customers but have access to ALL retail customers. With organization-wide default on Account set to Private, how might the architect meet these requirements?


A. Give View All access for Accounts to the Retail Sales profile.


B. Update Retail Sales profile to grant access to Person Account record type.


C. Create an owner-based sharing rule on AccountContactRelation to grant access to at account contact roles records owned by sales reps.


D. Create a criteria-based sharing rule giving Retail Sales role access to Accounts oftype PersonAccount.





D.
  Create a criteria-based sharing rule giving Retail Sales role access to Accounts oftype PersonAccount.

Explanation: A criteria-based sharing rule is the best option to give access to accounts based on a specific field value, such as the record type. Option A would give access to all accounts, not just person accounts. Option B would onlycontrol the layout and not the visibility. Option C would not apply to person accounts, since they do not have account contact roles

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?


A. No access


B. Read/Create/Edit access


C. Read/Create access


D. Read-only access





D.
  Read-only access

Explanation: The sales rep will have read-only access to the related account record. This is because the organization-wide default for the account object is private, which means that users can only access the accounts that they own or are shared with them. However, when a user has access to an opportunity, they also have implicit read-only access to the account associated with that opportunity1. This is called implicit sharing and it allows users to view the parent records of the child records they own or can access2. Therefore, the sales rep can view the account record related to the opportunity, but cannot create, edit, or delete it.


Page 16 out of 48 Pages
Previous