Question 950
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Document encryption requirements separately from GRE connectivity requirements.
- Audit source/destination tunnel-pair symmetry during new GRE turn-ups.
- Monitor underlay reachability independently from tunnel interface administrative state.
- Include encapsulation overhead in tunnel MTU and traffic acceptance tests.
Explanation
Correct Answer
D:Include encapsulation overhead in tunnel MTU and traffic acceptance tests. The current controlled acceptance rehearsal demonstrates why this check matters: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. It monitors the mechanism that GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU. The continuing safeguard should be correlated with the specific acceptance test: Large application packets traverse the tunnel without blackholing, and measured payload size respects the underlay capacity.
Incorrect Answers
A:Document encryption requirements separately from GRE connectivity requirements. This control addresses the distinct GRE confidentiality misconception operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. The directly relevant continuing check is: Include encapsulation overhead in tunnel MTU and traffic acceptance tests. The governing mechanism is: GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU.
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 GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. The directly relevant continuing check is: Include encapsulation overhead in tunnel MTU and traffic acceptance tests. The governing mechanism is: GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU.
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 GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. The directly relevant continuing check is: Include encapsulation overhead in tunnel MTU and traffic acceptance tests. The governing mechanism is: GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU.
Question 951
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Audit peer AS numbers during carrier handoffs and AS migration work.
- Review inbound prefix filtering and max-route thresholds with every peer change.
- Check peer-specific TCP reachability and filtering during peering change control.
- Audit route-reflector cluster design and iBGP full-mesh requirements as peer counts grow.
Explanation
Correct Answer
A:Audit peer AS numbers during carrier handoffs and AS migration work. The current controlled acceptance rehearsal demonstrates why this check matters: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. It monitors the mechanism that BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session. The continuing safeguard should be correlated with the specific acceptance test: Both peers establish an expected eBGP session and the remote AS displayed in session state matches the design.
Incorrect Answers
B: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 controlled acceptance rehearsal. The observed problem here is: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. The directly relevant continuing check is: Audit peer AS numbers during carrier handoffs and AS migration work. The governing mechanism is: BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session.
C: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 controlled acceptance rehearsal. The observed problem here is: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. The directly relevant continuing check is: Audit peer AS numbers during carrier handoffs and AS migration work. The governing mechanism is: BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session.
D:Audit route-reflector cluster design and iBGP full-mesh requirements as peer counts grow. This control addresses the distinct IBGP transit split horizon operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. The directly relevant continuing check is: Audit peer AS numbers during carrier handoffs and AS migration work. The governing mechanism is: BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session.
Question 952
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A router attempts graceful routing restart but downstream peers remove its routes immediately because helper behavior is not available or the restart contract is unmet. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Validate planned VRRP priorities and failover behavior after router maintenance.
- Track graceful-restart capabilities and maintenance test outcomes for every relevant peer.
- Monitor VRRP failover and preempt events correlated to upstream route health.
- Test control-plane and data-plane continuity separately under planned RE switchovers.
Explanation
Correct Answer
B:Track graceful-restart capabilities and maintenance test outcomes for every relevant peer. The current controlled acceptance rehearsal demonstrates why this check matters: A router attempts graceful routing restart but downstream peers remove its routes immediately because helper behavior is not available or the restart contract is unmet. It monitors the mechanism that Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior. The continuing safeguard should be correlated with the specific acceptance test: Peer capability and restart-state logs show the intended graceful behavior, and routes remain valid during the controlled test.
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 router attempts graceful routing restart but downstream peers remove its routes immediately because helper behavior is not available or the restart contract is unmet. The directly relevant continuing check is: Track graceful-restart capabilities and maintenance test outcomes for every relevant peer. The governing mechanism is: Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior.
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 router attempts graceful routing restart but downstream peers remove its routes immediately because helper behavior is not available or the restart contract is unmet. The directly relevant continuing check is: Track graceful-restart capabilities and maintenance test outcomes for every relevant peer. The governing mechanism is: Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior.
D: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 router attempts graceful routing restart but downstream peers remove its routes immediately because helper behavior is not available or the restart contract is unmet. The directly relevant continuing check is: Track graceful-restart capabilities and maintenance test outcomes for every relevant peer. The governing mechanism is: Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior.
Question 953
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- 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.
- Validate actual SR paths and segment lists after core metric or policy changes.
- Rehearse RSVP protection paths during maintenance and monitor bypass readiness.
Explanation
Correct Answer
C:Validate actual SR paths and segment lists after core metric or policy changes. The current controlled acceptance rehearsal demonstrates why this check matters: An SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. It monitors the mechanism that A node SID typically steers toward its destination using shortest-path IGP forwarding, while explicit adjacency segments can add finer path constraints. The continuing safeguard should be correlated with the specific acceptance test: The observed label stack and forwarding path match the documented shortest path or the specified explicit segment list.
Incorrect Answers
A: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 SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. The directly relevant continuing check is: Validate actual SR paths and segment lists after core metric or policy changes. The governing mechanism is: A node SID typically steers toward its destination using shortest-path IGP forwarding, while explicit adjacency segments can add finer path constraints.
B: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 SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. The directly relevant continuing check is: Validate actual SR paths and segment lists after core metric or policy changes. The governing mechanism is: A node SID typically steers toward its destination using shortest-path IGP forwarding, while explicit adjacency segments can add finer path constraints.
D:Rehearse RSVP protection paths during maintenance and monitor bypass readiness. This control addresses the distinct RSVP link protection plan operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: An SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. The directly relevant continuing check is: Validate actual SR paths and segment lists after core metric or policy changes. The governing mechanism is: A node SID typically steers toward its destination using shortest-path IGP forwarding, while explicit adjacency segments can add finer path constraints.
Question 954
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Reconcile customer port VLAN membership against service orders after provisioning.
- Maintain unique outer service identifiers for separate tenants and test cross-tenant isolation.
- Verify logical-unit VLAN IDs and encapsulation during each additional service turn-up.
- Include native VLAN agreement and negative isolation tests in trunk turn-up procedures.
Explanation
Correct Answer
D:Include native VLAN agreement and negative isolation tests in trunk turn-up procedures. The current controlled acceptance rehearsal demonstrates why this check matters: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. It monitors the mechanism that Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping. The continuing safeguard should be correlated with the specific acceptance test: A controlled untagged frame maps to the same intended VLAN on both ends and no unauthorized L2 reachability remains.
Incorrect Answers
A:Reconcile customer port VLAN membership against service orders after provisioning. This control addresses the distinct Access VLAN membership operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. The directly relevant continuing check is: Include native VLAN agreement and negative isolation tests in trunk turn-up procedures. The governing mechanism is: Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping.
B: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: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. The directly relevant continuing check is: Include native VLAN agreement and negative isolation tests in trunk turn-up procedures. The governing mechanism is: Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping.
C:Verify logical-unit VLAN IDs and encapsulation during each additional service turn-up. This control addresses the distinct Flexible VLAN tagging logical units operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. The directly relevant continuing check is: Include native VLAN agreement and negative isolation tests in trunk turn-up procedures. The governing mechanism is: Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping.
Question 955
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two PE routers exchange OSPF Hello packets on the same Ethernet segment but stay Down because one interface belongs to area 0 and the other to area 10. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Audit external route export allowlists against approved customer prefixes.
- Audit paired OSPF interface area assignments with neighbor-state monitoring.
- Review passive-interface policy whenever a customer-facing segment is added.
- Periodically compare intended and observed SPF cost paths after bandwidth changes.
Explanation
Correct Answer
B:Audit paired OSPF interface area assignments with neighbor-state monitoring. The current controlled acceptance rehearsal demonstrates why this check matters: Two PE routers exchange OSPF Hello packets on the same Ethernet segment but stay Down because one interface belongs to area 0 and the other to area 10. It monitors the mechanism that OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship. The continuing safeguard should be correlated with the specific acceptance test: Both peers reach Full adjacency in the same area and the intended routes are learned.
Incorrect Answers
A: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 PE routers exchange OSPF Hello packets on the same Ethernet segment but stay Down because one interface belongs to area 0 and the other to area 10. The directly relevant continuing check is: Audit paired OSPF interface area assignments with neighbor-state monitoring. The governing mechanism is: OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship.
C:Review passive-interface policy whenever a customer-facing segment is added. This control addresses the distinct OSPF passive interface operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: Two PE routers exchange OSPF Hello packets on the same Ethernet segment but stay Down because one interface belongs to area 0 and the other to area 10. The directly relevant continuing check is: Audit paired OSPF interface area assignments with neighbor-state monitoring. The governing mechanism is: OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship.
D: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: Two PE routers exchange OSPF Hello packets on the same Ethernet segment but stay Down because one interface belongs to area 0 and the other to area 10. The directly relevant continuing check is: Audit paired OSPF interface area assignments with neighbor-state monitoring. The governing mechanism is: OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship.
Question 956
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Validate both tag layers at each wholesale handoff and monitor service-tag drift.
- Review instance-to-interface memberships during virtual switching changes.
- Audit allowed VLAN sets per service and test tagged membership during changes.
- Include native VLAN agreement and negative isolation tests in trunk turn-up procedures.
Explanation
Correct Answer
A:Validate both tag layers at each wholesale handoff and monitor service-tag drift. The current controlled acceptance rehearsal demonstrates why this check matters: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. It monitors the mechanism that Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags. The continuing safeguard should be correlated with the specific acceptance test: Captured handoff frames carry the agreed outer tag and correct inner VLAN values and pass only the authorized service.
Incorrect Answers
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 wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. The directly relevant continuing check is: Validate both tag layers at each wholesale handoff and monitor service-tag drift. The governing mechanism is: Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags.
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 wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. The directly relevant continuing check is: Validate both tag layers at each wholesale handoff and monitor service-tag drift. The governing mechanism is: Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags.
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 wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. The directly relevant continuing check is: Validate both tag layers at each wholesale handoff and monitor service-tag drift. The governing mechanism is: Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags.
Question 957
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An LDP session is operational, but a destination FEC lacks the usable outgoing label that an ingress PE expects to use. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Rehearse RSVP protection paths during maintenance and monitor bypass readiness.
- Sample FEC label bindings and forwarding resolution after prefix or IGP changes.
- Validate actual SR paths and segment lists after core metric or policy changes.
- Verify label disposition and QoS handling at MPLS egress boundaries after policy changes.
Explanation
Correct Answer
B:Sample FEC label bindings and forwarding resolution after prefix or IGP changes. The current controlled acceptance rehearsal demonstrates why this check matters: An LDP session is operational, but a destination FEC lacks the usable outgoing label that an ingress PE expects to use. It monitors the mechanism that LDP maps forwarding equivalence classes to labels learned from the downstream next hop; a session can be up without an applicable mapping for every FEC. The continuing safeguard should be correlated with the specific acceptance test: The relevant FEC has a reachable next hop and valid incoming and outgoing label entries along the intended LSP.
Incorrect Answers
A:Rehearse RSVP protection paths during maintenance and monitor bypass readiness. This control addresses the distinct RSVP link protection plan operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: An LDP session is operational, but a destination FEC lacks the usable outgoing label that an ingress PE expects to use. The directly relevant continuing check is: Sample FEC label bindings and forwarding resolution after prefix or IGP changes. The governing mechanism is: LDP maps forwarding equivalence classes to labels learned from the downstream next hop; a session can be up without an applicable mapping for every FEC.
C:Validate actual SR paths and segment lists after core metric or policy changes. This control addresses the distinct SR-MPLS node-SID shortest path operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: An LDP session is operational, but a destination FEC lacks the usable outgoing label that an ingress PE expects to use. The directly relevant continuing check is: Sample FEC label bindings and forwarding resolution after prefix or IGP changes. The governing mechanism is: LDP maps forwarding equivalence classes to labels learned from the downstream next hop; a session can be up without an applicable mapping for every FEC.
D:Verify label disposition and QoS handling at MPLS egress boundaries after policy changes. This control addresses the distinct Explicit-null forwarding operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: An LDP session is operational, but a destination FEC lacks the usable outgoing label that an ingress PE expects to use. The directly relevant continuing check is: Sample FEC label bindings and forwarding resolution after prefix or IGP changes. The governing mechanism is: LDP maps forwarding equivalence classes to labels learned from the downstream next hop; a session can be up without an applicable mapping for every FEC.
Question 958
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. 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.
- Include OSPF interface MTU checks in transport migration validation.
- Audit external route export allowlists against approved customer prefixes.
- Baseline OSPF timer settings per transport class and alert on configuration drift.
Explanation
Correct Answer
D:Baseline OSPF timer settings per transport class and alert on configuration drift. The current controlled acceptance rehearsal demonstrates why this check matters: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. It monitors the mechanism that OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance. The continuing safeguard should be correlated with the specific acceptance test: The two interfaces report matching timers and the neighbor stays Full beyond several dead intervals.
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: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. The directly relevant continuing check is: Baseline OSPF timer settings per transport class and alert on configuration drift. The governing mechanism is: OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance.
B:Include OSPF interface MTU checks in transport migration validation. This control addresses the distinct OSPF MTU ExStart stall operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. The directly relevant continuing check is: Baseline OSPF timer settings per transport class and alert on configuration drift. The governing mechanism is: OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance.
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: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. The directly relevant continuing check is: Baseline OSPF timer settings per transport class and alert on configuration drift. The governing mechanism is: OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance.
Question 959
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A newly connected CE sends traffic to a destination MAC not yet learned in its VLAN, and operators mistake the initial flooding for a routing loop. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- 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.
- Verify logical-unit VLAN IDs and encapsulation during each additional service turn-up.
Explanation
Correct Answer
C:Monitor unknown-unicast rate together with MAC-table learning and churn. The current controlled acceptance rehearsal demonstrates why this check matters: A newly connected CE sends traffic to a destination MAC not yet learned in its VLAN, and operators mistake the initial flooding for a routing loop. It monitors the mechanism that A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic. The continuing safeguard should be correlated with the specific acceptance test: Initial flooding is VLAN-scoped, then subsequent frames to the learned MAC use the correct specific egress port.
Incorrect Answers
A: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: A newly connected CE sends traffic to a destination MAC not yet learned in its VLAN, and operators mistake the initial flooding for a routing loop. The directly relevant continuing check is: Monitor unknown-unicast rate together with MAC-table learning and churn. The governing mechanism is: A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic.
B: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: A newly connected CE sends traffic to a destination MAC not yet learned in its VLAN, and operators mistake the initial flooding for a routing loop. The directly relevant continuing check is: Monitor unknown-unicast rate together with MAC-table learning and churn. The governing mechanism is: A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic.
D:Verify logical-unit VLAN IDs and encapsulation during each additional service turn-up. This control addresses the distinct Flexible VLAN tagging logical units operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A newly connected CE sends traffic to a destination MAC not yet learned in its VLAN, and operators mistake the initial flooding for a routing loop. The directly relevant continuing check is: Monitor unknown-unicast rate together with MAC-table learning and churn. The governing mechanism is: A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic.
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.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests