A team wants to enforce a minimum quality level for all pull requests. They decide to implement quality gates that must pass before a pull request can be merged. Which combination of checks would form an effective set of quality gates?

A requirement that the pull request author approves their own changes.

Manual code review by a single senior developer.

A check that the build succeeds, but no tests are run.

Automated unit tests, code coverage threshold, and static analysis.

A team is running a continuous discovery experiment to test two different onboarding flows. They measure user engagement for each flow and find that Flow A performs significantly better. What should the team do with this feedback to support iterative improvement?

Abandon the feature because the experiment did not test all possible flows.

Adopt Flow B because it was the original idea.

Run the experiment again with the same parameters to confirm the result.

Adopt Flow A and continue to test and refine it based on further feedback.

How do testing and QA contribute to feedback loops in continuous discovery?

By providing data on user behavior and feature viability

By focusing only on internal team opinions

By preventing any changes to the product

By eliminating the need for iteration

Which of the following is an example of a quality gate applied to a pull request?

The pull request must be open for at least 24 hours

The developer must run tests locally

The code must be reviewed by at least two senior developers

What is continuous discovery in a DevOps context?

A one-time activity to define all requirements before development

A method for discovering defects in production

A process of testing all possible user scenarios

A process of continuously gathering feedback and validating assumptions about product features

Certified Tester Quality in DevOps

Domain 2Objective 2

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

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 16–20

16application · medium
A team wants to enforce a minimum quality level for all pull requests. They decide to implement quality gates that must pass before a pull request can be merged. Which combination of checks would form an effective set of quality gates?
Select an answer first
17application · medium
A team is running a continuous discovery experiment to test two different onboarding flows. They measure user engagement for each flow and find that Flow A performs significantly better. What should the team do with this feedback to support iterative improvement?
Select an answer first
18foundation · easy
How do testing and QA contribute to feedback loops in continuous discovery?
Select an answer first
19foundation · easy
Which of the following is an example of a quality gate applied to a pull request?
Select an answer first
20foundation · easy
What is continuous discovery in a DevOps context?
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.