- The CTAL-TTA Exam at a Glance
- How the Six Chapters Are Allocated
- Domain 1: The Technical Test Analyst's Tasks in Risk-Based Testing
- Domain 2: White-Box Test Techniques
- Domain 3: Static and Dynamic Analysis
- Domain 4: Quality Characteristics for Technical Testing
- Domain 5: Reviews
- Domain 6: Test Tools and Automation
- Sequencing Your Study by Domain
- Syllabus Version, Fees and Booking Details
- Frequently Asked Questions
- The exam covers six syllabus chapters: 45 multiple-choice questions, 78 points, 120 minutes, with 51 points (65%) needed to pass.
- Quality Characteristics for Technical Testing carries the most weight: 13 questions and 21 points.
- White-Box Test Techniques (8 questions, 17 points) and Reviews (10 questions, 11 points) together outweigh half the exam's point total of the smaller chapters...
- Official percentage weights are not published, so treat question and point allocations as your authoritative guide.
The CTAL-TTA Exam at a Glance
The credential discussed here is the ISTQB Certified Tester Advanced Level Technical Test Analyst (CTAL-TTA), administered in the United States by the American Software Testing Qualifications Board (ASTQB). It is a distinct Advanced Level scope, separate from the Test Analyst and Test Management modules. If you are still orienting yourself, our explainers on what CTAL certification is and what CTAL stands for cover the basics, and this article goes straight into the content areas.
The exam consists of 45 multiple-choice questions worth 78 available points, delivered in 120 minutes. Some questions require a single response and others require multiple responses, and many are built around technical scenarios or code analysis. That last detail matters: you will be reading code fragments, control-flow descriptions and architecture snippets, not just recalling definitions.
Passing requires at least 65% of the available points, which the official exam structure table specifies as 51 of 78. The exam is closed-book and proctored. Eligible candidates sitting the exam in a non-native language receive 25% extra time, which brings the limit to 150 minutes. For a deeper look at the threshold, see our page on the CTAL passing score.
How the Six Chapters Are Allocated
The six domains are official, examinable syllabus chapters. The ASTQB exam structure tables allocate questions and points to each chapter as follows:
| Chapter | Domain | Questions | Points |
|---|---|---|---|
| 1 | The Technical Test Analyst's Tasks in Risk-Based Testing | 2 | 2 |
| 2 | White-Box Test Techniques | 8 | 17 |
| 3 | Static and Dynamic Analysis | 7 | 14 |
| 4 | Quality Characteristics for Technical Testing | 13 | 21 |
| 5 | Reviews | 5 | 13 |
| 6 | Test Tools and Automation | 10 | 11 |
Notice how points and questions diverge. Reviews has only 5 questions but 13 points, meaning each review question is worth more than average, which suggests multi-response or heavier-scoring items. Test Tools and Automation has 10 questions but just 11 points, so those items skew toward lighter, single-point questions. Chapter 1 is tiny, at 2 questions and 2 points, but it frames the logic of everything else.
Domain 1: The Technical Test Analyst's Tasks in Risk-Based Testing
The Technical Test Analyst's Tasks in Risk-Based Testing (2 questions, 2 points)
This short chapter positions the Technical Test Analyst within the risk-based testing process, focusing on technical risks rather than purely business-domain risks.
- Which risks the Technical Test Analyst is best placed to identify and assess: performance, security, reliability, maintainability and similar technical concerns
- How risk assessment results influence the choice and depth of technical test techniques
- How this role differs from the Test Analyst, who concentrates on business-domain and user-oriented risks
Do not skip this chapter just because it is small. The two questions it supplies are among the most conceptually straightforward on the paper, and the ideas resurface in later chapters: the quality characteristics in Domain 4 are essentially the checklist of technical risk areas you will be asked to reason about. Spend a short, focused session here and connect it forward.
Domain 2: White-Box Test Techniques
White-Box Test Techniques (8 questions, 17 points)
This is the heart of what distinguishes the Technical Test Analyst from other Advanced Level roles. You must apply structure-based techniques to code and control flow, and reason about coverage.
- Statement and decision testing, including how coverage is calculated
- Condition-level techniques, including modified condition/decision coverage (MC/DC)
- Multiple condition coverage and how it relates to the other criteria
- API testing and selecting the right technique for a given situation
With 17 points from just 8 questions, white-box items are high-value, and they tend to be calculation-heavy. Expect to be handed a code snippet or a decision with several Boolean conditions and asked for the minimum number of test cases to achieve a given coverage level, or which test set achieves MC/DC. Practicing by hand matters because online delivery gives you only an on-screen calculator and a notepad.
Working MC/DC the Right Way
MC/DC trips up many candidates because it is easy to confuse with simple condition coverage. The core idea is that each condition in a decision must be shown to independently affect the decision's outcome. Take a decision such as (A and B) or C. To demonstrate independence for each condition, you identify pairs of test cases where only that condition changes and the overall outcome changes with it. A practical routine for exam day:
- List the conditions and write the full truth table for the decision.
- For each condition, find pairs of rows that differ only in that condition and produce different decision outcomes.
- Choose a minimal set of rows that covers at least one such pair per condition, noting that shared rows reduce the total.
- Check your answer against the options, since wrong choices often satisfy decision coverage but fail independence.
Work several examples until the truth-table method is automatic. This domain rewards precision, and our CTAL study guide pairs well with it for building a practice routine.
Domain 3: Static and Dynamic Analysis
Static and Dynamic Analysis (7 questions, 14 points)
This chapter covers analysis techniques that find defects without a conventional test case, plus analysis performed while the software executes.
- Static analysis: control flow analysis, data flow analysis, and the kinds of defects each exposes
- Using static analysis to evaluate maintainability, such as code complexity and coupling concerns
- Call graph analysis and what it reveals about structure and dependencies
- Dynamic analysis: detecting problems such as memory leaks, wild pointers and performance bottlenecks during execution
Questions here often present a short code listing and ask what a given analysis would report. Data flow anomalies, such as a variable being defined and never used, or used before it is defined, are classic material. Learn to scan code methodically for definition, use and kill patterns, because a careful read is faster than guessing.
The chapter also sits close to Domain 2 conceptually. Both reward comfort with code, and candidates with a development background tend to find this material more intuitive. Those without that background should budget extra reading time; the syllabus itself expects relevant programming and system-architecture knowledge.
Domain 4: Quality Characteristics for Technical Testing
Quality Characteristics for Technical Testing (13 questions, 21 points)
This chapter works through the non-functional characteristics a Technical Test Analyst is expected to test, including how to plan for them, what risks they carry and which techniques suit each.
- Security testing: identifying vulnerabilities and designing tests around them
- Reliability testing: maturity, availability, fault tolerance and recoverability
- Performance efficiency testing: load, stress and capacity concerns
- Maintainability, portability and compatibility, and the related technical concerns
- Operational profiles and how they shape realistic technical tests
The breadth is the difficulty. Each characteristic has its own vocabulary, typical risks, test approaches and metrics, and questions frequently ask you to match a scenario to the right characteristic or to choose the most appropriate test type. Build a one-page comparison per characteristic: what it means, what can go wrong, how you test it and what you measure.
Scenario questions in this chapter are where careful reading pays off. A prompt may describe a system that slows down as users are added and then ask which test type best investigates it, with plausible distractors drawn from neighboring characteristics. Practice distinguishing, for example, load from stress and recoverability from availability. For a sense of how this chapter feeds overall difficulty, read how hard the CTAL exam is.
Domain 5: Reviews
Reviews (5 questions, 13 points)
This chapter applies review techniques to technical work products, with a particular focus on code and architecture, using checklists and the Technical Test Analyst's perspective.
- The Technical Test Analyst's contribution to reviews of code and architecture
- Using review checklists to find technical defects
- Typical issues in architecture reviews, such as performance, security and maintainability concerns
- Typical issues in code reviews, such as unsafe constructs, poor structure and defects of omission
Because this chapter delivers 13 points from only 5 questions, treat each question as high stakes. Expect applied items: you may be shown a short code fragment or architectural description and asked which review finding is valid, or which checklist item would have caught a stated problem. Memorized lists help less than the ability to inspect an artifact and justify a finding.
Domain 6: Test Tools and Automation
Test Tools and Automation (10 questions, 11 points)
This chapter covers the tools a Technical Test Analyst uses and the principles for introducing and maintaining automation.
- Tool selection and the technical considerations behind adopting automation
- Test automation architecture and the concerns that determine long-term maintainability
- Tools that support specific technical testing tasks, including those used for performance, security and analysis work
- Risks and benefits of automation, and how to evaluate them for a given context
With 10 questions worth 11 points, this domain contributes many comparatively light items. That makes it a good place to collect dependable points, since the questions tend to reward clear conceptual understanding over lengthy calculation. Do not underestimate it simply because it is not code-heavy; a steady run of correct answers here offsets the harder calculation questions elsewhere.
Key Takeaway
Classify each domain by question style: Domains 2 and 3 are code-and-calculation, Domain 4 is scenario matching, Domain 5 is applied inspection, and Domain 6 is conceptual breadth. Practice each style on its own terms rather than reviewing everything the same way.
Sequencing Your Study by Domain
Rather than a generic schedule, order your study by dependency and payoff. This sample progression assumes several weeks of preparation; adapt it to your own timeline and use the CTAL cheat sheet for final review.
Risk framing and white-box foundations
- Read Domain 1 and map technical risks to the characteristics you will meet in Domain 4
- Begin statement and decision coverage by hand, using small code samples
Condition coverage and MC/DC
- Build truth tables for multi-condition decisions and identify independence pairs
- Cover API testing and technique selection
Static and dynamic analysis
- Practice spotting data flow anomalies in short listings
- Review control flow, call graph and dynamic analysis defect types
Quality characteristics
- Create one comparison sheet per characteristic
- Drill scenario questions that force you to choose between neighboring test types
Reviews, tools and full practice
- Work code and architecture review exercises, then tool and automation concepts
- Sit the official sample exams under timed, closed-book conditions
The reasoning: white-box techniques come first because they build the calculation habits that Domains 3 and 5 also lean on, while the largest chapter, quality characteristics, gets a dedicated block once the code-based material is secure. Finish with timed practice. You can run additional timed sets on our practice test site.
Syllabus Version, Fees and Booking Details
Match Your Materials to the Right Version
The relevant syllabus is the ISTQB Certified Tester Advanced Level Technical Test Analyst Syllabus v4.0, dated June 30, 2021. The official sample exams are labeled v4.2 (November 6, 2023) and are compatible with syllabus v4.0. The differing numbers do not mean the content changed; the sample exam revision simply has its own numbering. Similarly, an article dated 2026 does not imply a 2026 syllabus. When choosing a prep resource, confirm that it references this syllabus rather than an older or different one, and treat any third-party question counts or timers that conflict with the figures above as unreliable.
Eligibility and Prerequisites
You need ISTQB Foundation Level certification and sufficient practical testing experience. The ASTQB page specifies three years of experience, and AT*SQA describes it as approximately three years or equivalent. Candidates holding a prerequisite certificate from another board or provider must submit proof through their AT*SQA account before the exam. No separate degree requirement, reference requirement or mandatory training-hour gate is published; training is optional. Our page on CTAL requirements goes through qualification in more detail.
Fees, Delivery and Retakes
AT*SQA is ASTQB's official exam registrar, with delivery through Kryterion/Webassessor at testing centers or via online proctoring. The current U.S. standard exam fee is USD 249, with no published member/nonmember split, and the standard voucher price is the same for online and test-center delivery. Training costs are separate. Retakes normally require another purchase, though conditional free or discounted retake offers from ASTQB may apply. The credential is valid for life, with no renewal or continuing-education requirement. See the CTAL certification cost breakdown for budgeting and exam dates and scheduling for booking.
Frequently Asked Questions
Start with White-Box Test Techniques. The coverage calculations and MC/DC reasoning build skills that also help in Static and Dynamic Analysis and Reviews, and the chapter is worth 17 points from 8 questions.
Quality Characteristics for Technical Testing, with 13 questions and 21 points. Official percentage weights are not published, so use these question and point allocations as your guide.
You need at least 65% of the available points, which the official structure table specifies as 51 of 78. The exam has 45 multiple-choice questions and a 120-minute limit, or 150 minutes with the non-native-language extension for eligible candidates.
No. The Technical Test Analyst scope is distinct from Test Analyst and Test Management. It focuses on technical testing, including code-level techniques, analysis, technical quality characteristics and automation.
Yes. The official sample exams are version 4.2 and are compatible with syllabus v4.0. Use them for realistic practice, and pair them with extra worked exercises from our practice tests for MC/DC, code analysis and quality-characteristic scenarios.