A team is working on a legacy application with a monolithic architecture. They want to introduce test automation but have limited ability to refactor the code. The application has a complex user interface and a stable database schema. What is the most pragmatic automation strategy?

Focus on system-level tests through the UI, supplemented by a few integration tests for critical data flows

Rely on manual testing and avoid automation altogether

Attempt to write unit tests for the entire codebase, even though the code is not testable

Automate only acceptance tests and skip lower-level tests

An organization is moving from a waterfall to an Agile approach and wants to establish a sustainable test automation strategy. They have a large legacy codebase with no existing automated tests. What is the most pragmatic way to apply the test automation pyramid?

Automate only the acceptance tests and rely on manual testing for the rest

Begin with end-to-end tests to cover the main user journeys, then add unit tests later

Create a comprehensive suite of integration tests first, since they cover the most ground

Start by building a broad base of unit tests for the most critical and stable modules, then add integration and a few end-to-end tests

A team is working on a project with a very tight deadline. They have a small number of automated tests and a large amount of manual testing. The product owner wants to increase automation to improve quality, but the team is concerned about the time investment. What is the most effective way to apply the automation pyramid in this situation?

Automate end-to-end tests first to cover the main user journeys

Focus on automating the most critical unit and integration tests first, and defer end-to-end automation

Continue with manual testing and avoid automation to save time

Automate all manual tests without prioritization

A product owner wants to automate tests for a new feature that has high business risk and complex user interactions. The team has a well-established unit test suite and a moderate number of integration tests. What is the most appropriate automation approach for this feature?

Add a few end-to-end tests that cover the critical user journeys, in addition to unit and integration tests

Create a large suite of UI tests to cover every possible interaction

Rely solely on unit tests since they are fast and reliable

Skip automation and perform manual testing only

A team is developing a new feature that has a high risk of performance issues under load. They have a CI pipeline that runs tests on every commit. They want to catch performance regressions early without slowing down the pipeline significantly. What is the most appropriate automation approach?

Add a small set of integration tests that measure response times for critical paths, and run full load tests nightly

Skip performance testing until the end of the sprint

Rely on unit tests to verify performance

Run full load tests on every commit to catch all performance issues immediately

Certified Tester Advanced Level Agile Technical Tester

Domain 3Objective 2

Level of Automation CT-ATT Practice Questions (Page 1)

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

21questions here

5free pages

4concepts

Questions 1–5

1expert · hard
A team is working on a legacy application with a monolithic architecture. They want to introduce test automation but have limited ability to refactor the code. The application has a complex user interface and a stable database schema. What is the most pragmatic automation strategy?
Select an answer first
2application · medium
An organization is moving from a waterfall to an Agile approach and wants to establish a sustainable test automation strategy. They have a large legacy codebase with no existing automated tests. What is the most pragmatic way to apply the test automation pyramid?
Select an answer first
3expert · hard
A team is working on a project with a very tight deadline. They have a small number of automated tests and a large amount of manual testing. The product owner wants to increase automation to improve quality, but the team is concerned about the time investment. What is the most effective way to apply the automation pyramid in this situation?
Select an answer first
4application · medium
A product owner wants to automate tests for a new feature that has high business risk and complex user interactions. The team has a well-established unit test suite and a moderate number of integration tests. What is the most appropriate automation approach for this feature?
Select an answer first
5expert · hard
A team is developing a new feature that has a high risk of performance issues under load. They have a CI pipeline that runs tests on every commit. They want to catch performance regressions early without slowing down the pipeline significantly. What is the most appropriate automation approach?
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.