How does Infrastructure as Code (IaC) enable consistent and repeatable environments for testing?

By using the same versioned configuration files to provision test, staging, and production environments, reducing environment drift.

By requiring a dedicated team to manually set up each environment to ensure they are unique.

By allowing testers to manually adjust the environment configuration after each test run.

By using a different configuration for each environment to test for configuration-specific bugs.

In the context of DevOps principles, what is the primary purpose of 'automation' as it relates to testing?

To replace all manual testing activities with automated scripts, eliminating the need for human testers.

To ensure that all testing is performed by the operations team to reduce the workload on developers.

To increase the speed and consistency of testing by using tools to execute repetitive checks, allowing for faster feedback on code changes.

To automate the creation of test documentation so that testers can spend more time on manual testing.

What is the key difference between 'monitoring' and 'observability'?

Monitoring is only for infrastructure, while observability is only for applications.

Monitoring is a manual process, while observability is automated.

Monitoring is used in production, while observability is used in testing.

Monitoring is about collecting predefined metrics, while observability is about the ability to ask arbitrary questions about the system's behavior using its outputs.

What is the primary goal of Continuous Integration (CI) in a DevOps environment?

To create a detailed test plan before any code is written to ensure full coverage.

To deploy code to production automatically after every commit.

To integrate code changes from multiple developers into a shared repository frequently, allowing early detection of integration issues.

To ensure that all testing is performed manually before code is integrated.

What is the core idea behind 'shift-left' testing?

Moving testing activities earlier in the development lifecycle, such as during requirements analysis and design.

Moving testing activities to later in the development lifecycle to ensure the software is fully built.

Shifting the focus of testing from functional to non-functional requirements.

Shifting the responsibility of testing from the QA team to the operations team.

Certified Tester Agile Test Leadership at Scale

Domain 4Objective 1

Important DevOps Practices CT-ATLAS Practice Questions (Page 1)

Part of the Organizational Test Strategy in a Value-Driven Organization domain, which makes up ~23% of our current practice bank. ISTQB does not publish an official question count, but from its 120-minute exam (~50–80 total, ~12–18 in this domain), expect 2–4 from this objective — we provide 34 practice questions to prepare you well beyond it. (estimate)

34questions here

7free pages

10concepts

Questions 1–5

1foundation · easy
How does Infrastructure as Code (IaC) enable consistent and repeatable environments for testing?
Select an answer first
2foundation · easy
In the context of DevOps principles, what is the primary purpose of 'automation' as it relates to testing?
Select an answer first
3foundation · easy
What is the key difference between 'monitoring' and 'observability'?
Select an answer first
4foundation · easy
What is the primary goal of Continuous Integration (CI) in a DevOps environment?
Select an answer first
5foundation · easy
What is the core idea behind 'shift-left' testing?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CT-ATLAS

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