What is the primary role of continuous testing in a DevOps pipeline?

To ensure that all tests are executed only in the production environment

To replace all manual testing with automated tests

To provide fast, ongoing feedback on the quality of the software

To document test results for compliance audits

What is a common way for testers to contribute to a pull request review?

By merging the pull request without review

By writing all the code in the PR

By adding comments on test results and code changes

By approving the PR without running any tests

In a pull request, a developer has added a new feature and written unit tests. A reviewer notices that the test coverage is low for the new code. How should the testing activities and results be shared and reviewed within the pull request process to support collaborative quality assurance?

The reviewer should reject the pull request and close it without discussion.

The developer should merge the pull request and add the tests in a future pull request.

The reviewer should merge the pull request and file a bug report for the missing tests.

The reviewer should leave a comment on the pull request requesting additional tests, and the developer should add them before merging.

When in the development workflow does pull request testing occur?

Only during the annual regression testing

After the code is merged to the main branch

Before the code is merged, as part of the pull request review

Only after the release is deployed

A team is designing a CI/CD pipeline for a microservices application. They want to ensure that integration issues between services are caught as early as possible. Where in the pipeline should they place the integration tests to best achieve this?

In the build stage, after compiling the code but before running unit tests.

In the deployment stage, after the services are deployed to a production-like environment.

In the post-deployment stage, using production monitoring to detect integration failures.

In the test stage, after deploying the services to a shared environment that mimics production.

Certified Tester Quality in DevOps

Domain 2Objective 2

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

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 1–5

1foundation · easy
What is the primary role of continuous testing in a DevOps pipeline?
Select an answer first
2foundation · easy
What is a common way for testers to contribute to a pull request review?
Select an answer first
3application · medium
In a pull request, a developer has added a new feature and written unit tests. A reviewer notices that the test coverage is low for the new code. How should the testing activities and results be shared and reviewed within the pull request process to support collaborative quality assurance?
Select an answer first
4foundation · easy
When in the development workflow does pull request testing occur?
Select an answer first
5application · medium
A team is designing a CI/CD pipeline for a microservices application. They want to ensure that integration issues between services are caught as early as possible. Where in the pipeline should they place the integration tests to best achieve this?
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.