A company has a distributed data processing application running on Amazon EC2 instances. The instances are deployed across two Availability Zones ( and ) in a single VPC. The application nodes constantly exchange intermediate data, totaling approximately of data transfer monthly. The nodes currently communicate using their auto-assigned public IP addresses. Which two recommendations should a solutions architect make to reduce the monthly network data transfer charges? (Select TWO.)
- Configure the application nodes to communicate using their private IP addresses instead of public IP addressesAnswer
- Launch the EC2 instances in a single Availability Zone using a cluster placement groupAnswer
- CDeploy an AWS NAT Gateway in each Availability Zone and route the inter-node traffic through them
- DAssociate Elastic IP addresses with each instance and configure the nodes to communicate using these addresses
- EEstablish a VPC Peering connection within the VPC to route the inter-node traffic
Answer
The correct recommendations are to configure the application nodes to use private IP addresses for communication and to deploy the instances in a single Availability Zone using a cluster placement group.
Configuring nodes to communicate using private IP addresses is highly cost-effective because data transfer using private IPs within the same Availability Zone is free of charge. Launching the instances in a single Availability Zone using a cluster placement group eliminates cross-Availability Zone data transfer charges entirely while maintaining the low-latency network performance required for distributed data processing.
Step-by-Step Solution
Key Concept
AWS data transfer charges vary based on the IP address type (public vs. private) and network boundaries (same Availability Zone vs. cross-Availability Zone). Using private IPs and single-AZ cluster placement groups optimizes both cost and performance for high-throughput distributed workloads.