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 1

Question 1

During production incident triage, engineers observe: A provider calls a GRE tunnel secure against eavesdropping merely because customers cannot see its inner packet headers on the underlay. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path.
  2. Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself.
  3. Correct tunnel MTU or MSS considerations and verify fragmentation or PMTU behavior for the specific supported platform.
  4. Add an appropriate encryption mechanism such as supported IPsec where confidentiality is required, while treating GRE as encapsulation.

Explanation

Correct Answer

D:

Add an appropriate encryption mechanism such as supported IPsec where confidentiality is required, while treating GRE as encapsulation. In the live production incident, the reported evidence is: A provider calls a GRE tunnel secure against eavesdropping merely because customers cannot see its inner packet headers on the underlay. The intervention follows the governing fact that GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls. Closure requires the corresponding specific confirmation: A validated encryption layer protects inner payload on the monitored underlay while GRE routing still functions as designed.

Incorrect Answers

A:

Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path. This action was designed for the separate GRE tunnel endpoint mismatch case, not the live production incident being assessed. The present observation is: A provider calls a GRE tunnel secure against eavesdropping merely because customers cannot see its inner packet headers on the underlay. Its governing mechanism is: GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls. The narrower applicable remedy is: Add an appropriate encryption mechanism such as supported IPsec where confidentiality is required, while treating GRE as encapsulation.

B:

Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself. This action was designed for the separate GRE underlay recursive loss case, not the live production incident being assessed. The present observation is: A provider calls a GRE tunnel secure against eavesdropping merely because customers cannot see its inner packet headers on the underlay. Its governing mechanism is: GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls. The narrower applicable remedy is: Add an appropriate encryption mechanism such as supported IPsec where confidentiality is required, while treating GRE as encapsulation.

C:

Correct tunnel MTU or MSS considerations and verify fragmentation or PMTU behavior for the specific supported platform. This action was designed for the separate GRE encapsulation MTU overhead case, not the live production incident being assessed. The present observation is: A provider calls a GRE tunnel secure against eavesdropping merely because customers cannot see its inner packet headers on the underlay. Its governing mechanism is: GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls. The narrower applicable remedy is: Add an appropriate encryption mechanism such as supported IPsec where confidentiality is required, while treating GRE as encapsulation.

Question 2

During production incident triage, engineers observe: An operations team expects a type-5 external route inside an OSPF stub area and reports the absence as an interface failure. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Align the hello and dead intervals on both OSPF interfaces and confirm stable neighbor state.
  2. Validate stub-area design and use the intended summary or default-route strategy rather than expecting type-5 LSAs in the stub.
  3. Set a nonzero eligible interface priority where DR candidacy is intended and re-evaluate election behavior with the network design.
  4. Investigate adjacency stability and LSA flooding, then restore consistent current link-state information before relying on SPF.

Explanation

Correct Answer

B:

Validate stub-area design and use the intended summary or default-route strategy rather than expecting type-5 LSAs in the stub. In the live production incident, the reported evidence is: An operations team expects a type-5 external route inside an OSPF stub area and reports the absence as an interface failure. The intervention follows the governing fact that OSPF stub areas intentionally restrict external LSAs and normally rely on appropriate default reachability from an ABR for external destinations. Closure requires the corresponding specific confirmation: Internal prefixes remain present, the designed default is learned, and external traffic follows that default without type-5 LSAs in the stub.

Incorrect Answers

A:

Align the hello and dead intervals on both OSPF interfaces and confirm stable neighbor state. This action was designed for the separate OSPF hello dead timer mismatch case, not the live production incident being assessed. The present observation is: An operations team expects a type-5 external route inside an OSPF stub area and reports the absence as an interface failure. Its governing mechanism is: OSPF stub areas intentionally restrict external LSAs and normally rely on appropriate default reachability from an ABR for external destinations. The narrower applicable remedy is: Validate stub-area design and use the intended summary or default-route strategy rather than expecting type-5 LSAs in the stub.

C:

Set a nonzero eligible interface priority where DR candidacy is intended and re-evaluate election behavior with the network design. This action was designed for the separate DR priority zero misconception case, not the live production incident being assessed. The present observation is: An operations team expects a type-5 external route inside an OSPF stub area and reports the absence as an interface failure. Its governing mechanism is: OSPF stub areas intentionally restrict external LSAs and normally rely on appropriate default reachability from an ABR for external destinations. The narrower applicable remedy is: Validate stub-area design and use the intended summary or default-route strategy rather than expecting type-5 LSAs in the stub.

D:

Investigate adjacency stability and LSA flooding, then restore consistent current link-state information before relying on SPF. This action was designed for the separate OSPF LSDB discrepancy case, not the live production incident being assessed. The present observation is: An operations team expects a type-5 external route inside an OSPF stub area and reports the absence as an interface failure. Its governing mechanism is: OSPF stub areas intentionally restrict external LSAs and normally rely on appropriate default reachability from an ABR for external destinations. The narrower applicable remedy is: Validate stub-area design and use the intended summary or default-route strategy rather than expecting type-5 LSAs in the stub.

Question 3

During production incident triage, engineers observe: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Restore IGP or static reachability for the intended BGP next hop, or apply the correct next-hop policy where design requires it.
  2. Permit the intended peer-to-peer TCP 179 control connection through the applicable filter and verify bidirectional reachability.
  3. Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required.
  4. Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes.

Explanation

Correct Answer

B:

Permit the intended peer-to-peer TCP 179 control connection through the applicable filter and verify bidirectional reachability. In the live production incident, the reported evidence is: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. The intervention follows the governing fact that BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering. Closure requires the corresponding specific confirmation: A TCP session is established to the correct neighbor address, BGP reaches Established and intended routes are exchanged.

Incorrect Answers

A:

Restore IGP or static reachability for the intended BGP next hop, or apply the correct next-hop policy where design requires it. This action was designed for the separate BGP next-hop inaccessible case, not the live production incident being assessed. The present observation is: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. Its governing mechanism is: BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering. The narrower applicable remedy is: Permit the intended peer-to-peer TCP 179 control connection through the applicable filter and verify bidirectional reachability.

C:

Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required. This action was designed for the separate BGP AS-path comparison case, not the live production incident being assessed. The present observation is: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. Its governing mechanism is: BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering. The narrower applicable remedy is: Permit the intended peer-to-peer TCP 179 control connection through the applicable filter and verify bidirectional reachability.

D:

Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes. This action was designed for the separate BGP import policy leak case, not the live production incident being assessed. The present observation is: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. Its governing mechanism is: BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering. The narrower applicable remedy is: Permit the intended peer-to-peer TCP 179 control connection through the applicable filter and verify bidirectional reachability.

Question 4

During production incident triage, engineers observe: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Move the intended logical interface into the correct virtual-switch instance and align its VLAN or bridge-domain membership.
  2. Find the physical or logical loop and correct the CE's redundant attachment or approved multihoming design.
  3. Configure and bind the intended IRB Layer 3 interface to the VLAN and verify IP forwarding and gateway addressing.
  4. Add only the authorized VLAN to the relevant tagged-trunk membership and verify tagging end to end.

Explanation

Correct Answer

D:

Add only the authorized VLAN to the relevant tagged-trunk membership and verify tagging end to end. In the live production incident, the reported evidence is: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. The intervention follows the governing fact that A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers. Closure requires the corresponding specific confirmation: VLAN 340 MAC learning and tagged traffic are observed on the intended trunk without accidentally carrying other customer VLANs.

Incorrect Answers

A:

Move the intended logical interface into the correct virtual-switch instance and align its VLAN or bridge-domain membership. This action was designed for the separate Virtual switch instance membership case, not the live production incident being assessed. The present observation is: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. Its governing mechanism is: A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers. The narrower applicable remedy is: Add only the authorized VLAN to the relevant tagged-trunk membership and verify tagging end to end.

B:

Find the physical or logical loop and correct the CE's redundant attachment or approved multihoming design. This action was designed for the separate MAC move instability case, not the live production incident being assessed. The present observation is: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. Its governing mechanism is: A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers. The narrower applicable remedy is: Add only the authorized VLAN to the relevant tagged-trunk membership and verify tagging end to end.

C:

Configure and bind the intended IRB Layer 3 interface to the VLAN and verify IP forwarding and gateway addressing. This action was designed for the separate IRB routed gateway missing case, not the live production incident being assessed. The present observation is: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. Its governing mechanism is: A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers. The narrower applicable remedy is: Add only the authorized VLAN to the relevant tagged-trunk membership and verify tagging end to end.

Question 5

During production incident triage, engineers observe: PE-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Inspect the relevant martian and routing-policy configuration and explicitly enforce the authorized treatment of that prefix.
  2. Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination.
  3. Validate both route metrics and platform multipath configuration so that two intended next hops are eligible for ECMP.
  4. Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change.

Explanation

Correct Answer

A:

Inspect the relevant martian and routing-policy configuration and explicitly enforce the authorized treatment of that prefix. In the live production incident, the reported evidence is: PE-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. The intervention follows the governing fact that Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context. Closure requires the corresponding specific confirmation: The prefix is absent from permitted active forwarding while legitimate nearby routes remain reachable and logged rejection evidence matches policy.

Incorrect Answers

B:

Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination. This action was designed for the separate Aggregate rejection behavior case, not the live production incident being assessed. The present observation is: PE-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. Its governing mechanism is: Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context. The narrower applicable remedy is: Inspect the relevant martian and routing-policy configuration and explicitly enforce the authorized treatment of that prefix.

C:

Validate both route metrics and platform multipath configuration so that two intended next hops are eligible for ECMP. This action was designed for the separate Equal-cost multipath eligibility case, not the live production incident being assessed. The present observation is: PE-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. Its governing mechanism is: Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context. The narrower applicable remedy is: Inspect the relevant martian and routing-policy configuration and explicitly enforce the authorized treatment of that prefix.

D:

Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change. This action was designed for the separate Per-flow hash expectation case, not the live production incident being assessed. The present observation is: PE-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. Its governing mechanism is: Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context. The narrower applicable remedy is: Inspect the relevant martian and routing-policy configuration and explicitly enforce the authorized treatment of that prefix.

Question 6

During production incident triage, engineers observe: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Synchronize the intended IS-IS authentication method and accepted keys on both peers, then verify accepted PDUs.
  2. Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation.
  3. Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support.
  4. Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election.

Explanation

Correct Answer

A:

Synchronize the intended IS-IS authentication method and accepted keys on both peers, then verify accepted PDUs. In the live production incident, the reported evidence is: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. The intervention follows the governing fact that When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted. Closure requires the corresponding specific confirmation: Neighbor exchanges succeed without authentication errors and their corresponding LSDB contents are current.

Incorrect Answers

B:

Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation. This action was designed for the separate IS-IS ISO family missing case, not the live production incident being assessed. The present observation is: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. Its governing mechanism is: When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted. The narrower applicable remedy is: Synchronize the intended IS-IS authentication method and accepted keys on both peers, then verify accepted PDUs.

C:

Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support. This action was designed for the separate IS-IS narrow metric ceiling case, not the live production incident being assessed. The present observation is: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. Its governing mechanism is: When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted. The narrower applicable remedy is: Synchronize the intended IS-IS authentication method and accepted keys on both peers, then verify accepted PDUs.

D:

Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election. This action was designed for the separate IS-IS DIS election surprise case, not the live production incident being assessed. The present observation is: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. Its governing mechanism is: When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted. The narrower applicable remedy is: Synchronize the intended IS-IS authentication method and accepted keys on both peers, then verify accepted PDUs.

Question 7

During production incident triage, 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. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Set a nonzero eligible interface priority where DR candidacy is intended and re-evaluate election behavior with the network design.
  2. Investigate adjacency stability and LSA flooding, then restore consistent current link-state information before relying on SPF.
  3. Add a tightly scoped OSPF export policy for the intended prefix, preserving loop and source restrictions.
  4. Place both adjacency interfaces into the intended matching OSPF area, then validate neighbor exchange.

Explanation

Correct Answer

D:

Place both adjacency interfaces into the intended matching OSPF area, then validate neighbor exchange. In the live production incident, the reported evidence is: 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. The intervention follows the governing fact that OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship. Closure requires the corresponding specific confirmation: Both peers reach Full adjacency in the same area and the intended routes are learned.

Incorrect Answers

A:

Set a nonzero eligible interface priority where DR candidacy is intended and re-evaluate election behavior with the network design. This action was designed for the separate DR priority zero misconception case, not the live production incident being assessed. The present observation is: 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. Its governing mechanism is: OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship. The narrower applicable remedy is: Place both adjacency interfaces into the intended matching OSPF area, then validate neighbor exchange.

B:

Investigate adjacency stability and LSA flooding, then restore consistent current link-state information before relying on SPF. This action was designed for the separate OSPF LSDB discrepancy case, not the live production incident being assessed. The present observation is: 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. Its governing mechanism is: OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship. The narrower applicable remedy is: Place both adjacency interfaces into the intended matching OSPF area, then validate neighbor exchange.

C:

Add a tightly scoped OSPF export policy for the intended prefix, preserving loop and source restrictions. This action was designed for the separate OSPF export policy omission case, not the live production incident being assessed. The present observation is: 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. Its governing mechanism is: OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship. The narrower applicable remedy is: Place both adjacency interfaces into the intended matching OSPF area, then validate neighbor exchange.

Question 8

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. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Check the label binding and route resolution and restore the correct MPLS forwarding entry for that FEC.
  2. Enable and validate LDP on the intended interfaces that share IGP reachability with participating neighbors.
  3. Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls.
  4. Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth.

Explanation

Correct Answer

A:

Check the label binding and route resolution and restore the correct MPLS forwarding entry for that FEC. In the live production incident, the reported evidence is: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. The intervention follows the governing fact that MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions. Closure requires the corresponding specific confirmation: A lookup for the affected incoming label shows the expected output label and interface, and an MPLS trace reaches the egress.

Incorrect Answers

B:

Enable and validate LDP on the intended interfaces that share IGP reachability with participating neighbors. This action was designed for the separate LDP discovery and IGP mismatch case, not the live production incident being assessed. The present observation is: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. Its governing mechanism is: MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions. The narrower applicable remedy is: Check the label binding and route resolution and restore the correct MPLS forwarding entry for that FEC.

C:

Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls. This action was designed for the separate LDP TCP 646 establishment case, not the live production incident being assessed. The present observation is: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. Its governing mechanism is: MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions. The narrower applicable remedy is: Check the label binding and route resolution and restore the correct MPLS forwarding entry for that FEC.

D:

Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth. This action was designed for the separate RSVP reservable bandwidth shortage case, not the live production incident being assessed. The present observation is: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. Its governing mechanism is: MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions. The narrower applicable remedy is: Check the label binding and route resolution and restore the correct MPLS forwarding entry for that FEC.

Question 9

During production incident triage, engineers observe: An AE bundle loses one physical member but monitoring still shows the logical interface up, and traffic exceeds the remaining member's capacity. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Check VRRP virtual-address and group consistency, effective priority and owner/preemption conditions, then restore the intended priority policy.
  2. Check active LAG members and traffic distribution, then reduce load or restore capacity while preserving forwarding continuity.
  3. Use a supported combination of GRES and NSR or appropriate graceful restart to meet the control-plane continuity target.
  4. Enable and verify supported Nonstop Active Routing with the necessary routing-state synchronization before a controlled switchover.

Explanation

Correct Answer

B:

Check active LAG members and traffic distribution, then reduce load or restore capacity while preserving forwarding continuity. In the live production incident, the reported evidence is: An AE bundle loses one physical member but monitoring still shows the logical interface up, and traffic exceeds the remaining member's capacity. The intervention follows the governing fact that A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime. Closure requires the corresponding specific confirmation: The active member count and per-link utilization match service design, and the aggregate handles representative traffic without excessive drops.

Incorrect Answers

A:

Check VRRP virtual-address and group consistency, effective priority and owner/preemption conditions, then restore the intended priority policy. This action was designed for the separate VRRP master priority failover case, not the live production incident being assessed. The present observation is: An AE bundle loses one physical member but monitoring still shows the logical interface up, and traffic exceeds the remaining member's capacity. Its governing mechanism is: A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime. The narrower applicable remedy is: Check active LAG members and traffic distribution, then reduce load or restore capacity while preserving forwarding continuity.

C:

Use a supported combination of GRES and NSR or appropriate graceful restart to meet the control-plane continuity target. This action was designed for the separate GRES forwarding versus routing continuity case, not the live production incident being assessed. The present observation is: An AE bundle loses one physical member but monitoring still shows the logical interface up, and traffic exceeds the remaining member's capacity. Its governing mechanism is: A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime. The narrower applicable remedy is: Check active LAG members and traffic distribution, then reduce load or restore capacity while preserving forwarding continuity.

D:

Enable and verify supported Nonstop Active Routing with the necessary routing-state synchronization before a controlled switchover. This action was designed for the separate NSR backup routing synchronization case, not the live production incident being assessed. The present observation is: An AE bundle loses one physical member but monitoring still shows the logical interface up, and traffic exceeds the remaining member's capacity. Its governing mechanism is: A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime. The narrower applicable remedy is: Check active LAG members and traffic distribution, then reduce load or restore capacity while preserving forwarding continuity.

Question 10

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. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Validate stub-area design and use the intended summary or default-route strategy rather than expecting type-5 LSAs in the stub.
  2. Set a nonzero eligible interface priority where DR candidacy is intended and re-evaluate election behavior with the network design.
  3. Set the correct point-to-point OSPF interface type where supported and aligned at both ends.
  4. Coordinate compatible OSPFv2 authentication method, key identifier and active secret on both peers before cutover.

Explanation

Correct Answer

D:

Coordinate compatible OSPFv2 authentication method, key identifier and active secret on both peers before cutover. In the live production incident, the reported evidence is: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. The intervention follows the governing fact that OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree. Closure requires the corresponding specific confirmation: Authenticated OSPF packet exchange resumes, the neighbor reaches Full and no authentication failures remain in logs.

Incorrect Answers

A:

Validate stub-area design and use the intended summary or default-route strategy rather than expecting type-5 LSAs in the stub. This action was designed for the separate Stub area external LSA expectation case, not the live production incident being assessed. The present observation is: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. Its governing mechanism is: OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree. The narrower applicable remedy is: Coordinate compatible OSPFv2 authentication method, key identifier and active secret on both peers before cutover.

B:

Set a nonzero eligible interface priority where DR candidacy is intended and re-evaluate election behavior with the network design. This action was designed for the separate DR priority zero misconception case, not the live production incident being assessed. The present observation is: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. Its governing mechanism is: OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree. The narrower applicable remedy is: Coordinate compatible OSPFv2 authentication method, key identifier and active secret on both peers before cutover.

C:

Set the correct point-to-point OSPF interface type where supported and aligned at both ends. This action was designed for the separate Point-to-point OSPF network type case, not the live production incident being assessed. The present observation is: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. Its governing mechanism is: OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree. The narrower applicable remedy is: Coordinate compatible OSPFv2 authentication method, key identifier and active secret on both peers before cutover.


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.