Which method is commonly used to create traceability links between test basis items and testware artifacts?

Naming test cases with random numbers

Storing all testware in a single file without any references

Using a traceability matrix that maps requirements to test cases

Deleting test cases that do not have a corresponding requirement

In a DevOps environment, what is the primary characteristic of a single source of truth (SSOT) for testware?

A single, authoritative repository that all teams use to access and update test artifacts

A test management tool that is accessible only to the test team

A backup copy of all test artifacts stored in a separate location for disaster recovery

A version control system that stores only the latest version of each test artifact

A team is working on a system with a high degree of interdependencies between features. They need to ensure that when a requirement changes, all affected test cases are identified, including those that test other features indirectly. What is the best way to achieve this?

Create traceability links not only between requirements and test cases but also between test cases themselves.

Use a code coverage tool to identify all tests that execute the changed code.

Run the full regression suite whenever any requirement changes.

Maintain a separate document listing all affected tests for each requirement.

In a DevOps workflow, how does traceability support impact analysis?

By identifying which tests are affected by a change in the code or requirements

By storing all test results in a single log file

By preventing any changes to the testware

By automatically fixing any broken tests

A team wants to automate the maintenance of traceability links in their DevOps pipeline. They use a requirements tool and a test automation framework. What is the best way to integrate traceability into the pipeline?

Generate traceability reports only at the end of each release.

Use an API or plugin that automatically updates traceability links when requirements or tests change.

Have testers manually update the traceability matrix after each pipeline run.

Store traceability links in a separate database and update it weekly.

Certified Tester Quality in DevOps

Domain 3Objective 1

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

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 1–5

1foundation · easy
Which method is commonly used to create traceability links between test basis items and testware artifacts?
Select an answer first
2foundation · easy
In a DevOps environment, what is the primary characteristic of a single source of truth (SSOT) for testware?
Select an answer first
3expert · hard
A team is working on a system with a high degree of interdependencies between features. They need to ensure that when a requirement changes, all affected test cases are identified, including those that test other features indirectly. What is the best way to achieve this?
Select an answer first
4foundation · easy
In a DevOps workflow, how does traceability support impact analysis?
Select an answer first
5application · medium
A team wants to automate the maintenance of traceability links in their DevOps pipeline. They use a requirements tool and a test automation framework. What is the best way to integrate traceability into the 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.