A team wants to release a new feature to a small group of internal users for validation before rolling out to all customers. They also want to be able to disable the feature quickly if a critical issue is found. Which approach best meets these requirements?

Deploy the feature behind a feature toggle and enable it only for the internal user group

Use a canary release that routes 10% of all traffic to the new version

Deploy the feature to a separate staging environment and then promote it to production

Use a blue-green deployment and switch all traffic to the new version

What is the primary purpose of a feature toggle in a DevOps environment?

To enable or disable a feature at runtime without deploying new code

To control which users can access the application

To automatically roll back a deployment when errors occur

To manage different versions of the application in separate environments

A team is adopting continuous delivery and wants to ensure that every merge to the mainline is potentially releasable. They also want to support experimentation with new features without affecting the mainline. Which combination of practices best supports this?

Forking workflow with manual merge reviews

GitFlow with long-lived feature branches

Trunk-based development with feature toggles

GitHub Flow with release branches

Certified Tester Quality in DevOps

Domain 4Objective 2

Release and Deployment Strategies CT-QDO Practice Questions (Page 2)

Part of the Domain 4: Tools and Practices in DevOps domain, which makes up ~19% 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 16 practice questions to prepare you well beyond it. (estimate)

16questions here

4free pages

3concepts

Questions 6–10

6application · medium
A team wants to release a new feature to a small group of internal users for validation before rolling out to all customers. They also want to be able to disable the feature quickly if a critical issue is found. Which approach best meets these requirements?
Select an answer first
7foundation · easy
What is the primary purpose of a feature toggle in a DevOps environment?
Select an answer first
8foundation · easy
A team wants to validate a new version of a service with a small subset of real users before exposing it to the full user base. Which release strategy is most appropriate?
Select an answer first
9application · medium
A team is adopting continuous delivery and wants to ensure that every merge to the mainline is potentially releasable. They also want to support experimentation with new features without affecting the mainline. Which combination of practices best supports this?
Select an answer first
10foundation · easy
A team uses a branching model that includes a dedicated develop branch for integration, release branches for preparing releases, and hotfix branches for urgent fixes. Which branching model does this describe?
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.

Release and Deployment Strategies CT-QDO Practice Questions (Page 2)

Questions 6–10

A team wants to release a new feature to a small group of internal users for validation before rolling out to all customers. They also want to be able to disable the feature quickly if a critical issue is found. Which approach best meets these requirements?

What is the primary purpose of a feature toggle in a DevOps environment?

A team wants to validate a new version of a service with a small subset of real users before exposing it to the full user base. Which release strategy is most appropriate?

A team is adopting continuous delivery and wants to ensure that every merge to the mainline is potentially releasable. They also want to support experimentation with new features without affecting the mainline. Which combination of practices best supports this?

A team uses a branching model that includes a dedicated develop branch for integration, release branches for preparing releases, and hotfix branches for urgent fixes. Which branching model does this describe?

Keep studying — Domain 4: Tools and Practices in DevOps