M5 - Mulesoft Deploying apis

What is the purpose of API autodiscovery?

• Enables API Manager to dicover the published API on anypoint Exchange

• Allows the Mule application to be automatically discovered on Anypoint Exchange

• Enables an API to be directly managed in API Manager

• Allows a deployed Mule application to connect with API Manager to download policies and act as its onw API Proxy

How many Mule applications can run on a CloudHub worker

• At most one

• At least one

• Depends on the vCores of the worker

• Depends on the number of CloudHub workers configured

What does an API proxy application NOT do?

• Determine which request Mule event is allowed to pass through to the API backend service

• Apply runtime policies to enforce governance

• Determine which response Mule event is allowed to pass through to the API backend service

• Meter the traffic flowing through the proxy

What does the Mule runtime use to enforce policies and limit access to APIs?

• Anypoint Access Control

• The proxy created by API Manager

• API Manager

• The Mule runtime's embedded API Gateway

API Manager has been configured to enforce an SLA policy and the RAML spec has been updated with the required client_id and client_secret header requirements.

The new RAML spec has been published to Anypoint Exchange

What is the next step to gain access to the API?

• POST a JSON object to the /api/register endpoint of the API proxy

• Request access to the API in Anypoint Exchange

• Email the organization administrator to request access to the API

• Add a client application to the Anypoint Platform organization.