Salesforce Updated MuleSoft-Integration-Architect-I Exam Questions and Answers by ammar

Explanation

* Resilience testing is a type of software testing that observes how applications act under stress. It's meant to ensure the product's ability to perform in chaotic conditions without a loss of core functions or data; it ensures a quick recovery after unforeseen, uncontrollable events.

* In case an API invocation fails — even after a certain number of retries — it might be adequate to invoke a different API as a fallback. A fallback API, by definition, will never be ideal for the purpose of the API client, otherwise it would be the primary API.

* Here are some examples for fallback APIs:

- An old, deprecated version of the same API.

- An alternative endpoint of the same API and version (e.g. API in another CloudHub region).

- An API doing more than required, and therefore not as performant as the primary API.

- An API doing less than required and therefore forcing the API Client to offer a degraded service, which is still better than no service at all.

* API clients implemented as Mule applications offer the ‘Until Successful Scope and Exception’ strategies at their disposal, which together allow configuring fallback actions such as a fallback API invocation.

* All HTTP response status codes within the 3xx category are considered redirection messages. These codes indicate to the user agent (i.e. your web browser) that an additional action is required in order to complete the request and access the desired resource

Hence correct answer is Redirect client requests through an HTTP 303 temporary redirect status code to the fallback API whenever the Order API is unavailable

To achieve efficient caching and reduce redundant database transactions, the following strategy can be implemented:

On Table Row Listener: Implement an "On Table Row" trigger on the employees' table. This trigger will monitor changes (inserts, updates, deletes) in the employee records.

Invalidate Cache: Upon detecting changes in the employees' table, the trigger will call a flow to invalidate the current cache.

Object Store for Caching: Utilize MuleSoft's object store to cache the employee data. This store can hold the data for quick retrieval.

Set Expiration Interval: Configure the expiration interval for the cached data to ensure it is cleared when necessary. For this scenario, since we are invalidating cache on actual data changes, setting the expiration interval to empty can be suitable.

Return Cached Data: If there are no updates, the cached response is returned, reducing database load.

MuleSoft Documentation on Object Store

Caching Strategies

A synchronous invocation of a RESTful API using HTTP to get an individual customer record from a single system exemplifies the request-reply interaction pattern. In this pattern, a client sends a request to a service and waits for a response. The interaction is synchronous because the client expects an immediate reply and is blocked until it receives the response.

This pattern is common in scenarios where the client needs to retrieve specific data or perform an action that requires immediate feedback from the server, such as retrieving a customer record from a database.

References

MuleSoft Integration Patterns Documentation

Request-Reply Pattern Overview

https://help.mulesoft.com/s/feed/0D52T000055pzgsSAA.