Question 250
During production incident triage, engineers observe: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The selected active prefix shows the intended protocol, route preference, and forwarding next hop both before and after a controlled failover.
- The prefix is absent from permitted active forwarding while legitimate nearby routes remain reachable and logged rejection evidence matches policy.
- The intended route appears in both authorized tables with the right next hop, while unrelated routes are not leaked.
- The forwarding table shows both expected next hops and representative flows use the authorized paths without loop or asymmetry problems.
Explanation
Correct Answer
D:The forwarding table shows both expected next hops and representative flows use the authorized paths without loop or asymmetry problems. This tests the actual condition identified in the live production incident: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. It is meaningful because ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds.
Incorrect Answers
A:The selected active prefix shows the intended protocol, route preference, and forwarding next hop both before and after a controlled failover. This measurement may prove the unrelated Administrative preference overrides static condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. A relevant acceptance result here is: The forwarding table shows both expected next hops and representative flows use the authorized paths without loop or asymmetry problems.
B:The prefix is absent from permitted active forwarding while legitimate nearby routes remain reachable and logged rejection evidence matches policy. This measurement may prove the unrelated Martian-address acceptance condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. A relevant acceptance result here is: The forwarding table shows both expected next hops and representative flows use the authorized paths without loop or asymmetry problems.
C:The intended route appears in both authorized tables with the right next hop, while unrelated routes are not leaked. This measurement may prove the unrelated RIB group forwarding copy condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. A relevant acceptance result here is: The forwarding table shows both expected next hops and representative flows use the authorized paths without loop or asymmetry problems.
Question 251
During production incident triage, engineers observe: A router interface carries IPv4 traffic and is listed under IS-IS, but no IS-IS Hello packets form because the required ISO protocol family is absent. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The two devices show an up adjacency at the intended level and their Level 1 link-state databases exchange reachability.
- IS-IS Hello exchanges appear and the expected level adjacency establishes while IPv4 traffic still functions.
- A shared Level 1 or Level 2 adjacency comes up and the right set of level-specific routes is exchanged.
- The nodes appear with distinct system IDs and no repeated conflicting LSP originator entries in the database.
Explanation
Correct Answer
B:IS-IS Hello exchanges appear and the expected level adjacency establishes while IPv4 traffic still functions. This tests the actual condition identified in the live production incident: A router interface carries IPv4 traffic and is listed under IS-IS, but no IS-IS Hello packets form because the required ISO protocol family is absent. It is meaningful because Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration.
Incorrect Answers
A:The two devices show an up adjacency at the intended level and their Level 1 link-state databases exchange reachability. This measurement may prove the unrelated IS-IS level-one area mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A router interface carries IPv4 traffic and is listed under IS-IS, but no IS-IS Hello packets form because the required ISO protocol family is absent. A relevant acceptance result here is: IS-IS Hello exchanges appear and the expected level adjacency establishes while IPv4 traffic still functions.
C:A shared Level 1 or Level 2 adjacency comes up and the right set of level-specific routes is exchanged. This measurement may prove the unrelated IS-IS level capability mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A router interface carries IPv4 traffic and is listed under IS-IS, but no IS-IS Hello packets form because the required ISO protocol family is absent. A relevant acceptance result here is: IS-IS Hello exchanges appear and the expected level adjacency establishes while IPv4 traffic still functions.
D:The nodes appear with distinct system IDs and no repeated conflicting LSP originator entries in the database. This measurement may prove the unrelated Duplicate IS-IS system ID condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A router interface carries IPv4 traffic and is listed under IS-IS, but no IS-IS Hello packets form because the required ISO protocol family is absent. A relevant acceptance result here is: IS-IS Hello exchanges appear and the expected level adjacency establishes while IPv4 traffic still functions.
Question 252
During production incident triage, engineers observe: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The two devices show an up adjacency at the intended level and their Level 1 link-state databases exchange reachability.
- The nodes appear with distinct system IDs and no repeated conflicting LSP originator entries in the database.
- The LSDB advertises compatible wide metrics and SPF selects the intended path across the upgraded links.
- The intended prefix appears at the expected level without management or unrelated customer routes being leaked.
Explanation
Correct Answer
D:The intended prefix appears at the expected level without management or unrelated customer routes being leaked. This tests the actual condition identified in the live production incident: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. It is meaningful because IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain.
Incorrect Answers
A:The two devices show an up adjacency at the intended level and their Level 1 link-state databases exchange reachability. This measurement may prove the unrelated IS-IS level-one area mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. A relevant acceptance result here is: The intended prefix appears at the expected level without management or unrelated customer routes being leaked.
B:The nodes appear with distinct system IDs and no repeated conflicting LSP originator entries in the database. This measurement may prove the unrelated Duplicate IS-IS system ID condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. A relevant acceptance result here is: The intended prefix appears at the expected level without management or unrelated customer routes being leaked.
C:The LSDB advertises compatible wide metrics and SPF selects the intended path across the upgraded links. This measurement may prove the unrelated IS-IS narrow metric ceiling condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. A relevant acceptance result here is: The intended prefix appears at the expected level without management or unrelated customer routes being leaked.
Question 253
During production incident triage, engineers observe: An eBGP peering is established for inet unicast but the provider cannot receive approved IPv6 prefixes because the IPv6 address family is absent. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The relevant IPv6 reachability TLVs are present and remote IPv6 prefixes become active in inet6.0.
- Approved IPv6 prefixes are received, installed and reachable with the correct inet6.0 next-hop resolution.
- An IPv6 trace crosses the intended tunnel, while outer IPv4 packets reach the peer endpoints and encapsulation counters increment.
- Large IPv6 application transfers succeed and Packet Too Big messages reach the source when necessary.
Explanation
Correct Answer
B:Approved IPv6 prefixes are received, installed and reachable with the correct inet6.0 next-hop resolution. This tests the actual condition identified in the live production incident: An eBGP peering is established for inet unicast but the provider cannot receive approved IPv6 prefixes because the IPv6 address family is absent. It is meaningful because BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange.
Incorrect Answers
A:The relevant IPv6 reachability TLVs are present and remote IPv6 prefixes become active in inet6.0. This measurement may prove the unrelated IS-IS IPv6 reachability TLVs condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An eBGP peering is established for inet unicast but the provider cannot receive approved IPv6 prefixes because the IPv6 address family is absent. A relevant acceptance result here is: Approved IPv6 prefixes are received, installed and reachable with the correct inet6.0 next-hop resolution.
C:An IPv6 trace crosses the intended tunnel, while outer IPv4 packets reach the peer endpoints and encapsulation counters increment. This measurement may prove the unrelated IPv6 over IPv4 transit tunnel condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An eBGP peering is established for inet unicast but the provider cannot receive approved IPv6 prefixes because the IPv6 address family is absent. A relevant acceptance result here is: Approved IPv6 prefixes are received, installed and reachable with the correct inet6.0 next-hop resolution.
D:Large IPv6 application transfers succeed and Packet Too Big messages reach the source when necessary. This measurement may prove the unrelated ICMPv6 packet-too-big handling condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An eBGP peering is established for inet unicast but the provider cannot receive approved IPv6 prefixes because the IPv6 address family is absent. A relevant acceptance result here is: Approved IPv6 prefixes are received, installed and reachable with the correct inet6.0 next-hop resolution.
Question 254
During production incident triage, engineers observe: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- No OSPF neighbors form on the customer LAN, yet core routers still learn the intended LAN prefix.
- Internal prefixes remain present, the designed default is learned, and external traffic follows that default without type-5 LSAs in the stub.
- Calculated path costs and the active next hop match the expected path, and failover still uses a valid alternate.
- The routers advertise distinct IDs, neighbors remain Full and the LSDB no longer shows conflicting origins.
Explanation
Correct Answer
D:The routers advertise distinct IDs, neighbors remain Full and the LSDB no longer shows conflicting origins. This tests the actual condition identified in the live production incident: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. It is meaningful because OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain.
Incorrect Answers
A:No OSPF neighbors form on the customer LAN, yet core routers still learn the intended LAN prefix. This measurement may prove the unrelated OSPF passive interface condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. A relevant acceptance result here is: The routers advertise distinct IDs, neighbors remain Full and the LSDB no longer shows conflicting origins.
B:Internal prefixes remain present, the designed default is learned, and external traffic follows that default without type-5 LSAs in the stub. This measurement may prove the unrelated Stub area external LSA expectation condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. A relevant acceptance result here is: The routers advertise distinct IDs, neighbors remain Full and the LSDB no longer shows conflicting origins.
C:Calculated path costs and the active next hop match the expected path, and failover still uses a valid alternate. This measurement may prove the unrelated OSPF metric path preference condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. A relevant acceptance result here is: The routers advertise distinct IDs, neighbors remain Full and the LSDB no longer shows conflicting origins.
Question 255
During production incident triage, engineers observe: Two PE routers exchange OSPF Hello packets on the same Ethernet segment but stay Down because one interface belongs to area 0 and the other to area 10. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- An appropriate eligible router becomes DR or BDR after a controlled election and neighbor adjacency remains stable.
- Both peers reach Full adjacency in the same area and the intended routes are learned.
- Both peers show the expected current LSAs with consistent sequence and topology, and the computed path reaches the destination.
- The specifically allowed customer prefix appears as the expected external route on the peer, while other connected networks stay unadvertised.
Explanation
Correct Answer
B:Both peers reach Full adjacency in the same area and the intended routes are learned. This tests the actual condition identified in the live production incident: Two PE routers exchange OSPF Hello packets on the same Ethernet segment but stay Down because one interface belongs to area 0 and the other to area 10. It is meaningful because OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship.
Incorrect Answers
A:An appropriate eligible router becomes DR or BDR after a controlled election and neighbor adjacency remains stable. This measurement may prove the unrelated DR priority zero misconception condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two PE routers exchange OSPF Hello packets on the same Ethernet segment but stay Down because one interface belongs to area 0 and the other to area 10. A relevant acceptance result here is: Both peers reach Full adjacency in the same area and the intended routes are learned.
C:Both peers show the expected current LSAs with consistent sequence and topology, and the computed path reaches the destination. This measurement may prove the unrelated OSPF LSDB discrepancy condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two PE routers exchange OSPF Hello packets on the same Ethernet segment but stay Down because one interface belongs to area 0 and the other to area 10. A relevant acceptance result here is: Both peers reach Full adjacency in the same area and the intended routes are learned.
D:The specifically allowed customer prefix appears as the expected external route on the peer, while other connected networks stay unadvertised. This measurement may prove the unrelated OSPF export policy omission condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two PE routers exchange OSPF Hello packets on the same Ethernet segment but stay Down because one interface belongs to area 0 and the other to area 10. A relevant acceptance result here is: Both peers reach Full adjacency in the same area and the intended routes are learned.
Question 256
During production incident triage, engineers observe: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- A TCP session is established to the correct neighbor address, BGP reaches Established and intended routes are exchanged.
- The received BGP route resolves its next hop, becomes eligible, and forwards over the designed path.
- A route detail comparison shows the relevant AS-path difference and chosen path conforms to approved policy.
- The rejected prefix does not appear as an eligible route while approved advertised prefixes remain available.
Explanation
Correct Answer
A:A TCP session is established to the correct neighbor address, BGP reaches Established and intended routes are exchanged. This tests the actual condition identified in the live production incident: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. It is meaningful because BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering.
Incorrect Answers
B:The received BGP route resolves its next hop, becomes eligible, and forwards over the designed path. This measurement may prove the unrelated BGP next-hop inaccessible condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. A relevant acceptance result here is: A TCP session is established to the correct neighbor address, BGP reaches Established and intended routes are exchanged.
C:A route detail comparison shows the relevant AS-path difference and chosen path conforms to approved policy. This measurement may prove the unrelated BGP AS-path comparison condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. A relevant acceptance result here is: A TCP session is established to the correct neighbor address, BGP reaches Established and intended routes are exchanged.
D:The rejected prefix does not appear as an eligible route while approved advertised prefixes remain available. This measurement may prove the unrelated BGP import policy leak condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. A relevant acceptance result here is: A TCP session is established to the correct neighbor address, BGP reaches Established and intended routes are exchanged.
Question 257
During production incident triage, engineers observe: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- No OSPF neighbors form on the customer LAN, yet core routers still learn the intended LAN prefix.
- Internal prefixes remain present, the designed default is learned, and external traffic follows that default without type-5 LSAs in the stub.
- The two interfaces report matching timers and the neighbor stays Full beyond several dead intervals.
- Calculated path costs and the active next hop match the expected path, and failover still uses a valid alternate.
Explanation
Correct Answer
C:The two interfaces report matching timers and the neighbor stays Full beyond several dead intervals. This tests the actual condition identified in the live production incident: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. It is meaningful because OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance.
Incorrect Answers
A:No OSPF neighbors form on the customer LAN, yet core routers still learn the intended LAN prefix. This measurement may prove the unrelated OSPF passive interface condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. A relevant acceptance result here is: The two interfaces report matching timers and the neighbor stays Full beyond several dead intervals.
B:Internal prefixes remain present, the designed default is learned, and external traffic follows that default without type-5 LSAs in the stub. This measurement may prove the unrelated Stub area external LSA expectation condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. A relevant acceptance result here is: The two interfaces report matching timers and the neighbor stays Full beyond several dead intervals.
D:Calculated path costs and the active next hop match the expected path, and failover still uses a valid alternate. This measurement may prove the unrelated OSPF metric path preference condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. A relevant acceptance result here is: The two interfaces report matching timers and the neighbor stays Full beyond several dead intervals.
Question 258
During production incident triage, engineers observe: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- All intended members show collecting and distributing state in the correct AE bundle and packet forwarding is stable.
- The designated router is primary under normal conditions and the backup takes over promptly during an injected outage.
- Failback occurs only after verified upstream reachability and virtual gateway traffic remains stable across recovery.
- The session remains stable during representative load yet detects an injected forwarding fault within the approved interval.
Explanation
Correct Answer
A:All intended members show collecting and distributing state in the correct AE bundle and packet forwarding is stable. This tests the actual condition identified in the live production incident: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. It is meaningful because LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone.
Incorrect Answers
B:The designated router is primary under normal conditions and the backup takes over promptly during an injected outage. This measurement may prove the unrelated VRRP master priority failover condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. A relevant acceptance result here is: All intended members show collecting and distributing state in the correct AE bundle and packet forwarding is stable.
C:Failback occurs only after verified upstream reachability and virtual gateway traffic remains stable across recovery. This measurement may prove the unrelated VRRP preemption oscillation condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. A relevant acceptance result here is: All intended members show collecting and distributing state in the correct AE bundle and packet forwarding is stable.
D:The session remains stable during representative load yet detects an injected forwarding fault within the approved interval. This measurement may prove the unrelated BFD detect timer too aggressive condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. A relevant acceptance result here is: All intended members show collecting and distributing state in the correct AE bundle and packet forwarding is stable.
Question 259
During production incident triage, engineers observe: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- Expected LDP discovery packets and TCP session are present on the correct link, and relevant FEC labels are learned.
- A lookup for the affected incoming label shows the expected output label and interface, and an MPLS trace reaches the egress.
- An LDP session reaches Operational and displays the intended neighbor label bindings after selective filter correction.
- The LSP reserves its intended bandwidth end to end without exceeding the engineered link limits.
Explanation
Correct Answer
B:A lookup for the affected incoming label shows the expected output label and interface, and an MPLS trace reaches the egress. This tests the actual condition identified in the live production incident: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. It is meaningful because MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions.
Incorrect Answers
A:Expected LDP discovery packets and TCP session are present on the correct link, and relevant FEC labels are learned. This measurement may prove the unrelated LDP discovery and IGP mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. A relevant acceptance result here is: A lookup for the affected incoming label shows the expected output label and interface, and an MPLS trace reaches the egress.
C:An LDP session reaches Operational and displays the intended neighbor label bindings after selective filter correction. This measurement may prove the unrelated LDP TCP 646 establishment condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. A relevant acceptance result here is: A lookup for the affected incoming label shows the expected output label and interface, and an MPLS trace reaches the egress.
D:The LSP reserves its intended bandwidth end to end without exceeding the engineered link limits. This measurement may prove the unrelated RSVP reservable bandwidth shortage condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. A relevant acceptance result here is: A lookup for the affected incoming label shows the expected output label and interface, and an MPLS trace reaches the egress.
Question 260
During production incident triage, engineers observe: PE-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- A controlled packet to an active more-specific prefix forwards, while a packet to an uncovered address receives the intended reject or silent-discard behavior.
- The forwarding table shows both expected next hops and representative flows use the authorized paths without loop or asymmetry problems.
- The prefix is absent from permitted active forwarding while legitimate nearby routes remain reachable and logged rejection evidence matches policy.
- Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded.
Explanation
Correct Answer
C:The prefix is absent from permitted active forwarding while legitimate nearby routes remain reachable and logged rejection evidence matches policy. This tests the actual condition identified in the live production incident: PE-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. It is meaningful because Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context.
Incorrect Answers
A:A controlled packet to an active more-specific prefix forwards, while a packet to an uncovered address receives the intended reject or silent-discard behavior. This measurement may prove the unrelated Aggregate rejection behavior condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: PE-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. A relevant acceptance result here is: The prefix is absent from permitted active forwarding while legitimate nearby routes remain reachable and logged rejection evidence matches policy.
B:The forwarding table shows both expected next hops and representative flows use the authorized paths without loop or asymmetry problems. This measurement may prove the unrelated Equal-cost multipath eligibility condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: PE-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. A relevant acceptance result here is: The prefix is absent from permitted active forwarding while legitimate nearby routes remain reachable and logged rejection evidence matches policy.
D:Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded. This measurement may prove the unrelated Per-flow hash expectation condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: PE-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. A relevant acceptance result here is: The prefix is absent from permitted active forwarding while legitimate nearby routes remain reachable and logged rejection evidence matches policy.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests