A team wants to implement continuous delivery but is concerned about the reliability of their automated tests. They have a high rate of flaky tests in the pipeline. Which approach best addresses this concern while maintaining the goal of continuous delivery?

Move all tests to a nightly job so they do not block releases.

Increase the number of test reruns to reduce flakiness.

Quarantine flaky tests and fix them before relying on the pipeline for release decisions.

Ignore flaky tests and proceed with releases based on the tests that pass.

What is the primary implication of Continuous Deployment for the testing process?

Testing must be highly automated and comprehensive in the pipeline, as every change that passes tests is automatically released to production.

Testing is limited to unit tests only, as integration and system tests are too slow for the pipeline.

Testing becomes less important because deployments are automated and fast.

Testing is performed only by the operations team after deployment to production.

Which statement correctly differentiates Continuous Deployment from Continuous Delivery?

Continuous Deployment requires a manual approval step before production, while Continuous Delivery does not.

Continuous Deployment automates the release to production, while Continuous Delivery leaves the final deployment as a manual decision.

Continuous Deployment is only applicable to mobile apps, while Continuous Delivery is for web applications.

Continuous Deployment focuses on testing, while Continuous Delivery focuses on deployment.

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

To replace the need for any manual testing, as automation can cover all scenarios.

To provide fast and consistent feedback on the quality of code changes at each stage of the pipeline.

To ensure that all tests are run only at the end of the development cycle before release.

To generate test data and documentation automatically, saving time for testers.

How do cross-functional teams impact the testing process in a DevOps environment?

They eliminate the need for a separate testing phase, as developers write all the tests.

They enable testing to be integrated throughout the development process, with testers, developers, and operations working together.

They slow down testing because team members have conflicting priorities.

They require testers to also perform operations tasks, reducing the time available for testing.

Certified Tester Agile Test Leadership at Scale

Domain 4Objective 1

Important DevOps Practices CT-ATLAS Practice Questions (Page 5)

Part of the Organizational Test Strategy in a Value-Driven Organization domain, which makes up ~23% of our current practice bank. ISTQB does not publish an official question count, but from its 120-minute exam (~50–80 total, ~12–18 in this domain), expect 2–4 from this objective — we provide 34 practice questions to prepare you well beyond it. (estimate)

34questions here

7free pages

10concepts

Questions 21–25

21expert · hard
A team wants to implement continuous delivery but is concerned about the reliability of their automated tests. They have a high rate of flaky tests in the pipeline. Which approach best addresses this concern while maintaining the goal of continuous delivery?
Select an answer first
22foundation · easy
What is the primary implication of Continuous Deployment for the testing process?
Select an answer first
23foundation · easy
Which statement correctly differentiates Continuous Deployment from Continuous Delivery?
Select an answer first
24foundation · easy
What is the primary role of automated testing in a DevOps pipeline?
Select an answer first
25foundation · easy
How do cross-functional teams impact the testing process in a DevOps environment?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CT-ATLAS

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