Question 880
A design review confuses Type 2 MAC-IP advertisements with Type 5 IP prefix advertisements in an ERB fabric. Which controlled change best addresses the described requirement?
Explanation
Correct Answer
This action addresses the stated defect: advertise and import the required host or prefix routes according to the approved ERB routing design. The underlying constraint is that EVPN endpoint and routed-prefix reachability use different route types and their import policy must match the data path. Verify rather than assume success: confirm both host resolution and inter-subnet routed reachability use the expected EVPN routes.
Incorrect Answers
The option “Implement an authorized distributed gateway design and ensure the overlay advertises the required endpoint or prefix routes” is useful in a different setting: A leaf gateway must route a workload's inter-subnet traffic locally rather than always hairpinning through a central aggregation switch. The case being tested is: A design review confuses Type 2 MAC-IP advertisements with Type 5 IP prefix advertisements in an ERB fabric. Advertise and import the required host or prefix routes according to the approved ERB routing design. The most relevant correction is “Advertise and import the required host or prefix routes according to the approved ERB routing design”.
“Align the authorized distributed gateway configuration across participating VTEPs” is relevant to a different condition: Two racks advertise the same distributed gateway virtual address but clients see intermittent first-hop behavior after a deployment. The stated question instead concerns: A design review confuses Type 2 MAC-IP advertisements with Type 5 IP prefix advertisements in an ERB fabric. Advertise and import the required host or prefix routes according to the approved ERB routing design. The most relevant correction is “Advertise and import the required host or prefix routes according to the approved ERB routing design”.
That choice—“Correct prefix export/import and next-hop resolution for the routed EVPN IP prefix”—addresses this other problem: A fabric exchanges IP prefixes between tenant routing zones without requiring every remote subnet to be represented as an individual MAC. Here the scenario is: A design review confuses Type 2 MAC-IP advertisements with Type 5 IP prefix advertisements in an ERB fabric. Advertise and import the required host or prefix routes according to the approved ERB routing design. The most relevant correction is “Advertise and import the required host or prefix routes according to the approved ERB routing design”.