Factors to Consider for Setting up a Link Aggregation Group
Question
Your company has a set of AWS Direct Connect connections.
They want to aggregate the bandwidth of these connections to ensure that a large amount of data can be sent through the pipe.
So a decision has been made to set up a link aggregation group.
What are the factors that need to be considered when setting up the LAG group? Choose 2 answers from the options given below.
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.Answer - A and C.
The clear requirements for setting up LAG are given in the AWS Documentation.
The following rules apply:
· All connections in the LAG must use the same bandwidth.
The following bandwidths are supported: 1 Gbps and 10 Gbps.
· You can have a maximum of 4 connections in a LAG.
Each connection in the LAG counts towards your overall connection limit for the region.
· All connections in the LAG must terminate at the same AWS Direct Connect endpoint.
Options B and D are invalid because they break the rules for setting up a LAG group.
For more information on LAG groups, please refer to the below URL:
https://docs.aws.amazon.com/directconnect/latest/UserGuide/lags.htmlThe two factors that need to be considered when setting up a Link Aggregation Group (LAG) for AWS Direct Connect connections are:
A. You have to ensure that the existing AWS Direct Connect connections have the same bandwidth. C. You have to ensure that all AWS Direct Connect connections terminate at the same AWS endpoint.
Explanation:
A Link Aggregation Group (LAG) is a mechanism that allows multiple network connections to be combined into a single logical connection to provide increased bandwidth and redundancy. When setting up a LAG for AWS Direct Connect connections, it is important to consider the following factors:
A. You have to ensure that the existing AWS Direct Connect connections have the same bandwidth: In order to create a LAG, all the AWS Direct Connect connections that will be a part of the LAG should have the same bandwidth. For example, if one connection has a bandwidth of 1 Gbps and another connection has a bandwidth of 10 Gbps, they cannot be aggregated. Therefore, it is important to ensure that all the connections have the same bandwidth to create a LAG with aggregated bandwidth.
C. You have to ensure that all AWS Direct Connect connections terminate at the same AWS endpoint: In order to create a LAG, all the AWS Direct Connect connections should terminate at the same AWS endpoint. This endpoint is usually a Direct Connect gateway or a virtual private gateway. If the connections terminate at different endpoints, they cannot be aggregated into a single logical connection. Therefore, it is important to ensure that all the connections terminate at the same endpoint to create a LAG with aggregated bandwidth.
B and D are not correct answers for this question: B. You have to ensure that a VPN connection is also in place to attach to the LAG group: This is not a factor to consider when setting up a LAG for AWS Direct Connect connections. VPN connections are used to establish a secure and encrypted connection between on-premises networks and the AWS Cloud, but they are not required for setting up a LAG.
D. You have to ensure that all AWS Direct Connect connections terminate at different AWS endpoints: This is incorrect. As mentioned above, all the AWS Direct Connect connections should terminate at the same AWS endpoint to create a LAG with aggregated bandwidth. If they terminate at different endpoints, they cannot be aggregated into a single logical connection.
