A team is deploying a web application to a staging environment via a CD pipeline. They want to ensure the deployment is healthy before promoting to production. Which checkpoint is most appropriate in the CD pipeline?

Run unit tests on the build artifact before deployment to staging.

Manually verify the staging environment by having a QA engineer click through the main user flows.

Run smoke tests against the staging environment after deployment to verify the application responds and core functionality works.

Skip testing in staging and rely on production monitoring after the release.

A QA team needs to run end-to-end tests in CI that require a browser and a backend service. The current CI runners do not have browsers installed, and installing them manually is time-consuming. What is the most efficient way to provision the test environment?

Install the browser on each CI runner manually and document the steps.

Skip end-to-end tests in CI and run them only in a dedicated QA environment.

Run the end-to-end tests on a developer's local machine and report the results.

Use a Docker image that includes the browser and required dependencies for the test stage.

How does testing adapt to variable release schedules in a release-on-demand model?

By scheduling tests only on weekends

By using automated tests that can be run at any time

By requiring a fixed release date for all releases

By reducing test coverage to save time

What is a primary benefit of using feature toggles for testing?

They allow incomplete features to be deployed to production without being visible to users

They automatically fix bugs in the code

They replace the need for a staging environment

They eliminate the need for any testing

In a CI pipeline, how are test environments typically provisioned?

By reusing the production environment for all tests

Manually by a system administrator for each test run

By copying a developer's local machine configuration

Automatically using infrastructure as code or container images

Certified Tester Quality in DevOps

Domain 2Objective 3

QA in CI/CD Pipeline 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 33 practice questions to prepare you well beyond it. (estimate)

33questions here

7free pages

9concepts

Questions 11–15

11application · medium
A team is deploying a web application to a staging environment via a CD pipeline. They want to ensure the deployment is healthy before promoting to production. Which checkpoint is most appropriate in the CD pipeline?
Select an answer first
12application · medium
A QA team needs to run end-to-end tests in CI that require a browser and a backend service. The current CI runners do not have browsers installed, and installing them manually is time-consuming. What is the most efficient way to provision the test environment?
Select an answer first
13foundation · easy
How does testing adapt to variable release schedules in a release-on-demand model?
Select an answer first
14foundation · easy
What is a primary benefit of using feature toggles for testing?
Select an answer first
15foundation · easy
In a CI pipeline, how are test environments typically provisioned?
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.