Which design consideration should be observed when EIGRP is configured on Data Center switches?
Which design consideration should be observed when EIGRP is configured on Data Center switches?
When configuring EIGRP on Data Center switches, it is essential to prevent unnecessary EIGRP neighborships from forming across switch virtual interfaces (SVIs). In a Data Center environment, SVIs can be numerous, and allowing EIGRP to form neighborships on all of them can lead to unnecessary EIGRP overhead and potentially impact performance. This consideration ensures a more efficient and scalable EIGRP deployment in the Data Center.
Answer is B
I agree with B. Besides, A is not specific to the data center. its best practice, in general, to summarize at particular points in the EIGRP hierarchical design. Not all L3 interfaces.
Answer is A reference : ENSLD 300-420 Cert Guide - Chapter 3 "Routing Protocol Characteristics, EIGRP, and IS-IS" - EIGRP in the Data Center
Option B is the correct answer because EIGRP can form neighborships across switch virtual interfaces (SVIs) if the SVIs are configured with IP addresses. In a Data Center environment, where there are typically many SVIs, this can result in unnecessary EIGRP neighborships and potentially impact performance. To prevent this, it is recommended to configure EIGRP to only form neighborships on physical interfaces where necessary, rather than on all SVIs. Option A, performing manual summarization on all Layer 3 interfaces to minimize the size of the routing table, may be useful in some cases, but it is not a specific design consideration for EIGRP on Data Center switches.
reference : EIGRP in the Data Center Chapter 3 Because DCs will have many different services, networks, and applications, you should design for summarizing data center subnets, just as you would do in wide-area networking.
I researched this question I am strongly think answer is A. With answer B I do not think EIGRP will form neighbors on virtual interfaces because it is not possible. Forming neighbors has to be a physical connection not virtual.
Answer is A. Mardouk it´s right in chapter 3 - part EIGRP in the Data Center
Answer is A
Answer is A 100% EIGRP in the Data Center When EIGRP is used in the data center (DC), several design considerations are important. Because DCs will have many different services, networks, and applications, you should design for summarizing data center subnets, just as you would do in wide-area networking. Furthermore, it is a good idea to advertise a default route into the DC from the aggregation layer. This way, you do not have to advertise all global network routes into the DC.
A is 100% correct. Chapter 3 Page 114 "EIGRP in the Data Center" When EIGRP is used in the data center (DC), several design considerations are important. Because DCs will have my different services, networks and applications, you should design for summarizing data center subnets, just as you would do in WAN.
A is correct. reference : ENSLD 300-420 Cert Guide Chapter 3 "Routing Protocol Characteristics, EIGRP, and IS-IS" EIGRP in the Data Center page 114 "Because DCs will have many different services, networks, and applications, you should design for summarizing data center subnets..."