VM Connector supports both intra-application and inter-application asynchronous communication. MuleSoft specifically documents that two different Mule applications can publish to and consume from the same VM queue when both applications are part of the same Mule domain and reference the shared VM configuration.
The fact that the applications are deployed to a two-node Mule cluster does not prevent use of VM Connector. In cluster mode, VM queues are cluster-wide resources. Mule's cluster synchronizes access, and messages placed on a VM queue can be processed by another node in the cluster. MuleSoft identifies this as a supported mechanism for distributing asynchronous work across clustered runtime instances.
Therefore, option B is incorrect: each node does not operate an entirely isolated VM queue namespace for a shared clustered configuration. Option D also contradicts VM Connector's documented inter-application use case.
The required architectural condition is that both applications use the same domain/shared VM configuration so they can reference the same queue. The publisher can then send asynchronously while the second API consumes from the shared VM queue.
Reference topics: VM Connector; Mule domains; inter-application communication; persistent/transient queues; Mule HA clustering.
Official documentation: https://docs.mulesoft.com/vm-connector/latest/vm-publish-across-apps
Official documentation: https://docs.mulesoft.com/vm-connector/latest/vm-reference
===============================================================
