Support deployment, operations, and CI/CD across environments
The exam tests how an integration moves from source control to each environment with repeatable configuration, tests, and observability.
Pipeline rules
Keep everything in Git and build once, promoting the same artifact. Run MUnit tests and enforce a coverage gate in the pipeline. Use Maven and the Anypoint Maven plugin or Anypoint CLI to deploy. Publish contracts to Exchange and create API Manager instances per environment. Externalize properties per environment and keep secure properties out of the repository. Use separate business groups or folders for environment isolation, and separate client applications and credentials per environment.
Runtime and operations
CloudHub deployments specify region, worker size, and worker count; autoscaling and persistent queues are configuration, not code. Runtime Fabric and on-premises deployments add infrastructure concerns. Enable Anypoint Monitoring, alerts, and API functional monitoring; set log levels appropriately. Use semantic versions and autodiscovery per environment.
Worked example
A feature branch passes review and triggers a pipeline: MUnit with 80 percent coverage, Maven build, deploy to Sandbox, smoke test, manual approval, then deploy the identical artifact to Production with production properties and credentials. Reasoning: identical artifacts remove build drift, and smoke tests catch environment-specific wiring.
Traps
Building separately per environment; secrets in Git; manual API Manager changes that drift; deploying SNAPSHOT versions; no rollback plan; skipping smoke tests; reusing client credentials across environments.