A team has steady, high GPU demand for three years, and data that must stay on site. What fits?
Why A is the answer
On-premises
Steady use and data location favor owned infrastructure.
In detail
- Steady use and data location favor owned infrastructure.
- Run the cost model for your own use.
Use case
An illustrative scenario, not a real incident.
A hospital has steady GPU demand, and patient data must stay on site.
See it in different ways
flowchart TD
A{"Is demand steady and high?"} -->|Yes| B["On-premises can cost less over time"]
A -->|"No, it comes in bursts"| C["Cloud gives flexibility"]
D{"Are there data residency limits?"} -->|Yes| BstateDiagram-v2 [*] --> Demand Demand --> OnPremises: steady and high Demand --> Cloud: short bursts OnPremises --> DataRules Cloud --> DataRules DataRules --> [*]
flowchart TD
Q{"What is the demand?"}
Q -->|"Steady, data must stay"| A0["On-premises"]
Q -->|"Occasional bursts"| A1["Cloud"]Key point: Steady use and local data favor on-premises.
Why the other options are wrong
- B. Short-term cloud instances, started by hand
- That costs more over three years.
- C. A public cloud in another country
- That breaks the data rule.
- D. A burst contract with a GPU cloud provider
- Burst contracts do not suit steady use.