What is true about automating interactions with Anypoint Platform using tools such as Anypoint Platform REST API's, Anypoint CLI or the Mule Maven plugin?

What is true about automating interactions with Anypoint Platform using tools such as Anypoint Platform REST API’s, Anypoint CLI or the Mule Maven plugin?

What is true about automating interactions with Anypoint Platform using tools such as Anypoint Platform REST API’s, Anypoint CLI or the Mule Maven plugin?
A . By default, the Anypoint CLI and Mule Maven plugin are not included in the Mule runtime
B . Access to Anypoint Platform API;s and Anypoint CLI can be controlled separately thruough the roles and permissions in Anypoint platform, so that specific users can get access to Anypoint CLI while others get access to the platform API’s
C . Anypoint Platform API’s can only automate interactions with CloudHub while the Mule maven plugin is required for deployment to customer hosted Mule runtimes
D . API policies can be applied to the Anypoint platform API’s so that only certain LOS’s has access to specific functions

Answer: A

Explanation:

Correct answer is By default, the Anypoint CLI and Mule Maven plugin are not included in the Mule runtime Maven is not part of runtime though it is part of studio. You do not need it to deploy in order to deploy your app. Same is the case with CLI.