A Mule application exposes an HTTPS endpoint and is deployed to the CloudHub Shared Worker Cloud. All traffic to that Mule application must stay inside the AWS VPC.
To what TCP port do API invocations to that Mule application need to be sent?

• A.443
• B.8081
• C.8091
• D.8092

Comment: *

Name: *

Email: *

Verification: *

What CANNOT be effectively enforced using an API policy in Anypoint Platform?

• A.Guarding against Denial of Service attacks
• B.Maintaining tamper-proof credentials between APIs
• C.Backend system overloading
• D.Logging HTTP requests and responses

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.Search Anypoint Exchange for a suitable existing fallback API, and then implement invocations to this fallback API in addition to 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: *

Due to a limitation in the backend system, a system API can only handle up to 500 requests per second. What is the best type of API policy to apply to the system API to avoid overloading the backend system?

• A.Rate limiting
• B.HTTP caching
• C.Rate limiting - SLA based
• D.Spike control

Comment: *

Name: *

Email: *

Verification: *

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

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

Comment: *

Name: *

Email: *

Verification: *