CTAL-AT v2.0 · ISTQB · Updated August 2026
CTAL-AT v2.0 practice questions
Original & expert-reviewed · explanation for every option · no dumps
Practise CTAL-AT v2.0 with original, expert-reviewed questions — each with an explanation for every option, linked to the source, across the full exam blueprint. No dumps, no ads, 6 free to start.
Free: 6 questions in study mode, no card. Full CTAL-AT v2.0 bank with mock exams and the error log: $15 one-time, or every exam with All-Access for $19/mo or $119/yr.
What makes these different from dumps
📚 An explanation for every option
Not just the right answer — why each wrong option is wrong, linked to the source. Wrong answers teach the most.
⏱️ Real-format timed mocks
Sit full 40-question, 90-minute exams and get a readiness report by area — know when you're ready.
↻ Spaced-repetition error log
Every miss comes back on a 1 → 3 → 7 → 16-day schedule, so the fixes actually stick.
🔖 Original & reviewed
Every question is written to test the concepts and reviewed before it ships — never copied or leaked “dumps”.
Try 10 real CTAL-AT v2.0 questions — free, no sign-up
A representative slice of the bank: every syllabus chapters, mixed difficulty (hard ones included). Answers are one tap away — no email wall.
1/10 · Test Strategy and Test Approach Challenges
The Agile Testing Quadrants model (Q1-Q4) is commonly used to help an agile team decide which test types to plan for a story. According to this model, which quadrant contains tests that are business-facing and primarily support the team by guiding development?
AQ4 - performance, security and other quality-attribute tests, technology-facing, used to critique the product.
BQ1 - unit and component tests, technology-facing, used to support the team.
CQ3 - exploratory and usability testing, business-facing, used to critique the product.
DQ2 - functional/acceptance tests and story examples, business-facing, used to support the team.
Show answer & explanation
2/10 · People and Teams
What is the primary goal of the whole-team approach as described for agile testing?
ATo keep testing as the sole responsibility of a dedicated, independent test team that works separately from developers and business representatives.
BTo remove the need for testers entirely because developers are expected to write and execute all automated tests themselves.
CTo make quality a shared responsibility of the whole agile team, with testers contributing their specialized skills continuously throughout development rather than only at the end.
DTo transfer full ownership of defining and executing acceptance tests to business representatives, without tester involvement.
Show answer & explanation
3/10 · Test Management and Test Process Improvement
Which statement correctly distinguishes test planning at the iteration level from test planning at the release level in an agile project?
AIteration-level planning replaces the need for a release-level test strategy, because agile teams work exclusively from the sprint backlog.
BRelease-level planning is performed only once, at project kickoff, and is never revisited once the first iteration starts.
CRelease-level planning is the sole responsibility of the Scrum Master and excludes input from testers.
DIteration-level planning focuses on the testing tasks needed to deliver the committed backlog items within the current sprint, while release-level planning addresses overall test strategy, staffing, environments, and regression risk across multiple iterations.
Show answer & explanation
4/10 · Shift Left
In shift-left testing practices described in the Advanced Level Agile Tester syllabus, Behaviour-Driven Development (BDD) scenarios written in Given-When-Then format are primarily valued because they:
AGuarantee full regression coverage because every BDD scenario is automated by definition.
BAre written exclusively by testers after development is complete to describe found defects.
CServe as both executable specifications and living documentation that stay synchronized with the behavior of the system.
DReplace the need for any acceptance criteria once a story has been groomed by the product owner.
Show answer & explanation
5/10 · Agile Approaches and Test Techniques
In exploratory testing, the mnemonic SFDIPOT (Structure, Function, Data, Interfaces, Platform, Operations, Time) is primarily used to...
ASystematically identify product elements/dimensions to guide coverage and idea generation during exploration
BDefine oracle heuristics for judging whether an observed behavior is a bug
CPrioritize which regression test cases to re-execute before a release under time pressure
DStructure a debriefing conversation after an exploratory testing session has ended
Show answer & explanation
6/10 · Test Automation and Test Tools
In test-first approaches such as Acceptance Test-Driven Development (ATDD), which sequence best reflects the recommended flow of activities for a single user story before coding begins?
ADistill acceptance tests from the existing automated regression suite, discuss them with the product owner after release, then develop supporting code.
BDemo the feature to stakeholders first to gather feedback, then discuss and distill the acceptance criteria retrospectively.
CDevelop the code first, then discuss the acceptance criteria with the team, and finally automate the tests once the feature is complete.
DDiscuss the story with business and technical stakeholders, distill concrete examples into acceptance tests, then develop the code guided by those tests.
Show answer & explanation
7/10 · Test Strategy and Test Approach Challenges
A tester applies the RCRCRC heuristic to prioritize which existing automated tests to re-run in a time-boxed regression cycle after a defect fix. Which of the following is NOT one of the criteria represented by RCRCRC?
ARequirements-traceable - areas that have a documented requirement ID linking them to a specification.
BChronic - areas that have a history of repeated failures.
CConfiguration sensitive - areas affected by environment or configuration changes.
DRecent - areas that were recently added or changed.
Show answer & explanation
8/10 · People and Teams
Which of the following is an example of a synchronous communication channel commonly relied upon in agile teams to get fast feedback on testing information?
AA daily stand-up meeting where a tester raises exploratory or mob testing findings for immediate team discussion.
BAn email summarizing the week's test status sent to stakeholders.
CA recorded video walkthrough of a test session that team members watch later.
DA wiki page documenting test charters, kept for later reference by anyone who needs it.
Show answer & explanation
9/10 · Test Strategy and Test Approach Challenges · hard
In a program with four agile teams, each owning one microservice in a customer's 'registration -> identity verification -> funding' journey, each team's own service is well tested, but journey-level defects are repeatedly found only in late-stage staging, close to release. Which change to the test strategy would a test manager be best justified in recommending?
AIntroduce continuous, incremental cross-team end-to-end and integration testing throughout each iteration (e.g., shared contract tests, an always-updated integration environment, cross-team test charters), instead of deferring journey-level testing to a single late-stage phase.
BRequire each team to add more unit tests for its own microservice, since unit-level defects are the most likely cause of a journey-level failure discovered in staging.
CAccept the late discoveries as an unavoidable cost of using microservices and continue testing only within each service's boundary.
DMerge the four teams into a single team so that only one group is responsible for the whole journey.
Show answer & explanation
10/10 · Test Strategy and Test Approach Challenges · hard
A team releasing multiple times per day has grown its automated regression suite over two years. Many UI-level tests are now flaky, intermittently failing for reasons unrelated to real defects, and developers have started ignoring pipeline failures altogether. Which regression strategy should the team's test lead justify to leadership?
AIdentify and fix or remove flaky/duplicate tests (test smells), rebuild a fast, risk-based subset per RCRCRC for every commit, and run a fuller regression suite on a lower-frequency schedule (e.g., nightly).
BContinue running the entire existing suite, including flaky tests, on every commit, since removing any existing test represents a permanent loss of coverage.
CInstruct developers to automatically re-run any failing test up to five times and only fail the build if all five attempts fail, without further investigating why tests are flaky.
DRemove all UI-level tests permanently and replace end-to-end regression coverage exclusively with unit tests.
Show answer & explanation
Practice by knowledge area
Five more free questions for each section of the CTAL-AT v2.0 bank, drawn from that area only, with the answer explained and linked to the source:
Covering every syllabus chapters
The bank spans the whole CTAL-AT v2.0 blueprint, weighted toward what the exam tests most:
Start practising CTAL-AT v2.0 free
6 free questions in study mode · no card · full CTAL-AT v2.0 bank: $15 one-time · no dumps, no ads.
Start CTAL-AT v2.0 free →
CTAL-AT v2.0 practice — FAQ
What happened to CTFL-AT — is CTAL-AT v2.0 its replacement?
Yes — ISTQB is retiring the 2014 Foundation-level Agile Tester (exams sunset May 2027) and released CTAL-AT v2.0 in May 2026 as its flagship agile testing credential. Existing CTFL-AT certificates stay valid, but there's no automatic upgrade.
How hard is the CTAL-AT v2.0 exam?
It's Advanced Level: 40 questions worth 52 points, with K3/K4 scenario items (apply and analyze) worth extra points — exploratory heuristics, test charters, quadrants and shift-left practices. Noticeably deeper than the old Foundation-level exam.
Do I need CTFL before CTAL-AT v2.0?
Yes — a valid CTFL certificate (v4.0 or earlier) is a formal entry criterion; agile work experience is recommended on top.
How many questions is the CTAL-AT v2.0 exam and how long is it?
40 multiple-choice questions worth 52 points (K3/K4 scenario questions carry more points) in 90 minutes (+25% for non-native English speakers).
What is the passing score for CTAL-AT v2.0?
The passing score is 65% — 34 out of 52 points. Aim for a consistent 80–85% on realistic practice exams before booking.
What is the CTAL-AT v2.0 pass rate?
ISTQB does not publish official pass rates, so any exact percentage quoted online is unverified. The readiness signal that actually predicts passing: consistently holding 80–85% on realistic, full-length practice exams before you book.
What are the CTAL-AT v2.0 eligibility requirements?
ISTQB CTFL certificate required (any version). About 6 months of agile development or testing experience is strongly recommended, not mandatory.
How much does CTAL-AT v2.0 cost?
Set per member board — Advanced Level exams typically run ~$200–300 (e.g. ~$249 in the US via AT*SQA). As a 2026 release, board pricing is still rolling out — verify locally.
How long should I study for CTAL-AT v2.0?
For most candidates, ISTQB mandates ≥13 hours of accredited instruction; total prep commonly lands at 30–60 hours. What matters most is practising questions and analysing why each option is right or wrong — not just reading.
Does the CTAL-AT v2.0 certification need recertification?
None — ISTQB certificates do not expire.
Are ExamDeck's CTAL-AT v2.0 questions exam dumps?
No — every question is original, written to test the concepts and reviewed before it ships, with an explanation linked to the source for every option. Dumps are stale, often wrong, and against ISTQB's policies.
ExamDeck is an independent study tool, not affiliated with, endorsed by, or sponsored by ISTQB. CTAL-AT v2.0 and related marks are trademarks of their respective owners, used for identification only. Exam facts checked against official ISTQB materials (as of August 2026); always confirm current details with the vendor before booking.