CTA Quick Reference Guide
A fast-track refresher for the Salesforce Certified Technical Architect (CTA) exam. Read this if you have 2 hours before a mock board — it distills the full study vault into the essential patterns, rules, and gotchas you must recall under pressure.
How this works
This is NOT a substitute for deep study. It is a compressed recall aid. Each section assumes you have already studied the domain in depth and need a quick re-activation before walking into the board.
Quick Reference Sections
| # | Section | Domain | One-Line Summary |
|---|---|---|---|
| 1 | System Architecture | D1 | Org strategy, licensing, mobile, reporting, platform limits |
| 2 | Security | D2 | Sharing model, OWD, role hierarchy, field-level security, encryption |
| 3 | Data | D3 | Data modeling, LDV, migration, archival, external objects |
| 4 | Solution Architecture | D4 | Declarative vs code, AppExchange, build vs buy, Well-Architected |
| 5 | Integration | D5 | Patterns, middleware, APIs, error handling, governor limits |
| 6 | Dev Lifecycle | D6 | CI/CD, environments, branching, testing, governance, CoE |
| 7 | Communication | D7 | Presentation flow, Q&A survival, trade-off articulation, STAR-A |
| 8 | Artifacts | All | Diagram creation, the Big 3, supporting artifacts, Lucidchart |
| 9 | Scenario Analysis | All | Requirement extraction, assumption handling, time management |
How to Use This Quick Reference Guide
Suggested Reading Order (2 Hours)
flowchart LR
A["Artifacts\n15 min"] --> B["Scenario Analysis\n10 min"]
B --> C["System Architecture\n10 min"]
C --> D["Security\n15 min"]
D --> E["Data\n15 min"]
E --> F["Integration\n15 min"]
F --> G["Solution Arch\n10 min"]
G --> H["Dev Lifecycle\n10 min"]
H --> I["Communication\n15 min"]
style A fill:#1B96FF,color:#fff
style D fill:#d4504c,color:#fff
style E fill:#d4504c,color:#fff
style F fill:#d4504c,color:#fff
style I fill:#1B96FF,color:#fff
Red = highest failure rate
Security, Data, and Integration are the most commonly failed domains. Spend extra time here if you must prioritize.
If You Only Have 30 Minutes
Focus on these three sections only:
- Artifacts — know the Big 3 diagrams cold (System Landscape, Data Model, Role Hierarchy)
- Security — OWD defaults, sharing rules, role hierarchy patterns
- Communication — the trade-off formula and STAR-A framework for Q&A
Reading Strategy
- Tables first — every section leads with cheat-sheet tables. Read these before anything else.
- Gotchas second — the
:::cautionand:::dangercallouts flag common exam failures. - Mermaid diagrams — visual patterns you can reproduce on the board.
- Skip prose — these pages are intentionally terse. If something is unclear, follow the wikilink to the deep-dive file.
The Review Board at a Glance
| Phase | Duration | Your Goal |
|---|---|---|
| Preparation | 180 min | Read scenario, build all artifacts in Lucidchart |
| Presentation | 45 min (fixed allocation; unused time rolls to Q&A) | Walk judges through your architecture, tied to requirements |
| Q&A | 40 min (+ unused presentation time) | Defend every decision, adapt when challenged, never bluff |
Scoring Weights (Community-Sourced Estimates)
Presentation: 35% | Design Defense: 35% | Q&A: 30%. These weights are community-sourced estimates (TrailblazePrep, coaching sources) — Salesforce does not officially publish scoring weights, and the exact scoring framework is confidential. The directional insight is reliable: presentation and design defense together dominate the evaluation. Invest the majority of your prep time in artifacts and narrative flow. Q&A at 30% means you cannot pass on Q&A alone, but a weak Q&A can sink an otherwise strong presentation.
What You Must Produce in 180 Minutes
| Priority | Artifact | Time Budget |
|---|---|---|
| Tier 1 | System Landscape | 15-20 min |
| Tier 1 | Data Model / ERD | 15-20 min |
| Tier 1 | Role Hierarchy + Sharing | 15-20 min |
| Tier 2 | Integration Architecture | 10-15 min |
| Tier 2 | Identity / SSO Flow | 10-15 min |
| Tier 2 | Actors + Licenses | 10 min |
| Tier 2 | Data Migration Plan | 10 min |
| Tier 2 | Governance / DevOps | 10 min |
| Tier 3 | Risks, Exec Summary, Process Flows | 10-15 min |
| — | Scenario reading + slide assembly | 40-50 min |
Key Formulas to Memorize
The Trade-Off Formula
I chose [APPROACH] because [REASONS]. I considered [ALTERNATIVE] but rejected it because [LIMITATION]. The trade-off is [WHAT YOU GIVE UP], mitigated by [STRATEGY].
The STAR-A Framework (Q&A)
| Step | Action |
|---|---|
| S | Restate the challenge |
| T | Think — pause 3-5 seconds visibly |
| A | Answer the specific question |
| R | Rationale — explain your reasoning |
| A | Adapt — update your design if the challenge reveals a gap |
The 90-Second Diagram Rule
“This diagram shows [what]. The key decision is [decision]. The trade-off is [trade-off]. This connects to [next topic] because [reason].”
Deep-Dive Navigation
For comprehensive coverage beyond this quick reference guide:
- Complete Review Board Guide — full exam structure, costs, prerequisites
- Artifacts & Deliverables Deep Dive — detailed artifact creation guide
- Presentation & Q&A Strategies — complete communication playbook