Practice Free OMG-OCUP2-ADV300 Exam Online Questions
Question #1
What is the difference between a ValueSpecificattonActlon and a CreateObjectAction?
- A . There is no difference between the possible results of the CreateObjectAction and the ValueSpecificationAction
- B . A ValueSpecificationAction cannot produce instances of Classifiers, but a CreateObjectAction only produces instances of Classifiers
- C . When an InstanceValue is produced by a CreateObjectAction. the Structural Features can be assigned values, but when an InstanceValue is produced by a ValueSpecificationAction, the Structural Features have no values.
- D . When an InstanceValue is produced by a ValueSpecificationAction, the Structural Features can be assigned values, but when an InstanceValue is produced by a CreateObjectAction, the Structural Features have no values.
Correct Answer: B
B
Explanation:
The difference between ValueSpecificationAction and CreateObjectAction in UML is fundamental to the kinds of results they produce:
B
Explanation:
The difference between ValueSpecificationAction and CreateObjectAction in UML is fundamental to the kinds of results they produce:
Question #2
In a model of a commercial transaction, actors might exchange euros, pesos, and dollars.
Which figure illustrates compliant use of UML information items for these currency exchanges?
- A . Figure 1
- B . Figure 2
- C . Figure 3
- D . Figure 4
Correct Answer: B
B
Explanation:
In UML, an InformationItem represents an abstraction of all those elements in a UML model that have an information-bearing feature. It is depicted as a classifier with the keyword «informationItem». An InformationItem does not have direct instances and serves as a mechanism to handle unspecified, untyped information in a model. In the context of a commercial transaction model, currencies such as euros, pesos, and dollars can be abstractly represented as InformationItems to signify that they are used as a form of data exchange but without specifying the concrete structure or data type. Figure 2 correctly uses InformationItem notation, with the «informationItem» keyword and the directed association pointing from the Currency InformationItem to the Euro, Peso, and Dollar, which are likely representations or manifestations of the Currency. This complies with the UML specification for representing abstract entities in models that are involved in the exchange or flow of information.
B
Explanation:
In UML, an InformationItem represents an abstraction of all those elements in a UML model that have an information-bearing feature. It is depicted as a classifier with the keyword «informationItem». An InformationItem does not have direct instances and serves as a mechanism to handle unspecified, untyped information in a model. In the context of a commercial transaction model, currencies such as euros, pesos, and dollars can be abstractly represented as InformationItems to signify that they are used as a form of data exchange but without specifying the concrete structure or data type. Figure 2 correctly uses InformationItem notation, with the «informationItem» keyword and the directed association pointing from the Currency InformationItem to the Euro, Peso, and Dollar, which are likely representations or manifestations of the Currency. This complies with the UML specification for representing abstract entities in models that are involved in the exchange or flow of information.
Question #3
Which input element does lexical analysis of Action Language for Foundational UML text discard?
- A . term
- B . delimiters
- C . expression
- D . whitespace
Correct Answer: D
D
Explanation:
During the lexical analysis of Action Language for Foundational UML (fUML) text, whitespace (such as spaces, tabs, and line breaks) is discarded. The lexical analysis focuses on identifying meaningful tokens (such as keywords, identifiers, and operators) while ignoring whitespace, which does not contribute to the semantics of the language2.
D
Explanation:
During the lexical analysis of Action Language for Foundational UML (fUML) text, whitespace (such as spaces, tabs, and line breaks) is discarded. The lexical analysis focuses on identifying meaningful tokens (such as keywords, identifiers, and operators) while ignoring whitespace, which does not contribute to the semantics of the language2.
Question #4
Where does UML explicitly intend String Expression elements to be used?
- A . as (he ValueSpecifications for the nameExpressions of ParameterableElements within Template specifications
- B . as the model the author chooses for the specification of custom dynamically-generated names for any NamedElement
- C . whenever an OpaqueExpression form of a ValueSpecification needs to specify an expression that operates on String instances
- D . The specification has no metaclass StnngExpression and so no use of StringExpression is explicitly intended.
Correct Answer: D
D
Explanation:
In UML, ValueSpecifications are used to specify the value of an element. The UML 2 Specification does not define a metaclass named StringExpression. Instead, it provides a metaclass named OpaqueExpression, which can be used when an expression is written in a language that is not directly interpretable by the model. Since there is no metaclass called StringExpression in the UML 2 Specification, there is no explicitly intended use for it within the UML metamodel. The absence of this metaclass suggests that any use of a concept called "StringExpression" would not conform to standard UML 2 practices and would likely be part of an extension or profile, not the core UML metamodel.
D
Explanation:
In UML, ValueSpecifications are used to specify the value of an element. The UML 2 Specification does not define a metaclass named StringExpression. Instead, it provides a metaclass named OpaqueExpression, which can be used when an expression is written in a language that is not directly interpretable by the model. Since there is no metaclass called StringExpression in the UML 2 Specification, there is no explicitly intended use for it within the UML metamodel. The absence of this metaclass suggests that any use of a concept called "StringExpression" would not conform to standard UML 2 practices and would likely be part of an extension or profile, not the core UML metamodel.
Question #5
Let E be a UML 2.5 NamedElement with a name property of ‘_name" and with a name Expression property of "_expresslon".
Which one presentation or set of presentations of the name of E in a tool conforms to the OMG specification?
- A . _name
- B . _expression
- C . S_expression$ OR _name
- D . S_expression$
_expression
OR
_name:_expressk>n - E . UML 2.5 no longer includes a nameExpression properly within NamedElements.
Correct Answer: C
C
Explanation:
In UML 2.5, a NamedElement can have a name attribute, which is a string representing the element’s name, and a nameExpression attribute, which is a ValueSpecification used to specify the element’s
name in a more dynamic way. The presentation of the name of a NamedElement in a tool that conforms to the OMG specification could either be the literal name (as specified in the name attribute) or the evaluated expression from the nameExpression property. Therefore, a tool may choose to present either the simple name or the evaluated expression or allow toggling between the two. The specification does not mandate a single fixed presentation, allowing for flexibility in how tools display the name. This conforms to the OMG’s UML 2.5 specification, which describes the properties of NamedElement and their presentations within tools.
C
Explanation:
In UML 2.5, a NamedElement can have a name attribute, which is a string representing the element’s name, and a nameExpression attribute, which is a ValueSpecification used to specify the element’s
name in a more dynamic way. The presentation of the name of a NamedElement in a tool that conforms to the OMG specification could either be the literal name (as specified in the name attribute) or the evaluated expression from the nameExpression property. Therefore, a tool may choose to present either the simple name or the evaluated expression or allow toggling between the two. The specification does not mandate a single fixed presentation, allowing for flexibility in how tools display the name. This conforms to the OMG’s UML 2.5 specification, which describes the properties of NamedElement and their presentations within tools.
Question #6
What does a lower multiplicity of one for an end of an n-ary Association imply?
- A . Links combining the values of the other ends may exist or may not exist
- B . Exactly one link exists combining the values of the other ends.
- C . A link for every possible combination of values for the other ends must exist.
- D . Links combining the values of one or many other ends may exist.
Correct Answer: A
A
Explanation:
In UML, the multiplicity of an association end specifies how many instances of the class at that end can participate in a single association. A lower multiplicity of one (1) at one end of an n-ary (where n > 2) association implies that there must be at least one link that combines the values of the other ends, but it doesn’t require that a link exists for every possible combination. Therefore, it’s possible for some combinations to exist as links, while others do not, which is indicated by the option that links combining the values of the other ends may exist or may not exist. This interpretation is consistent with the definition of multiplicity in associations as outlined in the UML 2.x Superstructure Specification.
A
Explanation:
In UML, the multiplicity of an association end specifies how many instances of the class at that end can participate in a single association. A lower multiplicity of one (1) at one end of an n-ary (where n > 2) association implies that there must be at least one link that combines the values of the other ends, but it doesn’t require that a link exists for every possible combination. Therefore, it’s possible for some combinations to exist as links, while others do not, which is indicated by the option that links combining the values of the other ends may exist or may not exist. This interpretation is consistent with the definition of multiplicity in associations as outlined in the UML 2.x Superstructure Specification.
Question #7
Consider the following diagram fragment:
Assume that the system is in StateAl.
Which sequence of triggers will move the system to StateC?
- A . a6., a3, a1, a7, an
- B . a5, a5, a5. a1. a8, a8, a11
- C . a5, a6, a5, a3, a2, a10, a11, a12
D a1, a7, a8, a7, an
Correct Answer: C
C
Explanation:
Given that the system is in StateA1, the sequence of triggers that will move the system to StateC must take into account the transitions and their associated triggers as defined in the UML state diagram. Starting from StateA1, the trigger a5 will cause a transition within StateA, followed by a6, which moves to StateA2. The trigger a5 is not relevant as it is an internal transition in StateA1. Then, a3 (the exit action for StateA) and a2 would be followed to leave StateA altogether. Once out of StateA, a1 is used to transition to StateB, where a10 is an entry action, not a trigger. Finally, to get from StateB to StateC, the triggers a11 followed by a12 are needed. This sequence of triggers reflects the correct usage of exit, entry, and transition triggers as defined by UML state machine semantics.
C
Explanation:
Given that the system is in StateA1, the sequence of triggers that will move the system to StateC must take into account the transitions and their associated triggers as defined in the UML state diagram. Starting from StateA1, the trigger a5 will cause a transition within StateA, followed by a6, which moves to StateA2. The trigger a5 is not relevant as it is an internal transition in StateA1. Then, a3 (the exit action for StateA) and a2 would be followed to leave StateA altogether. Once out of StateA, a1 is used to transition to StateB, where a10 is an entry action, not a trigger. Finally, to get from StateB to StateC, the triggers a11 followed by a12 are needed. This sequence of triggers reflects the correct usage of exit, entry, and transition triggers as defined by UML state machine semantics.
Question #8
Which subclasses of Classifiers can be parameterized and used as Template Parameters?
- A . Class. Component. Interface, but not Signal
- B . Signal. Use Case, Component, but not Datatype
- C . Activity. Interaction, State Machine, but not Collaboration
- D . all subclasses of Classifier e.g. Class. Component. Datatype. Interface. Signal
Correct Answer: D
D
Explanation:
In UML, a template is a parameterizable element, and the parameters for a template are typically classes or other classifiers. According to the UML 2.x Superstructure Specification, all subclasses of Classifier can potentially be used as template parameters. This includes classes, components, datatypes, interfaces, signals, and more. The specification provides the flexibility to define template parameters that are specialized types, allowing for powerful and reusable designs. The ability to parameterize these elements is foundational to creating generic and reusable model elements, which is a core capability of the UML’s templating mechanism.
D
Explanation:
In UML, a template is a parameterizable element, and the parameters for a template are typically classes or other classifiers. According to the UML 2.x Superstructure Specification, all subclasses of Classifier can potentially be used as template parameters. This includes classes, components, datatypes, interfaces, signals, and more. The specification provides the flexibility to define template parameters that are specialized types, allowing for powerful and reusable designs. The ability to parameterize these elements is foundational to creating generic and reusable model elements, which is a core capability of the UML’s templating mechanism.
Question #9
What is a coregion?
- A . two Interactions that share the same border
- B . two combined fragments that have the same operands
- C . a shorthand for a parallel combined fragment on one lifeline
- D . the area between two lifelines that communicate
Correct Answer: C
C
Explanation:
A coregion in a UML Sequence Diagram is a notation that:
C
Explanation:
A coregion in a UML Sequence Diagram is a notation that:
Question #9
What is a coregion?
- A . two Interactions that share the same border
- B . two combined fragments that have the same operands
- C . a shorthand for a parallel combined fragment on one lifeline
- D . the area between two lifelines that communicate
Correct Answer: C
C
Explanation:
A coregion in a UML Sequence Diagram is a notation that:
C
Explanation:
A coregion in a UML Sequence Diagram is a notation that: