EU data must be processed only within the EU, but pay-per-token pricing is preferred. What fits?
Why A is the answer
Data Zone Standard
Data Zone types process data only within the specified zone, such as the EU. Global types may process in any region.
In detail
- Data Zone keeps processing within the zone.
- Standard keeps pay-per-token pricing.
- Confirm the zone covers your rules.
Use case
An illustrative scenario, not a real incident.
A European bank needs EU-only processing and pay-per-token pricing. Data Zone Standard meets both.
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{"Must data stay in the EU?"}
Q -->|"Yes, pay per token"| A0["Data Zone Standard"]
Q -->|"No"| A1["Global Standard"]Key point: Data Zone keeps processing in the zone.
Why the other options are wrong
- B. A Developer deployment type
- Developer is not for production.
- C. Global Batch, for lower processing costs
- Global Batch is also not limited to the EU.
- D. Global Standard, because every region is covered
- Global can process in any region.