HomeCTAL-AT v2.0Practice questionsTest Management and Test Process Improvement
CTAL-AT v2.0 · ISTQB · Test Management and Test Process Improvement · Bank updated 2026-07-03

CTAL-AT v2.0 practice questions: Test Management and Test Process Improvement

5 free questions from 27 on this area · answer and explanation for each · no sign-up

These 5 questions come from the Test Management and Test Process Improvement section of our CTAL-AT v2.0 bank (27 questions on this area, which carries 18% of the real exam). Every question is original, with the correct answer explained and linked to the source it is drawn from.

Start 6 free in study mode → All CTAL-AT v2.0 sample questions
1/5 · Test Management and Test Process Improvement · easy
In the agile testing quadrants model, in which quadrant do technology-facing tests that primarily support the team, such as unit tests and component tests, belong?
AQuadrant 2
BQuadrant 4
CQuadrant 3
DQuadrant 1
Show answer & explanation
D is correct. The agile testing quadrants classify tests along two axes: business-facing vs. technology-facing, and supporting the team vs. critiquing the product. Unit and component tests are technology-facing and support the team by giving fast feedback to developers, placing them in Quadrant 1.
↗ the ISTQB Advanced Level Agile Tester Syllabus v2.0 (GA 2026-04-17) + ISTQB CTFL v4.0 as base knowledge — Test Management and Test Process Improvement
2/5 · Test Management and Test Process Improvement
A tester drafts a test charter for an exploratory testing session on a checkout discount feature: 'Explore the discount code field to find problems related to invalid, expired, and stacked codes, using boundary and negative data, within a 60-minute session.' Which element of the 5W1H structure for test charters is missing from this charter?
AWhat — the charter fails to state what feature is under test.
BWhy — the charter does not explain the mission motivating the session.
CHow — the charter does not mention which testing techniques or data will be used.
DWhere — the charter does not specify which build, environment, or test data set the session will target.
Show answer & explanation
D is correct. A well-formed test charter typically covers who, what, where, when, why, and how. This charter specifies the target (what), the mission (why), the approach (how), and the timebox (when), but never states the environment, build, or data set the session targets — the missing 'Where'.
↗ the ISTQB Advanced Level Agile Tester Syllabus v2.0 (GA 2026-04-17) + ISTQB CTFL v4.0 as base knowledge — Test Management and Test Process Improvement
3/5 · Test Management and Test Process Improvement · hard
During a release retrospective, the team reviews these trends: escaped production defects increased over the last three releases; Quadrant 1 (unit/component) coverage stayed above 90% throughout; and the proportion of exploratory testing sessions run before release fell from 30% to under 5% due to time pressure. What is the most defensible improvement recommendation for the team to adopt?
AReinstate adequate time and charters for exploratory testing sessions targeting business-facing risk areas, since high unit coverage alone is not compensating for the loss of exploratory coverage of real user scenarios and integration risks.
BIncrease Quadrant 1 unit test coverage further, since the retrospective shows unit testing is clearly ineffective and simply needs more tests written.
CStop measuring escaped defects altogether, since the metric is causing unnecessary tension in retrospectives.
DMove all exploratory testing into Quadrant 1 so it can be automated and no longer depend on tester availability.
Show answer & explanation
A is correct. K4-level retrospective analysis requires identifying which variable actually changed and correlates with the outcome. Here, unit coverage remained constant and high, while exploratory coverage dropped sharply as escaped defects rose — pointing to restoring exploratory testing time as the defensible, evidence-based improvement action rather than adding more of an already-stable practice.
↗ the ISTQB Advanced Level Agile Tester Syllabus v2.0 (GA 2026-04-17) + ISTQB CTFL v4.0 as base knowledge — Test Management and Test Process Improvement
4/5 · Test Management and Test Process Improvement
A Scrum team is two days from the end of a two-week iteration. The iteration burn-down chart shows remaining work has been flat for the last three days, while the CI/CD pipeline dashboard shows a growing number of failing automated regression tests on the main branch. As the test manager reviewing these lightweight monitoring artifacts, what is the MOST appropriate immediate action?
ATemporarily disable the failing regression tests so the CI/CD dashboard shows green, letting the team focus on finishing remaining story points before the deadline.
BWait until the sprint retrospective to raise the flat burn-down and failing pipeline, since lightweight monitoring data is meant only to feed retrospective discussion, not to trigger mid-iteration action.
CRaise the observation with the team now, since a stalled burn-down combined with a growing red build signals a likely blocked or regressing feature that should be investigated before the iteration ends.
DAdd more automated regression tests to increase code coverage, expecting that higher coverage will make the currently failing pipeline pass.
Show answer & explanation
C is correct. Lightweight monitoring tools such as burn-down charts and CI/CD dashboards are used for continuous, real-time control decisions within an iteration, not merely as retrospective input. A flat burn-down together with a degrading build is a strong combined signal of a blocked or regressing item, and the appropriate response is to surface and investigate it immediately so the team can still adapt before the iteration closes.
↗ the ISTQB Advanced Level Agile Tester Syllabus v2.0 (GA 2026-04-17) + ISTQB CTFL v4.0 as base knowledge — Test Management and Test Process Improvement
5/5 · Test Management and Test Process Improvement · hard
A test manager supports an agile team that already delivers working, tested software every sprint, and wants to improve the testing process further without disrupting the existing delivery cadence. Which approach best aligns with agile test process improvement principles?
APause the next two sprints to run a full formal assessment (e.g., a maturity-model-style review) and implement every recommended change simultaneously.
BDefer any process changes until the next major release to avoid disturbing the current sprints.
CIntroduce small, incremental changes surfaced through retrospectives, observe their effect over a sprint or two, and adapt further based on results.
DAssign responsibility for all test process improvement exclusively to the automation engineers, excluding testers and developers.
Show answer & explanation
C is correct. Agile test process improvement favors small, incremental, team-driven changes validated over short cycles rather than disruptive, big-bang overhauls. This mirrors a Kaizen/continuous-improvement mindset: identify an improvement in a retrospective, try it, inspect the outcome, and adapt. Large formal assessments and improvement plans imposed all at once conflict with the iterative rhythm of agile delivery.
↗ the ISTQB Advanced Level Agile Tester (CTAL-AT) Syllabus v2.0 — Test Management and Test Process Improvement
Practise all 27 Test Management and Test Process Improvement questions - start free → See the whole CTAL-AT v2.0 bank

Other CTAL-AT v2.0 areas

The same kind of free sample for every other section of the CTAL-AT v2.0 bank:

Test Strategy and Test Approach Challenges17 qPeople and Teams21 qShift Left26 qAgile Approaches and Test Techniques37 qTest Automation and Test Tools13 q

Study Test Management and Test Process Improvement with instant feedback

6 free questions · filter study mode by area and difficulty · error log with spaced repetition · no card, no dumps, no ads.

Create your free account →
Read next
CTFL (ISTQB) Study Plan: 4 Weeks to Pass Without a Bootcamp ISTQB CTFL: 40 questions, 60 minutes, 26 to pass, no course required. A four-week self-study plan sized to the syllabus hours. Verified 14 Sep 2026.
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.