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 35

Question 340

During production incident triage, engineers observe: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. An engineer suggests the shortcut: "Disable authentication permanently on one neighbor to force the adjacency up." Which critique explains the specific risk of that shortcut?

  1. Blindly redistributing external information conflicts with the intended stub-area containment model.
  2. SPF path cost is distinct from the DR election priority; changing cost does not reverse priority-zero ineligibility.
  3. Unilateral removal of authentication does not establish a trusted matching configuration and weakens control-plane protection.
  4. DR election priority does not remove a broadcast network-type assumption from a dedicated point-to-point link.

Explanation

Correct Answer

C:

Unilateral removal of authentication does not establish a trusted matching configuration and weakens control-plane protection. In this live production incident the shortcut was explicitly proposed as: Disable authentication permanently on one neighbor to force the adjacency up. It fails to resolve the underlying problem that OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree. A sound alternative is the targeted engineering action: Coordinate compatible OSPFv2 authentication method, key identifier and active secret on both peers before cutover.

Incorrect Answers

A:

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 live production incident is: Disable authentication permanently on one neighbor to force the adjacency up. It should be rejected for the narrower reason that Unilateral removal of authentication does not establish a trusted matching configuration and weakens control-plane protection. This distinction matters because OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree.

B:

SPF path cost is distinct from the DR election priority; changing cost does not reverse priority-zero ineligibility. That critique concerns a shortcut from the unrelated DR priority zero misconception case. The shortcut actually proposed in this live production incident is: Disable authentication permanently on one neighbor to force the adjacency up. It should be rejected for the narrower reason that Unilateral removal of authentication does not establish a trusted matching configuration and weakens control-plane protection. This distinction matters because OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree.

D:

DR election priority does not remove a broadcast network-type assumption from a dedicated point-to-point link. That critique concerns a shortcut from the unrelated Point-to-point OSPF network type case. The shortcut actually proposed in this live production incident is: Disable authentication permanently on one neighbor to force the adjacency up. It should be rejected for the narrower reason that Unilateral removal of authentication does not establish a trusted matching configuration and weakens control-plane protection. This distinction matters because OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree.

Question 341

During production incident triage, engineers observe: Two IPv6-only customer islands must communicate across an IPv4 underlay, but no tunnel endpoints have been configured for their routed IPv6 traffic. An engineer suggests the shortcut: "Announce only an IPv6 static route without providing a working cross-underlay tunnel." 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. Changing IPv4 OSPFv2 parameters does not establish an independent OSPFv3 adjacency.
  3. IPv6 route configuration alone cannot deliver IPv6 payload across an IPv4-only segment with no encapsulation path.
  4. IPv4 path preference cannot create missing IPv6 NLRI negotiation or advertisement.

Explanation

Correct Answer

C:

IPv6 route configuration alone cannot deliver IPv6 payload across an IPv4-only segment with no encapsulation path. In this live production incident the shortcut was explicitly proposed as: Announce only an IPv6 static route without providing a working cross-underlay tunnel. It fails to resolve the underlying problem that An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct. A sound alternative is the targeted engineering action: Configure a supported IPv6-over-IPv4 tunnel with reachable outer IPv4 endpoints and correct IPv6 routing into the tunnel.

Incorrect Answers

A:

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 live production incident is: Announce only an IPv6 static route without providing a working cross-underlay tunnel. It should be rejected for the narrower reason that IPv6 route configuration alone cannot deliver IPv6 payload across an IPv4-only segment with no encapsulation path. This distinction matters because An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct.

B:

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 live production incident is: Announce only an IPv6 static route without providing a working cross-underlay tunnel. It should be rejected for the narrower reason that IPv6 route configuration alone cannot deliver IPv6 payload across an IPv4-only segment with no encapsulation path. This distinction matters because An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct.

D:

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 live production incident is: Announce only an IPv6 static route without providing a working cross-underlay tunnel. It should be rejected for the narrower reason that IPv6 route configuration alone cannot deliver IPv6 payload across an IPv4-only segment with no encapsulation path. This distinction matters because An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct.

Question 342

During production incident triage, 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. Layer 3 route changes cannot change the Layer 2 VLAN assignment of untagged frames.
  2. Loopback addressing does not determine how untagged trunk traffic is mapped into VLANs.
  3. Removing MAC learning generally prolongs unknown-destination flooding rather than creating targeted forwarding.
  4. A duplicate name does not move frames into the intended instance and can increase configuration confusion.

Explanation

Correct Answer

A:

Layer 3 route changes cannot change the Layer 2 VLAN assignment of untagged frames. In this live production incident 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

B:

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 live production incident 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:

Removing MAC learning generally prolongs unknown-destination flooding rather than creating targeted forwarding. That critique concerns a shortcut from the unrelated Unknown unicast flooding behavior case. The shortcut actually proposed in this live production incident 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:

A duplicate name does not move frames into the intended instance and can increase configuration confusion. That critique concerns a shortcut from the unrelated Virtual switch instance membership case. The shortcut actually proposed in this live production incident is: 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 343

During production incident triage, engineers observe: An area border router carries area 20 routes, but traffic between area 20 and area 30 is missing because backbone attachment is broken. An engineer suggests the shortcut: "Redistribute every OSPF route into BGP to conceal the broken area hierarchy." 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. Removing the interface entirely can also remove the necessary prefix advertisement.
  3. DR election priority does not remove a broadcast network-type assumption from a dedicated point-to-point link.
  4. Unilateral removal of authentication does not establish a trusted matching configuration and weakens control-plane protection.

Explanation

Correct Answer

A:

Uncontrolled redistribution does not restore the designed OSPF backbone and can create loops or route leaks. In this live production incident the shortcut was explicitly proposed as: Redistribute every OSPF route into BGP to conceal the broken area hierarchy. It fails to resolve the underlying problem that Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers. A sound alternative is the targeted engineering action: Restore the intended area 0 backbone connectivity for the affected ABRs and verify inter-area summaries.

Incorrect Answers

B:

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 live production incident is: Redistribute every OSPF route into BGP to conceal the broken area hierarchy. It should be rejected for the narrower reason that Uncontrolled redistribution does not restore the designed OSPF backbone and can create loops or route leaks. This distinction matters because Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers.

C:

DR election priority does not remove a broadcast network-type assumption from a dedicated point-to-point link. That critique concerns a shortcut from the unrelated Point-to-point OSPF network type case. The shortcut actually proposed in this live production incident is: Redistribute every OSPF route into BGP to conceal the broken area hierarchy. It should be rejected for the narrower reason that Uncontrolled redistribution does not restore the designed OSPF backbone and can create loops or route leaks. This distinction matters because Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers.

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 live production incident is: Redistribute every OSPF route into BGP to conceal the broken area hierarchy. It should be rejected for the narrower reason that Uncontrolled redistribution does not restore the designed OSPF backbone and can create loops or route leaks. This distinction matters because Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers.

Question 344

During production incident triage, 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. A static workaround can mask an unresolved control-plane synchronization problem and fail during another topology change.
  2. Unilateral removal of authentication does not establish a trusted matching configuration and weakens control-plane protection.
  3. Uncontrolled redistribution does not restore the designed OSPF backbone and can create loops or route leaks.
  4. DR election priority does not remove a broadcast network-type assumption from a dedicated point-to-point link.

Explanation

Correct Answer

D:

DR election priority does not remove a broadcast network-type assumption from a dedicated point-to-point link. In this live production incident 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:

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 live production incident 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:

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 live production incident 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.

C:

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 live production incident 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 345

During production incident triage, 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. Removing the interface entirely can also remove the necessary prefix advertisement.
  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. BGP keepalive changes do not resolve an OSPF interface timer mismatch.

Explanation

Correct Answer

D:

BGP keepalive changes do not resolve an OSPF interface timer mismatch. In this live production incident 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:

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 live production incident 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.

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 live production incident 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:

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 live production incident 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 346

During production incident triage, 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. VLAN membership does not make incompatible LACP peers join a single forwarding aggregate.
  2. Logical link state does not certify available bandwidth after a partial member failure.
  3. Routing metrics in OSPF do not directly determine VRRP primary election.
  4. A gateway-election priority has no role in preserving the chassis routing protocol state across RE change.

Explanation

Correct Answer

D:

A gateway-election priority has no role in preserving the chassis routing protocol state across RE change. In this live production incident 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:

VLAN membership does not make incompatible LACP peers join a single forwarding aggregate. That critique concerns a shortcut from the unrelated LACP partner mismatch case. The shortcut actually proposed in this live production incident is: 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.

B:

Logical link state does not certify available bandwidth after a partial member failure. That critique concerns a shortcut from the unrelated LAG member imbalance after failure case. The shortcut actually proposed in this live production incident is: 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:

Routing metrics in OSPF do not directly determine VRRP primary election. That critique concerns a shortcut from the unrelated VRRP master priority failover case. The shortcut actually proposed in this live production incident is: 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 347

During production incident triage, engineers observe: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. An engineer suggests the shortcut: "Flood every core prefix as a static route into each Level 1 edge." Which critique explains the specific risk of that shortcut?

  1. Mass static redistribution adds scale and maintenance risk instead of using the designed hierarchy.
  2. Additional IPv4 addresses do not provide the ISO interface family needed for IS-IS signaling.
  3. Documentation cannot extend a protocol metric's encoding or cause routers to use a new metric style.
  4. OSPF election settings are unrelated to IS-IS DIS selection on the LAN.

Explanation

Correct Answer

A:

Mass static redistribution adds scale and maintenance risk instead of using the designed hierarchy. In this live production incident the shortcut was explicitly proposed as: Flood every core prefix as a static route into each Level 1 edge. It fails to resolve the underlying problem that Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes. A sound alternative is the targeted engineering action: Ensure appropriate L1/L2 router connectivity and default-reachability design toward the Level 2 backbone.

Incorrect Answers

B:

Additional IPv4 addresses do not provide the ISO interface family needed for IS-IS signaling. That critique concerns a shortcut from the unrelated IS-IS ISO family missing case. The shortcut actually proposed in this live production incident is: Flood every core prefix as a static route into each Level 1 edge. It should be rejected for the narrower reason that Mass static redistribution adds scale and maintenance risk instead of using the designed hierarchy. This distinction matters because Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes.

C:

Documentation cannot extend a protocol metric's encoding or cause routers to use a new metric style. That critique concerns a shortcut from the unrelated IS-IS narrow metric ceiling case. The shortcut actually proposed in this live production incident is: Flood every core prefix as a static route into each Level 1 edge. It should be rejected for the narrower reason that Mass static redistribution adds scale and maintenance risk instead of using the designed hierarchy. This distinction matters because Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes.

D:

OSPF election settings are unrelated to IS-IS DIS selection on the LAN. That critique concerns a shortcut from the unrelated IS-IS DIS election surprise case. The shortcut actually proposed in this live production incident is: Flood every core prefix as a static route into each Level 1 edge. It should be rejected for the narrower reason that Mass static redistribution adds scale and maintenance risk instead of using the designed hierarchy. This distinction matters because Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes.

Question 348

During production incident triage, engineers observe: A generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. An engineer suggests the shortcut: "Manually advertise an unrelated default without fixing generation conditions." 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. Removing valid specifics would disrupt actual destinations and does not establish a correct summary-fallback design.
  3. Forcing packets of one flow onto different paths can reorder packets and harm transport performance.
  4. Physical link-up does not establish downstream forwarding correctness beyond the adjacent hop.

Explanation

Correct Answer

A:

An unconditional default masks missing prerequisites and may direct traffic into an unintended path. In this live production incident the shortcut was explicitly proposed as: Manually advertise an unrelated default without fixing generation conditions. It fails to resolve the underlying problem that Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text. A sound alternative is the targeted engineering action: Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior.

Incorrect Answers

B:

Removing valid specifics would disrupt actual destinations and does not establish a correct summary-fallback design. That critique concerns a shortcut from the unrelated Aggregate rejection behavior case. The shortcut actually proposed in this live production incident is: Manually advertise an unrelated default without fixing generation conditions. It should be rejected for the narrower reason that An unconditional default masks missing prerequisites and may direct traffic into an unintended path. This distinction matters because Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text.

C:

Forcing packets of one flow onto different paths can reorder packets and harm transport performance. That critique concerns a shortcut from the unrelated Per-flow hash expectation case. The shortcut actually proposed in this live production incident is: Manually advertise an unrelated default without fixing generation conditions. It should be rejected for the narrower reason that An unconditional default masks missing prerequisites and may direct traffic into an unintended path. This distinction matters because Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text.

D:

Physical link-up does not establish downstream forwarding correctness beyond the adjacent hop. That critique concerns a shortcut from the unrelated Static backup blackhole case. The shortcut actually proposed in this live production incident is: Manually advertise an unrelated default without fixing generation conditions. It should be rejected for the narrower reason that An unconditional default masks missing prerequisites and may direct traffic into an unintended path. This distinction matters because Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text.

Question 349

During production incident triage, engineers observe: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. An engineer suggests the shortcut: "Change only the packet's IP source address and keep the invalid incoming-label mapping." 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. Additional network-layer routes cannot substitute for the required LDP session transport.
  3. Packet size settings cannot create capacity for an RSVP admission request.
  4. IP addressing does not repair the label operation needed at a transit LSR.

Explanation

Correct Answer

D:

IP addressing does not repair the label operation needed at a transit LSR. In this live production incident the shortcut was explicitly proposed as: Change only the packet's IP source address and keep the invalid incoming-label mapping. It fails to resolve the underlying problem that MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions. A sound alternative is the targeted engineering action: Check the label binding and route resolution and restore the correct MPLS forwarding entry for that FEC.

Incorrect Answers

A:

OSPF metric calculations cannot cause LDP to participate on an interface where it is not configured. That critique concerns a shortcut from the unrelated LDP discovery and IGP mismatch case. The shortcut actually proposed in this live production incident is: Change only the packet's IP source address and keep the invalid incoming-label mapping. It should be rejected for the narrower reason that IP addressing does not repair the label operation needed at a transit LSR. This distinction matters because MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions.

B:

Additional network-layer routes cannot substitute for the required LDP session transport. That critique concerns a shortcut from the unrelated LDP TCP 646 establishment case. The shortcut actually proposed in this live production incident is: Change only the packet's IP source address and keep the invalid incoming-label mapping. It should be rejected for the narrower reason that IP addressing does not repair the label operation needed at a transit LSR. This distinction matters because MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions.

C:

Packet size settings cannot create capacity for an RSVP admission request. That critique concerns a shortcut from the unrelated RSVP reservable bandwidth shortage case. The shortcut actually proposed in this live production incident is: Change only the packet's IP source address and keep the invalid incoming-label mapping. It should be rejected for the narrower reason that IP addressing does not repair the label operation needed at a transit LSR. This distinction matters because MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions.

Question 350

During production incident triage, 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. BGP keepalive changes do not resolve an OSPF interface timer mismatch.
  2. Removing the interface entirely can also remove the necessary prefix advertisement.
  3. SPF path cost is distinct from the DR election priority; changing cost does not reverse priority-zero ineligibility.
  4. A static workaround can mask an unresolved control-plane synchronization problem and fail during another topology change.

Explanation

Correct Answer

B:

Removing the interface entirely can also remove the necessary prefix advertisement. In this live production incident 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:

BGP keepalive changes do not resolve an OSPF interface timer mismatch. That critique concerns a shortcut from the unrelated OSPF hello dead timer mismatch case. The shortcut actually proposed in this live production incident is: 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.

C:

SPF path cost is distinct from the DR election priority; changing cost does not reverse priority-zero ineligibility. That critique concerns a shortcut from the unrelated DR priority zero misconception case. The shortcut actually proposed in this live production incident is: 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:

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 live production incident 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.


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.