A tester is writing test cases for a new feature. The requirement document has been updated several times. To ensure traceability, what should the tester do?

Link each test case to the specific requirement version it validates.

Link test cases to the requirement title only, without version information.

Do not link test cases until the feature is released.

Link test cases to the latest version of the requirement document at the end of the sprint.

In a DevOps pipeline, a change to a requirement triggers a build. The team wants to automatically run only the tests that are affected by this change to save time. What is the best way to achieve this?

Use traceability links to map requirements to test cases, and configure the pipeline to select tests based on the changed requirement.

Use code coverage data to determine which tests to run.

Manually review the change and decide which tests to run, then update the pipeline configuration.

Run all tests in the regression suite every time to ensure nothing is missed.

A team is migrating from a monolithic application to microservices. They have a single traceability matrix for the monolith. After migration, they need to maintain traceability for each microservice. What is the best approach?

Keep the single traceability matrix and add microservice names as tags.

Create separate traceability matrices for each microservice and link them to the overall system requirements.

Use a single matrix but only include high-level requirements, ignoring microservice details.

Delete the old matrix and create a new one only for the microservices.

A DevOps team maintains test cases in a spreadsheet, test data in a shared drive, and automation scripts in a Git repository. After a production incident, they struggle to identify which test cases covered the affected feature. The team wants to establish a single source of truth for testware to improve traceability. Which approach best achieves this?

Store test cases in the same Git repository as the application code, but keep test data in the shared drive.

Use a test management tool that imports test cases from the spreadsheet and exports reports to the shared drive.

Create a shared spreadsheet that lists all test cases and their associated requirements.

Migrate all testware artifacts into a single version-controlled repository and link them to requirements.

During a sprint, a product owner changes a requirement. The team wants to know which test cases are affected and whether any new tests are needed. What should they use?

The traceability matrix that maps requirements to test cases.

The test execution report from the last run.

The code coverage report from the CI pipeline.

Certified Tester Quality in DevOps

Domain 3Objective 1

Testware Management and Traceability CT-QDO Practice Questions (Page 4)

Part of the Domain 3: Automated and Manual Tasks in DevOps domain, which makes up ~21% of our current practice bank. ISTQB does not publish an official question count, but from its 60-minute exam (~25–40 total, ~5–8 in this domain), expect 1–2 from this objective — we provide 28 practice questions to prepare you well beyond it. (estimate)

28questions here

6free pages

5concepts

Questions 16–20

16application · medium
A tester is writing test cases for a new feature. The requirement document has been updated several times. To ensure traceability, what should the tester do?
Select an answer first
17application · medium
In a DevOps pipeline, a change to a requirement triggers a build. The team wants to automatically run only the tests that are affected by this change to save time. What is the best way to achieve this?
Select an answer first
18expert · hard
A team is migrating from a monolithic application to microservices. They have a single traceability matrix for the monolith. After migration, they need to maintain traceability for each microservice. What is the best approach?
Select an answer first
19application · medium
A DevOps team maintains test cases in a spreadsheet, test data in a shared drive, and automation scripts in a Git repository. After a production incident, they struggle to identify which test cases covered the affected feature. The team wants to establish a single source of truth for testware to improve traceability. Which approach best achieves this?
Select an answer first
20application · medium
During a sprint, a product owner changes a requirement. The team wants to know which test cases are affected and whether any new tests are needed. What should they use?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CT-QDO

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