Deploying and Managing APIs and Integrations7% of the exam
Deploying and redeploying applications to CloudHub
Prepare a Mule app for worker-based CloudHub (listener on 0.0.0.0 and ${http.port}, a globally unique application name), deploy it from Studio or Runtime Manager, size workers for high availability, hide sensitive properties, and predict what clients see during a zero-downtime redeploy.
Deploy applications to CloudHub.
~8 min read · 7 practice questions ·
What the exam expects
- Configure the HTTP Listener for CloudHub: host
0.0.0.0, port${http.port}. - Explain why a CloudHub application name can be rejected even when your organization never used it, and state the naming rules.
- Choose a valid way to deploy: Studio's Deploy to CloudHub, Runtime Manager's Deploy application with an uploaded JAR, or the Mule Maven plugin's deploy goal.
- Choose between more workers (horizontal, multi data center) and a bigger worker (vertical) for a high-availability requirement.
- Hide a sensitive property value from every Runtime Manager user, and know what happens to it when the app is copied from sandbox.
- Predict what clients experience during a redeploy.
Key terms:
- Worker: a dedicated instance of Mule runtime engine that runs your application on CloudHub.
${http.port}: a reserved CloudHub property the platform assigns; port 80 traffic on the app's domain is routed to it.- Safely hidden property: a property whose name shows in Runtime Manager but whose value no user can view or retrieve.
Everything here is worker-based CloudHub (CloudHub 1.0), which the exam means by "CloudHub"; CloudHub 2.0 differences are flagged.
Key facts
Listener host and port
- Detail
0.0.0.0and${http.port}
Name rules
- Detail
- 3-42 alphanumerics and dashes, globally unique, not renameable
Maven deploy
- Detail
mvn clean deploy -DmuleDeploy
Multiple workers
- Detail
- Spread across two or more data centers, round-robin load balancing
Property precedence
- Detail
- Runtime Manager values override the bundled file
Hiding a property
- Detail
- Name in
securePropertiesofmule-artifact.json
Copy from sandbox
- Detail
- Hidden values are not copied; redefine them
Redeploy
- Detail
- Old version serves until the new one is fully started
Automatic restart
- Detail
- Same worker, up to five restarts, then up to three relaunches on a new worker; never a second concurrent instance
Sources for this section (7)
- Deploy a Mule Application to CloudHub (Studio)docs.mulesoft.com (opens in a new tab)
- Deploy to CloudHubdocs.mulesoft.com (opens in a new tab)
- Deploy Applications to CloudHub Using the Mule Maven Plugindocs.mulesoft.com (opens in a new tab)
- CloudHub Architecturedocs.mulesoft.com (opens in a new tab)
- Manage Properties for Applications on CloudHubdocs.mulesoft.com (opens in a new tab)
- Safely Hide Application Propertiesdocs.mulesoft.com (opens in a new tab)
- Application Monitoring and Automatic Restartsdocs.mulesoft.com (opens in a new tab)
- What does CloudHub do when an application assigns its own value to
http.port? - Why can't you rename a CloudHub application after it is deployed?
- Why does a value on Runtime Manager's Properties tab win over the same name in a properties file bundled in the archive?
- When can a CloudHub redeploy cause one to three minutes of downtime?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the MuleSoft Developer pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 40 lessons of the MuleSoft Developer guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (7 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams