System Architecture

Key Takeaways

System Architecture is the broadest CTA domain, spanning org strategy, licensing, mobile, reporting, document management, and platform capabilities. Master the on-platform vs off-platform decision framework, understand governor limits and multi-tenant constraints, and be ready to justify single-org vs multi-org trade-offs at the review board.

This domain covers the ability to design solutions using the appropriate mix of on-platform and off-platform systems, considering platform capabilities, constraints, and limits. It is the broadest CTA domain with 6 objectives spanning org strategy, licensing, mobile, reporting, document management, and platform capabilities.

Objectives & Study Pages

Each objective maps to one or more dedicated study pages:

1. Single-Org vs Multi-Org Environments

• Org Strategy — Single vs multi-org decision matrix, Hyperforce, data residency, M&A consolidation, cross-org data sharing, Government Cloud, edition differences

2. License Types

• Licensing — Full CRM, Platform, Experience Cloud, Identity, Chatter, Einstein, Data Cloud, MuleSoft, Tableau, Shield, Industry Clouds, feature vs permission set licenses, cost optimization

3. Mobile Solutions

• Mobile Strategy — Salesforce Mobile App, Mobile Publisher, PWA, Mobile SDK, offline capabilities (Briefcase, SmartStore), MDM, Field Service mobile, push notifications
• Field Service Architecture — Work Orders, Service Appointments, scheduling optimization (ESO), territory design, Dispatcher Console, mobile offline (Briefcase), preventive maintenance, Agentforce for Field Service

4. Reporting & Analytics

• Reporting & Analytics — Standard Reports vs CRM Analytics vs Tableau vs Data Cloud, historical trending, Analytic Snapshots, Einstein Discovery, architecture patterns

5. Document Management

• Document Management — Salesforce Files vs external DMS, Files Connect, Knowledge management, document generation, e-signature, storage optimization

6. On/Off-Platform Systems

• Platform Capabilities & Constraints — Governor limits, multi-tenant architecture, on vs off platform decision framework, async Apex patterns, Platform Events, CDC, Big Objects, Custom Metadata

Cross-Cutting Guides

• Decision Guides — Mermaid decision flowcharts for every major system architecture decision
• Best Practices & Anti-Patterns — Platform-first thinking, Well-Architected Framework alignment, common anti-patterns
• Trade-Offs — On/off platform, single/multi-org, build vs buy, license optimization, mobile, reporting, document management

Practice

• Domain Grilling: D1 System Architecture Q&A

Related Topics

System architecture intersects with every other domain. These are the tightest connections:

• Security — Security requirements and identity constraints shape every system design decision
• Data Architecture — Data volume, modeling, and LDV strategies drive scalability and org design
• Integration — Integration patterns define system boundaries and API surface area
• Development Lifecycle — Governance, CI/CD, and environment strategy depend on org architecture
• Communication — Presenting and defending system architecture decisions at the review board

Frequently Asked Questions

What topics does the CTA exam cover in System Architecture?

System Architecture spans org strategy (single vs multi-org), licensing models, mobile solutions (Salesforce Mobile, Mobile Publisher, PWA, offline), reporting and analytics (standard reports, CRM Analytics, Tableau, Data Cloud), document management, and platform capabilities including governor limits and multi-tenant architecture constraints.

How is System Architecture scored in the CTA review board?

Judges evaluate whether your solution appropriately leverages platform capabilities while respecting governor limits and multi-tenant constraints. They look for justified org strategy decisions, correct license type selection, and a clear on-platform vs off-platform decision framework with supporting trade-off analysis.

What are the most common mistakes in System Architecture during the CTA exam?

Candidates frequently fail by defaulting to custom code when declarative or platform-native solutions exist, ignoring governor limits in their design, choosing multi-org without sufficient justification, overlooking mobile and offline requirements buried in the scenario, and underestimating reporting volume against platform limits.

How should I approach single-org vs multi-org decisions at the CTA review board?

Default to single-org unless the scenario presents compelling reasons for separation such as regulatory data residency requirements, M&A with incompatible data models, or fundamentally different business units with conflicting security models. Always articulate the trade-offs: multi-org increases integration complexity, cross-org reporting difficulty, and total cost of ownership.

What platform limits should I memorize for the CTA exam?

Focus on the limits that affect architectural decisions: API call limits per 24 hours, Bulk API batch sizes, data storage allocation per license type, custom object limits, SOQL query row limits, Apex CPU time limits, Platform Event delivery guarantees, and file storage caps. Know thresholds that trigger an off-platform decision rather than memorizing exact numbers.