Skip to content
SF CTA Study Hub

Review Board Preparation Guide

This guide consolidates the latest (2024-2026) strategies, tips, and first-hand advice for preparing and presenting at the Salesforce CTA Review Board. It draws from CTA coaches, community leaders, and architects who have passed.

1. Review Board Format and Structure

Two-Step Credential Process

The CTA credential requires passing two separate evaluations:

StepNameFormatDurationCostRetake Cost
Step 1Architect Review Board Evaluation (CTA-601 style)Shorter scenario, 1 evaluator~2 hours total$1,500 USD$750 USD
Step 2Architect Review Board ExamFull scenario, 3-4 CTA judges~4.5 hours total$4,500 USD$2,250 USD

Total investment: approximately $6,000 USD (before any retakes or training programs).

Two-step process

The Evaluation (Step 1) is a “mini-review board” testing broader domain knowledge with a simpler scenario in front of one judge. It validates readiness before the full Review Board Exam (Step 2). You must pass Step 1 before attempting Step 2.

Three Phases of the Review Board Exam

gantt
    title CTA Review Board Exam Day
    dateFormat HH:mm
    axisFormat %H:%M

    section Phases
    Preparation (read & design)    :prep, 00:00, 3h
    Break                          :break, after prep, 15min
    Presentation                   :pres, after break, 45min
    Q&A                            :qa, after pres, 40min
PhaseDurationWhat Happens
Preparation180 minutes (3 hours)Read the scenario, analyze requirements, design your complete solution, create all artifacts and diagrams
Break15 minutesBrief rest before presenting
Presentation45 minutesPresent your solution to the panel of 3-4 CTA judges. Unused time transfers to Q&A
Q&A40-90 minutesJudges probe your solution, challenge your decisions, and test broader platform knowledge

Non-English speakers

Non-native English speakers receive additional time: 3.5 hours for preparation (vs. 3 hours) and 60 minutes for Q&A (vs. 40-90 minutes). This is built into the exam format — you do not need to request it separately.

Virtual Format (Since October 2023)

The review board is now conducted entirely virtually via video conference:

  • Lucidchart is the only officially allowed diagramming tool, with the Salesforce Shape Library pre-loaded
  • Google Slides is available for additional presentation slides
  • Hand-drawn artifacts are no longer accepted
  • All artifacts must be created digitally during the preparation phase
  • You share your screen to present diagrams and artifacts to the judges

Prerequisites

Before you can register for the Review Board, you must hold:

  • Salesforce Certified Application Architect (requires Platform App Builder + 3 designer certs)
  • Salesforce Certified System Architect (requires Platform Developer I + 3 architect certs)

2. Presentation Strategy

Based on guidance from CTA coaches and successful candidates, structure your 45-minute presentation in this order:

#SectionTime BudgetPriority
1Company Overview & Project Objectives2-3 minAlways
2Org Strategy & Translation/Multi-Currency2-3 minAlways
3Risks & Assumptions2-3 minHigh
4Actors, User Types & Licenses3-4 minHigh
5Role Hierarchy3-4 minAlways
6System Landscape (the “Big Picture”)5-6 minAlways
7Data Model (ERD)4-5 minAlways
8Business Requirements & Solution Design6-8 minAlways
9Integration Architecture4-5 minAlways
10Data Migration Strategy3-4 minHigh
11Security, Sharing & Accessibility3-4 minAlways
12Reporting & Analytics2-3 minHigh
13Development Lifecycle, Governance & Deployment3-4 minAlways

The “Big 3” diagrams

The three most critical diagrams you must get right are: System Landscape, Data Model (ERD), and Role Hierarchy. These form the backbone of your entire solution. If these are wrong, everything else falls apart. Invest significant preparation time in getting these correct.

Key Presentation Principles

  1. Tell a story, not a list — Structure your presentation as a coherent narrative connecting all components. Do not just read bullet points from slides.

  2. Lead with “why”, not “what” — For every architectural decision, explain the business rationale, what alternatives you considered, and what trade-offs you accepted.

  3. Address ALL scenario requirements — Do not skip requirements or introduce new ones that are not in the scenario. Judges notice both omissions and additions.

  4. Be the recommending architect — Give strong, confident recommendations with clear assumptions. Do not present multiple options and let the “customer” decide. The judges want to see your judgment as the Technical Architect.

  5. Show governance throughout — Governance is not a separate section at the end. Weave risk identification, mitigation strategies, and governance considerations throughout your entire presentation.

  6. Communicate to a CXO audience — Your diagrams and communication should be polished enough to present to a Chief Information Officer. Professional attention to detail matters.

Diagram Best Practices

  • Use the Salesforce Shape Library in Lucidchart for consistent, professional-looking diagrams
  • Diagrams must be readable, correct, and clearly labeled — wrong diagrams automatically hurt your score
  • Include legends and annotations on complex diagrams
  • Practice creating all standard diagram types under time pressure in Lucidchart
  • Standard diagram types to prepare:
    • System Landscape / Context Diagram
    • Entity Relationship Diagram (ERD / Data Model)
    • Role Hierarchy
    • SSO / Identity Flow Diagram
    • Integration Architecture (with patterns, protocols, sync/async)
    • Data Migration Flow
    • Environment / Deployment Strategy
    • Sequence Diagrams for complex integration flows
    • Business Process Diagrams (optional, but helpful)

3. Q&A Preparation

Types of Questions the Board Asks

The Q&A is 40-90 minutes of judges probing your solution. Expect these categories:

Solution-Specific Questions:

  • “Why did you choose X over Y?”
  • “What happens if [component] fails?”
  • “How does your data model handle [edge case]?”
  • “Walk me through the identity flow at the attribute level”
  • “What are the governor limits implications of your approach?”
  • “How does your integration handle error scenarios?”

Clarification Questions:

  • “Can you elaborate on how [requirement] is addressed?”
  • “I noticed you didn’t mention [topic]. How would you handle it?”
  • “What assumptions did you make about [aspect]?”

Challenge Questions (Pushback):

  • “What if the data volume was 10x what you assumed?”
  • “The customer pushes back on your license recommendation. What’s your alternative?”
  • “What if the budget only allows for one middleware tool?”
  • “Your approach seems complex. Why not just use [simpler approach]?”

Broader Platform Knowledge:

  • OAuth flows and asset flow diagrams
  • SAML token attributes and SSO configuration
  • ETL vs. ESB: when to use each
  • Platform limits and governor limits
  • Salesforce Connect vs. custom integration
  • LDV (Large Data Volume) mitigation strategies
  • Sharing rule performance implications

Q&A Strategy

  1. Listen carefully — Restate the question to confirm you understand what the judge is asking. Do not answer a different question.

  2. Be concise — Keep answers “correct and concise.” Verbose answers consume valuable Q&A time and reduce the number of questions you can answer well. More questions answered = more opportunities to score points.

  3. It is OK to say “I don’t know” — Saying this occasionally is acceptable and shows intellectual honesty. But do not overuse it, and try to reason through what you do know.

  4. Distinguish pushback from correction — When judges push back, they are often testing your conviction, not telling you that you are wrong. Stand firm when you have sound reasoning. Adapt gracefully when the challenge reveals a genuine gap.

  5. Do not offer alternatives unless asked — Recommend ONE approach and justify it. Offering multiple options makes you look indecisive. Only discuss alternatives when a judge specifically asks “what else could you do?”

  6. Provide technical depth — Answers like “I’ll do a callout from an Apex trigger after save” lack sufficient detail. Instead: “I’ll use an external service invocation in a request-and-reply pattern, triggered by a platform event, to ensure asynchronous processing and retry capability.”

4. Communication Style

What Works Best

The CTA Review Board tests you as a consulting architect, not just a technical expert. The most successful candidates demonstrate:

  • Business-value framing — Connect technical decisions to business outcomes
  • Stakeholder awareness — Show you understand different stakeholders have different concerns (CIO cares about TCO, business users care about usability, IT team cares about maintainability)
  • Confident delivery — Speak with authority. You are the Technical Architect advising this company.
  • Structured communication — Logical flow, clear transitions between topics, signposting where you are in your presentation
  • Visual communication — Let your diagrams do heavy lifting. Point to them, reference them, connect them across topics

What to Avoid

  • Unexplained jargon — If you use a technical term, explain it briefly. Judges will probe unexplained buzzwords.
  • Reading from slides — Use slides as visual aids, not scripts
  • Monotone delivery — Vary your pace and emphasis to highlight critical decisions
  • Apologizing for your solution — Present with confidence, even if you realize mid-presentation that something could be better

5. Time Management

During the 180-Minute Preparation Phase

Recommended time allocation:

ActivityTimeNotes
Read the entire scenario carefully (first pass)20-25 minHighlight key requirements, constraints, and stakeholder concerns
Re-read and extract requirements systematically15-20 minCreate a requirements checklist; identify actors, systems, data volumes
Design your solution (architecture decisions)45-50 minWork through the Big 3 first: System Landscape, Data Model, Role Hierarchy
Create diagrams in Lucidchart50-60 minUse Salesforce Shape Library; keep diagrams clean and labeled
Create remaining presentation slides20-25 minCover migration, governance, deployment, risks
Review and rehearse mentally10-15 minVerify all requirements are addressed; plan your presentation flow

Start diagramming immediately

As you read the scenario, start drawing the system landscape and extracting actors. Do not wait until you have read the entire scenario before starting your diagrams. Build them incrementally as you progress through requirements.

During the 45-Minute Presentation

  • Do not rush — Speak at a measured pace that conveys confidence
  • Watch the clock — Keep mental checkpoints (e.g., “I should be at Integration by minute 25”)
  • If running long, summarize remaining sections briefly rather than skipping them entirely
  • Unused presentation time converts to Q&A time — So finishing a few minutes early can actually help by giving you more Q&A opportunities to score points

During the 40-Minute Q&A

  • Keep answers to 2-3 minutes maximum per question
  • If a question requires a long answer, provide a summary first, then offer to go deeper
  • Do not ramble — stop talking when you have answered the question

6. Common Pitfalls and Why People Fail

The Most Common Mistakes

Based on CTA coaches, judges, and candidates who have shared their experiences:

Strategic Errors:

  1. Changing your strategy on exam day — “A recipe for failure, guaranteed.” Stick with the preparation approach and presentation structure you have practiced.
  2. Introducing requirements not in the scenario — Only solve for what the scenario asks. Adding requirements wastes time and shows you did not read carefully.
  3. Generic, one-size-fits-all solutions — Tailor everything (data migration, governance, deployment) to the specific scenario context. Cookie-cutter approaches are immediately obvious to judges.
  4. Not recommending — presenting options instead — The judges want your recommendation as the architect, not a menu of choices.

Technical Errors: 5. Data model does not support all requirements — The data model is the foundation. If it is wrong, every section built on top of it crumbles. This is the section candidates most frequently fail. 6. License choices misaligned with chosen standard objects — Know which licenses grant access to which objects and features. 7. Integration design that “throws systems together” — Show architectural rigor: patterns, protocols, error handling, monitoring, and retry strategies. 8. Missing Salesforce Connect when the scenario calls for it — Recognize when external objects or Salesforce Connect are the right tool. 9. Insufficient identity/SSO depth — Be able to describe identity flows at the SAML attribute level, not just “we’ll use SSO.” 10. Not addressing LDV (Large Data Volume) considerations — If the scenario mentions millions of records, you must address skinny tables, indexing, archiving strategies, and query optimization.

Communication Errors: 11. Neglecting soft skills — Presentation, communication, and diagramming skills are explicitly scored (Domain 7: Communication). These are not “nice to have.” 12. Verbose Q&A answers — Long answers waste time and reduce your scoring opportunities. 13. Not listening to judge questions — Answer the question that was asked, not the question you want to answer. 14. Poor diagrams — Unreadable, incorrect, or missing diagrams directly impact your score.

Preparation Errors: 15. Not doing enough mock boards — Candidates who pass typically complete 8-20+ mock sessions. There is no substitute for practice. 16. Studying theory without practicing presentations — Knowing the content is necessary but not sufficient. You must practice presenting under time pressure. 17. Going it alone — “Nobody passes the CTA alone, it is just too tough.” Community, coaching, and study partners are essential.

Lessons from a Failed Attempt

One candidate who shared their failure analysis identified these specific mistakes:

  • Missing an entire artifact (Integrations slide) — judges cannot score what you do not present
  • Not practicing under exam conditions (virtual PC with input lag)
  • Speaking at normal speed instead of being deliberate and paced
  • Offering alternatives instead of making strong recommendations
  • Answers lacking sufficient technical depth and justification
  • Failing to recognize a Salesforce Connect requirement in the scenario
  • Not utilizing extra time available for non-English speakers

7. Preparation Timeline

Reality check

As of 2024, there are ~500 CTAs worldwide. The certification has existed since 2011. The pass rate is historically low. This is a marathon, not a sprint. Average preparation time is approximately 500-1,000+ hours.

PhaseTimelineActivitiesHours/Week
FoundationMonths 1-2Complete Application & System Architect certs; join community groups; attend CTA-601 workshop5-10
Knowledge BuildingMonths 3-4Deep-dive into all 7 domains; gap analysis against Exam Guide; study architecture patterns10-15
Scenario PracticeMonths 5-6Begin mock scenarios with study group; start with short scenarios (3-5 pages); practice diagramming in Lucidchart15-20
Intensive PracticeMonths 7-8Full-length mock boards (1-2 per week); practice with CTA judges; attend CTA-602 Readiness Diagnostic15-20
Final SprintMonths 9-10Polish presentation style; 2 mocks per week; focus on weak areas identified in feedback15-20
Exam ReadyMonth 11-12Final 2-3 mocks with CTA judges; schedule exam; mental preparation10-15

Key Milestones

flowchart LR
    A[Prerequisites Complete] --> B[CTA-601 Workshop]
    B --> C[Gap Analysis]
    C --> D[Join Study Group]
    D --> E[First Mock Scenario]
    E --> F[8-10 Mocks Complete]
    F --> G[CTA-602 Readiness Check]
    G --> H[Evaluation Step 1]
    H --> I[Review Board Step 2]
    I --> J[CTA Certified]

Study Hours Benchmark

From a survey of successful CTAs:

  • Minimum: 500 hours (very experienced architects with 10+ years)
  • Average: 500-1,000+ hours
  • Upper range: 1,000+ hours
  • Weekly commitment: 15-20 hours per week for 6 months minimum
  • Salesforce-specific experience: Minimum 3 years, average 5+ years
  • Total professional experience: Average 10+ years

8. Practice Strategies

Mock Board Sessions

Mock boards are the single most important preparation activity. Here is how to approach them:

Progression:

StageScenario LengthFocusSessions
Early (Months 1-3)Short (3-5 pages): Baby Box, City Scooter, Green RoofBasic artifact creation, time management3-4
Middle (Months 4-6)Medium (5-8 pages): Laptop to School, Pollard FinancialFull solution design, presentation flow4-6
Late (Months 7-10)Full-length (8-12 pages): Universal Safety, Universal RacingComplete exam simulation with Q&A8-10

Minimum target: 8-10 full mock sessions before the actual exam. Many successful CTAs recommend 15-20+.

Mock Session Format:

  1. Preparation: 3 hours reading scenario and creating artifacts (use Lucidchart!)
  2. Presentation: 45 minutes presenting to mock judges
  3. Q&A: 40-90 minutes of challenging questions
  4. Feedback: 30-60 minutes of constructive feedback
  5. Total per session: approximately 5-6 hours

Mock best practices

  • Have at least one CTA among your mock judges whenever possible
  • Record your mock sessions and review them afterward
  • Practice on a virtual machine or remote desktop to simulate the exam’s input lag
  • Do not repeat the same scenario back-to-back — space them out with weeks in between
  • In the last 6-8 weeks, do 1-2 mocks per week

Study Groups and Communities

Essential communities to join:

CommunityPlatformDescription
Architect OhanaSlackFounded by Melissa Shepard. Monthly CTA office hours, study groups, mock scenarios, presentations from CTAs
Architect TrailblazersTrailhead CommunityOfficial Salesforce community with practice scenarios, solution recordings, and study group links
CTA Gang of FourWebsite (ctagof.com)Comprehensive list of publicly available mock scenarios; experienced feedback from CTAs
Ladies Be ArchitectsWebsite & CommunityMock scenarios (Flower Racing, Wine & Sunflowers), study resources, mentorship
FlowRepublic AlumniPrivate communityFor graduates of the FlowRepublic coaching program

Coaching and Training Programs

ProgramDurationCostWhat’s Included
FlowRepublic CTA Coaching12 months~6,250 EUR28 modules, monthly scenarios, mock recordings, 1:1 coaching. Claims 50%+ of all new CTAs since 2018 (80+ CTAs)
CTA-601 Preparation Workshop (Trailhead Academy)2-3 daysVariesLed by active CTAs; scenario walkthrough with feedback. Take this early in your preparation
CTA-602 Readiness Diagnostic (Trailhead Academy)1-2 daysVariesReadiness assessment. Take this 1-2 months before your exam
”Becoming a Salesforce CTA” (Book by Tameem Bahri, Packt)Self-paced~$40-509+ practice scenarios with solution approaches; architectural strategy patterns

Publicly Available Mock Scenarios

A comprehensive list from the CTA Gang of Four and community sources:

Official Salesforce Scenarios:

  1. City Scooter Share (2017)
  2. Laptop to School (2017)
  3. Green Roof Systems (2017)
  4. Pollard Financial Services (Australian edition)
  5. Universal Safety Technologies (2019)
  6. Greenhouse Recycling Corporation (2018)
  7. Galaxy Cars (Retired)
  8. Clean Bikes (Retired)

Community-Created Scenarios: 9. Universal Parcel — FlowRepublic (180-minute full length) 10. Xmas Santa Clause — FlowRepublic (2020) 11. Flower Racing — Ladies Be Architects 12. Wine & Sunflowers — Ladies Be Architects 13. Constructus Temporary Buildings — Andrew Hart / cta202.com (2021) 14. Musicians Incorporated — Andrew Hart (2021) 15. Hire Me Services — Andrew Hart (2021) 16. Greens & Veg — Andrew Hart (2021) 17. Roads for Everyone — Andrew Hart (2021) 18. High End Clothing — Andrew Hart (2021)

Packt Book Scenarios (by Tameem Bahri): 19. Packt Lightning Utility 20. Packt Pioneer Auto 21. Packt Digital 22. Packt Innovative Retailers 23. Packt Medical Equipment 24. Packt Modern Furniture 25. Packt Online Wizz 26. Packt United Builders 27. Packt Visiting Angels

Scenario progression

Start with shorter, simpler scenarios (City Scooter, Green Roof, Baby Box) and gradually work up to the full-length, complex ones (Universal Safety, Universal Parcel). Practice each one under real exam conditions — 3 hours preparation, 45-minute presentation, 40-minute Q&A.

9. Tips from CTAs Who Passed

First-Hand Advice from Successful Candidates

Sebastian Wagner (CTA Master Coach, behind 80+ of the ~500 CTAs worldwide):

  • “DO NOT CHANGE YOUR STRATEGY between preparation and exam day”
  • Real-world architect experience is non-negotiable
  • Do not skip softer competencies — presentation, communication, and diagramming are crucial
  • Manage stress through thorough preparation — the exam creates an artificial high-stress environment
  • Not everybody can become a CTA, and that is OK — the preparation itself makes you a better architect

Keir Bowden (Bob Buzzard, CTA):

  1. Brush up on everything — do not focus only on weak areas
  2. Give yourself plenty of time to arrive and settle before the exam
  3. Keep calm — you will make mistakes; do not let them derail you
  4. Do not play favorites — evaluate all platform features objectively, even ones you personally dislike
  5. Do not stick with bad decisions — if you realize mid-presentation that you made a mistake, correct it rather than defending a wrong answer

Guy Keshet (CTA):

  • Plan 12-15 hours of study per week for at least 6 months
  • Each mock session takes approximately 6 hours end-to-end
  • Join Architect Ohana community to find study partners
  • Start with shorter scenarios and gradually advance
  • Honestly assess your motivation before starting — this is a massive commitment
  • Soft skills are non-negotiable: presenting, time management under pressure, defending decisions

Jannis Bott (CTA):

  • On first attempt: “I did around three mock exams but never really presented them to anyone but myself. This was one of my major downfalls — I got into serious time management issues.”
  • On successful retake: completed 5+ full mocks under real exam conditions with feedback
  • Start drawing diagrams immediately while reading the scenario — do not wait until you finish reading
  • Extract actors and system landscape from the first page
  • Build data model and hierarchies concurrently, not at the end
  • Only attempt the board “when you have gained enough consulting experience that allows you to speak freely and without hesitation to the panel of judges”

Martin Humpolec (shared failure analysis):

  • Missing even one major artifact (like Integrations) is devastating — judges cannot score what you do not present
  • Create slides for every major topic as backup references
  • “I’ll do a callout from an Apex trigger” lacks the detail required — provide specific patterns and justifications
  • Practice full mock exams end-to-end, not fragmented sections
  • Mentorship is non-negotiable for presentation and Q&A practice

Collective Wisdom from 9 CTAs (Salesforce Ben survey):

  • “Almost nobody passes the CTA exam alone”
  • Average preparation: 500-1,000+ hours over 4-12 months
  • Weekly commitment: 15-20 hours for 6 months minimum
  • All successful candidates used coaching or professional offerings
  • Five key principles:
    1. Embrace failure as part of the learning process
    2. Maintain momentum — do not rush or excessively prolong preparation
    3. Focus exclusively on review board requirements (not peripheral topics)
    4. Practice extensively: solutioning, presenting, and Q&A
    5. Maintain enjoyment throughout the demanding journey

10. The 7 Domains Deep Dive

Each domain is scored independently. There are no published percentage weightings — you must pass every domain.

Domain 1: System Architecture (6 objectives)

What the board evaluates:

  • Appropriate mix of on/off-platform systems
  • Reporting and analytics strategy
  • Single vs. multi-org considerations
  • Mobile solution design
  • License type selection (know what each license grants down to the object level)
  • Document management approach

Common pitfalls: License choices that do not support the standard objects in your data model. Not knowing the difference between Sales Cloud, Service Cloud, and Experience Cloud license capabilities.

Domain 2: Security (6 objectives)

What the board evaluates:

  • Platform security mechanisms (OWD, sharing rules, role hierarchy, profiles, permission sets)
  • Portal/community security architecture
  • Declarative vs. programmatic security (when to use each)
  • Object and field-level security
  • End-to-end identity management (SSO, OAuth, SAML)

Common pitfalls: Inability to describe identity flows at the SAML attribute level. Not knowing when to use implicit sharing vs. sharing rules vs. Apex-managed sharing. Overlooking the security implications of community/portal users.

Domain 3: Data (3 objectives)

What the board evaluates:

  • Large Data Volume (LDV) architecture and optimization
  • Data modeling concepts and database design
  • Data migration strategy and tool selection

Common pitfalls: This is the domain candidates most frequently get partially wrong. Generic “Extract-Format-Dedupe-Load” migration strategies instead of tailored approaches. Not addressing LDV mitigation (skinny tables, indexing, archiving). Data model that does not support all requirements across all sections.

Data is foundational

Your data model must support EVERY other section: security (sharing model depends on object hierarchy), integration (data must be available for integrations), reporting (data structure determines what reports are possible), and solution architecture (object choices affect automation options). Get data wrong and everything else collapses.

Domain 4: Solution Architecture (2 objectives)

What the board evaluates:

  • Config vs. customize vs. code vs. buy decisions
  • Trade-offs of incorporating external applications (AppExchange, third-party)

Common pitfalls: Not knowing when to use declarative (Flow) vs. programmatic (Apex, LWC). Note: Process Builder is deprecated — always recommend Flow instead. Not considering AppExchange solutions where appropriate. Inability to explain component-level integration end-to-end.

Domain 5: Integration (4 objectives)

What the board evaluates:

  • Enterprise integration landscape design
  • Technology selection and justification (MuleSoft, middleware, point-to-point)
  • Integration patterns (request-reply, fire-and-forget, batch, near-real-time, pub/sub)
  • Platform-specific integration tech (REST, SOAP, Platform Events, Change Data Capture, Salesforce Connect)

Common pitfalls: Not distinguishing ESB (for orchestration) from ETL (for heavy data lifting). Missing error handling, retry strategies, and monitoring in integration design. Not addressing data availability for reporting after integration.

Domain 6: Development Lifecycle & Deployment (6 objectives)

What the board evaluates:

  • Risk identification and mitigation strategies
  • Methodology choices (Agile, waterfall, hybrid) fitting the customer context
  • Comprehensive test strategy
  • Governance frameworks
  • Environment management (sandbox strategy)
  • Source control and CI/CD (branching strategy aligned with release management)

Common pitfalls: Cookie-cutter “we’ll use Agile with Scrum” without considering the customer’s actual environment. Not identifying project-specific risks. Governance described as an afterthought rather than woven throughout the solution.

Domain 7: Communication (3 objectives)

What the board evaluates:

  • Articulation of benefits, limitations, design choices, and trade-offs
  • Use of visualization and documentation tools (diagrams!)
  • Handling unexpected roadblocks and objections

Common pitfalls: Neglecting this as a “soft” domain — it is explicitly scored. Unreadable or incorrect diagrams. Inability to handle pushback gracefully. Verbose, unfocused answers during Q&A.

Official Salesforce Resources

Community and Coaching

Articles and First-Hand Accounts

Books

  • “Becoming a Salesforce Certified Technical Architect” by Tameem Bahri (Packt, 2nd Edition 2023) — Includes 9+ practice scenarios and architectural strategy patterns
  • Amazon Link

GitHub Study Resources

Sources

All URLs in Section 11 above serve as the primary source list for this page. The following additional official Salesforce resources informed the content throughout:

Official Salesforce

Community (cited in content)