A digital publishing platform hosts its content delivery tier in VPC Alpha and its logging and analytics cluster in VPC Beta, both located in the `eu-west-1` Region. Every month, the content delivery tier transfers of raw log files to the analytics cluster. The instances in both VPCs reside in private subnets. Which TWO configuration steps should a Solutions Architect recommend to achieve the most cost-effective network routing? (Select TWO.)
- Establish a VPC peering connection between VPC Alpha and VPC Beta, and update the route tables to route the log transfer traffic through the peering connection.Cevap
- Configure the content delivery instances to transfer the log files using the private IP addresses of the analytics instances in VPC Beta.Cevap
- CDeploy an AWS Transit Gateway in the region, attach both VPCs, and route the log transfer traffic through the Transit Gateway.
- DConfigure a NAT Gateway in VPC Alpha and route the traffic to the public IP addresses of the instances in VPC Beta.
- ESet up an AWS Site-to-Site VPN connection between the two VPCs using a Virtual Private Gateway in each VPC.
Cevap
Establish a VPC peering connection between VPC Alpha and VPC Beta, update the route tables to route the traffic through the peering connection, and configure the instances to communicate using their private IP addresses.
Establishing a VPC peering connection and using private IP addresses is the most cost-effective architecture. VPC peering has no setup fees, hourly attachment fees, or data processing charges. Using private IP addresses ensures that traffic remains within the AWS private network, avoiding NAT Gateway processing fees (which cost per GB) and public IP data transfer charges.
Adım Adım Çözüm
Anahtar Kavram
VPC Peering provides a cost-effective, high-bandwidth connection between VPCs in the same region without data processing fees, whereas Transit Gateway and NAT Gateways charge per-GB processing fees that escalate costs significantly for large data volumes.
Tahmini Süre:2m 0s