A distributed agile team uses a shared dashboard to show test results. The dashboard updates nightly and is the primary source of status for stakeholders. During a sprint review, a stakeholder asks why a critical defect found yesterday is not visible. What is the most likely cause and the best adjustment?

The defect should have been communicated in the daily stand-up instead of on the dashboard; remove it from the dashboard to avoid duplication.

The stakeholder should not expect to see defects on the dashboard because it is for the team only; restrict access to the team.

The dashboard is not an information radiator because it is not physically displayed; replace it with a wall chart.

The nightly update is too infrequent for real-time communication; configure the dashboard to update continuously or after each test run.

A team reports a high test pass rate and high requirement coverage, but stakeholders are concerned about a recent increase in customer-reported defects. What is the most likely explanation for this discrepancy?

The requirement coverage is too high; the team should reduce it to avoid over-testing.

The metrics are being manipulated to look good, so the team should be penalized.

The customer-reported defects are not real; they are user errors.

The tests are not effective at finding defects that customers encounter, such as integration or usability issues.

A team uses a burndown chart to track remaining test effort. Mid-sprint, the burndown line is above the ideal line. What does this indicate, and what should the team do?

The team is behind schedule; investigate the cause and adjust the plan.

The team is ahead of schedule; continue as planned.

The burndown chart is only for development; use a different chart for testing.

The burndown chart is not useful for testing; ignore it.

A team is deciding which quality metrics to track for a new product. They want to balance internal quality and user-perceived quality. Which combination of metrics best achieves this?

Test execution rate and pass/fail counts

Requirement coverage and test execution rate

Defect density and escaped defects

Escaped defects and test execution rate

Certified Tester Foundation Level Agile Tester

Domain 2Objective 6

Communicating Test Status, Progress, and Product Quality CT-AT Practice Questions (Page 5)

Part of the Fundamental Agile Testing Principles, Practices, and Processes domain, which makes up ~44% of our current practice bank.

32questions here

7free pages

7concepts

Questions 21–25

21application · medium
A distributed agile team uses a shared dashboard to show test results. The dashboard updates nightly and is the primary source of status for stakeholders. During a sprint review, a stakeholder asks why a critical defect found yesterday is not visible. What is the most likely cause and the best adjustment?
Select an answer first
22expert · hard
A team reports a high test pass rate and high requirement coverage, but stakeholders are concerned about a recent increase in customer-reported defects. What is the most likely explanation for this discrepancy?
Select an answer first
23application · medium
A team uses a burndown chart to track remaining test effort. Mid-sprint, the burndown line is above the ideal line. What does this indicate, and what should the team do?
Select an answer first
24foundation · easy
Which tool is commonly used in agile to visualize the status of tasks, such as 'To Do', 'In Progress', and 'Done'?
Select an answer first
25expert · hard
A team is deciding which quality metrics to track for a new product. They want to balance internal quality and user-perceived quality. Which combination of metrics best achieves this?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CT-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. “CT-AT” is a trademark of its owner, used for identification only.

Communicating Test Status, Progress, and Product Quality CT-AT Practice Questions (Page 5)

Questions 21–25

A team reports a high test pass rate and high requirement coverage, but stakeholders are concerned about a recent increase in customer-reported defects. What is the most likely explanation for this discrepancy?

A team uses a burndown chart to track remaining test effort. Mid-sprint, the burndown line is above the ideal line. What does this indicate, and what should the team do?

Which tool is commonly used in agile to visualize the status of tasks, such as 'To Do', 'In Progress', and 'Done'?

A team is deciding which quality metrics to track for a new product. They want to balance internal quality and user-perceived quality. Which combination of metrics best achieves this?

Keep studying — Fundamental Agile Testing Principles, Practices, and Processes