A parks mobile app team ships weekly feature updates. Leadership asks which cloud benefit best describes rapid change without hardware refresh cycles. What should the team answer?
Select an answer to reveal the explanation.
Short Explanation
Weekly park-app features should not wait on a hardware refresh calendar. Agility is the cloud benefit for changing product quickly without racking new boxes every sprint. Ship the update; leave the decade-long disk purchase story behind.
Full Explanation
Agility best describes a parks mobile app team shipping weekly feature updates without waiting on hardware refresh cycles. Cloud capacity and managed services let product change proceed on a software cadence rather than a rack-and-refresh calendar, so leadership hears "we can change the citizen experience weekly" instead of "we ship when new disks arrive."
Buying larger disks once a decade so features can only ship yearly couples product velocity to hardware refresh and is the anti-pattern agility removes. High availability that solely measures how many UPS batteries sit in a closet addresses facilities resilience metrics, not release frequency. Economies of scale that freeze the app's feature roadmap for five years misuse a cost concept as a change-management brake.
Exam caveat: Agility is about speed of change and experimentation; do not answer with HA battery counts or economies-of-scale pricing when the stem is weekly features. Operational check: measure lead time from commit to production for a parks-app feature in the cloud pipeline, confirm no hardware PO gates the release, and report cycle time to leadership against the old annual refresh baseline. Keep a simple changelog tied to citizen-visible outcomes so sponsors see agility as service improvement, not churn.