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

How can the application of a rate limiting API policy be accurately reflected in the RAML definition of an API?

• A.By refining the resource definitions by adding a description of the rate limiting policy behavior
• B.By refining the request definitions by adding a remaining Requests query parameter with description, type, and example
• C.By refining the response definitions by adding the out-of-the-box Anypoint Platform rate-limit-enforcement securityScheme with description, type, and example
• D.By refining the response definitions by adding the x-ratelimit-* response headers with description, type, and example

Correct Answer: D

Correct answer: By refining the response definitions by adding the x-ratelimit-* response headers with description, type, and example
*****************************************

References:
https://docs.mulesoft.com/api-manager/2.x/rate-limiting-and-throttling#response-headers
https://docs.mulesoft.com/api-manager/2.x/rate-limiting-and-throttling-sla-based-policies#response-headers

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.Logging HTTP requests and responses
• D.Backend system overloading

Comment: *

Name: *

Email: *

Verification: *

An organization wants MuleSoft-hosted runtime plane features (such as HTTP load balancing, zero downtime, and horizontal and vertical scaling) in its Azure environment. What runtime plane minimizes the organization's effort to achieve these features?

• A.Anypoint Runtime Fabric
• B.Anypoint Platform for Pivotal Cloud Foundry
• C.CloudHub
• D.A hybrid combination of customer-hosted and MuleSoft-hosted Mule runtimes

Comment: *

Name: *

Email: *

Verification: *

Refer to the exhibit. An organization is running a Mule standalone runtime and has configured Active Directory as the Anypoint Platform external Identity Provider. The organization does not have budget for other system components.

What policy should be applied to all instances of APIs in the organization to most effecuvelyKestrict access to a specific group of internal users?

• A.Apply a basic authentication - LDAP policy; the internal Active Directory will be configured as the LDAP source for authenticating users
• B.Apply a client ID enforcement policy; the specific group of users will configure their client applications to use their specific client credentials
• C.Apply an IP whitelist policy; only the specific users' workstations will be in the whitelist
• D.Apply an OAuth 2.0 access token enforcement policy; the internal Active Directory will be configured as the OAuth server

Comment: *

Name: *

Email: *

Verification: *