# Deploying and redeploying applications to CloudHub

*MuleSoft Developer Study Guide · Deploying and Managing APIs and Integrations · Last updated October 28, 2026 · https://www.certifyforce.com/study-guide/mulesoft-developer/deploying-and-managing-apis-and-integrations/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.

- Certification: Salesforce MuleSoft Developer
- Exam section: Deploying and Managing APIs and Integrations
- Study guide: https://www.certifyforce.com/study-guide/mulesoft-developer

**Official exam objective:**

> Deploy applications to CloudHub.

## 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

| Fact | Detail | Source |
|---|---|---|
| Listener host and port | `0.0.0.0` and `${http.port}` | [Deploy a Mule Application to CloudHub (Studio)](https://docs.mulesoft.com/studio/deploy-mule-application-task) |
| Name rules | 3-42 alphanumerics and dashes, globally unique, not renameable | [Deploy to CloudHub](https://docs.mulesoft.com/cloudhub/deploying-to-cloudhub) |
| Maven deploy | `mvn clean deploy -DmuleDeploy` | [Deploy Applications to CloudHub Using the Mule Maven Plugin](https://docs.mulesoft.com/mule-runtime/latest/deploy-to-cloudhub) |
| Multiple workers | Spread across two or more data centers, round-robin load balancing | [CloudHub Architecture](https://docs.mulesoft.com/cloudhub/cloudhub-architecture) |
| Property precedence | Runtime Manager values override the bundled file | [Manage Properties for Applications on CloudHub](https://docs.mulesoft.com/cloudhub/cloudhub-manage-props) |
| Hiding a property | Name in `secureProperties` of `mule-artifact.json` | [Safely Hide Application Properties](https://docs.mulesoft.com/cloudhub/secure-application-properties) |
| Copy from sandbox | Hidden values are not copied; redefine them | [Deploy to CloudHub](https://docs.mulesoft.com/cloudhub/deploying-to-cloudhub) |
| Redeploy | Old version serves until the new one is fully started | [CloudHub Architecture](https://docs.mulesoft.com/cloudhub/cloudhub-architecture) |
| Automatic restart | Same worker, up to five restarts, then up to three relaunches on a new worker; never a second concurrent instance | [Application Monitoring and Automatic Restarts](https://docs.mulesoft.com/cloudhub/worker-monitoring) |

## Check yourself

- 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?

## Sources

- [Deploy to CloudHub](https://docs.mulesoft.com/cloudhub/deploying-to-cloudhub)
- [Develop Applications for CloudHub](https://docs.mulesoft.com/cloudhub/developing-applications-for-cloudhub)
- [Deploy a Mule Application to CloudHub (Studio)](https://docs.mulesoft.com/studio/deploy-mule-application-task)
- [CloudHub Architecture](https://docs.mulesoft.com/cloudhub/cloudhub-architecture)
- [Safely Hide Application Properties](https://docs.mulesoft.com/cloudhub/secure-application-properties)
- [Manage Properties for Applications on CloudHub](https://docs.mulesoft.com/cloudhub/cloudhub-manage-props)
- [Deploy Applications to CloudHub Using the Mule Maven Plugin](https://docs.mulesoft.com/mule-runtime/latest/deploy-to-cloudhub)
- [Application Monitoring and Automatic Restarts](https://docs.mulesoft.com/cloudhub/worker-monitoring)

## About the full unit

The "Core concepts", "Exam traps" and "Worked scenario" sections of this unit, its 7 linked practice questions, and unlimited timed mock exams are included with the MuleSoft Developer pack (USD $19): https://www.certifyforce.com/practice-exams