What is true about automating interactions with Anypoint Platform using tools such as Anypoint Platform REST APIs, Anypoint CU, or the Mule Maven…

Correct Answer: By default, the Anypoint CLI and Mule Maven plugin are NOT included in the Mule

runtime, so are NOT available to be used by deployed Mule applications

*****************************************

>> We CANNOT apply API policies to the Anypoint Platform APIs like we can do on our custom

written API instances. So, option suggesting this is FALSE.

>> Anypoint Platform APIs can be used for automating interactions with both CloudHub and

customer-hosted Mule runtimes. Not JUST the CloudHub. So, option opposing this is FALSE.

>> Mule Maven plugin is NOT mandatory for deployment to customer-hosted Mule runtimes. It just

helps your CI/CD to have smoother automation. But not a compulsory requirement to deploy. So,

option opposing this is FALSE.

>> We DO NOT have any such special roles and permissions on the platform to separately control

access for some users to have Anypoint CLI and others to have Anypoint Platform APIs. With proper

general roles/permissions (API Owner, Cloudhub Admin etc..), one can use any of the options

(Anypoint CLI or Platform APIs). So, option suggesting this is FALSE.

Only TRUE statement given in the choices is that - Anypoint CLI and Mule Maven plugin are NOT

included in the Mule runtime, so are NOT available to be used by deployed Mule applications.

Maven is part of Studio or you can use other Maven installation for development.

CLI is convenience only. It is one of many ways how to install app to the runtime.

These are definitely NOT part of anything except your process of deployment or automation.