Certified Integration Architect - Level 1 MAINTENANCE Exam Questions in PDF and Online

QUESTION: 11

An API implementation is being designed that must invoke an Order API which is known to repeatedly experience downtime. For this reason a fallback API is to be called when the Order API is unavailable. What approach to designing invocation of the fallback API provides the best resilience?

Redirect client requests through an HTTP 303 temporary redirect status code to the fallback API whenever the Order API is unavailable
Set an option in the HTTP Requester component that invokes the order API to instead invoke a fallback API whenever an HTTP 4XX or 5XX response status code is received from Order API
Create a separate entry for the order API in API manager and then invoke this API as a fallback API if the primary Order API is unavailable
Search Anypoint Exchange for a suitable existing fallback API and them implement invocations to their fallback API in addition to the Order API

Answer(s): A

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.

Reveal Solution Next Question

QUESTION: 12

How are the API implementation , API client, and API consumer combined to invoke and process an API?

The API consumer creates an API implementation , which receives API invocations from an API such that they are processed for an API client
The API consumer creates an API client which sends API invocations to an API such that they are processed by an API implementation
An API client creates an API consumer, which receives API invocation from an API such that they are processed for an API implementation
The API client creates an API consumer which sends API invocations to an API such that they are processed by API implementation

Answer(s): C

Explanation:

The API consumer creates an API client which sends API invocations to an API such that they areprocessed by an API implementation.
This is based on below definitions API client:
· An application component · that accesses a service · by invoking an API of that service by definition of the term API over HTTP API consumer
· A business role, which is often assigned to an individual · that develops API clients, i.e., performs the activities necessary for enabling an API client to invoke APIs API implementation
· An application component · that implements the functionality

Reveal Solution Next Question

QUESTION: 13

What Mule application can have API policies applied by Anypoint Platform to the endpoint exposed by that Mule application?

A Mule application that accepts requests over HTTP/1x
A Mule application that accepts JSON requests over TCP but is NOT required to provide a response.
A Mule application that accepts JSON requests over WebSocket
A Mule application that accepts gRPC requests over HTTP/2

Answer(s): A

Explanation:

* HTTP/1.1 keeps all requests and responses in plain text format.

* HTTP/2 uses the binary framing layer to encapsulate all messages in binary format, while still maintaining HTTP semantics, such as verbs, methods, and headers. It came into use in 2015, and offers several methods to decrease latency, especially when dealing with mobile platforms and server-intensive graphics and videos

* Currently, Mule application can have API policies only for Mule application that accepts requests over HTTP/1x

Reveal Solution Next Question

QUESTION: 14

The implementation of a Process API must change. What is a valid approach that minimizes the impact of this change on API clients?

Implement required changes to the Process API implementation so that whenever possible, the Process API's RAML definition remains unchanged
Update the RAML definition of the current Process API and notify API client developers by sending them links to the updated RAML definition
Postpone changes until API consumers acknowledge they are ready to migrate to a new Process API or API version
Implement the Process API changes in a new API implementation, and have the old API implementation return an HTTP status code 301
Moved Permanently to inform API clients they should be calling the new API implementation

Answer(s): A

Explanation:

* Option B shouldn't be used unless extremely needed, if RAML is changed, client needs to accommodate changes. Question is about minimizing impact on Client. So this is not a valid choice.

* Option C isn't valid as Business can't stop for consumers acknowledgment.

* Option D again needs Client to accommodate changes and isn't viable option.

* Best choice is A where RAML definition isn't changed and underlined functionality is changed without any dependency on client and without impacting client.

Reveal Solution Next Question

QUESTION: 15

Organization wants to achieve high availability goal for Mule applications in customer hosted runtime plane. Due to the complexity involved, data cannot be shared among of different instances of same Mule application. What option best suits to this requirement considering high availability is very much critical to the organization?

The cluster can be configured
Use third party product to implement load balancer
High availability can be achieved only in CloudHub
Use persistent object store

Answer(s): B

Explanation:

High availability is about up-time of your application A) High availability can be achieved only in CloudHub isn't correct statement. It can be achieved in customer hosted runtime planes as well
B) An object store is a facility for storing objects in or across Mule applications. Mule runtime engine (Mule) uses object stores to persist data for eventual retrieval. It can be used for disaster recovery but not for High Availability. Using object store can't guarantee that all instances won't go down at once. So not an appropriate choice.

Reference:

https://docs.mulesoft.com/mule-runtime/4.3/mule-object-stores
C) High availability can be achieved by below two models for on-premise MuleSoft implementations.
1) Mule Clustering Where multiple Mule servers are available within the same cluster environment and the routing of requests will be done by the load balancer. A cluster is a set of up to eight servers that act as a single deployment target and high-availability processing unit. Application instances in a cluster are aware of each other, share common information, and synchronize statuses. If one server fails, another server takes over processing applications.
A cluster can run multiple applications. ( refer left half of the diagram)
In given scenario, it's mentioned that 'data cannot be shared among of different instances'. So this is not a correct choice.

https://docs.mulesoft.com/runtime-manager/cluster-about
2) Load balanced standalone Mule instances The high availability can be achieved even without cluster, with the usage of third party load balancer pointing requests to different Mule servers. This approach does not share or synchronize data between Mule runtimes. Also high availability achieved as load balanced algorithms can be implemented using external load balancer. ( refer right half of the diagram)

Reveal Solution Next Question

MuleSoft Certified Integration Architect - Level 1 MAINTENANCE MuleSoft Certified Integration Architect - Level 1 MAINTENANCE Exam Questions in PDF

Free MuleSoft MuleSoft Certified Integration Architect - Level 1 MAINTENANCE Dumps Questions (page: 3)

QUESTION: 11

Explanation:

QUESTION: 12

Explanation:

QUESTION: 13

Explanation:

QUESTION: 14

Explanation:

QUESTION: 15

Explanation:

Reference: