12 free Salesforce Platform Sharing and Visibility Architect practice questions from the CertStash pack of 100, each with the correct answer and a full explanation. The rule is the same for every exam: ten free on the product page, 12 free here, all 100 in the pack, and each step includes the one before it.
Get all 100 questions (US$39) · Download the first 10 as a PDF
Question 1
Universal 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?
Show answer and explanation
Correct answer: D. Partner Community
Distributors need to work with opportunities, and among the Experience Cloud licenses only Partner Community gives external users access to the Opportunity object, along with leads and campaigns. Partner users also get partner roles within their partner account, so users at a distributor can see the opportunities assigned to that distributor while other distributors stay separated. This makes Partner Community the license that meets the requirement for the distributors' external users.
Why the other options are wrong
- A. Customer Community licenses do not include access to opportunities.
- B. Customer Community Plus licenses do not include access to opportunities.
- C. Sales Cloud is an internal user license and is not meant for external distributor users of a site.
Question 2
What advanced tool can Salesforce enable for large-scale role hierarchy realignments?
Show answer and explanation
Correct answer: B. Granular locking
Changes to the role hierarchy and group membership update the tables that store group membership and sharing data, and without granular locking the system locks broadly while those updates run. Granular locking locks only the portions of the data affected by each operation, so several role hierarchy and group changes can be processed at the same time with far fewer lock contention errors. That makes it the tool for large-scale role hierarchy realignments.
Why the other options are wrong
- A. The external organization-wide default sets external users' baseline access and does nothing for role realignment processing.
- C. Divisions partition data for search and reporting and do not speed up role hierarchy changes.
- D. Skinny tables speed up queries on large objects and do not help with role hierarchy realignments.
Question 3
By default, how many roles are created when the first external user is created on a partner account?
Show answer and explanation
Correct answer: C. 1
When the first external user on a partner account is enabled, Salesforce creates the partner roles for that account according to the number of partner roles configured in the Digital Experiences settings. That setting is one by default, so one role is created for the account. An administrator can raise the setting to as many as three roles, such as Executive, Manager and User, but keeping the number low avoids unused roles and keeps sharing calculations lighter.
Why the other options are wrong
- A. Three roles are created only when the number of partner roles setting has been increased to three.
- B. Two roles are created only when the number of partner roles setting has been changed to two.
- D. Enabling the first partner user always creates at least one role for the account.
Question 4
Universal Containers keeps product brochures in Salesforce as files. Sarah shares a public link to a product brochure with potential customers during a meeting. She wants to ensure they do not have access to the file after the meeting.
How should Sarah accomplish this?
Show answer and explanation
Correct answer: A. Delete the public link.
A public link lets anyone who has the URL view the file without logging in to Salesforce. Deleting the public link immediately removes that access for everyone who received it, while the file itself stays in Salesforce for Sarah and her colleagues to keep using. If the brochure needs to be shared again later, a new link can be created.
Why the other options are wrong
- B. Moving the file does not disable its public link, so customers could still open it.
- C. Deleting the file removes the brochure that the company still needs, which is unnecessary when only the link must go.
- D. Renaming the file does not affect its public link.
Question 5
Universal Containers’ organization wide-defaults model is private for the Account object. A sales representative user has Create/Edit access to opportunity records.
Which level of access will the sales rep have to the related account record?
Show answer and explanation
Correct answer: D. Read-only access
With a private organization-wide default on Account, a user who has access to an opportunity gains implicit Read access to the account the opportunity belongs to. This implicit parent sharing lets the sales rep see the related account in order to work the opportunity, but it only ever provides read-only access. Edit access to the account would have to come from ownership, the role hierarchy or sharing.
Why the other options are wrong
- A. Implicit parent sharing never grants edit access to the account.
- B. Access to the opportunity grants Read access to its parent account, so the rep does not have zero access.
- C. Create is an object permission rather than record access, and implicit sharing grants read access only.
Question 6
Universal Containers (UC) is implementing Sales Cloud. During the last quarter of the financial year, sales agents help each other close deals.
They requested a solution in Salesforce to allow them to specify an assistant agent on the opportunity record.
When the sales agent changes the assistant field, the system should automatically remove access from the previous assistant and grant access to the new assistant.
What is the optimum solution to meet the requirements?
Show answer and explanation
Correct answer: B. Use apex sharing to share and unshare opportunities with the assistant agent.
Declarative sharing cannot share a record with a user named in a lookup field, so the requirement needs code. A trigger on the opportunity can use Apex sharing to insert a share record for the new assistant agent and delete the share for the previous assistant whenever the assistant field changes. Access then stays in step with the field automatically, with no manual work by the sales agents.
Why the other options are wrong
- A. Adding opportunity teams on top of a custom field and Apex adds complexity without benefit, since Apex sharing alone meets the requirement.
- C. Sharing rules share records with groups and roles based on owner or criteria, not with the user in a lookup field.
- D. Share groups give access to records owned by high-volume Experience Cloud users and do not apply to internal sales agents.
Question 7
Universal 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?
Show answer and explanation
Correct answer: D. Create a Sharing Set for the Distributor Profile to grant access to the Delivery object.
A sharing set grants Experience Cloud site users access to records whose account lookup matches the account of the user. With delivery records related to the distributor's account, one sharing set for the distributor profile gives every user at each of the 200 distributors access to the deliveries for that distributor's customers. The same configuration works for every distributor, so no per-distributor rules or groups need to be built or maintained.
Why the other options are wrong
- A. Criteria-based sharing rules would be needed for each distributor, which does not scale to 200 distributors and exceeds the per-object limit on criteria-based rules.
- B. A public group and sharing rule for each of 200 distributors is difficult to build and maintain.
- C. Owning a record gives access to that user and the roles above, not to all users at the distributor.
Question 8
The 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?
Show answer and explanation
Correct answer: C. The field has been configured for encryption.
Fields encrypted with Shield Platform Encryption cannot be used as criteria in criteria-based sharing rules, so they do not appear in the list of available fields when the rule is defined. A Social Security number is a typical field to encrypt for compliance, which explains why it is missing from the Contact sharing rule setup. The rule would need to use a different, unencrypted field as its criterion.
Why the other options are wrong
- A. Validation rules do not affect whether a field can be used in sharing rule criteria.
- B. Field-level security controls who can see field data and is not what removes a field from the sharing rule criteria list.
- D. There is no Compliance fields permission that controls which fields appear in sharing rule criteria.
Question 9
What 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?
Show answer and explanation
Correct answer: B. Create a specific Apex Sharing Reason for the custom object.
Share records created with the Manual row cause are deleted when the owner of a record changes. Apex managed sharing on a custom object should use a custom Apex sharing reason defined on that object, and share records written with that reason are kept when ownership changes. Users who received access through the code therefore keep it after the owner is changed. Apex sharing reasons are available for custom objects.
Why the other options are wrong
- A. The with sharing keyword makes code respect the running user's access and does not preserve share records.
- C. Share records with the Manual row cause are exactly the ones removed when ownership changes.
- D. The runAs method is available only in test methods and does not affect record access in production.
Question 10
Universal Containers (UC) has Affiliates who sell containers in countries where UC does not have a local office. UC has leveraged the Partner Community to manage the sales cycle. One of their affiliates has exponentially grown in the last years and restructured its internal sales team with the following structure:
Sales VP -> Director of Sales -> Sales Manager -> Sales Reps. UC would like to have the ability to open up access to the sales opportunities according to the above structure.
What is the main problem a Salesforce Architect will face to provide a solution?
Show answer and explanation
Correct answer: A. Partner User Roles are limited to three levels.
Each partner account can have at most three partner roles, such as Executive, Manager and User. The affiliate's new structure has four levels, Sales VP, Director of Sales, Sales Manager and Sales Reps, so it cannot be reproduced with partner roles. Sharing opportunities according to that structure through the partner role hierarchy is therefore the main problem the architect has to work around.
Why the other options are wrong
- B. Partner Community does support a role hierarchy within each partner account.
- C. Super user access does work in Partner Community.
- D. The channel manager role is an internal role, and sharing with it is not the issue in this structure.
Question 11
Universal 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?
Show answer and explanation
Correct answer: C. There is an Account ownership data skew problem.
Ownership data skew occurs when a single user owns a very large number of records of one object, generally more than about 10,000. When such owners change roles or records change owner, sharing recalculations across the role hierarchy take a long time and cause locking, which degrades performance. Donation reps owning more than 50,000 donor accounts each is a clear case, and the remedy is to spread ownership or place those owners carefully in the role hierarchy.
Why the other options are wrong
- A. Having access to assigned accounts is normal and does not cause performance problems by itself.
- B. A private organization-wide default is a normal sharing model and is not the cause; the skewed ownership volumes are.
- D. Sharing recalculation is a consequence of the skewed ownership rather than the root reason.
Question 12
The 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 associates 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?
Show answer and explanation
Correct answer: A. Use Account teams to define access to accounts as well as opportunities and cases related to accounts.
Account teams let each member have a team role, such as sales associate, along with separate access levels for the account, its opportunities and its cases. Sales associates can be added with Read access to the account, Read access to related cases and private access to related opportunities, which meets every requirement with one feature. When an associate needs to work an opportunity, the opportunity access for that team member can be raised.
Why the other options are wrong
- B. Opportunity teams and case teams are unnecessary, since account team members already have opportunity and case access settings.
- C. Case sharing rules add configuration that the account team case access setting already provides.
- D. Case teams are unnecessary, since account team members already have a case access setting.
That was 12 of 100.
The full Salesforce Platform Sharing and Visibility Architect pack has all 100 questions, each with the answer, the explanation and why the other options are wrong, plus a questions-only copy for timed runs. US$39, paid once, with free monthly updates and a pass-or-your-money-back guarantee.
Not ready yet? Get the first 48 free as one PDF by email. Get the Half Pack →