Salesforce Exam MuleSoft Integration Architect I Topic 3 Question 5 Discussion

Actual exam question for Salesforce's MuleSoft Integration Architect I exam

Question #: 5
Topic #: 3

[All MuleSoft Integration Architect I 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.

AUse 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.

BUse an On Table Row operation configured with the Employees table and cail invalidate cache. Use an object-store-caching-strategy and the default expiration interval.

CUse 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.

DUse 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.

Show Suggested Answer

Suggested Answer: A

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

Limited Time Offer

25%

Off

Get Premium MuleSoft Integration Architect I Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Alayna

11 months 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

10 months ago

I think option A sounds like the best approach to minimize redundant transactions and keep the data fresh.

upvoted 0 times

...

Chaya

10 months 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

11 months 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

11 months 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

11 months 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

11 months 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

10 months 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

10 months 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

10 months 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

10 months 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

10 months 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

11 months 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

11 months 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

11 months 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

11 months ago

I agree, D seems like the most efficient option for minimizing redundant transactions.

upvoted 0 times

...

Margret

11 months 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

11 months 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

11 months ago

B: Agreed, simplicity is key in this scenario.

upvoted 0 times

...

Lili

11 months 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

...