To enable API Autodiscovery in a deployed Mule application, which configuration steps are required?

• A. Configure TLS settings in Studio to enable Autodiscovery.
• B. Disable Autodiscovery in Studio.
• C. Add API ID to AAD config in Studio, then add environment client ID and client secret in environment credentials in Studio.
• D. Publish the API to Exchange.

Answer: (C)

API Autodiscovery relies on the deployed runtime being able to authenticate and identify the API so it can register with the Anypoint Platform. To enable this, the runtime needs the API’s unique ID and valid OAuth credentials for the environment.

That’s why adding the API ID to the AAD configuration in Studio ties the deployment to the correct API, and why supplying the environment client ID and client secret in the environment credentials in Studio lets the deployed app obtain an access token to perform autodiscovery. Without the API ID, the platform wouldn’t know what to register; without valid environment credentials, the runtime can’t authenticate to the platform to complete the autodiscovery process.

TLS settings aren’t involved in enabling autodiscovery, and disabling it wouldn’t activate the feature. Publishing to Exchange alone doesn’t enable autodiscovery in the deployed runtime.