About the Exam

This ISTQB Advanced Level certification covers technical testing skills used in software testing, including risk-based testing, white-box testing, static and dynamic analysis, non-functional testing, and test automation. It is aimed at people involved in testing and related roles such as test analysis, test consulting, and software development. Passing demonstrates knowledge of technical testing techniques and the ability to apply them to quality risks, reviews, and automation tasks.

Exam Topics

  • The Technical Test Analyst's Tasks in Risk-Based Testing2%
  • White-Box Test Techniques25%
  • Static and Dynamic Analysis15%
  • Quality Characteristics for Technical Testing29%
  • Reviews14%
  • Test Tools and Automation15%

How to Use This Practice Exam

  1. Browse — Read each question, select your answer, and reveal the explanation.
  2. Exam Mode — Simulate real exam conditions with a timed session and score report.
  3. Learn Mode — Spaced repetition schedules questions you struggle with for long-term retention.

Download the Full Exam PDF

Get every question and answer in a clean, printable PDF built for offline study. Purchase once, keep permanent access, and re-download the latest version anytime.

Last updated December 2, 2025 at 8:56 AM

Topic filter
Retired questions
Question sort

QuestionQ1

Quality Characteristics for Technical Testing

In an embedded software project, software maintainability is considered critical. Static analysis has been chosen for every delivered software component.

Which of the following metrics is not a maintainability metric typically used with static analysis?

  • A Number of Lines of Code (LOC)
  • B Number of Function Calls
  • C Mean Time Between Failures
  • D Comment Frequency
Explanation

Mean Time Between Failures (MTBF) is a reliability metric based on failures occurring during operation over time. Static analysis assesses source-code characteristics such as size, structural complexity, dependencies, and documentation, rather than operational failure intervals.

Community Discussion

No comments yet. Be the first to start the discussion!

QuestionQ2

Quality Characteristics for Technical Testing

Consider this fault attack:

  • Force every possible incoming error from the software/operating-system interfaces to the application.

Which kind of failure are you looking for when using this attack?

  • A Application crashes when unsupported characters are pasted into an input field.
  • B Application crashes when the network is unavailable.
  • C Application crashes due to a lack of portability.
  • D Application miscalculates total monthly balance due on credit cards.
Explanation

Applications should handle errors returned by software and operating-system interfaces without terminating unexpectedly. A network outage produces an interface-level error; an application crash in that condition demonstrates inadequate error handling.

Community Discussion

No comments yet. Be the first to start the discussion!

QuestionQ3

Test Tools and Automation

Which of the following is not a common problem with traditional capture/playback test automation?

  • A Difficult to maintain when software changes.
  • B Recorded scripts are difficult to maintain by non-technical persons.
  • C Data and actions are mixed in the recorded script.
  • D Execution of the recorded script is difficult outside office hours.
Explanation

Capture/playback scripts are typically brittle when the application changes, often combine test data and actions, and can require technical skill to maintain. They can be scheduled or run unattended, so execution outside office hours is not an inherent issue.

Community Discussion

No comments yet. Be the first to start the discussion!

QuestionQ4

White-Box Test Techniques

A component has been assessed during a risk assessment and rated as highly critical. Which of the following white-box testing techniques delivers the highest level of coverage and could therefore be used to test this component?

  • A Decision testing
  • B Statement testing
  • C Multiple condition testing
  • D Modified condition/decision testing
Explanation

Multiple condition testing covers all possible combinations of individual condition outcomes within each decision. It is more exhaustive than MC/DC, decision testing, and statement testing, making it the listed technique with the highest coverage level for a highly critical component.

Community Discussion

No comments yet. Be the first to start the discussion!

QuestionQ5

Quality Characteristics for Technical Testing

Which of the following is a valid justification for including security testing in a test approach?

  • A There is a threat of unauthorized copying of applications or data.
  • B To provide measurements from which an overall level of availability can be obtained.
  • C To evaluate the ability of a system to handle peak loads at or beyond the limits of its anticipated or specified workloads.
  • D Software changes will be frequent after it enters production.
Explanation

Security testing evaluates whether applications and data are protected from unauthorized actions, including unauthorized copying. This addresses confidentiality and other security risks.

Community Discussion

No comments yet. Be the first to start the discussion!
Know a question that should be here? Contribute to this exam
Back home