New to this track? Our Salesforce Certified Platform Administrator II exam prep is the recommended first step. See our certification path to understand where this certification fits. The Salesforce Certified Platform Sharing and Visibility Architect exam weights Access to Records most heavily (39%), see the full breakdown, study tips, and practice questions below.
Free practice • No sign-up required
Independent study resource
Exam objectives and policies can change. Confirm current details with the certification issuer.
Check current objectives
Use the official exam guide as the source for current objectives and section weights.
Practice for learning
Use sample questions to review concepts and identify topics for further study.
Works on Any Device
Full practice experience on phone, tablet, or desktop
Free, No Sign-Up
Start practicing immediately, no account or email required
Salesforce Certified Platform Sharing and Visibility Architect – Complete 2026 Guide
This exam tests how you design who can see and edit which data in Salesforce. You choose org-wide defaults, roles, sharing rules and permission sets, and you plan for external users and large data volumes. The exam is 60 scored questions in 120 minutes, with a 58% pass mark, weighted towards Access to Records (39%) and Permissions to Standard Objects, Custom Objects, and Fields (27%).
Recommended Prerequisites
We recommend completing this certification first to prepare you better.
| Official exam name and code | Salesforce Certified Platform Sharing and Visibility Architect (Sharing & Visibility) |
|---|---|
| Questions | 60 |
| Time allotted | 120 min |
| Passing score | 58% |
| Exam fee | $400 |
| Retake fee | $200 |
| Prerequisite certifications | Recommended preparation: Salesforce Certified Platform Administrator II |
| Study guide release | Summer '26 |
Salesforce Certified Platform Sharing and Visibility Architect Exam Weightage by Section
1. Permissions to Standard Objects, Custom Objects, and Fields (27%)
27%2. Access to Records (39%)
39%3. Access to Other Data (16%)
16%4. Implications of Security Model Choice (18%)
18%Exam Topics
Last updated:
Who is the Sharing and Visibility Architect exam for?
- Security-Focused Admins: You already set up profiles, roles and sharing rules, and you want to learn how to design a sharing model for a large org from the start.
- Platform Architects: Sharing and Visibility Architect is one of the four exams you need for Application Architect, so it sits on most architect paths.
- Compliance Specialists: You need to prove who can see which records, and explain why, to auditors or security teams.
Exam Fees & Registration
Exam Fee
$400
One-time registration fee
Retake Fee
$200
If you need to retake the exam
Comparing certs? View all Salesforce exam fees in one place →
Certification Validity
Maintenance and renewal requirements vary. Check the issuer’s current credential page for requirements that apply to you.
How to Register
Check current Salesforce Certified Platform Sharing and Visibility Architect credential and registration details with the issuer.
View official credential detailsOfficial references: Use the issuer’s current materials to confirm exam objectives, format, and fees before booking.
Official sources: Exam guide·Salesforce exam pricing·Independent exam-prep resource; details may change.
Exam Tips
- 1Sharing Model and Visibility/Security are 60%. Know OWD, sharing rules, and data access patterns.
- 2Understand when to use private, public read-only, public read/write, and controlled by parent.
- 3Know sharing calculation and performance implications of complex sharing models.
- 4Be ready for "how would you design sharing for X requirement?" questions.
Prerequisites
- •Application Architect
- •System Architect
- •Deep security and sharing experience
Focus Areas
- •Sharing Model
- •Visibility and Security
- •Data Access Patterns
- •Best Practices
Study Strategy
Design sharing models for complex scenarios.
Understand performance implications and best practices.
Practice explaining trade-offs between different sharing approaches.
Exam Format and First-Attempt Readiness
The Salesforce Certified Platform Sharing and Visibility Architect exam has 60 questions in 120 min, passing score 58%. Most Salesforce exams test scenario-based decisions. Focus on when to use each feature, not just terms.
- Study Access to Records and Permissions to Standard Objects, Custom Objects, and Fields first, together they carry 66% of the exam.
- Do timed question sets. Build pacing and confidence.
- Review why wrong answers are wrong. It improves scenario reasoning.
- Book the exam once your mock scores are steady at 75%+.
Is the Sharing and Visibility Architect Exam Hard?
Is the Sharing and Visibility Architect Exam Hard?
It is harder than it looks. Most questions describe a user who can or can't see a record, and you have to work out which layer is causing it: org-wide defaults, the role hierarchy, sharing rules, teams, or something in code.
- 60 multiple-choice questions in 120 minutes.
- 58% to pass, which is about 41 correct answers. Many questions have two answers that look right and differ by one sharing setting.
- External users trip people up. Experience Cloud sharing sets, external org-wide defaults and guest user rules come up often.
- Performance is tested too. Know what makes sharing recalculation slow, such as data skew and very deep role hierarchies.
Pass Rate Guidance
You will do best if you have designed a sharing model for a real org, not just added a sharing rule here and there. Before you book. Aim for 75% or more on practice tests and be able to explain, step by step, why a user can see a record.
Sharing and Visibility Architect Exam Format Explained
Sharing and Visibility Architect Exam Format Explained
You can take the exam online with a proctor or at a test centre. Here is what to expect:
Total Questions
60 scored questions
Time Limit
120 min
Passing Score
58%
Question Type
Multiple-choice & multiple-select
How Many Questions Are Scenario-Based?
Almost every question is a short scenario. A typical one says a group of users needs to see some records but not others, then asks for the simplest setup that does it without opening up too much access.
Best Way to Pass on Your First Attempt
- Start from the most locked-down setting: Set org-wide defaults to the most private level anyone needs, then open access up with roles and rules. The exam favours this approach.
- Separate object, field and record access: Profiles and permission sets control objects and fields. Sharing controls which records. Many wrong answers mix these up.
- Study external sharing on its own: Partner and customer users follow different rules from internal users. Learn sharing sets, share groups and external defaults.
- Know when code is needed: Apex managed sharing is the answer only when declarative sharing can't express the rule.
Sharing and Visibility Architect: Key Concepts
OWD and the Security Baseline
Org-wide defaults (OWD) set the starting level of record access for each object: Private, Public Read Only or Public Read/Write. Everything else can only add access on top of OWD, never take it away. So the rule is simple: set OWD to the most restricted level any user needs, then open access up for the people who need more. For child objects in a master-detail relationship, the setting is Controlled by Parent. Internal and external users can have different defaults, and the external default can't be more open than the internal one.
Record Sharing: Role Hierarchy, Rules, and Manual Sharing
The role hierarchy lets managers see the records their team owns. You can turn this off for custom objects with Grant Access Using Hierarchies. Owner-based sharing rules share records owned by one group with another group. Criteria-based sharing rules share records based on a field value, such as Region equals EMEA. Account, Opportunity and Case teams give access to named people on a single record. Manual sharing lets a record owner share one record with someone, but it is removed if the owner changes. Apex managed sharing covers the rules none of these can handle, and it survives an owner change.
External User Sharing: Communities and Partner Portals
Experience Cloud users are external, and they follow their own rules. Customer Community users don't use roles, so you give them access with sharing sets (for example, all Cases on the user's Account) and share groups. Partner and Customer Community Plus users have roles and can be included in sharing rules. Guest users (people who aren't logged in) have the tightest rules: their OWD is always Private, and you share records to them only with guest user sharing rules. Watch for questions where an internal setting accidentally opens access to external users.
Field and Object Security: Profiles vs Permission Sets
Record sharing decides which rows a user can see. Object and field permissions decide which objects and columns. Every user has one profile, and Salesforce recommends keeping it minimal and adding access with permission sets and permission set groups. A muting permission set inside a group can remove a permission the group would otherwise grant. Field-level security hides a field everywhere, including reports, list views and the API. Restriction rules go the other way from sharing: they filter which records a user can see even if sharing would allow more.
Sharing Performance and Audit
Sharing gets slow when one user owns a huge number of records (ownership skew) or one parent record has thousands of child records (account data skew). Both cause long sharing recalculations and record locking. Fixes include spreading ownership across several users, placing integration users high or outside the role hierarchy, and using Defer Sharing Calculations during large data changes. For audits. Use the Sharing button on a record to see why each user has access, Setup Audit Trail for configuration changes, and Field History Tracking or Shield Field Audit Trail for data changes.
A user’s access to a record is the union of every path shown below. If any one path grants access, the record is visible; this is why architects trace all four sources when diagnosing a visibility issue.
How to Pass the Salesforce Sharing and Visibility Architect Exam
Most questions come down to one thing: which setting gives exactly the access described, and no more. Read the scenario for who needs access, to which records, and whether they are internal or external.
Access Evaluation Order
Work through it in order: object permission first, then OWD, then role hierarchy, sharing rules, teams and manual shares. If the object permission is missing, no sharing setting will help.
Criteria-Based Sharing Rules
Use these when access depends on a field value, not on who owns the record. They can't use formula fields, and they re-run when the field changes.
External Sharing Model
Customer Community users: sharing sets and share groups. Partner and Customer Community Plus users: roles and sharing rules. Guests: guest user sharing rules only.
Performance Considerations
Watch for one owner with more than about 10,000 records, or one Account with more than about 10,000 child records. Both are signs of data skew.
Apex Managed Sharing
Pick Apex sharing only when the rule is too complex for configuration, such as access based on a related record in another object. Use a custom sharing reason so the shares survive owner changes.
Is the Salesforce Certified Platform Sharing and Visibility Architect Exam Hard?
DifficultyChallenging; plan about 8-16 weeks of focused prep.
Book When ReadyScore 75%+ on three timed mocks before scheduling.
Use Practice, Not DumpsOriginal practice questions build skill without risking your credential.
Exam format: 60 questions, 120 min, 58% passing score.
Salesforce Certified Platform Sharing and Visibility Architect Practice Questions (With Explanations)
Test your knowledge with these 15 sample questions.
Question 1: Sales reps should only see Opportunities they own. Their managers should see their team's Opportunities. What is the right starting setup?
Key takeaway: Private OWD hides other reps' records.
Show correct answer and explanation
Correct answer: C. OWD Private with the role hierarchy granting manager access
Private OWD hides other reps' records. The role hierarchy then lets each manager see what their team owns, with no extra rules.
- Manual sharing on every record is slow, error-prone and is removed when the owner changes.
- Public Read Only lets every rep see every Opportunity, which breaks the first requirement.
- Field-level security hides fields, not records. Every rep could still open every Opportunity.
Question 2: A user can see an Account in a list view but gets an error when opening a custom object record related to it. Sharing looks correct. What should the architect check first?
Key takeaway: If a user has no Read permission on an object, no sharing setting can give them access.
Show correct answer and explanation
Correct answer: D. The user's object permissions on the custom object
If a user has no Read permission on an object, no sharing setting can give them access. Object permission is always checked first.
- Account sharing is already working, since the user can see the Account.
- The role affects record access, but the error here points to the object itself.
- Login IP ranges would block the whole login, not one object.
Question 3: All Cases with Region set to EMEA must be visible to the EMEA Support public group, no matter who owns them. What should be used?
Key takeaway: The access depends on a field value, not on the owner.
Show correct answer and explanation
Correct answer: C. A criteria-based sharing rule on Case
The access depends on a field value, not on the owner. That is exactly what a criteria-based sharing rule does.
- Public Read Only would open every Case to everyone, not just EMEA Support.
- Adding a team to every Case by hand doesn't scale and is easy to miss.
- Owner-based rules share by who owns the record, and the owners here vary.
Question 4: Customer Community users should see all Cases related to their own Account. Customer Community users don't have roles. What should the architect use?
Key takeaway: Sharing sets are built for this.
Show correct answer and explanation
Correct answer: A. A sharing set based on the user's Account
Sharing sets are built for this. They give Customer Community users access to records that match their Account or Contact.
- View All would show every Case in the org, including other customers' Cases.
- Customer Community users without roles can't be added to most sharing rules.
- These users have no roles, so the role hierarchy doesn't apply.
Question 5: An integration user owns 2 million Account records. Updates to the role hierarchy now take hours to process. What is the most likely cause?
Key takeaway: When one user owns a huge number of records, every change to their role or groups forces Salesforce to recalculate sharing on all of those records.
Show correct answer and explanation
Correct answer: B. Ownership data skew on the integration user
When one user owns a huge number of records, every change to their role or groups forces Salesforce to recalculate sharing on all of those records.
- The number of profiles doesn't affect sharing recalculation.
- Permission set groups control object and field access, not record sharing.
- Field-level security isn't part of record sharing calculations.
Question 6: Project records must be shared with every user listed in a related Project Member object. The list changes often. What should the architect recommend?
Key takeaway: The access depends on records in another object, which sharing rules can't express.
Show correct answer and explanation
Correct answer: C. Apex managed sharing with a custom sharing reason
The access depends on records in another object, which sharing rules can't express. Apex managed sharing can, and a custom reason keeps the shares when the owner changes.
- Owner-based rules can't read a list of members from another object.
- Public Read/Write gives everyone access, not just project members.
- Manual sharing depends on someone remembering to do it, and it is removed on owner change.
Question 7: A manager in the role hierarchy should NOT automatically see records of a custom object owned by their team. What setting should be changed?
Key takeaway: Grant Access Using Hierarchies can be turned off for custom objects.
Show correct answer and explanation
Correct answer: D. Uncheck Grant Access Using Hierarchies on that custom object
Grant Access Using Hierarchies can be turned off for custom objects. Managers then get no automatic access through the role hierarchy for that object.
- Removing Read permission stops the manager seeing any of these records, including their own.
- Removing the role affects every object, not just this one.
- Restriction rules could work, but turning off hierarchy access is simpler and is the intended setting.
Question 8: Which statement about org-wide defaults is correct?
Key takeaway: External users can never get a broader default than internal users.
Show correct answer and explanation
Correct answer: B. External OWD can't be more open than internal OWD
External users can never get a broader default than internal users. You can set external defaults to be the same or more private.
- Sharing rules only add access. They never take it away.
- Permission sets grant object and field access. Only View All or Modify All bypass sharing, and they apply to the whole object.
- It is the other way round: external defaults must be equal to or stricter than internal ones.
Question 9: Partner users need to see Opportunities owned by other users at their own partner company, but not at other partner companies. What is the best approach?
Key takeaway: Partner users get roles under their partner account.
Show correct answer and explanation
Correct answer: B. Share using the partner account's roles in a sharing rule
Partner users get roles under their partner account. A sharing rule can share records owned by a partner account's roles with the other users in that same account.
- Public Read Only would show all Opportunities to all partners.
- Sharing sets are for Customer Community users, not partner users.
- View All would show every Opportunity in the org.
Question 10: Because of an old sharing rule, reps can see every record of a custom Invoice object. The business now wants reps to see only Invoices for their own country, without redesigning the sharing model. What feature fits?
Key takeaway: Restriction rules filter the records a user can see, even when sharing would allow more.
Show correct answer and explanation
Correct answer: B. A restriction rule
Restriction rules filter the records a user can see, even when sharing would allow more. They are the only tool here that removes record visibility.
- Muting permission sets remove object or field permissions, not record visibility.
- Sharing rules only add access, so they can't narrow what a rep already sees.
- Field-level security hides fields, not records.
Question 11: Anonymous visitors to a public Experience Cloud site need to read published Knowledge-style records from a custom object. How is access given?
Key takeaway: Guest users always have Private OWD.
Show correct answer and explanation
Correct answer: A. Create a guest user sharing rule
Guest users always have Private OWD. The only way to share records with them is a guest user sharing rule.
- Guest users don't have roles.
- Guest users are locked to Private and can't use more open defaults.
- Guest users can't be added to regular public groups for sharing.
Question 12: A rep shares an Opportunity manually with a colleague. Later the Opportunity is reassigned to a new owner. What happens to the manual share?
Key takeaway: Manual shares are deleted when the record owner changes.
Show correct answer and explanation
Correct answer: D. It is removed
Manual shares are deleted when the record owner changes. Apex managed sharing with a custom reason is the way to keep shares through owner changes.
- Manual shares are not carried over to a new owner.
- The colleague's role doesn't matter. The share is removed either way.
- Manual shares never turn into sharing rules.
Question 13: A company is about to load 5 million records and change several sharing rules. They want to avoid long sharing recalculations during the load. What should they use?
Key takeaway: Defer Sharing Calculations pauses recalculation while you make changes, then runs it once at the end.
Show correct answer and explanation
Correct answer: C. Defer Sharing Calculations
Defer Sharing Calculations pauses recalculation while you make changes, then runs it once at the end.
- You can't turn off the role hierarchy for standard objects, and it would change access for everyone.
- Opening OWD would expose data to everyone, even for a short time.
- Deleting and recreating rules causes two big recalculations instead of one.
Question 14: A support agent should be able to edit the Status field on Cases but never see the Customer SSN field on Contact. Which tool controls the SSN requirement?
Key takeaway: Field-level security controls whether a user can see or edit a field.
Show correct answer and explanation
Correct answer: A. Field-level security
Field-level security controls whether a user can see or edit a field. It hides the field in pages, reports, list views and the API.
- OWD sets record access, not field visibility.
- Sharing rules control records, not fields.
- The role hierarchy controls record access, not fields.
Question 15: Auditors ask why a specific user can see a specific Account. What is the fastest way to find out?
Key takeaway: The Sharing Hierarchy button on a record lists the users who can access it and the reason for each, such as a role, a sharing rule or a team.
Show correct answer and explanation
Correct answer: A. Use the Sharing Hierarchy button on the Account record
The Sharing Hierarchy button on a record lists the users who can access it and the reason for each, such as a role, a sharing rule or a team.
- A profile report shows object permissions, not why one record is visible.
- Reading every rule by hand is slow and can miss teams or manual shares.
- Login history shows when someone logged in, not why they have access.
Get the Full Question Bank
Most candidates book the exam after scoring 75%+ on full mocks.
If you’re planning to test this quarter, aim to complete full mocks at least 10–14 days before your exam date.
Contact us for more information on our full 60-question mock exams and a personalized study plan. Use the contact form.
Request Mock Exams & Study PlanSalesforce Certified Platform Sharing and Visibility Architect Exam FAQs
- What is covered on the Salesforce Certified Platform Sharing and Visibility Architect exam?
- The Salesforce Certified Platform Sharing and Visibility Architect exam (formerly Salesforce Certified Sharing and Visibility Architect) covers section-wise weightage as shown above. Use the exam topics and practice questions on this page to align your study with the official outline.
- What is Sharing and Visibility Architect?
- Sharing and Visibility Architect designs secure, scalable sharing models, understands data access patterns, and ensures proper visibility and security in Salesforce orgs.
- Do I need Application Architect before Sharing and Visibility Architect?
- Yes, Application Architect is typically required. Sharing and Visibility Architect requires deep understanding of Salesforce security and sharing models.
- Are there free practice questions for the Salesforce Certified Platform Sharing and Visibility Architect exam?
- Yes. This page includes free sample practice questions with explanations. Use them alongside the current official documentation.
- How do I prepare for the Salesforce Certified Platform Sharing and Visibility Architect certification?
- Use the exam tips, prerequisites, and study strategy on this Salesforce Certified Platform Sharing and Visibility Architect study guide (formerly Salesforce Certified Sharing and Visibility Architect). Focus first on the highest-weighted sections, then take the sample practice questions. Schedule the exam when you consistently score well on practice tests.
Next Architect Certifications
After Sharing and Visibility Architect, most people work toward Application Architect and then CTA:
Honest Cert Breakdown
Difficulty: Hard
4/5One of the four CTA domain exams. OWD, role hierarchy, sharing rules, permission sets, field-level security, all tested at enterprise scale and edge cases.
Salary Range
$122,000–$162,000 / year
US average for certified professionals • Updated Summer '26 • Source: Salesforce Talent Ecosystem
Is it worth it?
Required on the CTA path. Also highly applicable for architects troubleshooting complex sharing models in large multi-org environments.
Weightings by Section
What Each Domain Covers
Sharing Model Design
Designing the organisation-wide default (OWD) sharing model: Public Read/Write, Public Read Only, Private, Controlled by Parent. Role hierarchy and its implicit sharing. Sharing rules (criteria-based and ownership-based). Manual sharing. Account Teams, Opportunity Teams, and Case Teams for collaborative access.
Programmatic Sharing
Apex Managed Sharing: creating Share objects, assigning access levels (Read, Edit, All), Apex sharing reasons. When declarative sharing is insufficient and programmatic sharing is required. Sharing object naming convention (ObjectName + __Share). Maintaining Apex shares across ownership changes.
Performance & Scalability
Sharing recalculation: when it triggers, impact on system performance, deferral strategy. Ownership skew and its impact on sharing rule calculations. Large sharing groups and their performance implications. Monitoring sharing jobs in Setup. High-volume portal users (HVPU) and their sharing model restrictions.
Territory Management
Enterprise Territory Management: territory hierarchy, territory types, assignment rules. Differences from role hierarchy: territory assignment is non-hierarchical, supports multiple assignments. Account and opportunity access via territories. Territory model states (planning, active, archived). When to use territories vs roles.
Compliance & Field Access
Field-level security (FLS) vs record-level security, understanding that FLS controls field visibility independently of record access. Object permissions: CRUD controls. Profile vs permission set hierarchy for access control. Restriction rules and scoping rules (newer feature to restrict/grant record visibility without sharing recalculation).
10-Week Study Plan
Working Through Scenario Questions
- 1.OWD is the floor: Sharing can only open access above OWD; it can never restrict below it. If a scenario requires restricting access below what OWD would grant, use restriction rules or change the OWD setting itself.
- 2.Apex sharing for complex rules: If a sharing rule scenario cannot be expressed with criteria-based or ownership-based rules (e.g., "share with user who owns the related object two levels up"), the answer is Apex Managed Sharing.
- 3.HVPU vs standard users: High-Volume Portal users do not have a role and cannot be in sharing groups. They use account-based or contact-based access instead. If a question involves high-volume external users, standard sharing rules do not apply.
- 4.Ownership skew degrades performance: When one user owns millions of records and their OWD is Private, sharing recalculation when that user’s role changes is extremely slow. The fix is to use a separate integration user profile designed for bulk ownership, or re-architect using Public Read OWD with restriction rules.
Practice-Test Benchmark
Aim for 75%+ on practice exams before scheduling. The sharing model section (35%) is scenario-heavy; you will be given complex multi-user access requirements and must select the most appropriate sharing architecture. Drawing out the access model before selecting an answer helps significantly.
10 Concepts Worth Reviewing
- All OWD settings and their implications for each standard object
- Role hierarchy: implicit access, hierarchical vs non-hierarchical objects
- Sharing rules: criteria-based vs ownership-based, limitations (no OR conditions)
- Manual sharing: who can create, when it is removed, relationship to OWD
- Apex Managed Sharing: Share objects, access levels, custom sharing reasons
- Sharing recalculation: what triggers it, deferral, performance impact
- Ownership skew: definition, symptoms, and mitigation strategies
- Territory Management vs role hierarchy: when to use each
- Restriction rules: use cases, limitations, comparison to Private OWD
- High-Volume Portal Users: sharing model restrictions, account-based access
Questions Candidates Ask
- What is the Salesforce Sharing & Visibility Architect certification?
- The Sharing & Visibility Architect certification validates expertise in designing record-level security models for complex Salesforce orgs. It covers OWD settings, role hierarchy, sharing rules, manual sharing, Apex Managed Sharing, territory management, and performance implications of each design choice. The exam has 60 questions, ~110-minute time limit, 58% passing score, and a $400 fee.
- What is the difference between OWD, role hierarchy, and sharing rules?
- OWD (Organisation-Wide Default) sets the baseline record access for all users. Private OWD = users can only see their own records by default. Role hierarchy grants access upward, managers see records of their subordinates. Sharing rules extend access to specific groups of users beyond what OWD and role hierarchy provide. All three work together: OWD is the floor, role hierarchy and sharing rules open access above it.
- What is Apex Managed Sharing and when is it needed?
- Apex Managed Sharing allows Apex code to programmatically insert records into the Share object (e.g., AccountShare, OpportunityShare) to grant specific users or groups access to records. It is needed when declarative sharing rules cannot express the required logic, for example, when access depends on complex business rules, related record data, or dynamic conditions that change frequently. Apex shares are maintained separately from declarative shares and survive sharing recalculation if you use a custom Apex sharing reason.
- What is the difference between territory management and role hierarchy?
- Role hierarchy is a strict hierarchical structure, each user has one role, and managers automatically see subordinates' records. Territory management is a flexible matrix structure, a user can be assigned to multiple territories, and territories can overlap. Territory management is better for complex sales territory models where geographic or industry segmentation doesn't fit neatly into a hierarchy. Both can coexist in the same org.
- What are restriction rules and scoping rules?
- Restriction rules (Winter 2021+) allow you to restrict which records a user can see, even if they would otherwise have access via OWD or sharing. Use case: limit a user to only see their own region's records despite a Public Read/Write OWD. Scoping rules control which records appear in list views, related lists, and lookups for a user. Both avoid performance-costly sharing recalculations by filtering at query time rather than maintaining share records.
Plan Your Next Certification
After this certification, consider: Application Architect, System Architect, or Technical Architect (CTA).
Topic Difficulty Heatmap
Which topics are a gimme vs which ones trap confident candidates. Use this to prioritise your final-week revision. These are our own topic groupings for study planning, not the official exam sections, those and their weightings are in the credential's exam guide.
| Topic | Difficulty | Study Tip |
|---|---|---|
| Sharing Model | Hard | OWD, role hierarchy, sharing rules, and manual share, order and interaction are key. |
| Visibility and Security | Trap ⚠ | Profiles vs permission sets vs OWD, candidates often choose the wrong layer. |
| Data Access Patterns | Hard | LDV and sharing recalculation. Know when sharing is recalculated. |
| Best Practices | Moderate | Security and performance best practices, standard recommendations. |
Difficulty based on analysis of common candidate errors across each exam section.
Try It Yourself
Test yourself with free Sharing & Visibility Architect practice questions.
Start Free Practice QuestionsQuick Answer: What Sharing & Visibility Architect Tests
- Sharing model design: OWD strategy, role hierarchy depth trade-offs, implicit vs. explicit sharing, and when each sharing mechanism is the right architectural choice.
- Performance implications: How sharing rule complexity affects query performance at large data volumes, and when to favour restrictive OWDs over permissive ones to maintain performance.
- Special sharing scenarios: Community/portal user access, territory management sharing, Apex managed sharing, and sharing for external users.
Highest-Weight Exam Sections
Designing the Sharing Model is 35% alone; this is your single most important study topic.
Scenario Strategy: How to Approach Sharing Questions
Sharing & Visibility questions describe an organisation’s access requirements and ask which configuration satisfies them. Always start from the most restrictive baseline and open access incrementally.
- The OWD baseline principle: set OWDs to the most restrictive setting required by any subset of users. Never set OWD to Public Read/Write if any user group needs restricted access.
- Sharing rule order: role hierarchy grants access UP the hierarchy (not sideways). Criteria-based sharing rules open access across the hierarchy. Manual sharing is for ad-hoc exceptions; it is not an architectural solution.
- For performance questions: sharing recalculation at large data volumes is expensive. Overly complex sharing rules (many criteria-based rules + large record counts) cause performance degradation. Simpler role-hierarchy-based sharing is always more performant.
- For Apex managed sharing: only use it when standard sharing mechanisms cannot meet the requirement. It requires a sharing reason and bypasses normal recalculation. Know the implications.
Mock-Test Benchmark Before Booking
75%+ on 3 timed full mocks before booking
Sharing & Visibility Architect has one of the highest retry rates of any Salesforce exam. The performance implications and Apex managed sharing scenarios are not learnable from documentation alone, design real sharing models in a sandbox before sitting the exam.
3 Concepts That Fail Most Sharing & Visibility Architect Candidates
These are not the hardest topics; they are the ones where candidates are most confidently wrong. Learn the distinction early.
1. OWD + Role Hierarchy + Sharing Rules: The Correct Evaluation Order
Salesforce evaluates record access in this order: OWD (baseline) → Role Hierarchy (opens access upward) → Sharing Rules (open access horizontally) → Manual Sharing (record-by-record grants). Candidates apply sharing rules expecting them to restrict access below OWD, sharing rules can only OPEN access, never restrict below OWD. The only way to restrict below OWD is to change OWD itself.
2. With Sharing vs Without Sharing vs Inherited Sharing in Apex
Apex classes declared "with sharing" enforce the running user’s sharing rules. "Without sharing" bypasses sharing (runs as admin). "Inherited sharing" passes the sharing context from the calling class. Candidates use "without sharing" for all utility classes to avoid access issues, the exam expects "with sharing" for user-facing operations and "without sharing" only for system-level operations with a documented security justification.
3. Territory Management vs Role Hierarchy: Two Separate Sharing Mechanisms
The Role Hierarchy extends record access to managers above the record owner. Territory Management grants access to accounts and their related records based on geographic or segment-based territory assignment, independent of the Role Hierarchy. A user can gain access to an Account through Territory assignment even if they are not above the owner in the Role Hierarchy. Candidates assume territory access is role-based.
Frequently Asked Questions
- What is the Salesforce Sharing & Visibility Architect exam format?
- The Salesforce Sharing & Visibility Architect exam has 60 multiple-choice questions, a 105-minute time limit, a 58% passing score, and a $200 fee. It is a component exam for the Application Architect role-based credential and tests the full Salesforce sharing and security model.
- What are the highest-weight Sharing & Visibility Architect exam sections?
- Designing the Sharing Model (35%) is the single highest-weight section, making it by far the most important study area. Record-Level Access (20%) and Field and Object Security (18%) round out the top three, accounting for 73% of the exam together.
- What prerequisites do I need for Sharing & Visibility Architect?
- There are no hard prerequisites, but Salesforce recommends Salesforce Administrator (ADM-201) before Sharing & Visibility Architect since the exam builds directly on the sharing model topics in ADM-201 but at a deeper, architectural level. Real experience designing OWDs and sharing rules for complex multi-team organisations is essential.
- What is the hardest part of the Sharing & Visibility Architect exam?
- The performance implications of sharing configurations are the hardest area; candidates must understand when complex sharing rules cause query performance degradation at large data volumes, and when to recommend implicit sharing vs. explicit sharing vs. manual sharing. These architectural trade-offs require real project experience.
- What concepts do most Sharing & Visibility Architect candidates get wrong?
- The most commonly misunderstood topics for the Sharing & Visibility Architect exam are: (1) OWD + Role Hierarchy + Sharing Rules: The Correct Evaluation Order; (2) With Sharing vs Without Sharing vs Inherited Sharing in Apex; (3) Territory Management vs Role Hierarchy: Two Separate Sharing Mechanisms. Candidates are most confidently wrong on these. Learn the distinctions early to avoid losing marks on questions you expect to get right.
- Why do most Sharing Visibility Architect candidates fail questions about OWD + Role Hierarchy + Sharing Rules?
- Salesforce evaluates record access in this order: OWD (baseline) → Role Hierarchy (opens access upward) → Sharing Rules (open access horizontally) → Manual Sharing (record-by-record grants). Candidates apply sharing rules expecting them to restrict access below OWD, sharing rules can only OPEN access, never restrict below OWD. The only way to restrict below OWD is to change OWD itself.
- Why do most Sharing Visibility Architect candidates fail questions about With Sharing vs Without Sharing vs Inherited Sharing...?
- Apex classes declared "with sharing" enforce the running user's sharing rules. "Without sharing" bypasses sharing (runs as admin). "Inherited sharing" passes the sharing context from the calling class. Candidates use "without sharing" for all utility classes to avoid access issues, the exam expects "with sharing" for user-facing operations and "without sharing" only for system-level operations...
- Why do most Sharing Visibility Architect candidates fail questions about Territory Management vs Role Hierarchy?
- The Role Hierarchy extends record access to managers above the record owner. Territory Management grants access to accounts and their related records based on geographic or segment-based territory assignment, independent of the Role Hierarchy. A user can gain access to an Account through Territory assignment even if they are not above the owner in the Role Hierarchy. Candidates assume territor...
Related Exam Tips
Start Sharing & Visibility Prep
After this exam, consider Application Architect or System Architect next.
Share or cite this study guide
Free to link from a forum post, study repo or article. Copy the Markdown and paste it anywhere.