Salesforce Plat-Arch-205 Real Exam Questions [October 2026 Update]

Ownership skew is the Plat-Arch-205 performance topic that experienced Salesforce administrators most consistently underestimate – not because they are unfamiliar with the term, but because they have never seen it produce the consequences the exam expects them to know. In standard-volume orgs, sharing recalculation jobs that run after role hierarchy changes complete without incident. In orgs where a single user – or a small number of users at the top of the role hierarchy – owns millions of records, sharing recalculation becomes an org-threatening event.

When the role hierarchy changes, Salesforce must recalculate access for every record owned by affected users and re-evaluate implicit access for all users above them in the hierarchy. If one user owns 3 million Account records, a single role change triggers a sharing recalculation affecting 3 million records and all parent-role access chains simultaneously. The result: recalculation jobs that run for hours or days, inconsistent record visibility during recalculation, and scheduled recalculation queue backlog that blocks all subsequent sharing changes.

The exam tests the architectural mitigations that prevent this: moving high-volume record ownership to queues (queues are outside the role hierarchy, so implicit parent-role access does not propagate from queue-owned records), replacing owner-based sharing rules with criteria-based sharing rules (criteria-based rules evaluate field values rather than record ownership, eliminating ownership concentration as a performance factor), and designing role hierarchies with this constraint explicitly in mind from the start.

Exam Snapshot

The Four-Layer Sharing Model

Every Plat-Arch-205 scenario question is ultimately a question about which layer controls access in the described situation and what the correct configuration of that layer is.

Layer 1 – Object and Field Permissions: Controlled by Profile and Permission Sets. Determines whether a user can access an object (CRUD) and which fields are visible or editable. A user without Read permission on an object cannot see any records of that type regardless of any sharing configuration below this layer.

Layer 2 – OWD: Sets baseline record access for every user on each object. Private (own records only), Public Read Only (all users can read, only owners can edit), Public Read/Write (all users can read and edit), Controlled by Parent (child access follows parent). The External OWD is a separate setting for external (community) users on the same object.

Layer 3 – Role Hierarchy, Sharing Rules, Manual Sharing, Teams: Opens access beyond what the OWD establishes. Role hierarchy provides automatic parent-role access. Sharing rules grant access to groups based on ownership or field criteria. Manual sharing grants one-time access to specific records. Teams grant named users access to specific records.

Layer 4 – Programmatic Sharing: Apex managed sharing inserts __Share records to grant access when declarative tools cannot express the required logic.

Domain 1: Permissions to Objects, Custom Objects, and Fields (27%+)

Profile vs. Permission Set architecture: Modern Salesforce architecture uses minimum-access profiles granting almost nothing by default, with all meaningful access granted through Permission Sets targeted at specific user populations. Permission Set Groups bundle related Permission Sets for efficient assignment. The exam tests that expanding a Profile affects all users on that profile simultaneously – so any targeted expansion must use Permission Sets, which affect only assigned users.

Field-level security (FLS) is independent of record-level sharing. A user who accesses a record through sharing rules may still be unable to see specific fields if FLS restricts them. The exam tests FLS as a separate configuration layer from record sharing – both must be correct for full access.

External user license types: Customer Community users do not receive access through the role hierarchy – they see only records they own or that are explicitly shared. Customer Community Plus users participate in a limited role hierarchy. Partner Community users have a more complete sharing model. The exam tests these distinctions in community implementation scenarios.

Domain 2: Access to Records

OWD design principle: Always start at the most restrictive setting (Private) and open access upward through sharing rules and role hierarchy. Starting at Public and attempting to restrict is architecturally incorrect – Salesforce’s sharing model grants access, it does not deny it at the record level once broad access is established.

Role hierarchy design at scale: Deep hierarchies with 150+ roles create sharing recalculation complexity. Flatter hierarchies with territory management or criteria-based sharing rules handling nuanced access requirements are architecturally preferred for large organisations.

Owner-based vs. criteria-based sharing rules:

Owner-based: Grant access based on record ownership – who owns the record. “Share all Accounts owned by the Pacific Region role with the National Accounts team.”

Criteria-based: Grant access based on field values – what the record contains. “Share all Accounts where Industry equals Financial Services with the FS Specialist team.”

The exam presents requirements and tests which rule type is correct. Ownership-relationship requirements → owner-based. Record-content requirements → criteria-based.

Manual sharing grants access to specific records for specific users but is removed when the record owner changes. Appropriate for ad hoc or temporary access; inappropriate for systematic access that should be handled by sharing rules.

Domain 3: Access to Other Data

External objects (Salesforce Connect / OData) support OWD and criteria-based sharing rules but do not support role hierarchy-based access. Users above an external object record’s owner in the role hierarchy do not automatically gain access. The exam tests this constraint in scenarios involving sensitive external data.

Territory Management provides an alternative access model for sales organisations where the territory structure does not match the organisational hierarchy. Territory assignment rules automatically assign accounts and related records to territories; users assigned to a territory receive access regardless of record ownership. Appropriate when coverage model and org hierarchy are structurally misaligned, territory assignments change frequently, or overlapping territory coverage is required.

Domain 4: Programmatic Sharing

When declarative tools are insufficient: Complex multi-condition logic (“share this record if Amount exceeds $100,000 AND Account is in Technology AND the requesting user is on the Account’s support team”), dynamic user-specific access that standard sharing rules cannot evaluate, or access patterns that change based on workflow state.

with sharing, without sharing, and inherited sharing:

with sharing enforces the running user’s sharing context – SOQL returns only records the user can access.

without sharing bypasses all sharing – SOQL returns all records regardless of the running user’s access.

inherited sharing adopts the sharing context of the calling class. If called by a with sharing class, it enforces sharing. If called by a without sharing class, it bypasses sharing. The same method produces different data access results depending on who calls it – a security risk when a developer assumes a method always enforces sharing without verifying all possible call paths.

Apex sharing records: Custom objects have an auto-generated __Share object. Required fields for a sharing record: ParentId (the shared record), UserOrGroupId (recipient), AccessLevel (Read or Edit), and RowCause (the sharing reason identifying this as Apex-managed access, enabling targeted removal when conditions change).

5 Study Tips for Salesforce Plat-Arch-205

• Study ownership skew with its specific performance consequence and both architectural mitigations – queue ownership removes high-volume records from role hierarchy calculations, and criteria-based rules eliminate ownership concentration as a performance factor.
• Study inherited sharing as a dynamic context mechanism – the sharing behaviour depends entirely on the calling class, creating security risk when the call path is not fully controlled.
• Study the External OWD as a separate configuration from the internal OWD, controlling baseline access for Customer Community, Customer Community Plus, and Partner Community users differently.
• Study territory management as the correct solution when the organisational hierarchy and sales territory coverage model are structurally misaligned.
• Practice with Cert Empire’s Plat-Arch-205 exam questions built as multi-layer sharing scenarios requiring reasoning through all four access layers to identify which layer is responsible for a described access problem.

Best Study Resources

• Cert Empire Plat-Arch-205 exam questions PDF and practice simulator (September 2026 edition).
• Salesforce Security Implementation Guide (Salesforce Help – help.salesforce.com, search “Security Implementation Guide”).
• Salesforce official Plat-Arch-205 exam guide (Trailhead Academy – trailheadacademy.salesforce.com).
• Trailhead Trailmix: “Architect Journey: Sharing and Visibility.”
• Salesforce Developer documentation: Apex sharing and inherited sharing (developer.salesforce.com).

Why Candidates Choose Cert Empire for Salesforce Plat-Arch-205 Preparation

Free Practice Tests

Test your understanding of OWD design, role hierarchy logic, and Apex sharing keywords with free Plat-Arch-205 sample questions. Identify whether your gaps are in declarative sharing configuration, programmatic sharing patterns, or large data volume performance design.

Regular Updates

Salesforce’s sharing model and Permission Set architecture evolve across releases. Our Plat-Arch-205 question bank is regularly reviewed and updated to stay aligned with the current platform and official exam objectives.

Free Exam Guides

Every purchase includes our free Plat-Arch-205 exam guide covering the four sharing model layers, ownership skew and its mitigations, the Apex sharing keyword distinctions, External OWD for community users, and a structured study plan.

PDF Exam Questions – Study Anywhere, Anytime

Download your Plat-Arch-205 questions immediately after purchase. Study on any device or print the PDF for structured offline sessions. No login required after download.

24/7 Chat Support

Available at any hour for questions about your Plat-Arch-205 materials, your order, or specific Salesforce sharing model concepts – including inherited sharing behaviour and ownership skew performance implications.

3 Months of Unlimited Access

Three full months of unlimited access to the Plat-Arch-205 question bank and simulator. Work through multi-layer sharing scenarios, External OWD questions, and Apex programmatic sharing patterns at your own pace.

Official Vendor Resources – Learn from the Source

Every solution in our Plat-Arch-205 question bank links directly to the relevant Salesforce official resource – the Security Implementation Guide, the Apex sharing documentation, or the Trailhead module – so every answer connects you to the authoritative Salesforce source.

Deep Knowledge – Every Answer, Every Option, Fully Explained

Every Plat-Arch-205 question includes a complete explanation covering not just why the correct sharing configuration, OWD setting, or Apex keyword is right, but precisely why each incorrect option fails – whether it is an OWD set too broadly, an inherited sharing class called by a without sharing context, or a criteria-based rule applied to an ownership-based requirement. Each explanation references the specific Salesforce official documentation behind the answer.

Interactive Practice Simulator – Think Like the Exam

Our simulator presents multi-layer sharing access scenarios exactly as the real Plat-Arch-205 exam does – describing an enterprise security requirement across multiple user types and testing which combination of OWD, role hierarchy, sharing rules, and programmatic sharing correctly satisfies all stated constraints simultaneously.

Backed by a Full Money-Back Guarantee

If our Plat-Arch-205 exam questions do not help you pass, you receive a full refund – no questions asked.

FAQs

What is the Salesforce Plat-Arch-205 certification?

Plat-Arch-205 is the Salesforce Certified Platform Sharing and Visibility Architect exam. It validates architect-level expertise in designing Salesforce data access models using OWD, role hierarchy, sharing rules, manual sharing, programmatic Apex sharing, and large data volume performance design.

What is organization-wide default (OWD) and why does it matter?

OWD sets the baseline record access for all users on a given Salesforce object. Private means users see only records they own or that are explicitly shared. The fundamental design principle is to start Private and open access upward – it is architecturally much harder to restrict access that was initially set too broadly.

What is inherited sharing in Apex?

inherited sharing makes an Apex class adopt the sharing context of whatever class calls it. If called by a with sharing class, it enforces sharing. If called by a without sharing class, it bypasses sharing. The same method can produce different data access results depending on the call path – a confirmed security risk the exam tests at the architectural level.

What is ownership skew and why is it a problem?

Ownership skew occurs when a single user or small group owns millions of records. When the role hierarchy changes, Salesforce must recalculate sharing for every owned record simultaneously. With millions of records concentrated under one owner, recalculation can run for many hours and cause org-level performance degradation.

When should Apex managed sharing be used?

When the required access logic cannot be expressed as any combination of OWD, role hierarchy, sharing rules, or manual sharing – typically complex multi-condition logic or dynamic access that depends on relationships between the requesting user and related record data.

What is the External OWD?

The External OWD is a separate OWD setting that controls baseline access for external (community) users – independent from the internal OWD. An object can have different internal and external OWD settings simultaneously, enabling multi-tenant community architectures where internal and external users coexist on the same org.

What is the difference between owner-based and criteria-based sharing rules?

Owner-based rules grant access based on record ownership – they fire based on who owns the record. Criteria-based rules grant access based on field values – they fire based on what the record contains. Criteria-based rules are preferred in high-volume scenarios because they do not contribute to ownership skew performance problems.

How much does the Plat-Arch-205 exam cost?

The Plat-Arch-205 exam costs USD $400 for the first attempt and typically $200 for a retake. Registration is through Salesforce Trailhead Academy. Pricing may vary by country.

What is the Application Architect aggregate credential?

The Salesforce Application Architect aggregate credential requires passing Plat-Arch-205 (Sharing and Visibility), Data Architect, and two additional architect-level exams. Completing all required exams automatically earns the credential.

Related Certifications Worth Exploring

Plat-Arch-205 is one of the exams required for the Salesforce Application Architect aggregate credential. Candidates working toward the full credential will find the Salesforce Plat-Arch-202 (Development Lifecycle and Deployment Architect) exam questions page covers the System Architect companion credential – the deployment and release management architecture that pairs with the security models Plat-Arch-205 addresses on the path to the full Salesforce Certified Technical Architect credential. For those building data model expertise alongside sharing knowledge, the Salesforce Data Architect exam questions page covers data modeling, data governance, and Master Data Management – the data design complement to Plat-Arch-205’s access design expertise.