Salesforce Certified Sharing and Visibility Designer Exam

Question 6 of 119

Every day, Ursa Major Solar uploads a large number of parent and child records into Salesforce to maintain integrations with other systems that update their data in scheduled batches or continuously in real time. Ursa Major Solar is concerned about locking errors.

Which two situations may introduce locking errors for Ursa Major Solar? (Choose two.)

Updates to parent records and their child records being processed simultaneously in separate threads

Updates to child records that have the same parent records are being processed simultaneously in separate transactions

Updates to parent and child records are being processed synchronously in the same threads

Updates to parent and child records are being processed in the same batch

Question 7 of 119

Cloud Kicks recently started a community for its customers using the Customer Community license type. They have implemented a custom object to store service requests that has a lookup to the account record. The Organization-Wide Default External Access to the service request object is set to Private.

Cloud Kicks wants their customers to be able to see service requests for their account through the community. However, customers should not see service requests for other accounts.

How should the Architect implement this while using a Salesforce feature?

Utilize manual sharing to share the service requests manually when a new community user is added

Utilize a Sharing Set to share service requests related to the account based on the community user’s profile

Utilize a Sharing Rule to share service requests to the community user based on their role

Utilize Apex Managed Sharing to share service requests related to the account to the appropriate community users

Question 8 of 119

Get Cloudy Consulting has a custom Contract object that requires Org-Wide Defaults set to Private. The owner of the Contract record will be the Contract Origination Officer, and the Contract record must be shared with a certain Underwriter on a contract-by-contract basis. The Underwriters should only see the Contract records for which they are assigned.

Which recommendation is appropriate for meeting these requirements?

Create a master-detail relationship from the Contract to the User object. Contract records will be automatically shared with the Underwriter.

Use criteria-based sharing rules to share the Contract object with the Underwriter based upon the criteria defined in the criteria-based sharing.

Create an Apex Sharing Reason on the Contract object that shares the Contract with the Underwriter based upon the criteria defined in the Sharing Reason.

Create a lookup relationship from the Contract object to the User object. Use a trigger on the Contract object to create the corresponding record in the Contract Share object

Question 9 of 119

Cloud Kicks has the following setup and requirements:

A strict software architecture for their custom Apex code.

All SOQL queries must be contained within reusable classes.

Depending on the context of the Apex transaction, the queries should be able to run either “With Sharing” or “Without Sharing”.

What are two methods for meeting these requirements? (Choose two.)

1. Create a SystemSOQLQueries class and a UserSOQLQueries class.
2. Set the “With Sharing” keyword on the UserSOQLQueries class and “Without Sharing” on the SystemSOQLQueries class.

1. Create a reusable SOQLQueries class.
2. Specify “With Sharing” on the methods that require user context and “Without Sharing” on the methods requiring system context.

1. Create a reusable SOQLQueries class.
2. Do NOT specify “With” or “Without Sharing” on the SOQLQueries class and use the runAs() method to dynamically set the context.

1. Create a reusable SOQLQueries class.
2. Do NOT specify “With” or “Without Sharing” on the SOQLQueries class.

Question 10 of 119

Cloud Kicks, a global corporation, has the following environment:

50,000 users

24×7 call center operated by 25,000 users, including both employees and contractors

A sales organization that has 15,000 users

The sales organization began processing about 120,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?

Due to system-initiated sharing rule recalculation, there is Lock contention

Due to Territory object updates, there is Lock contention on Territory object

Due to Action Plan custom object updates, there is Lock contention on Case records

Due to Opportunity object updates, there is Lock contention on Account records