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 85

Question 840

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. An engineer suggests the shortcut: "Watch only local interface carrier and assume the remote service must be operational." Which critique explains the specific risk of that shortcut?

  1. Removing valid specifics would disrupt actual destinations and does not establish a correct summary-fallback design.
  2. Global relaxation hides a routing or addressing error and exposes unrelated prefixes to the same risk.
  3. Hostname changes do not import a route between separate routing information bases.
  4. Physical link-up does not establish downstream forwarding correctness beyond the adjacent hop.

Explanation

Correct Answer

D:

Physical link-up does not establish downstream forwarding correctness beyond the adjacent hop. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Watch only local interface carrier and assume the remote service must be operational. It fails to resolve the underlying problem that A static next hop may appear link-reachable while the remote end-to-end path is unusable, so a tracking mechanism such as BFD can be necessary. A sound alternative is the targeted engineering action: Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure.

Incorrect Answers

A:

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 controlled acceptance rehearsal is: Watch only local interface carrier and assume the remote service must be operational. It should be rejected for the narrower reason that Physical link-up does not establish downstream forwarding correctness beyond the adjacent hop. This distinction matters because A static next hop may appear link-reachable while the remote end-to-end path is unusable, so a tracking mechanism such as BFD can be necessary.

B:

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: Watch only local interface carrier and assume the remote service must be operational. It should be rejected for the narrower reason that Physical link-up does not establish downstream forwarding correctness beyond the adjacent hop. This distinction matters because A static next hop may appear link-reachable while the remote end-to-end path is unusable, so a tracking mechanism such as BFD can be necessary.

C:

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: Watch only local interface carrier and assume the remote service must be operational. It should be rejected for the narrower reason that Physical link-up does not establish downstream forwarding correctness beyond the adjacent hop. This distinction matters because A static next hop may appear link-reachable while the remote end-to-end path is unusable, so a tracking mechanism such as BFD can be necessary.

Question 841

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. An engineer suggests the shortcut: "Enable an export policy that accepts every connected route on the router." Which critique explains the specific risk of that shortcut?

  1. Blanket redistribution can expose management and unrelated customer networks and create routing instability.
  2. Blindly redistributing external information conflicts with the intended stub-area containment model.
  3. Router-ID identity is not an OSPF path-cost control knob.
  4. A static workaround can mask an unresolved control-plane synchronization problem and fail during another topology change.

Explanation

Correct Answer

A:

Blanket redistribution can expose management and unrelated customer networks and create routing instability. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Enable an export policy that accepts every connected route on the router. It fails to resolve the underlying problem that External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements. A sound alternative is the targeted engineering action: Add a tightly scoped OSPF export policy for the intended prefix, preserving loop and source restrictions.

Incorrect Answers

B:

Blindly redistributing external information conflicts with the intended stub-area containment model. That critique concerns a shortcut from the unrelated Stub area external LSA expectation case. The shortcut actually proposed in this controlled acceptance rehearsal is: Enable an export policy that accepts every connected route on the router. It should be rejected for the narrower reason that Blanket redistribution can expose management and unrelated customer networks and create routing instability. This distinction matters because External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements.

C:

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: Enable an export policy that accepts every connected route on the router. It should be rejected for the narrower reason that Blanket redistribution can expose management and unrelated customer networks and create routing instability. This distinction matters because External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements.

D:

A static workaround can mask an unresolved control-plane synchronization problem and fail during another topology change. That critique concerns a shortcut from the unrelated OSPF LSDB discrepancy case. The shortcut actually proposed in this controlled acceptance rehearsal is: Enable an export policy that accepts every connected route on the router. It should be rejected for the narrower reason that Blanket redistribution can expose management and unrelated customer networks and create routing instability. This distinction matters because External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements.

Question 842

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. An engineer suggests the shortcut: "Force an unrelated VLAN trunk membership without fixing the LACP mismatch." Which critique explains the specific risk of that shortcut?

  1. Unreasonably small intervals can cause false liveness failures and repeated routing churn.
  2. VLAN membership does not make incompatible LACP peers join a single forwarding aggregate.
  3. A gateway-election priority has no role in preserving the chassis routing protocol state across RE change.
  4. LAG link redundancy cannot substitute for backup RE routing protocol state synchronization.

Explanation

Correct Answer

B:

VLAN membership does not make incompatible LACP peers join a single forwarding aggregate. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Force an unrelated VLAN trunk membership without fixing the LACP mismatch. It fails to resolve the underlying problem that LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone. A sound alternative is the targeted engineering action: Align the member's LACP configuration with the approved peer aggregated Ethernet group and verify partner negotiation.

Incorrect Answers

A:

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 controlled acceptance rehearsal is: Force an unrelated VLAN trunk membership without fixing the LACP mismatch. It should be rejected for the narrower reason that VLAN membership does not make incompatible LACP peers join a single forwarding aggregate. This distinction matters because LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone.

C:

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 an unrelated VLAN trunk membership without fixing the LACP mismatch. It should be rejected for the narrower reason that VLAN membership does not make incompatible LACP peers join a single forwarding aggregate. This distinction matters because LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone.

D:

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 an unrelated VLAN trunk membership without fixing the LACP mismatch. It should be rejected for the narrower reason that VLAN membership does not make incompatible LACP peers join a single forwarding aggregate. This distinction matters because LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone.

Question 843

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

  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. LDP discovery on an unrelated peer does not satisfy a broken RSVP explicit-hop constraint.
  4. Additional network-layer routes cannot substitute for the required LDP session transport.

Explanation

Correct Answer

C:

LDP discovery on an unrelated peer does not satisfy a broken RSVP explicit-hop constraint. In this controlled acceptance rehearsal 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:

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: 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:

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: 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.

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

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

  1. Encapsulation hides protocol framing but provides no cryptographic confidentiality or integrity against an observer.
  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. Circular resolution sends the tunnel's transport traffic back into the overlay it depends upon.

Explanation

Correct Answer

A:

Encapsulation hides protocol framing but provides no cryptographic confidentiality or integrity against an observer. In this controlled acceptance rehearsal 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:

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: 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:

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

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: 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.

Question 845

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. An engineer suggests the shortcut: "Raise the physical MTU on a link while leaving insufficient reservable bandwidth." Which critique explains the specific risk of that shortcut?

  1. Packet size settings cannot create capacity for an RSVP admission request.
  2. Session establishment says nothing about whether an individual FEC has a usable label mapping.
  3. IP addressing does not repair the label operation needed at a transit LSR.
  4. PHP is a normal label disposition behavior and not evidence that the entire LSP should be removed.

Explanation

Correct Answer

A:

Packet size settings cannot create capacity for an RSVP admission request. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Raise the physical MTU on a link while leaving insufficient reservable bandwidth. It fails to resolve the underlying problem that RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability. A sound alternative is the targeted engineering action: Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth.

Incorrect Answers

B:

Session establishment says nothing about whether an individual FEC has a usable label mapping. That critique concerns a shortcut from the unrelated Missing LDP FEC label mapping case. The shortcut actually proposed in this controlled acceptance rehearsal is: Raise the physical MTU on a link while leaving insufficient reservable bandwidth. It should be rejected for the narrower reason that Packet size settings cannot create capacity for an RSVP admission request. This distinction matters because RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability.

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 controlled acceptance rehearsal is: Raise the physical MTU on a link while leaving insufficient reservable bandwidth. It should be rejected for the narrower reason that Packet size settings cannot create capacity for an RSVP admission request. This distinction matters because RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability.

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 controlled acceptance rehearsal is: Raise the physical MTU on a link while leaving insufficient reservable bandwidth. It should be rejected for the narrower reason that Packet size settings cannot create capacity for an RSVP admission request. This distinction matters because RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability.

Question 846

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. An engineer suggests the shortcut: "Use the GRE tunnel itself as the only path to reach its outer destination." Which critique explains the specific risk of that shortcut?

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

Explanation

Correct Answer

B:

Circular resolution sends the tunnel's transport traffic back into the overlay it depends upon. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Use the GRE tunnel itself as the only path to reach its outer destination. It fails to resolve the underlying problem that GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable. A sound alternative is the targeted engineering action: Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself.

Incorrect Answers

A:

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 controlled acceptance rehearsal is: Use the GRE tunnel itself as the only path to reach its outer destination. It should be rejected for the narrower reason that Circular resolution sends the tunnel's transport traffic back into the overlay it depends upon. This distinction matters because GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable.

C:

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: Use the GRE tunnel itself as the only path to reach its outer destination. It should be rejected for the narrower reason that Circular resolution sends the tunnel's transport traffic back into the overlay it depends upon. This distinction matters because GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable.

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 controlled acceptance rehearsal is: Use the GRE tunnel itself as the only path to reach its outer destination. It should be rejected for the narrower reason that Circular resolution sends the tunnel's transport traffic back into the overlay it depends upon. This distinction matters because GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable.

Question 847

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. An engineer suggests the shortcut: "Disable LSP alarms while keeping the original unprotected 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. IP TTL does not control implicit-null versus explicit-null label disposition.
  3. Suppressing alarms cannot provide a precomputed alternate label-switched route.
  4. RSVP reservable bandwidth is independent of whether the source has a valid SR-MPLS SID mapping.

Explanation

Correct Answer

C:

Suppressing alarms cannot provide a precomputed alternate label-switched route. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Disable LSP alarms while keeping the original unprotected path. It fails to resolve the underlying problem that RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost. A sound alternative is the targeted engineering action: Configure and validate supported RSVP link protection with a viable bypass for the affected protected link.

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: Disable LSP alarms while keeping the original unprotected path. It should be rejected for the narrower reason that Suppressing alarms cannot provide a precomputed alternate label-switched route. This distinction matters because RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost.

B:

IP TTL does not control implicit-null versus explicit-null label disposition. That critique concerns a shortcut from the unrelated Explicit-null forwarding case. The shortcut actually proposed in this controlled acceptance rehearsal is: Disable LSP alarms while keeping the original unprotected path. It should be rejected for the narrower reason that Suppressing alarms cannot provide a precomputed alternate label-switched route. This distinction matters because RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost.

D:

RSVP reservable bandwidth is independent of whether the source has a valid SR-MPLS SID mapping. That critique concerns a shortcut from the unrelated Segment routing SID advertisement case. The shortcut actually proposed in this controlled acceptance rehearsal is: Disable LSP alarms while keeping the original unprotected path. It should be rejected for the narrower reason that Suppressing alarms cannot provide a precomputed alternate label-switched route. This distinction matters because RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost.

Question 848

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. An engineer suggests the shortcut: "Delete all more-specific routes so the aggregate is the only route." Which critique explains the specific risk of that shortcut?

  1. An unconditional default masks missing prerequisites and may direct traffic into an unintended path.
  2. Global relaxation hides a routing or addressing error and exposes unrelated prefixes to the same risk.
  3. Physical link-up does not establish downstream forwarding correctness beyond the adjacent hop.
  4. Removing valid specifics would disrupt actual destinations and does not establish a correct summary-fallback design.

Explanation

Correct Answer

D:

Removing valid specifics would disrupt actual destinations and does not establish a correct summary-fallback design. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Delete all more-specific routes so the aggregate is the only route. It fails to resolve the underlying problem that An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match. A sound alternative is the targeted engineering action: Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination.

Incorrect Answers

A:

An unconditional default masks missing prerequisites and may direct traffic into an unintended path. That critique concerns a shortcut from the unrelated Generated default route prerequisite case. The shortcut actually proposed in this controlled acceptance rehearsal is: Delete all more-specific routes so the aggregate is the only route. It should be rejected for the narrower reason that Removing valid specifics would disrupt actual destinations and does not establish a correct summary-fallback design. This distinction matters because An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match.

B:

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: Delete all more-specific routes so the aggregate is the only route. It should be rejected for the narrower reason that Removing valid specifics would disrupt actual destinations and does not establish a correct summary-fallback design. This distinction matters because An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match.

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: Delete all more-specific routes so the aggregate is the only route. It should be rejected for the narrower reason that Removing valid specifics would disrupt actual destinations and does not establish a correct summary-fallback design. This distinction matters because An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match.

Question 849

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. An engineer suggests the shortcut: "Add an arbitrary IPv4 gateway address to the inet.0 table only." Which critique explains the specific risk of that shortcut?

  1. An IPv4 route cannot supply the missing IPv6 link-local scope or next-hop selection.
  2. Blocking needed ICMPv6 breaks IPv6 control mechanisms including Path MTU Discovery.
  3. IPv4 path preference cannot create missing IPv6 NLRI negotiation or advertisement.
  4. Changing IPv4 OSPFv2 parameters does not establish an independent OSPFv3 adjacency.

Explanation

Correct Answer

A:

An IPv4 route cannot supply the missing IPv6 link-local scope or next-hop selection. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Add an arbitrary IPv4 gateway address to the inet.0 table only. It fails to resolve the underlying problem that An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop. A sound alternative is the targeted engineering action: Specify the intended outgoing interface together with the link-local next hop and confirm the route is usable.

Incorrect Answers

B:

Blocking needed ICMPv6 breaks IPv6 control mechanisms including Path MTU Discovery. That critique concerns a shortcut from the unrelated ICMPv6 packet-too-big handling case. The shortcut actually proposed in this controlled acceptance rehearsal is: Add an arbitrary IPv4 gateway address to the inet.0 table only. It should be rejected for the narrower reason that An IPv4 route cannot supply the missing IPv6 link-local scope or next-hop selection. This distinction matters because An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop.

C:

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: Add an arbitrary IPv4 gateway address to the inet.0 table only. It should be rejected for the narrower reason that An IPv4 route cannot supply the missing IPv6 link-local scope or next-hop selection. This distinction matters because An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop.

D:

Changing IPv4 OSPFv2 parameters does not establish an independent OSPFv3 adjacency. That critique concerns a shortcut from the unrelated OSPFv3 neighbor uses link-local case. The shortcut actually proposed in this controlled acceptance rehearsal is: Add an arbitrary IPv4 gateway address to the inet.0 table only. It should be rejected for the narrower reason that An IPv4 route cannot supply the missing IPv6 link-local scope or next-hop selection. This distinction matters because An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop.

Question 850

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. An engineer suggests the shortcut: "Rewrite the customer inner VLAN identifiers to mask the mismatched service outer tag." Which critique explains the specific risk of that shortcut?

  1. A duplicate name does not move frames into the intended instance and can increase configuration confusion.
  2. Opening all VLANs expands the Layer 2 service boundary rather than fixing the specific missing membership.
  3. Changing customer tags can disrupt their VLAN separation and leaves the provider's outer-tag contract unresolved.
  4. Loopback addressing does not determine how untagged trunk traffic is mapped into VLANs.

Explanation

Correct Answer

C:

Changing customer tags can disrupt their VLAN separation and leaves the provider's outer-tag contract unresolved. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Rewrite the customer inner VLAN identifiers to mask the mismatched service outer tag. It fails to resolve the underlying problem that Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags. A sound alternative is the targeted engineering action: Align service-provider outer VLAN tags and preserve the customer's intended inner VLAN identifiers through the Q-in-Q handoff.

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 controlled acceptance rehearsal is: Rewrite the customer inner VLAN identifiers to mask the mismatched service outer tag. It should be rejected for the narrower reason that Changing customer tags can disrupt their VLAN separation and leaves the provider's outer-tag contract unresolved. This distinction matters because Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags.

B:

Opening all VLANs expands the Layer 2 service boundary rather than fixing the specific missing membership. That critique concerns a shortcut from the unrelated Trunk allowed VLAN omission case. The shortcut actually proposed in this controlled acceptance rehearsal is: Rewrite the customer inner VLAN identifiers to mask the mismatched service outer tag. It should be rejected for the narrower reason that Changing customer tags can disrupt their VLAN separation and leaves the provider's outer-tag contract unresolved. This distinction matters because Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags.

D:

Loopback addressing does not determine how untagged trunk traffic is mapped into VLANs. That critique concerns a shortcut from the unrelated Native VLAN mismatch case. The shortcut actually proposed in this controlled acceptance rehearsal is: Rewrite the customer inner VLAN identifiers to mask the mismatched service outer tag. It should be rejected for the narrower reason that Changing customer tags can disrupt their VLAN separation and leaves the provider's outer-tag contract unresolved. This distinction matters because Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags.


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.