Question 620
At fictional Beacon Healthcare, a network engineer supporting hospital network services is reviewing route-policy and traffic-control behavior during a network troubleshooting drill (HCIP-H12-821-POLICY-155). The observed network issue is: An engineer sets a BGP route community but forgets the matching export policy and upstream advertisements are unchanged. Which next engineering action best addresses the reported problem?
Explanation
Correct Answer
The directly responsive action is: Verify community attachment, propagation and explicit community matching at the export policy. The specific reported fault is: An engineer sets a BGP route community but forgets the matching export policy and upstream advertisements are unchanged. Confirmation should show: Only routes carrying the approved community receive the intended export action. The supporting technical principle is: Community marking and route-policy enforcement are separate configured stages.
Incorrect Answers
“Recalculate token-bucket parameters and choose intended conform, exceed and violate actions” responds to another technical or business failure: A WAN traffic policy drops packets after a bandwidth threshold because committed and excess rates were configured incorrectly. That source case depends on: Token bucket policers classify traffic using configured rate and burst parameters. The present issue is: An engineer sets a BGP route community but forgets the matching export policy and upstream advertisements are unchanged. The more direct action is “Verify community attachment, propagation and explicit community matching at the export policy” because Community marking and route-policy enforcement are separate configured stages.
“Correct the prefix-filter network and mask length parameters for intended component routes” responds to another technical or business failure: A prefix-list denies an entire /16 because its mask range does not include the intended /24 subnet entries. That source case depends on: IP prefix filtering depends on both address prefix and permitted length ranges. The present issue is: An engineer sets a BGP route community but forgets the matching export policy and upstream advertisements are unchanged. The more direct action is “Verify community attachment, propagation and explicit community matching at the export policy” because Community marking and route-policy enforcement are separate configured stages.
“Generate probes from each intended source address or VLAN and observe policy match statistics” responds to another technical or business failure: A traffic-engineering plan changes route selection but the test validates only traceroute from the wrong source network. That source case depends on: Source-sensitive forwarding policy cannot be verified using only destination-based generic probes. The present issue is: An engineer sets a BGP route community but forgets the matching export policy and upstream advertisements are unchanged. The more direct action is “Verify community attachment, propagation and explicit community matching at the export policy” because Community marking and route-policy enforcement are separate configured stages.