Question 740
A filter-based forwarding term matching one subscriber address also captures an overlapping shared services subnet. What remediation is most directly applicable?
Explanation
Correct Answer
Because overlapping address classification makes precise route-filter and policy terms essential, the best response is to tighten the filter match and verify the next-table lookup with explicit positive and negative examples. A reviewer can close the technical case only after confirming that only the subscriber's approved traffic enters the alternate routing instance.
Incorrect Answers
That result would be useful for a different failure, namely: An operator accepts a source-address block as an ordinary next-hop network even though the address is classified as martian. The current case specifically calls for: Tighten the filter match and verify the next-table lookup with explicit positive and negative examples. The required observed result is: Only the subscriber's approved traffic enters the alternate routing instance.
Restore the intended route preferences and check selected forwarding next hops is a relevant step for the separate scenario in which a backup path becomes primary after a preference edit even though the design called for failover only. It does not directly fix this case. Instead tighten the filter match and verify the next-table lookup with explicit positive and negative examples; verify: Only the subscriber's approved traffic enters the alternate routing instance.
The alternative addresses an OSPF route appears longer than expected after failover because a backup link's cost was never verified, not the present root cause. Here the selected correction must reflect overlapping address classification makes precise route-filter and policy terms essential. Test for: Only the subscriber's approved traffic enters the alternate routing instance.