How does a canary deployment differ from a blue-green deployment?

Canary gradually routes a small percentage of users to the new version

Canary uses two identical environments and switches traffic

Canary deploys the new version to all users at once

Canary requires feature toggles to be used

What is a key characteristic of the blue-green deployment strategy?

Two identical environments are used, with one active and one idle

Features are hidden behind configuration flags

A new version is gradually rolled out to a small subset of users

The old version is immediately deleted after deployment

How do CI, CT, and CD create fast feedback loops for agile teams?

By requiring manual testing at each stage

By using a single large test suite run at the end

By automating build, test, and deployment processes to provide rapid feedback on changes

By delaying feedback until the end of the sprint

A team is integrating automated tests into their CI pipeline. They have a mix of unit, integration, and end-to-end tests. The end-to-end tests are flaky and sometimes fail due to timing issues. What is the best way to handle these flaky tests in the CI pipeline?

Increase the timeout for the flaky tests so they pass more often.

Delete the flaky tests to keep the pipeline green.

Quarantine the flaky tests, investigate and fix them, and do not let them block the pipeline.

Run the flaky tests only on the nightly build, but keep them in the pipeline.

A team is implementing continuous testing in their CI pipeline. They have a large suite of end-to-end tests that take 30 minutes to run, and a smaller suite of unit tests that take 2 minutes. They want to provide rapid feedback to developers on every commit. Which approach best supports continuous testing?

Run the end-to-end tests only when a developer manually triggers them.

Run the unit tests on every commit and run the end-to-end tests on a nightly basis.

Run the end-to-end tests on every commit and run the unit tests on a nightly basis.

Run both the unit and end-to-end tests on every commit, accepting the 32-minute wait.

Certified Tester Advanced Level Agile Technical Tester

Domain 4Objective 1

Continuous Integration, Continuous Testing and Continuous Delivery CT-ATT Practice Questions (Page 2)

Part of the Deployment and Delivery domain, which makes up ~20% of our current practice bank. ISTQB does not publish an official question count, but from its 90-minute exam (~35–60 total, ~7–12 in this domain), expect 4–6 from this objective — we provide 29 practice questions to prepare you well beyond it. (estimate)

29questions here

6free pages

8concepts

Questions 6–10

6foundation · easy
How does a canary deployment differ from a blue-green deployment?
Select an answer first
7foundation · easy
What is a key characteristic of the blue-green deployment strategy?
Select an answer first
8foundation · easy
How do CI, CT, and CD create fast feedback loops for agile teams?
Select an answer first
9application · medium
A team is integrating automated tests into their CI pipeline. They have a mix of unit, integration, and end-to-end tests. The end-to-end tests are flaky and sometimes fail due to timing issues. What is the best way to handle these flaky tests in the CI pipeline?
Select an answer first
10application · medium
A team is implementing continuous testing in their CI pipeline. They have a large suite of end-to-end tests that take 30 minutes to run, and a smaller suite of unit tests that take 2 minutes. They want to provide rapid feedback to developers on every commit. Which approach best supports continuous testing?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CT-ATT

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