A mayor’s innovation office wants staff to experiment with new citizen apps without waiting on capital budgets for servers. Which AWS Cloud benefit best describes that freedom?
Select an answer to reveal the explanation.
Short Explanation
Innovation stalls when every idea waits on a capital request for iron. Agility in the cloud means spinning up a citizen-app pilot without buying a rack first—and changing course just as fast. That CapEx-light experimentation is the benefit the mayor’s office is after.
Full Explanation
Agility is the AWS Cloud benefit that best describes a mayor's innovation office spinning up citizen-app pilots without waiting on capital budgets for servers. Staff can try and change workloads quickly because capacity is consumed as a service rather than purchased, racked, and depreciated as heavy upfront CapEx.
Mandatory purchase of five years of servers before any pilot may begin recreates the CapEx gate that stalls innovation. Locking every experiment to a single physical host that staff must rack first adds facilities work before learning can start. High availability that only covers disk mirroring inside one closet addresses a different concern—failure resilience—not the freedom to experiment without buying iron.
Exam caveat: Agility on CLF-C02 emphasizes faster experimentation and change with less upfront hardware commitment; do not substitute high availability or Reserved Instance terms when the stem is about pilots and CapEx friction. Operational check: stand up a short-lived pilot account or project with budgets and tags, launch a minimal citizen-app prototype, iterate once without a hardware PO, then tear it down and show finance the OpEx line items instead of a five-year asset.