Skip to content

Exam Format

The CTA Review Board is a half-day, scenario-based oral exam. Candidates receive a complex hypothetical business scenario, design a solution, and present it to a panel of judges.

Four sequential phases showing preparation, break, presentation, and Q&A with durations across a half-day exam window.
Figure 1. The four phases of the CTA Review Board exam day, from three hours of unassisted preparation through a structured Q&A with active CTA judges.

Candidates receive a detailed business scenario document describing a fictional company with complex requirements. The task is to design a complete technical solution using only the tools provided:

  • Provided: Google Docs (scenario document), Google Slides (presentation), Google Sheets (tables/calculations), Lucidchart (diagrams, with Salesforce Shape Library), paper and pen
  • Not allowed: Internet access, personal notes, reference materials, or any outside resources
  • Goal: Create a presentation that covers your recommended architecture, addressing all 7 exam domains
  • Non-English speakers: Receive 210 minutes (3.5 hours) instead of 180

See Review Board Artifacts & Deliverables for the full artifact creation guide: what to build, how to allocate your 180 minutes, Lucidchart techniques, and lessons from candidates who passed and failed.

Candidates present their solution to a panel of 3 active CTA judges. This is the window for walking through the architecture, explaining decisions, and demonstrating depth of knowledge.

What judges look for:

  • Clear articulation of the overall architecture
  • Identification of risks and trade-offs (not just the happy path)
  • Appropriate use of platform capabilities
  • Justification for technology choices
  • Realistic approach to data, integration, and security

Judges probe the solution with challenging questions. Expect them to:

  • Push back on decisions to test conviction and reasoning
  • Ask about alternatives that were not chosen
  • Explore edge cases and failure scenarios
  • Test depth in areas where the presentation was thin
  • Challenge assumptions with “what if” scenarios

A typical CTA scenario covers:

  • Company profile: Industry, size, geography, org structure
  • Current state: Existing systems, pain points, technical debt
  • Requirements: Business requirements, technical constraints, compliance needs
  • Stakeholder concerns: Performance expectations, budget constraints, timeline
  • Integration landscape: Enterprise systems that must be connected
  • Data considerations: Volume, migration needs, reporting requirements
  • User types: Internal users, external communities, partner portals with different access needs

The scenario is intentionally complex and ambiguous. There is no single right answer. Judges evaluate the quality of reasoning, not whether the candidate matched a rubric.

  • Pass/Fail with no percentage score
  • All 7 domains are scored independently by each judge
  • Minimum threshold required in each domain
  • Failing more than one domain = full fail (must retake everything)
  • Failing exactly one domain = eligible for a targeted section retake

See Domains & Scoring for the full domain breakdown.

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.