BGP Configuration for Hybrid Connectivity
Question
A Global IT organization has deployed Hybrid Connectivity for its intranet application.
They have set up AWS Direct Connect from regional offices to AWS.
Finance Servers are deployed in each region.
Central HRservers are deployed in the us-west-1 region along with servers in each regional office.
Finance servers need to be assessed locally while HR servers need to assess from all regions globally.
IT Head wants to ensure that Finance server IP prefixes are advertised only in the region where it is deployed, while all servers globally should have connectivity to central HR servers in the us-west-1 region to upload employee attendance details.
You are working as a Network engineer for this organization & have been assigned the task to completeBGP configuration for this setup.
While advertising prefixes to BGP peer which tags can be used to control these prefixes advertisements?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answer - A.
BGP Community tags can be used to control the advertisement of IP prefixes towards the Amazon network.
With no BGP Community or Tag 7224:9300, prefixes will be advertised to all AWS regions, while with Tag 7224:9200, it will be advertised to AWS regions in that Continent.
With BGP Community Tag 7224:9100, it will be advertised only to specific AWS regions in which it is part of & not to any other regions.In the above case, the client wants HR server IP prefixes to be only advertised in each region so they can be tagged with Community Tags 7224:9100
Finance servers need to be globally accessed so they can be advertised without any Tag.
Option B is incorrect as with no BGP community Tags which is a default option will advertise prefixes to all AWS regions.
Option C is incorrect as with Community Tag 7224:9300, the server IP Pool will be advertised to all regions.
Option D is incorrect as this will advertise server IP pool to all AWS regions in North America.
For more information on using BGP Community Tags for Prefix Advertisements, refer to the following URL.
https://docs.aws.amazon.com/directconnect/latest/UserGuide/routing-and-bgp.htmlIn this scenario, the organization has a hybrid network with AWS Direct Connect from regional offices to AWS. The finance servers are deployed in each region, and the central HR servers are deployed in the us-west-1 region, along with servers in each regional office. The organization wants to ensure that Finance server IP prefixes are advertised only in the region where they are deployed, while all servers globally should have connectivity to central HR servers in the us-west-1 region to upload employee attendance details.
To achieve this, the organization needs to configure BGP advertisement for each server to control the prefix advertisements. BGP community tags can be used to control the advertisements. BGP community tags are numeric values that can be attached to a BGP route advertisement to control how the route is treated by BGP peers.
Option A suggests using BGP Community Tags 7224:9100 for the server to be accessed in each AWS region and no BGP community tags for servers to be accessed from all regions. This option is incorrect because it does not provide a tag for central HR servers, which should be accessible from all regions.
Option B suggests using no BGP community tags for the server to be accessed in each AWS region and BGP Community Tags 7224:9300 for servers to be accessed from all regions. This option is incorrect because it does not provide a tag for finance servers to restrict the advertisement to the region where they are deployed.
Option C suggests using BGP Community Tags 7224:9300 for the server to be accessed in each AWS region and BGP Community Tags 7224:9200 for servers to be accessed from all regions. This option is incorrect because it does not provide a tag for finance servers to restrict the advertisement to the region where they are deployed.
Option D suggests using BGP Community Tags 7224:9200 for servers to be accessed in each AWS region and BGP Community Tags 7224:9300 for servers to be accessed from all regions. This option is correct because it provides a tag for finance servers to restrict the advertisement to the region where they are deployed (7224:9200) and a tag for central HR servers to be accessible from all regions (7224:9300).
Therefore, the correct answer is D - Use BGP Community Tags 7224:9200 for servers to be accessed in each AWS region and BGP Community Tags 7224:9300 for servers to be accessed from all regions.
