Free OMG-OCUP2-ADV300 Practice Test Questions and Answers (2026)

In UML, profiles and stereotypes provide a lightweight extension mechanism to adapt existing UML metaclasses for specific domains or platforms. A stereotype can add new attributes (properties/tagged values), add constraints (using OCL or natural language), and customize visual notation (such as icons). However, a fundamental rule of UML profile semantics is that a profile or stereotype cannot alter or relax the semantics of the base UML metamodel. Specifically, stereotypes cannot remove, reduce, or invalidate any existing constraints or constructs defined by the underlying base UML metaclass elements. Therefore, removing constraints from a metaclass or model element is explicitly prohibited by the UML specification.

A. Stereotypes can define visual icons or graphical shapes to customize the visual notation of the extended model element.

B. Stereotypes are permitted to introduce additional constraints (e.g., OCL expressions) to further restrict the base metaclass semantics.

D. Stereotypes can define structural properties (tagged values/attributes) to extend model elements with domain-specific metadata.

- Object Management Group (OMG). (2017). OMG Unified Modeling Language (OMG UML), Version 2.5.1, Clause 12.3 (Profiles), Section 12.3.1. https://www.omg.org/spec/UML/2.5.1/PDF

In UML sequence diagrams, critical is a combined fragment operator used to designate a critical region within an interaction. According to the OMG UML specification, a critical region enforces atomicity over the set of lifelines covered by the fragment. This means that event occurrences within the critical fragment cannot be interleaved with any other event occurrences on those lifelines from outside the fragment. Once an event inside the critical region begins execution, all subsequent events within that region must execute to completion before any external events on the involved lifelines can occur. Thus, no other events may interfere between the events of the critical fragment.

A. critical refers to critical regions (atomicity/non-interleaving), not message delivery priority or network QoS settings.

B. The operator critical has formal runtime semantics regarding event interleaving, not informal design status or pending architectural redesign.

D. critical is a formal semantic constraint ensuring non-interleaved trace execution, not an informal design directive about message importance.

- Object Management Group (OMG). (2015). OMG Unified Modeling Language (OMG UML), Version 2.5. Section 17.6.3.1 (CombinedFragmentKind - critical), p. 583.

In UML, the «bind» relationship is used to specify that a class is a template instantiation of a

template class, where actual parameters are bound to the formal parameters of the template class1.

However, in the case of the relationship between a concrete class like Vector and an abstract class

like AbstractList, the correct relationship should be Generalization, not «bind».

Generalization is a taxonomic relationship between a more general classifier and a more specific

classifier. Each instance of the specific classifier is also an instance of the general classifier1.

Thus, Vector being a concrete implementation of AbstractList, should inherit from AbstractList, which

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/OMG-OCUP2-ADV300/page_3_img_2.jpg

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/OMG-OCUP2-ADV300/page_3_img_3.jpg

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/OMG-OCUP2-ADV300/page_3_img_4.jpg

is correctly represented by a Generalization relationship in UML.

The other options can be evaluated as follows:

Option A: The upper limit for the size of PhontyQueue is a design decision that should be based on

the requirements and use cases of the application. It is not inherently incorrect in UML to have a

specific upper limit.

Option C: The Generalization relationship is correctly used

between PriorityQueue and AbstractQueue as it represents inheritance in UML.

Option D: While it is true that template parameters are typically defined at the top of the hierarchy,

the statement is too absolute. In UML, template parameters can be added to specialized classes, but

it depends on the specific design and requirements. Therefore, without additional context, this

statement cannot be deemed universally valid.

In conclusion, the most applicable and valid review comment is option B, which correctly identifies

the misuse of the «bind» relationship in the context of the class diagram provided.

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/OMG-OCUP2-ADV300/page_4_img_1.jpg

In UML, an n-ary association models a relationship among n classifiers. The multiplicity bounds on a member end of an n-ary association specify the allowable number of instances that can appear at that end for a given combination of single instances for the remaining n-1 ends. A lower multiplicity bound of 1 on an end dictates that for every possible tuple or combination of instances formed by the other ends, there must exist at least one link connecting them to an instance at this specific end. Thus, a link incorporating every valid combination of values for the other ends must be present in the model instance.

A. A lower multiplicity of 1 requires links to exist for every combination of the other ends, rather than being optional.

B. A lower bound of 1 enforces at least one link, but does not restrict it to exactly one unless the upper bound is also 1.

D. Multiplicity on an end evaluates combinations of all remaining n-1 ends simultaneously, not arbitrary subsets of one or many ends.

- Object Management Group (OMG), "Unified Modeling Language (OMG UML) Specification", Version 2.5.1, Section 11.5.3 (Association - Semantics), p. 201.

- Object Management Group (OMG), "UML 2.4.1 Superstructure Specification", Section 7.3.3 (Association), p. 39.

When an Action within an Activity is invoked asynchronously (such as via an asynchronous CallBehaviorAction or CallOperationAction with isSynchronous = false), the calling thread continues its execution independently without waiting for the invoked behavior to complete or return a response. Because there is no active call stack or return channel connecting the asynchronous execution back to the caller, any exception raised during the execution of the asynchronous activity cannot be propagated back to the invoking caller. If the exception is not caught and handled locally by an ExceptionHandler within the invoked Activity itself, the exception is permanently lost.

Option A: Asynchronous invocations do not maintain a call stack connection, making propagation to the caller impossible.

Option B: Exceptions in asynchronous activities can be handled normally using internal ExceptionHandler nodes inside the activity.

Option C: Catching exception handlers inside an activity do not require exactly one output pin to handle asynchronous exceptions.

- Object Management Group (OMG). (2017). OMG Unified Modeling Language (OMG UML) Specification, Version 2.5.1, Section 15.5.3 (ExceptionHandler) & Section 16.3 (Call Actions), pp. 411-412, 447.

In UML 2.5.1, an operation template defines formal template parameters (such as ). When binding a template operation, a bound operation is created by substituting actual parameters (such as Card) for the formal parameters in the template's signature. According to the UML notation specification for templateable elements and operation templates, a bound operation is depicted with the same signature as the template operation, but with the actual template parameter types directly substituted for the formal template parameters. Thus, substituting parameter E with Card in addElement (e : E) yields addElement (e : Card).

B: This option removes the parameter list entirely, omitting necessary parameter types and failing to represent the bound operation signature.

C: This notation incorrectly mixes explicit template binding parameter mapping syntax with standard operation declaration syntax within guillemets.

D: This option uses invalid UML syntax, misapplying the «bind» keyword to an operation call/declaration without valid parameter typing.

- OMG Unified Modeling Language (OMG UML) Specification, Version 2.5.1, Section 9.5.4 (Notation - Operation Templates), p. 125.

- Object Management Group, UML 2.5.1 Metamodel & Notation Specification.

In the Unified Modeling Language (UML), an operation owned by a classifier can redefine an operation inherited from a general classifier to refine its contract or behavior. According to the UML specification, redefinition allows the specializing classifier's operation to specify additional preconditions and postconditions. A precondition is a constraint that must be satisfied prior to invoking the operation. When an operation is redefined, adding preconditions allows modelers to enforce stricter or additional logical constraints specific to the context of the subtype. Conversely, structural elements like parameters or scope cannot be arbitrarily added or altered during redefinition, as doing so would violate signature compatibility rules defined by the metamodel.

A: Scope is not a valid UML operation construct that can be added during redefinition.

B: Templates pertain to templateable elements and cannot be arbitrarily added to redefine an inherited operation.

C: Parameters define the operation's signature and cannot be added or modified arbitrarily during operation redefinition.

- Object Management Group. (2017). OMG Unified Modeling Language (OMG UML) Specification, Version 2.5.1, Section 9.6.3 (Operation), p. 115. https://www.omg.org/spec/UML/2.5.1/PDF

In the Meta Object Facility (MOF) 2.5 Core Specification, Reflection is a core capability that provides a generic, reflective interface for discovering and manipulating metaobjects and metadata at runtime. It allows programs to inspect the structure of a model, query meta-classes, create instances, and read or modify property values without requiring compile-time generated interfaces or prior domain-specific knowledge. By exposing operations such as getMetaClass(), get(), set(), and invoke(), Reflection ensures flexible dynamic metaobject management across model-driven engineering frameworks, repository tools, and meta-modeling environments.

Option A is wrong because Life Cycle handles the creation, copying, and destruction of metaobjects rather than runtime structural discovery and reflective metadata manipulation.

Option B is wrong because Extension defines mechanisms to extend metamodels (such as stereotype applications or profiles), not reflective introspective APIs for metaobjects.

Option D is wrong because Federation relates to combining multiple distributed repositories or models, not discovering and manipulating individual metaobject structures directly.

- OMG Meta Object Facility (MOF) Core Specification, Version 2.5.1 (formal/2016-11-01), Section 9.1 "Reflection Package", p. 33.

- OMG Unified Modeling Language (OMG UML) Specification, Version 2.5.1 (formal/2017-12-05), Section 7.3.3 "Reflective Capabilities", p. 39.

In UML, a DecisionNode routes tokens along outgoing edges based on guard conditions. A DecisionNode can have a decisionInput behavior and an optional decisionInputFlow. According to the UML specification constraints for DecisionNode, if a DecisionNode has an incoming ObjectFlow and a decisionInputFlow, the decisionInput behavior requires two in parameters: the first corresponds to the type of the incoming object token from the primary ObjectFlow, and the second corresponds to the type of the token arriving on the decisionInputFlow. This design allows the decision behavior to evaluate both data inputs concurrently to determine which outgoing edge guards are satisfied during activity execution.

Option A: A DecisionNode can have up to two incoming activity edges if one of them is designated as a decisionInputFlow.

Option B: A DecisionNode allows at most two incoming edges total, but one must strictly be a decisionInputFlow, not two standard ControlFlows.

Option C: When an incoming edge is a ControlFlow and a decisionInput exists without a decisionInputFlow, the decisionInput behavior takes zero input parameters.

- Object Management Group (OMG). (2017). OMG Unified Modeling Language (OMG UML) Specification, Version 2.5.1, Section 15.2.3.2 (DecisionNode Constraints, twoinputparameters), p. 375.