Question 1

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

Options :

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 Permanently to inform API clients they should be calling the new API implementation

Answer: C

Question 2

In which layer of API-led connectivity, does the business logic orchestration reside?

Options :

A : System Layer

B : Experience Layer

C : Process Layer

Answer: C

Question 3

An API has been updated in Anypoint exchange by its API producer from version 3.1.1 to 3.2.0 following accepted semantic versioning practices and the changes have been communicated via the APIs public portal. The API endpoint does NOT change in the new version. How should the developer of an API client respond to this change?

Options :

A : The API producer should be requested to run the old version in parallel with the new one

B : The API producer should be contacted to understand the change to existing functionality

C : The API client code only needs to be changed if it needs to take advantage of the new features

D : The API clients need to update the code on their side and need to do full regression

Answer: C

Question 4

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

Options :

A : TRUE

B : FALSE

Answer: A

Question 5

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 :

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

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

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

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

Answer: A