Question 580
A provider creates a customer routing instance but assumes its routes will automatically be present in the master inet.0 table. A reviewer requires a remedy and concrete test evidence. Which pairing fits?
Explanation
Correct Answer
Correct diagnosis: Routing instances isolate routing tables unless explicit import or export mechanisms connect them. The appropriate action is: Define the intended route-leaking boundary between the customer's instance and the master routing table. The follow-up evidence required is: Each customer route is visible only in the tables approved by the design.
Incorrect Answers
That result would be useful for a different failure, namely: Two static routes for the same prefix have unequal preferences and the operator expects both paths to share traffic. The current case specifically calls for: Define the intended route-leaking boundary between the customer's instance and the master routing table. The required observed result is: Each customer route is visible only in the tables approved by the design.
This response would target a different source scenario: A RIB group leak forwards a VPN service toward the wrong next hop after a route update. It cannot establish the current acceptance requirement, which is: Each customer route is visible only in the tables approved by the design. The relevant action is: Define the intended route-leaking boundary between the customer's instance and the master routing table.
Verify IP reachability, routing instance context, TCP transport and session authentication is a relevant step for the separate scenario in which a BGP peer is stuck in Active after a maintenance window even though the remote address is configured. It does not directly fix this case. Instead define the intended route-leaking boundary between the customer's instance and the master routing table; verify: Each customer route is visible only in the tables approved by the design.