Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce Certified MuleSoft Developer II (Mule-Dev-301) Exam - Topic 2 Question 34 Discussion

Actual exam question for Salesforce's Salesforce Certified MuleSoft Developer II (Mule-Dev-301) exam
Question #: 34
Topic #: 2
[All Salesforce Certified MuleSoft Developer II (Mule-Dev-301) Questions]

Refer to the exhibit.

A Mute Object Store is configured with an entry TTL of one second and an expiration interval of 30 seconds.

What is the result of the flow if processing between os'store and os:retrieve takes 10 seconds?

Show Suggested Answer Hide Answer
Suggested Answer: A

The result of the flow is nullPayload if processing between os:store and os:retrieve takes 10 seconds. This is because the entry TTL of the object store is one second, which means that any stored value expires after one second and is removed from the object store. The expiration interval of 30 seconds only determines how often the object store checks for expired values, but it does not affect the TTL. Therefore, when os:retrieve tries to get the value after 10 seconds, it returns nullPayload because the value has already expired and been removed. Reference: https://docs.mulesoft.com/object-store/osv2-faq#how-does-the-time-to-live-work


by Roosevelt at Aug 16, 2025, 05:54 AM

Limited Time Offer

25%

Off

Get Premium Salesforce Certified MuleSoft Developer II (Mule-Dev-301) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Tenesha
4 months ago
I agree, C makes the most sense here.
upvoted 0 times
...
Mindy
4 months ago
Definitely going with C, OS:KEY_NOT_FOUND.
upvoted 0 times
...
Vallie
5 months ago
But what if the processing time was shorter? Would it change?
upvoted 0 times
...
Bo
5 months ago
Wait, how can it expire that fast? Sounds off.
upvoted 0 times
...
Huey
5 months ago
The entry TTL is 1 second, so it expires quickly.
upvoted 0 times
...
Cordelia
5 months ago
I practiced a similar question, and I think if the processing takes too long, we might end up with a null payload or something like that.
upvoted 0 times
...
Dahlia
5 months ago
I’m a bit confused about the expiration interval. Does it mean the object is still available for 30 seconds after being stored?
upvoted 0 times
...
Christoper
6 months ago
This kind of question seems familiar; I think if the object expires before retrieval, we might get a key not found error.
upvoted 0 times
...
Nydia
6 months ago
I remember that the TTL is really short, just one second, so I'm not sure how that interacts with the 10 seconds processing time.
upvoted 0 times
...
Galen
6 months ago
I'm a bit confused by the different time constraints at play here. I'll need to make sure I fully understand how the Mute Object Store works before I can confidently select the right answer.
upvoted 0 times
...
Wade
6 months ago
Okay, let's think this through. The 30-second expiration interval means the object should still be in the store, but the 1-second TTL means it might have expired by the time it's retrieved. I'll have to weigh the options carefully.
upvoted 0 times
...
Eladia
6 months ago
Hmm, the 10-second processing time between os'store and os:retrieve is key here. Given the 1-second TTL, I'm guessing the original payload won't be available by the time it reaches os:retrieve.
upvoted 0 times
...
Audry
6 months ago
This seems like a tricky one. I'll need to carefully consider the time constraints and the Mute Object Store's configuration to determine the outcome.
upvoted 0 times
...
Kindra
7 months ago
I'm leaning towards originalPayload as the result.
upvoted 0 times
...
Karl
7 months ago
I believe it will be OS:KEY_NOT_FOUND.
upvoted 0 times
...
Zack
7 months ago
I think the result will be nullPayload.
upvoted 1 times
...

Save Cancel