Certified Sharing and Visibility Architect — Free Practice Questions
10 free sample questions from a bank of 51, with the correct answers and explanations. No signup required — start practising right now.
1Universal Containers uses 75,000 distributors that have close to 1 million total users. Distributors need to use the community to see closing opportunities assigned to their distributor for delivery.
What license recommendation will meet distributor needs?
Customer Community
Customer Community Plus
Sales Cloud
Partner Community
Answer: D
The short version
D — Partner Community is the correct license. Distributors need role-based sharing and opportunity access, which is the Partner Community use case.
Key concepts in this question
Partner Community license: broadest sharing and CRM object access for B2B partners, with external roles.
Customer Community vs Plus: basic support access; Plus adds roles but not full partner sales access.
Opportunity visibility for distributors: closing opportunities assigned to their distributor for delivery.
Why D is correct
Distributors are partners/resellers needing access to sales objects such as opportunities. Partner Community offers the broadest sharing and CRM object access among community licenses, including external roles and role-based sharing rules needed to scope each distributor to its own opportunities.
Why the others are wrong
A. Customer Community has no roles and suits basic cases/knowledge, not distributor opportunity sharing.
B. Customer Community Plus adds roles and reports but is aimed at customers needing advanced access, not B2B partners working opportunities.
C. Sales Cloud full licenses for 1 million distributor users are cost-prohibitive and unnecessary for community delivery visibility.
Certified-Sharing-and-Visibility-Architect exam tip
Distributors, resellers, dealers = Partner Community; customers needing support = Customer Community; customers needing roles and reports = Customer Community Plus.
2Universal Containers (UC) has a partner community for its 200 distributors. UC customer accounts are assigned an individual distributor. The organization-wide default setting for the custom Delivery object is private.
How can an architect advise UC to grant all users at a distributor access to delivery records for all customers assigned to a particular distributor?
Create a criteria-based sharing rule that shares delivery records matching a distributor to the Distributor role in the role hierarchy.
Create a criteria-based sharing rule that shares delivery records matching the Distributor to users of a Public Group created for the distributor.
Give ownership of the delivery record to a distributor user.
Create a Sharing Set for the Distributor Profile to grant access to the Delivery object.
Answer: D
Correct answer: D
The short version
Create a Sharing Set for the Distributor profile with Delivery as the target object. A sharing set is the declarative Experience Cloud mechanism that opens record access to external partner users in bulk, matching on the user's account or contact instead of on the internal role hierarchy.
Key concepts
Sharing set / sharing set rule: an access mapping (Account, or Account and Contact) that grants site users read or read/write on the target object's records whose related account or contact matches theirs. Profiles, not roles, scope it to external users.
Partner account role hierarchy is not the internal role hierarchy, so criteria-based sharing rules cannot target it.
Sharing rules have a hard ceiling of 50 per object, so a per-distributor design is not viable at 200 distributors.
OWD Private means nobody but the owner sees Delivery records until one of these mechanisms opens them up.
Why D are correct
Delivery is private by default, so access has to be granted declaratively. The business rule is a relationship rule - each Delivery record belongs to a customer account, and each customer account belongs to one distributor - and a sharing set is exactly the tool that turns that relationship into record access for every site user at that distributor. One sharing set serves all 200 distributors, it recalculates when account assignments or partner contacts change, and it needs no Apex and no nightly job. Options A and B would each need one criteria-based rule per distributor and would target internal roles or public groups rather than the partner users who need the access.
Why the others are wrong
A. A criteria-based sharing rule cannot resolve "the Distributor role in the role hierarchy" for partner community users: they are external users with partner-account roles, and the internal role hierarchy the rule would target does not contain them. Even if they were internal, one rule per distributor is not scalable at 200 distributors.
B. A public group per distributor works only as a sharing-rule target, so it inherits the same one-rule-per-distributor ceiling, and public-group membership for external users is not the model the sharing engine resolves customer-to-distributor relationships through.
C. Giving one distributor user ownership makes exactly one user see the record. The requirement is all users at the distributor, and ownership also destroys the accountability model the account assignment is meant to preserve.
Sharing-and-Visibility exam tip
External Experience Cloud or partner users are served by sharing sets, share groups and super-user access; internal users are served by OWD, the role hierarchy, sharing rules, teams and Apex. If the target of the access is people outside the org, look at sharing sets first.
3The architect has a requirement to create a criteria-based sharing rule based on the customer Social Security number. However, when setting up the rule in Contact Sharing, the field is not shown on the list of available fields.
What might cause this?
Text fields with validation rules are not available for sharing rules.
The architect’s profile does not have Field level Security (FLS) for this field.
The field has been configured for encryption.
The architect does not have permission to Compliance fields.
Answer: C
The short version
C — The SSN field is encrypted, so it cannot drive a criteria-based sharing rule. Encrypted fields are excluded from rule criteria.
Key concepts in this question
Criteria-based sharing rules: share by record field values rather than ownership.
Encrypted field restrictions: encryption removes fields from filters, criteria, and sorting surfaces.
SSN as sensitive data: commonly protected with Shield Platform Encryption.
Why C is correct
The SSN field does not appear in the sharing-rule field list because encrypted fields are ineligible for criteria-based sharing rules. Encryption intentionally blocks value-based filtering, so the architect must use another mechanism such as owner-based sharing or Apex managed sharing.
Why the others are wrong
A. Validation rules do not remove text fields from sharing-rule criteria.
B. The architect's own FLS does not control which fields appear as rule criteria org-wide.
D. There is no such gatekeeping Compliance-field permission that hides rule criteria.
Certified-Sharing-and-Visibility-Architect exam tip
Encrypted + lookup + formula + derived fields can never be used in criteria-based sharing rules.
4What should a Salesforce architect recommend to make sure that users that gained access to a custom object record through Apex managed sharing do not lose access to it when its owner is changed?
Use “With Sharing” keyword to make sure record visibility will be considered.
Create a specific Apex Sharing Reason for the custom object.
Create a new record in _Share object with RowCause “Manual”.
Use “runAs” system method in Apex classes to enforce visibility.
Answer: B
Correct answer: B
The short version
Create a specific Apex Sharing Reason for the custom object and write the share rows with that row cause. Rows created that way are Apex managed sharing, and Salesforce maintains them when the record's owner changes.
Key concepts
Manual sharing (share rows with RowCause = Manual) is owned by the record owner. The platform wipes those rows when ownership changes.
Apex managed sharing is share rows written from Apex or the API with a custom row cause; it survives owner change and user deactivation.
Apex sharing reason is the Setup metadata record that defines that custom row cause for a custom object, and it is what makes the grant attributable, auditable and re-calculable.
with sharing / without sharing are class-level keywords that affect queries at runtime; they change nothing about stored share rows.
Why B are correct
The access in this scenario was granted programmatically, and it evaporates when the owner changes - which is what happens to any share row carrying the default Manual row cause, because the platform assumes the new owner should decide who else sees the record. Salesforce documents the opposite behaviour for Apex managed sharing: it "is maintained when the record owner changes or is deactivated". Getting there requires an Apex sharing reason on the object, so that the rows are written with a custom row cause instead of the manual one. The bonus is that the reason becomes a filter you can query on the object's _Share table, so you can recalculate or retire exactly that grant without touching manual shares made by humans.
Why the others are wrong
A.With Sharing is a declaration about how the class's SOQL and DML evaluate row-level access while it runs. It does not change the RowCause of rows already written, so the owner change still deletes them.
C. This is precisely the failure mode being reported. Share rows inserted into the _Share object with RowCause = "Manual" are removed by the platform when ownership changes, so users who "gained access through Apex" by inserting manual rows lose that access on every transfer.
D.runAs only changes the user context inside a test method. It has no effect on production share rows and would never make an existing grant survive an ownership change.
Sharing-and-Visibility exam tip
Remember the two row causes: Manual dies with the owner, a custom Apex sharing reason does not. If code must grant access that outlives a transfer of ownership, always write the row with an Apex sharing reason, never with the default.
5The sales managers at Universal Containers (UC) requested their teams to define each user’s role on their accounts in order to provide an easy way to establish accountability and collaboration. Sales managers also requested that sales associated should only get the following permissions:
Read access to the accounts.
Read access to cases related to the accounts.
No access to deals related to the accounts.
The sales associates may be granted access to opportunities when needed.
Assuming the overall sharing model of the organization is private and no sharing rules are configured on the account object. How can an Architect achieve these requirements?
Use Account teams to define access to accounts as well as opportunities and cases related to accounts.
Use Account teams, Opportunity teams, and Case teams.
Use Account teams and use Sharing rules to share cases with sales associates. No change required to the opportunity object.
Use Account teams, Case teams. No configuration required for the opportunity object.
Answer: A
Answer: A
The short version
Use Account teams. An account team can grant a member read access to the account, read access to its cases, and - if you choose not to grant it - no access to its opportunities, which is exactly the requirement in one construct.
Key concepts
Account team associates users with an account and grants each member a defined access level to the account and to related records.
Team-based access on an account can extend to cases, opportunities and contacts, and it can be asymmetric: read on one related object, nothing on another.
Default Account team auto-populates the owner, which matters because the stem says no sharing rules exist on Account.
Opportunity teams and case teams are separate constructs for granting access when the account team is not the right lever.
Why A are correct
The requirement is a bundle of per-record access decisions on one parent: read on accounts, read on cases, nothing on opportunities, and opportunities only when specifically needed. The account team is the only construct that expresses all of it in one place. Add the sales associate to the account's team with read access to the account and its cases, and leave the opportunity access ungranted - then the associate has no deals access by default, and an admin can grant opportunity access on the team later "when needed". Nothing else has to be configured, and the model is easy for a manager to audit by opening the account team.
Why the others are wrong
B. Adding opportunity teams and case teams on top of the account team is redundant. The account team's related-record access already covers both, and maintaining three team memberships per account multiplies the work with no security benefit.
C. The scenario states that no sharing rules are configured on Account, and cases need no separate rule: the account team's related-record access already grants case read. Introducing sharing rules would add a second, conflicting mechanism for the same grant.
D. Account teams alone with no configuration note still leaves the question of opportunity access ambiguous, and treating opportunity access as requiring "no configuration" risks granting it by default through the account team's related-object access - the opposite of the "no access to deals" requirement.
Sharing-and-Visibility exam tip
Read bundles of per-record requirements as a team question. Account teams, opportunity teams and case teams exist to grant related-record access declaratively; sharing rules are for audiences defined by ownership or field criteria, and permission sets for object and field permissions.
6Universal Containers (UC) has implemented Customer Community with customer community plus licenses for its distributors. Some distributors requested granting specific community users (agents) to view cases submitted by other agents of the same distributor.
Which feature only supports these requirements?
Permission set to grant community admin permission
Delegate external user
Partner community admin
Partner super user
Answer: D
Answer: D
The short version
Partner super user access. It is the only feature on the list that lets selected community users see the cases and data owned by other users at the same distributor, and Salesforce makes it available to Customer Community Plus licence holders.
Key concepts
Super user access gives a community user read and edit on cases, leads, custom objects and opportunities owned by other users of the same account who sit at the same role or a lower one.
Community admin permission (a user permission, commonly assigned via a permission set) governs administration of the site - member management, password resets - not record visibility.
Delegate external user / delegated external administration delegates user lifecycle tasks such as activate, deactivate and reset passwords for partner users.
Partner Community Admin is a partner-licence role and does not exist for Customer Community or Customer Community Plus users.
Why D are correct
The requirement is horizontal visibility inside one distributor: agents at a distributor must see cases submitted by other agents at that same distributor. That is exactly the shape super user access is built for - it is scoped to the account, and it reaches users at the same role or below, so the whole distributor group participates without touching any other partner account. Because it is a permission granted on the user or its contact, an admin can switch it on for the agents at a distributor and off again as roles change, with no rules and no code. The other three options are all administrative surfaces that leave the Case sharing model exactly as it was.
Why the others are wrong
A. A permission set granting community admin permission confers site administration rights - managing members, resetting passwords, running community maintenance. It changes nothing about which Case records a user can query, so agents still cannot see each other's cases.
B. A delegate external user is an administrative delegate for partner users: they can activate and deactivate users and reset passwords within the bounds set by the delegating user. Delegation is about user setup, not about record access, so it does not surface other agents' cases.
C. Partner Community Admin is a partner-licence concept that does not exist for a Customer Community Plus audience, and even in a partner community it is an administrative profile-level role rather than a record-visibility mechanism.
Sharing-and-Visibility exam tip
Sort community features into two buckets before you answer: record-visibility tools (sharing sets, share groups, super user access, account and contact relationships) versus administration tools (community admin permission, delegated external administration, partner community admin). This question is squarely in the first bucket.
7Universal Containers (UC) uses a custom Lightning component with an Apex class to display shipment information (custom object, private OWD). UC sales managers are complaining about two important points:
Shipment records that belong to their teams can be seen by other users.
Shipment amount should be visible only by managers, but sales reps are able to view it.
Which two features did the development team miss that is causing the problems? (Choose two.)
Use isSearchable keyword in Apex classes to assure record visibility.
Use With Sharing keyword in Apex classes to enforce sharing rules evaluation.
Use runAs in test class to enforce user permissions and field-level permissions.
Use isAccessible() method in Apex classes to check field accessibility.
Answer: B, D
The short version
BD — The Apex class needs with sharing for records and explicit FLS checks for fields. Apex enforces neither by default in a Lightning/Aura controller context.
Key concepts in this question
with sharing: enforces record-level sharing rules in Apex.
FLS/CRUD in Apex: never enforced automatically; requires describe checks, stripInaccessible, or user mode.
Private OWD custom object: leaking records and amounts points exactly at these two gaps.
Why BD is correct
Without with sharing the class runs in system context and returns shipment records other users should not see. Separately, even with sharing, Apex ignores field-level security, so the amount field must be gated with an accessibility check such as isAccessible before display. The two symptoms map one-to-one onto the two missing features.
Why the others are wrong
A. There is no isSearchable Apex keyword that controls record visibility.
C. runAs only applies inside test methods and enforces sharing for tests; it does not fix production visibility.
Certified-Sharing-and-Visibility-Architect exam tip
with sharing = records; isAccessible/stripInaccessible/USER_MODE = fields; memorize the split.
8Universal Containers (UC) is a non-profit organization and has over 20,000,000 members (donors). The company decided to assign those accounts to Donations Reps based on their regions. Donations Reps ended up owning over 50,000 donors each.
The donation reps started to see significant degradation of the system performance.
What could be the reason for this problem?
The Donations Reps access to the assigned accounts.
The Account (donor) object OWD is Private.
There is an Account ownership data skew problem.
Salesforce sharing recalculation kicked off.
Answer: C
The short version
C — Each rep owning 50,000 donor accounts is textbook ownership data skew. Past the 10,000-record threshold, sharing calculations and locks degrade performance.
Key concepts in this question
Ownership data skew: one user owning more than about 10,000 records of an object.
Sharing recalculation cost: ownership changes and group operations fan out across every owned record.
20M donors over few reps: 50,000 each is five times the guideline.
Why C is correct
Assigning donors by region concentrated over 50,000 account records per donation rep. Above the 10,000-record ownership guideline, every sharing recalculation, role change, or ownership transfer becomes long-running and lock-prone, which matches the reported systemic slowdown.
Why the others are wrong
A. Merely having access to assigned accounts is normal and does not itself cause degradation.
B. A Private OWD alone is a standard, performant baseline; the volume-per-owner is the problem.
D. A sharing recalculation may be the symptom, but the skew is the root cause triggering it.
Certified-Sharing-and-Visibility-Architect exam tip
One owner > 10,000 records = ownership skew; one parent > 10,000 children = account/data skew.
9What vulnerability can exist when controllers use dynamic rather than static queries and bind variables?
Buffer Overflow Attacks
Record Access Override
SOQL Injection
Cross-site scripting
Answer: C
Answer: C
The short version
SOQL injection. When Apex builds a dynamic query by concatenating end-user input into the query string, the user can supply their own SOQL and make the org execute database operations the developer never wrote.
Key concepts
Dynamic SOQL is built at runtime with Database.query(...) and is the only way to assemble a query whose shape is not known at compile time.
Bind variables (:variableName, or the typed Database.queryWithBinds) send values separately from the query text, so input can never be parsed as SOQL.
SOQL injection is what an attacker achieves when input is concatenated into the query rather than bound.
Buffer overflow, cross-site scripting and record-access override belong to memory-safety, browser and sharing layers respectively - none is produced by query construction.
Why C are correct
Dynamic SOQL exists for legitimate reasons - the object, fields or filter values are only known at runtime - but it is also the one place where user input can change the shape of the statement instead of its values. If a controller passes a search term into a string that is then handed to Database.query, the term can carry FROM, a relationship traversal or a WHERE clause of the attacker's choosing, so the org runs a query the developer never authorised. Binding the variable, or restricting the query with String.escapeSingleQuotes as a last resort, keeps the input in the value position where SOQL cannot reinterpret it. That risk exists only for dynamic queries, which is why the stem's dynamic-versus-static contrast is the whole question.
Why the others are wrong
A. A buffer overflow is a memory-safety defect in native code; Salesforce's managed runtime is not the place where an examiner is asking you to find it, and nothing about query construction produces one.
B. A record access override is a sharing problem - code that runs without sharing, or View All used where it should not be. It is about which rows a user may see, not about the text of a statement, and it would occur with a static query just as easily.
D. Cross-site scripting is an output-encoding problem: untrusted data rendered in a browser without escaping. It lives in Visualforce, Lightning web components or any rendered string, not in how a SOQL string is assembled.
Sharing-and-Visibility exam tip
For every dynamic SOQL question, look at how the value travels. Concatenation is an injection bug; bind variables are the fix. And keep the vulnerability classes separate - XSS is rendering, buffer overflow is memory, and a record access override is sharing.
10Universal Containers has a large network of partners, who each have seasonal workers that need short-term access to the community.
How might the Architect design the solution to federate user setup to the Partners? (Choose two.)
Assign delegated external administrators at each partner.
Grant the Modify Users permission to the partner managers.
Create a permission set giving Read/Write to the User object to partner manager.
Allow external users to self register.
Answer: A, D
Answer: A and D
The short version
Delegate external administration at each partner, and let external users self-register. Between the two, partners can provision seasonal workers themselves and new users can activate themselves, instead of routing every request through UC administrators.
Key concepts
Delegate external user / delegated external administration lets a designated partner user manage a bounded set of partner users - activate and deactivate them, reset passwords, assign roles - without holding admin rights over the whole org.
Self-registration lets an external user create and activate their own account from the site, subject to the site's profile and licence restrictions.
Modify Users is a broad internal permission; Activate Users is the specific permission that governs activating and deactivating accounts.
Delegation is bounded on purpose: the delegate can only manage users beneath them in the partner hierarchy.
Why A and D are correct
The estate is 75,000 partners with seasonal staff, so any centrally administered queue becomes the bottleneck. Delegated external administration pushes routine provisioning to the partner who actually knows the joiners and leavers, while the partner organisation keeps control of how far that delegation reaches. Self-registration removes the remaining hand-off: a seasonal worker can create and activate their own account, and the partner or UC admin only has to deal with exceptions. Together they are the scalable design - both are declarative, both are supported for partner licences, and neither requires custom code.
Why the others are wrong
B. Modify Users is far too broad an instrument for this job - it is not assignable to a partner licence in the first place, and even where it exists it grants sweeping user-administration rights rather than the bounded, delegated provisioning the requirement describes.
C. A permission set granting read/write on the User object lets a partner manager edit user records, but editing a record is not the same as managing access. Activating or deactivating accounts needs the Activate Users permission specifically, and a plain edit of the User record will not suspend anyone's login. So C does not deliver the delegation behaviour the requirement needs.
Sharing-and-Visibility exam tip
On Experience Cloud user management, remember the separation: record access to the User object is not account activation. Delegated external administration and self-registration are the two federated models; anything built on User-object CRUD alone will not let a partner suspend a seasonal worker.