What is the difference between persistent and non-persistent data stores in the MuleSoft Object Store?

• A. Persistent data survives redeployments, server crashes, or when the CloudHub worker is stopped.
• B. Non-persistent data can be reused while the application is running but is lost after the application restarts.
• C. Persistent data is stored only in the JVM memory.
• D. Non-persistent data is automatically replicated across the cluster.

Answer: (A)

Durability across restarts is what differentiates persistent from non-persistent data stores in the MuleSoft Object Store. Persistent data is stored in a durable backing (not just in the JVM memory), so it remains available after redeployments, server crashes, or when a CloudHub worker is stopped. Non-persistent data lives in memory for the life of the application instance and is lost if the application restarts. Therefore, the statement that persistent data survives redeployments, server crashes, or a stopped CloudHub worker best captures this difference. The other options describe in-memory behavior or assumptions that don’t define how durability is handled.