What is the next step to preseive the current vCore usage, but still allow the Mule application to be managed by API Manager?

An API implementation has been deployed to CloudHub and now needs to be governed. IT will not allocate additional vCore for a new Mule application to act as an API proxy.

What is the next step to preseive the current vCore usage, but still allow the Mule application to be managed by API Manager?
A . Register the same API implementation in Runtime Manager to connect to API Manager
B . Modify the API implementation to use auto-discovery to register with API Manager
C . Upload the Mule application’s JAR file to the API instance in API Manager
D . Deploy the same API implementation behind a VPC and configure the VPC to connect to API Manager

View Answer

Answer: B

Explanation:

Correct answer is Modify the API implementation to use auto-discovery to register with API Manager

API Autodiscovery

Configuring autodiscovery allows a deployed Mule runtime engine (Mule) application to connect with API Manager to download and manage policies and to generate analytics data. Additionally, with autodiscovery, you can configure your Mule applications to act as their own API proxy.

When autodiscovery is correctly configured in your Mule application, you can say that your application’s API is tracked by (green dot) or paired to API Manager. You can associate an API in a Mule setup with only one autodiscovery instance at a given time.

MuleSoft Doc Ref: https://docs.mulesoft.com/api-manager/2.x/api-auto-discovery-new-concept