OMG-OCUP2-ADV300 Exam Dumps : OMG Certified UML Professional 2 (OCUP 2) - Advanced Level

In addition to ObjectFlow, which is used to denote the flow of objects between activities in a UML Activity diagram, data movement can also be facilitated through:

• A.Pin is a point on a node that is used to accept or provide objects or data, but does not move data by itself.
• B.Correct. Variables can be used to hold and move data within an activity, facilitating state maintenance or transitions between different actions.
• C.Property, while it holds data, typically pertains to classes or components, not activities.
• D.ControlFlow dictates the order of execution but does not inherently move data.

References:

• UML Specification: Activity Diagrams section.
• Details on how data can be managed within activities can be explored in the UML 2.5 Documentation, particularly under Activity and Object Nodes.

For asynchronous invocations in UML, when an exception is thrown and there is no matching exception handler within the activity, the exception is effectively lost because there is no direct mechanism to propagate it back to the caller. This reflects the nature of asynchronous communication where the calling process does not wait for the completion of the called process and, thus, may not be designed to handle exceptions that occur during the called process.

References:

• UML 2.5 Specification: The UML specification describes the behavior of actions within activities and how exceptions are handled, or not handled, in the case of asynchronous calls. It specifically states that for asynchronous calls, the exception is not propagated back to the caller as there is no return flow defined for such invocations.

Given that the system is inStateA1, the sequence of triggers that will move the system toStateCmust take into account the transitions and their associated triggers as defined in the UML state diagram. Starting fromStateA1, the triggera5will cause a transition withinStateA, followed bya6, which moves toStateA2. The triggera5is not relevant as it is an internal transition inStateA1. Then,a3(the exit action forStateA) anda2would be followed to leaveStateAaltogether. Once out ofStateA,a1is used to transition toStateB, wherea10is an entry action, not a trigger. Finally, to get fromStateBtoStateC, the triggersa11followed bya12are needed. This sequence of triggers reflects the correct usage of exit, entry, and transition triggers as defined by UML state machine semantics.