Nightly work can wait and should cost less. Which category fits?
Why B is the answer
Batch
Batch is the discounted asynchronous category.
In detail
- Batch suits work that can wait, at a lower cost.
- Keep live traffic on a standard deployment.
Use case
An illustrative scenario, not a real incident.
A retailer scores reviews overnight. Nobody waits for the results, so Batch costs less.
See it in different ways
flowchart TD
A["Start: Global Standard"] --> B{"Why change?"}
B -->|"Data must stay in a zone"| C["Data Zone"]
B -->|"Reserved throughput"| D["Provisioned"]
B -->|"Work can wait"| E["Batch"]mindmap
root((Deployment types))
Global
Default start
Global Standard
Data Zone
Stays in a zone
Provisioned
Reserved capacity
Batch
Can wait, costs less
Developer
Evaluationflowchart TD
Q{"When are results needed?"}
Q -->|"Now"| A0["Standard"]
Q -->|"Later"| A1["Batch"]Key point: Work that can wait suits Batch.
Why the other options are wrong
- A. Provisioned, so that capacity is always reserved
- Reserved capacity costs more when it sits idle.
- C. Standard, in a single region of your choice
- Standard pays the normal rate for speed you do not need.
- D. Developer, because it is meant for evaluation
- Developer is for evaluation.