Question 390
During production incident triage, engineers observe: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. An engineer suggests the shortcut: "Turn every trunk into an unrestricted all-VLAN connection." Which critique explains the specific risk of that shortcut?
- A duplicate name does not move frames into the intended instance and can increase configuration confusion.
- Opening all VLANs expands the Layer 2 service boundary rather than fixing the specific missing membership.
- An aging change cannot prevent contradictory source-MAC observations on multiple ports.
- MAC aging does not create a Layer 3 interface or provide inter-subnet forwarding.
Explanation
Correct Answer
B:Opening all VLANs expands the Layer 2 service boundary rather than fixing the specific missing membership. In this live production incident the shortcut was explicitly proposed as: Turn every trunk into an unrestricted all-VLAN connection. It fails to resolve the underlying problem that A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers. A sound alternative is the targeted engineering action: Add only the authorized VLAN to the relevant tagged-trunk membership and verify tagging end to end.
Incorrect Answers
A:A duplicate name does not move frames into the intended instance and can increase configuration confusion. That critique concerns a shortcut from the unrelated Virtual switch instance membership case. The shortcut actually proposed in this live production incident is: Turn every trunk into an unrestricted all-VLAN connection. It should be rejected for the narrower reason that Opening all VLANs expands the Layer 2 service boundary rather than fixing the specific missing membership. This distinction matters because A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers.
C:An aging change cannot prevent contradictory source-MAC observations on multiple ports. That critique concerns a shortcut from the unrelated MAC move instability case. The shortcut actually proposed in this live production incident is: Turn every trunk into an unrestricted all-VLAN connection. It should be rejected for the narrower reason that Opening all VLANs expands the Layer 2 service boundary rather than fixing the specific missing membership. This distinction matters because A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers.
D:MAC aging does not create a Layer 3 interface or provide inter-subnet forwarding. That critique concerns a shortcut from the unrelated IRB routed gateway missing case. The shortcut actually proposed in this live production incident is: Turn every trunk into an unrestricted all-VLAN connection. It should be rejected for the narrower reason that Opening all VLANs expands the Layer 2 service boundary rather than fixing the specific missing membership. This distinction matters because A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers.
Question 391
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. An engineer suggests the shortcut: "Change an IPv4 interface prefix while leaving the conflicting ISO area addresses." Which critique explains the specific risk of that shortcut?
- Additional IPv4 addresses do not provide the ISO interface family needed for IS-IS signaling.
- Documentation cannot extend a protocol metric's encoding or cause routers to use a new metric style.
- OSPF election settings are unrelated to IS-IS DIS selection on the LAN.
- An IP subnet change alone cannot resolve IS-IS Level 1 NET area incompatibility.
Explanation
Correct Answer
D:An IP subnet change alone cannot resolve IS-IS Level 1 NET area incompatibility. In this live production incident the shortcut was explicitly proposed as: Change an IPv4 interface prefix while leaving the conflicting ISO area addresses. It fails to resolve the underlying problem that IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas. A sound alternative is the targeted engineering action: Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended.
Incorrect Answers
A:Additional IPv4 addresses do not provide the ISO interface family needed for IS-IS signaling. That critique concerns a shortcut from the unrelated IS-IS ISO family missing case. The shortcut actually proposed in this live production incident is: Change an IPv4 interface prefix while leaving the conflicting ISO area addresses. It should be rejected for the narrower reason that An IP subnet change alone cannot resolve IS-IS Level 1 NET area incompatibility. This distinction matters because IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas.
B:Documentation cannot extend a protocol metric's encoding or cause routers to use a new metric style. That critique concerns a shortcut from the unrelated IS-IS narrow metric ceiling case. The shortcut actually proposed in this live production incident is: Change an IPv4 interface prefix while leaving the conflicting ISO area addresses. It should be rejected for the narrower reason that An IP subnet change alone cannot resolve IS-IS Level 1 NET area incompatibility. This distinction matters because IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas.
C:OSPF election settings are unrelated to IS-IS DIS selection on the LAN. That critique concerns a shortcut from the unrelated IS-IS DIS election surprise case. The shortcut actually proposed in this live production incident is: Change an IPv4 interface prefix while leaving the conflicting ISO area addresses. It should be rejected for the narrower reason that An IP subnet change alone cannot resolve IS-IS Level 1 NET area incompatibility. This distinction matters because IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas.
Question 392
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. An engineer suggests the shortcut: "Disable all MAC learning on the switch to eliminate the observed flood." Which critique explains the specific risk of that shortcut?
- An aging change cannot prevent contradictory source-MAC observations on multiple ports.
- Removing MAC learning generally prolongs unknown-destination flooding rather than creating targeted forwarding.
- A duplicate name does not move frames into the intended instance and can increase configuration confusion.
- Changing customer tags can disrupt their VLAN separation and leaves the provider's outer-tag contract unresolved.
Explanation
Correct Answer
B:Removing MAC learning generally prolongs unknown-destination flooding rather than creating targeted forwarding. In this live production incident the shortcut was explicitly proposed as: Disable all MAC learning on the switch to eliminate the observed flood. It fails to resolve the underlying problem that A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic. A sound alternative is the targeted engineering action: Verify unknown-unicast flooding within the VLAN, then confirm MAC learning limits later traffic to the learned egress port.
Incorrect Answers
A:An aging change cannot prevent contradictory source-MAC observations on multiple ports. That critique concerns a shortcut from the unrelated MAC move instability case. The shortcut actually proposed in this live production incident is: Disable all MAC learning on the switch to eliminate the observed flood. It should be rejected for the narrower reason that Removing MAC learning generally prolongs unknown-destination flooding rather than creating targeted forwarding. This distinction matters because A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic.
C:A duplicate name does not move frames into the intended instance and can increase configuration confusion. That critique concerns a shortcut from the unrelated Virtual switch instance membership case. The shortcut actually proposed in this live production incident is: Disable all MAC learning on the switch to eliminate the observed flood. It should be rejected for the narrower reason that Removing MAC learning generally prolongs unknown-destination flooding rather than creating targeted forwarding. This distinction matters because A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic.
D:Changing customer tags can disrupt their VLAN separation and leaves the provider's outer-tag contract unresolved. That critique concerns a shortcut from the unrelated Q-in-Q outer tag mismatch case. The shortcut actually proposed in this live production incident is: Disable all MAC learning on the switch to eliminate the observed flood. It should be rejected for the narrower reason that Removing MAC learning generally prolongs unknown-destination flooding rather than creating targeted forwarding. This distinction matters because A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic.
Question 393
During production incident triage, engineers observe: Two routers have interface-based GRE tunnels, but the source address on one end does not match the destination configured on the remote end. An engineer suggests the shortcut: "Change only the inner tunnel-interface subnet mask and leave outer endpoints mismatched." Which critique explains the specific risk of that shortcut?
- Larger packets increase the encapsulation MTU violation and do not solve delivery.
- Encapsulation hides protocol framing but provides no cryptographic confidentiality or integrity against an observer.
- Changing inner routing parameters does not repair an incorrectly addressed outer GRE encapsulation path.
- Circular resolution sends the tunnel's transport traffic back into the overlay it depends upon.
Explanation
Correct Answer
C:Changing inner routing parameters does not repair an incorrectly addressed outer GRE encapsulation path. In this live production incident the shortcut was explicitly proposed as: Change only the inner tunnel-interface subnet mask and leave outer endpoints mismatched. It fails to resolve the underlying problem that GRE encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel. A sound alternative is the targeted engineering action: Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path.
Incorrect Answers
A:Larger packets increase the encapsulation MTU violation and do not solve delivery. That critique concerns a shortcut from the unrelated GRE encapsulation MTU overhead case. The shortcut actually proposed in this live production incident is: Change only the inner tunnel-interface subnet mask and leave outer endpoints mismatched. It should be rejected for the narrower reason that Changing inner routing parameters does not repair an incorrectly addressed outer GRE encapsulation path. This distinction matters because GRE encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel.
B:Encapsulation hides protocol framing but provides no cryptographic confidentiality or integrity against an observer. That critique concerns a shortcut from the unrelated GRE confidentiality misconception case. The shortcut actually proposed in this live production incident is: Change only the inner tunnel-interface subnet mask and leave outer endpoints mismatched. It should be rejected for the narrower reason that Changing inner routing parameters does not repair an incorrectly addressed outer GRE encapsulation path. This distinction matters because GRE encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel.
D:Circular resolution sends the tunnel's transport traffic back into the overlay it depends upon. That critique concerns a shortcut from the unrelated GRE underlay recursive loss case. The shortcut actually proposed in this live production incident is: Change only the inner tunnel-interface subnet mask and leave outer endpoints mismatched. It should be rejected for the narrower reason that Changing inner routing parameters does not repair an incorrectly addressed outer GRE encapsulation path. This distinction matters because GRE encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel.
Question 394
During production incident triage, engineers observe: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. An engineer suggests the shortcut: "Assume the outgoing LSP defines a bidirectional circuit and ignore return-path programming." Which critique explains the specific risk of that shortcut?
- One-way RSVP signaling does not establish reverse-path label forwarding through the same LSP.
- IP reachability alone does not create MPLS label switching capability on a disabled interface.
- OSPF metric calculations cannot cause LDP to participate on an interface where it is not configured.
- Additional network-layer routes cannot substitute for the required LDP session transport.
Explanation
Correct Answer
A:One-way RSVP signaling does not establish reverse-path label forwarding through the same LSP. In this live production incident the shortcut was explicitly proposed as: Assume the outgoing LSP defines a bidirectional circuit and ignore return-path programming. It fails to resolve the underlying problem that RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP. A sound alternative is the targeted engineering action: Provision and verify a separate return LSP or alternate reverse forwarding mechanism consistent with the service design.
Incorrect Answers
B:IP reachability alone does not create MPLS label switching capability on a disabled interface. That critique concerns a shortcut from the unrelated MPLS interface not enabled case. The shortcut actually proposed in this live production incident is: Assume the outgoing LSP defines a bidirectional circuit and ignore return-path programming. It should be rejected for the narrower reason that One-way RSVP signaling does not establish reverse-path label forwarding through the same LSP. This distinction matters because RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP.
C:OSPF metric calculations cannot cause LDP to participate on an interface where it is not configured. That critique concerns a shortcut from the unrelated LDP discovery and IGP mismatch case. The shortcut actually proposed in this live production incident is: Assume the outgoing LSP defines a bidirectional circuit and ignore return-path programming. It should be rejected for the narrower reason that One-way RSVP signaling does not establish reverse-path label forwarding through the same LSP. This distinction matters because RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP.
D:Additional network-layer routes cannot substitute for the required LDP session transport. That critique concerns a shortcut from the unrelated LDP TCP 646 establishment case. The shortcut actually proposed in this live production incident is: Assume the outgoing LSP defines a bidirectional circuit and ignore return-path programming. It should be rejected for the narrower reason that One-way RSVP signaling does not establish reverse-path label forwarding through the same LSP. This distinction matters because RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP.
Question 395
During production incident triage, engineers observe: An infrastructure route is present in inet.0 but absent from a secondary table whose applications depend on that route, and operators assume all tables automatically share entries. An engineer suggests the shortcut: "Change the router hostname to match the routing-instance name." Which critique explains the specific risk of that shortcut?
- Administrative descriptions and physical speeds do not establish equal routing cost or multipath eligibility.
- Forcing packets of one flow onto different paths can reorder packets and harm transport performance.
- Physical link-up does not establish downstream forwarding correctness beyond the adjacent hop.
- Hostname changes do not import a route between separate routing information bases.
Explanation
Correct Answer
D:Hostname changes do not import a route between separate routing information bases. In this live production incident the shortcut was explicitly proposed as: Change the router hostname to match the routing-instance name. It fails to resolve the underlying problem that Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms. A sound alternative is the targeted engineering action: Configure and test the intended RIB group or specific controlled route import into the appropriate secondary routing table.
Incorrect Answers
A:Administrative descriptions and physical speeds do not establish equal routing cost or multipath eligibility. That critique concerns a shortcut from the unrelated Equal-cost multipath eligibility case. The shortcut actually proposed in this live production incident is: Change the router hostname to match the routing-instance name. It should be rejected for the narrower reason that Hostname changes do not import a route between separate routing information bases. This distinction matters because Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms.
B:Forcing packets of one flow onto different paths can reorder packets and harm transport performance. That critique concerns a shortcut from the unrelated Per-flow hash expectation case. The shortcut actually proposed in this live production incident is: Change the router hostname to match the routing-instance name. It should be rejected for the narrower reason that Hostname changes do not import a route between separate routing information bases. This distinction matters because Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms.
C:Physical link-up does not establish downstream forwarding correctness beyond the adjacent hop. That critique concerns a shortcut from the unrelated Static backup blackhole case. The shortcut actually proposed in this live production incident is: Change the router hostname to match the routing-instance name. It should be rejected for the narrower reason that Hostname changes do not import a route between separate routing information bases. This distinction matters because Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms.
Question 396
During production incident triage, 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. An engineer suggests the shortcut: "Assume every routing neighbor automatically supports graceful restart with no negotiation." Which critique explains the specific risk of that shortcut?
- VLAN membership does not make incompatible LACP peers join a single forwarding aggregate.
- Logical link state does not certify available bandwidth after a partial member failure.
- Routing metrics in OSPF do not directly determine VRRP primary election.
- Peer implementations and configuration differ; lack of helper cooperation can invalidate preserved-routing expectations.
Explanation
Correct Answer
D:Peer implementations and configuration differ; lack of helper cooperation can invalidate preserved-routing expectations. In this live production incident the shortcut was explicitly proposed as: Assume every routing neighbor automatically supports graceful restart with no negotiation. It fails to resolve the underlying problem that Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior. A sound alternative is the targeted engineering action: Validate supported graceful-restart negotiation and helper capability, or choose NSR when helper dependency is unacceptable.
Incorrect Answers
A:VLAN membership does not make incompatible LACP peers join a single forwarding aggregate. That critique concerns a shortcut from the unrelated LACP partner mismatch case. The shortcut actually proposed in this live production incident is: Assume every routing neighbor automatically supports graceful restart with no negotiation. It should be rejected for the narrower reason that Peer implementations and configuration differ; lack of helper cooperation can invalidate preserved-routing expectations. This distinction matters because Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior.
B:Logical link state does not certify available bandwidth after a partial member failure. That critique concerns a shortcut from the unrelated LAG member imbalance after failure case. The shortcut actually proposed in this live production incident is: Assume every routing neighbor automatically supports graceful restart with no negotiation. It should be rejected for the narrower reason that Peer implementations and configuration differ; lack of helper cooperation can invalidate preserved-routing expectations. This distinction matters because Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior.
C:Routing metrics in OSPF do not directly determine VRRP primary election. That critique concerns a shortcut from the unrelated VRRP master priority failover case. The shortcut actually proposed in this live production incident is: Assume every routing neighbor automatically supports graceful restart with no negotiation. It should be rejected for the narrower reason that Peer implementations and configuration differ; lack of helper cooperation can invalidate preserved-routing expectations. This distinction matters because Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior.
Question 397
During production incident triage, engineers observe: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. An engineer suggests the shortcut: "Increase BGP import policy acceptance without correcting the remote AS." Which critique explains the specific risk of that shortcut?
- MED is normally used to influence inbound choice by neighbors, not internal egress preference across the local AS.
- OSPF LAN DR election settings do not modify the BGP path attributes being compared.
- Routing policy is evaluated for routes after a session forms; it cannot make an invalid peer-AS OPEN exchange acceptable.
- Remote-side policy is outside local control and does not enforce an explicit receiving security boundary.
Explanation
Correct Answer
C:Routing policy is evaluated for routes after a session forms; it cannot make an invalid peer-AS OPEN exchange acceptable. In this live production incident the shortcut was explicitly proposed as: Increase BGP import policy acceptance without correcting the remote AS. It fails to resolve the underlying problem that BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session. A sound alternative is the targeted engineering action: Correct the explicitly configured neighbor peer AS to match the authorized remote routing domain and verify the session parameters.
Incorrect Answers
A:MED is normally used to influence inbound choice by neighbors, not internal egress preference across the local AS. That critique concerns a shortcut from the unrelated BGP local preference egress case. The shortcut actually proposed in this live production incident is: Increase BGP import policy acceptance without correcting the remote AS. It should be rejected for the narrower reason that Routing policy is evaluated for routes after a session forms; it cannot make an invalid peer-AS OPEN exchange acceptable. This distinction matters because BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session.
B:OSPF LAN DR election settings do not modify the BGP path attributes being compared. That critique concerns a shortcut from the unrelated BGP AS-path comparison case. The shortcut actually proposed in this live production incident is: Increase BGP import policy acceptance without correcting the remote AS. It should be rejected for the narrower reason that Routing policy is evaluated for routes after a session forms; it cannot make an invalid peer-AS OPEN exchange acceptable. This distinction matters because BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session.
D:Remote-side policy is outside local control and does not enforce an explicit receiving security boundary. That critique concerns a shortcut from the unrelated BGP import policy leak case. The shortcut actually proposed in this live production incident is: Increase BGP import policy acceptance without correcting the remote AS. It should be rejected for the narrower reason that Routing policy is evaluated for routes after a session forms; it cannot make an invalid peer-AS OPEN exchange acceptable. This distinction matters because BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session.
Question 398
During production incident triage, engineers observe: An LDP session is operational, but a destination FEC lacks the usable outgoing label that an ingress PE expects to use. An engineer suggests the shortcut: "Assume that an Operational LDP session alone proves all labeled destinations work." Which critique explains the specific risk of that shortcut?
- Session establishment says nothing about whether an individual FEC has a usable label mapping.
- OSPF metric calculations cannot cause LDP to participate on an interface where it is not configured.
- Packet size settings cannot create capacity for an RSVP admission request.
- Suppressing alarms cannot provide a precomputed alternate label-switched route.
Explanation
Correct Answer
A:Session establishment says nothing about whether an individual FEC has a usable label mapping. In this live production incident the shortcut was explicitly proposed as: Assume that an Operational LDP session alone proves all labeled destinations work. It fails to resolve the underlying problem 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. A sound alternative is the targeted engineering action: Verify FEC route reachability, neighbor label advertisement and the label mapping installed for the specific destination.
Incorrect Answers
B:OSPF metric calculations cannot cause LDP to participate on an interface where it is not configured. That critique concerns a shortcut from the unrelated LDP discovery and IGP mismatch case. The shortcut actually proposed in this live production incident is: Assume that an Operational LDP session alone proves all labeled destinations work. It should be rejected for the narrower reason that Session establishment says nothing about whether an individual FEC has a usable label mapping. This distinction matters because 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:Packet size settings cannot create capacity for an RSVP admission request. That critique concerns a shortcut from the unrelated RSVP reservable bandwidth shortage case. The shortcut actually proposed in this live production incident is: Assume that an Operational LDP session alone proves all labeled destinations work. It should be rejected for the narrower reason that Session establishment says nothing about whether an individual FEC has a usable label mapping. This distinction matters because 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:Suppressing alarms cannot provide a precomputed alternate label-switched route. That critique concerns a shortcut from the unrelated RSVP link protection plan case. The shortcut actually proposed in this live production incident is: Assume that an Operational LDP session alone proves all labeled destinations work. It should be rejected for the narrower reason that Session establishment says nothing about whether an individual FEC has a usable label mapping. This distinction matters because 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 399
During production incident triage, 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. An engineer suggests the shortcut: "Change a loopback IPv4 address without altering trunk native VLAN definitions." Which critique explains the specific risk of that shortcut?
- Loopback addressing does not determine how untagged trunk traffic is mapped into VLANs.
- An aging change cannot prevent contradictory source-MAC observations on multiple ports.
- A duplicate name does not move frames into the intended instance and can increase configuration confusion.
- Layer 3 route changes cannot change the Layer 2 VLAN assignment of untagged frames.
Explanation
Correct Answer
A:Loopback addressing does not determine how untagged trunk traffic is mapped into VLANs. In this live production incident the shortcut was explicitly proposed as: Change a loopback IPv4 address without altering trunk native VLAN definitions. It fails to resolve the underlying problem that Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping. A sound alternative is the targeted engineering action: Align intended native VLAN handling on both ends or require explicit tagging according to the approved design.
Incorrect Answers
B:An aging change cannot prevent contradictory source-MAC observations on multiple ports. That critique concerns a shortcut from the unrelated MAC move instability case. The shortcut actually proposed in this live production incident is: Change a loopback IPv4 address without altering trunk native VLAN definitions. It should be rejected for the narrower reason that Loopback addressing does not determine how untagged trunk traffic is mapped into VLANs. This distinction matters because Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping.
C:A duplicate name does not move frames into the intended instance and can increase configuration confusion. That critique concerns a shortcut from the unrelated Virtual switch instance membership case. The shortcut actually proposed in this live production incident is: Change a loopback IPv4 address without altering trunk native VLAN definitions. It should be rejected for the narrower reason that Loopback addressing does not determine how untagged trunk traffic is mapped into VLANs. This distinction matters because Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping.
D:Layer 3 route changes cannot change the Layer 2 VLAN assignment of untagged frames. That critique concerns a shortcut from the unrelated Access VLAN membership case. The shortcut actually proposed in this live production incident is: Change a loopback IPv4 address without altering trunk native VLAN definitions. It should be rejected for the narrower reason that Loopback addressing does not determine how untagged trunk traffic is mapped into VLANs. This distinction matters because Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping.
Question 400
During production incident triage, engineers observe: A router interface carries IPv4 traffic and is listed under IS-IS, but no IS-IS Hello packets form because the required ISO protocol family is absent. An engineer suggests the shortcut: "Add an extra IPv4 secondary address as a substitute for ISO interface support." Which critique explains the specific risk of that shortcut?
- An IP subnet change alone cannot resolve IS-IS Level 1 NET area incompatibility.
- Route preference affects installation of received routes, not which IS-IS levels can form an adjacency.
- Additional IPv4 addresses do not provide the ISO interface family needed for IS-IS signaling.
- Changing interface labels cannot repair conflicting protocol system identities.
Explanation
Correct Answer
C:Additional IPv4 addresses do not provide the ISO interface family needed for IS-IS signaling. In this live production incident the shortcut was explicitly proposed as: Add an extra IPv4 secondary address as a substitute for ISO interface support. It fails to resolve the underlying problem that Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration. A sound alternative is the targeted engineering action: Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation.
Incorrect Answers
A:An IP subnet change alone cannot resolve IS-IS Level 1 NET area incompatibility. That critique concerns a shortcut from the unrelated IS-IS level-one area mismatch case. The shortcut actually proposed in this live production incident is: Add an extra IPv4 secondary address as a substitute for ISO interface support. It should be rejected for the narrower reason that Additional IPv4 addresses do not provide the ISO interface family needed for IS-IS signaling. This distinction matters because Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration.
B:Route preference affects installation of received routes, not which IS-IS levels can form an adjacency. That critique concerns a shortcut from the unrelated IS-IS level capability mismatch case. The shortcut actually proposed in this live production incident is: Add an extra IPv4 secondary address as a substitute for ISO interface support. It should be rejected for the narrower reason that Additional IPv4 addresses do not provide the ISO interface family needed for IS-IS signaling. This distinction matters because Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration.
D:Changing interface labels cannot repair conflicting protocol system identities. That critique concerns a shortcut from the unrelated Duplicate IS-IS system ID case. The shortcut actually proposed in this live production incident is: Add an extra IPv4 secondary address as a substitute for ISO interface support. It should be rejected for the narrower reason that Additional IPv4 addresses do not provide the ISO interface family needed for IS-IS signaling. This distinction matters because Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests