Question 920
During a controlled acceptance rehearsal of the same defect on a separate test network, 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?
- Audit LACP partner identity and collecting/distributing state during bundle maintenance.
- Baseline BFD timer settings by platform and monitor false-flap trends.
- Test control-plane and data-plane continuity separately under planned RE switchovers.
- Audit NSR state and replicate routing databases before maintenance windows.
Explanation
Correct Answer
A:Audit LACP partner identity and collecting/distributing state during bundle maintenance. The current controlled acceptance rehearsal 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
B: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 controlled acceptance rehearsal. 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.
C:Test control-plane and data-plane continuity separately under planned RE switchovers. This control addresses the distinct GRES forwarding versus routing continuity operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. 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:Audit NSR state and replicate routing databases before maintenance windows. This control addresses the distinct NSR backup routing synchronization operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. 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 921
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Hosts in a VLAN can bridge to each other but cannot reach a different subnet because the VLAN has no correctly attached integrated routing and bridging interface. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Audit VLAN-to-IRB bindings and routed interfaces during new service activation.
- Validate both tag layers at each wholesale handoff and monitor service-tag drift.
- Maintain unique outer service identifiers for separate tenants and test cross-tenant isolation.
- Monitor unknown-unicast rate together with MAC-table learning and churn.
Explanation
Correct Answer
A:Audit VLAN-to-IRB bindings and routed interfaces during new service activation. The current controlled acceptance rehearsal demonstrates why this check matters: Hosts in a VLAN can bridge to each other but cannot reach a different subnet because the VLAN has no correctly attached integrated routing and bridging interface. It monitors the mechanism that An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching. The continuing safeguard should be correlated with the specific acceptance test: Hosts reach their VLAN gateway, the IRB interface appears active, and inter-VLAN traffic follows the intended security policy.
Incorrect Answers
B:Validate both tag layers at each wholesale handoff and monitor service-tag drift. This control addresses the distinct Q-in-Q outer tag mismatch operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: Hosts in a VLAN can bridge to each other but cannot reach a different subnet because the VLAN has no correctly attached integrated routing and bridging interface. The directly relevant continuing check is: Audit VLAN-to-IRB bindings and routed interfaces during new service activation. The governing mechanism is: An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching.
C:Maintain unique outer service identifiers for separate tenants and test cross-tenant isolation. This control addresses the distinct Provider VLAN customer isolation operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: Hosts in a VLAN can bridge to each other but cannot reach a different subnet because the VLAN has no correctly attached integrated routing and bridging interface. The directly relevant continuing check is: Audit VLAN-to-IRB bindings and routed interfaces during new service activation. The governing mechanism is: An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching.
D:Monitor unknown-unicast rate together with MAC-table learning and churn. This control addresses the distinct Unknown unicast flooding behavior operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: Hosts in a VLAN can bridge to each other but cannot reach a different subnet because the VLAN has no correctly attached integrated routing and bridging interface. The directly relevant continuing check is: Audit VLAN-to-IRB bindings and routed interfaces during new service activation. The governing mechanism is: An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching.
Question 922
During a controlled acceptance rehearsal of the same defect on a separate test network, 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?
- Maintain a registry of ISO NET system IDs across every area and lab clone.
- Baseline metric-style compatibility before area-wide IS-IS cost adjustments.
- Include interface family iso in standardized IS-IS provisioning templates.
- Monitor Level 1 attached-bit or default-route availability at area boundaries.
Explanation
Correct Answer
C:Include interface family iso in standardized IS-IS provisioning templates. The current controlled acceptance rehearsal 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: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 controlled acceptance rehearsal. 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: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 controlled acceptance rehearsal. 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:Monitor Level 1 attached-bit or default-route availability at area boundaries. This control addresses the distinct IS-IS Level 1 exit default operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. 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 923
During a controlled acceptance rehearsal of the same defect on a separate test network, 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. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Include AS-path comparisons in periodic interdomain routing audit reports.
- Check BGP negotiated families and IPv6 route policy during dual-stack migrations.
- Document intended MED comparison scope and test different-neighbor-AS cases.
- Record negotiated BGP timers and correlate flap events with packet-loss telemetry.
Explanation
Correct Answer
B:Check BGP negotiated families and IPv6 route policy during dual-stack migrations. The current controlled acceptance rehearsal demonstrates why this check matters: 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 monitors the mechanism that BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session. The continuing safeguard should be correlated with the specific acceptance test: The peer exchanges approved IPv6 routes and their next hops resolve into inet6.0 without exposing unintended prefixes.
Incorrect Answers
A:Include AS-path comparisons in periodic interdomain routing audit reports. This control addresses the distinct BGP AS-path comparison operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here 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. The directly relevant continuing check is: Check BGP negotiated families and IPv6 route policy during dual-stack migrations. The governing mechanism is: BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session.
C:Document intended MED comparison scope and test different-neighbor-AS cases. This control addresses the distinct BGP MED comparison scope operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here 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. The directly relevant continuing check is: Check BGP negotiated families and IPv6 route policy during dual-stack migrations. The governing mechanism is: BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session.
D:Record negotiated BGP timers and correlate flap events with packet-loss telemetry. This control addresses the distinct BGP peer flap from mismatched hold timers operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here 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. The directly relevant continuing check is: Check BGP negotiated families and IPv6 route policy during dual-stack migrations. The governing mechanism is: BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session.
Question 924
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: IS-IS neighbors are up for IPv4, but IPv6 routes do not appear because the IPv6 reachability information is not advertised in supported IS-IS TLVs. 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.
- Exercise large-packet IPv6 and PMTU tests through tunneled or low-MTU paths.
- Inspect both protocol levels' IPv6 TLV propagation during dual-stack deployments.
- Monitor OSPFv2 and OSPFv3 neighbor health independently on dual-stack links.
Explanation
Correct Answer
C:Inspect both protocol levels' IPv6 TLV propagation during dual-stack deployments. The current controlled acceptance rehearsal demonstrates why this check matters: IS-IS neighbors are up for IPv4, but IPv6 routes do not appear because the IPv6 reachability information is not advertised in supported IS-IS TLVs. It monitors the mechanism that IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information. The continuing safeguard should be correlated with the specific acceptance test: The relevant IPv6 reachability TLVs are present and remote IPv6 prefixes become active 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 controlled acceptance rehearsal. The observed problem here is: IS-IS neighbors are up for IPv4, but IPv6 routes do not appear because the IPv6 reachability information is not advertised in supported IS-IS TLVs. The directly relevant continuing check is: Inspect both protocol levels' IPv6 TLV propagation during dual-stack deployments. The governing mechanism is: IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information.
B: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 controlled acceptance rehearsal. The observed problem here is: IS-IS neighbors are up for IPv4, but IPv6 routes do not appear because the IPv6 reachability information is not advertised in supported IS-IS TLVs. The directly relevant continuing check is: Inspect both protocol levels' IPv6 TLV propagation during dual-stack deployments. The governing mechanism is: IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information.
D:Monitor OSPFv2 and OSPFv3 neighbor health independently on dual-stack links. This control addresses the distinct OSPFv3 neighbor uses link-local operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: IS-IS neighbors are up for IPv4, but IPv6 routes do not appear because the IPv6 reachability information is not advertised in supported IS-IS TLVs. The directly relevant continuing check is: Inspect both protocol levels' IPv6 TLV propagation during dual-stack deployments. The governing mechanism is: IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information.
Question 925
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An infrastructure route is present in inet.0 but absent from a secondary table whose applications depend on that route, and operators assume all tables automatically share entries. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Exercise backup-path liveness detection under downstream and local failure scenarios.
- Review first-match precedence with representative negative and positive traffic tests.
- Review import/export scope and route-copy audits when new routing instances are introduced.
- Maintain explicit inter-instance route-leak allowlists and regression tests.
Explanation
Correct Answer
C:Review import/export scope and route-copy audits when new routing instances are introduced. The current controlled acceptance rehearsal demonstrates why this check matters: An infrastructure route is present in inet.0 but absent from a secondary table whose applications depend on that route, and operators assume all tables automatically share entries. It monitors the mechanism that Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms. The continuing safeguard should be correlated with the specific acceptance test: The intended route appears in both authorized tables with the right next hop, while unrelated routes are not leaked.
Incorrect Answers
A:Exercise backup-path liveness detection under downstream and local failure scenarios. This control addresses the distinct Static backup blackhole operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: An infrastructure route is present in inet.0 but absent from a secondary table whose applications depend on that route, and operators assume all tables automatically share entries. The directly relevant continuing check is: Review import/export scope and route-copy audits when new routing instances are introduced. The governing mechanism is: Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms.
B: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 controlled acceptance rehearsal. The observed problem here is: An infrastructure route is present in inet.0 but absent from a secondary table whose applications depend on that route, and operators assume all tables automatically share entries. The directly relevant continuing check is: Review import/export scope and route-copy audits when new routing instances are introduced. The governing mechanism is: Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms.
D:Maintain explicit inter-instance route-leak allowlists and regression tests. This control addresses the distinct Routing instance cross-leak operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: An infrastructure route is present in inet.0 but absent from a secondary table whose applications depend on that route, and operators assume all tables automatically share entries. The directly relevant continuing check is: Review import/export scope and route-copy audits when new routing instances are introduced. The governing mechanism is: Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms.
Question 926
During a controlled acceptance rehearsal of the same defect on a separate test network, 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?
- Rotate authenticated neighbor keys using synchronized maintenance and failure rollback checks.
- Test backbone adjacency and ABR inter-area route reachability on every area change.
- Audit external route export allowlists against approved customer prefixes.
- Include OSPF interface MTU checks in transport migration validation.
Explanation
Correct Answer
D:Include OSPF interface MTU checks in transport migration validation. The current controlled acceptance rehearsal 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
A: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 controlled acceptance rehearsal. 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.
B:Test backbone adjacency and ABR inter-area route reachability on every area change. This control addresses the distinct OSPF backbone connectivity operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. 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:Audit external route export allowlists against approved customer prefixes. This control addresses the distinct OSPF export policy omission operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. 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 927
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Test control-plane and data-plane continuity separately under planned RE switchovers.
- Audit NSR state and replicate routing databases before maintenance windows.
- Track graceful-restart capabilities and maintenance test outcomes for every relevant peer.
- Monitor VRRP failover and preempt events correlated to upstream route health.
Explanation
Correct Answer
D:Monitor VRRP failover and preempt events correlated to upstream route health. The current controlled acceptance rehearsal demonstrates why this check matters: A recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. It monitors the mechanism that VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic. The continuing safeguard should be correlated with the specific acceptance test: Failback occurs only after verified upstream reachability and virtual gateway traffic remains stable across recovery.
Incorrect Answers
A:Test control-plane and data-plane continuity separately under planned RE switchovers. This control addresses the distinct GRES forwarding versus routing continuity operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. The directly relevant continuing check is: Monitor VRRP failover and preempt events correlated to upstream route health. The governing mechanism is: VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic.
B:Audit NSR state and replicate routing databases before maintenance windows. This control addresses the distinct NSR backup routing synchronization operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. The directly relevant continuing check is: Monitor VRRP failover and preempt events correlated to upstream route health. The governing mechanism is: VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic.
C:Track graceful-restart capabilities and maintenance test outcomes for every relevant peer. This control addresses the distinct Graceful restart helper expectations operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. The directly relevant continuing check is: Monitor VRRP failover and preempt events correlated to upstream route health. The governing mechanism is: VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic.
Question 928
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Validate planned VRRP priorities and failover behavior after router maintenance.
- Test control-plane and data-plane continuity separately under planned RE switchovers.
- Monitor VRRP failover and preempt events correlated to upstream route health.
- Baseline BFD timer settings by platform and monitor false-flap trends.
Explanation
Correct Answer
B:Test control-plane and data-plane continuity separately under planned RE switchovers. The current controlled acceptance rehearsal demonstrates why this check matters: A dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. It monitors the mechanism that GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions. The continuing safeguard should be correlated with the specific acceptance test: A controlled RE switchover maintains data-plane forwarding and routing neighbor continuity according to the selected supported feature set.
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 controlled acceptance rehearsal. The observed problem here is: A dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. The directly relevant continuing check is: Test control-plane and data-plane continuity separately under planned RE switchovers. The governing mechanism is: GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions.
C: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 controlled acceptance rehearsal. The observed problem here is: A dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. The directly relevant continuing check is: Test control-plane and data-plane continuity separately under planned RE switchovers. The governing mechanism is: GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions.
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 controlled acceptance rehearsal. The observed problem here is: A dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. The directly relevant continuing check is: Test control-plane and data-plane continuity separately under planned RE switchovers. The governing mechanism is: GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions.
Question 929
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Monitor unknown-unicast rate together with MAC-table learning and churn.
- Review instance-to-interface memberships during virtual switching changes.
- Alert on MAC move spikes and review customer redundancy topology before accepting dual links.
- Audit allowed VLAN sets per service and test tagged membership during changes.
Explanation
Correct Answer
C:Alert on MAC move spikes and review customer redundancy topology before accepting dual links. The current controlled acceptance rehearsal demonstrates why this check matters: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. It monitors the mechanism that Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments. The continuing safeguard should be correlated with the specific acceptance test: The MAC stabilizes on its expected port or approved redundancy construct and packet loss disappears.
Incorrect Answers
A:Monitor unknown-unicast rate together with MAC-table learning and churn. This control addresses the distinct Unknown unicast flooding behavior operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. The directly relevant continuing check is: Alert on MAC move spikes and review customer redundancy topology before accepting dual links. The governing mechanism is: Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments.
B:Review instance-to-interface memberships during virtual switching changes. This control addresses the distinct Virtual switch instance membership operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. The directly relevant continuing check is: Alert on MAC move spikes and review customer redundancy topology before accepting dual links. The governing mechanism is: Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments.
D:Audit allowed VLAN sets per service and test tagged membership during changes. This control addresses the distinct Trunk allowed VLAN omission operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. The directly relevant continuing check is: Alert on MAC move spikes and review customer redundancy topology before accepting dual links. The governing mechanism is: Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments.
Question 930
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Periodically compare intended and observed SPF cost paths after bandwidth changes.
- Rotate authenticated neighbor keys using synchronized maintenance and failure rollback checks.
- Audit external route export allowlists against approved customer prefixes.
- Reserve router IDs in an inventory and audit uniqueness during device provisioning.
Explanation
Correct Answer
D:Reserve router IDs in an inventory and audit uniqueness during device provisioning. The current controlled acceptance rehearsal demonstrates why this check matters: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. It monitors the mechanism that OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain. The continuing safeguard should be correlated with the specific acceptance test: The routers advertise distinct IDs, neighbors remain Full and the LSDB no longer shows conflicting origins.
Incorrect Answers
A:Periodically compare intended and observed SPF cost paths after bandwidth changes. This control addresses the distinct OSPF metric path preference operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. The directly relevant continuing check is: Reserve router IDs in an inventory and audit uniqueness during device provisioning. The governing mechanism is: OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain.
B: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 controlled acceptance rehearsal. The observed problem here is: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. The directly relevant continuing check is: Reserve router IDs in an inventory and audit uniqueness during device provisioning. The governing mechanism is: OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain.
C:Audit external route export allowlists against approved customer prefixes. This control addresses the distinct OSPF export policy omission operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. The directly relevant continuing check is: Reserve router IDs in an inventory and audit uniqueness during device provisioning. The governing mechanism is: OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests