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.