A team has developed a model for a user authentication system. They want to validate that the model correctly handles the 'account locked' scenario. Which validation method is most appropriate for this specific behavioral check?

Review the model's graphical layout to ensure the locked state is visually prominent.

Compare the model's class names with the requirement document.

Ask a developer to confirm the model looks reasonable.

Execute the model with a test sequence that triggers five failed logins and verify the model reaches the locked state.

During a structured review of a sequence diagram for a login process, a reviewer notes that the diagram includes a step for 'send password reset email' that is not mentioned in any requirement. The team must decide how to handle this. What is the best course of action?

Keep the step and add a comment that it is 'nice to have'.

Ignore the step because it does not affect the main login flow.

Flag the step as a potential scope creep and verify with the product owner whether it is an implicit requirement.

Remove the step immediately because it is not in the requirements.

What is the primary purpose of feedback loops in iterative MBT model development?

To document the model for stakeholders without any further changes

To ensure the model is never changed after initial creation

To incorporate lessons learned from reviews and validation into subsequent model refinements

To replace the need for requirements analysis

A team is developing a state model for a vending machine. They have completed a basic version covering normal operation. They now want to add handling for 'out of stock' and 'insufficient funds' scenarios. According to iterative model development, what is the recommended approach?

Add the new states and transitions in a new iteration, then re-run validation tests.

Rewrite the entire model from scratch to incorporate the new scenarios.

Add the new scenarios to the test cases but leave the model unchanged.

Defer the new scenarios until after the system is deployed.

Certified Tester Model-Based Testing

Domain 2Objective 8

Iterative Model Development, Review and Validation CT-MBT Practice Questions (Page 4)

Part of the MBT Modeling domain, which makes up ~27% of our current practice bank. ISTQB does not publish an official question count, but from its 60-minute exam (~25–40 total, ~7–11 in this domain), expect 1–1 from this objective — we provide 27 practice questions to prepare you well beyond it. (estimate)

27questions here

6free pages

6concepts

Questions 16–20

16application · medium
A team has developed a model for a user authentication system. They want to validate that the model correctly handles the 'account locked' scenario. Which validation method is most appropriate for this specific behavioral check?
Select an answer first
17application · medium
During a structured review of a sequence diagram for a login process, a reviewer notes that the diagram includes a step for 'send password reset email' that is not mentioned in any requirement. The team must decide how to handle this. What is the best course of action?
Select an answer first
18foundation · easy
What is the primary purpose of feedback loops in iterative MBT model development?
Select an answer first
19foundation · easy
Which structured review technique is specifically designed to evaluate an MBT model for correctness, completeness, and consistency?
Select an answer first
20application · medium
A team is developing a state model for a vending machine. They have completed a basic version covering normal operation. They now want to add handling for 'out of stock' and 'insufficient funds' scenarios. According to iterative model development, what is the recommended approach?
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.