What does continuous delivery ensure about the software?

It is only released at the end of each sprint

It is automatically deployed to production after every commit

It is always in a releasable state

Which practice is a core element of continuous integration?

Using feature branches for long-lived development

Automated builds and tests run on every code commit

Manual code reviews before any integration

Deploying to production after every commit

A team of five developers works on a shared codebase. They commit code to individual feature branches and only merge to the main branch at the end of each two-week sprint. After merging, they run the full test suite, which takes several hours, and then manually deploy to a staging environment. The team wants to adopt continuous integration to get faster feedback on integration issues. Which change best aligns with the principles of CI?

Have developers merge their feature branches into the main branch at least once daily, and run the automated test suite on every merge.

Create a dedicated integration branch where developers merge their work weekly, and run tests only on that branch.

Require developers to run the full test suite locally before merging, but keep the merge to the main branch at the end of the sprint.

Keep the current merge frequency but run the full test suite in parallel on multiple machines to reduce the feedback time.

What is the primary purpose of continuous integration (CI) in agile development?

To automate the deployment of software to production

To integrate code changes frequently and detect integration issues early

To ensure that all features are complete before integration

To replace manual testing with automated testing

An agile team is experiencing long delays between writing code and receiving feedback on whether it works correctly. They want to shorten this feedback loop. Which practice would be most effective?

Have a dedicated QA team test the software manually at the end of the sprint.

Run automated unit tests on every commit and report failures to the developer immediately.

Run the full regression suite only on the nightly build.

Conduct a code review only after the entire feature is complete.

Certified Tester Advanced Level Agile Technical Tester

Domain 4Objective 1

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

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

1foundation · easy
What does continuous delivery ensure about the software?
Select an answer first
2foundation · easy
Which practice is a core element of continuous integration?
Select an answer first
3application · medium
A team of five developers works on a shared codebase. They commit code to individual feature branches and only merge to the main branch at the end of each two-week sprint. After merging, they run the full test suite, which takes several hours, and then manually deploy to a staging environment. The team wants to adopt continuous integration to get faster feedback on integration issues. Which change best aligns with the principles of CI?
Select an answer first
4foundation · easy
What is the primary purpose of continuous integration (CI) in agile development?
Select an answer first
5application · medium
An agile team is experiencing long delays between writing code and receiving feedback on whether it works correctly. They want to shorten this feedback loop. Which practice would be most effective?
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.