Skip to content
SF CTA Study Hub

CTA Preparation Roadmap

A visual, milestone-driven roadmap for preparing for the Salesforce CTA Review Board. This page focuses on the visual journey — for detailed resource lists, see Preparation Guide.

The End-to-End CTA Journey

timeline
    title CTA Journey — Typical 4-6 Year Path
    section Foundation (Years 1-2)
        Platform App Builder : First architect cert
        Platform Developer I : Technical foundation
        Data Architect : Data domain mastery
    section Intermediate (Years 2-3)
        Sharing & Visibility Architect : Security expertise
        Integration Architect : Integration patterns
        Identity & Access Mgmt Architect : Identity flows
    section Advanced (Years 3-4)
        Dev Lifecycle & Deployment Architect : DevOps mastery
        Application Architect (awarded) : Super-credential 1
        System Architect (awarded) : Super-credential 2
    section CTA Prep (Year 4-5)
        CTA-601 Workshop : Official prep begins
        Domain deep study : 6-12 months
        Mock review boards : 8-10 sessions
        CTA-602 Diagnostic : Final readiness check
    section Certification (Year 5-6)
        Step 1 Evaluation : $1,500 gate
        Step 2 Review Board : $4,500 exam
        CTA Certified : Pinnacle credential

Prerequisite Certification Path

flowchart TD
    PD1["Platform Developer I<br/>$200"]
    PAB["Platform App Builder<br/>$200"]
    DA["Data Architect<br/>$400"]
    SVA["Sharing & Visibility Architect<br/>$400"]
    DLD["Dev Lifecycle & Deployment<br/>Architect — $400"]
    IAM["Identity & Access Management<br/>Architect — $400"]
    IA["Integration Architect<br/>$400"]

    PAB --> AA["Application Architect<br/>(auto-awarded)"]
    PD1 --> AA
    DA --> AA
    SVA --> AA

    PD1 --> SysA["System Architect<br/>(auto-awarded)"]
    DLD --> SysA
    IAM --> SysA
    IA --> SysA

    AA --> READY["Ready for CTA<br/>Step 1: Evaluation"]
    SysA --> READY

    style AA fill:#4CAF50,color:#fff
    style SysA fill:#4CAF50,color:#fff
    style READY fill:#FF9800,color:#fff
flowchart LR
    A["1. Platform Developer I"] --> B["2. Platform App Builder"]
    B --> C["3. Data Architect"]
    C --> D["4. Sharing & Visibility"]
    D --> E["5. Integration Architect"]
    E --> F["6. Identity & Access Mgmt"]
    F --> G["7. Dev Lifecycle & Deploy"]
    G --> H["Application Architect\n+ System Architect\nAWARDED"]

    style H fill:#4CAF50,color:#fff

Optimal sequence

This order builds knowledge cumulatively — each cert builds on concepts from the previous one. Data informs Sharing & Visibility, which informs Integration, which informs Identity.

Review Board Preparation Timeline (6-12 Months)

Phase Overview

gantt
    title CTA Review Board Preparation — 6-Month Plan
    dateFormat YYYY-MM-DD
    axisFormat %b

    section Foundation
    Attend CTA-601 Workshop        :milestone, 2026-04-01, 1d
    Gap Assessment (all 7 domains) :gap, 2026-04-01, 14d
    Join Study Groups              :join, 2026-04-01, 7d

    section Deep Domain Study
    System Architecture            :d1, 2026-04-15, 14d
    Security & Identity            :d2, after d1, 14d
    Data Architecture              :d3, after d2, 14d
    Integration                    :d5, after d3, 14d

    section Advanced Practice
    Solution Architecture          :d4, after d5, 7d
    Dev Lifecycle & Governance     :d6, after d4, 7d
    Communication Skills           :d7, after d6, 7d
    Cross-Domain Scenarios         :cross, after d7, 21d

    section Mock Boards
    Mock Sessions 1-4              :mock1, 2026-07-15, 28d
    CTA-602 Readiness Diagnostic   :milestone, 2026-08-01, 1d
    Mock Sessions 5-8              :mock2, 2026-08-15, 21d
    Final Mock 9-10                :mock3, 2026-09-01, 14d
    Rest Week                      :rest, after mock3, 7d

    section Exam
    Step 1 Evaluation              :milestone, 2026-09-22, 1d
    Step 2 Review Board            :milestone, 2026-10-15, 1d

Weekly Study Plan Structure

pie title Weekly Time Allocation (10-15 hours)
    "Domain Study (reading, notes)" : 30
    "Scenario Practice (timed)" : 25
    "Mock Presentations (record + review)" : 20
    "Diagram Practice (Lucidchart)" : 15
    "Community Engagement (study groups)" : 10

The Sprint-Based Study Approach

flowchart TD
    S1["Sprint 1 (Weeks 1-6)<br/>System Architecture + Security<br/>2 mini-mocks per week"] --> B1["Break Week<br/>Recovery + Internalization"]
    B1 --> S2["Sprint 2 (Weeks 8-13)<br/>Data + Integration<br/>3 mini-mocks per week"]
    S2 --> B2["Break Week"]
    B2 --> S3["Sprint 3 (Weeks 15-20)<br/>Solution + DevLifecycle + Comms<br/>Full mock boards begin"]
    S3 --> B3["Break Week"]
    B3 --> S4["Sprint 4 (Weeks 22-27)<br/>Cross-Domain Integration<br/>1-2 full mocks per week"]
    S4 --> CTA601["CTA-602 Readiness Diagnostic<br/>(Week 28)"]
    CTA601 --> S5["Sprint 5 (Weeks 29-34)<br/>Final Intensive<br/>2-3 full mocks per week"]
    S5 --> REST["Rest Week (Week 35)<br/>No studying last 5-7 days"]
    REST --> EXAM["Review Board Exam"]

    style EXAM fill:#FF5722,color:#fff
    style CTA601 fill:#FF9800,color:#fff

Domain Mastery Tracker

Use this to track your confidence across the 7 domains as you study:

quadrantChart
    title Domain Confidence Assessment
    x-axis Low Knowledge --> High Knowledge
    y-axis Low Practice --> High Practice
    quadrant-1 Ready to Present
    quadrant-2 Know It, Need Practice
    quadrant-3 Study + Practice Needed
    quadrant-4 Practice Without Depth
    System Architecture: [0.3, 0.3]
    Security: [0.3, 0.2]
    Data: [0.3, 0.3]
    Solution Architecture: [0.4, 0.3]
    Integration: [0.3, 0.2]
    Dev Lifecycle: [0.4, 0.4]
    Communication: [0.5, 0.3]

How to use this

Assess yourself on each domain and plot where you fall. Your study plan should prioritize domains in the bottom-left quadrant (low knowledge + low practice). Move everything to the top-right before attempting the board.

Exam Day Flow

Phase 1: Preparation (180 Minutes)

flowchart LR
    subgraph "Pass 1: Orient (15-20 min)"
        R1["Skim entire scenario"]
        R1 --> R2["Identify company,\nindustry, scope"]
        R2 --> R3["Count systems,\nuser types, regions"]
    end
    subgraph "Pass 2: Extract (25-35 min)"
        E1["Re-read with\nannotation"]
        E1 --> E2["Color-code by\ndomain"]
        E2 --> E3["Flag ambiguities\n& assumptions"]
    end
    subgraph "Architect (60-80 min)"
        A1["System Landscape\n(20-25 min)"]
        A1 --> A2["Data Model\n(20-25 min)"]
        A2 --> A3["Role Hierarchy &\nSecurity (15-20 min)"]
        A3 --> A4["Integration +\nDevOps (20-30 min)"]
    end
    subgraph "Prepare (15-20 min)"
        P1["Structure\nnarrative"]
        P1 --> P2["Mental\nrehearsal"]
        P2 --> P3["Gap check:\nall 7 domains?"]
    end

Time Budget

pie title 180-Minute Preparation Breakdown
    "First Read (Skim)" : 18
    "Second Read (Annotate)" : 30
    "System Landscape" : 23
    "Data Model" : 23
    "Role Hierarchy & Security" : 18
    "Integration Details" : 13
    "Dev Lifecycle & Governance" : 13
    "Presentation Flow & Notes" : 17
    "Review & Gap Check" : 12
    "Buffer" : 13

Phase 2: Presentation Flow (45 Minutes)

flowchart TD
    subgraph "Act 1: Opening (3-5 min)"
        O1["Business context\n& key requirements"]
        O1 --> O2["State assumptions"]
        O2 --> O3["Preview architectural\nphilosophy"]
    end
    subgraph "Act 2: Architecture Walkthrough (25-35 min)"
        W1["System Landscape\n(4-5 min)"]
        W1 --> W2["Data Model\n(4-5 min)"]
        W2 --> W3["Integration\n(4-5 min)"]
        W3 --> W4["Security & Identity\n(3-4 min)"]
        W4 --> W5["Actors & Licenses\n(2-3 min)"]
        W5 --> W6["Role Hierarchy\n(2-3 min)"]
        W6 --> W7["Data Migration\n(2-3 min)"]
        W7 --> W8["Governance & DevOps\n(3-4 min)"]
        W8 --> W9["Risks\n(2-3 min)"]
    end
    subgraph "Act 3: Close (2-3 min)"
        C1["Recap top 3 decisions"]
        C1 --> C2["Key trade-offs"]
        C2 --> C3["Confidence statement"]
    end

The 9 Essential Artifacts

mindmap
  root((CTA Artifacts))
    Tier 1: The Big 3
      System Landscape
        All systems + integration patterns
        Salesforce at center
        Color-coded with legend
      Data Model / ERD
        Standard + custom objects
        Relationships + cardinality
        OWD settings + volumes
      Role Hierarchy & Sharing
        Hierarchy tree
        Sharing rules
        Portal user placement
    Tier 2: Supporting
      Actors & Licenses
        User types mapped to licenses
        Access channels
      Identity & SSO Flow
        Authentication flow
        IdP configuration
        MFA + IP restrictions
      Integration Architecture
        Pattern per system
        Error handling
        Middleware decisions
    Tier 3: Governance
      Data Migration
        Source-to-target mapping
        Sequencing + tooling
        Cutover plan
      Dev & Deployment
        Environment strategy
        CI/CD pipeline
        Branching model
      Governance & Risks
        Decision framework
        Risk register
        Stakeholder cadence

Domain Coverage Matrix

Ensure your artifacts cover all 7 scoring domains:

block-beta
    columns 8
    block:header:8
        H["Artifact vs Domain Coverage"]
    end
    space D1["D1\nSys Arch"] D2["D2\nSecurity"] D3["D3\nData"] D4["D4\nSol Arch"] D5["D5\nInteg"] D6["D6\nDevOps"] D7["D7\nComms"]
    A1["System\nLandscape"] S1["PRIMARY"] s1[" "] s2[" "] S4["PRIMARY"] S5["PRIMARY"] s3[" "] s4[" "]
    A2["Data\nModel"] s5[" "] S2b["linked"] S3["PRIMARY"] S4b["linked"] s6[" "] s7[" "] s8[" "]
    A3["Role\nHierarchy"] s9[" "] S2c["PRIMARY"] S3b["PRIMARY"] s10[" "] s11[" "] s12[" "] s13[" "]
    A4["Integration"] s14[" "] s15[" "] s16[" "] s17[" "] S5b["PRIMARY"] s18[" "] s19[" "]
    A5["Governance"] s20[" "] s21[" "] s22[" "] s23[" "] s24[" "] S6["PRIMARY"] S7["PRIMARY"]

Cross-Domain Decision Cascade

Every major decision ripples through multiple domains. This diagram shows the most critical cascades:

flowchart TD
    ORG["Org Strategy\n(Single vs Multi-Org)"] --> SEC["Security Model\n(Sharing complexity)"]
    ORG --> INT["Integration\n(Org-to-org sync?)"]
    ORG --> DATA["Data Model\n(Volume per org)"]
    ORG --> DEV["Dev Lifecycle\n(Deploy targets)"]

    SEC --> DATA2["Data Access\n(OWD + Sharing Rules)"]
    SEC --> SOL["Solution Architecture\n(Apex sharing code?)"]
    SEC --> INT2["Integration\n(API visibility)"]

    DATA --> INT3["Integration\n(Data mapping)"]
    DATA --> PERF["Performance\n(LDV strategy)"]

    LIC["License Selection"] --> SEC2["Security\n(Feature access)"]
    LIC --> COST["Cost\n(Budget impact)"]
    LIC --> SOL2["Solution\n(Available features)"]

    style ORG fill:#E91E63,color:#fff
    style LIC fill:#9C27B0,color:#fff
    style SEC fill:#2196F3,color:#fff
    style DATA fill:#4CAF50,color:#fff

Mock Board Progression

flowchart LR
    subgraph "Early Mocks (Months 3-4)"
        M1["Focus: Complete\nall artifacts"]
        M1 --> M2["Focus: Cover\nall 7 domains"]
        M2 --> M3["Minimal Q&A\npractice"]
    end
    subgraph "Middle Mocks (Months 4-6)"
        M4["Add hostile\nQ&A sessions"]
        M4 --> M5["Practice defending\ndecisions"]
        M5 --> M6["Handle curveballs\nand what-ifs"]
    end
    subgraph "Final Mocks (Last 6-8 wks)"
        M7["Full simulation\nstrict timing"]
        M7 --> M8["CTA judges\non panel"]
        M8 --> M9["No mercy\nin Q&A"]
    end
    subgraph "Final Week"
        M10["Last mock:\n5-7 days before"]
        M10 --> M11["REST\nNo mock day before"]
    end

The Q&A Defense Framework

flowchart TD
    Q["Judge asks\na question"] --> S["S — Restate\nthe challenge"]
    S --> T["T — Think\nPause 3-5 seconds"]
    T --> A["A — Answer\nAddress specifically"]
    A --> R["R — Rationale\nExplain reasoning"]
    R --> AD["A — Adapt\nRevise if gap revealed"]

    style Q fill:#F44336,color:#fff
    style S fill:#FF9800,color:#fff
    style T fill:#FFC107,color:#000
    style A fill:#4CAF50,color:#fff
    style R fill:#2196F3,color:#fff
    style AD fill:#9C27B0,color:#fff

When to Stand Firm vs Adapt

flowchart TD
    CH["Judge challenges\nyour decision"] --> NEW{Does challenge\nintroduce NEW\ninformation?}
    NEW -->|No — testing conviction| FIRM["STAND FIRM\nRestate reasoning\nCite requirements\nAcknowledge alternative"]
    NEW -->|Yes — reveals gap| ADAPT["ADAPT\nAcknowledge the point\nRevise approach\nCheck cascading impact"]
    FIRM --> OK["Judges respect\nreasoned conviction"]
    ADAPT --> OK2["Judges respect\ngraceful adaptation"]

Key Success Factors

mindmap
  root((Pass the CTA))
    Technical Depth
      All 7 domains mastered
      Trade-offs for every decision
      Platform-first thinking
      Governor limit awareness
    Preparation
      8-10 full mock boards
      Lucidchart proficiency
      Timed practice sessions
      CTA-601 + CTA-602
    Communication
      Business-first narrative
      Clear, labeled diagrams
      Concise Q&A answers
      Calm under pressure
    Mindset
      No single right answer
      Honest about gaps
      Adaptable not rigid
      Confident not arrogant
    Community
      Study group membership
      CTA mentor
      Almost nobody passes alone
      Architect Ohana Slack

Sources

Official Salesforce

Community