1. You want to hide the shipping address fields of the account object from all of your sales representative users. What do you do?
   1. Configure field-level security to hide fields from sales representative profiles.
   2. Create a permission set to configure field-level security to hide fields.
   3. Assign no layout to the account object.
   4. Change the org-wide default sharing to Controlled by Parent for the Shipping Address object.
2. You need the sales representative users to be able to do some service-related work. What do you do?
   1. Create multiple profiles and assign them to the sales representative users.
   2. Assign a sales representative profile and the service representative profile to the selected sales representative users.
   3. Use a permission set to enable specific service abilities.
   4. Create a new license and profile to provide the new service features.
3. You want to give Delete access to the account object but not the Edit permission. How can you do this?
   1. Delete access requires Read and Edit OLS: this requirement makes no sense regarding OLS.
   2. Simply flag the Delete permission on the user's profile and unflag the Edit permission.
   3. Add the Modify All Data permission to the user's profile.
4. Your OWD sharing on the lead object is set to Public Read/Write. How can you restrict its access to Public Read Only for a selected role?
   1. Create a permission set and give it the Private OLS permission on the lead object.
   2. You cannot restrict the record-access level except by changing the OWD settings.
   3. Create a sharing rule to restrict access to the Private object level for the given role.
   4. Enable the View All permission on the lead object for the given role.

5. The OWD on the account is set to Private. An SLA custom object, which is the child of a master-detail relationship with the account object, should be able to be edited by the account's owner. How do you set up the OWD on the SLA object?
   1. OWD between master and child objects cannot relate.
   2. Set the OWD on the SLA object to Controlled by Parent .
   3. Set the OWD on the account object to Controlling Children.
   4. Set the OWD on the SLA object to Public Read/Write.
6. The OWD on the Interview custom object is set to Private. HR managers should be able to see their HR reps records. How can they do this?
   1. Change the OWD of the Interview custom object to Public Read-Only.
   2. HR reps should have a role above HR managers and Grant Access Using Hierarchies for the Interview object should be flagged.
   3. HR reps should have a role above HR managers and Grant Access Using Hierarchies for the Interview object should not be flagged.
   4. HR managers should have a role above HR reps and Grant Access Using Hierarchies for the Interview object should be flagged.
7. You are required to create a sharing rule to give read/write access to accounts objects owned by all the sales representatives to all the service managers (OWD on the account is Public Read). How do you do this?
   1. Create a criteria-based sharing rule that shares all the records owned by the sales representatives role with the sales managers role by setting the default access on the account object to Read/Write.
   2. Create an owner-based sharing rule that shares all the records owned by the sales representatives role with the Sales Managers role by setting the default access on the account object to Read/Write.
   3. Create a criteria-based sharing rule that shares all the records owned by the Service Managers role with the sales representatives role by setting the default access on the account object to Private.
8. The OWD on the lead object is set to Public Read-Only. Which statements are true regarding this?
   1. Only the owner can manually share the record.
   2. The administrator can manually share the record, as well as change the lead's ownership.
   3. Users in the role above the current owner can see the record and edit it. 
   4. The owner cannot change ownership of the record.
   5. Any owner or administrator can manually set the lead setting access to Private.
   6. Any owner or administrator can manually set the lead setting access to Public Read-Only.
   7. Any owner or administrator can manually set the lead setting access to Public Read/Write.

9. You are sharing policies on the account object involves highly complex logic, such as making queries on different related child objects and external system Apex callouts. What can you do to achieve this?
   1. Enable a sharing model that involves criteria-based sharing rules for the child objects queries and manual sharing for the external system Apex callouts.
   2. Set the OWD of the account object to Private or Public Read-Only (depending on the requirements) and deliver Apex managed sharing by implementing custom Apex code with a developer of your team.
   3. Set the OWD of the account object to Private and allow users to use manual sharing with predefined public groups.
10. Service representatives work in groups and share their accounts and related objects (such as cases or opportunities) to provide a better service experience to their customers. While owning an account, a service representative wants to give access to their team. How can they do this?
    1. Enable account teams and instruct the service representative on how to set up an account team and provide read/write access to case and opportunity objects.
    2. Enable opportunity teams and instruct the service representative on how to set up an account team and provide Read/Write access to case and account objects.
    3. Enable case teams and instruct the service representative on how to set up an account team and provide read/write access to account and opportunity objects.
11. You can set up different team roles for opportunity and account teams.
    1. True
    2. False
12. You can set up different team roles for case and account teams.
    1. True
    2. False

13. You found that a lot of contacts are not related to any account. What does this mean?
    1. The account field on the contact object is always required.
    2. Unparented contacts are always considered with OWD set to Private, regardless of the OWD configuration. 
    3. Contact sharing rules are not applied to this category of contacts. 
    4. Unparented contacts are always considered with OWD set to Public Read-Only, no matter the OWD configuration.
14. Manager users cannot see case records owned by their subordinates. How can we deal with this? The OWD on the case record is set to Private:
    1. The OWD should be changed to at least Public Read-Only.
    2. The OWD on the case records may have the Grant Access Using Hierarchies set to false.
    3. Check the manager profile and see if it doesn't have the case's OLS set to Read or Edit. 
    4. Check the manager profile and see if it doesn't have the case's sharing model set to Owned by Manages.
    5. The OWD on the case records may have the Controlled by Parent value.
15. What is data skew?
    1. A performance degradation issue caused by users that own thousands of records
    2. A performance degradation issue caused by a few accounts with thousands of related children 
    3. A performance boost created by the defer automatic sharing rule calculations feature
16. Your sales strategy depends on accounts based on the Industry field (for example, utilities, high-tech, software, and food) but also on geographic regions (such as EMEA, north-america, and asia-pacific). How can you configure your organization to match this territory configuration?
    1. Enable Enterprise Territory Management and define territory types based on geography and industry.
    2. Enable Enterprise Territory Management and define territory types based on geography only.
    3. Enable Enterprise Territory Management and define territory types based on industry only.
    4. You cannot mix territories of a different kind in your model.

17. Which statements are true about Enterprise Territory Management?
    1. You can open access to account, contact, opportunity, and case objects but not custom objects.
    2. You can open access to account, contact, opportunity, case, and custom objects.
    3. You can assign accounts and opportunities manually to a given territory.
    4. An account and a related opportunity can belong to different territories at a given time.
    5. An account can belong to different territories at a given time.
18. Your organization has a partner community that's used by sales partners so that they can create opportunities. You want all the opportunities that are used by partner users to be shared with all internal sales representatives. How can you do this?
    1. Enable sharing sets for your community.
    2. Enable share groups for your community.
    3. Enable partner roles on the community's setup and create sharing rules for each partner role that opens up access to sales representative users.
    4. Enable partner superuser access.
19. Which kind of objects can be shared with high-volume users using sharing sets?
    1. All objects, no matter their format
    2. Only objects that are related to the user's account/contact/user object 
    3. Only accounts, contacts, and users