Question 430
An operator accepts a source-address block as an ordinary next-hop network even though the address is classified as martian. Which root-cause explanation and corrective action fit the case?
Explanation
Correct Answer
Correct diagnosis: Address validity and martian filtering affect which route sources are considered acceptable. The appropriate action is: Review martian-address treatment and justify any carefully scoped exception. The follow-up evidence required is: The rejected address remains excluded or a documented narrowly scoped exception is applied.
Incorrect Answers
The alternative addresses a provider router has a static route for a customer prefix but its configured next hop is not reachable through any active route, not the present root cause. Here the selected correction must reflect address validity and martian filtering affect which route sources are considered acceptable. Test for: The rejected address remains excluded or a documented narrowly scoped exception is applied.
This answer would be more suitable when after a maintenance window a configured customer static prefix is missing from active routes despite no syntax errors, where the corrective action is to inspect the configuration, active route state and next-hop reachability before changing preference. The failure here is different: Address validity and martian filtering affect which route sources are considered acceptable. Required validation: The rejected address remains excluded or a documented narrowly scoped exception is applied.
This option overlooks the decisive condition. Its supporting principle is disabling loop prevention can introduce persistent interdomain routing loops, while this scenario depends on address validity and martian filtering affect which route sources are considered acceptable. Verify the correction with: The rejected address remains excluded or a documented narrowly scoped exception is applied.