A company is migrating from a monolithic application to microservices. They want to release new versions of individual services independently without affecting the entire system. They also want to minimize the risk of a bad release impacting all users. Which release strategy is most appropriate?

Feature toggle to enable new microservices

Blue-green deployment for the entire system

Rolling deployment for the entire system

Canary release for each microservice

A company wants to release a new version of its mobile app backend that is not backward-compatible with the current client version. They need to ensure that users who have not updated their app are not affected. Which strategy is most appropriate?

Use a rolling deployment to gradually replace the backend instances

Use a feature toggle to enable the new backend only for clients that support it

Use a canary release that routes a small percentage of all traffic to the new backend

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

A team is using feature toggles to manage a new feature. They want to ensure that the toggle is removed from the codebase after the feature is fully released to avoid technical debt. However, they also want to be able to quickly disable the feature if a problem is discovered after full rollout. Which approach best balances these concerns?

Remove the toggle after a stabilization period and rely on the release strategy for rollback

Keep the toggle permanently to allow instant disablement at any time

Keep the toggle but document it as deprecated

Remove the toggle immediately after the feature is released to production

A team wants to minimize downtime during a database schema change that is not backward-compatible. They plan to deploy a new application version that works with the new schema, but they need to be able to roll back quickly if issues arise. Which release strategy is most appropriate?

Feature toggle to hide the new feature

Rolling deployment with in-place schema updates

Canary release with a forward-only migration

Blue-green deployment with a database migration that is reversible

Certified Tester Quality in DevOps

Domain 4Objective 2

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

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

1expert · hard
A company is migrating from a monolithic application to microservices. They want to release new versions of individual services independently without affecting the entire system. They also want to minimize the risk of a bad release impacting all users. Which release strategy is most appropriate?
Select an answer first
2application · hard
A company wants to release a new version of its mobile app backend that is not backward-compatible with the current client version. They need to ensure that users who have not updated their app are not affected. Which strategy is most appropriate?
Select an answer first
3expert · hard
A team is using feature toggles to manage a new feature. They want to ensure that the toggle is removed from the codebase after the feature is fully released to avoid technical debt. However, they also want to be able to quickly disable the feature if a problem is discovered after full rollout. Which approach best balances these concerns?
Select an answer first
4application · hard
A team wants to minimize downtime during a database schema change that is not backward-compatible. They plan to deploy a new application version that works with the new schema, but they need to be able to roll back quickly if issues arise. Which release strategy is most appropriate?
Select an answer first
5foundation · easy
A team wants to deploy a new version of an application with minimal risk by keeping the previous version fully operational and switching all traffic only after the new version passes verification. Which release strategy 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 1)

Questions 1–5

A company is migrating from a monolithic application to microservices. They want to release new versions of individual services independently without affecting the entire system. They also want to minimize the risk of a bad release impacting all users. Which release strategy is most appropriate?

A company wants to release a new version of its mobile app backend that is not backward-compatible with the current client version. They need to ensure that users who have not updated their app are not affected. Which strategy is most appropriate?

A team wants to minimize downtime during a database schema change that is not backward-compatible. They plan to deploy a new application version that works with the new schema, but they need to be able to roll back quickly if issues arise. Which release strategy is most appropriate?

A team wants to deploy a new version of an application with minimal risk by keeping the previous version fully operational and switching all traffic only after the new version passes verification. Which release strategy does this describe?

Keep studying — Domain 4: Tools and Practices in DevOps