Question 310
Following a supported configuration correction, the original issue was: A provider uses BGP community 65000:123 as a traffic-engineering signal but one edge strips communities on eBGP export, so the upstream never applies the requested policy. Which observation verifies success?
Explanation
Correct Answer
The upstream sandbox peer receives the intended community and applies only the agreed action. This confirms the approved response: Preserve and transmit the negotiated community using the supported neighbor settings and route policy. It is relevant because: BGP communities are optional policy metadata and must be explicitly propagated when the design depends on them.
Incorrect Answers
Tests accept the specified /25 and deny an unrelated /25 outside the controlled prefix. This would validate ANOTHER scenario: A route-policy template attempts to match a more-specific /25 by using an exact /24 prefix without a length range, mistakenly accepting only the aggregate. The specific correction here is: Preserve and transmit the negotiated community using the supported neighbor settings and route policy.
Test prefixes show the tagged route rejected and only approved routes advertised. This would validate ANOTHER scenario: A route map denies a tagged customer route but includes a later permit clause matching all prefixes, and operations misinterprets the first match behavior. The specific correction here is: Preserve and transmit the negotiated community using the supported neighbor settings and route policy.
IPv6 topology and route output show the expected prefix end-to-end while IPv4 remains stable. This would validate ANOTHER scenario: An IPv6 service prefix disappears after enabling IS-IS multitopology, and operations only checks the IPv4 SPF database. The specific correction here is: Preserve and transmit the negotiated community using the supported neighbor settings and route policy.