Question 160
To prevent recurrence of this provider network issue: 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. Which control should be retained?
Explanation
Correct Answer
Exercise RTBH announcements with disposable prefixes and post-event withdrawal checks. This helps prevent recurrence of the issue: 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. Acceptance evidence should be: A lab target route resolves to the discard path while a neighboring nonvictim prefix remains reachable.
Incorrect Answers
Verify MACsec secure-channel state after optics and link-aggregation changes. That is a sensible control for ANOTHER scenario: MACsec was enabled on only one end of a provider cross-connect, leaving the routed adjacency down with integrity errors. It is less targeted to this issue than: Exercise RTBH announcements with disposable prefixes and post-event withdrawal checks.
Include positive ICMPv6 neighbor and packet-too-big fixtures in policy acceptance. That is a sensible control for ANOTHER scenario: A provider limits subscriber attacks using an ingress ACL but accidentally filters essential ICMPv6 neighbor discovery on the same link. It is less targeted to this issue than: Exercise RTBH announcements with disposable prefixes and post-event withdrawal checks.
Require peer and prefix authorization and monitor FlowSpec rule impacts. That is a sensible control for ANOTHER scenario: A route server receives a new FlowSpec route and applies a blanket drop to an entire customer prefix without checking the match and validation policy. It is less targeted to this issue than: Exercise RTBH announcements with disposable prefixes and post-event withdrawal checks.