New Year Sale 2026! 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 5 Question 27 Discussion

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

A developer deploys an API to CloudHub and applies an OAuth policy on API Manager. During testing, the API response is slow, so the developer reconfigures the API so that the out-of-the-box HTTP Caching policy is applied first, and the OAuth API policy is applied second.

What will happen when an HTTP request is received?

Show Suggested Answer Hide Answer
Suggested Answer: B

When an HTTP request is received and the HTTP Caching policy is applied first, it checks if there is a cached response for that request in Object Store. If there is a cache hit, meaning that a valid cached response exists, then only the HTTP Caching policy is evaluated and the cached response is returned to the caller without invoking the OAuth policy or the API implementation. If there is a cache miss, meaning that no valid cached response exists, then both the HTTP Caching policy and the OAuth policy are evaluated before invoking the API implementation. Reference: https://docs.mulesoft.com/api-manager/2.x/http-caching-policy#policy-ordering


by Corinne at Mar 19, 2025, 02:25 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
Nidia
2 months ago
Wait, are we sure about that? I thought both policies might still get checked.
upvoted 0 times
...
Lenora
2 months ago
Totally agree with you, B makes the most sense!
upvoted 0 times
...
Luz
3 months ago
I think option B is correct. Only the HTTP Caching policy gets evaluated on a cache hit.
upvoted 0 times
...
Shay
3 months ago
Yup, that's correct! D is the way to go for cache misses.
upvoted 0 times
...
Jettie
3 months ago
Just to clarify, in a cache miss, both policies are evaluated, right?
upvoted 0 times
...
Marcos
3 months ago
I remember a similar question where only the caching policy was evaluated on a cache hit. So, I’m leaning towards option B, but I’m not 100% confident.
upvoted 0 times
...
Lai
3 months ago
I think I recall something about cache misses leading to the API implementation being called, but I’m confused about whether the OAuth policy gets evaluated in that case.
upvoted 0 times
...
Claribel
4 months ago
I’m not entirely sure, but I feel like both policies get evaluated regardless of the cache hit or miss. It seems like that’s what we practiced in class.
upvoted 0 times
...
Michell
4 months ago
I remember that in caching scenarios, if there's a cache hit, we usually don't need to evaluate other policies like OAuth. So, I think option B might be correct.
upvoted 0 times
...
Oretha
4 months ago
I feel pretty confident about this. The question is testing our understanding of how the policies are applied in sequence. As long as I remember that the caching policy comes first, I think I can nail this.
upvoted 0 times
...
Lucy
4 months ago
I'm not totally sure about this one. I'll need to walk through the different scenarios - cache hit, cache miss, etc. - to figure out the right answer.
upvoted 0 times
...
Cassandra
4 months ago
Okay, I think I've got this. The key is that the HTTP Caching policy is evaluated first, and if there's a cache hit, the OAuth policy doesn't even get evaluated. That makes sense.
upvoted 0 times
...
Huey
5 months ago
Hmm, I'm a bit confused about how the caching and OAuth policies interact. I'll need to review the policy documentation to make sure I understand the expected behavior.
upvoted 0 times
...
Margret
5 months ago
This looks like a tricky one. I'll need to think through the order of policy evaluation and caching behavior carefully.
upvoted 0 times
...
Jules
10 months ago
I'm going with option C. If there's a cache miss, the HTTP Caching policy should evaluate first, then the API should retrieve the data and store it in the Object Store.
upvoted 0 times
Anastacia
9 months ago
That makes sense, it's important to handle caching efficiently for better performance.
upvoted 0 times
...
Talia
9 months ago
Then the API retrieves the data and stores it in the Object Store.
upvoted 0 times
...
Dannette
10 months ago
I agree, the HTTP Caching policy should be evaluated first in case of a cache miss.
upvoted 0 times
...
Stephen
10 months ago
I think option C is the correct choice.
upvoted 0 times
...
...
Katlyn
10 months ago
Ha! I bet the developer is regretting that decision to apply the OAuth policy after the HTTP Caching policy. Talk about a recipe for disaster!
upvoted 0 times
...
Kirk
10 months ago
Option D seems more logical to me. If there's a cache miss, both the OAuth and HTTP Caching policies should be evaluated before the API retrieves the data from the implementation.
upvoted 0 times
Blossom
10 months ago
I agree, it makes sense to have both policies evaluated before retrieving the data.
upvoted 0 times
...
Hannah
10 months ago
I think option D is the correct one. Both policies should be evaluated in case of a cache miss.
upvoted 0 times
...
...
Veronique
11 months ago
You're right, I didn't consider that. So the correct answer might actually be D, where both OAuth and HTTP Caching policies are evaluated in case of a cache miss.
upvoted 0 times
...
Bettina
11 months ago
I think option B is the correct answer. In the case of a cache hit, only the HTTP Caching policy should be evaluated, and the cached response should be returned to the caller.
upvoted 0 times
Fredric
9 months ago
By reconfiguring the API, the developer can optimize the performance by leveraging caching.
upvoted 0 times
...
Nikita
9 months ago
It makes sense to prioritize the HTTP Caching policy for faster responses.
upvoted 0 times
...
Nicholle
9 months ago
I agree, the HTTP Caching policy should handle the cached response in that scenario.
upvoted 0 times
...
Evangelina
9 months ago
Option B is correct. Only the HTTP Caching policy is evaluated in case of a cache hit.
upvoted 0 times
...
Veronica
9 months ago
It's important to optimize the API configuration to ensure efficient performance during testing.
upvoted 0 times
...
Gearldine
10 months ago
By applying the HTTP Caching policy first, it helps improve the API response time for cached requests.
upvoted 0 times
...
Tiffiny
10 months ago
I agree, the cached response should be returned to the caller without evaluating the OAuth policy.
upvoted 0 times
...
Basilia
10 months ago
Option B is correct. Only the HTTP Caching policy is evaluated in case of a cache hit.
upvoted 0 times
...
...
Toshia
11 months ago
That makes sense, but wouldn't the OAuth policy also be evaluated in case of a cache miss?
upvoted 0 times
...
Veronique
11 months ago
I disagree, I believe the answer is C. The HTTP Caching policy is evaluated in case of a cache miss, and the data is retrieved from the API implementation.
upvoted 0 times
...
Toshia
11 months ago
I think the answer is B, because only the HTTP Caching policy is evaluated in case of a cache hit.
upvoted 0 times
...

Save Cancel