A company is developing a medical device with strict regulatory requirements. The team wants to use MBT to support requirements engineering. They have a large set of requirements that are constantly changing. They also need to demonstrate traceability for audits. Which approach best balances these needs?

Use MBT to generate test cases, but manually update the traceability matrix after each change.

Use MBT to create a test model that is linked to requirements, and regenerate test cases automatically when requirements change.

Use MBT only for the initial test design and then freeze the test cases.

Use MBT to validate requirements, but do not use it for test generation.

Which practice is essential for maintaining requirements traceability in a model-based testing project?

Keeping traceability information only in the testers' memory

Deleting traceability links after test execution

Updating traceability links whenever requirements or models change

Creating traceability links only for high-priority requirements

Which technique uses MBT to check that a model accurately reflects the stated requirements?

Test execution on the final system

A regulatory requirement mandates that each test case must be traceable to a specific requirement. The team uses MBT. What is the best practice to ensure this traceability is maintained over time?

Store traceability links in the test model and regenerate test cases with embedded requirement IDs.

Use a naming convention for test cases that includes the requirement ID.

Document traceability in the test report at the end of the project.

Maintain a separate traceability matrix that is updated manually after each test run.

A project requires that every test case be traceable to a specific requirement. The team uses MBT with a test model. What is the most effective way to establish and maintain this traceability?

Manually add requirement IDs to test cases after they are generated.

Link each element in the test model to the corresponding requirement ID and propagate this to generated test cases.

Create a separate spreadsheet mapping test cases to requirements, updated at the end of each sprint.

Use a naming convention for test cases that includes the requirement ID.

Certified Tester Model-Based Testing

Domain 1Objective 6

Supporting Requirements Engineering CT-MBT Practice Questions (Page 5)

Part of the Introduction to Model-Based Testing 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–1 from this objective — we provide 29 practice questions to prepare you well beyond it. (estimate)

29questions here

6free pages

5concepts

Questions 21–25

21expert · hard
A company is developing a medical device with strict regulatory requirements. The team wants to use MBT to support requirements engineering. They have a large set of requirements that are constantly changing. They also need to demonstrate traceability for audits. Which approach best balances these needs?
Select an answer first
22foundation · easy
Which practice is essential for maintaining requirements traceability in a model-based testing project?
Select an answer first
23foundation · easy
Which technique uses MBT to check that a model accurately reflects the stated requirements?
Select an answer first
24application · medium
A regulatory requirement mandates that each test case must be traceable to a specific requirement. The team uses MBT. What is the best practice to ensure this traceability is maintained over time?
Select an answer first
25application · medium
A project requires that every test case be traceable to a specific requirement. The team uses MBT with a test model. What is the most effective way to establish and maintain this traceability?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CT-MBT

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