Question 70
A BGP export policy matches a community but no routes leave the peer after a group-level policy reorder. What should the operations engineer do first to address the stated fault?
Explanation
Correct Answer
This option addresses the stated case rather than another networking issue. Principle: Policy inheritance and term action order affect BGP route advertisement. Remedy: Inspect effective group and neighbor export policy evaluation order. Proof: A neighbor route view confirms the approved community-tagged routes are sent.
Incorrect Answers
Split export policy by authorized customer scope and verify negative advertisements is a relevant step for the separate scenario in which one customer’s new prefixes are advertised to a second unrelated customer via a shared export group. It does not directly fix this case. Instead inspect effective group and neighbor export policy evaluation order; verify: A neighbor route view confirms the approved community-tagged routes are sent.
This answer would be more suitable when a provider chooses segment-routing MPLS but assumes every transit hop needs per-LSP RSVP state, where the corrective action is to review segment identifiers and forwarding under SR-MPLS. The failure here is different: Policy inheritance and term action order affect BGP route advertisement. Required validation: A neighbor route view confirms the approved community-tagged routes are sent.
This option overlooks the decisive condition. Its supporting principle is eBGP speakers separated by intermediate devices require deliberate transport reachability and hop policy, while this scenario depends on policy inheritance and term action order affect BGP route advertisement. Verify the correction with: A neighbor route view confirms the approved community-tagged routes are sent.