Question 230
During production incident triage, engineers observe: A customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The static prefix becomes active with a resolved next hop, and a sourced packet test reaches the destination through the intended interface.
- Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded.
- The aggregate appears as an active route with contributing prefixes shown, and the permitted summary is advertised to the intended peer.
- The generated default becomes active with the expected next hop only when the qualifying contributor exists.
Explanation
Correct Answer
B:Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded. This tests the actual condition identified in the live production incident: A customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. It is meaningful because Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths.
Incorrect Answers
A:The static prefix becomes active with a resolved next hop, and a sourced packet test reaches the destination through the intended interface. This measurement may prove the unrelated Recursive next-hop resolution condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. A relevant acceptance result here is: Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded.
C:The aggregate appears as an active route with contributing prefixes shown, and the permitted summary is advertised to the intended peer. This measurement may prove the unrelated Aggregate route contribution condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. A relevant acceptance result here is: Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded.
D:The generated default becomes active with the expected next hop only when the qualifying contributor exists. This measurement may prove the unrelated Generated default route prerequisite condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. A relevant acceptance result here is: Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded.
Question 231
During production incident triage, engineers observe: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- With the downstream fault injected, the unsuitable backup route is withdrawn or de-preferred and valid traffic moves to the tested alternate.
- Permitted prefixes are visible in the correct tables and an unauthorized destination is absent from the receiving customer's forwarding view.
- The intended route appears in both authorized tables with the right next hop, while unrelated routes are not leaked.
- The selected active prefix shows the intended protocol, route preference, and forwarding next hop both before and after a controlled failover.
Explanation
Correct Answer
B:Permitted prefixes are visible in the correct tables and an unauthorized destination is absent from the receiving customer's forwarding view. This tests the actual condition identified in the live production incident: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. It is meaningful because Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy.
Incorrect Answers
A:With the downstream fault injected, the unsuitable backup route is withdrawn or de-preferred and valid traffic moves to the tested alternate. This measurement may prove the unrelated Static backup blackhole condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. A relevant acceptance result here is: Permitted prefixes are visible in the correct tables and an unauthorized destination is absent from the receiving customer's forwarding view.
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: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. A relevant acceptance result here is: Permitted prefixes are visible in the correct tables and an unauthorized destination is absent from the receiving customer's forwarding view.
D: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: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. A relevant acceptance result here is: Permitted prefixes are visible in the correct tables and an unauthorized destination is absent from the receiving customer's forwarding view.
Question 232
During production incident triage, engineers observe: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. 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.
- 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.
- The IPv6 route is active in inet6.0 with the correct interface-scoped next hop and test traffic reaches the peer.
Explanation
Correct Answer
D:The IPv6 route is active in inet6.0 with the correct interface-scoped next hop and test traffic reaches the peer. This tests the actual condition identified in the live production incident: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. It is meaningful because An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop.
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: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. A relevant acceptance result here is: The IPv6 route is active in inet6.0 with the correct interface-scoped next hop and test traffic reaches the peer.
B: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: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. A relevant acceptance result here is: The IPv6 route is active in inet6.0 with the correct interface-scoped next hop and test traffic reaches the peer.
C: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: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. A relevant acceptance result here is: The IPv6 route is active in inet6.0 with the correct interface-scoped next hop and test traffic reaches the peer.
Question 233
During production incident triage, engineers observe: A customer CE is connected to an access port configured for VLAN 110, while its service should be VLAN 120, and its frames cannot reach the correct broadcast domain. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- A controlled untagged frame maps to the same intended VLAN on both ends and no unauthorized L2 reachability remains.
- Initial flooding is VLAN-scoped, then subsequent frames to the learned MAC use the correct specific egress port.
- The customer MAC and VLAN appear in the correct virtual-switch instance with no leakage into default bridging context.
- The CE MAC is learned in VLAN 120 and its frames reach a same-VLAN peer without leaking into VLAN 110.
Explanation
Correct Answer
D:The CE MAC is learned in VLAN 120 and its frames reach a same-VLAN peer without leaking into VLAN 110. This tests the actual condition identified in the live production incident: A customer CE is connected to an access port configured for VLAN 110, while its service should be VLAN 120, and its frames cannot reach the correct broadcast domain. It is meaningful because An access port classifies untagged received frames into its configured VLAN, which determines Layer 2 forwarding membership.
Incorrect Answers
A:A controlled untagged frame maps to the same intended VLAN on both ends and no unauthorized L2 reachability remains. This measurement may prove the unrelated Native VLAN mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A customer CE is connected to an access port configured for VLAN 110, while its service should be VLAN 120, and its frames cannot reach the correct broadcast domain. A relevant acceptance result here is: The CE MAC is learned in VLAN 120 and its frames reach a same-VLAN peer without leaking into VLAN 110.
B:Initial flooding is VLAN-scoped, then subsequent frames to the learned MAC use the correct specific egress port. This measurement may prove the unrelated Unknown unicast flooding behavior condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A customer CE is connected to an access port configured for VLAN 110, while its service should be VLAN 120, and its frames cannot reach the correct broadcast domain. A relevant acceptance result here is: The CE MAC is learned in VLAN 120 and its frames reach a same-VLAN peer without leaking into VLAN 110.
C:The customer MAC and VLAN appear in the correct virtual-switch instance with no leakage into default bridging context. This measurement may prove the unrelated Virtual switch instance membership condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A customer CE is connected to an access port configured for VLAN 110, while its service should be VLAN 120, and its frames cannot reach the correct broadcast domain. A relevant acceptance result here is: The CE MAC is learned in VLAN 120 and its frames reach a same-VLAN peer without leaking into VLAN 110.
Question 234
During production incident triage, engineers observe: A router attempts graceful routing restart but downstream peers remove its routes immediately because helper behavior is not available or the restart contract is unmet. 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 active member count and per-link utilization match service design, and the aggregate handles representative traffic without excessive drops.
- The designated router is primary under normal conditions and the backup takes over promptly during an injected outage.
- Peer capability and restart-state logs show the intended graceful behavior, and routes remain valid during the controlled test.
Explanation
Correct Answer
D:Peer capability and restart-state logs show the intended graceful behavior, and routes remain valid during the controlled test. This tests the actual condition identified in the live production incident: A router attempts graceful routing restart but downstream peers remove its routes immediately because helper behavior is not available or the restart contract is unmet. It is meaningful because Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior.
Incorrect Answers
A:All intended members show collecting and distributing state in the correct AE bundle and packet forwarding is stable. This measurement may prove the unrelated LACP partner mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A router attempts graceful routing restart but downstream peers remove its routes immediately because helper behavior is not available or the restart contract is unmet. A relevant acceptance result here is: Peer capability and restart-state logs show the intended graceful behavior, and routes remain valid during the controlled test.
B:The active member count and per-link utilization match service design, and the aggregate handles representative traffic without excessive drops. This measurement may prove the unrelated LAG member imbalance after failure condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A router attempts graceful routing restart but downstream peers remove its routes immediately because helper behavior is not available or the restart contract is unmet. A relevant acceptance result here is: Peer capability and restart-state logs show the intended graceful behavior, and routes remain valid during the controlled test.
C: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: A router attempts graceful routing restart but downstream peers remove its routes immediately because helper behavior is not available or the restart contract is unmet. A relevant acceptance result here is: Peer capability and restart-state logs show the intended graceful behavior, and routes remain valid during the controlled test.
Question 235
During production incident triage, engineers observe: A prefix is received from a valid BGP peer but remains unusable because the advertised BGP next hop has no resolving route in the local table. 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 multihop session forms between the designed IP endpoints, TTL is appropriate and only intended neighbors can connect.
- The received BGP route resolves its next hop, becomes eligible, and forwards over the designed path.
- The rejected prefix does not appear as an eligible route while approved advertised prefixes remain available.
Explanation
Correct Answer
C:The received BGP route resolves its next hop, becomes eligible, and forwards over the designed path. This tests the actual condition identified in the live production incident: A prefix is received from a valid BGP peer but remains unusable because the advertised BGP next hop has no resolving route in the local table. It is meaningful because BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection.
Incorrect Answers
A:A TCP session is established to the correct neighbor address, BGP reaches Established and intended routes are exchanged. This measurement may prove the unrelated BGP TCP transport blocked condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A prefix is received from a valid BGP peer but remains unusable because the advertised BGP next hop has no resolving route in the local table. A relevant acceptance result here is: The received BGP route resolves its next hop, becomes eligible, and forwards over the designed path.
B:The multihop session forms between the designed IP endpoints, TTL is appropriate and only intended neighbors can connect. This measurement may prove the unrelated EBGP multihop peering condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A prefix is received from a valid BGP peer but remains unusable because the advertised BGP next hop has no resolving route in the local table. A relevant acceptance result here is: The received BGP route resolves its next hop, becomes eligible, and forwards over the designed path.
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: A prefix is received from a valid BGP peer but remains unusable because the advertised BGP next hop has no resolving route in the local table. A relevant acceptance result here is: The received BGP route resolves its next hop, becomes eligible, and forwards over the designed path.
Question 236
During production incident triage, engineers observe: An eBGP IPv4 session is Established and carries inet routes, but expected IPv6 prefixes never appear because inet6 unicast is not enabled for the peering design. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The peer exchanges approved IPv6 routes and their next hops resolve into inet6.0 without exposing unintended prefixes.
- The received BGP route resolves its next hop, becomes eligible, and forwards over the designed path.
- The designated BGP exit wins best-path selection for the intended prefixes and backup behavior remains correct.
- A route detail comparison shows the relevant AS-path difference and chosen path conforms to approved policy.
Explanation
Correct Answer
A:The peer exchanges approved IPv6 routes and their next hops resolve into inet6.0 without exposing unintended prefixes. This tests the actual condition identified in the live production incident: An eBGP IPv4 session is Established and carries inet routes, but expected IPv6 prefixes never appear because inet6 unicast is not enabled for the peering design. It is meaningful because BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session.
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: An eBGP IPv4 session is Established and carries inet routes, but expected IPv6 prefixes never appear because inet6 unicast is not enabled for the peering design. A relevant acceptance result here is: The peer exchanges approved IPv6 routes and their next hops resolve into inet6.0 without exposing unintended prefixes.
C:The designated BGP exit wins best-path selection for the intended prefixes and backup behavior remains correct. This measurement may prove the unrelated BGP local preference egress condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An eBGP IPv4 session is Established and carries inet routes, but expected IPv6 prefixes never appear because inet6 unicast is not enabled for the peering design. A relevant acceptance result here is: The peer exchanges approved IPv6 routes and their next hops resolve into inet6.0 without exposing unintended prefixes.
D: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: An eBGP IPv4 session is Established and carries inet routes, but expected IPv6 prefixes never appear because inet6 unicast is not enabled for the peering design. A relevant acceptance result here is: The peer exchanges approved IPv6 routes and their next hops resolve into inet6.0 without exposing unintended prefixes.
Question 237
During production incident triage, engineers observe: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- Hosts reach their VLAN gateway, the IRB interface appears active, and inter-VLAN traffic follows the intended security policy.
- Initial flooding is VLAN-scoped, then subsequent frames to the learned MAC use the correct specific egress port.
- A same-tag packet from one customer cannot reach the other's service, while each customer's traffic traverses its own outer VLAN.
- A controlled untagged frame maps to the same intended VLAN on both ends and no unauthorized L2 reachability remains.
Explanation
Correct Answer
C:A same-tag packet from one customer cannot reach the other's service, while each customer's traffic traverses its own outer VLAN. This tests the actual condition identified in the live production incident: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. It is meaningful because Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers.
Incorrect Answers
A:Hosts reach their VLAN gateway, the IRB interface appears active, and inter-VLAN traffic follows the intended security policy. This measurement may prove the unrelated IRB routed gateway missing condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. A relevant acceptance result here is: A same-tag packet from one customer cannot reach the other's service, while each customer's traffic traverses its own outer VLAN.
B:Initial flooding is VLAN-scoped, then subsequent frames to the learned MAC use the correct specific egress port. This measurement may prove the unrelated Unknown unicast flooding behavior condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. A relevant acceptance result here is: A same-tag packet from one customer cannot reach the other's service, while each customer's traffic traverses its own outer VLAN.
D:A controlled untagged frame maps to the same intended VLAN on both ends and no unauthorized L2 reachability remains. This measurement may prove the unrelated Native VLAN mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. A relevant acceptance result here is: A same-tag packet from one customer cannot reach the other's service, while each customer's traffic traverses its own outer VLAN.
Question 238
During production incident triage, engineers observe: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The LSP reserves its intended bandwidth end to end without exceeding the engineered link limits.
- The core interface is MPLS enabled and labeled forwarding entries exist for the expected transport destination.
- An LDP session reaches Operational and displays the intended neighbor label bindings after selective filter correction.
- The relevant FEC has a reachable next hop and valid incoming and outgoing label entries along the intended LSP.
Explanation
Correct Answer
A:The LSP reserves its intended bandwidth end to end without exceeding the engineered link limits. This tests the actual condition identified in the live production incident: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. It is meaningful because RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability.
Incorrect Answers
B:The core interface is MPLS enabled and labeled forwarding entries exist for the expected transport destination. This measurement may prove the unrelated MPLS interface not enabled condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. A relevant acceptance result here is: The LSP reserves its intended bandwidth end to end without exceeding the engineered link limits.
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 new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. A relevant acceptance result here is: The LSP reserves its intended bandwidth end to end without exceeding the engineered link limits.
D:The relevant FEC has a reachable next hop and valid incoming and outgoing label entries along the intended LSP. This measurement may prove the unrelated Missing LDP FEC label mapping condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. A relevant acceptance result here is: The LSP reserves its intended bandwidth end to end without exceeding the engineered link limits.
Question 239
During production incident triage, engineers observe: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- Authenticated OSPF packet exchange resumes, the neighbor reaches Full and no authentication failures remain in logs.
- Internal prefixes remain present, the designed default is learned, and external traffic follows that default without type-5 LSAs in the stub.
- An appropriate eligible router becomes DR or BDR after a controlled election and neighbor adjacency remains stable.
- Each endpoint shows a point-to-point interface and one stable Full neighbor without DR or BDR expectations.
Explanation
Correct Answer
A:Authenticated OSPF packet exchange resumes, the neighbor reaches Full and no authentication failures remain in logs. This tests the actual condition identified in the live production incident: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. It is meaningful because OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree.
Incorrect Answers
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 rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. A relevant acceptance result here is: Authenticated OSPF packet exchange resumes, the neighbor reaches Full and no authentication failures remain in logs.
C: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: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. A relevant acceptance result here is: Authenticated OSPF packet exchange resumes, the neighbor reaches Full and no authentication failures remain in logs.
D:Each endpoint shows a point-to-point interface and one stable Full neighbor without DR or BDR expectations. This measurement may prove the unrelated Point-to-point OSPF network type condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. A relevant acceptance result here is: Authenticated OSPF packet exchange resumes, the neighbor reaches Full and no authentication failures remain in logs.
Question 240
During production incident triage, engineers observe: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The two interfaces report matching timers and the neighbor stays Full beyond several dead intervals.
- No OSPF neighbors form on the customer LAN, yet core routers still learn the intended LAN prefix.
- An appropriate eligible router becomes DR or BDR after a controlled election and neighbor adjacency remains stable.
- Both peers show the expected current LSAs with consistent sequence and topology, and the computed path reaches the destination.
Explanation
Correct Answer
B:No OSPF neighbors form on the customer LAN, yet core routers still learn the intended LAN prefix. This tests the actual condition identified in the live production incident: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. It is meaningful because Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information.
Incorrect Answers
A:The two interfaces report matching timers and the neighbor stays Full beyond several dead intervals. This measurement may prove the unrelated OSPF hello dead timer mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. A relevant acceptance result here is: No OSPF neighbors form on the customer LAN, yet core routers still learn the intended LAN prefix.
C: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: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. A relevant acceptance result here is: No OSPF neighbors form on the customer LAN, yet core routers still learn the intended LAN prefix.
D: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: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. A relevant acceptance result here is: No OSPF neighbors form on the customer LAN, yet core routers still learn the intended LAN prefix.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests