An organization has several APIs that accept JSON data over HTTP POST. The APIs are all publicly available and are associated with several mobile applications and web applications.
The organization does NOT want to use any authentication or compliance policies for these APIs, but at the same time, is worried that some bad actor could send payloads that could somehow compromise the applications or servers running the API implementations.
What out-of-the-box Anypoint Platform policy can address exposure to this threat?

• A.Shut out bad actors by using HTTPS mutual authentication for all API invocations
• B.Apply an IP blacklist policy to all APIs; the blacklist will Include all bad actors
• C.Apply a Header injection and removal policy that detects the malicious data before it is used
• D.Apply a JSON threat protection policy to all APIs to detect potential threat vectors

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

Comment: *

Name: *

Email: *

Verification: *

What best explains the use of auto-discovery in API implementations?

• A.It makes API Manager aware of API implementations and hence enables it to enforce policies
• B.It enables Anypoint Studio to discover API definitions configured in Anypoint Platform
• C.It enables Anypoint Exchange to discover assets and makes them available for reuse
• D.It enables Anypoint Analytics to gain insight into the usage of APIs

Comment: *

Name: *

Email: *

Verification: *

A System API is designed to retrieve data from a backend system that has scalability challenges. What API policy can best safeguard the backend system?

• A.IPwhitelist
• B.SLA-based rate limiting
• C.Auth 2 token enforcement
• D.Client ID enforcement

Comment: *

Name: *

Email: *

Verification: *

When designing an upstream API and its implementation, the development team has been advised to NOT set timeouts when invoking a downstream API, because that downstream API has no SLA that can be relied upon.
This is the only downstream API dependency of that upstream API.

• A.An SLA for the upstream API CANNOT be provided
• B.Assume the downstream API runs uninterrupted without crashing. What is the impact of this advice?
• C.A default timeout of 500 ms will automatically be applied by the Mule runtime in which the upstream API implementation executes
• D.The invocation of the downstream API will run to completion without timing out
• E.A toad-dependent timeout of less than 1000 ms will be applied by the Mule runtime in which the downstream API implementation executes

Comment: *

Name: *

Email: *

Verification: *