Question 440
During production incident triage, engineers observe: PE-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Use multi-flow telemetry and documented hashing expectations when evaluating ECMP efficiency.
- Monitor aggregate active state and contributor counts before each upstream announcement change.
- Check classifier counters, filter attachment and target-table availability after changes.
- Review first-match precedence with representative negative and positive traffic tests.
Explanation
Correct Answer
B:Monitor aggregate active state and contributor counts before each upstream announcement change. The current live production incident demonstrates why this check matters: PE-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. It monitors the mechanism that A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active. The continuing safeguard should be correlated with the specific acceptance test: The aggregate appears as an active route with contributing prefixes shown, and the permitted summary is advertised to the intended peer.
Incorrect Answers
A:Use multi-flow telemetry and documented hashing expectations when evaluating ECMP efficiency. This control addresses the distinct Per-flow hash expectation operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: PE-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. The directly relevant continuing check is: Monitor aggregate active state and contributor counts before each upstream announcement change. The governing mechanism is: A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active.
C:Check classifier counters, filter attachment and target-table availability after changes. This control addresses the distinct Filter-based forwarding classification operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: PE-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. The directly relevant continuing check is: Monitor aggregate active state and contributor counts before each upstream announcement change. The governing mechanism is: A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active.
D:Review first-match precedence with representative negative and positive traffic tests. This control addresses the distinct Filter policy overmatch operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: PE-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. The directly relevant continuing check is: Monitor aggregate active state and contributor counts before each upstream announcement change. The governing mechanism is: A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active.
Question 441
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. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Check peer-specific TCP reachability and filtering during peering change control.
- Document peer distance, TTL, and authorized transport path for remote eBGP sessions.
- Monitor unresolved BGP next hops separately from session establishment.
- Review inbound prefix filtering and max-route thresholds with every peer change.
Explanation
Correct Answer
C:Monitor unresolved BGP next hops separately from session establishment. The current live production incident demonstrates why this check matters: 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 monitors the mechanism that BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection. The continuing safeguard should be correlated with the specific acceptance test: The received BGP route resolves its next hop, becomes eligible, and forwards over the designed path.
Incorrect Answers
A:Check peer-specific TCP reachability and filtering during peering change control. This control addresses the distinct BGP TCP transport blocked operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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. The directly relevant continuing check is: Monitor unresolved BGP next hops separately from session establishment. The governing mechanism is: BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection.
B:Document peer distance, TTL, and authorized transport path for remote eBGP sessions. This control addresses the distinct EBGP multihop peering operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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. The directly relevant continuing check is: Monitor unresolved BGP next hops separately from session establishment. The governing mechanism is: BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection.
D:Review inbound prefix filtering and max-route thresholds with every peer change. This control addresses the distinct BGP import policy leak operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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. The directly relevant continuing check is: Monitor unresolved BGP next hops separately from session establishment. The governing mechanism is: BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection.
Question 442
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. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Document stub and normal area policies and validate expected LSA types.
- Document broadcast-segment DR priorities and rehearse controlled elections.
- Include interface network-type checks in PE-to-PE circuit acceptance.
- Rotate authenticated neighbor keys using synchronized maintenance and failure rollback checks.
Explanation
Correct Answer
D:Rotate authenticated neighbor keys using synchronized maintenance and failure rollback checks. The current live production incident demonstrates why this check matters: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. It monitors the mechanism that OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree. The continuing safeguard should be correlated with the specific acceptance test: Authenticated OSPF packet exchange resumes, the neighbor reaches Full and no authentication failures remain in logs.
Incorrect Answers
A:Document stub and normal area policies and validate expected LSA types. This control addresses the distinct Stub area external LSA expectation operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. The directly relevant continuing check is: Rotate authenticated neighbor keys using synchronized maintenance and failure rollback checks. The governing mechanism is: OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree.
B:Document broadcast-segment DR priorities and rehearse controlled elections. This control addresses the distinct DR priority zero misconception operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. The directly relevant continuing check is: Rotate authenticated neighbor keys using synchronized maintenance and failure rollback checks. The governing mechanism is: OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree.
C:Include interface network-type checks in PE-to-PE circuit acceptance. This control addresses the distinct Point-to-point OSPF network type operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. The directly relevant continuing check is: Rotate authenticated neighbor keys using synchronized maintenance and failure rollback checks. The governing mechanism is: OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree.
Question 443
During production incident triage, engineers observe: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Review route-preference conventions for static backups during routing-policy audits.
- Review first-match precedence with representative negative and positive traffic tests.
- Monitor aggregate active state and contributor counts before each upstream announcement change.
- Track ECMP next-hop count and routing-cost drift after transport changes.
Explanation
Correct Answer
B:Review first-match precedence with representative negative and positive traffic tests. The current live production incident demonstrates why this check matters: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. It monitors the mechanism that Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. The continuing safeguard should be correlated with the specific acceptance test: Matched and unmatched packet samples increment their intended counters and resolve to the expected respective routing tables.
Incorrect Answers
A:Review route-preference conventions for static backups during routing-policy audits. This control addresses the distinct Administrative preference overrides static operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. The directly relevant continuing check is: Review first-match precedence with representative negative and positive traffic tests. The governing mechanism is: Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules.
C:Monitor aggregate active state and contributor counts before each upstream announcement change. This control addresses the distinct Aggregate route contribution operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. The directly relevant continuing check is: Review first-match precedence with representative negative and positive traffic tests. The governing mechanism is: Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules.
D:Track ECMP next-hop count and routing-cost drift after transport changes. This control addresses the distinct Equal-cost multipath eligibility operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. The directly relevant continuing check is: Review first-match precedence with representative negative and positive traffic tests. The governing mechanism is: Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules.
Question 444
During production incident triage, engineers observe: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Check MPLS interface participation during each core link turn-up.
- Compare LDP-enabled links with IGP core interfaces after changes.
- Track intended one-way and reverse-path LSP inventories for bidirectional services.
- Check LDP session transport filtering as part of control-plane ACL reviews.
Explanation
Correct Answer
C:Track intended one-way and reverse-path LSP inventories for bidirectional services. The current live production incident demonstrates why this check matters: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. It monitors the mechanism that RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP. The continuing safeguard should be correlated with the specific acceptance test: Forward and reverse tests each map to separately verified forwarding paths with their intended egress destinations.
Incorrect Answers
A:Check MPLS interface participation during each core link turn-up. This control addresses the distinct MPLS interface not enabled operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. The directly relevant continuing check is: Track intended one-way and reverse-path LSP inventories for bidirectional services. The governing mechanism is: RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP.
B:Compare LDP-enabled links with IGP core interfaces after changes. This control addresses the distinct LDP discovery and IGP mismatch operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. The directly relevant continuing check is: Track intended one-way and reverse-path LSP inventories for bidirectional services. The governing mechanism is: RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP.
D:Check LDP session transport filtering as part of control-plane ACL reviews. This control addresses the distinct LDP TCP 646 establishment operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. The directly relevant continuing check is: Track intended one-way and reverse-path LSP inventories for bidirectional services. The governing mechanism is: RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP.
Question 445
During production incident triage, engineers observe: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Check MPLS interface participation during each core link turn-up.
- Compare LDP-enabled links with IGP core interfaces after changes.
- Document expected label stacks at ingress, transit and penultimate hop for key services.
- Continuously validate configured RSVP explicit paths against network topology inventory.
Explanation
Correct Answer
D:Continuously validate configured RSVP explicit paths against network topology inventory. The current live production incident demonstrates why this check matters: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. It monitors the mechanism that RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange. The continuing safeguard should be correlated with the specific acceptance test: The RSVP LSP becomes operational on the authorized explicit route and reports a complete signaled path.
Incorrect Answers
A:Check MPLS interface participation during each core link turn-up. This control addresses the distinct MPLS interface not enabled operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. The directly relevant continuing check is: Continuously validate configured RSVP explicit paths against network topology inventory. The governing mechanism is: RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange.
B:Compare LDP-enabled links with IGP core interfaces after changes. This control addresses the distinct LDP discovery and IGP mismatch operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. The directly relevant continuing check is: Continuously validate configured RSVP explicit paths against network topology inventory. The governing mechanism is: RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange.
C:Document expected label stacks at ingress, transit and penultimate hop for key services. This control addresses the distinct Penultimate hop popping operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. The directly relevant continuing check is: Continuously validate configured RSVP explicit paths against network topology inventory. The governing mechanism is: RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange.
Question 446
During production incident triage, engineers observe: Two routers become OSPF neighbors but repeatedly remain in ExStart or Exchange after a transport change that reduced interface MTU on one end. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Include OSPF interface MTU checks in transport migration validation.
- Baseline OSPF timer settings per transport class and alert on configuration drift.
- Alert on repeated OSPF adjacency resets and divergent LSA conditions.
- Rotate authenticated neighbor keys using synchronized maintenance and failure rollback checks.
Explanation
Correct Answer
A:Include OSPF interface MTU checks in transport migration validation. The current live production incident demonstrates why this check matters: Two routers become OSPF neighbors but repeatedly remain in ExStart or Exchange after a transport change that reduced interface MTU on one end. It monitors the mechanism that OSPF database description negotiation checks interface compatibility; mismatched MTU can prevent the adjacency from progressing to Full. The continuing safeguard should be correlated with the specific acceptance test: Both sides report compatible MTU and move through Exchange to Full with a synchronized LSDB.
Incorrect Answers
B:Baseline OSPF timer settings per transport class and alert on configuration drift. This control addresses the distinct OSPF hello dead timer mismatch operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: Two routers become OSPF neighbors but repeatedly remain in ExStart or Exchange after a transport change that reduced interface MTU on one end. The directly relevant continuing check is: Include OSPF interface MTU checks in transport migration validation. The governing mechanism is: OSPF database description negotiation checks interface compatibility; mismatched MTU can prevent the adjacency from progressing to Full.
C:Alert on repeated OSPF adjacency resets and divergent LSA conditions. This control addresses the distinct OSPF LSDB discrepancy operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: Two routers become OSPF neighbors but repeatedly remain in ExStart or Exchange after a transport change that reduced interface MTU on one end. The directly relevant continuing check is: Include OSPF interface MTU checks in transport migration validation. The governing mechanism is: OSPF database description negotiation checks interface compatibility; mismatched MTU can prevent the adjacency from progressing to Full.
D:Rotate authenticated neighbor keys using synchronized maintenance and failure rollback checks. This control addresses the distinct OSPF authentication key mismatch operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: Two routers become OSPF neighbors but repeatedly remain in ExStart or Exchange after a transport change that reduced interface MTU on one end. The directly relevant continuing check is: Include OSPF interface MTU checks in transport migration validation. The governing mechanism is: OSPF database description negotiation checks interface compatibility; mismatched MTU can prevent the adjacency from progressing to Full.
Question 447
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. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Validate planned VRRP priorities and failover behavior after router maintenance.
- Monitor VRRP failover and preempt events correlated to upstream route health.
- Audit LACP partner identity and collecting/distributing state during bundle maintenance.
- Baseline BFD timer settings by platform and monitor false-flap trends.
Explanation
Correct Answer
C:Audit LACP partner identity and collecting/distributing state during bundle maintenance. The current live production incident demonstrates why this check matters: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. It monitors the mechanism that LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone. The continuing safeguard should be correlated with the specific acceptance test: All intended members show collecting and distributing state in the correct AE bundle and packet forwarding is stable.
Incorrect Answers
A:Validate planned VRRP priorities and failover behavior after router maintenance. This control addresses the distinct VRRP master priority failover operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. The directly relevant continuing check is: Audit LACP partner identity and collecting/distributing state during bundle maintenance. The governing mechanism is: LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone.
B:Monitor VRRP failover and preempt events correlated to upstream route health. This control addresses the distinct VRRP preemption oscillation operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. The directly relevant continuing check is: Audit LACP partner identity and collecting/distributing state during bundle maintenance. The governing mechanism is: LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone.
D:Baseline BFD timer settings by platform and monitor false-flap trends. This control addresses the distinct BFD detect timer too aggressive operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. The directly relevant continuing check is: Audit LACP partner identity and collecting/distributing state during bundle maintenance. The governing mechanism is: LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone.
Question 448
During production incident triage, engineers observe: An IPv6 routing interface has global unicast addresses and a healthy OSPFv2 adjacency, yet OSPFv3 neighbor state is absent and no IPv6 routes are learned. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Test both outer IPv4 reachability and inner IPv6 routes during tunnel maintenance.
- Monitor OSPFv2 and OSPFv3 neighbor health independently on dual-stack links.
- Exercise large-packet IPv6 and PMTU tests through tunneled or low-MTU paths.
- Inspect both protocol levels' IPv6 TLV propagation during dual-stack deployments.
Explanation
Correct Answer
B:Monitor OSPFv2 and OSPFv3 neighbor health independently on dual-stack links. The current live production incident demonstrates why this check matters: An IPv6 routing interface has global unicast addresses and a healthy OSPFv2 adjacency, yet OSPFv3 neighbor state is absent and no IPv6 routes are learned. It monitors the mechanism that OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2. The continuing safeguard should be correlated with the specific acceptance test: The OSPFv3 neighbor reaches the expected state and learned IPv6 prefixes appear in inet6.0.
Incorrect Answers
A:Test both outer IPv4 reachability and inner IPv6 routes during tunnel maintenance. This control addresses the distinct IPv6 over IPv4 transit tunnel operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: An IPv6 routing interface has global unicast addresses and a healthy OSPFv2 adjacency, yet OSPFv3 neighbor state is absent and no IPv6 routes are learned. The directly relevant continuing check is: Monitor OSPFv2 and OSPFv3 neighbor health independently on dual-stack links. The governing mechanism is: OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2.
C:Exercise large-packet IPv6 and PMTU tests through tunneled or low-MTU paths. This control addresses the distinct ICMPv6 packet-too-big handling operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: An IPv6 routing interface has global unicast addresses and a healthy OSPFv2 adjacency, yet OSPFv3 neighbor state is absent and no IPv6 routes are learned. The directly relevant continuing check is: Monitor OSPFv2 and OSPFv3 neighbor health independently on dual-stack links. The governing mechanism is: OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2.
D:Inspect both protocol levels' IPv6 TLV propagation during dual-stack deployments. This control addresses the distinct IS-IS IPv6 reachability TLVs operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: An IPv6 routing interface has global unicast addresses and a healthy OSPFv2 adjacency, yet OSPFv3 neighbor state is absent and no IPv6 routes are learned. The directly relevant continuing check is: Monitor OSPFv2 and OSPFv3 neighbor health independently on dual-stack links. The governing mechanism is: OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2.
Question 449
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. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Validate NET area planning and permitted levels before adding a core adjacency.
- Review link-level capability profiles for L1, L2 and L1/L2 routers.
- Include interface family iso in standardized IS-IS provisioning templates.
- Maintain a registry of ISO NET system IDs across every area and lab clone.
Explanation
Correct Answer
C:Include interface family iso in standardized IS-IS provisioning templates. The current live production incident demonstrates why this check matters: 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 monitors the mechanism that Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration. The continuing safeguard should be correlated with the specific acceptance test: IS-IS Hello exchanges appear and the expected level adjacency establishes while IPv4 traffic still functions.
Incorrect Answers
A:Validate NET area planning and permitted levels before adding a core adjacency. This control addresses the distinct IS-IS level-one area mismatch operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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. The directly relevant continuing check is: Include interface family iso in standardized IS-IS provisioning templates. The governing mechanism is: Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration.
B:Review link-level capability profiles for L1, L2 and L1/L2 routers. This control addresses the distinct IS-IS level capability mismatch operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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. The directly relevant continuing check is: Include interface family iso in standardized IS-IS provisioning templates. The governing mechanism is: Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration.
D:Maintain a registry of ISO NET system IDs across every area and lab clone. This control addresses the distinct Duplicate IS-IS system ID operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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. The directly relevant continuing check is: Include interface family iso in standardized IS-IS provisioning templates. The governing mechanism is: Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration.
Question 450
During production incident triage, engineers observe: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Include interface family iso in standardized IS-IS provisioning templates.
- Baseline metric-style compatibility before area-wide IS-IS cost adjustments.
- Validate NET area planning and permitted levels before adding a core adjacency.
- Record DIS priorities and pseudonode behavior in service-provider switching design reviews.
Explanation
Correct Answer
C:Validate NET area planning and permitted levels before adding a core adjacency. The current live production incident demonstrates why this check matters: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. It monitors the mechanism that IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas. The continuing safeguard should be correlated with the specific acceptance test: The two devices show an up adjacency at the intended level and their Level 1 link-state databases exchange reachability.
Incorrect Answers
A:Include interface family iso in standardized IS-IS provisioning templates. This control addresses the distinct IS-IS ISO family missing operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. The directly relevant continuing check is: Validate NET area planning and permitted levels before adding a core adjacency. The governing mechanism is: IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas.
B:Baseline metric-style compatibility before area-wide IS-IS cost adjustments. This control addresses the distinct IS-IS narrow metric ceiling operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. The directly relevant continuing check is: Validate NET area planning and permitted levels before adding a core adjacency. The governing mechanism is: IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas.
D:Record DIS priorities and pseudonode behavior in service-provider switching design reviews. This control addresses the distinct IS-IS DIS election surprise operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. The directly relevant continuing check is: Validate NET area planning and permitted levels before adding a core adjacency. The governing mechanism is: IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests