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 Platform Integration Architect (Mule-Arch-202) Exam - Topic 3 Question 5 Discussion

Actual exam question for Salesforce's Salesforce Certified MuleSoft Platform Integration Architect (Mule-Arch-202) exam
Question #: 5
Topic #: 3
[All Salesforce Certified MuleSoft Platform Integration Architect (Mule-Arch-202) Questions]

An external API frequently invokes an Employees System API to fetch employee data from a MySQL database. The architect must design a caching strategy to query the database only when there Is an update to the Employees table or else return a cached response in order to minimize the number of redundant transactions being handled by the database.

Show Suggested Answer Hide Answer
Suggested Answer: A

by Mariann at May 19, 2024, 03:28 AM

Limited Time Offer

25%

Off

Get Premium Salesforce Certified MuleSoft Platform Integration Architect (Mule-Arch-202) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Ilda
3 months ago
D is the way to go, consistent and reliable!
upvoted 0 times
...
Billy
3 months ago
Wait, using a scheduler every hour? That feels off.
upvoted 0 times
...
Chery
3 months ago
C seems inefficient, why not just invalidate on updates?
upvoted 0 times
...
Stephanie
4 months ago
I think B is better, less manual work involved.
upvoted 0 times
...
Herminia
4 months ago
Option A sounds solid, hardcoding new data can be risky though.
upvoted 0 times
...
Felicidad
4 months ago
I’m leaning towards option D since it combines a fixed schedule with an expiration interval, but I’m not entirely confident about the frequency setting.
upvoted 0 times
...
Yolande
4 months ago
I practiced a similar question where we had to decide on cache invalidation methods. I feel like option B might be too basic for this scenario.
upvoted 0 times
...
Mayra
4 months ago
I think option A sounds familiar because it mentions hardcoding the new data, but that seems risky for updates.
upvoted 0 times
...
Domingo
5 months ago
I remember we discussed caching strategies in class, but I'm not sure if using a Scheduler is the best approach here.
upvoted 0 times
...
Zita
5 months ago
This is a tricky one. I'm not super familiar with the caching strategies mentioned, so I'll have to think it through carefully. I'm drawn to option C since it uses a Scheduler to invalidate the cache on a fixed frequency. That seems like a simple and reliable approach. But I'm also wondering if the 1-hour expiration in option D might be better. Hmm, I'll have to weigh the pros and cons of each.
upvoted 0 times
...
Winfred
5 months ago
Hmm, I'm a bit unsure about this one. The question mentions minimizing redundant database transactions, so I'm wondering if option A or D might be better since they set the expiration interval to 1 hour. That could help reduce the number of cache invalidations. But I'm not totally sure which one is the best approach.
upvoted 0 times
...
Lucille
5 months ago
This seems like a pretty straightforward caching problem. I think option B is the way to go - using an On Table Row operation to invalidate the cache whenever the Employees table is updated. The default expiration interval should be fine, no need to complicate things.
upvoted 0 times
...
Miss
5 months ago
Okay, let me think this through. The key here is to invalidate the cache whenever the Employees table is updated, right? So I think options B, C, and D all have the right idea there. The difference is in the expiration interval. I'm leaning towards option D since the 1-hour expiration seems like a good balance between keeping the cache fresh and not hitting the database too often.
upvoted 0 times
...
Leslee
5 months ago
I've got a good feeling about this one. The key is to understand the different validation checks and where they're performed. I think I can narrow it down to the right answer.
upvoted 0 times
...
Casey
5 months ago
I'll look for an option that suggests ongoing monitoring of drug therapy across multiple patients, not just one individual.
upvoted 0 times
...
Aleta
5 months ago
Hmm, I feel like it could also be the manifest tag, but that doesn't sound quite right for themes.
upvoted 0 times
...
Ronny
5 months ago
Hmm, I'm a bit confused about the difference between CE, PE, and P devices. I'll have to think this through carefully.
upvoted 0 times
...
Alayna
2 years ago
This question is a real head-scratcher. I'm just hoping I don't end up 'caching' my career if I get it wrong!
upvoted 0 times
Rodolfo
2 years ago
I think option A sounds like the best approach to minimize redundant transactions and keep the data fresh.
upvoted 0 times
...
Chaya
2 years ago
C) Use a Scheduler with a fixed frequency set to every hour to trigger an invalidate cache flow. Use an object-store-caching-strategy and the default expiration interval.
upvoted 0 times
...
Daren
2 years ago
A) Use an On Table Row operation configured with the Employees table, call invalidate cache, and hardcode the new Employees data to cache. Use an object-store-caching-strategy and set the expiration interval to 1 hour.
upvoted 0 times
...
...
Yong
2 years ago
Hmm, this question is a real brain-teaser. I'm going to go with option D - it seems the most robust and reliable solution.
upvoted 0 times
...
Tanja
2 years ago
C is a nice compromise, but I'd rather not rely on a scheduled job to invalidate the cache. Seems like a potential point of failure.
upvoted 0 times
...
Shawn
2 years ago
A is a bit overkill, don't you think? Hardcoding the data feels like a hack, and 1 hour is too long for a cache expiration.
upvoted 0 times
Janna
2 years ago
A is a bit overkill, don't you think? Hardcoding the data feels like a hack, and 1 hour is too long for a cache expiration.
upvoted 0 times
...
Thurman
2 years ago
Use a Scheduler with a fixed frequency set to every hour, triggering an invalidate cache flow. Use an object-store-caching-strategy and set the expiration interval to 1 hour.
upvoted 0 times
...
Kattie
2 years ago
C) Use a Scheduler with a fixed frequency set to every hour to trigger an invalidate cache flow. Use an object-store-caching-strategy and the default expiration interval.
upvoted 0 times
...
Roxanne
2 years ago
B) Use an On Table Row operation configured with the Employees table and call invalidate cache. Use an object-store-caching-strategy and the default expiration interval.
upvoted 0 times
...
Katie
2 years ago
C) Use a Scheduler with a fixed frequency set to every hour to trigger an invalidate cache flow. Use an object-store-caching-strategy and the default expiration interval.
upvoted 0 times
...
Joanne
2 years ago
B) Use an On Table Row operation configured with the Employees table and call invalidate cache. Use an object-store-caching-strategy and the default expiration interval.
upvoted 0 times
...
Marylin
2 years ago
B) Use an On Table Row operation configured with the Employees table and call invalidate cache. Use an object-store-caching-strategy and the default expiration interval.
upvoted 0 times
...
...
Gabriele
2 years ago
D is the best choice here. Scheduled invalidation with a 1-hour expiration interval ensures the cache is up-to-date without unnecessary database queries.
upvoted 0 times
Deeanna
2 years ago
I agree, D seems like the most efficient option for minimizing redundant transactions.
upvoted 0 times
...
Margret
2 years ago
D is the best choice here. Scheduled invalidation with a 1-hour expiration interval ensures the cache is up-to-date without unnecessary database queries.
upvoted 0 times
...
...
Annmarie
2 years ago
Option B seems like the way to go. Keep it simple and let the default expiration interval handle the caching.
upvoted 0 times
Izetta
2 years ago
B: Agreed, simplicity is key in this scenario.
upvoted 0 times
...
Lili
2 years ago
A: Option B seems like the way to go. Keep it simple and let the default expiration interval handle the caching.
upvoted 0 times
...
...

Save Cancel