Question 960
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A provider-facing Ethernet port must carry multiple distinct tagged logical units, but one unit uses the wrong VLAN encapsulation and traffic enters the wrong service. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Verify logical-unit VLAN IDs and encapsulation during each additional service turn-up.
- Monitor unknown-unicast rate together with MAC-table learning and churn.
- Alert on MAC move spikes and review customer redundancy topology before accepting dual links.
- Include native VLAN agreement and negative isolation tests in trunk turn-up procedures.
Explanation
Correct Answer
A:Verify logical-unit VLAN IDs and encapsulation during each additional service turn-up. The current controlled acceptance rehearsal demonstrates why this check matters: A provider-facing Ethernet port must carry multiple distinct tagged logical units, but one unit uses the wrong VLAN encapsulation and traffic enters the wrong service. It monitors the mechanism that Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit. The continuing safeguard should be correlated with the specific acceptance test: Per-unit counters and a packet capture demonstrate each authorized VLAN tag reaches its mapped logical interface.
Incorrect Answers
B: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 provider-facing Ethernet port must carry multiple distinct tagged logical units, but one unit uses the wrong VLAN encapsulation and traffic enters the wrong service. The directly relevant continuing check is: Verify logical-unit VLAN IDs and encapsulation during each additional service turn-up. The governing mechanism is: Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit.
C:Alert on MAC move spikes and review customer redundancy topology before accepting dual links. This control addresses the distinct MAC move instability operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A provider-facing Ethernet port must carry multiple distinct tagged logical units, but one unit uses the wrong VLAN encapsulation and traffic enters the wrong service. The directly relevant continuing check is: Verify logical-unit VLAN IDs and encapsulation during each additional service turn-up. The governing mechanism is: Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit.
D:Include native VLAN agreement and negative isolation tests in trunk turn-up procedures. This control addresses the distinct Native VLAN mismatch operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A provider-facing Ethernet port must carry multiple distinct tagged logical units, but one unit uses the wrong VLAN encapsulation and traffic enters the wrong service. The directly relevant continuing check is: Verify logical-unit VLAN IDs and encapsulation during each additional service turn-up. The governing mechanism is: Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit.
Question 961
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Baseline metric-style compatibility before area-wide IS-IS cost adjustments.
- Include interface family iso in standardized IS-IS provisioning templates.
- Maintain a registry of ISO NET system IDs across every area and lab clone.
- Record DIS priorities and pseudonode behavior in service-provider switching design reviews.
Explanation
Correct Answer
A:Baseline metric-style compatibility before area-wide IS-IS cost adjustments. The current controlled acceptance rehearsal demonstrates why this check matters: A designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. It monitors the mechanism that IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering. The continuing safeguard should be correlated with the specific acceptance test: The LSDB advertises compatible wide metrics and SPF selects the intended path across the upgraded links.
Incorrect Answers
B: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 controlled acceptance rehearsal. The observed problem here is: A designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. The directly relevant continuing check is: Baseline metric-style compatibility before area-wide IS-IS cost adjustments. The governing mechanism is: IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering.
C: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 designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. The directly relevant continuing check is: Baseline metric-style compatibility before area-wide IS-IS cost adjustments. The governing mechanism is: IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering.
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 controlled acceptance rehearsal. The observed problem here is: A designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. The directly relevant continuing check is: Baseline metric-style compatibility before area-wide IS-IS cost adjustments. The governing mechanism is: IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering.
Question 962
During a controlled acceptance rehearsal of the same defect on a separate test network, 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?
- Continuously validate configured RSVP explicit paths against network topology inventory.
- Document expected label stacks at ingress, transit and penultimate hop for key services.
- Track reserved and unreserved bandwidth on TE links before new LSP provisioning.
- Check LDP session transport filtering as part of control-plane ACL reviews.
Explanation
Correct Answer
A:Continuously validate configured RSVP explicit paths against network topology inventory. The current controlled acceptance rehearsal 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
B: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 controlled acceptance rehearsal. 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:Track reserved and unreserved bandwidth on TE links before new LSP provisioning. This control addresses the distinct RSVP reservable bandwidth shortage operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. 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.
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 controlled acceptance rehearsal. 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 963
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Record DIS priorities and pseudonode behavior in service-provider switching design reviews.
- Audit IS-IS route advertisements against customer import and export inventories.
- Stage IS-IS key rotations with overlap and rollback checks wherever supported.
- Use controlled startup overload and readiness criteria after routing-engine restarts.
Explanation
Correct Answer
C:Stage IS-IS key rotations with overlap and rollback checks wherever supported. The current controlled acceptance rehearsal demonstrates why this check matters: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. It monitors the mechanism that When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted. The continuing safeguard should be correlated with the specific acceptance test: Neighbor exchanges succeed without authentication errors and their corresponding LSDB contents are current.
Incorrect Answers
A: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 controlled acceptance rehearsal. The observed problem here is: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. The directly relevant continuing check is: Stage IS-IS key rotations with overlap and rollback checks wherever supported. The governing mechanism is: When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted.
B:Audit IS-IS route advertisements against customer import and export inventories. This control addresses the distinct IS-IS route export scope operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. The directly relevant continuing check is: Stage IS-IS key rotations with overlap and rollback checks wherever supported. The governing mechanism is: When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted.
D:Use controlled startup overload and readiness criteria after routing-engine restarts. This control addresses the distinct IS-IS overload-state recovery operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. The directly relevant continuing check is: Stage IS-IS key rotations with overlap and rollback checks wherever supported. The governing mechanism is: When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted.
Question 964
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Track ECMP next-hop count and routing-cost drift after transport changes.
- Review import/export scope and route-copy audits when new routing instances are introduced.
- Review first-match precedence with representative negative and positive traffic tests.
- Exercise backup-path liveness detection under downstream and local failure scenarios.
Explanation
Correct Answer
A:Track ECMP next-hop count and routing-cost drift after transport changes. The current controlled acceptance rehearsal demonstrates why this check matters: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. It monitors the mechanism that ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds. The continuing safeguard should be correlated with the specific acceptance test: The forwarding table shows both expected next hops and representative flows use the authorized paths without loop or asymmetry problems.
Incorrect Answers
B:Review import/export scope and route-copy audits when new routing instances are introduced. This control addresses the distinct RIB group forwarding copy operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. The directly relevant continuing check is: Track ECMP next-hop count and routing-cost drift after transport changes. The governing mechanism is: ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds.
C: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: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. The directly relevant continuing check is: Track ECMP next-hop count and routing-cost drift after transport changes. The governing mechanism is: ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds.
D: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: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. The directly relevant continuing check is: Track ECMP next-hop count and routing-cost drift after transport changes. The governing mechanism is: ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds.
Question 965
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A provider virtual-switch routing instance is configured but one interface remains attached to the default switching context, so tenant MAC learning is fragmented. 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.
- 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.
- Review instance-to-interface memberships during virtual switching changes.
Explanation
Correct Answer
D:Review instance-to-interface memberships during virtual switching changes. The current controlled acceptance rehearsal demonstrates why this check matters: A provider virtual-switch routing instance is configured but one interface remains attached to the default switching context, so tenant MAC learning is fragmented. It monitors the mechanism that Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned. The continuing safeguard should be correlated with the specific acceptance test: The customer MAC and VLAN appear in the correct virtual-switch instance with no leakage into default bridging context.
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 provider virtual-switch routing instance is configured but one interface remains attached to the default switching context, so tenant MAC learning is fragmented. The directly relevant continuing check is: Review instance-to-interface memberships during virtual switching changes. The governing mechanism is: Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned.
B:Alert on MAC move spikes and review customer redundancy topology before accepting dual links. This control addresses the distinct MAC move instability operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A provider virtual-switch routing instance is configured but one interface remains attached to the default switching context, so tenant MAC learning is fragmented. The directly relevant continuing check is: Review instance-to-interface memberships during virtual switching changes. The governing mechanism is: Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned.
C: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 provider virtual-switch routing instance is configured but one interface remains attached to the default switching context, so tenant MAC learning is fragmented. The directly relevant continuing check is: Review instance-to-interface memberships during virtual switching changes. The governing mechanism is: Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned.
Question 966
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Record DIS priorities and pseudonode behavior in service-provider switching design reviews.
- Alert on unusual LSP aging patterns and repeated adjacency churn.
- Maintain a registry of ISO NET system IDs across every area and lab clone.
- Review link-level capability profiles for L1, L2 and L1/L2 routers.
Explanation
Correct Answer
D:Review link-level capability profiles for L1, L2 and L1/L2 routers. The current controlled acceptance rehearsal demonstrates why this check matters: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. It monitors the mechanism that An IS-IS adjacency needs compatible protocol levels as well as link reachability. The continuing safeguard should be correlated with the specific acceptance test: A shared Level 1 or Level 2 adjacency comes up and the right set of level-specific routes is exchanged.
Incorrect Answers
A: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 controlled acceptance rehearsal. The observed problem here is: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. The directly relevant continuing check is: Review link-level capability profiles for L1, L2 and L1/L2 routers. The governing mechanism is: An IS-IS adjacency needs compatible protocol levels as well as link reachability.
B:Alert on unusual LSP aging patterns and repeated adjacency churn. This control addresses the distinct IS-IS LSP lifetime anomaly operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. The directly relevant continuing check is: Review link-level capability profiles for L1, L2 and L1/L2 routers. The governing mechanism is: An IS-IS adjacency needs compatible protocol levels as well as link reachability.
C: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: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. The directly relevant continuing check is: Review link-level capability profiles for L1, L2 and L1/L2 routers. The governing mechanism is: An IS-IS adjacency needs compatible protocol levels as well as link reachability.
Question 967
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. 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.
- Periodically compare intended and observed SPF cost paths after bandwidth changes.
- Rotate authenticated neighbor keys using synchronized maintenance and failure rollback checks.
- Document broadcast-segment DR priorities and rehearse controlled elections.
Explanation
Correct Answer
D:Document broadcast-segment DR priorities and rehearse controlled elections. The current controlled acceptance rehearsal demonstrates why this check matters: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. It monitors the mechanism that OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links. The continuing safeguard should be correlated with the specific acceptance test: An appropriate eligible router becomes DR or BDR after a controlled election and neighbor adjacency remains stable.
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 controlled acceptance rehearsal. The observed problem here is: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. The directly relevant continuing check is: Document broadcast-segment DR priorities and rehearse controlled elections. The governing mechanism is: OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links.
B: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: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. The directly relevant continuing check is: Document broadcast-segment DR priorities and rehearse controlled elections. The governing mechanism is: OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links.
C: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: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. The directly relevant continuing check is: Document broadcast-segment DR priorities and rehearse controlled elections. The governing mechanism is: OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links.
Question 968
During a controlled acceptance rehearsal of the same defect on a separate test network, 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?
- Inspect both protocol levels' IPv6 TLV propagation during dual-stack deployments.
- Monitor OSPFv2 and OSPFv3 neighbor health independently on dual-stack links.
- Check BGP families, IPv6 route filters and next-hop resolution on each dual-stack peer.
- Check IPv6 static routes for proper next-hop scope after link renumbering.
Explanation
Correct Answer
B:Monitor OSPFv2 and OSPFv3 neighbor health independently on dual-stack links. The current controlled acceptance rehearsal 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: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 controlled acceptance rehearsal. 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:Check BGP families, IPv6 route filters and next-hop resolution on each dual-stack peer. This control addresses the distinct IPv6 BGP NLRI family omitted operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. 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:Check IPv6 static routes for proper next-hop scope after link renumbering. This control addresses the distinct IPv6 static link-local next hop operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. 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 969
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A provider calls a GRE tunnel secure against eavesdropping merely because customers cannot see its inner packet headers on the underlay. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Include encapsulation overhead in tunnel MTU and traffic acceptance tests.
- Audit source/destination tunnel-pair symmetry during new GRE turn-ups.
- Monitor underlay reachability independently from tunnel interface administrative state.
- Document encryption requirements separately from GRE connectivity requirements.
Explanation
Correct Answer
D:Document encryption requirements separately from GRE connectivity requirements. The current controlled acceptance rehearsal demonstrates why this check matters: A provider calls a GRE tunnel secure against eavesdropping merely because customers cannot see its inner packet headers on the underlay. It monitors the mechanism that GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls. The continuing safeguard should be correlated with the specific acceptance test: A validated encryption layer protects inner payload on the monitored underlay while GRE routing still functions as designed.
Incorrect Answers
A:Include encapsulation overhead in tunnel MTU and traffic acceptance tests. This control addresses the distinct GRE encapsulation MTU overhead operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A provider calls a GRE tunnel secure against eavesdropping merely because customers cannot see its inner packet headers on the underlay. The directly relevant continuing check is: Document encryption requirements separately from GRE connectivity requirements. The governing mechanism is: GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls.
B:Audit source/destination tunnel-pair symmetry during new GRE turn-ups. This control addresses the distinct GRE tunnel endpoint mismatch operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A provider calls a GRE tunnel secure against eavesdropping merely because customers cannot see its inner packet headers on the underlay. The directly relevant continuing check is: Document encryption requirements separately from GRE connectivity requirements. The governing mechanism is: GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls.
C:Monitor underlay reachability independently from tunnel interface administrative state. This control addresses the distinct GRE underlay recursive loss operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A provider calls a GRE tunnel secure against eavesdropping merely because customers cannot see its inner packet headers on the underlay. The directly relevant continuing check is: Document encryption requirements separately from GRE connectivity requirements. The governing mechanism is: GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls.
Question 970
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. 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.
- Audit external route export allowlists against approved customer prefixes.
- Periodically compare intended and observed SPF cost paths after bandwidth changes.
- Alert on repeated OSPF adjacency resets and divergent LSA conditions.
Explanation
Correct Answer
B:Audit external route export allowlists against approved customer prefixes. The current controlled acceptance rehearsal demonstrates why this check matters: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. It monitors the mechanism that External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements. The continuing safeguard should be correlated with the specific acceptance test: The specifically allowed customer prefix appears as the expected external route on the peer, while other connected networks stay unadvertised.
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 controlled acceptance rehearsal. The observed problem here is: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. The directly relevant continuing check is: Audit external route export allowlists against approved customer prefixes. The governing mechanism is: External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements.
C: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: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. The directly relevant continuing check is: Audit external route export allowlists against approved customer prefixes. The governing mechanism is: External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements.
D: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 controlled acceptance rehearsal. The observed problem here is: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. The directly relevant continuing check is: Audit external route export allowlists against approved customer prefixes. The governing mechanism is: External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests