OMG-OCSMP-MBI300 Practice Exam Questions with Answers OMG-Certified Systems Modeling Professional - Model Builder – Intermediate Certification

b1 or b2 or b3 or b4

(b1 or b?) and (b3 or b4)

(b1 or b2) and b3 and b4

The question cannot be answered because Activity Diagram Fragment 1 is ambiguous

Subclasses may only redefine existing features of a superclass.

Subclasses may add, remove, and redefine existing features of a superclass

Subclasses may add and remove, but not redefine, existing features of a superclass

Subclasses may add and redefine, but not remove existing features of a superclass

Subclasses may remove or redefine existing features, but not add features, to a superclass.

Message a1 overtakes message m1, which is processed after receipt of a1.

Message a1 overtakes messages m1 and m2 and is processed before them.

Message m1 overtakes message a1, which is processed after receipt of m2.

Message m1 overtakes messages a1 and m2 and is processed before them.

on any diagram

only on parametric diagrams

only on block definition diagrams

only on block definition diagrams or package diagrams

only on block definition diagrams or parametric diagrams

only on block definition diagrams or internal block diagrams

A metamodel is used to define the stereotypes and the properties of a profile.

A metamodel Is the result of applying a profile to a user model to define new domain concepts.

A profile is a mechanism for extending existing concepts defined In a metamodel.

A profile is a mechanism for defining stereotypes, which is not related to metamodels in any way.

Package diagram

Activity diagram

Parametric diagram

Requirements diagram

internal block diagram

Block definition diagram

The modeling tool provides the stereotypes

The stereotypes are part of the SysML standard

Each modeler who writes requirements can define stereotypes

A profile that maps modeling methodology concepts to the model defines the stereotypes

Composition allows requirements to inherit properties and requirements relationships

Composition allows role names to be assigned to sub-requirements thus providing a contextual reference

Composition allows a particularly useful requirement to be reused by multiple higher level requirements or specifications

Composition allows a requirement to be decomposed into sub-requirements as long as they don't add to or change the meaning of the original requirement.

Requirements cannot use composition. They are not classifiers

Option A

Option B

Option C

Option D

an Interaction use referencing an interaction defined on a separate sequence diagram

an interaction template construct that is instantiated from the referring sequence diagram

the call interaction operator with an operand referring to the reusable Interaction defined elsewhere

an activation on the referring sequence diagram allocated to another activation on the referenced diagram

The Security viewpoint conforms to the requirements specified by the Security view

The Security view is intended to address the purpose specified by the Security viewpoint

The Security view imports the Security viewpoint to ensure the security requirements are satisfied

The Security viewpoint imports the model elements associated with flowing down the security requirements

Option A

Option B

Option C

Option D

action 2

action 2 action 3

action 2 action 4

action 3

action 4

action 5 action 2 action 3

action 5 action 2 action 4

an activity diagram

a parametric diagram

an internal block diagram

a block definition diagram

on a lifeline in a sd

on a transition in a stm

on an object node In an act

in the s rates compartment of a block on a bdd

Every project should create its own domain specific profile to describe modeling standards and conventions

Organizations should create specific modeling standards and conventions to ensure modeling consistency across projects

The SysML specification alone is sufficient to describe modeling standards and conventions when the modeling tool has a proper implementation of SysML

The SysML specification and the modeling tool documentation are sufficient to describe modeling standards and conventions

The testCase model element can be used in SystvIL but it only applies to software

Validation of a requirement can be indicated using a satisfiedBy relationship to a testCase

Only the verdict model element (which can be a property of a testCase) can have a verifies relationship to a requirement.

A requirement can have a vehfiedBy relationship to a testCase even if the test has not yet been conducted or even fully specified

testCase is part of the UML Testing Profile and cannot be used with SysML.

Option A

Option B

Option C

Option D

11

14

13

There is no value - the instance model is invalid

Option A

Option B

Option C

Option D

Option A

Option B

Option C

Option D

Option E

The pressure of each part is constrained to be 50 psi.

if not redefined individually by each part, the value of pressure must be 50 psi.

The values may be redefined, but they must be the same for both front and rear.

To be other than 50 psi. instance specifications must be developed for front and rear tires.