Question 290
For a multi-region fiber backbone operator, operators addressed: MACsec was enabled on only one end of a provider cross-connect, leaving the routed adjacency down with integrity errors. What is the strongest acceptance evidence?
Explanation
Correct Answer
An authorized lab peer establishes an encrypted link and passes the intended L3 adjacency and data traffic. This confirms the approved response: Align supported MACsec connectivity association, keying, cipher settings and operational policy at both link endpoints. It is relevant because: MACsec protects Ethernet links through mutually compatible link-layer security associations rather than unilateral encryption.
Incorrect Answers
A lab target route resolves to the discard path while a neighboring nonvictim prefix remains reachable. This would validate ANOTHER scenario: A provider triggers RTBH by announcing a route with an incorrect blackhole community, and legitimate subscriber traffic to the target continues to traverse the core. The specific correction here is: Align supported MACsec connectivity association, keying, cipher settings and operational policy at both link endpoints.
Spoofed test source packets are rejected while legitimate multihomed customer traffic remains reachable. This would validate ANOTHER scenario: A PE applies loose uRPF on a single-homed subscriber port but an upstream source-spoofing event still enters through a route that exists via another edge. The specific correction here is: Align supported MACsec connectivity association, keying, cipher settings and operational policy at both link endpoints.
The legitimate adjacent session remains established while a distant test source with unsuitable TTL is rejected. This would validate ANOTHER scenario: A BGP session from an adjacent PE can be spoofed by packets arriving many router hops away because the provider leaves TTL-security disabled. The specific correction here is: Align supported MACsec connectivity association, keying, cipher settings and operational policy at both link endpoints.