What is a best practice when building System APIs?

• A.Document the API using an easily consumable asset like a RAML definition
• B.Model all API resources and methods to closely mimic the operations of the backend system
• C.Build an Enterprise Data Model (Canonical Data Model) for each backend system and apply it to System APIs
• D.Expose to API clients all technical details of the API implementation's interaction wifch the backend system

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: *

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 the invocation of the fallback API provides the best resilience?

• A.Redirect client requests through an HTTP 307 Temporary Redirect status code to the fallback API whenever the Order API is unavailable
• B.Search Anypoint Exchange for a suitable existing fallback API, and then implement invocations to this fallback API in addition to the Order API
• C.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 returned from the Order API
• D.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

Comment: *

Name: *

Email: *

Verification: *

What Mule application deployment scenario requires using Anypoint Platform Private Cloud Edition or Anypoint Platform for Pivotal Cloud Foundry?

• A.When it Is required to make ALL applications highly available across multiple data centers
• B.When it is required that ALL APIs are private and NOT exposed to the public cloud
• C.When regulatory requirements mandate on-premises processing of EVERY data item, including meta-data
• D.When ALL backend systems in the application network are deployed in the organization's intranet

Comment: *

Name: *

Email: *

Verification: *

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 the invocation of the fallback API provides the best resilience?

• A.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 returned from the Order API
• B.Redirect client requests through an HTTP 307 Temporary Redirect status code to the fallback API whenever the Order API is unavailable
• C.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
• D.Search Anypoint Exchange for a suitable existing fallback API, and then implement invocations to this fallback API in addition to the Order API

Comment: *

Name: *

Email: *

Verification: *