What is the most performant out-of-the-box solution in Anypoint Platform to track transaction state in an asynchronously executing long-running process implemented as a Mule application deployed to multiple CloudHub workers?

• A.Redis distributed cache
• B.java.util.WeakHashMap
• C.Persistent Object Store
• D.File-based storage

Comment: *

Name: *

Email: *

Verification: *

An organization wants to create a Center for Enablement (C4E). The IT director schedules a series of meetings with IT senior managers.
What should be on the agenda of the first meeting?

• A.Define C4E objectives, mission statement, guiding principles, a
• B.Explore API monetization options based on identified use cases through MuleSoft
• C.A walk through of common-services best practices for logging, auditing, exception handling, caching, security via policy, and rate limiting/throttling via policy
• D.Specify operating model for the MuleSoft Integrations division

Comment: *

Name: *

Email: *

Verification: *

What should be ensured before sharing an API through a public Anypoint Exchange portal?

• A.The visibility level of the API instances of that API that need to be publicly accessible should be set to public visibility
• B.The users needing access to the API should be added to the appropriate role in Anypoint Platform
• C.The API should be functional with at least an initial implementation deployed and accessible for users to interact with
• D.The API should be secured using one of the supported authentication/authorization mechanisms to ensure that data is not compromised

Correct Answer: A

Correct answer: The visibility level of the API instances of that API that need to be publicly accessible should be set to public visibility.
*****************************************
Reference:
https://docs.mulesoft.com/exchange/to-share-api-asset-to-portal

Comment: *

Name: *

Email: *

Verification: *

An API implementation is deployed on a single worker on CloudHub and invoked by external API clients (outside of CloudHub). How can an alert be set up that is guaranteed to trigger AS SOON AS that API implementation stops responding to API invocations?

• A.Implement a heartbeat/health check within the API and invoke it from outside the Anypoint Platform and alert when the heartbeat does not respond
• B.Configure a "worker not responding" alert in Anypoint Runtime Manager
• C.Handle API invocation exceptions within the calling API client and raise an alert from that API client when the API Is unavailable
• D.Create an alert for when the API receives no requests within a specified time period

Correct Answer: B

Correct answer: Configure a "Worker not responding" alert in Anypoint Runtime Manager.
*****************************************
>> All the options eventually helps to generate the alert required when the application stops responding.
>> However, handling exceptions within calling API and then raising alert from API client is inappropriate and silly. There could be many API clients invoking the API implementation and it is not ideal to have this setup consistently in all of them. Not a realistic way to do.
>> Implementing a health check/ heartbeat with in the API and calling from outside to detmine the health sounds OK but needs extra setup for it and same time there are very good chances of generating false alarms when there are any intermittent network issues between external tool calling the health check API on API implementation. The API implementation itself may not have any issues but due to some other factors some false alarms may go out.
>> Creating an alert in API Manager when the API receives no requests within a specified time period would actually generate realistic alerts but even here some false alarms may go out when there are genuinely no requests from API clients.
The best and right way to achieve this requirement is to setup an alert on Runtime Manager with a condition "Worker not responding". This would generate an alert AS SOON AS the workers become unresponsive.

Comment: *

Name: *

Email: *

Verification: *

Question 10: Skipped
An API implementation returns three X-RateLimit-* HTTP response headers to a requesting API client. What type of information do these response headers indicate to the API client?

• A.The error codes that result from throttling
• B.A correlation ID that should be sent in the next request
• C.The HTTP response size
• D.The remaining capacity allowed by the API implementation

Correct Answer: D

The remaining capacity allowed by the API implementation.
*****************************************
>>
Reference:https://docs.mulesoft.com/api-manager/2.x/rate-limiting-and-throttling-sla-based-policies#response-he

Comment: *

Name: *

Email: *

Verification: *