Free Salesforce Sharing and Visibility Architect Practice Questions with Answers

Correct answer: D. Grant Managers access to the fields using Field-Level Security; do not add them to a page layout.

Field-Level Security controls field visibility independently of page layouts, so Managers can have Read access to the 50 fields (making them available for reports) without those fields ever appearing on a page layout and cluttering the UI.

Correct answer: B. Enable Salesforce Shield Platform Data Encryption and mark the patient notes field as encrypted.

Shield Platform Encryption supports encryption of long text area fields (unlike the legacy Classic Encrypted Text field type, which is limited to short text) while data is at rest, satisfying the regulatory requirement without custom Apex encryption logic.

Correct answer: A. The users are in profiles that have no access to the Account object.

A sharing rule can only extend record-level visibility beyond what the OWD provides; it can never grant more access than the user's profile-level object permissions allow. If the affected users' profiles have no Read access to the Account object at all, the sharing rule is powerless to show them any Account records regardless of group membership.

Correct answer: A. Bob and Phil

Manual shares are tied to the specific record and are automatically removed when the record's owner changes, unless the sharing was created with a custom Apex Sharing Reason. Since Karen's manual share to Kevin was a standard manual share, it is deleted when Phil becomes the new owner. Access after the change is limited to the new owner (Phil) and anyone above him in the role hierarchy (Bob, the CEO).

Correct answer: D. Read-only access.

Access to a child Opportunity grants implicit Read-only access to the parent Account, even when the OWD for Account is Private and the user has no other explicit access to that Account, so that the Opportunity record makes contextual sense to the user viewing it.

Correct answer: D. Set the organization-wide default to Private and uncheck the "Grant Access Using Hierarchies" option.

Setting the OWD to Private restricts NPS records to the owner by default, and unchecking "Grant Access Using Hierarchies" (available for custom objects) specifically blocks the automatic visibility that managers above the owner in the role hierarchy would otherwise receive, which is exactly the access this requirement needs to prevent.

Correct answer: D. The Invoice Line Item object should have a Master-Detail relationship to the Invoice object.

A Master-Detail relationship from Invoice Line Item (child) to Invoice (parent) both enables declarative roll-up summary fields for Quantity/Extended Amount on Invoice, and ensures Invoice Line Items always inherit the parent Invoice's sharing (Controlled by Parent) so anyone who can see the invoice automatically sees all of its line items.

Correct answer: A. Build Apex Managed Sharing code to share the Job Interview record with the Interviewer user.

Declarative criteria-based and owner-based sharing rules can only share to Public Groups, Roles, Roles and Subordinates, or Territories, not dynamically to whatever specific user happens to be populated in a lookup field on the record. Only Apex Managed Sharing (typically via a trigger on the lookup field change) can programmatically create a share record targeting the exact user referenced by the Interviewer lookup.

Correct answer: A and C. Public Groups / Roles and Subordinates

List views can be shared with Public Groups or Roles and Subordinates. Profiles and Manual Sharing are not valid sharing targets for list view visibility.

Correct answer: D. Remove the "Export Reports" profile permission.

The "Export Reports" system permission on a Profile (or Permission Set) is the control point that governs whether a user can export report data to Excel/CSV; removing it prevents export regardless of folder settings, since report folders do not have a granular "Allow Export" toggle.

Correct answer: A. Minimize possible performance impacts by not assigning the user(s) to a role.

Ownership (or "record") data skew occurs when a single user owns an excessive number of records of an object, which is compounded when that user has a role in the hierarchy (triggering costly sharing recalculations up the chain). Not assigning the high-record-count owner (such as an integration or queue-like user) to a role minimizes the performance impact of that skew.

Correct answer: B and C and E. Deferred Sharing Recalculation / Parallel Sharing Rule recalculation / Granular Locking

Deferred Sharing Recalculation postpones sharing rule recalculation until after bulk role/ownership changes complete, avoiding repeated recalculation during the operation. Parallel Sharing Rule recalculation speeds up the eventual recalculation across multiple processes. Granular Locking prevents "unable to lock row" errors on the group membership table when many role/group changes happen concurrently.