Skip to content
SF CTA Study Hub

System Architecture

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

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