An API implementation has been deployed to CloudHub and now needs to be governed. IT will not allocate additional vCores for a new Mule application to act as an API proxy.
What is the next step to preserve the current vCore usage, but still allow the Mule application to be managed by API Manager?
To govern the deployed API implementation without allocating additional vCores for a new Mule application to act as a proxy, the existing API implementation should be modified to use auto-discovery to register with API Manager. This approach allows the API to be managed directly by API Manager without the need for additional resources.
After a Mule app (an API implementation) has been deployed, it is possible to create a proxy for it, but the proxy would use an additional vCore. In case that it is not wanted to use separate vCore allocations for the API proxy, it is possible to modify an implementation to use something MuleSoft calls auto-discovery to register the app with API Manager, to be able to govern it as there was na API proxy. E-Schatz - https://www.friendsofmulesoft.com/en/news/exam_questions/exam_question_ms_21_020_for_mulesoft_certified_developer_mcd_level_1/62/
Answer A: Modify the API implementation to use auto-discovery to register with API Manager
Answer A is correct. I agree with ibrahim_akbiyik