A development team wants to deploy a new feature to production without making it visible to all users immediately. They plan to enable it for internal testers first, then gradually expand to a percentage of users, and finally to everyone. Which approach best supports this requirement?

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

Use a feature toggle with a rollout configuration that supports user targeting and percentage rollout

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

Create a separate branch for the feature and merge it later

A company wants to release a new version of its application to a small percentage of users first to gather feedback, but they also want to be able to disable the new feature quickly if a critical issue is found. They are concerned about the cost of maintaining two full environments. Which approach is most cost-effective among the listed options?

Feature toggle only, without a canary release

Canary release with a feature toggle

Rolling deployment with a feature toggle

Blue-green deployment with a feature toggle

Certified Tester Quality in DevOps

Domain 4Objective 2

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

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 11–15

11foundation · easy
A team wants to gradually roll out a new feature to a small percentage of users and monitor its impact before enabling it for everyone. Which type of feature toggle is best suited for this purpose?
Select an answer first
12application · medium
A team is using GitFlow and wants to release a new version. They have a develop branch with all the features for the next release. They want to stabilize the release and then deploy it to production. Which branch should they create from develop to prepare the release?
Select an answer first
13application · medium
A development team wants to deploy a new feature to production without making it visible to all users immediately. They plan to enable it for internal testers first, then gradually expand to a percentage of users, and finally to everyone. Which approach best supports this requirement?
Select an answer first
14expert · hard
A company wants to release a new version of its application to a small percentage of users first to gather feedback, but they also want to be able to disable the new feature quickly if a critical issue is found. They are concerned about the cost of maintaining two full environments. Which approach is most cost-effective among the listed options?
Select an answer first
15foundation · easy
Which branching model is characterized by short-lived feature branches that are merged into a single main branch frequently, often multiple times per day, to support continuous integration?
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 3)

Questions 11–15

A team wants to gradually roll out a new feature to a small percentage of users and monitor its impact before enabling it for everyone. Which type of feature toggle is best suited for this purpose?

A team is using GitFlow and wants to release a new version. They have a develop branch with all the features for the next release. They want to stabilize the release and then deploy it to production. Which branch should they create from develop to prepare the release?

A development team wants to deploy a new feature to production without making it visible to all users immediately. They plan to enable it for internal testers first, then gradually expand to a percentage of users, and finally to everyone. Which approach best supports this requirement?

Which branching model is characterized by short-lived feature branches that are merged into a single main branch frequently, often multiple times per day, to support continuous integration?

Keep studying — Domain 4: Tools and Practices in DevOps