A code-centric API documentation environment should allow API consumers to investigate and execute API client source code that demonstrates invoking one or more APIs as part of representative scenarios.
What is the most effective way to provide this type of code-centric API documentation environment using Anypoint Platform?

• A.Enable mocking services for each of the relevant APIs and expose them via their Anypoint Exchange entry
• B.Ensure the APIs are well documented through their Anypoint Exchange entries and API Consoles and share these pages with all API consumers
• C.Create API Notebooks and include them in the relevant Anypoint Exchange entries
• D.Make relevant APIs discoverable via an Anypoint Exchange entry

Correct Answer: C

Correct answer: Create API Notebooks and Include them in the relevant Anypoint exchange entries
*****************************************
>> API Notebooks are the one on Anypoint Platform that enable us to provide code-centric API documentation Reference:

Comment: *

Name: *

Email: *

Verification: *

Which of the following sequence is correct?

• A.API Client implementes logic to call an API >> API Consumer requests access to API >> API Implementation routes the request to >> API
• B.API Consumer requests access to API >> API Client implementes logic to call an API >> API routes the request to >> API Implementation
• C.API Consumer implementes logic to call an API >> API Client requests access to API >> API Implementation routes the request to >> API
• D.API Client implementes logic to call an API >> API Consumer requests access to API >> API routes the request to >> API Implementation

Comment: *

Name: *

Email: *

Verification: *

A new upstream API Is being designed to offer an SLA of 500 ms median and 800 ms maximum (99th percentile) response time. The corresponding API implementation needs to sequentially invoke 3 downstream APIs of very similar complexity.
The first of these downstream APIs offers the following SLA for its response time: median: 100 ms, 80th percentile: 500 ms, 95th percentile: 1000 ms.
If possible, how can a timeout be set in the upstream API for the invocation of the first downstream API to meet the new upstream API's desired SLA?

• A.Set a timeout of 100 ms; that leaves 400 ms for the other two downstream APIs to complete
• B.Set a timeout of 50 ms; this times out more invocations of that API but gives additional room for retries
• C.Do not set a timeout; the Invocation of this API Is mandatory and so we must wait until it responds
• D.No timeout is possible to meet the upstream API's desired SLA; a different SLA must be negotiated with the first downstream API or invoke an alternative API

Comment: *

Name: *

Email: *

Verification: *

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 API policy would be LEAST LIKELY used when designing an Experience API that is intended to work with a consumer mobile phone or tablet application?

• A.JSON threat protection
• B.IPwhitellst
• C.Client ID enforcement
• D.OAuth 2.0 access token enforcement

Comment: *

Name: *

Email: *

Verification: *