Question bank
Salesforce Certified Sharing and Visibility Designer
40 Salesforce Certified Sharing and Visibility Designer questions with the correct answer and a written explanation, organised across 4 exam domains.
- 40 questions
- 4 domains
- Foundation level
certilumQuestion index
Jump straight to any question. Answers and explanations are inline.
Data Access
12 questions in this domain
- Question 1Single Choice
When a user has access to an Account record, what is the automatic visibility of related child records called?
- AExplicit sharing
- BImplicit sharingCorrect answer
- CManual sharing
- DApex sharing
Why this is the answer
Implicit sharing grants access to related child records through parent record access, such as Account-to-Contact and Account-to-Opportunity relationships.
- Question 2Multiple Select
Select all common parent-to-child relationships where implicit sharing can grant access to child records.
- AAccount to ContactCorrect answer
- BAccount to CaseCorrect answer
- CAccount to OpportunityCorrect answer
- DContact to Account
Why this is the answer
Implicit sharing commonly flows from Account to Contacts, Cases, and Opportunities. Access does not typically flow from child Contact to parent Account.
- Question 3Interactive
Review the Apex class in the code block. Which statement about Field-Level Security is true?
- AIt automatically enforces FLS
- BIt does not enforce FLSCorrect answer
- CIt only enforces FLS for Account
- DIt prevents the query from running
Why this is the answer
`with sharing` enforces record-level sharing, not Field-Level Security. Use `Security.stripInaccessible()` or `WITH USER_MODE` to enforce FLS.
- Question 4Single Choice
In a Master-Detail relationship, what is the child record's ownership model?
- AChild has its own owner
- BChild inherits the master's ownerCorrect answer
- CChild is owned by the running user
- DChild is unowned
Why this is the answer
Master-Detail records do not have independent owners. The detail record inherits its owner and security from the master record.
- Question 5Multiple Select
Select two characteristics that are true of Lookup relationships when compared to Master-Detail relationships.
- ANo native roll-up summary fieldsCorrect answer
- BVisibility controlled by parent
- COptional by design with independent ownershipCorrect answer
- DAutomatically delete children with parent
Why this is the answer
Lookup relationships are optional, allow independent ownership, and do not support native Roll-Up Summary fields. Deleting parent can nullify the lookup or be restricted.
- Question 6Interactive
Given the Apex class in the code block, how does it execute by default?
- ASystem ModeCorrect answer
- BUser Mode
- CObject Mode
- DMixed Mode
Why this is the answer
Apex runs in System Mode by default unless the class uses `with sharing`. This means sharing rules are not enforced automatically.
- Question 7Single Choice
For high-volume external users, which lightweight sharing mechanism maps a user to records through a common field?
- ASharing SetsCorrect answer
- BSharing Rules
- CRole Hierarchy
- DManual Sharing
Why this is the answer
Sharing Sets are designed for high-volume external users and grant access based on field values like Account ID or Contact ID.
- Question 8Multiple Select
Select all true statements about Territory Management.
- AETM is the modern standardCorrect answer
- BAssignment rules move Accounts into TerritoriesCorrect answer
- CTerritory Management grants access to all objects
- DUser assignment moves users into TerritoriesCorrect answer
Why this is the answer
ETM is the modern standard; assignment rules map Accounts to Territories and user assignment maps people to Territories. Territory access is focused mainly on Accounts and Opportunities.
- Question 9Interactive
What is the purpose of the security utility method used in the code block?
- AEnforce record sharing
- BRemove inaccessible fields from query resultsCorrect answer
- CDelete records without permission
- DSet field permissions
Why this is the answer
`Security.stripInaccessible` enforces Field-Level Security by removing fields from SOQL results that the current user cannot access.
- Question 10Single Choice
What is a common misconception about Experience Cloud users and the internal Role Hierarchy?
- ARole HierarchyCorrect answer
- BSharing Sets
- COWD
- DManual Sharing
Why this is the answer
A common trap is assuming the internal Role Hierarchy applies to all Experience Cloud users; many community licenses rely on Account relationships.
- Question 11Multiple Select
Select all traps that can undermine a sharing and visibility design.
- AAssuming OWD is the only factor that controls record accessCorrect answer
- BConfusing object-level security with record-level visibilityCorrect answer
- CAssuming implicit sharing flows from child to parentCorrect answer
- DUsing Sharing Sets for high-volume external users
Why this is the answer
Designers must avoid treating OWD as the only control, conflating object security with record access, and ignoring that implicit sharing flows from parent to child.
- Question 12Interactive
In the code block, why is the query likely to be selective for large data volumes?
- AIt uses the indexed OwnerId fieldCorrect answer
- BIt selects all accounts
- CIt has no WHERE clause
- DIt enforces FLS automatically
Why this is the answer
Filtering on an indexed field such as OwnerId makes the query more selective and avoids full table scans in large data volumes.
Design & Governance
8 questions in this domain
- Question 13Single Choice
In a Master-Detail relationship, how is the child record's ownership determined?
- AThe child record has its own owner
- BThe child record inherits the master's owner and security settingsCorrect answer
- CThe child record is assigned by a sharing rule
- DThe child record uses a lookup field to select an owner
Why this is the answer
In a Master-Detail relationship, the child record does not have its own owner and inherits the master record's owner and security settings.
- Question 14Multiple Select
Which statements about Master-Detail and Lookup relationships are accurate?
- ADeleting a master record deletes its detail recordsCorrect answer
- BLookup relationships support roll-up summary fields natively
- CA Master-Detail field is required at the database levelCorrect answer
- DLookup relationships allow independent ownership of child recordsCorrect answer
Why this is the answer
Master-Detail relationships enforce cascading deletion and required fields, while Lookup relationships allow independent ownership and do not support native roll-up summaries.
- Question 15Interactive
In an org with Private OWD on Account, what will the method in the code block return for a user with no explicit Account access?
- AOnly the accounts the user can accessCorrect answer
- BAll accounts in the org
- CAn exception because sharing is enforced
- DAn empty list because sharing is disabled
Why this is the answer
Apex declared with \"with sharing\" respects the org's sharing settings, so the user only sees accounts they have access to.
- Question 16Single Choice
Which relationship is the primary driver of implicit visibility from Account to Contact?
- ACase-to-Account relationship
- BAccount-to-Contact relationshipCorrect answer
- COpportunity-to-Account relationship
- DContact-to-Account relationship
Why this is the answer
The Account-to-Contact relationship is the primary driver of implicit visibility; access to an Account often grants implicit access to its Contacts.
- Question 17Multiple Select
Which of the following are common traps related to implicit sharing?
- AAssuming OWD is the only factorCorrect answer
- BAssuming Private OWD prevents all implicit access to child recordsCorrect answer
- CAssuming implicit sharing flows from child to parent
- DConfusing object-level security with record-level visibilityCorrect answer
Why this is the answer
Implicit sharing is often misunderstood: OWD is not the only factor, child access can be granted through the parent, and sharing does not flow from child to parent.
- Question 18Interactive
In an org with Private OWD on Opportunity, what does the method in the code block return when called by a user without explicit Opportunity access?
- AThe count of all Opportunity recordsCorrect answer
- BThe count of only accessible Opportunity records
- CAn error is thrown
- DThe value zero
Why this is the answer
Apex declared with \"without sharing\" runs in system mode and bypasses sharing rules, so it returns all records regardless of user access.
- Question 19Single Choice
In Enterprise Territory Management, what do assignment rules automate?
- AAccount assignment to territoriesCorrect answer
- BUser assignment to territories
- CCreation of permission set groups
- DDeletion of inactive accounts
Why this is the answer
Territory assignment rules automatically assign Accounts to Territories based on field values such as Zip Code, Industry, or Annual Revenue.
- Question 20Multiple Select
Which of the following accurately describe external sharing mechanisms?
- ASharing Sets map external users to records based on a common fieldCorrect answer
- BSharing Groups group multiple external users together for record accessCorrect answer
- CSharing Sets are designed for high-volume external usersCorrect answer
- DSharing Sets and Sharing Rules are the same mechanism
Why this is the answer
Sharing Sets use field mappings for high-volume external users, Sharing Groups combine multiple external users, and Sharing Rules are a separate traditional mechanism.
Sharing Model
10 questions in this domain
- Question 21Single Choice
What is the primary effect of implicit sharing from a parent record?
- AAccess to certain related child records without explicit sharing rulesCorrect answer
- BAccess to every record in the organization
- CAccess only to records owned by the user's manager
- DAccess to child records only after manual sharing is created
Why this is the answer
Implicit sharing automatically grants access to related child records when the parent is visible to the user.
- Question 22Multiple Select
Which two statements about Account-to-Contact implicit visibility are correct?
- AAccount access can grant implicit access to related Contacts when Contact visibility is not more restrictive.Correct answer
- BThe Account-to-Contact relationship is a primary driver of implicit visibility.Correct answer
- CContacts require explicit sharing rules even when the parent Account is visible.
- DAccount access never influences whether a user can see related Contacts.
Why this is the answer
Account-to-Contact is a primary implicit visibility driver; users with Account access often see Contacts unless Contact visibility is more restrictive.
- Question 23Interactive
Review the Apex class in the code block. What does the `with sharing` keyword enforce when this method is executed?
- ARecord-level sharing rules for the running user are enforced.Correct answer
- BAll record sharing rules are bypassed.
- CField-level security is automatically enforced.
- DObject-level security is ignored and no records are returned.
Why this is the answer
With sharing enforces record-level sharing; it does not automatically enforce field- or object-level security.
- Question 24Single Choice
Why is it a trap to assume Organization-Wide Defaults are the only factor in record visibility?
- AImplicit sharing may still grant access to child records through the parent record.Correct answer
- BOWD has no impact on record-level visibility.
- COWD always overrides implicit sharing.
- DOWD applies only to external users.
Why this is the answer
Even with Private OWDs, implicit sharing through a parent relationship can expose child records.
- Question 25Multiple Select
Which two statements correctly describe Sharing Sets for external users?
- ASharing Sets are a lightweight, high-performance mechanism for high-volume external users.Correct answer
- BSharing Sets map external users to records based on common fields such as Account ID or Contact ID.Correct answer
- CSharing Sets use the same criteria and owner logic as traditional Sharing Rules.
- DSharing Sets require Apex triggers to grant record access.
Why this is the answer
Sharing Sets provide high-volume external users with record access based on field mapping, not traditional sharing rules.
- Question 26Interactive
Review the Apex class in the code block. What is the most likely security risk when executing this class?
- AIt may expose records to users who should not see them because sharing rules are bypassed.Correct answer
- BIt will always trigger a governor limit exception.
- CIt enforces stricter field-level security.
- DIt prevents all users from querying Account records.
Why this is the answer
Without sharing bypasses record-level sharing rules, so queries can return records the user is not entitled to see.
- Question 27Single Choice
Which statement accurately compares the territory hierarchy with the role hierarchy?
- ARole hierarchy manages vertical access by management level; territory hierarchy manages horizontal access by business attributes.Correct answer
- BTerritory hierarchy and role hierarchy are identical.
- CRole hierarchy manages horizontal access; territory hierarchy manages vertical access.
- DA user can belong to only one territory.
Why this is the answer
Role hierarchy is vertical based on management; territory hierarchy is horizontal based on attributes and supports multiple memberships.
- Question 28Multiple Select
Which two statements describe how ownership influences implicit sharing?
- AOwning a parent record extends authoritative access to child entities within the data silo.Correct answer
- BImplicit sharing acts as an extension of the owner's access to related child records.Correct answer
- COwnership has no influence on implicit sharing.
- DOnly administrators receive implicit access through ownership.
Why this is the answer
Ownership is a strong driver of implicit sharing; owning the parent extends access to related child records.
- Question 29Interactive
Review the code snippet. A user has the Account object in their Profile but no sharing rule grants record access. Which statement about this scenario is correct?
- AObject-level security does not guarantee record-level visibility; the user still needs sharing access to specific records.Correct answer
- BThe `with sharing` keyword automatically grants record access.
- CProfile access to the Account object grants access to all Account records.
- DRecord sharing is irrelevant when the Profile includes the object.
Why this is the answer
Object access via Profile is not the same as record-level visibility; sharing must also provide access to the specific records.
- Question 30Single Choice
What is the primary purpose of Sharing Groups for external users?
- ATo group external users together and grant record access when Sharing Sets are too restrictive or account hierarchies are complex.Correct answer
- BTo replace the internal role hierarchy.
- CTo prevent external users from accessing any records.
- DTo assign Accounts to territories automatically.
Why this is the answer
Sharing Groups support more complex external sharing logic than Sharing Sets, especially for account hierarchies.
Visibility
10 questions in this domain
- Question 31Single Choice
Which statement best describes implicit sharing in Salesforce?
- AAccess to a parent record can grant access to related child records.Correct answer
- BAccess to a child record grants access to its parent record.
- CImplicit sharing only applies to records explicitly shared with the user.
- DImplicit sharing ignores Organization-Wide Defaults.
Why this is the answer
Implicit sharing flows from parent records to child records, such as from Account to its related Contacts, Cases, and Opportunities.
- Question 32Multiple Select
Which of the following record types can a user typically gain implicit access to when they have access to an Account? Select all that apply.
- AContactsCorrect answer
- BCasesCorrect answer
- COpportunitiesCorrect answer
- DPrice Books
Why this is the answer
Account access can implicitly expose associated Contacts, Cases, and Opportunities, helping users see the full business relationship.
- Question 33Interactive
Consider the Apex class declaration in the code block. What access behavior does the sharing keyword enforce?
- AIt enforces record-level sharing for the query.Correct answer
- BIt enforces Field-Level Security on the selected fields.
- CIt bypasses all record sharing and permissions.
- DIt prevents the query from returning child records.
Why this is the answer
With sharing enforces sharing rules and record visibility, but it does not automatically enforce Field-Level Security.
- Question 34Single Choice
In a Master-Detail relationship, what is the default result when the master record is deleted?
- AAll associated detail records are also deleted.Correct answer
- BDetail records remain but the lookup field is blanked.
- CDeletion is blocked until all detail records are reassigned.
- DDetail records become private to the system administrator.
Why this is the answer
Master-Detail relationships enforce strict lifecycle coupling; deleting the master automatically deletes all detail records.
- Question 35Multiple Select
Which of the following are characteristics of a Master-Detail relationship? Select all that apply.
- AThe detail record inherits the master record's owner and security settings.Correct answer
- BRoll-up Summary fields can be created on the master record.Correct answer
- CDeleting the master record automatically deletes detail records.Correct answer
- DThe detail record has its own independent owner and sharing rules.
Why this is the answer
Master-Detail creates tightly coupled visibility, supports roll-up summaries, and cascades deletes; independent ownership is a Lookup trait.
- Question 36Interactive
The code block applies a security method to a query result. Which type of access does this method help enforce?
- AField-Level SecurityCorrect answer
- BRecord-Level Sharing
- COrganization-Wide Defaults
- DRole Hierarchy access
Why this is the answer
Security.stripInaccessible removes fields the user cannot read, enforcing Field-Level Security in Apex.
- Question 37Single Choice
Which sharing mechanism is designed for high-volume external users and grants record access based on a matching field value?
- ASharing SetsCorrect answer
- BSharing Groups
- CInternal Role Hierarchy
- DTerritory Assignment Rules
Why this is the answer
Sharing Sets are a lightweight, high-performance mechanism that maps external users to records through a common field.
- Question 38Multiple Select
Which of the following are common mistakes when designing sharing for external users? Select all that apply.
- AAssuming the internal Role Hierarchy applies to all Experience Cloud users.Correct answer
- BConfusing Sharing Sets with Sharing Rules.Correct answer
- COverlooking the distinction between Internal and External OWDs.Correct answer
- DUsing Permission Set Groups to grant record access to high-tier external users.
Why this is the answer
External sharing designs often fail when designers rely on role hierarchy, mix up Sharing Sets and Rules, or ignore external OWDs.
- Question 39Interactive
The Apex class in the code block is declared in a specific sharing mode. What is the primary security risk of using this mode?
- AThe query can expose records the user is not authorized to see.Correct answer
- BThe query will execute in a user context.
- CThe query will fail with a governor limit error.
- DThe query automatically enforces Field-Level Security.
Why this is the answer
Without sharing bypasses record-level sharing, creating the risk of unauthorized record access in custom Apex.
- Question 40Single Choice
In Salesforce implicit sharing, what is the primary direction of access flow?
- AFrom parent records to child recordsCorrect answer
- BFrom child records to parent records
- CBetween users in the same role
- DFrom external accounts to internal accounts
Why this is the answer
Implicit sharing flows from the parent record to associated child records, not in reverse.
Frequently asked questions
Everything about the Salesforce Certified Sharing and Visibility Designer question bank and how to use it.