Salesforce MuleSoft MuleSoft-Platform-Architect-I Release Date

Page: 6 / 6

Question 24

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?

Options:

Enable mocking services for each of the relevant APIs and expose them via their Anypoint Exchange entry

Ensure the APIs are well documented through their Anypoint Exchange entries and API Consoles and share these pages with all API consumers

Create API Notebooks and include them in the relevant Anypoint Exchange entries

Make relevant APIs discoverable via an Anypoint Exchange entry

Question 25

The application network is recomposable: it is built for change because it "bends but does not break"

Options:

TRUE

FALSE

Question 26

Mule applications that implement a number of REST APIs are deployed to their own subnet that is inaccessible from outside the organization.

External business-partners need to access these APIs, which are only allowed to be invoked from a separate subnet dedicated to partners - called Partner-subnet. This subnet is accessible from the public internet, which allows these external partners to reach it.

Anypoint Platform and Mule runtimes are already deployed in Partner-subnet. These Mule runtimes can already access the APIs.

What is the most resource-efficient solution to comply with these requirements, while having the least impact on other applications that are currently using the APIs?

Options:

Implement (or generate) an API proxy Mule application for each of the APIs, then deploy the API proxies to the Mule runtimes

Redeploy the API implementations to the same servers running the Mule runtimes

Add an additional endpoint to each API for partner-enablement consumption

Duplicate the APIs as Mule applications, then deploy them to the Mule runtimes

Question 27

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?

Options:

Search Anypoint Exchange for a suitable existing fallback API, and then implement invocations to this fallback API in addition to the Order API

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

Redirect client requests through an HTTP 307 Temporary Redirect status code to the fallback API whenever the Order API is unavailable

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