How many Mule applications can run on a CloudHub worker?

The CloudHub platform architecture is designed to run exactly one Mule application per CloudHub worker. Each worker is a dedicated instance of Mule runtime engine in the cloud. This one-to-one mapping ensures that applications are isolated from each other, with their own dedicated CPU, memory, and other resources. This isolation prevents one application's performance or failure from impacting another.

B. While it's true a worker runs at least one application, this answer is imprecise. The strict limit is one, making "At most one" the most accurate choice.

C. The number of applications per worker is a fixed architectural constraint of CloudHub and does not depend on other factors like worker size or region.

D. Option A is the correct answer, as a CloudHub worker is designed to host a single Mule application.

1. MuleSoft Documentation, "CloudHub Architecture", Section "Workers". It states, "Each worker is a dedicated instance of Mule that runs your integration application." This implies a single application per worker. (docs.mulesoft.com/runtime-manager/cloudhub-architecture#workers)

2. MuleSoft Documentation, "Deploy to CloudHub". The deployment process involves selecting an application and assigning it to one or more workers. The documentation consistently describes the model as one application running on a set of workers. (docs.mulesoft.com/runtime-manager/deploying-to-cloudhub)