How does a Mule application implement an object store?

• A. Persistent: OSv2 = Anypoint Object Store service; cloud native implementation; Data is shared between all CH workers.
• B. Non-persistent: Does NOT use OSv2 service.
• C. Object store is implemented globally for all runtimes.
• D. Persistent: Data is isolated per CloudHub worker.

Answer: (A)

The key idea here is that in a CloudHub deployment, the object store is a persistent, cloud-native service provided by Anypoint called OSv2. When a Mule application uses OSv2, its stored data lives in that centralized store rather than in the memory of a single runtime. This persistence means the data survives restarts and, importantly, is accessible by all CloudHub workers handling the deployment, allowing sharing and coordination across the app.

So, using the persistent OSv2 object store and its cloud-native nature—with data shared among all CloudHub workers—is the correct approach. The other options describe scenarios that are either non-persistent, isolated to a single worker, or ambiguously global across runtimes, none of which capture the central, shared, persistent OSv2 behavior.