A team is comparing release-level and iteration-level test planning. Which statement correctly contrasts the two?

Release planning defines the overall test strategy and risks, while iteration planning details specific test cases for each story.

Release planning focuses on daily tasks, while iteration planning focuses on the overall release scope.

Release planning is done by testers only, while iteration planning involves the whole team.

Iteration planning is done once per release, while release planning is done daily.

A team is new to Agile and believes that test planning is only the tester's job. The product owner asks the team to plan testing for the next iteration. What is the best way to address this misconception?

Skip formal test planning and rely on ad-hoc testing during the iteration.

Facilitate a collaborative session where developers, testers, and the product owner jointly define test approaches and effort.

Assign the test planning task solely to the testers, as they have the expertise.

Have the testers create a plan and then present it to the team for approval.

A team is in the middle of a sprint. A critical defect was found in a story that was supposed to be completed. The team is already at capacity. The daily stand-up is happening now. What is the most appropriate action?

Ignore the defect until the next sprint, as the team is at capacity.

Assign the defect to a tester to fix immediately, without discussing it in the stand-up.

Ask the product owner to remove a low-priority story to free up time for the defect.

Discuss the defect in the stand-up and collaboratively decide whether to reprioritize tasks or adjust the sprint scope.

Who are the typical stakeholders involved in iteration test planning?

The project manager and the test manager only.

External auditors and compliance officers.

The product owner, developers, and testers.

In risk-based test estimation, what is the primary factor that influences the amount of test effort allocated to a feature?

The personal preference of the test lead.

The level of risk associated with the feature, considering both likelihood and impact.

The order in which the feature appears in the product backlog.

The number of testers available on the team.

Certified Tester Advanced Level Agile Tester

Domain 3Objective 1

Test Planning CTAL-AT Practice Questions (Page 3)

Part of the Test Management and Test Process Improvement domain, which makes up ~24% of our current practice bank. ISTQB does not publish an official question count, but from its 90-minute exam (~35–60 total, ~8–14 in this domain), expect 2–4 from this objective — we provide 27 practice questions to prepare you well beyond it. (estimate)

27questions here

6free pages

8concepts

Questions 11–15

11application · medium
A team is comparing release-level and iteration-level test planning. Which statement correctly contrasts the two?
Select an answer first
12application · medium
A team is new to Agile and believes that test planning is only the tester's job. The product owner asks the team to plan testing for the next iteration. What is the best way to address this misconception?
Select an answer first
13expert · hard
A team is in the middle of a sprint. A critical defect was found in a story that was supposed to be completed. The team is already at capacity. The daily stand-up is happening now. What is the most appropriate action?
Select an answer first
14foundation · easy
Who are the typical stakeholders involved in iteration test planning?
Select an answer first
15foundation · easy
In risk-based test estimation, what is the primary factor that influences the amount of test effort allocated to a feature?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CTAL-AT

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by ISTQB. “CTAL-AT” is a trademark of its owner, used for identification only.