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 58

Question 570

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Verify FEC route reachability, neighbor label advertisement and the label mapping installed for the specific destination.
  2. Check the label binding and route resolution and restore the correct MPLS forwarding entry for that FEC.
  3. Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth.
  4. Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure.

Explanation

Correct Answer

C:

Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth. In the controlled acceptance rehearsal, the reported evidence is: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. The intervention follows the governing fact that RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability. Closure requires the corresponding specific confirmation: The LSP reserves its intended bandwidth end to end without exceeding the engineered link limits.

Incorrect Answers

A:

Verify FEC route reachability, neighbor label advertisement and the label mapping installed for the specific destination. This action was designed for the separate Missing LDP FEC label mapping case, not the controlled acceptance rehearsal being assessed. The present observation is: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. Its governing mechanism is: RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability. The narrower applicable remedy is: Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth.

B:

Check the label binding and route resolution and restore the correct MPLS forwarding entry for that FEC. This action was designed for the separate Incoming label missing in LFIB case, not the controlled acceptance rehearsal being assessed. The present observation is: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. Its governing mechanism is: RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability. The narrower applicable remedy is: Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth.

D:

Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure. This action was designed for the separate Penultimate hop popping case, not the controlled acceptance rehearsal being assessed. The present observation is: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. Its governing mechanism is: RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability. The narrower applicable remedy is: Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth.

Question 571

During a controlled acceptance rehearsal of the same defect on a separate test network, 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. Permit the intended peer-to-peer TCP 179 control connection through the applicable filter and verify bidirectional reachability.
  2. Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes.
  3. Use the designed full-mesh or route-reflector topology and validate route reflection where appropriate.
  4. Inspect negotiated hold time, keepalive behavior and actual packet loss before applying an agreed stable timer policy.

Explanation

Correct Answer

A:

Permit the intended peer-to-peer TCP 179 control connection through the applicable filter and verify bidirectional reachability. In the controlled acceptance rehearsal, 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

B:

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

Use the designed full-mesh or route-reflector topology and validate route reflection where appropriate. This action was designed for the separate IBGP transit split horizon case, not the controlled acceptance rehearsal 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:

Inspect negotiated hold time, keepalive behavior and actual packet loss before applying an agreed stable timer policy. This action was designed for the separate BGP peer flap from mismatched hold timers case, not the controlled acceptance rehearsal 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 572

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An engineer sees a route in the routing protocol database and assumes data packets must use it, but the route is hidden or inactive relative to an alternative. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Inspect the active route and forwarding-table next hop, then resolve the preference, policy or next-hop condition suppressing the expected path.
  2. Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design.
  3. Validate both route metrics and platform multipath configuration so that two intended next hops are eligible for ECMP.
  4. Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior.

Explanation

Correct Answer

A:

Inspect the active route and forwarding-table next hop, then resolve the preference, policy or next-hop condition suppressing the expected path. In the controlled acceptance rehearsal, the reported evidence is: An engineer sees a route in the routing protocol database and assumes data packets must use it, but the route is hidden or inactive relative to an alternative. The intervention follows the governing fact that Junos can retain candidate and inactive routes in routing tables while forwarding uses only the selected active route installed in the forwarding information base. Closure requires the corresponding specific confirmation: The chosen route becomes active and the forwarding table points to its resolved next hop; an end-to-end trace follows that path.

Incorrect Answers

B:

Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design. This action was designed for the separate Administrative preference overrides static case, not the controlled acceptance rehearsal being assessed. The present observation is: An engineer sees a route in the routing protocol database and assumes data packets must use it, but the route is hidden or inactive relative to an alternative. Its governing mechanism is: Junos can retain candidate and inactive routes in routing tables while forwarding uses only the selected active route installed in the forwarding information base. The narrower applicable remedy is: Inspect the active route and forwarding-table next hop, then resolve the preference, policy or next-hop condition suppressing the expected path.

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 controlled acceptance rehearsal being assessed. The present observation is: An engineer sees a route in the routing protocol database and assumes data packets must use it, but the route is hidden or inactive relative to an alternative. Its governing mechanism is: Junos can retain candidate and inactive routes in routing tables while forwarding uses only the selected active route installed in the forwarding information base. The narrower applicable remedy is: Inspect the active route and forwarding-table next hop, then resolve the preference, policy or next-hop condition suppressing the expected path.

D:

Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior. This action was designed for the separate Generated default route prerequisite case, not the controlled acceptance rehearsal being assessed. The present observation is: An engineer sees a route in the routing protocol database and assumes data packets must use it, but the route is hidden or inactive relative to an alternative. Its governing mechanism is: Junos can retain candidate and inactive routes in routing tables while forwarding uses only the selected active route installed in the forwarding information base. The narrower applicable remedy is: Inspect the active route and forwarding-table next hop, then resolve the preference, policy or next-hop condition suppressing the expected path.

Question 573

During a controlled acceptance rehearsal of the same defect on a separate test network, 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. Coordinate compatible OSPFv2 authentication method, key identifier and active secret on both peers before cutover.
  2. Set the correct point-to-point OSPF interface type where supported and aligned at both ends.
  3. Correct the actual transport MTU mismatch across the link, then validate database description exchange.
  4. Restore the intended area 0 backbone connectivity for the affected ABRs and verify inter-area summaries.

Explanation

Correct Answer

A:

Coordinate compatible OSPFv2 authentication method, key identifier and active secret on both peers before cutover. In the controlled acceptance rehearsal, 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

B:

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

Correct the actual transport MTU mismatch across the link, then validate database description exchange. This action was designed for the separate OSPF MTU ExStart stall case, not the controlled acceptance rehearsal 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.

D:

Restore the intended area 0 backbone connectivity for the affected ABRs and verify inter-area summaries. This action was designed for the separate OSPF backbone connectivity case, not the controlled acceptance rehearsal 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.

Question 574

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes.
  2. Enable and verify the intended BGP IPv6 unicast family and IPv6 next-hop reachability on the appropriate peer context.
  3. Use a controlled import policy to assign the desired BGP local preference to the selected exit paths.
  4. Inspect negotiated hold time, keepalive behavior and actual packet loss before applying an agreed stable timer policy.

Explanation

Correct Answer

C:

Use a controlled import policy to assign the desired BGP local preference to the selected exit paths. In the controlled acceptance rehearsal, the reported evidence is: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. The intervention follows the governing fact that Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility. Closure requires the corresponding specific confirmation: The designated BGP exit wins best-path selection for the intended prefixes and backup behavior remains correct.

Incorrect Answers

A:

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 controlled acceptance rehearsal being assessed. The present observation is: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. Its governing mechanism is: Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility. The narrower applicable remedy is: Use a controlled import policy to assign the desired BGP local preference to the selected exit paths.

B:

Enable and verify the intended BGP IPv6 unicast family and IPv6 next-hop reachability on the appropriate peer context. This action was designed for the separate BGP IPv6 family inactive case, not the controlled acceptance rehearsal being assessed. The present observation is: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. Its governing mechanism is: Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility. The narrower applicable remedy is: Use a controlled import policy to assign the desired BGP local preference to the selected exit paths.

D:

Inspect negotiated hold time, keepalive behavior and actual packet loss before applying an agreed stable timer policy. This action was designed for the separate BGP peer flap from mismatched hold timers case, not the controlled acceptance rehearsal being assessed. The present observation is: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. Its governing mechanism is: Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility. The narrower applicable remedy is: Use a controlled import policy to assign the desired BGP local preference to the selected exit paths.

Question 575

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Choose and configure an appropriate supported per-VLAN STP approach with documented root assignment for each VLAN.
  2. Apply the supported BPDU protection policy on true edge ports and investigate the unauthorized bridge attachment.
  3. Enable root protection on the designated administrative boundary port where superior BPDUs must not be accepted.
  4. Validate RSTP root and alternate port roles and point-to-point link conditions before testing rapid alternate-port transition.

Explanation

Correct Answer

B:

Apply the supported BPDU protection policy on true edge ports and investigate the unauthorized bridge attachment. In the controlled acceptance rehearsal, the reported evidence is: A customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. The intervention follows the governing fact that Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action. Closure requires the corresponding specific confirmation: The violating connection is blocked or alerted according to policy while legitimate host-facing links remain available.

Incorrect Answers

A:

Choose and configure an appropriate supported per-VLAN STP approach with documented root assignment for each VLAN. This action was designed for the separate Per-VLAN spanning-tree path case, not the controlled acceptance rehearsal being assessed. The present observation is: A customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. Its governing mechanism is: Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action. The narrower applicable remedy is: Apply the supported BPDU protection policy on true edge ports and investigate the unauthorized bridge attachment.

C:

Enable root protection on the designated administrative boundary port where superior BPDUs must not be accepted. This action was designed for the separate Root protection against rogue core case, not the controlled acceptance rehearsal being assessed. The present observation is: A customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. Its governing mechanism is: Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action. The narrower applicable remedy is: Apply the supported BPDU protection policy on true edge ports and investigate the unauthorized bridge attachment.

D:

Validate RSTP root and alternate port roles and point-to-point link conditions before testing rapid alternate-port transition. This action was designed for the separate RSTP alternate port activation case, not the controlled acceptance rehearsal being assessed. The present observation is: A customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. Its governing mechanism is: Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action. The narrower applicable remedy is: Apply the supported BPDU protection policy on true edge ports and investigate the unauthorized bridge attachment.

Question 576

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

  1. Set the correct point-to-point OSPF interface type where supported and aligned at both ends.
  2. Restore the intended area 0 backbone connectivity for the affected ABRs and verify inter-area summaries.
  3. Add a tightly scoped OSPF export policy for the intended prefix, preserving loop and source restrictions.
  4. Align the hello and dead intervals on both OSPF interfaces and confirm stable neighbor state.

Explanation

Correct Answer

A:

Set the correct point-to-point OSPF interface type where supported and aligned at both ends. In the controlled acceptance rehearsal, the reported evidence is: Two routers on an engineered point-to-point interface spend time trying to use an unnecessary broadcast DR election process. The intervention follows the governing fact that OSPF point-to-point network types use one direct adjacency without broadcast-network DR and BDR election. Closure requires the corresponding specific confirmation: Each endpoint shows a point-to-point interface and one stable Full neighbor without DR or BDR expectations.

Incorrect Answers

B:

Restore the intended area 0 backbone connectivity for the affected ABRs and verify inter-area summaries. This action was designed for the separate OSPF backbone connectivity case, not the controlled acceptance rehearsal being assessed. The present observation is: Two routers on an engineered point-to-point interface spend time trying to use an unnecessary broadcast DR election process. Its governing mechanism is: OSPF point-to-point network types use one direct adjacency without broadcast-network DR and BDR election. The narrower applicable remedy is: Set the correct point-to-point OSPF interface type where supported and aligned at both ends.

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 controlled acceptance rehearsal being assessed. The present observation is: Two routers on an engineered point-to-point interface spend time trying to use an unnecessary broadcast DR election process. Its governing mechanism is: OSPF point-to-point network types use one direct adjacency without broadcast-network DR and BDR election. The narrower applicable remedy is: Set the correct point-to-point OSPF interface type where supported and aligned at both ends.

D:

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 controlled acceptance rehearsal being assessed. The present observation is: Two routers on an engineered point-to-point interface spend time trying to use an unnecessary broadcast DR election process. Its governing mechanism is: OSPF point-to-point network types use one direct adjacency without broadcast-network DR and BDR election. The narrower applicable remedy is: Set the correct point-to-point OSPF interface type where supported and aligned at both ends.

Question 577

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Configure and test the intended RIB group or specific controlled route import into the appropriate secondary routing table.
  2. Validate both route metrics and platform multipath configuration so that two intended next hops are eligible for ECMP.
  3. Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path.
  4. Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure.

Explanation

Correct Answer

B:

Validate both route metrics and platform multipath configuration so that two intended next hops are eligible for ECMP. In the controlled acceptance rehearsal, the reported evidence is: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. The intervention follows the governing fact that ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds. Closure requires the corresponding specific confirmation: The forwarding table shows both expected next hops and representative flows use the authorized paths without loop or asymmetry problems.

Incorrect Answers

A:

Configure and test the intended RIB group or specific controlled route import into the appropriate secondary routing table. This action was designed for the separate RIB group forwarding copy case, not the controlled acceptance rehearsal being assessed. The present observation is: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. Its governing mechanism is: ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds. The narrower applicable remedy is: Validate both route metrics and platform multipath configuration so that two intended next hops are eligible for ECMP.

C:

Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path. This action was designed for the separate Filter policy overmatch case, not the controlled acceptance rehearsal being assessed. The present observation is: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. Its governing mechanism is: ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds. The narrower applicable remedy is: Validate both route metrics and platform multipath configuration so that two intended next hops are eligible for ECMP.

D:

Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure. This action was designed for the separate Static backup blackhole case, not the controlled acceptance rehearsal being assessed. The present observation is: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. Its governing mechanism is: ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds. The narrower applicable remedy is: Validate both route metrics and platform multipath configuration so that two intended next hops are eligible for ECMP.

Question 578

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A router attempts graceful routing restart but downstream peers remove its routes immediately because helper behavior is not available or the restart contract is unmet. 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. Validate supported graceful-restart negotiation and helper capability, or choose NSR when helper dependency is unacceptable.
  3. Tune supported preemption timing or tracking against actual upstream readiness so role recovery follows path health.
  4. Use a supported combination of GRES and NSR or appropriate graceful restart to meet the control-plane continuity target.

Explanation

Correct Answer

B:

Validate supported graceful-restart negotiation and helper capability, or choose NSR when helper dependency is unacceptable. In the controlled acceptance rehearsal, the reported evidence is: A router attempts graceful routing restart but downstream peers remove its routes immediately because helper behavior is not available or the restart contract is unmet. The intervention follows the governing fact that Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior. Closure requires the corresponding specific confirmation: Peer capability and restart-state logs show the intended graceful behavior, and routes remain valid during the controlled test.

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 controlled acceptance rehearsal being assessed. The present observation is: A router attempts graceful routing restart but downstream peers remove its routes immediately because helper behavior is not available or the restart contract is unmet. Its governing mechanism is: Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior. The narrower applicable remedy is: Validate supported graceful-restart negotiation and helper capability, or choose NSR when helper dependency is unacceptable.

C:

Tune supported preemption timing or tracking against actual upstream readiness so role recovery follows path health. This action was designed for the separate VRRP preemption oscillation case, not the controlled acceptance rehearsal being assessed. The present observation is: A router attempts graceful routing restart but downstream peers remove its routes immediately because helper behavior is not available or the restart contract is unmet. Its governing mechanism is: Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior. The narrower applicable remedy is: Validate supported graceful-restart negotiation and helper capability, or choose NSR when helper dependency is unacceptable.

D:

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 controlled acceptance rehearsal being assessed. The present observation is: A router attempts graceful routing restart but downstream peers remove its routes immediately because helper behavior is not available or the restart contract is unmet. Its governing mechanism is: Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior. The narrower applicable remedy is: Validate supported graceful-restart negotiation and helper capability, or choose NSR when helper dependency is unacceptable.

Question 579

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Specify the intended outgoing interface together with the link-local next hop and confirm the route is usable.
  2. Permit required ICMPv6 Packet Too Big signaling and align encapsulation MTU with the supported end-to-end path.
  3. Enable and verify the BGP inet6 unicast family with permitted IPv6 export/import policy and resolvable next hops.
  4. Enable and validate OSPFv3 link participation and neighbor exchange using the intended IPv6 link-local connectivity.

Explanation

Correct Answer

A:

Specify the intended outgoing interface together with the link-local next hop and confirm the route is usable. In the controlled acceptance rehearsal, the reported evidence is: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. The intervention follows the governing fact that An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop. Closure requires the corresponding specific confirmation: The IPv6 route is active in inet6.0 with the correct interface-scoped next hop and test traffic reaches the peer.

Incorrect Answers

B:

Permit required ICMPv6 Packet Too Big signaling and align encapsulation MTU with the supported end-to-end path. This action was designed for the separate ICMPv6 packet-too-big handling case, not the controlled acceptance rehearsal being assessed. The present observation is: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. Its governing mechanism is: An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop. The narrower applicable remedy is: Specify the intended outgoing interface together with the link-local next hop and confirm the route is usable.

C:

Enable and verify the BGP inet6 unicast family with permitted IPv6 export/import policy and resolvable next hops. This action was designed for the separate IPv6 BGP NLRI family omitted case, not the controlled acceptance rehearsal being assessed. The present observation is: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. Its governing mechanism is: An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop. The narrower applicable remedy is: Specify the intended outgoing interface together with the link-local next hop and confirm the route is usable.

D:

Enable and validate OSPFv3 link participation and neighbor exchange using the intended IPv6 link-local connectivity. This action was designed for the separate OSPFv3 neighbor uses link-local case, not the controlled acceptance rehearsal being assessed. The present observation is: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. Its governing mechanism is: An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop. The narrower applicable remedy is: Specify the intended outgoing interface together with the link-local next hop and confirm the route is usable.

Question 580

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Use a supported combination of GRES and NSR or appropriate graceful restart to meet the control-plane continuity target.
  2. Enable and verify supported Nonstop Active Routing with the necessary routing-state synchronization before a controlled switchover.
  3. Tune supported preemption timing or tracking against actual upstream readiness so role recovery follows path health.
  4. Validate supported graceful-restart negotiation and helper capability, or choose NSR when helper dependency is unacceptable.

Explanation

Correct Answer

C:

Tune supported preemption timing or tracking against actual upstream readiness so role recovery follows path health. In the controlled acceptance rehearsal, the reported evidence is: A recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. The intervention follows the governing fact that VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic. Closure requires the corresponding specific confirmation: Failback occurs only after verified upstream reachability and virtual gateway traffic remains stable across recovery.

Incorrect Answers

A:

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 controlled acceptance rehearsal being assessed. The present observation is: A recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. Its governing mechanism is: VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic. The narrower applicable remedy is: Tune supported preemption timing or tracking against actual upstream readiness so role recovery follows path health.

B:

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 controlled acceptance rehearsal being assessed. The present observation is: A recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. Its governing mechanism is: VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic. The narrower applicable remedy is: Tune supported preemption timing or tracking against actual upstream readiness so role recovery follows path health.

D:

Validate supported graceful-restart negotiation and helper capability, or choose NSR when helper dependency is unacceptable. This action was designed for the separate Graceful restart helper expectations case, not the controlled acceptance rehearsal being assessed. The present observation is: A recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. Its governing mechanism is: VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic. The narrower applicable remedy is: Tune supported preemption timing or tracking against actual upstream readiness so role recovery follows path health.


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.