What is essential for maintaining traceability links over time?

Using only manual processes to track links

Updating the links whenever the test basis or testware changes

Storing the links in a separate, unversioned document

Creating the links once and never changing them

A team has a traceability matrix that is maintained manually. After a major refactoring, many test cases are obsolete, but the matrix still shows them as linked to requirements. The team wants to clean up the matrix and ensure it reflects the current state. What is the best approach?

Delete the entire traceability matrix and start over.

Manually review each test case and remove those that are no longer relevant.

Use an automated tool to analyze the code and test cases to identify obsolete links, then update the matrix.

Keep the matrix as is and only add new links for new requirements.

Why is establishing a single source of truth for testware important in a DevOps environment?

It restricts access to testware to only the quality assurance team

It guarantees that all test defects are automatically resolved

It ensures that all team members work from the same, current version of test artifacts

It eliminates the need for test automation by centralizing manual test cases

A team is adopting a trunk-based development model with frequent merges to the main branch. They want to maintain traceability between requirements and tests, but the fast pace makes it difficult to update links manually. What is the best way to maintain traceability in this environment?

Use a separate branch for testware and merge it weekly.

Require testers to update links before merging each pull request.

Automate the generation of traceability links based on commit messages and code changes.

Update the traceability matrix at the end of each sprint.

How can traceability be used to ensure coverage in a DevOps pipeline?

By automatically generating new requirements from test results

By storing test coverage data in a separate database

By running all tests in the pipeline regardless of changes

By verifying that every requirement has at least one associated test case

Certified Tester Quality in DevOps

Domain 3Objective 1

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

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 11–15

11foundation · easy
What is essential for maintaining traceability links over time?
Select an answer first
12expert · hard
A team has a traceability matrix that is maintained manually. After a major refactoring, many test cases are obsolete, but the matrix still shows them as linked to requirements. The team wants to clean up the matrix and ensure it reflects the current state. What is the best approach?
Select an answer first
13foundation · easy
Why is establishing a single source of truth for testware important in a DevOps environment?
Select an answer first
14expert · hard
A team is adopting a trunk-based development model with frequent merges to the main branch. They want to maintain traceability between requirements and tests, but the fast pace makes it difficult to update links manually. What is the best way to maintain traceability in this environment?
Select an answer first
15foundation · easy
How can traceability be used to ensure coverage in a DevOps pipeline?
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.