Question 370
During production incident triage, engineers observe: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. An engineer suggests the shortcut: "Change OSPF cost only while ignoring VRRP priority and virtual-router state." Which critique explains the specific risk of that shortcut?
- VLAN membership does not make incompatible LACP peers join a single forwarding aggregate.
- Routing metrics in OSPF do not directly determine VRRP primary election.
- Logical link state does not certify available bandwidth after a partial member failure.
- Unreasonably small intervals can cause false liveness failures and repeated routing churn.
Explanation
Correct Answer
B:Routing metrics in OSPF do not directly determine VRRP primary election. In this live production incident the shortcut was explicitly proposed as: Change OSPF cost only while ignoring VRRP priority and virtual-router state. It fails to resolve the underlying problem that VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway. A sound alternative is the targeted engineering action: Check VRRP virtual-address and group consistency, effective priority and owner/preemption conditions, then restore the intended priority policy.
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: Change OSPF cost only while ignoring VRRP priority and virtual-router state. It should be rejected for the narrower reason that Routing metrics in OSPF do not directly determine VRRP primary election. This distinction matters because VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway.
C: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: Change OSPF cost only while ignoring VRRP priority and virtual-router state. It should be rejected for the narrower reason that Routing metrics in OSPF do not directly determine VRRP primary election. This distinction matters because VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway.
D:Unreasonably small intervals can cause false liveness failures and repeated routing churn. That critique concerns a shortcut from the unrelated BFD detect timer too aggressive case. The shortcut actually proposed in this live production incident is: Change OSPF cost only while ignoring VRRP priority and virtual-router state. It should be rejected for the narrower reason that Routing metrics in OSPF do not directly determine VRRP primary election. This distinction matters because VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway.
Question 371
During production incident triage, engineers observe: A service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. An engineer suggests the shortcut: "Increase the IPv4 packet TTL in an attempt to preserve the MPLS label header." Which critique explains the specific risk of that shortcut?
- 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.
- IP TTL does not control implicit-null versus explicit-null label disposition.
- Packet size settings cannot create capacity for an RSVP admission request.
Explanation
Correct Answer
C:IP TTL does not control implicit-null versus explicit-null label disposition. In this live production incident the shortcut was explicitly proposed as: Increase the IPv4 packet TTL in an attempt to preserve the MPLS label header. It fails to resolve the underlying problem that Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping. A sound alternative is the targeted engineering action: Apply supported explicit-null disposition where the QoS design requires a labeled packet to reach the egress.
Incorrect Answers
A: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: Increase the IPv4 packet TTL in an attempt to preserve the MPLS label header. It should be rejected for the narrower reason that IP TTL does not control implicit-null versus explicit-null label disposition. This distinction matters because Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping.
B: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: Increase the IPv4 packet TTL in an attempt to preserve the MPLS label header. It should be rejected for the narrower reason that IP TTL does not control implicit-null versus explicit-null label disposition. This distinction matters because Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping.
D: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: Increase the IPv4 packet TTL in an attempt to preserve the MPLS label header. It should be rejected for the narrower reason that IP TTL does not control implicit-null versus explicit-null label disposition. This distinction matters because Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping.
Question 372
During production incident triage, engineers observe: A route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. An engineer suggests the shortcut: "Disable all export filtering so the full routing table is advertised to the customer." Which critique explains the specific risk of that shortcut?
- Local preference governs route choice and does not change TCP source address or peer reachability.
- MED is normally used to influence inbound choice by neighbors, not internal egress preference across the local AS.
- Router IDs are late tie-breakers and duplicating them cannot replace proper MED comparison or policy.
- Unbounded export may disclose internal prefixes or become a source of accidental Internet route leaks.
Explanation
Correct Answer
D:Unbounded export may disclose internal prefixes or become a source of accidental Internet route leaks. In this live production incident the shortcut was explicitly proposed as: Disable all export filtering so the full routing table is advertised to the customer. It fails to resolve the underlying problem that BGP route advertisements are shaped by export routing policy and eligibility rather than the mere presence of a route in inet.0. A sound alternative is the targeted engineering action: Apply an export policy that permits precisely the required public prefix to the designated neighbor and rejects unrelated routes.
Incorrect Answers
A:Local preference governs route choice and does not change TCP source address or peer reachability. That critique concerns a shortcut from the unrelated IBGP loopback source resolution case. The shortcut actually proposed in this live production incident is: Disable all export filtering so the full routing table is advertised to the customer. It should be rejected for the narrower reason that Unbounded export may disclose internal prefixes or become a source of accidental Internet route leaks. This distinction matters because BGP route advertisements are shaped by export routing policy and eligibility rather than the mere presence of a route in inet.0.
B: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: Disable all export filtering so the full routing table is advertised to the customer. It should be rejected for the narrower reason that Unbounded export may disclose internal prefixes or become a source of accidental Internet route leaks. This distinction matters because BGP route advertisements are shaped by export routing policy and eligibility rather than the mere presence of a route in inet.0.
C:Router IDs are late tie-breakers and duplicating them cannot replace proper MED comparison or policy. That critique concerns a shortcut from the unrelated BGP MED comparison scope case. The shortcut actually proposed in this live production incident is: Disable all export filtering so the full routing table is advertised to the customer. It should be rejected for the narrower reason that Unbounded export may disclose internal prefixes or become a source of accidental Internet route leaks. This distinction matters because BGP route advertisements are shaped by export routing policy and eligibility rather than the mere presence of a route in inet.0.
Question 373
During production incident triage, engineers observe: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. An engineer suggests the shortcut: "Advertise an extra IGP prefix while leaving TCP 646 blocked." Which critique explains the specific risk of that shortcut?
- IP reachability alone does not create MPLS label switching capability on a disabled interface.
- Additional network-layer routes cannot substitute for the required LDP session transport.
- IP addressing does not repair the label operation needed at a transit LSR.
- PHP is a normal label disposition behavior and not evidence that the entire LSP should be removed.
Explanation
Correct Answer
B:Additional network-layer routes cannot substitute for the required LDP session transport. In this live production incident the shortcut was explicitly proposed as: Advertise an extra IGP prefix while leaving TCP 646 blocked. It fails to resolve the underlying problem that LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment. A sound alternative is the targeted engineering action: Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls.
Incorrect Answers
A: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: Advertise an extra IGP prefix while leaving TCP 646 blocked. It should be rejected for the narrower reason that Additional network-layer routes cannot substitute for the required LDP session transport. This distinction matters because LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment.
C:IP addressing does not repair the label operation needed at a transit LSR. That critique concerns a shortcut from the unrelated Incoming label missing in LFIB case. The shortcut actually proposed in this live production incident is: Advertise an extra IGP prefix while leaving TCP 646 blocked. It should be rejected for the narrower reason that Additional network-layer routes cannot substitute for the required LDP session transport. This distinction matters because LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment.
D:PHP is a normal label disposition behavior and not evidence that the entire LSP should be removed. That critique concerns a shortcut from the unrelated Penultimate hop popping case. The shortcut actually proposed in this live production incident is: Advertise an extra IGP prefix while leaving TCP 646 blocked. It should be rejected for the narrower reason that Additional network-layer routes cannot substitute for the required LDP session transport. This distinction matters because LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment.
Question 374
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. An engineer suggests the shortcut: "Turn off all routing-policy checks globally to allow the questionable prefix." Which critique explains the specific risk of that shortcut?
- Global relaxation hides a routing or addressing error and exposes unrelated prefixes to the same risk.
- Removing valid specifics would disrupt actual destinations and does not establish a correct summary-fallback design.
- 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.
Explanation
Correct Answer
A:Global relaxation hides a routing or addressing error and exposes unrelated prefixes to the same risk. In this live production incident the shortcut was explicitly proposed as: Turn off all routing-policy checks globally to allow the questionable prefix. It fails to resolve the underlying problem that Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context. A sound alternative is the targeted engineering action: Inspect the relevant martian and routing-policy configuration and explicitly enforce the authorized treatment of that prefix.
Incorrect Answers
B:Removing valid specifics would disrupt actual destinations and does not establish a correct summary-fallback design. That critique concerns a shortcut from the unrelated Aggregate rejection behavior case. The shortcut actually proposed in this live production incident is: Turn off all routing-policy checks globally to allow the questionable prefix. It should be rejected for the narrower reason that Global relaxation hides a routing or addressing error and exposes unrelated prefixes to the same risk. This distinction matters because Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context.
C: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: Turn off all routing-policy checks globally to allow the questionable prefix. It should be rejected for the narrower reason that Global relaxation hides a routing or addressing error and exposes unrelated prefixes to the same risk. This distinction matters because Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context.
D: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: Turn off all routing-policy checks globally to allow the questionable prefix. It should be rejected for the narrower reason that Global relaxation hides a routing or addressing error and exposes unrelated prefixes to the same risk. This distinction matters because Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context.
Question 375
During production incident triage, 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. An engineer suggests the shortcut: "Change the node-SID numeric label alone and expect traffic to follow a different topology path." Which critique explains the specific risk of that shortcut?
- Renumbering a destination node SID does not inherently specify a new intermediate route sequence.
- Additional network-layer routes cannot substitute for the required LDP session transport.
- IP addressing does not repair the label operation needed at a transit LSR.
- PHP is a normal label disposition behavior and not evidence that the entire LSP should be removed.
Explanation
Correct Answer
A:Renumbering a destination node SID does not inherently specify a new intermediate route sequence. In this live production incident the shortcut was explicitly proposed as: Change the node-SID numeric label alone and expect traffic to follow a different topology path. It fails to resolve the underlying problem that A node SID typically steers toward its destination using shortest-path IGP forwarding, while explicit adjacency segments can add finer path constraints. A sound alternative is the targeted engineering action: Use appropriate segment choices or a supported SR policy when explicit path steering is required, rather than treating a node SID as an exact-hop instruction.
Incorrect Answers
B: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: Change the node-SID numeric label alone and expect traffic to follow a different topology path. It should be rejected for the narrower reason that Renumbering a destination node SID does not inherently specify a new intermediate route sequence. This distinction matters because A node SID typically steers toward its destination using shortest-path IGP forwarding, while explicit adjacency segments can add finer path constraints.
C:IP addressing does not repair the label operation needed at a transit LSR. That critique concerns a shortcut from the unrelated Incoming label missing in LFIB case. The shortcut actually proposed in this live production incident is: Change the node-SID numeric label alone and expect traffic to follow a different topology path. It should be rejected for the narrower reason that Renumbering a destination node SID does not inherently specify a new intermediate route sequence. This distinction matters because A node SID typically steers toward its destination using shortest-path IGP forwarding, while explicit adjacency segments can add finer path constraints.
D:PHP is a normal label disposition behavior and not evidence that the entire LSP should be removed. That critique concerns a shortcut from the unrelated Penultimate hop popping case. The shortcut actually proposed in this live production incident is: Change the node-SID numeric label alone and expect traffic to follow a different topology path. It should be rejected for the narrower reason that Renumbering a destination node SID does not inherently specify a new intermediate route sequence. This distinction matters because A node SID typically steers toward its destination using shortest-path IGP forwarding, while explicit adjacency segments can add finer path constraints.
Question 376
During production incident triage, engineers observe: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. An engineer suggests the shortcut: "Change the advertised OSPF router ID so the path seems more attractive." Which critique explains the specific risk of that shortcut?
- BGP keepalive changes do not resolve an OSPF interface timer mismatch.
- SPF path cost is distinct from the DR election priority; changing cost does not reverse priority-zero ineligibility.
- Router-ID identity is not an OSPF path-cost control knob.
- Blanket redistribution can expose management and unrelated customer networks and create routing instability.
Explanation
Correct Answer
C:Router-ID identity is not an OSPF path-cost control knob. In this live production incident the shortcut was explicitly proposed as: Change the advertised OSPF router ID so the path seems more attractive. It fails to resolve the underlying problem that OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric. A sound alternative is the targeted engineering action: Correct the relevant OSPF interface costs in line with the approved traffic-engineering design and validate SPF selection.
Incorrect Answers
A:BGP keepalive changes do not resolve an OSPF interface timer mismatch. That critique concerns a shortcut from the unrelated OSPF hello dead timer mismatch case. The shortcut actually proposed in this live production incident is: Change the advertised OSPF router ID so the path seems more attractive. It should be rejected for the narrower reason that Router-ID identity is not an OSPF path-cost control knob. This distinction matters because OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric.
B:SPF path cost is distinct from the DR election priority; changing cost does not reverse priority-zero ineligibility. That critique concerns a shortcut from the unrelated DR priority zero misconception case. The shortcut actually proposed in this live production incident is: Change the advertised OSPF router ID so the path seems more attractive. It should be rejected for the narrower reason that Router-ID identity is not an OSPF path-cost control knob. This distinction matters because OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric.
D:Blanket redistribution can expose management and unrelated customer networks and create routing instability. That critique concerns a shortcut from the unrelated OSPF export policy omission case. The shortcut actually proposed in this live production incident is: Change the advertised OSPF router ID so the path seems more attractive. It should be rejected for the narrower reason that Router-ID identity is not an OSPF path-cost control knob. This distinction matters because OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric.
Question 377
During production incident triage, engineers observe: Two switches intended to operate in the same MSTP region treat each other as a boundary because their VLAN-to-instance mapping digests differ. An engineer suggests the shortcut: "Change only VLAN interface descriptions without fixing the region mapping." Which critique explains the specific risk of that shortcut?
- Making redundant ports forward simultaneously can introduce a Layer 2 loop and broadcast storm.
- Removing STP protection can permit the unauthorized bridge to create a forwarding loop.
- Descriptions do not participate in MSTP region identification or instance mapping.
- MTU is not the STP bridge-ID control and does not prevent superior BPDUs from winning election.
Explanation
Correct Answer
C:Descriptions do not participate in MSTP region identification or instance mapping. In this live production incident the shortcut was explicitly proposed as: Change only VLAN interface descriptions without fixing the region mapping. It fails to resolve the underlying problem that MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping. A sound alternative is the targeted engineering action: Align the MSTP region name, revision and VLAN-to-instance mapping across intended region members.
Incorrect Answers
A:Making redundant ports forward simultaneously can introduce a Layer 2 loop and broadcast storm. That critique concerns a shortcut from the unrelated RSTP alternate port activation case. The shortcut actually proposed in this live production incident is: Change only VLAN interface descriptions without fixing the region mapping. It should be rejected for the narrower reason that Descriptions do not participate in MSTP region identification or instance mapping. This distinction matters because MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping.
B:Removing STP protection can permit the unauthorized bridge to create a forwarding loop. That critique concerns a shortcut from the unrelated Unexpected BPDU on edge port case. The shortcut actually proposed in this live production incident is: Change only VLAN interface descriptions without fixing the region mapping. It should be rejected for the narrower reason that Descriptions do not participate in MSTP region identification or instance mapping. This distinction matters because MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping.
D:MTU is not the STP bridge-ID control and does not prevent superior BPDUs from winning election. That critique concerns a shortcut from the unrelated Root protection against rogue core case. The shortcut actually proposed in this live production incident is: Change only VLAN interface descriptions without fixing the region mapping. It should be rejected for the narrower reason that Descriptions do not participate in MSTP region identification or instance mapping. This distinction matters because MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping.
Question 378
During production incident triage, engineers observe: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. An engineer suggests the shortcut: "Raise the IP routing preference for all IS-IS routes without changing level configuration." 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.
- Route preference affects installation of received routes, not which IS-IS levels can form an adjacency.
- OSPF election settings are unrelated to IS-IS DIS selection on the LAN.
Explanation
Correct Answer
C:Route preference affects installation of received routes, not which IS-IS levels can form an adjacency. In this live production incident the shortcut was explicitly proposed as: Raise the IP routing preference for all IS-IS routes without changing level configuration. It fails to resolve the underlying problem that An IS-IS adjacency needs compatible protocol levels as well as link reachability. A sound alternative is the targeted engineering action: Configure a common allowed IS-IS level on the two interfaces in accordance with the area and backbone design.
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: Raise the IP routing preference for all IS-IS routes without changing level configuration. It should be rejected for the narrower reason that Route preference affects installation of received routes, not which IS-IS levels can form an adjacency. This distinction matters because An IS-IS adjacency needs compatible protocol levels as well as link reachability.
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: Raise the IP routing preference for all IS-IS routes without changing level configuration. It should be rejected for the narrower reason that Route preference affects installation of received routes, not which IS-IS levels can form an adjacency. This distinction matters because An IS-IS adjacency needs compatible protocol levels as well as link reachability.
D: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: Raise the IP routing preference for all IS-IS routes without changing level configuration. It should be rejected for the narrower reason that Route preference affects installation of received routes, not which IS-IS levels can form an adjacency. This distinction matters because An IS-IS adjacency needs compatible protocol levels as well as link reachability.
Question 379
During production incident triage, engineers observe: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. An engineer suggests the shortcut: "Enable LDP on a different PE and expect the RSVP explicit route to be repaired." Which critique explains the specific risk of that shortcut?
- 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.
- PHP is a normal label disposition behavior and not evidence that the entire LSP should be removed.
- LDP discovery on an unrelated peer does not satisfy a broken RSVP explicit-hop constraint.
Explanation
Correct Answer
D:LDP discovery on an unrelated peer does not satisfy a broken RSVP explicit-hop constraint. In this live production incident the shortcut was explicitly proposed as: Enable LDP on a different PE and expect the RSVP explicit route to be repaired. It fails to resolve the underlying problem that RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange. A sound alternative is the targeted engineering action: Correct the constrained explicit path or restore its required hop and rerun RSVP path signaling.
Incorrect Answers
A: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: Enable LDP on a different PE and expect the RSVP explicit route to be repaired. It should be rejected for the narrower reason that LDP discovery on an unrelated peer does not satisfy a broken RSVP explicit-hop constraint. This distinction matters because RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange.
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: Enable LDP on a different PE and expect the RSVP explicit route to be repaired. It should be rejected for the narrower reason that LDP discovery on an unrelated peer does not satisfy a broken RSVP explicit-hop constraint. This distinction matters because RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange.
C:PHP is a normal label disposition behavior and not evidence that the entire LSP should be removed. That critique concerns a shortcut from the unrelated Penultimate hop popping case. The shortcut actually proposed in this live production incident is: Enable LDP on a different PE and expect the RSVP explicit route to be repaired. It should be rejected for the narrower reason that LDP discovery on an unrelated peer does not satisfy a broken RSVP explicit-hop constraint. This distinction matters because RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange.
Question 380
During production incident triage, engineers observe: A provider calls a GRE tunnel secure against eavesdropping merely because customers cannot see its inner packet headers on the underlay. An engineer suggests the shortcut: "Rely on GRE encapsulation alone as if it were end-to-end encryption." Which critique explains the specific risk of that shortcut?
- 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.
- Larger packets increase the encapsulation MTU violation and do not solve delivery.
Explanation
Correct Answer
A:Encapsulation hides protocol framing but provides no cryptographic confidentiality or integrity against an observer. In this live production incident the shortcut was explicitly proposed as: Rely on GRE encapsulation alone as if it were end-to-end encryption. It fails to resolve the underlying problem that GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls. A sound alternative is the targeted engineering action: Add an appropriate encryption mechanism such as supported IPsec where confidentiality is required, while treating GRE as encapsulation.
Incorrect Answers
B:Changing inner routing parameters does not repair an incorrectly addressed outer GRE encapsulation path. That critique concerns a shortcut from the unrelated GRE tunnel endpoint mismatch case. The shortcut actually proposed in this live production incident is: Rely on GRE encapsulation alone as if it were end-to-end encryption. It should be rejected for the narrower reason that Encapsulation hides protocol framing but provides no cryptographic confidentiality or integrity against an observer. This distinction matters because GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls.
C: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: Rely on GRE encapsulation alone as if it were end-to-end encryption. It should be rejected for the narrower reason that Encapsulation hides protocol framing but provides no cryptographic confidentiality or integrity against an observer. This distinction matters because GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls.
D: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: Rely on GRE encapsulation alone as if it were end-to-end encryption. It should be rejected for the narrower reason that Encapsulation hides protocol framing but provides no cryptographic confidentiality or integrity against an observer. This distinction matters because GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests