Pass Your Juniper JN0-364 Exam Easy!

Juniper JN0-364 Exam Questions & Answers, Accurate & Verified By IT Experts

Instant Download, Free Fast Updates, 99.6% Pass Rate

JN0-364 Premium VCE File

Juniper JN0-364 Premium File

69 Questions & Answers

Last Update: Oct 24, 2026

$69.99

JN0-364 Bundle gives you unlimited access to "JN0-364" files. However, this does not replace the need for a .vce exam simulator. To download VCE exam simulator click here
JN0-364 Premium VCE File
Juniper JN0-364 Premium File

69 Questions & Answers

Last Update: Oct 24, 2026

$69.99

Juniper JN0-364 Exam Bundle gives you unlimited access to "JN0-364" files. However, this does not replace the need for a .vce exam simulator. To download your .vce exam simulator click here

Juniper JN0-364 Practice Test 82

Question 810

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: PE-11 has a configured static route to 198.51.100.0/24, but the specified next hop 192.0.2.14 is not reachable by any active route, and traffic drops. An engineer suggests the shortcut: "Change the route description and leave the unresolved next hop unchanged." Which critique explains the specific risk of that shortcut?

  1. More routes in the original table do not implement selective forwarding through a different routing table.
  2. A text description has no effect on recursive route resolution and cannot install a usable forwarding entry.
  3. Physical link-up does not establish downstream forwarding correctness beyond the adjacent hop.
  4. Hostname changes do not import a route between separate routing information bases.

Explanation

Correct Answer

B:

A text description has no effect on recursive route resolution and cannot install a usable forwarding entry. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Change the route description and leave the unresolved next hop unchanged. It fails to resolve the underlying problem that A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface. A sound alternative is the targeted engineering action: Restore an active route to the specified next-hop address or replace it with a verified reachable next hop before relying on the static route.

Incorrect Answers

A:

More routes in the original table do not implement selective forwarding through a different routing table. That critique concerns a shortcut from the unrelated Filter-based forwarding classification case. The shortcut actually proposed in this controlled acceptance rehearsal is: Change the route description and leave the unresolved next hop unchanged. It should be rejected for the narrower reason that A text description has no effect on recursive route resolution and cannot install a usable forwarding entry. This distinction matters because A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface.

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 controlled acceptance rehearsal is: Change the route description and leave the unresolved next hop unchanged. It should be rejected for the narrower reason that A text description has no effect on recursive route resolution and cannot install a usable forwarding entry. This distinction matters because A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface.

D:

Hostname changes do not import a route between separate routing information bases. That critique concerns a shortcut from the unrelated RIB group forwarding copy case. The shortcut actually proposed in this controlled acceptance rehearsal is: Change the route description and leave the unresolved next hop unchanged. It should be rejected for the narrower reason that A text description has no effect on recursive route resolution and cannot install a usable forwarding entry. This distinction matters because A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface.

Question 811

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An IPv6 routing interface has global unicast addresses and a healthy OSPFv2 adjacency, yet OSPFv3 neighbor state is absent and no IPv6 routes are learned. An engineer suggests the shortcut: "Modify only OSPFv2 hello timers and expect OSPFv3 to appear." Which critique explains the specific risk of that shortcut?

  1. IPv4 routing entries cannot replace the missing IPv6 prefix advertisements.
  2. IPv4 path preference cannot create missing IPv6 NLRI negotiation or advertisement.
  3. An IPv4 route cannot supply the missing IPv6 link-local scope or next-hop selection.
  4. Changing IPv4 OSPFv2 parameters does not establish an independent OSPFv3 adjacency.

Explanation

Correct Answer

D:

Changing IPv4 OSPFv2 parameters does not establish an independent OSPFv3 adjacency. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Modify only OSPFv2 hello timers and expect OSPFv3 to appear. It fails to resolve the underlying problem that OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2. A sound alternative is the targeted engineering action: Enable and validate OSPFv3 link participation and neighbor exchange using the intended IPv6 link-local connectivity.

Incorrect Answers

A:

IPv4 routing entries cannot replace the missing IPv6 prefix advertisements. That critique concerns a shortcut from the unrelated IS-IS IPv6 reachability TLVs case. The shortcut actually proposed in this controlled acceptance rehearsal is: Modify only OSPFv2 hello timers and expect OSPFv3 to appear. It should be rejected for the narrower reason that Changing IPv4 OSPFv2 parameters does not establish an independent OSPFv3 adjacency. This distinction matters because OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2.

B:

IPv4 path preference cannot create missing IPv6 NLRI negotiation or advertisement. That critique concerns a shortcut from the unrelated IPv6 BGP NLRI family omitted case. The shortcut actually proposed in this controlled acceptance rehearsal is: Modify only OSPFv2 hello timers and expect OSPFv3 to appear. It should be rejected for the narrower reason that Changing IPv4 OSPFv2 parameters does not establish an independent OSPFv3 adjacency. This distinction matters because OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2.

C:

An IPv4 route cannot supply the missing IPv6 link-local scope or next-hop selection. That critique concerns a shortcut from the unrelated IPv6 static link-local next hop case. The shortcut actually proposed in this controlled acceptance rehearsal is: Modify only OSPFv2 hello timers and expect OSPFv3 to appear. It should be rejected for the narrower reason that Changing IPv4 OSPFv2 parameters does not establish an independent OSPFv3 adjacency. This distinction matters because OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2.

Question 812

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. An engineer suggests the shortcut: "Add a static route to inet.0 for every destination, ignoring the ingress filter." Which critique explains the specific risk of that shortcut?

  1. Global relaxation hides a routing or addressing error and exposes unrelated prefixes to the same risk.
  2. Forcing packets of one flow onto different paths can reorder packets and harm transport performance.
  3. Physical link-up does not establish downstream forwarding correctness beyond the adjacent hop.
  4. More routes in the original table do not implement selective forwarding through a different routing table.

Explanation

Correct Answer

D:

More routes in the original table do not implement selective forwarding through a different routing table. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Add a static route to inet.0 for every destination, ignoring the ingress filter. It fails to resolve the underlying problem that Filter-based forwarding selects a routing table based on matched packet fields at the ingress point; the selected table must contain a usable destination route. A sound alternative is the targeted engineering action: Apply a narrowly matched ingress firewall filter action that selects the intended forwarding routing instance and verify its routes.

Incorrect Answers

A:

Global relaxation hides a routing or addressing error and exposes unrelated prefixes to the same risk. That critique concerns a shortcut from the unrelated Martian-address acceptance case. The shortcut actually proposed in this controlled acceptance rehearsal is: Add a static route to inet.0 for every destination, ignoring the ingress filter. It should be rejected for the narrower reason that More routes in the original table do not implement selective forwarding through a different routing table. This distinction matters because Filter-based forwarding selects a routing table based on matched packet fields at the ingress point; the selected table must contain a usable destination route.

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 controlled acceptance rehearsal is: Add a static route to inet.0 for every destination, ignoring the ingress filter. It should be rejected for the narrower reason that More routes in the original table do not implement selective forwarding through a different routing table. This distinction matters because Filter-based forwarding selects a routing table based on matched packet fields at the ingress point; the selected table must contain a usable destination route.

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 controlled acceptance rehearsal is: Add a static route to inet.0 for every destination, ignoring the ingress filter. It should be rejected for the narrower reason that More routes in the original table do not implement selective forwarding through a different routing table. This distinction matters because Filter-based forwarding selects a routing table based on matched packet fields at the ingress point; the selected table must contain a usable destination route.

Question 813

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: On an IS-IS broadcast LAN, an unintended router acts as the designated intermediate system because its interface priority differs from the design. An engineer suggests the shortcut: "Tune OSPF DR priority on that link instead of IS-IS DIS priority." Which critique explains the specific risk of that shortcut?

  1. OSPF election settings are unrelated to IS-IS DIS selection on the LAN.
  2. Documentation cannot extend a protocol metric's encoding or cause routers to use a new metric style.
  3. Mass static redistribution adds scale and maintenance risk instead of using the designed hierarchy.
  4. Static routes conceal incomplete flooding and can become incorrect during legitimate topology changes.

Explanation

Correct Answer

A:

OSPF election settings are unrelated to IS-IS DIS selection on the LAN. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Tune OSPF DR priority on that link instead of IS-IS DIS priority. It fails to resolve the underlying problem that The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design. A sound alternative is the targeted engineering action: Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election.

Incorrect Answers

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 controlled acceptance rehearsal is: Tune OSPF DR priority on that link instead of IS-IS DIS priority. It should be rejected for the narrower reason that OSPF election settings are unrelated to IS-IS DIS selection on the LAN. This distinction matters because The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design.

C:

Mass static redistribution adds scale and maintenance risk instead of using the designed hierarchy. That critique concerns a shortcut from the unrelated IS-IS Level 1 exit default case. The shortcut actually proposed in this controlled acceptance rehearsal is: Tune OSPF DR priority on that link instead of IS-IS DIS priority. It should be rejected for the narrower reason that OSPF election settings are unrelated to IS-IS DIS selection on the LAN. This distinction matters because The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design.

D:

Static routes conceal incomplete flooding and can become incorrect during legitimate topology changes. That critique concerns a shortcut from the unrelated IS-IS LSP lifetime anomaly case. The shortcut actually proposed in this controlled acceptance rehearsal is: Tune OSPF DR priority on that link instead of IS-IS DIS priority. It should be rejected for the narrower reason that OSPF election settings are unrelated to IS-IS DIS selection on the LAN. This distinction matters because The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design.

Question 814

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. An engineer suggests the shortcut: "Force rapid repeated role changes without checking upstream readiness." Which critique explains the specific risk of that shortcut?

  1. Aggressive preemption repeats the same transient blackhole while the upstream path remains unready.
  2. A gateway-election priority has no role in preserving the chassis routing protocol state across RE change.
  3. LAG link redundancy cannot substitute for backup RE routing protocol state synchronization.
  4. Peer implementations and configuration differ; lack of helper cooperation can invalidate preserved-routing expectations.

Explanation

Correct Answer

A:

Aggressive preemption repeats the same transient blackhole while the upstream path remains unready. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Force rapid repeated role changes without checking upstream readiness. It fails to resolve the underlying problem that VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic. A sound alternative is the targeted engineering action: Tune supported preemption timing or tracking against actual upstream readiness so role recovery follows path health.

Incorrect Answers

B:

A gateway-election priority has no role in preserving the chassis routing protocol state across RE change. That critique concerns a shortcut from the unrelated GRES forwarding versus routing continuity case. The shortcut actually proposed in this controlled acceptance rehearsal is: Force rapid repeated role changes without checking upstream readiness. It should be rejected for the narrower reason that Aggressive preemption repeats the same transient blackhole while the upstream path remains unready. This distinction matters because VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic.

C:

LAG link redundancy cannot substitute for backup RE routing protocol state synchronization. That critique concerns a shortcut from the unrelated NSR backup routing synchronization case. The shortcut actually proposed in this controlled acceptance rehearsal is: Force rapid repeated role changes without checking upstream readiness. It should be rejected for the narrower reason that Aggressive preemption repeats the same transient blackhole while the upstream path remains unready. This distinction matters because VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic.

D:

Peer implementations and configuration differ; lack of helper cooperation can invalidate preserved-routing expectations. That critique concerns a shortcut from the unrelated Graceful restart helper expectations case. The shortcut actually proposed in this controlled acceptance rehearsal is: Force rapid repeated role changes without checking upstream readiness. It should be rejected for the narrower reason that Aggressive preemption repeats the same transient blackhole while the upstream path remains unready. This distinction matters because VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic.

Question 815

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. An engineer suggests the shortcut: "Apply the same MED to routes sent to an unrelated external neighbor." Which critique explains the specific risk of that shortcut?

  1. MED is normally used to influence inbound choice by neighbors, not internal egress preference across the local AS.
  2. Remote-side policy is outside local control and does not enforce an explicit receiving security boundary.
  3. Interface IPv6 addressing alone does not authorize or exchange BGP inet6 unicast NLRI.
  4. Suppressing logs hides liveness evidence and cannot repair lost control traffic or poorly chosen timers.

Explanation

Correct Answer

A:

MED is normally used to influence inbound choice by neighbors, not internal egress preference across the local AS. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Apply the same MED to routes sent to an unrelated external neighbor. It fails to resolve the underlying problem that Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility. A sound alternative is the targeted engineering action: Use a controlled import policy to assign the desired BGP local preference to the selected exit paths.

Incorrect Answers

B:

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 controlled acceptance rehearsal is: Apply the same MED to routes sent to an unrelated external neighbor. It should be rejected for the narrower reason that MED is normally used to influence inbound choice by neighbors, not internal egress preference across the local AS. This distinction matters because Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility.

C:

Interface IPv6 addressing alone does not authorize or exchange BGP inet6 unicast NLRI. That critique concerns a shortcut from the unrelated BGP IPv6 family inactive case. The shortcut actually proposed in this controlled acceptance rehearsal is: Apply the same MED to routes sent to an unrelated external neighbor. It should be rejected for the narrower reason that MED is normally used to influence inbound choice by neighbors, not internal egress preference across the local AS. This distinction matters because Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility.

D:

Suppressing logs hides liveness evidence and cannot repair lost control traffic or poorly chosen timers. That critique concerns a shortcut from the unrelated BGP peer flap from mismatched hold timers case. The shortcut actually proposed in this controlled acceptance rehearsal is: Apply the same MED to routes sent to an unrelated external neighbor. It should be rejected for the narrower reason that MED is normally used to influence inbound choice by neighbors, not internal egress preference across the local AS. This distinction matters because Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility.

Question 816

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. An engineer suggests the shortcut: "Increase BGP hold time on a different routing process." Which critique explains the specific risk of that shortcut?

  1. Router-ID identity is not an OSPF path-cost control knob.
  2. BGP keepalive changes do not resolve an OSPF interface timer mismatch.
  3. A process reset can temporarily restart negotiation but leaves the same incompatibility in place.
  4. Blanket redistribution can expose management and unrelated customer networks and create routing instability.

Explanation

Correct Answer

B:

BGP keepalive changes do not resolve an OSPF interface timer mismatch. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Increase BGP hold time on a different routing process. It fails to resolve the underlying problem that OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance. A sound alternative is the targeted engineering action: Align the hello and dead intervals on both OSPF interfaces and confirm stable neighbor state.

Incorrect Answers

A:

Router-ID identity is not an OSPF path-cost control knob. That critique concerns a shortcut from the unrelated OSPF metric path preference case. The shortcut actually proposed in this controlled acceptance rehearsal is: Increase BGP hold time on a different routing process. It should be rejected for the narrower reason that BGP keepalive changes do not resolve an OSPF interface timer mismatch. This distinction matters because OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance.

C:

A process reset can temporarily restart negotiation but leaves the same incompatibility in place. That critique concerns a shortcut from the unrelated OSPF MTU ExStart stall case. The shortcut actually proposed in this controlled acceptance rehearsal is: Increase BGP hold time on a different routing process. It should be rejected for the narrower reason that BGP keepalive changes do not resolve an OSPF interface timer mismatch. This distinction matters because OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance.

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 controlled acceptance rehearsal is: Increase BGP hold time on a different routing process. It should be rejected for the narrower reason that BGP keepalive changes do not resolve an OSPF interface timer mismatch. This distinction matters because OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance.

Question 817

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. An engineer suggests the shortcut: "Increase a counter without changing the overmatching term." Which critique explains the specific risk of that shortcut?

  1. Administrative descriptions and physical speeds do not establish equal routing cost or multipath eligibility.
  2. Forcing packets of one flow onto different paths can reorder packets and harm transport performance.
  3. Physical link-up does not establish downstream forwarding correctness beyond the adjacent hop.
  4. Changing accounting counters does not change first-match classification or forwarding decisions.

Explanation

Correct Answer

D:

Changing accounting counters does not change first-match classification or forwarding decisions. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Increase a counter without changing the overmatching term. It fails to resolve the underlying problem that Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. A sound alternative is the targeted engineering action: Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path.

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 controlled acceptance rehearsal is: Increase a counter without changing the overmatching term. It should be rejected for the narrower reason that Changing accounting counters does not change first-match classification or forwarding decisions. This distinction matters because Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules.

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 controlled acceptance rehearsal is: Increase a counter without changing the overmatching term. It should be rejected for the narrower reason that Changing accounting counters does not change first-match classification or forwarding decisions. This distinction matters because Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules.

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 controlled acceptance rehearsal is: Increase a counter without changing the overmatching term. It should be rejected for the narrower reason that Changing accounting counters does not change first-match classification or forwarding decisions. This distinction matters because Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules.

Question 818

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. 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?

  1. PHP is a normal label disposition behavior and not evidence that the entire LSP should be removed.
  2. Packet size settings cannot create capacity for an RSVP admission request.
  3. Suppressing alarms cannot provide a precomputed alternate label-switched route.
  4. Renumbering a destination node SID does not inherently specify a new intermediate route sequence.

Explanation

Correct Answer

D:

Renumbering a destination node SID does not inherently specify a new intermediate route sequence. In this controlled acceptance rehearsal 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

A:

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 controlled acceptance rehearsal 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.

B:

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 controlled acceptance rehearsal 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:

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 controlled acceptance rehearsal 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 819

During a controlled acceptance rehearsal of the same defect on a separate test network, 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?

  1. Circular resolution sends the tunnel's transport traffic back into the overlay it depends upon.
  2. Larger packets increase the encapsulation MTU violation and do not solve delivery.
  3. Changing inner routing parameters does not repair an incorrectly addressed outer GRE encapsulation path.
  4. Encapsulation hides protocol framing but provides no cryptographic confidentiality or integrity against an observer.

Explanation

Correct Answer

C:

Changing inner routing parameters does not repair an incorrectly addressed outer GRE encapsulation path. In this controlled acceptance rehearsal 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:

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 controlled acceptance rehearsal 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:

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 controlled acceptance rehearsal 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:

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 controlled acceptance rehearsal 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 820

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. An engineer suggests the shortcut: "Configure only an RSVP bandwidth request without addressing missing SR segment information." Which critique explains the specific risk of that shortcut?

  1. RSVP reservable bandwidth is independent of whether the source has a valid SR-MPLS SID mapping.
  2. PHP is a normal label disposition behavior and not evidence that the entire LSP should be removed.
  3. Packet size settings cannot create capacity for an RSVP admission request.
  4. Suppressing alarms cannot provide a precomputed alternate label-switched route.

Explanation

Correct Answer

A:

RSVP reservable bandwidth is independent of whether the source has a valid SR-MPLS SID mapping. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Configure only an RSVP bandwidth request without addressing missing SR segment information. It fails to resolve the underlying problem that SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels. A sound alternative is the targeted engineering action: Verify the intended node or prefix SID advertisement in the participating IGP and the label allocation on the source and transit routers.

Incorrect Answers

B:

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 controlled acceptance rehearsal is: Configure only an RSVP bandwidth request without addressing missing SR segment information. It should be rejected for the narrower reason that RSVP reservable bandwidth is independent of whether the source has a valid SR-MPLS SID mapping. This distinction matters because SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels.

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 controlled acceptance rehearsal is: Configure only an RSVP bandwidth request without addressing missing SR segment information. It should be rejected for the narrower reason that RSVP reservable bandwidth is independent of whether the source has a valid SR-MPLS SID mapping. This distinction matters because SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels.

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 controlled acceptance rehearsal is: Configure only an RSVP bandwidth request without addressing missing SR segment information. It should be rejected for the narrower reason that RSVP reservable bandwidth is independent of whether the source has a valid SR-MPLS SID mapping. This distinction matters because SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels.


Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests

Purchase Individually

JN0-364 Premium File

Premium File
JN0-364 Premium File
69 Q&A
$76.99$69.99

Site Search:

 

VISA, MasterCard, AmericanExpress, UnionPay

SPECIAL OFFER: GET 10% OFF

ExamCollection Premium

ExamCollection Premium Files

Pass your Exam with ExamCollection's PREMIUM files!

  • ExamCollection Certified Safe Files
  • Guaranteed to have ACTUAL Exam Questions
  • Up-to-Date Exam Study Material - Verified by Experts
  • Instant Downloads
Enter Your Email Address to Receive Your 10% Off Discount Code
A Confirmation Link will be sent to this email address to verify your login
We value your privacy. We will not rent or sell your email address

SPECIAL OFFER: GET 10% OFF

Use Discount Code:

MIN10OFF

A confirmation link was sent to your e-mail.
Please check your mailbox for a message from support@examcollection.com and follow the directions.

Next

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

Simply submit your e-mail address below to get started with our interactive software demo of your free trial.

Free Demo Limits: In the demo version you will be able to access only first 5 questions from exam.