hard20 pts · first answer countscost-optimizationnetwork-design

Unexpected data transfer bill

After spreading a chatty microservice system across three AZs for high availability, the monthly bill jumps even though instance counts did not change. What is the most likely cause and a good mitigation?

A.Cross-AZ data transfer charges; use zone-aware routing so services prefer same-AZ targets while keeping multi-AZ capacityB.Internet gateway hourly charges; remove the internet gatewayC.Elastic Load Balancer idle charges; delete the load balancerD.IAM API call charges; cache IAM credentials

Discussion 0

Join free to post in the discussion.

Unexpected data transfer bill

Discussion 0

Related questions