What aspects of a CI/CD pipeline for Mule applications can be automated using MuleSoft-provided Maven plugins?
A. Import from API designer, compile, package, unit test, deploy, publish to Anypoint Exchange
B. Compile, package, unit test, validate unit test coverage, deploy
C. Compile, package, unit test, deploy, integration test
D. Compile, package, unit test, deploy, create associated API instances in API Manager
|
Download Printable PDF. VALID exam to help you PASS. |
 |
https://docs.mulesoft.com/mule-runtime/3.9/mule-maven-plugin-v2.2
Mule 3 supports integration test, so answer would be C.
As per Mulesoft Docs –>
The plugin allows you to:
Deploy a Mule application to a local standalone server
Run integration tests in a local standalone deployment
Deploy Mule applications to Anypoint Runtime Manager
Deploy Mule applications to CloudHub
Deploy Mule applications to a local cluster
B is the correct answer. Integration Testing is not included in maven phases and we are validating unit test coverage in our build pipelines.
C is wrong since mave does MUnit test. Integration tests are not MUnit test and therefore C is wrong.
Correct answer is B
Compile, package, unit test, validate unit test coverage, deploy
C
C is the correct answer.
B
I think it has to be B. Maven can do unit test coverage (https://docs.mulesoft.com/munit/2.3/coverage-maven-concept) and it cannot do Integration Testing (that’s outside of unit testing. It uses actual data)