The correct answer is C. In Business Automation Workflow case/process integration, case content objects represent the properties associated with a case and activity. Data objects defined in a case solution are available in the designer and can be used to implement case activities that use a process and build user interfaces. Case content objects are passed by reference from a case to a process, with no input mapping required; the reference is automatically assigned to the matching case object declaration in process variables. This behavior establishes the case or case activity as the authoritative source that pushes the content-object reference into the process context. It is not a source-code pull request, so option A is irrelevant. It is not simply asynchronous messaging, because the tested concept is propagation of case/activity content objects into the process execution context. It is also not a generic synchronous update model where both sides independently commit changes at the same time. In solution design, the case/activity supplies the content object context to the process. References/topics: Case activities with workflow processes, content object variables, case content objects, parent case interaction, process variables.