Failed Salesforce Certified Technical Architect (CTA)? Here's Your Recovery Plan

Pro tip: Contact the exam provider directly for their specific retake policy.

• Treating the Architect Review Board Evaluation as an optional practice run.
  Salesforce lists it as step 1 of the credential, not a warm-up. You pass it before you sit the review board exam. Budget the $1,500 and the preparation for it as part of the path rather than something to skip toward the $4,500 exam.
• Ignoring Communication because it feels like a soft domain.
  Communication is one of the seven scored domains in the Salesforce exam outline, with explicit objectives on handling objections, using visualisation and documentation, and dealing with unexpected roadblocks. Rehearse the presentation and Q&A as deliberately as you rehearse integration patterns.
• Designing a technically elegant solution that does not trace to the stated requirements.
  Judges hold your design against the scenario they gave you. Keep a numbered requirement list from the reading phase and include a traceability slide that maps each requirement to the part of the architecture that satisfies it, so nothing goes unaddressed when the clock forces you to cut.
• Overrunning the preparation window and arriving with an incomplete deck.
  You get 180 minutes in the review board exam and only 60 in the evaluation. Fix a deck skeleton in advance and practise populating it under a timer so the preparation phase is data entry against a known structure rather than design from a blank page.
• Defaulting to code where configuration would meet the requirement.
  Solution Architecture is a scored domain specifically about the appropriate combination of declarative and programmatic functionality. Every time you propose Apex or Lightning Web Components, be ready to name the declarative option you rejected and why it fails the requirement.
• Presenting an integration landscape without naming volumes and patterns.
  Build an interface table during preparation with direction, pattern, technology, volume and frequency for each integration. A judge asking why you chose Platform Events over Bulk API wants the volume and timing argument, not a description of the feature.
• Conceding a correct design the moment a judge pushes back.
  The Communication objectives include handling objections related to the design. Judges probe correct answers as well as wrong ones. Restate the constraint that drove your choice, acknowledge the trade-off, and change position only when the objection introduces new information.
• Skipping licensing until the last week.
  Recommending the correct mix of licence types against capabilities, trade-offs and constraints is an explicit System Architecture objective. Build the actor-to-licence table early and keep it current, because licence errors cascade into the security and portal parts of your design.
• Relying on notes and lookups during practice.
  The exam guide states no hard-copy or online materials may be referenced during the exam, and smart devices must be removed and stored beforehand. If your practice sessions involve checking limits online, you are rehearsing a condition that will not exist on the day.

• Roughly 300 CTAs exist worldwide
• Review board format: present architecture solution to a panel of experts
• Requires deep experience across all Salesforce clouds and integration patterns
• Join CTA study groups, the community is small and supportive
• Practice presenting architecture decisions under pressure
• Most candidates attempt 2-3 times before passing, budget accordingly