A network engineer is troubleshooting a BGP route filtering issue. Router R1 is advertising a prefix 10.1.1.0/24 to its eBGP neighbor R2, but R2 is not receiving it. The engineer checks R1's BGP configuration and sees a route-map named FILTER-OUT applied outbound to the neighbor. The route-map references an ACL that permits 10.1.1.0/24, but the prefix is still not being sent. What is the most likely cause?
Trap 1: The ACL is using the wrong wildcard mask; it should be 0.0.0.255…
Incorrect because the wildcard mask 0.0.0.0 matches only the exact prefix, which is fine for 10.1.1.0/24.
Trap 2: The neighbor is configured with 'soft-reconfiguration inbound'…
Incorrect because soft-reconfiguration inbound only affects inbound updates, not outbound.
Trap 3: The route-map is applied inbound instead of outbound on R1.
Incorrect because the scenario states the route-map is applied outbound.
- A
The route-map is missing a 'permit' statement; the default action is deny.
Correct because route-maps without an explicit permit will implicitly deny all prefixes.
- B
The ACL is using the wrong wildcard mask; it should be 0.0.0.255 instead of 0.0.0.0.
Why wrong: Incorrect because the wildcard mask 0.0.0.0 matches only the exact prefix, which is fine for 10.1.1.0/24.
- C
The neighbor is configured with 'soft-reconfiguration inbound' which blocks outbound updates.
Why wrong: Incorrect because soft-reconfiguration inbound only affects inbound updates, not outbound.
- D
The route-map is applied inbound instead of outbound on R1.
Why wrong: Incorrect because the scenario states the route-map is applied outbound.