what happens after undeployment completes?

Composite A has two versions deployed lo the SOA runtime. Version 2.0 is the default revision,
and Version 1.0 is an earlier (but active) revision. Version 2.0 has 100 instances in the Running
state also hits 50 instances that are waiting for a callback on a mid-process < receiver> within a
BPEL component in the composite. You undeploy Version 2.0.
Which statement describes what happens after undeployment completes?

A.
All running Instances and the callbacks are allowed to complete on Version 1.0, but all new
requests are served by Version 1.0.

B.
All running Instances are allowed to complete, the callbacks fail after undeployment and all new
requests ate served by Version 1.0.

C.
All running instances immediately go stale, including the instances that are awaiting callbacks
on the mid process <receive>.

D.
All running instances immediately go stale, but the callbacks are processed by Version 1.0.

Explanation:

Note:
You can undeploy SOA composite applications from Oracle Enterprise Manager Fusion
Middleware Control with the Undeploy SOA Composite wizard. Using the Undeploy SOA
Composite wizard has the following consequences:
* The instance state of the undeployed composite application is set to stale. The instance state is
available in the instance listing, and you can access audit trail and flow trace details.
* If you undeploy the default revision of the SOA composite application (for example, 2.0), the next
active, available revision of the application is automatically designated as the new default (for
example, 1.0).
* You can no longer configure and monitor this revision of the application.
* You can no longer process instances of this revision of the application.
* The state of currently running instances is changed to stale and no new messages sent to this
composite are processed.
* A warning message is displayed at the end of this wizard when you undeploy the default
composite revision.