Salesforce Certified MuleSoft Platform Architect Practice Questions

Salesforce Certified MuleSoft Platform Architect exam preparation

Salesforce Certified MuleSoft Platform Architect practice questions in English: 119 questions with explanations. The mock exam has 60 questions and 120 minutes.

Salesforce Certified MuleSoft Platform Architect free question 9 / 10 · Domain 8: Meeting API quality goals

On a two-node Mule cluster, an expensive quote calculation is cached with a Cache scope. Identical requests that miss the cache often arrive together, and measurements show long waits in front of the cache. Which statement matches the caching strategy documentation?

  1. Synchronization is on by default, but in a cluster a node has its own cache, so no waiting can occur
  2. Access is synchronized by default and this hurts most in a cluster, so it can be turned off with synchronized set to false
  3. Access is not synchronized by default, so the waits come from outside the cache and changing the strategy would not reduce them
  4. Synchronization is not switchable, as the second request for the same input could not write to the cache and would fail
Show the answer and explanation

Answer: B

Why this is correct
By default Mule synchronizes access to a cache so that several message processors, on the same or different Mule instances, cannot use it at the same time with unexpected results. A synchronized cache is locked while a processor modifies it, so a second processor waits for the first to calculate the value. The page warns that synchronization affects performance and that the impact is most severe in cluster mode. You can disable it by defining the synchronized property on the caching strategy, accepting that two results for one input may be produced and only the last one stored.

Why the other options are wrong
"Access is not synchronized by default, so the waits come from outside the cache and changing the strategy would not reduce them" … The page says that by default Mule synchronizes access to a cache.
"Synchronization is on by default, but in a cluster a node has its own cache, so no waiting can occur" … The page says the performance impact is most severe in cluster mode, so waits do occur there.
"Synchronization is not switchable, as the second request for the same input could not write to the cache and would fail" … The page says you can disable cache synchronization with the synchronized property. The cost is that the last value inserted overwrites the earlier one.

Synchronized access to the cache
The page's example caching strategy synchronizes access to the cache and defines a persistent Object Store to store the cached responses.

Go to the Salesforce Certified MuleSoft Platform Architect practice app (10 free questions; purchase unlocks all questions)

See the full practice set