The exhibit shows a BGP routing process where an Import Policy is being applied to routes received in the RIB-IN. Specifically, Policy 1 states: " Reject 0.0.0.0/0 from AS 64512. "
In Junos OS, when a routing policy rejects a route, that route is not placed in the main routing table (inet.0) for active use. Instead, it becomes a hidden route. To verify that a specific peer is actually sending a route that is subsequently being rejected by your policy, you must use specific diagnostic commands:
Understanding " Hidden " Routes: When a BGP route is received but fails to meet policy requirements (or has an unreachable next-hop), Junos keeps it in the BGP RIB-IN but marks it as " hidden. " It will not appear in a standard show route command.
Command Logic (Option D): The command show route receive-protocol bgp < peer ip > hidden allows an administrator to view all routes received from a specific neighbor, including those that were rejected by import policies.
show route receive-protocol bgp < peer ip > : Shows only the routes that passed the import policy and were accepted into the table. Since the 0.0.0.0/0 route from AS 64512 is explicitly rejected in the exhibit, it would not show up here.
Adding the hidden keyword is the essential step to see the rejected default route and verify that AS 64512 is indeed sending it before the policy drops it.
Other Options:
Option A is incorrect because it only shows accepted routes.
Option B and C are used to filter the existing active routing table based on gateway or next-hop attributes, but they cannot show routes that have been rejected and excluded from that table.
