Open-data crunch seasons are short, but the city previously bought large always-on clusters. Which cloud cost-flexibility idea applies?
Select an answer to reveal the explanation.
Short Explanation
Buying a banquet hall you use two weekends a year is pricey CapEx theater. Cloud consumption lets seasonal open-data crunches rent capacity when needed. Flexibility beats idle iron for short seasons.
Full Explanation
Cloud cost models often emphasize consumption or operational spending over large up-front capital clusters that sit idle between civic peaks. Seasonal open-data workloads fit that flexibility without requiring a full FinOps specialty exam. Permanent oversized CapEx, budget denial, or unshareable one-off hardware purchases miss the Chapter 9 benefit framing. Cities should match spend tempo to analytics tempo.