What is required before an API implemented using the components of Anypoint Platform can be managed and governed (by applying API policies) on Anypoint
Platform?
What is required before an API implemented using the components of Anypoint Platform can be managed and governed (by applying API policies) on Anypoint
Platform?
Before an API implemented using the components of Anypoint Platform can be managed and governed by applying API policies on Anypoint Platform, the API must be published to Anypoint Exchange, and a corresponding API instance ID must be obtained from API Manager to be used in the API implementation.
Answer is B. Reason 1: API must be published to Anypoint exchange. This generates an instance ID. This instance ID needs to be configured in API implementation (Mule Project) using Global Configuration - API Autodiscovery. Why not A? : Because RAML is only for REST, yet Mule supports SOAP based services which is not supported by Design Center. Also, it is not mandatory to create the RAML in API Designer like the option suggests by use of the word "must". Anypoint Studio can be used to create the RAML as well. Point is, you need to publish in Exchange and you need to add the instance ID to your app for API manager to be able to access it.
B. The API must be published to Anypoint Exchange and a corresponding API instance ID must be obtained from API Manager to be used in the API implementation
B. The API must be published to Anypoint Exchange and a corresponding API instance ID must be obtained from API Manager to be used in the API implementation
it should be B
It should be B. It should not be A cause you can upload a RAML file directly to exchange rather than using API Designer.
It should be B
B. The API must be published to Anypoint Exchange and a corresponding API instance ID must be obtained from API Manager to be used in the API implementation
B correct