Aggregating Direct Connections for Enhanced Bandwidth
Question
Your company is migrating an entire project to AWS.
However, as certain legacy databases are too old to be migrated, your team has established two direct connections (10 gigabits) to link the on-premises data center with various AWS services such as S3, EC2, Lambda, etc.
Your lead asks you to aggregate the two direct connections ( that use the same AWS device ) to increase the bandwidth.
Which combination of steps should you take to fulfill this requirement? (Select TWO)
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answer - A, C.
As this case needs to aggregate the two direct connections to increase the bandwidth, Direct Connect LAG should be considered.
To establish a LAG connection, it needs the below steps:
1, Create a new link aggregation group (LAG).
2, Associate existing connections or new connections with the LAG.Details can be checked in https://docs.aws.amazon.com/directconnect/latest/UserGuide/lags.html.
Option A is correct: AWS Direct Connect supports LAG which uses the Link Aggregation Control Protocol (LACP) to aggregate multiple connections.
Option B is incorrect: LAG supports existing connections.
So creating new direct connections is not required.
Option C is correct: Refer to https://docs.aws.amazon.com/directconnect/latest/UserGuide/associate-connection-with-lag.html on how to associate connections with LAG.Option D is incorrect: AWS Direct Connect gateway is used to connect Direct Connect connection to one or more VPCs in the AWS account, which is not needed for this scenario.
Sure, I'd be happy to provide a detailed explanation.
The requirement here is to increase the bandwidth by aggregating two direct connections between the on-premises data center and various AWS services. To achieve this, we need to create a link aggregation group (LAG) in the AWS Direct Connect console.
A LAG allows us to combine multiple connections into a single logical connection, providing increased bandwidth and improved reliability. In this case, we can use a LAG to combine the two existing direct connections.
To create a LAG and associate the existing connections, we need to follow these steps:
In the AWS Direct Connect console, select "Link Aggregation Groups" from the navigation pane.
Click the "Create LAG" button to create a new LAG.
Specify the LAG details, such as the name, number of connections, and bandwidth capacity.
Select the two existing connections that you want to associate with the LAG.
Choose the same AWS device for both connections to ensure that they can be aggregated.
Click "Create" to create the LAG and associate the connections.
Once the LAG is created, traffic between the on-premises data center and AWS services will be evenly distributed across the two connections in the LAG, providing increased bandwidth.
Option B, which suggests provisioning two new connections and associating them with the LAG, is not necessary since we already have two existing connections that can be associated with the LAG. Therefore, option B is not the correct answer.
Option D, which suggests creating an AWS Direct Connect gateway to combine two existing connections over a private virtual interface, is also not necessary in this case. A Direct Connect gateway is used to connect a virtual private cloud (VPC) to on-premises resources over a Direct Connect connection. It is not used to combine multiple Direct Connect connections into a LAG. Therefore, option D is also not the correct answer.
In summary, the correct answers are A and C. We need to create a LAG in the AWS Direct Connect console and associate the two existing direct connections with the LAG to increase the bandwidth.
