A company is adopting continuous discovery but is struggling to get stakeholders to buy in. Stakeholders are used to seeing a detailed requirements document before any development. How can the team demonstrate the value of continuous discovery to stakeholders?

Show how continuous discovery reduces the risk of building the wrong product by validating assumptions early.

Promise that continuous discovery will shorten the overall development time for every feature.

Tell stakeholders that continuous discovery is the latest industry trend and they should adopt it.

Explain that continuous discovery eliminates the need for any requirements documentation.

How does continuous testing differ from traditional testing in terms of timing?

Continuous testing is performed manually, while traditional testing is automated

Continuous testing is integrated throughout the pipeline, while traditional testing often occurs in a dedicated phase

Continuous testing is performed only after the code is deployed to production

Continuous testing is performed only at the end of each sprint, while traditional testing is continuous

A development team is transitioning from a monthly release cycle with a dedicated QA phase to a DevOps model with multiple daily deployments. The team wants to ensure that quality issues are identified as early as possible in the pipeline. Which approach best aligns with the principles of continuous testing?

Defer all testing until the end of the sprint when a complete feature set is available for a full end-to-end test.

Automate a subset of fast, reliable tests to run on every code commit, with results fed back to the development team immediately.

Run a comprehensive regression suite in a staging environment the night before each release.

Perform manual exploratory testing on the production environment after each deployment to catch any issues that automation missed.

A team has a high volume of test failures in their CI pipeline, many of which are flaky tests. Developers are starting to ignore test failures, assuming they are flaky. This is leading to real defects being missed. What is the best strategy to address this problem?

Quarantine flaky tests and require developers to fix them before they can be re-enabled.

Increase the number of test reruns to reduce the impact of flaky tests.

Ignore test failures and rely on code review to catch defects.

Remove all flaky tests from the pipeline to reduce noise.

What is the purpose of feedback loops in continuous discovery?

To reduce the need for user involvement

To finalize all requirements before development

To ensure no changes are made after initial discovery

To enable iterative improvement of product features

Certified Tester Quality in DevOps

Domain 2Objective 2

Continuous Testing and Feedback CT-QDO Practice Questions (Page 3)

Part of the Domain 2: Quality Assurance (QA) and Testing in DevOps domain, which makes up ~21% of our current practice bank. ISTQB does not publish an official question count, but from its 60-minute exam (~25–40 total, ~5–8 in this domain), expect 1–2 from this objective — we provide 39 practice questions to prepare you well beyond it. (estimate)

39questions here

8free pages

10concepts

Questions 11–15

11expert · hard
A company is adopting continuous discovery but is struggling to get stakeholders to buy in. Stakeholders are used to seeing a detailed requirements document before any development. How can the team demonstrate the value of continuous discovery to stakeholders?
Select an answer first
12foundation · easy
How does continuous testing differ from traditional testing in terms of timing?
Select an answer first
13application · medium
A development team is transitioning from a monthly release cycle with a dedicated QA phase to a DevOps model with multiple daily deployments. The team wants to ensure that quality issues are identified as early as possible in the pipeline. Which approach best aligns with the principles of continuous testing?
Select an answer first
14expert · hard
A team has a high volume of test failures in their CI pipeline, many of which are flaky tests. Developers are starting to ignore test failures, assuming they are flaky. This is leading to real defects being missed. What is the best strategy to address this problem?
Select an answer first
15foundation · easy
What is the purpose of feedback loops in continuous discovery?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CT-QDO

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-QDO” is a trademark of its owner, used for identification only.