Question 130
At a telecommunications exchange in Dallas, a BGP import allows an overly broad route that could divert internal traffic. The change affects voice services. What outcome directly proves this configuration works?
Explanation
Correct Answer
At a telecommunications exchange in Dallas, this verifies the specific redistribution and routing policies requirement rather than merely recording an intended configuration: The rejected prefix is absent from the routing table and an approved prefix still installs. The associated implementation is: use filtering and route policy to exclude unapproved prefixes before import.
Incorrect Answers
The offered observation would confirm the separate intervention: Define direction-specific redistribution controls and route tagging where supported. It measures: Routes retain intended origin markings and no repeated feedback paths appear during the migration test. The current redistribution and routing policies configuration is Use filtering and route policy to exclude unapproved prefixes before import, and must demonstrate: The rejected prefix is absent from the routing table and an approved prefix still installs. The two acceptance checks are not interchangeable even though they share a feature area.
That observation measures dynamic routing protocols after this other intervention: Configure an OSPF adjacency and advertisement on the proper routed interface/router. Its result is: The OSPF neighbor is Full and the expected route appears with its learned next hop. The requested redistribution and routing policies change is Use filtering and route policy to exclude unapproved prefixes before import, which must demonstrate: The rejected prefix is absent from the routing table and an approved prefix still installs. The offered evidence does not validate the specified control.
The offered observation would confirm the separate intervention: Apply a scoped redistribution rule and appropriate prefix filtering. It measures: Neighbors learn the three permitted prefixes and do not learn unrelated management routes. The current redistribution and routing policies configuration is Use filtering and route policy to exclude unapproved prefixes before import, and must demonstrate: The rejected prefix is absent from the routing table and an approved prefix still installs. The two acceptance checks are not interchangeable even though they share a feature area.