CUR shows high data-processing charges from NAT Gateways and unexpected cross-AZ traffic between chatty microservices in a courts case-management VPC. Architects must cut networking spend without abandoning Multi-AZ for the data tier. Which optimization best addresses the waste?
Select an answer to reveal the explanation.
Short Explanation
Chatty east-west that hops AZs and hairpins NAT is pure municipal money on fire. Pull traffic local, use endpoints, keep Multi-AZ where state needs it. Putting IGWs on private subnets just relocates the pain.
Full Explanation
Networking cost optimization targets unnecessary cross-AZ chatter and NAT data processing by redesigning service locality, adopting gateway/interface endpoints for AWS APIs, and trimming egress that need not traverse NAT—while preserving Multi-AZ for databases and other stateful tiers. Single-AZ collapse for everything harms reliability; IGWs on private subnets and self-peering are not valid fixes for these cost drivers.