In the same setup, how many dispatcher/publish servers are allocated to the Staging environment?

In the same setup, how many dispatcher/publish servers are allocated to the Staging environment?

• A. 2
• B. 1
• C. 0
• D. 3

Answer: (B)

Staging is kept lean to validate deployment and how things work without the cost and complexity of a full production setup. The dispatcher acts as the gateway, directing traffic to the publish tier and providing caching for content delivery. In this setup, the staging environment uses the simplest working arrangement: a dispatcher in front of the publish resources. This lets you exercise the request flow, permissions, and caching behavior while staying cost-efficient and easy to debug. You’d scale up only if you need to test higher load or redundancy, at which point you’d add more dispatchers or more publish nodes.

Staging is kept lean to validate deployment and how things work without the cost and complexity of a full production setup. The dispatcher acts as the gateway, directing traffic to the publish tier and providing caching for content delivery. In this setup, the staging environment uses the simplest working arrangement: a dispatcher in front of the publish resources. This lets you exercise the request flow, permissions, and caching behavior while staying cost-efficient and easy to debug. You’d scale up only if you need to test higher load or redundancy, at which point you’d add more dispatchers or more publish nodes.