# Free SSAV practice questions

> 10 free SSAV practice questions with the correct answer and an explanation.

Page: https://devopscodelab.com/exams/salesforce-sharing-and-visibility/free-practice-questions/
Practice exams: https://devopscodelab.com/exams/salesforce-sharing-and-visibility/

### Question 1 of 10

A financial services firm uses Experience Cloud for thousands of advisors at partner firms. Advisors use Customer Community Plus licenses. Each partner firm's account has a three-level hierarchy of partner users, and the firm wants to cut the number of roles created per partner account without losing the ability for firm managers to see their advisors' records. What should the architect do?

- A. Convert advisors to Customer Community licenses and give the firm managers Delegated External User Administration to view records
- B. Set the number of partner roles to two in the Experience Cloud settings, so that each new account creates only a manager and a user role
- C. Assign every advisor in the partner firm to the executive role of the partner account so that all advisors share one role and its visibility
- D. Disable the role hierarchy for external users and create one sharing set per partner account to expose the advisors' records to managers

**Answer:** B

**Explanation:** The Roles setting for partner and customer accounts controls how many roles are created per account (one to three), so reducing it to two keeps a manager-over-user structure while cutting role count. Customer Community licenses have no roles, and delegated administration manages users rather than granting record visibility. Sharing sets grant access based on account or contact lookups and do not model manager-over-subordinate visibility. Putting everyone in the executive role would give all advisors visibility into each other's records.

### Question 2 of 10

A company stores sensitive Bonus fields on the User object. Managers should see bonus values for their direct and indirect reports only. Which approach meets this requirement?

- A. Keep the fields on User and enable Enhanced Personal Information Management for every manager and their direct reports
- B. Move bonus data to a custom object with a Private OWD and share records to the employee's Manager Subordinates group
- C. Use field-level security on the Bonus fields on User, granting them to a permission set for managers only
- D. Keep the fields on User and set the User OWD to Private so managers see only their reports

**Answer:** B

**Explanation:** Field-level security on User cannot vary by which user record is being viewed, so moving the data to a custom Private object and sharing each record with the relevant manager group (for example through Manager Groups) scopes visibility by reporting line. A permission set with FLS would show bonus values for every user. Enhanced Personal Information Management hides personal fields from external users, not from colleagues. The User OWD controls who can see user records, not specific fields.

### Question 3 of 10

Universal Containers has a Private organization-wide default on Opportunity. Sales engineers report to a separate branch of the role hierarchy than account executives, and they must have Read/Write access to every opportunity whose Product Line field equals 'Industrial Robotics', regardless of owner. What is the most scalable solution?

- A. Opportunity teams that a scheduled flow populates with every sales engineer whenever an Industrial Robotics opportunity is created or updated
- B. A criteria-based sharing rule on Opportunity for Product Line equals 'Industrial Robotics' that grants Read/Write to a public group containing the sales engineers' role
- C. A permission set with Modify All on Opportunity assigned to every sales engineer so that they can maintain Industrial Robotics deals
- D. An owner-based sharing rule that shares all opportunities owned by the account executives' role with the sales engineers' role and subordinates

**Answer:** B

**Explanation:** A criteria-based sharing rule evaluates the field value and shares only matching opportunities, and sharing to a public group based on a role keeps membership automatic as engineers join or leave. Populating opportunity teams through a flow creates many share rows and custom automation to maintain. An owner-based rule would share every opportunity the account executives own, not just Industrial Robotics. Modify All grants access to all opportunities, which is far broader than required.

### Question 4 of 10

A large org has Users OWD set to Private. Partner users at different partner accounts must not be able to look up each other's users, but internal sales reps should still see every partner user who works on their accounts. What should the architect do?

- A. Disable the Portal User Visibility setting so that partner users can see every user in the org through lookups and the user directory
- B. Set the User OWD to Public Read Only for external users and hide partner users from search with field-level security
- C. Keep the User OWD Private for external users and create user sharing rules granting internal sales roles access to partner users
- D. Create a share group for each partner account that includes the internal sales reps and the partner's users

**Answer:** C

**Explanation:** With a Private external User default, partner users see only themselves and those users granted to them, and user sharing rules can give internal roles visibility of partner users. Public Read Only for external users would let partners see each other's users. Disabling Portal User Visibility reduces, not widens, what portal users can see and does not help internal reps. Share groups apply to records owned by high-volume users, not to partner user visibility for internal staff.

### Question 5 of 10

A software company plans a customer portal for 3,000 B2B customer admins. Each customer company has managers who must see records owned by their colleagues, and the business wants role-based sharing rules for some objects. Which license should the architect recommend?

- A. Customer Community, which supports sharing sets and share groups at high volume
- B. Customer Community Plus, which supports roles and sharing rules
- C. Partner Community, which is required for any role-based visibility
- D. Customer Community, after enabling super user access

**Answer:** B

**Explanation:** Customer Community Plus includes account roles and supports role-based sharing rules, meeting the manager visibility requirement at this moderate scale. Customer Community users are high-volume and have no roles, and super user access does not add a role hierarchy to them. Plain Customer Community with sharing sets cannot model manager-over-colleague visibility. Partner Community is meant for channel partners, not customer portals, even though it also has roles.

### Question 6 of 10

A medical device manufacturer stores Service Contract Review records in a custom object. Reviewers should see only the reviews they own, but each regional quality manager must see every review owned by reviewers in their region. Reviewers in other regions must never see each other's reviews. The role hierarchy already mirrors the regional reporting lines. What should the architect configure?

- A. Set the object's organization-wide default to Public Read Only and add a criteria-based sharing rule per region
- B. Set the object's organization-wide default to Private and create an owner-based sharing rule from each region's role to itself
- C. Set the object's organization-wide default to Controlled by Parent and relate each review to the reviewer's account
- D. Set the object's organization-wide default to Private and keep Grant Access Using Hierarchies selected

**Answer:** D

**Explanation:** A Private default limits each reviewer to their own reviews, and Grant Access Using Hierarchies automatically opens those records to managers above the owner in the role hierarchy. Public Read Only would expose every review to all reviewers. A role-to-same-role sharing rule would let peers in a region see each other's reviews, which the requirement forbids. Controlled by Parent only applies to detail objects in a master-detail relationship and would tie access to account visibility instead of the reporting line.

### Question 7 of 10

A healthcare provider stores patient Encounter records with a Private OWD. Clinicians in a care team need access only while assigned to the patient; assignments last a few days to weeks and are managed in an external scheduling system that sends updates through an integration. What is the most robust design?

- A. Manual sharing by the charge nurse for each assignment, with a weekly report to remove stale shares
- B. Criteria-based sharing rules on an Assigned Clinician text field that share matching encounters with a public group of all clinicians
- C. Integration sets the Encounter owner to the currently assigned clinician so that ownership provides access
- D. Integration maintains Apex managed shares with a custom sharing reason, adding and removing them as assignments change

**Answer:** D

**Explanation:** Apex managed shares with a custom reason can be created and removed precisely as assignments change and persist through ownership changes, which fits time-bound, externally driven access. Changing ownership loses the record's true owner and supports only one clinician. Criteria rules on a text field cannot share with the specific user named in the field and would expose records to all clinicians. Manual sharing with weekly cleanup leaves stale access and relies on discipline.

### Question 8 of 10

A custom Grant Application object has a Private OWD. When an application is submitted, the reviewer selected in a lookup field must get Edit access, and the access must persist even if the application owner changes. What should a developer implement?

- A. Apex that inserts Grant_Application__Share rows with the row cause set to Manual in an after trigger
- B. A record-triggered flow that adds the reviewer as an owner of the record through a queue assignment
- C. Apex managed sharing that inserts Grant_Application__Share rows with a custom Apex sharing reason
- D. A criteria-based sharing rule on the reviewer lookup field shared with a public group of reviewers

**Answer:** C

**Explanation:** Shares created with a custom Apex sharing reason are retained when the record owner changes, which meets the persistence requirement. Shares with row cause Manual are removed on ownership transfer. Criteria-based sharing rules cannot share with a user identified by a lookup field and would grant all reviewers access. Changing ownership to a queue would remove the applicant's ownership instead of adding reviewer access.

### Question 9 of 10

A developer must write a batch that recalculates Apex managed shares on a custom object after a reorganization. How should it be registered so that administrators can rerun it from Setup?

- A. Schedule the class hourly with System.schedule from the Developer Console
- B. Run the logic in a trigger on the User object that fires whenever a user's role changes during the reorganization
- C. Expose the class as a REST resource that administrators call from Workbench
- D. Associate a class implementing Database.Batchable with the object's Apex sharing recalculation

**Answer:** D

**Explanation:** Apex sharing recalculation classes implement Database.Batchable and are associated with a custom object, which adds a Recalculate button in the object's sharing settings. A REST resource or scheduled job works but cannot be launched from the sharing settings and needs extra tooling. Triggers on User are not allowed to perform mixed DML on setup and non-setup objects and are not a recalculation mechanism.

### Question 10 of 10

An integration loads 400,000 Contact records nightly, all owned by a single integration user who has no role. Users report slow sharing recalculation and occasional record-locking errors when the integration runs alongside daytime edits. Which design change most directly reduces the problem?

- A. Assign the integration user to a role at the bottom of the role hierarchy so that the records roll up to managers
- B. Change Contact to Public Read/Write so that no sharing rows are needed when records are loaded overnight
- C. Move the integration user into a public group and share the records with that group through a sharing rule
- D. Distribute ownership of the records across several users so that no single owner holds more than about 10,000 records

**Answer:** D

**Explanation:** Ownership skew occurs when one user owns a very large number of records; spreading ownership keeps owners under roughly 10,000 records and reduces recalculation work and lock contention. Placing a high-volume owner low in the hierarchy actually increases sharing work because access must propagate up many levels. Public Read/Write sidesteps the issue only by abandoning the security requirement. Adding sharing rules to a group creates more share rows, not fewer.

Ready for a timed run? Take the free 15-question SSAV mini exam: https://devopscodelab.com/app/exams/salesforce-sharing-and-visibility/mini/

DevOpsCode Lab is not affiliated with Salesforce. SSAV and related names are trademarks of their owners. We write every question ourselves; these are not real exam questions.
