A team is starting a new project and wants to use MBT to support requirements engineering. They have a set of high-level requirements but no detailed specifications. What is the first step they should take?

Write detailed specifications before creating any models.

Start coding the system to see what happens.

Create test cases directly from the high-level requirements.

Create a test model from the high-level requirements to identify gaps and ambiguities.

A team is validating requirements for a safety-critical system. They have a test model that generates test cases. During validation, they find that the model does not cover a scenario that is implied by the requirements. What should they do?

Add the missing scenario as a manual test case without updating the model.

Ignore the missing scenario because it is not explicitly stated in the requirements.

Rewrite the requirements to exclude the implied scenario.

Update the test model to include the missing scenario and regenerate test cases.

What is the primary purpose of a requirements-based test model?

To document the project's testing schedule

To provide a basis for systematic test case generation

To record the results of test runs

To replace the need for test execution

A team is using MBT for a system with both complex business rules and critical state-based behavior. They need a single test model that can generate test cases for both aspects. Which modeling approach is most appropriate?

Use only a decision table to cover all scenarios.

Use only a state machine to cover all scenarios.

Use a sequence diagram to model both business rules and states.

Use a combination of decision tables and state machines, integrated into a single model.

A requirement change is proposed that affects multiple test models. The team needs to assess the impact of the change before implementing it. What is the most effective way to do this using MBT?

Ask the developer to estimate the impact based on their knowledge.

Implement the change and then run all tests to see what fails.

Use traceability links to identify which test models and test cases are affected by the change.

Manually review all test cases to see which ones might be affected.

Certified Tester Model-Based Testing

Domain 1Objective 6

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

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

1application · medium
A team is starting a new project and wants to use MBT to support requirements engineering. They have a set of high-level requirements but no detailed specifications. What is the first step they should take?
Select an answer first
2expert · hard
A team is validating requirements for a safety-critical system. They have a test model that generates test cases. During validation, they find that the model does not cover a scenario that is implied by the requirements. What should they do?
Select an answer first
3foundation · easy
What is the primary purpose of a requirements-based test model?
Select an answer first
4expert · hard
A team is using MBT for a system with both complex business rules and critical state-based behavior. They need a single test model that can generate test cases for both aspects. Which modeling approach is most appropriate?
Select an answer first
5expert · hard
A requirement change is proposed that affects multiple test models. The team needs to assess the impact of the change before implementing it. What is the most effective way to do this using MBT?
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.