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 88

Question 870

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. An engineer suggests the shortcut: "Add a permanent static route for every intermittent IS-IS destination." Which critique explains the specific risk of that shortcut?

  1. OSPF election settings are unrelated to IS-IS DIS selection on the LAN.
  2. Mass static redistribution adds scale and maintenance risk instead of using the designed hierarchy.
  3. Premature transit eligibility can blackhole traffic while the node has incomplete routing state.
  4. Static routes conceal incomplete flooding and can become incorrect during legitimate topology changes.

Explanation

Correct Answer

D:

Static routes conceal incomplete flooding and can become incorrect during legitimate topology changes. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Add a permanent static route for every intermittent IS-IS destination. It fails to resolve the underlying problem that IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB. A sound alternative is the targeted engineering action: Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information.

Incorrect Answers

A:

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 controlled acceptance rehearsal is: Add a permanent static route for every intermittent IS-IS destination. It should be rejected for the narrower reason that Static routes conceal incomplete flooding and can become incorrect during legitimate topology changes. This distinction matters because IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB.

B:

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: Add a permanent static route for every intermittent IS-IS destination. It should be rejected for the narrower reason that Static routes conceal incomplete flooding and can become incorrect during legitimate topology changes. This distinction matters because IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB.

C:

Premature transit eligibility can blackhole traffic while the node has incomplete routing state. That critique concerns a shortcut from the unrelated IS-IS overload-state recovery case. The shortcut actually proposed in this controlled acceptance rehearsal is: Add a permanent static route for every intermittent IS-IS destination. It should be rejected for the narrower reason that Static routes conceal incomplete flooding and can become incorrect during legitimate topology changes. This distinction matters because IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB.

Question 871

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A remote eBGP session must cross an intervening router but was configured as directly connected, so it fails even though both endpoints are routable. An engineer suggests the shortcut: "Enable multipath forwarding in inet.0 without changing the peering transport assumptions." Which critique explains the specific risk of that shortcut?

  1. ECMP settings do not allow an eBGP session to cross an intermediate hop when multihop is missing.
  2. Router IDs are late tie-breakers and duplicating them cannot replace proper MED comparison or policy.
  3. Remote-side policy is outside local control and does not enforce an explicit receiving security boundary.
  4. MED is normally used to influence inbound choice by neighbors, not internal egress preference across the local AS.

Explanation

Correct Answer

A:

ECMP settings do not allow an eBGP session to cross an intermediate hop when multihop is missing. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Enable multipath forwarding in inet.0 without changing the peering transport assumptions. It fails to resolve the underlying problem that An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers. A sound alternative is the targeted engineering action: Configure an approved eBGP multihop arrangement with suitable TTL and reachable peer addresses at both ends.

Incorrect Answers

B:

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 controlled acceptance rehearsal is: Enable multipath forwarding in inet.0 without changing the peering transport assumptions. It should be rejected for the narrower reason that ECMP settings do not allow an eBGP session to cross an intermediate hop when multihop is missing. This distinction matters because An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers.

C:

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: Enable multipath forwarding in inet.0 without changing the peering transport assumptions. It should be rejected for the narrower reason that ECMP settings do not allow an eBGP session to cross an intermediate hop when multihop is missing. This distinction matters because An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers.

D:

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 controlled acceptance rehearsal is: Enable multipath forwarding in inet.0 without changing the peering transport assumptions. It should be rejected for the narrower reason that ECMP settings do not allow an eBGP session to cross an intermediate hop when multihop is missing. This distinction matters because An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers.

Question 872

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. An engineer suggests the shortcut: "Increase the OSPF reference bandwidth without enabling LDP on the missing interface." Which critique explains the specific risk of that shortcut?

  1. OSPF metric calculations cannot cause LDP to participate on an interface where it is not configured.
  2. PHP is a normal label disposition behavior and not evidence that the entire LSP should be removed.
  3. IP TTL does not control implicit-null versus explicit-null label disposition.
  4. LDP discovery on an unrelated peer does not satisfy a broken RSVP explicit-hop constraint.

Explanation

Correct Answer

A:

OSPF metric calculations cannot cause LDP to participate on an interface where it is not configured. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Increase the OSPF reference bandwidth without enabling LDP on the missing interface. It fails to resolve the underlying problem that LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation. A sound alternative is the targeted engineering action: Enable and validate LDP on the intended interfaces that share IGP reachability with participating neighbors.

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: Increase the OSPF reference bandwidth without enabling LDP on the missing interface. It should be rejected for the narrower reason that OSPF metric calculations cannot cause LDP to participate on an interface where it is not configured. This distinction matters because LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation.

C:

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: Increase the OSPF reference bandwidth without enabling LDP on the missing interface. It should be rejected for the narrower reason that OSPF metric calculations cannot cause LDP to participate on an interface where it is not configured. This distinction matters because LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation.

D:

LDP discovery on an unrelated peer does not satisfy a broken RSVP explicit-hop constraint. That critique concerns a shortcut from the unrelated RSVP-TE constrained path missing case. The shortcut actually proposed in this controlled acceptance rehearsal is: Increase the OSPF reference bandwidth without enabling LDP on the missing interface. It should be rejected for the narrower reason that OSPF metric calculations cannot cause LDP to participate on an interface where it is not configured. This distinction matters because LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation.

Question 873

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. An engineer suggests the shortcut: "Remove the LAN from every OSPF configuration to stop the Hellos." Which critique explains the specific risk of that shortcut?

  1. A static workaround can mask an unresolved control-plane synchronization problem and fail during another topology change.
  2. Uncontrolled redistribution does not restore the designed OSPF backbone and can create loops or route leaks.
  3. Removing the interface entirely can also remove the necessary prefix advertisement.
  4. Syslog names are not OSPF originator identifiers, so the underlying conflict remains.

Explanation

Correct Answer

C:

Removing the interface entirely can also remove the necessary prefix advertisement. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Remove the LAN from every OSPF configuration to stop the Hellos. It fails to resolve the underlying problem that Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information. A sound alternative is the targeted engineering action: Set the LAN interface passive within the relevant OSPF area while retaining the intended prefix advertisement.

Incorrect Answers

A:

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: Remove the LAN from every OSPF configuration to stop the Hellos. It should be rejected for the narrower reason that Removing the interface entirely can also remove the necessary prefix advertisement. This distinction matters because Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information.

B:

Uncontrolled redistribution does not restore the designed OSPF backbone and can create loops or route leaks. That critique concerns a shortcut from the unrelated OSPF backbone connectivity case. The shortcut actually proposed in this controlled acceptance rehearsal is: Remove the LAN from every OSPF configuration to stop the Hellos. It should be rejected for the narrower reason that Removing the interface entirely can also remove the necessary prefix advertisement. This distinction matters because Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information.

D:

Syslog names are not OSPF originator identifiers, so the underlying conflict remains. That critique concerns a shortcut from the unrelated Duplicate OSPF router identifier case. The shortcut actually proposed in this controlled acceptance rehearsal is: Remove the LAN from every OSPF configuration to stop the Hellos. It should be rejected for the narrower reason that Removing the interface entirely can also remove the necessary prefix advertisement. This distinction matters because Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information.

Question 874

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A customer CE is connected to an access port configured for VLAN 110, while its service should be VLAN 120, and its frames cannot reach the correct broadcast domain. An engineer suggests the shortcut: "Add an unrelated static route to the routing table without correcting the access VLAN." 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. Layer 3 route changes cannot change the Layer 2 VLAN assignment of untagged frames.
  3. An aging change cannot prevent contradictory source-MAC observations on multiple ports.
  4. Opening all VLANs expands the Layer 2 service boundary rather than fixing the specific missing membership.

Explanation

Correct Answer

B:

Layer 3 route changes cannot change the Layer 2 VLAN assignment of untagged frames. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Add an unrelated static route to the routing table without correcting the access VLAN. It fails to resolve the underlying problem that An access port classifies untagged received frames into its configured VLAN, which determines Layer 2 forwarding membership. A sound alternative is the targeted engineering action: Move the access port to the approved VLAN and verify logical interface membership and learning.

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: Add an unrelated static route to the routing table without correcting the access VLAN. It should be rejected for the narrower reason that Layer 3 route changes cannot change the Layer 2 VLAN assignment of untagged frames. This distinction matters because An access port classifies untagged received frames into its configured VLAN, which determines Layer 2 forwarding membership.

C:

An aging change cannot prevent contradictory source-MAC observations on multiple ports. That critique concerns a shortcut from the unrelated MAC move instability case. The shortcut actually proposed in this controlled acceptance rehearsal is: Add an unrelated static route to the routing table without correcting the access VLAN. It should be rejected for the narrower reason that Layer 3 route changes cannot change the Layer 2 VLAN assignment of untagged frames. This distinction matters because An access port classifies untagged received frames into its configured VLAN, which determines Layer 2 forwarding membership.

D:

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: Add an unrelated static route to the routing table without correcting the access VLAN. It should be rejected for the narrower reason that Layer 3 route changes cannot change the Layer 2 VLAN assignment of untagged frames. This distinction matters because An access port classifies untagged received frames into its configured VLAN, which determines Layer 2 forwarding membership.

Question 875

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An eBGP peering is established for inet unicast but the provider cannot receive approved IPv6 prefixes because the IPv6 address family is absent. An engineer suggests the shortcut: "Raise IPv4 local preference but do not configure IPv6 BGP family." Which critique explains the specific risk of that shortcut?

  1. IPv4 path preference cannot create missing IPv6 NLRI negotiation or advertisement.
  2. Blocking needed ICMPv6 breaks IPv6 control mechanisms including Path MTU Discovery.
  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

A:

IPv4 path preference cannot create missing IPv6 NLRI negotiation or advertisement. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Raise IPv4 local preference but do not configure IPv6 BGP family. It fails to resolve the underlying problem that BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange. A sound alternative is the targeted engineering action: Enable and verify the BGP inet6 unicast family with permitted IPv6 export/import policy and resolvable next hops.

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: Raise IPv4 local preference but do not configure IPv6 BGP family. It should be rejected for the narrower reason that IPv4 path preference cannot create missing IPv6 NLRI negotiation or advertisement. This distinction matters because BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange.

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: Raise IPv4 local preference but do not configure IPv6 BGP family. It should be rejected for the narrower reason that IPv4 path preference cannot create missing IPv6 NLRI negotiation or advertisement. This distinction matters because BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange.

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: Raise IPv4 local preference but do not configure IPv6 BGP family. It should be rejected for the narrower reason that IPv4 path preference cannot create missing IPv6 NLRI negotiation or advertisement. This distinction matters because BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange.

Question 876

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. An engineer suggests the shortcut: "Increase the OSPF interface metric to make the priority-zero router electable." Which critique explains the specific risk of that shortcut?

  1. SPF path cost is distinct from the DR election priority; changing cost does not reverse priority-zero ineligibility.
  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. Unilateral removal of authentication does not establish a trusted matching configuration and weakens control-plane protection.

Explanation

Correct Answer

A:

SPF path cost is distinct from the DR election priority; changing cost does not reverse priority-zero ineligibility. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Increase the OSPF interface metric to make the priority-zero router electable. It fails to resolve the underlying problem that OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links. A sound alternative is the targeted engineering action: Set a nonzero eligible interface priority where DR candidacy is intended and re-evaluate election behavior with the network design.

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: Increase the OSPF interface metric to make the priority-zero router electable. It should be rejected for the narrower reason that SPF path cost is distinct from the DR election priority; changing cost does not reverse priority-zero ineligibility. This distinction matters because OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links.

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: Increase the OSPF interface metric to make the priority-zero router electable. It should be rejected for the narrower reason that SPF path cost is distinct from the DR election priority; changing cost does not reverse priority-zero ineligibility. This distinction matters because OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links.

D:

Unilateral removal of authentication does not establish a trusted matching configuration and weakens control-plane protection. That critique concerns a shortcut from the unrelated OSPF authentication key mismatch case. The shortcut actually proposed in this controlled acceptance rehearsal is: Increase the OSPF interface metric to make the priority-zero router electable. It should be rejected for the narrower reason that SPF path cost is distinct from the DR election priority; changing cost does not reverse priority-zero ineligibility. This distinction matters because OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links.

Question 877

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

  1. Blanket redistribution can expose management and unrelated customer networks and create routing instability.
  2. Router-ID identity is not an OSPF path-cost control knob.
  3. Syslog names are not OSPF originator identifiers, so the underlying conflict remains.
  4. Removing the interface entirely can also remove the necessary prefix advertisement.

Explanation

Correct Answer

B:

Router-ID identity is not an OSPF path-cost control knob. In this controlled acceptance rehearsal 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:

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

C:

Syslog names are not OSPF originator identifiers, so the underlying conflict remains. That critique concerns a shortcut from the unrelated Duplicate OSPF router identifier case. The shortcut actually proposed in this controlled acceptance rehearsal 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:

Removing the interface entirely can also remove the necessary prefix advertisement. That critique concerns a shortcut from the unrelated OSPF passive interface case. The shortcut actually proposed in this controlled acceptance rehearsal 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 878

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two routers on an engineered point-to-point interface spend time trying to use an unnecessary broadcast DR election process. An engineer suggests the shortcut: "Increase OSPF broadcast DR priority instead of changing the network type." Which critique explains the specific risk of that shortcut?

  1. Uncontrolled redistribution does not restore the designed OSPF backbone and can create loops or route leaks.
  2. Blanket redistribution can expose management and unrelated customer networks and create routing instability.
  3. DR election priority does not remove a broadcast network-type assumption from a dedicated point-to-point link.
  4. BGP keepalive changes do not resolve an OSPF interface timer mismatch.

Explanation

Correct Answer

C:

DR election priority does not remove a broadcast network-type assumption from a dedicated point-to-point link. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Increase OSPF broadcast DR priority instead of changing the network type. It fails to resolve the underlying problem that OSPF point-to-point network types use one direct adjacency without broadcast-network DR and BDR election. A sound alternative is the targeted engineering action: Set the correct point-to-point OSPF interface type where supported and aligned at both ends.

Incorrect Answers

A:

Uncontrolled redistribution does not restore the designed OSPF backbone and can create loops or route leaks. That critique concerns a shortcut from the unrelated OSPF backbone connectivity case. The shortcut actually proposed in this controlled acceptance rehearsal is: Increase OSPF broadcast DR priority instead of changing the network type. It should be rejected for the narrower reason that DR election priority does not remove a broadcast network-type assumption from a dedicated point-to-point link. This distinction matters because OSPF point-to-point network types use one direct adjacency without broadcast-network DR and BDR election.

B:

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 OSPF broadcast DR priority instead of changing the network type. It should be rejected for the narrower reason that DR election priority does not remove a broadcast network-type assumption from a dedicated point-to-point link. This distinction matters because OSPF point-to-point network types use one direct adjacency without broadcast-network DR and BDR election.

D:

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 controlled acceptance rehearsal is: Increase OSPF broadcast DR priority instead of changing the network type. It should be rejected for the narrower reason that DR election priority does not remove a broadcast network-type assumption from a dedicated point-to-point link. This distinction matters because OSPF point-to-point network types use one direct adjacency without broadcast-network DR and BDR election.

Question 879

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. An engineer suggests the shortcut: "Only increase VRRP priority on an unrelated gateway to preserve routing sessions." Which critique explains the specific risk of that shortcut?

  1. Routing metrics in OSPF do not directly determine VRRP primary election.
  2. A gateway-election priority has no role in preserving the chassis routing protocol state across RE change.
  3. Aggressive preemption repeats the same transient blackhole while the upstream path remains unready.
  4. Unreasonably small intervals can cause false liveness failures and repeated routing churn.

Explanation

Correct Answer

B:

A gateway-election priority has no role in preserving the chassis routing protocol state across RE change. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Only increase VRRP priority on an unrelated gateway to preserve routing sessions. It fails to resolve the underlying problem that GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions. A sound alternative is the targeted engineering action: Use a supported combination of GRES and NSR or appropriate graceful restart to meet the control-plane continuity target.

Incorrect Answers

A:

Routing metrics in OSPF do not directly determine VRRP primary election. That critique concerns a shortcut from the unrelated VRRP master priority failover case. The shortcut actually proposed in this controlled acceptance rehearsal is: Only increase VRRP priority on an unrelated gateway to preserve routing sessions. It should be rejected for the narrower reason that A gateway-election priority has no role in preserving the chassis routing protocol state across RE change. This distinction matters because GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions.

C:

Aggressive preemption repeats the same transient blackhole while the upstream path remains unready. That critique concerns a shortcut from the unrelated VRRP preemption oscillation case. The shortcut actually proposed in this controlled acceptance rehearsal is: Only increase VRRP priority on an unrelated gateway to preserve routing sessions. It should be rejected for the narrower reason that A gateway-election priority has no role in preserving the chassis routing protocol state across RE change. This distinction matters because GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions.

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 controlled acceptance rehearsal is: Only increase VRRP priority on an unrelated gateway to preserve routing sessions. It should be rejected for the narrower reason that A gateway-election priority has no role in preserving the chassis routing protocol state across RE change. This distinction matters because GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions.

Question 880

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two PE routers exchange OSPF Hello packets on the same Ethernet segment but stay Down because one interface belongs to area 0 and the other to area 10. An engineer suggests the shortcut: "Only change the OSPF reference bandwidth on one 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. Reference bandwidth affects metric calculation, not the area ID carried in Hello packets.
  3. Removing the interface entirely can also remove the necessary prefix advertisement.
  4. Router-ID identity is not an OSPF path-cost control knob.

Explanation

Correct Answer

B:

Reference bandwidth affects metric calculation, not the area ID carried in Hello packets. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Only change the OSPF reference bandwidth on one router. It fails to resolve the underlying problem that OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship. A sound alternative is the targeted engineering action: Place both adjacency interfaces into the intended matching OSPF area, then validate neighbor exchange.

Incorrect Answers

A:

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: Only change the OSPF reference bandwidth on one router. It should be rejected for the narrower reason that Reference bandwidth affects metric calculation, not the area ID carried in Hello packets. This distinction matters because OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship.

C:

Removing the interface entirely can also remove the necessary prefix advertisement. That critique concerns a shortcut from the unrelated OSPF passive interface case. The shortcut actually proposed in this controlled acceptance rehearsal is: Only change the OSPF reference bandwidth on one router. It should be rejected for the narrower reason that Reference bandwidth affects metric calculation, not the area ID carried in Hello packets. This distinction matters because OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship.

D:

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: Only change the OSPF reference bandwidth on one router. It should be rejected for the narrower reason that Reference bandwidth affects metric calculation, not the area ID carried in Hello packets. This distinction matters because OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship.


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.