Question 260
During production incident triage, engineers observe: PE-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- A controlled packet to an active more-specific prefix forwards, while a packet to an uncovered address receives the intended reject or silent-discard behavior.
- The forwarding table shows both expected next hops and representative flows use the authorized paths without loop or asymmetry problems.
- The prefix is absent from permitted active forwarding while legitimate nearby routes remain reachable and logged rejection evidence matches policy.
- Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded.
Explanation
Correct Answer
C:The prefix is absent from permitted active forwarding while legitimate nearby routes remain reachable and logged rejection evidence matches policy. This tests the actual condition identified in the live production incident: PE-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. It is meaningful because Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context.
Incorrect Answers
A:A controlled packet to an active more-specific prefix forwards, while a packet to an uncovered address receives the intended reject or silent-discard behavior. This measurement may prove the unrelated Aggregate rejection behavior condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: PE-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. A relevant acceptance result here is: The prefix is absent from permitted active forwarding while legitimate nearby routes remain reachable and logged rejection evidence matches policy.
B:The forwarding table shows both expected next hops and representative flows use the authorized paths without loop or asymmetry problems. This measurement may prove the unrelated Equal-cost multipath eligibility condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: PE-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. A relevant acceptance result here is: The prefix is absent from permitted active forwarding while legitimate nearby routes remain reachable and logged rejection evidence matches policy.
D:Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded. This measurement may prove the unrelated Per-flow hash expectation condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: PE-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. A relevant acceptance result here is: The prefix is absent from permitted active forwarding while legitimate nearby routes remain reachable and logged rejection evidence matches policy.
Question 261
During production incident triage, engineers observe: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The static prefix becomes active with a resolved next hop, and a sourced packet test reaches the destination through the intended interface.
- The selected active prefix shows the intended protocol, route preference, and forwarding next hop both before and after a controlled failover.
- The generated default becomes active with the expected next hop only when the qualifying contributor exists.
- A controlled packet to an active more-specific prefix forwards, while a packet to an uncovered address receives the intended reject or silent-discard behavior.
Explanation
Correct Answer
D:A controlled packet to an active more-specific prefix forwards, while a packet to an uncovered address receives the intended reject or silent-discard behavior. This tests the actual condition identified in the live production incident: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. It is meaningful because An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match.
Incorrect Answers
A:The static prefix becomes active with a resolved next hop, and a sourced packet test reaches the destination through the intended interface. This measurement may prove the unrelated Recursive next-hop resolution condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. A relevant acceptance result here is: A controlled packet to an active more-specific prefix forwards, while a packet to an uncovered address receives the intended reject or silent-discard behavior.
B:The selected active prefix shows the intended protocol, route preference, and forwarding next hop both before and after a controlled failover. This measurement may prove the unrelated Administrative preference overrides static condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. A relevant acceptance result here is: A controlled packet to an active more-specific prefix forwards, while a packet to an uncovered address receives the intended reject or silent-discard behavior.
C:The generated default becomes active with the expected next hop only when the qualifying contributor exists. This measurement may prove the unrelated Generated default route prerequisite condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. A relevant acceptance result here is: A controlled packet to an active more-specific prefix forwards, while a packet to an uncovered address receives the intended reject or silent-discard behavior.
Question 262
During production incident triage, engineers observe: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The bypass LSP is operational before fault injection and protected traffic follows the bypass after the link is disabled.
- The core interface is MPLS enabled and labeled forwarding entries exist for the expected transport destination.
- The relevant FEC has a reachable next hop and valid incoming and outgoing label entries along the intended LSP.
- The egress receives the expected payload context and end-to-end service passes despite the absence of a top transport label.
Explanation
Correct Answer
A:The bypass LSP is operational before fault injection and protected traffic follows the bypass after the link is disabled. This tests the actual condition identified in the live production incident: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. It is meaningful because RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost.
Incorrect Answers
B:The core interface is MPLS enabled and labeled forwarding entries exist for the expected transport destination. This measurement may prove the unrelated MPLS interface not enabled condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. A relevant acceptance result here is: The bypass LSP is operational before fault injection and protected traffic follows the bypass after the link is disabled.
C:The relevant FEC has a reachable next hop and valid incoming and outgoing label entries along the intended LSP. This measurement may prove the unrelated Missing LDP FEC label mapping condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. A relevant acceptance result here is: The bypass LSP is operational before fault injection and protected traffic follows the bypass after the link is disabled.
D:The egress receives the expected payload context and end-to-end service passes despite the absence of a top transport label. This measurement may prove the unrelated Penultimate hop popping condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. A relevant acceptance result here is: The bypass LSP is operational before fault injection and protected traffic follows the bypass after the link is disabled.
Question 263
During production incident triage, engineers observe: An IPv6 routing interface has global unicast addresses and a healthy OSPFv2 adjacency, yet OSPFv3 neighbor state is absent and no IPv6 routes are learned. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The OSPFv3 neighbor reaches the expected state and learned IPv6 prefixes appear in inet6.0.
- An IPv6 trace crosses the intended tunnel, while outer IPv4 packets reach the peer endpoints and encapsulation counters increment.
- Large IPv6 application transfers succeed and Packet Too Big messages reach the source when necessary.
- The relevant IPv6 reachability TLVs are present and remote IPv6 prefixes become active in inet6.0.
Explanation
Correct Answer
A:The OSPFv3 neighbor reaches the expected state and learned IPv6 prefixes appear in inet6.0. This tests the actual condition identified in the live production incident: 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 is meaningful because OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2.
Incorrect Answers
B:An IPv6 trace crosses the intended tunnel, while outer IPv4 packets reach the peer endpoints and encapsulation counters increment. This measurement may prove the unrelated IPv6 over IPv4 transit tunnel condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: 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. A relevant acceptance result here is: The OSPFv3 neighbor reaches the expected state and learned IPv6 prefixes appear in inet6.0.
C:Large IPv6 application transfers succeed and Packet Too Big messages reach the source when necessary. This measurement may prove the unrelated ICMPv6 packet-too-big handling condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: 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. A relevant acceptance result here is: The OSPFv3 neighbor reaches the expected state and learned IPv6 prefixes appear in inet6.0.
D:The relevant IPv6 reachability TLVs are present and remote IPv6 prefixes become active in inet6.0. This measurement may prove the unrelated IS-IS IPv6 reachability TLVs condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: 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. A relevant acceptance result here is: The OSPFv3 neighbor reaches the expected state and learned IPv6 prefixes appear in inet6.0.
Question 264
During production incident triage, engineers observe: A BGP feed contains private or customer-specific prefixes that should be rejected but are installed because the receiving policy accepts too broadly. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- Both peers establish an expected eBGP session and the remote AS displayed in session state matches the design.
- A TCP session is established to the correct neighbor address, BGP reaches Established and intended routes are exchanged.
- The session establishes using the intended loopback source and destination and stays up after a physical link fails.
- The rejected prefix does not appear as an eligible route while approved advertised prefixes remain available.
Explanation
Correct Answer
D:The rejected prefix does not appear as an eligible route while approved advertised prefixes remain available. This tests the actual condition identified in the live production incident: A BGP feed contains private or customer-specific prefixes that should be rejected but are installed because the receiving policy accepts too broadly. It is meaningful because BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice.
Incorrect Answers
A:Both peers establish an expected eBGP session and the remote AS displayed in session state matches the design. This measurement may prove the unrelated BGP peer autonomous system mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A BGP feed contains private or customer-specific prefixes that should be rejected but are installed because the receiving policy accepts too broadly. A relevant acceptance result here is: The rejected prefix does not appear as an eligible route while approved advertised prefixes remain available.
B:A TCP session is established to the correct neighbor address, BGP reaches Established and intended routes are exchanged. This measurement may prove the unrelated BGP TCP transport blocked condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A BGP feed contains private or customer-specific prefixes that should be rejected but are installed because the receiving policy accepts too broadly. A relevant acceptance result here is: The rejected prefix does not appear as an eligible route while approved advertised prefixes remain available.
C:The session establishes using the intended loopback source and destination and stays up after a physical link fails. This measurement may prove the unrelated IBGP loopback source resolution condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A BGP feed contains private or customer-specific prefixes that should be rejected but are installed because the receiving policy accepts too broadly. A relevant acceptance result here is: The rejected prefix does not appear as an eligible route while approved advertised prefixes remain available.
Question 265
During production incident triage, engineers observe: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- IS-IS Hello exchanges appear and the expected level adjacency establishes while IPv4 traffic still functions.
- The LSDB advertises compatible wide metrics and SPF selects the intended path across the upgraded links.
- The two devices show an up adjacency at the intended level and their Level 1 link-state databases exchange reachability.
- The designated system matches the planned candidate, pseudonode LSPs are coherent, and LAN adjacencies remain stable.
Explanation
Correct Answer
C:The two devices show an up adjacency at the intended level and their Level 1 link-state databases exchange reachability. This tests the actual condition identified in the live production incident: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. It is meaningful because IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas.
Incorrect Answers
A:IS-IS Hello exchanges appear and the expected level adjacency establishes while IPv4 traffic still functions. This measurement may prove the unrelated IS-IS ISO family missing condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. A relevant acceptance result here is: The two devices show an up adjacency at the intended level and their Level 1 link-state databases exchange reachability.
B:The LSDB advertises compatible wide metrics and SPF selects the intended path across the upgraded links. This measurement may prove the unrelated IS-IS narrow metric ceiling condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. A relevant acceptance result here is: The two devices show an up adjacency at the intended level and their Level 1 link-state databases exchange reachability.
D:The designated system matches the planned candidate, pseudonode LSPs are coherent, and LAN adjacencies remain stable. This measurement may prove the unrelated IS-IS DIS election surprise condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. A relevant acceptance result here is: The two devices show an up adjacency at the intended level and their Level 1 link-state databases exchange reachability.
Question 266
During production incident triage, engineers observe: An ingress router has routes to the LSP egress but its core-facing interface is not participating in MPLS, so label forwarding is absent. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- An LDP session reaches Operational and displays the intended neighbor label bindings after selective filter correction.
- The core interface is MPLS enabled and labeled forwarding entries exist for the expected transport destination.
- The RSVP LSP becomes operational on the authorized explicit route and reports a complete signaled path.
- The LSP reserves its intended bandwidth end to end without exceeding the engineered link limits.
Explanation
Correct Answer
B:The core interface is MPLS enabled and labeled forwarding entries exist for the expected transport destination. This tests the actual condition identified in the live production incident: An ingress router has routes to the LSP egress but its core-facing interface is not participating in MPLS, so label forwarding is absent. It is meaningful because MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path.
Incorrect Answers
A:An LDP session reaches Operational and displays the intended neighbor label bindings after selective filter correction. This measurement may prove the unrelated LDP TCP 646 establishment condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An ingress router has routes to the LSP egress but its core-facing interface is not participating in MPLS, so label forwarding is absent. A relevant acceptance result here is: The core interface is MPLS enabled and labeled forwarding entries exist for the expected transport destination.
C:The RSVP LSP becomes operational on the authorized explicit route and reports a complete signaled path. This measurement may prove the unrelated RSVP-TE constrained path missing condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An ingress router has routes to the LSP egress but its core-facing interface is not participating in MPLS, so label forwarding is absent. A relevant acceptance result here is: The core interface is MPLS enabled and labeled forwarding entries exist for the expected transport destination.
D:The LSP reserves its intended bandwidth end to end without exceeding the engineered link limits. This measurement may prove the unrelated RSVP reservable bandwidth shortage condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An ingress router has routes to the LSP egress but its core-facing interface is not participating in MPLS, so label forwarding is absent. A relevant acceptance result here is: The core interface is MPLS enabled and labeled forwarding entries exist for the expected transport destination.
Question 267
During production incident triage, engineers observe: A static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The aggregate appears as an active route with contributing prefixes shown, and the permitted summary is advertised to the intended peer.
- The generated default becomes active with the expected next hop only when the qualifying contributor exists.
- A controlled packet to an active more-specific prefix forwards, while a packet to an uncovered address receives the intended reject or silent-discard behavior.
- With the downstream fault injected, the unsuitable backup route is withdrawn or de-preferred and valid traffic moves to the tested alternate.
Explanation
Correct Answer
D:With the downstream fault injected, the unsuitable backup route is withdrawn or de-preferred and valid traffic moves to the tested alternate. This tests the actual condition identified in the live production incident: A static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. It is meaningful because A static next hop may appear link-reachable while the remote end-to-end path is unusable, so a tracking mechanism such as BFD can be necessary.
Incorrect Answers
A:The aggregate appears as an active route with contributing prefixes shown, and the permitted summary is advertised to the intended peer. This measurement may prove the unrelated Aggregate route contribution condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. A relevant acceptance result here is: With the downstream fault injected, the unsuitable backup route is withdrawn or de-preferred and valid traffic moves to the tested alternate.
B:The generated default becomes active with the expected next hop only when the qualifying contributor exists. This measurement may prove the unrelated Generated default route prerequisite condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. A relevant acceptance result here is: With the downstream fault injected, the unsuitable backup route is withdrawn or de-preferred and valid traffic moves to the tested alternate.
C:A controlled packet to an active more-specific prefix forwards, while a packet to an uncovered address receives the intended reject or silent-discard behavior. This measurement may prove the unrelated Aggregate rejection behavior condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. A relevant acceptance result here is: With the downstream fault injected, the unsuitable backup route is withdrawn or de-preferred and valid traffic moves to the tested alternate.
Question 268
During production incident triage, engineers observe: An AE bundle loses one physical member but monitoring still shows the logical interface up, and traffic exceeds the remaining member's capacity. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The designated router is primary under normal conditions and the backup takes over promptly during an injected outage.
- A controlled RE switchover maintains data-plane forwarding and routing neighbor continuity according to the selected supported feature set.
- The active member count and per-link utilization match service design, and the aggregate handles representative traffic without excessive drops.
- The standby RE has synchronized routing state and peer sessions stay established through a tested RE switch.
Explanation
Correct Answer
C:The active member count and per-link utilization match service design, and the aggregate handles representative traffic without excessive drops. This tests the actual condition identified in the live production incident: An AE bundle loses one physical member but monitoring still shows the logical interface up, and traffic exceeds the remaining member's capacity. It is meaningful because A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime.
Incorrect Answers
A:The designated router is primary under normal conditions and the backup takes over promptly during an injected outage. This measurement may prove the unrelated VRRP master priority failover condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An AE bundle loses one physical member but monitoring still shows the logical interface up, and traffic exceeds the remaining member's capacity. A relevant acceptance result here is: The active member count and per-link utilization match service design, and the aggregate handles representative traffic without excessive drops.
B:A controlled RE switchover maintains data-plane forwarding and routing neighbor continuity according to the selected supported feature set. This measurement may prove the unrelated GRES forwarding versus routing continuity condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An AE bundle loses one physical member but monitoring still shows the logical interface up, and traffic exceeds the remaining member's capacity. A relevant acceptance result here is: The active member count and per-link utilization match service design, and the aggregate handles representative traffic without excessive drops.
D:The standby RE has synchronized routing state and peer sessions stay established through a tested RE switch. This measurement may prove the unrelated NSR backup routing synchronization condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An AE bundle loses one physical member but monitoring still shows the logical interface up, and traffic exceeds the remaining member's capacity. A relevant acceptance result here is: The active member count and per-link utilization match service design, and the aggregate handles representative traffic without excessive drops.
Question 269
During production incident triage, engineers observe: An IBGP session targets a remote loopback but the local router sources traffic from a physical interface not permitted by its peer, so the BGP connection fails. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- The best path matches the documented MED comparison scope and the selected inbound preference is confirmed with peer attributes.
- The authorized prefix appears in the neighbor's received-route view and unrelated infrastructure addresses remain absent.
- The session establishes using the intended loopback source and destination and stays up after a physical link fails.
- The rejected prefix does not appear as an eligible route while approved advertised prefixes remain available.
Explanation
Correct Answer
C:The session establishes using the intended loopback source and destination and stays up after a physical link fails. This tests the actual condition identified in the live production incident: An IBGP session targets a remote loopback but the local router sources traffic from a physical interface not permitted by its peer, so the BGP connection fails. It is meaningful because IBGP loopback peering depends on correct local address selection and recursive reachability to the configured peer endpoint.
Incorrect Answers
A:The best path matches the documented MED comparison scope and the selected inbound preference is confirmed with peer attributes. This measurement may prove the unrelated BGP MED comparison scope condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An IBGP session targets a remote loopback but the local router sources traffic from a physical interface not permitted by its peer, so the BGP connection fails. A relevant acceptance result here is: The session establishes using the intended loopback source and destination and stays up after a physical link fails.
B:The authorized prefix appears in the neighbor's received-route view and unrelated infrastructure addresses remain absent. This measurement may prove the unrelated BGP export policy omission condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An IBGP session targets a remote loopback but the local router sources traffic from a physical interface not permitted by its peer, so the BGP connection fails. A relevant acceptance result here is: The session establishes using the intended loopback source and destination and stays up after a physical link fails.
D:The rejected prefix does not appear as an eligible route while approved advertised prefixes remain available. This measurement may prove the unrelated BGP import policy leak condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An IBGP session targets a remote loopback but the local router sources traffic from a physical interface not permitted by its peer, so the BGP connection fails. A relevant acceptance result here is: The session establishes using the intended loopback source and destination and stays up after a physical link fails.
Question 270
During production incident triage, 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. After the appropriate change, which observation would most directly establish that this particular issue was corrected?
- Initial flooding is VLAN-scoped, then subsequent frames to the learned MAC use the correct specific egress port.
- The MAC stabilizes on its expected port or approved redundancy construct and packet loss disappears.
- The customer MAC and VLAN appear in the correct virtual-switch instance with no leakage into default bridging context.
- Captured handoff frames carry the agreed outer tag and correct inner VLAN values and pass only the authorized service.
Explanation
Correct Answer
A:Initial flooding is VLAN-scoped, then subsequent frames to the learned MAC use the correct specific egress port. This tests the actual condition identified in the live production incident: 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 is meaningful because A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic.
Incorrect Answers
B:The MAC stabilizes on its expected port or approved redundancy construct and packet loss disappears. This measurement may prove the unrelated MAC move instability condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault 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. A relevant acceptance result here is: Initial flooding is VLAN-scoped, then subsequent frames to the learned MAC use the correct specific egress port.
C:The customer MAC and VLAN appear in the correct virtual-switch instance with no leakage into default bridging context. This measurement may prove the unrelated Virtual switch instance membership condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A 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. A relevant acceptance result here is: Initial flooding is VLAN-scoped, then subsequent frames to the learned MAC use the correct specific egress port.
D:Captured handoff frames carry the agreed outer tag and correct inner VLAN values and pass only the authorized service. This measurement may prove the unrelated Q-in-Q outer tag mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault 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. A relevant acceptance result here is: Initial flooding is VLAN-scoped, then subsequent frames to the learned MAC use the correct specific egress port.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests