A water utility wants to launch a leak-reporting app simultaneously for three counties without opening three datacenters. Which AWS Cloud benefit most directly enables that plan?
Select an answer to reveal the explanation.
Short Explanation
Three counties should not mean three construction projects. AWS lets the utility deploy once and reach multiple places without owning a datacenter in each county. That global reach plus speed is the benefit—not three basement builds.
Full Explanation
Global reach combined with rapid multi-location deployment lets a water utility launch a leak-reporting app for three counties without opening three datacenters. AWS Regions and on-demand resources support serving multiple geographies from cloud infrastructure the utility does not have to build, staff, or maintain in each county.
Building a new staffed datacenter in each county before any app launch maximizes facilities CapEx and timeline for a software service. Limiting the app to one basement server that all counties must VPN into creates a single point of failure and poor citizen UX for public leak reporting. Requiring separate hardware bids for every county's identical stack multiplies procurement work without adding cloud reach.
Exam caveat: Global reach and speed of deployment often appear together in multi-jurisdiction civic scenarios; the wrong answers usually reintroduce per-site datacenters or VPN-only access patterns. Operational check: deploy the leak-reporting app so citizens in each county can reach it over the public internet with acceptable latency, confirm no county-specific basement VPN is required for residents, and tag costs so each county's share of OpEx is visible to finance. Record the go-live checklist so future multi-county launches reuse the same pattern.