Skip to content
theCodeFlash

CTA Preparation Roadmap

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

The End-to-End CTA Journey

Figure 1. Typical 4-6 year CTA journey from first architect cert through the pinnacle credential, with the two super-credentials (Application Architect and System Architect) auto-awarded along the way.

Prerequisite Certification Path

Seven exams converge into Application Architect and System Architect super-credentials, both required before registering for the CTA Step 1 Evaluation.
Figure 2. Prerequisite certification map showing how seven exams converge into the Application Architect and System Architect super-credentials, both required before registering for the CTA Step 1 Evaluation.
Seven certifications in a sequenced chain where each builds on the prior — Data feeds Sharing, Integration feeds Identity — ending with both super-credentials awarded.
Figure 3. Recommended sequential order for the seven prerequisite exams: each certification builds on knowledge from the prior one, with Data feeding Sharing, Integration feeding Identity.

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

Foundation, domain study, cross-domain practice, and ten mock board sessions sequenced from April through October, ending with Step 1 and Step 2 exam dates.
Figure 4. Six-month preparation plan from CTA-601 Workshop through the Step 2 Review Board, with domain study, cross-domain scenarios, and 10 mock board sessions sequenced across the timeline.

Weekly Study Plan Structure

Domain study leads at 30%, scenario practice at 25%, mock presentations at 20%, Lucidchart diagramming at 15%, and community engagement at 10%.
Figure 5. Recommended weekly time split across five study activities: domain reading anchors at 30%, with scenario practice and mock presentations together accounting for nearly half of all study hours.

The Sprint-Based Study Approach

Five domain-focused sprints separated by break weeks, escalating from mini-mocks to two or three full boards per week, ending with a mandatory rest week before the exam.
Figure 6. Five-sprint study structure across 35 weeks: each sprint targets specific domains, intensity escalates from mini-mocks to 2-3 full boards per week, and a mandatory rest week precedes the exam.

Domain Mastery Tracker

Track confidence across the 7 domains as study progresses:

Plot each of the seven CTA domains by knowledge versus practice level to identify which fall in the study-and-practice-needed quadrant requiring the most attention.
Figure 7. Domain confidence self-assessment quadrant: plot each of the seven domains by knowledge vs. practice level, then prioritize study time on whichever domains fall in the bottom-left quadrant.

How to use this

Plot each domain based on self-assessment. Prioritize 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)

Two reading passes build context, the architect block creates all key diagrams, and the prepare block structures the narrative before the presentation begins.
Figure 8. Four-pass structure for the 180-minute preparation phase: two reading passes build context, the architect block creates all diagrams, and the final prepare block structures the narrative before presenting.

Time Budget

The Big 3 diagrams — System Landscape, Data Model, Role Hierarchy — claim the largest share, with explicit buffer time built in for overruns across all activities.
Figure 9. Minute-by-minute budget for the 180-minute preparation window: the Big 3 diagrams (System Landscape, Data Model, Role Hierarchy) claim the largest share, with explicit buffer time built in for overruns.

Phase 2: Presentation Flow (45 Minutes)

Three-act structure — opening sets context, architecture walkthrough covers all nine artifact areas in sequence, close recaps top decisions and trade-offs for the judges.
Figure 10. Recommended 45-minute presentation structure across three acts: opening sets context, the architecture walkthrough covers all nine artifact areas in sequence, and the close recaps the top decisions and trade-offs.

The 9 Essential Artifacts

Figure 11. The nine CTA artifacts grouped by tier: the Big 3 (System Landscape, Data Model, Role Hierarchy) are foundational and must be correct, while Tier 2 and Tier 3 artifacts support and extend them.

Domain Coverage Matrix

Verify that artifacts cover all 7 scoring domains:

Figure 12. Artifact-to-domain coverage matrix: each row is one of the nine artifacts, each column is a scoring domain, showing which artifacts carry primary vs. supporting coverage for each domain.

Cross-Domain Decision Cascade

Every major decision ripples through multiple domains. The diagram below shows the common cascades:

Org strategy and license selection each trigger downstream effects on security, data, integration, and development lifecycle decisions throughout the solution design.
Figure 13. Cross-domain decision cascade: org strategy and license selection each trigger downstream effects on security, data, integration, and development lifecycle decisions throughout the solution.

Mock Board Progression

Early mocks focus on artifact completion and domain coverage, middle mocks add hostile Q&A, final mocks simulate the full exam with CTA judges and strict timing.
Figure 14. Mock board progression from early artifact-focused sessions through hostile Q&A practice to full exam simulations, ending with a mandatory rest period in the final week before the board.

The Q&A Defense Framework

Five-step structure — Restate, Think, Answer, Rationale, Adapt — that keeps Q&A responses focused and signals architectural maturity to the judges.
Figure 15. The STARA Q&A response framework: Restate, Think, Answer, Rationale, Adapt. This five-step structure keeps answers focused and signals architectural maturity to the judges.

When to Stand Firm vs Adapt

When a judge challenge introduces genuinely new information, adapt gracefully; when it tests conviction only, restate reasoning and hold the position confidently.
Figure 16. Stand firm vs. adapt decision tree: when a judge challenge introduces genuinely new information, adapt; when it is testing conviction alone, restate the reasoning and hold the position.

Key Success Factors

Figure 17. Five pillars of CTA success: technical depth across all seven domains, structured preparation through mock boards, clear communication under pressure, the right mindset, and active community participation.

Sources

Official Salesforce

Community

Personal study notes for the Salesforce CTA exam. Content compiled from VJ's study notes, official Salesforce documentation, community sources, and online publicly available content, then organized and presented with AI assistance. Not affiliated with Salesforce. © 2025–2026 VJ Srivastava.