What is the difference between a worker and vCore?

• A. A worker is a memory unit; vCore is a CPU.
• B. A worker is a load balancer; vCore is a data storage.
• C. A worker is a dedicated Mule runtime instance; vCore is the CPU capacity allocated
• D. A worker is a deployment region; vCore is a network bandwidth.

Answer: (C)

The main idea here is that a worker is the runtime where your Mule applications actually run, while vCore is the amount of CPU power allocated to that runtime. A worker is a dedicated Mule runtime instance that executes your flows, handles processing, and scales by adding more such instances as needed. vCore represents the CPU capacity you give to that runtime, influencing how much processing power it has to handle concurrent messages. In practice, you manage performance by choosing the right worker size (which ties to the CPU available) and by scaling the number of workers. This makes sense because CPU capacity directly affects compute performance, whereas the worker is the environment that runs your apps. The other options describe memory, load balancing, data storage, region, or bandwidth, none of which define what a worker or a vCore are in this context.