- Email support@dumps4free.com
An organization is designing Mule application which connects to a legacy backend. It has been reported that backend services are not highly available and experience downtime quite often. As an integration architect which of the below approach you would propose to achieve high reliability goals?
A. Alerts can be configured in Mule runtime so that backend team can be communicated when services are down
B. Until Successful scope can be implemented while calling backend API's
C. On Error Continue scope to be used to call in case of error again
D. Create a batch job with all requests being sent to backend using that job as per the availability of backend API's
Explanation
Correct answer is Untill Successful scope can be implemented while calling backend API's The Until Successful scope repeatedly triggers the scope's components (including flow references) until they all succeed or until a maximum number of retries is exceeded The scope provides option to control the max number of retries and the interval between retries The scope can execute any sequence of processors that may fail for whatever reason and may succeed upon retry
What Mule application can have API policies applied by Anypoint Platform to the endpoint exposed by that Mule application?
A. A Mule application that accepts requests over HTTP/1x
B. A Mule application that accepts JSON requests over TCP but is NOT required to provide a response.
C. A Mule application that accepts JSON requests over WebSocket
D. A Mule application that accepts gRPC requests over HTTP/2
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
A developer is examining the responses from a RESTful web service that is compliant with the Mypertext Transfer Protocol (HTTP/1.1) a8 defined by the Internet Engineering Task Force (IETF). In this HTTP/1.1-compliant web service, which class of HTTP response status codes should be specified to indicate when client requests are successfully received, understood, and accepted by the web service?
A. 3xx
B. 2xx
C. 4xx
D. 5xx
Explanation:
In an HTTP/1.1-compliant web service, the class of HTTP response status codes that indicates successful client requests is the 2xx class. These status codes signify that the client's request was successfully received, understood, and accepted by the web service. Common 2xx status codes include:
200 OK: The request was successful.
201 Created: The request was successful and a new resource was created.
202 Accepted: The request has been accepted for processing, but the processing is not yet complete.
Other status code classes like 3xx (redirection), 4xx (client errors), and 5xx (server errors) indicate different types of responses and do not signify successful request processing.
References
IETF RFC 2616: HTTP/1.1 Specification
HTTP Status Code Definitions
A Mule application uses APIkit for SOAP to implement a SOAP web service. The Mule application has been deployed to a CloudHub worker in a testing environment.
The integration testing team wants to use a SOAP client to perform Integration testing. To carry out the integration tests, the integration team must obtain the interface definition for the SOAP web service.
What is the most idiomatic (used for its intended purpose) way for the integration testing team to obtain the interface definition for the deployed SOAP web service in order to perform integration testing with the SOAP client?
A. Retrieve the OpenAPI Specification file(s) from API Manager
B. Retrieve the WSDL file(s) from the deployed Mule application
C. Retrieve the RAML file(s) from the deployed Mule application
D. Retrieve the XML file(s) from Runtime Manager
Explanation:
Reference: [Reference: https://docs.spring.io/spring-framework/docs/4.2.x/spring-framework-reference/html/integration-testing.html , , , ]
An organization plans to extend its Mule APIs to the EU (Frankfurt) region.
Currently, all Mule applications are deployed to CloudHub 1.0 in the default North American region, from the North America control plane, following this naming convention: {API-name}—{environment} (for example, Orderssapi—dev, Orders-sapi-—qa, Orders-sapi-—prod, etc.).
There is no network restriction to block communications between APIs.
What strategy should be implemented in order to deploy the same Mule APIs to the CloudHub 1.0 EU region from the North America control plane,
as well as to minimize latency between APIs and target users and systems in Europe?
A. In Runtime Manager, for each Mule application deployment, set the Region property to EU (Frankfurt) and reuse the same Mule application mame as in the North American
region.
Communicate the new urls {API-name}—{environment}.de-ci.cloudhub.io to the consuming API clients In Europe.
B. In API Manager, set the Region property to EU (Frankfurt) to create an API proxy named {API-name}—proxy—{environment} for each Mule application.
Communicate the new url {API-name}—proxy—{environment}.de-c1.cloudhub.io to the consuming API clients In Europe.
C. In Runtime Manager, for each Mule application deployment, leave the Region property
blank (default) and change the Mule application name to {API-name}—
{environment).de-cl.
Communicate the new urls {API-name}—{environment}.de-ci1.cloudhub.io to the
consuming API clients in Europe.
D. In API Manager, leave the Region property blank (default) to deploy an API proxy named {API-name}~proxy~- (environment}.de-cl for each Mule application.
Communicate the new url {API-name}—proxy—{environment}.de-cl.cloudhub.io to the consuming API clients in Europe.
Explanation:
To extend Mule APIs to the EU (Frankfurt) region and minimize latency for European users, follow these steps:
Set Region Property: In Runtime Manager, for each Mule application deployment, set the Region property to EU (Frankfurt). This deploys the application to the desired region, optimizing performance for European users.
Reuse Application Names: Keep the same Mule application names as used in the North American region. This approach maintains consistency and simplifies management.
Communicate New URLs: Inform the consuming API clients in Europe of the new URLs in the format {API-name}—{environment}.de-ci.cloudhub.io. These URLs will direct the clients to the applications deployed in the EU region, ensuring reduced latency and improved performance.
This strategy effectively deploys the same Mule APIs to the CloudHub EU region, leveraging the existing control plane in North America.
| Page 17 out of 54 Pages |
| Previous |