ANS-C01 Question 438
Single answerYour organization has implemented a hybrid cloud architecture using AWS Direct Connect to connect its on-premises data center to AWS. Recently, some applications hosted in AWS have been experiencing high latency when communicating with the on-premises environment. Upon investigation, you found that traffic destined for AWS services like Amazon S3 and DynamoDB from on-premises is taking a suboptimal path through the public internet instead of the Direct Connect connection. How can you ensure that such traffic is routed optimally through the Direct Connect connection?
- A
Enable Direct Connect Gateway and attach it to your VPC and on-premises environments.
- B
Advertise the AWS public IP prefixes to your on-premises network through BGP over the Direct Connect connection.
- C
Use AWS Transit Gateway to route traffic between your on-premises environment and AWS services.
- D
Create a static route in your on-premises router to direct AWS public IP ranges through the Direct Connect connection.
Show answer and explanation
Correct answer: B
Explanation
To ensure AWS public service traffic such as S3 or DynamoDB is routed through your Direct Connect connection, you need to advertise AWS public IP prefixes via BGP over the Direct Connect connection. This allows your on-premises network to recognize these prefixes and route traffic directly through Direct Connect instead of defaulting to the public internet.
- A. Incorrect.
Direct Connect Gateway is used to connect multiple VPCs across regions or accounts, but it does not resolve the issue of routing AWS public service traffic via Direct Connect.
- B. Correct.
Advertising AWS public IP prefixes via BGP ensures that AWS public services traffic from your on-premises network is routed through the Direct Connect connection instead of taking the public internet path.
- C. Incorrect.
AWS Transit Gateway is used for interconnecting VPCs and on-premises networks, but it does not directly optimize routing for AWS public service traffic over Direct Connect.
- D. Incorrect.
Creating static routes for AWS public IP ranges in your on-premises router is not recommended due to the complexity and dynamic nature of AWS IP ranges, which are subject to frequent changes.