An Agile team is developing a microservices-based application. They want to validate performance early but are concerned that running full load tests in the CI pipeline will slow down feedback. What is the best approach?

Run a small-scale performance test as part of CI and a full load test on a scheduled basis

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

Wait until the system is feature-complete before running any performance tests

Use a unit testing framework to test performance of individual services

An Agile team is evaluating two test automation tools. Tool X has a steep learning curve but offers powerful scripting and integrates well with their CI. Tool Y is easy to use but has limited integration and requires manual test execution. The team has two developers who are new to automation. Which tool should they choose?

Tool X, because integration with CI is more important than ease of use

Tool X, because powerful scripting is essential for complex test scenarios

Tool Y, because manual test execution is acceptable in Agile

Tool Y, because the team can start automating quickly and learn as they go

How do session-based test management tools support exploratory testing?

By helping testers structure and document their exploratory sessions

By automatically generating test cases from user stories

By executing all tests without human intervention

By replacing the need for testers to think creatively

Why are performance testing tools used early in Agile development?

To validate non-functional requirements and identify performance issues before they become costly

To automatically fix performance bottlenecks

To generate user stories for performance requirements

To replace the need for functional testing

In a CI/CD pipeline, where do automated tests typically run?

After the build is created and before deployment to production

Only when a defect is reported by a user

Only after the product is released to customers

Only in the developer's local environment

Certified Tester Advanced Level Agile Tester

Domain 6Objective 2

Test Tools in Agile Software Development CTAL-AT Practice Questions (Page 4)

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

39questions here

8free pages

10concepts

Questions 16–20

16expert · hard
An Agile team is developing a microservices-based application. They want to validate performance early but are concerned that running full load tests in the CI pipeline will slow down feedback. What is the best approach?
Select an answer first
17expert · hard
An Agile team is evaluating two test automation tools. Tool X has a steep learning curve but offers powerful scripting and integrates well with their CI. Tool Y is easy to use but has limited integration and requires manual test execution. The team has two developers who are new to automation. Which tool should they choose?
Select an answer first
18foundation · easy
How do session-based test management tools support exploratory testing?
Select an answer first
19foundation · easy
Why are performance testing tools used early in Agile development?
Select an answer first
20foundation · easy
In a CI/CD pipeline, where do automated tests typically run?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CTAL-AT

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