# Object Store persistence by deployment

*MuleSoft Developer II Study Guide · Implement performant and reliable Mule applications · Last updated November 7, 2026 · https://www.certifyforce.com/study-guide/mulesoft-developer-ii/implement-performant-and-reliable-mule-applications/object-store-persistence-by-deployment*

Select Object Store persistence and backend access by deployment, distinguish rolling lifetime from cleanup, and recognize the limits of durable key-value state.

- Certification: Salesforce MuleSoft Developer II
- Exam section: Implement performant and reliable Mule applications
- Study guide: https://www.certifyforce.com/study-guide/mulesoft-developer-ii

**Official exam objective:**

> Implement ObjectStore persistence for all Mule deployment options.

## What the exam expects

- Choose persistence and backend access for the actual deployment option.
- Partition component state and select a supplied store implementation.
- Distinguish entry lifetime, cleanup timing and transaction guarantees.
- Predict storage mutation and read results without confusing them with persistence.

An **Object Store** holds keyed values; a **partition** separates a key space; **persistent** storage survives a runtime crash; **TTL** sets entry lifetime; an **ObjectStoreManager** supplies the storage implementation. Persistence does not make an Object Store a transactional database ([Connector overview](https://docs.mulesoft.com/object-store-connector/latest/), [Reference](https://docs.mulesoft.com/object-store-connector/latest/object-store-connector-reference)).

## Key facts

| Fact | Detail | Source |
|---|---|---|
| Default store | Persistent and available without an explicit store reference. | [Overview](https://docs.mulesoft.com/object-store-connector/latest/) |
| Transient store | `persistent="false"` chooses memory-only state. | [Custom store](https://docs.mulesoft.com/object-store-connector/latest/) |
| Provider selection | Configuration Reference selects a supplied implementation. | [Reference](https://docs.mulesoft.com/object-store-connector/latest/object-store-connector-reference) |
| Partitioning | Distinct stores isolate component key spaces. | [Overview](https://docs.mulesoft.com/object-store-connector/latest/) |
| On-premises access to v2 | Uses the Object Store REST API. | [v2](https://docs.mulesoft.com/object-store/) |
| Rolling renewal | Retrieve can renew eligible entries; Contains cannot. | [TTL](https://docs.mulesoft.com/object-store/) |
| Cleanup interval | Schedules checks rather than immediate write-time eviction. | [Expiration](https://docs.mulesoft.com/object-store-connector/latest/object-store-connector-reference) |
| ACID requirement | Needs an appropriate transactional store. | [Limitations](https://docs.mulesoft.com/object-store-connector/latest/) |

## Check yourself

- Why must an archive be read before calling Clear?
- When Remove receives a key that is not present, what outcome should you handle?
- Which read supplies values together with keys for a snapshot?

## Sources

- [Object Store Connector](https://docs.mulesoft.com/object-store-connector/latest/)
- [Object Store Connector Reference](https://docs.mulesoft.com/object-store-connector/latest/object-store-connector-reference)
- [Object Store v2 Overview](https://docs.mulesoft.com/object-store/)
- [Configuring Persistence Gateway with Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/persistence-gateway)

## About the full unit

The "Core concepts", "Exam traps" and "Worked scenario" sections of this unit, its 7 linked practice questions, and unlimited timed mock exams are included with the MuleSoft Developer II pack (USD $19): https://www.certifyforce.com/practice-exams