Question 250
A provider creates a customer routing instance but assumes its routes will automatically be present in the master inet.0 table. What observable result most directly verifies the intended configuration?
Explanation
Correct Answer
Because routing instances isolate routing tables unless explicit import or export mechanisms connect them, the best response is to define the intended route-leaking boundary between the customer's instance and the master routing table. A reviewer can close the technical case only after confirming that each customer route is visible only in the tables approved by the design.
Incorrect Answers
The proposed principle concerns another network fault: Moving route information between tables does not remove the need for a valid forwarding next hop. Here, routing instances isolate routing tables unless explicit import or export mechanisms connect them. The most direct correction is to define the intended route-leaking boundary between the customer's instance and the master routing table, confirmed by each customer route is visible only in the tables approved by the design.
That result would be useful for a different failure, namely: A filter-based forwarding term matching one subscriber address also captures an overlapping shared services subnet. 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 branch uses a higher OSPF interface cost but expects that branch to remain the preferred primary path. 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.