What is the most appropriate way to implement persistence for the watermark in order to support the required data replication integration logic?
Refer to the exhibit.
A Mule application is being designed to be deployed to several CIoudHub workers. The Mule application’s integration logic is to replicate changed Accounts from Satesforce to a backend system every 5 minutes.
A watermark will be used to only retrieve those Satesforce Accounts that have been modified since the last time the integration logic ran.
What is the most appropriate way to implement persistence for the watermark in order to support the required data replication integration logic?
A . Persistent Anypoint MQ Queue
B . Persistent Object Store
C . Persistent Cache Scope
D . Persistent VM Queue
Answer: B
Explanation:
* An object store is a facility for storing objects in or across Mule applications. Mule uses object stores to persist data for eventual retrieval.
* Mule provides two types of object stores:
1) In-memory store C stores objects in local Mule runtime memory. Objects are lost on shutdown of the Mule runtime.
2) Persistent store C Mule persists data when an object store is explicitly configured to be persistent. In a standalone Mule runtime, Mule creates a default persistent store in the file system. If you do not specify an object store, the default persistent object store is used.
MuleSoft
Reference: https://docs.mulesoft.com/mule-runtime/3.9/mule-object-stores
Latest MuleSoft Integration Architect I Dumps Valid Version with 244 Q&As
Latest And Valid Q&A | Instant Download | Once Fail, Full Refund