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 8

Question 70

During production incident triage, engineers observe: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Correct the explicitly configured neighbor peer AS to match the authorized remote routing domain and verify the session parameters.
  2. Permit the intended peer-to-peer TCP 179 control connection through the applicable filter and verify bidirectional reachability.
  3. Configure an approved eBGP multihop arrangement with suitable TTL and reachable peer addresses at both ends.
  4. Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required.

Explanation

Correct Answer

D:

Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required. In the live production incident, the reported evidence is: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. The intervention follows the governing fact that When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers. Closure requires the corresponding specific confirmation: A route detail comparison shows the relevant AS-path difference and chosen path conforms to approved policy.

Incorrect Answers

A:

Correct the explicitly configured neighbor peer AS to match the authorized remote routing domain and verify the session parameters. This action was designed for the separate BGP peer autonomous system mismatch case, not the live production incident being assessed. The present observation is: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. Its governing mechanism is: When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers. The narrower applicable remedy is: Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required.

B:

Permit the intended peer-to-peer TCP 179 control connection through the applicable filter and verify bidirectional reachability. This action was designed for the separate BGP TCP transport blocked case, not the live production incident being assessed. The present observation is: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. Its governing mechanism is: When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers. The narrower applicable remedy is: Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required.

C:

Configure an approved eBGP multihop arrangement with suitable TTL and reachable peer addresses at both ends. This action was designed for the separate EBGP multihop peering case, not the live production incident being assessed. The present observation is: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. Its governing mechanism is: When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers. The narrower applicable remedy is: Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required.

Question 71

During production incident triage, 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. Align the member's LACP configuration with the approved peer aggregated Ethernet group and verify partner negotiation.
  2. Check active LAG members and traffic distribution, then reduce load or restore capacity while preserving forwarding continuity.
  3. Validate supported graceful-restart negotiation and helper capability, or choose NSR when helper dependency is unacceptable.
  4. Check VRRP virtual-address and group consistency, effective priority and owner/preemption conditions, then restore the intended priority policy.

Explanation

Correct Answer

C:

Validate supported graceful-restart negotiation and helper capability, or choose NSR when helper dependency is unacceptable. In the live production incident, 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:

Align the member's LACP configuration with the approved peer aggregated Ethernet group and verify partner negotiation. This action was designed for the separate LACP partner mismatch case, not the live production incident 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.

B:

Check active LAG members and traffic distribution, then reduce load or restore capacity while preserving forwarding continuity. This action was designed for the separate LAG member imbalance after failure case, not the live production incident 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:

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

During production incident triage, engineers observe: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Set the LAN interface passive within the relevant OSPF area while retaining the intended prefix advertisement.
  2. Validate stub-area design and use the intended summary or default-route strategy rather than expecting type-5 LSAs in the stub.
  3. Correct the relevant OSPF interface costs in line with the approved traffic-engineering design and validate SPF selection.
  4. Assign and verify a unique stable OSPF router ID for each router, then refresh affected neighbor state.

Explanation

Correct Answer

D:

Assign and verify a unique stable OSPF router ID for each router, then refresh affected neighbor state. In the live production incident, the reported evidence is: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. The intervention follows the governing fact that OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain. Closure requires the corresponding specific confirmation: The routers advertise distinct IDs, neighbors remain Full and the LSDB no longer shows conflicting origins.

Incorrect Answers

A:

Set the LAN interface passive within the relevant OSPF area while retaining the intended prefix advertisement. This action was designed for the separate OSPF passive interface case, not the live production incident being assessed. The present observation is: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. Its governing mechanism is: OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain. The narrower applicable remedy is: Assign and verify a unique stable OSPF router ID for each router, then refresh affected neighbor state.

B:

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 cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. Its governing mechanism is: OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain. The narrower applicable remedy is: Assign and verify a unique stable OSPF router ID for each router, then refresh affected neighbor state.

C:

Correct the relevant OSPF interface costs in line with the approved traffic-engineering design and validate SPF selection. This action was designed for the separate OSPF metric path preference case, not the live production incident being assessed. The present observation is: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. Its governing mechanism is: OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain. The narrower applicable remedy is: Assign and verify a unique stable OSPF router ID for each router, then refresh affected neighbor state.

Question 73

During production incident triage, engineers observe: After a provider switch reboot, the wrong access switch becomes the STP root because its bridge identifier is lower than the intended core root's ID. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Apply the supported BPDU protection policy on true edge ports and investigate the unauthorized bridge attachment.
  2. Use loop protection where BPDU loss on non-designated ports could cause an unsafe transition, after verifying platform support.
  3. Validate RSTP root and alternate port roles and point-to-point link conditions before testing rapid alternate-port transition.
  4. Set a lower appropriate bridge priority for the approved root switch and validate the redundant root hierarchy.

Explanation

Correct Answer

D:

Set a lower appropriate bridge priority for the approved root switch and validate the redundant root hierarchy. In the live production incident, the reported evidence is: After a provider switch reboot, the wrong access switch becomes the STP root because its bridge identifier is lower than the intended core root's ID. The intervention follows the governing fact that Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address. Closure requires the corresponding specific confirmation: The intended core device is reported as root and a designated backup root is stable after an election test.

Incorrect Answers

A:

Apply the supported BPDU protection policy on true edge ports and investigate the unauthorized bridge attachment. This action was designed for the separate Unexpected BPDU on edge port case, not the live production incident being assessed. The present observation is: After a provider switch reboot, the wrong access switch becomes the STP root because its bridge identifier is lower than the intended core root's ID. Its governing mechanism is: Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address. The narrower applicable remedy is: Set a lower appropriate bridge priority for the approved root switch and validate the redundant root hierarchy.

B:

Use loop protection where BPDU loss on non-designated ports could cause an unsafe transition, after verifying platform support. This action was designed for the separate Loop protection after BPDU loss case, not the live production incident being assessed. The present observation is: After a provider switch reboot, the wrong access switch becomes the STP root because its bridge identifier is lower than the intended core root's ID. Its governing mechanism is: Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address. The narrower applicable remedy is: Set a lower appropriate bridge priority for the approved root switch and validate the redundant root hierarchy.

C:

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 live production incident being assessed. The present observation is: After a provider switch reboot, the wrong access switch becomes the STP root because its bridge identifier is lower than the intended core root's ID. Its governing mechanism is: Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address. The narrower applicable remedy is: Set a lower appropriate bridge priority for the approved root switch and validate the redundant root hierarchy.

Question 74

During production incident triage, engineers observe: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Configure and bind the intended IRB Layer 3 interface to the VLAN and verify IP forwarding and gateway addressing.
  2. Align service-provider outer VLAN tags and preserve the customer's intended inner VLAN identifiers through the Q-in-Q handoff.
  3. Verify unknown-unicast flooding within the VLAN, then confirm MAC learning limits later traffic to the learned egress port.
  4. Move the intended logical interface into the correct virtual-switch instance and align its VLAN or bridge-domain membership.

Explanation

Correct Answer

B:

Align service-provider outer VLAN tags and preserve the customer's intended inner VLAN identifiers through the Q-in-Q handoff. In the live production incident, the reported evidence is: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. The intervention follows the governing fact that Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags. Closure requires the corresponding specific confirmation: Captured handoff frames carry the agreed outer tag and correct inner VLAN values and pass only the authorized service.

Incorrect Answers

A:

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: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. Its governing mechanism is: Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags. The narrower applicable remedy is: Align service-provider outer VLAN tags and preserve the customer's intended inner VLAN identifiers through the Q-in-Q handoff.

C:

Verify unknown-unicast flooding within the VLAN, then confirm MAC learning limits later traffic to the learned egress port. This action was designed for the separate Unknown unicast flooding behavior case, not the live production incident being assessed. The present observation is: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. Its governing mechanism is: Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags. The narrower applicable remedy is: Align service-provider outer VLAN tags and preserve the customer's intended inner VLAN identifiers through the Q-in-Q handoff.

D:

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: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. Its governing mechanism is: Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags. The narrower applicable remedy is: Align service-provider outer VLAN tags and preserve the customer's intended inner VLAN identifiers through the Q-in-Q handoff.

Question 75

During production incident triage, engineers observe: A remote BGP peer repeatedly closes sessions after sporadic delays, and operations incorrectly assume the configured hold timers on both routers must be identical even though negotiation occurs. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Use a controlled import policy to assign the desired BGP local preference to the selected exit paths.
  2. Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required.
  3. Validate Junos MED comparison rules and the contributing neighbor AS, then apply an explicit policy only if required by traffic design.
  4. Inspect negotiated hold time, keepalive behavior and actual packet loss before applying an agreed stable timer policy.

Explanation

Correct Answer

D:

Inspect negotiated hold time, keepalive behavior and actual packet loss before applying an agreed stable timer policy. In the live production incident, the reported evidence is: A remote BGP peer repeatedly closes sessions after sporadic delays, and operations incorrectly assume the configured hold timers on both routers must be identical even though negotiation occurs. The intervention follows the governing fact that BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long. Closure requires the corresponding specific confirmation: The negotiated hold time is visible and the session remains Established under representative transport jitter without spurious expiry.

Incorrect Answers

A:

Use a controlled import policy to assign the desired BGP local preference to the selected exit paths. This action was designed for the separate BGP local preference egress case, not the live production incident being assessed. The present observation is: A remote BGP peer repeatedly closes sessions after sporadic delays, and operations incorrectly assume the configured hold timers on both routers must be identical even though negotiation occurs. Its governing mechanism is: BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long. The narrower applicable remedy is: Inspect negotiated hold time, keepalive behavior and actual packet loss before applying an agreed stable timer policy.

B:

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: A remote BGP peer repeatedly closes sessions after sporadic delays, and operations incorrectly assume the configured hold timers on both routers must be identical even though negotiation occurs. Its governing mechanism is: BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long. The narrower applicable remedy is: Inspect negotiated hold time, keepalive behavior and actual packet loss before applying an agreed stable timer policy.

C:

Validate Junos MED comparison rules and the contributing neighbor AS, then apply an explicit policy only if required by traffic design. This action was designed for the separate BGP MED comparison scope case, not the live production incident being assessed. The present observation is: A remote BGP peer repeatedly closes sessions after sporadic delays, and operations incorrectly assume the configured hold timers on both routers must be identical even though negotiation occurs. Its governing mechanism is: BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long. The narrower applicable remedy is: Inspect negotiated hold time, keepalive behavior and actual packet loss before applying an agreed stable timer policy.

Question 76

During production incident triage, engineers observe: Hosts in a VLAN can bridge to each other but cannot reach a different subnet because the VLAN has no correctly attached integrated routing and bridging interface. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Find the physical or logical loop and correct the CE's redundant attachment or approved multihoming design.
  2. Correct the interface's supported VLAN tagging and logical-unit encapsulation so each service is matched to the intended tag.
  3. Align service-provider outer VLAN tags and preserve the customer's intended inner VLAN identifiers through the Q-in-Q handoff.
  4. Configure and bind the intended IRB Layer 3 interface to the VLAN and verify IP forwarding and gateway addressing.

Explanation

Correct Answer

D:

Configure and bind the intended IRB Layer 3 interface to the VLAN and verify IP forwarding and gateway addressing. In the live production incident, the reported evidence is: Hosts in a VLAN can bridge to each other but cannot reach a different subnet because the VLAN has no correctly attached integrated routing and bridging interface. The intervention follows the governing fact that An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching. Closure requires the corresponding specific confirmation: Hosts reach their VLAN gateway, the IRB interface appears active, and inter-VLAN traffic follows the intended security policy.

Incorrect Answers

A:

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: Hosts in a VLAN can bridge to each other but cannot reach a different subnet because the VLAN has no correctly attached integrated routing and bridging interface. Its governing mechanism is: An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching. The narrower applicable remedy is: Configure and bind the intended IRB Layer 3 interface to the VLAN and verify IP forwarding and gateway addressing.

B:

Correct the interface's supported VLAN tagging and logical-unit encapsulation so each service is matched to the intended tag. This action was designed for the separate Flexible VLAN tagging logical units case, not the live production incident being assessed. The present observation is: Hosts in a VLAN can bridge to each other but cannot reach a different subnet because the VLAN has no correctly attached integrated routing and bridging interface. Its governing mechanism is: An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching. The narrower applicable remedy is: Configure and bind the intended IRB Layer 3 interface to the VLAN and verify IP forwarding and gateway addressing.

C:

Align service-provider outer VLAN tags and preserve the customer's intended inner VLAN identifiers through the Q-in-Q handoff. This action was designed for the separate Q-in-Q outer tag mismatch case, not the live production incident being assessed. The present observation is: Hosts in a VLAN can bridge to each other but cannot reach a different subnet because the VLAN has no correctly attached integrated routing and bridging interface. Its governing mechanism is: An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching. The narrower applicable remedy is: Configure and bind the intended IRB Layer 3 interface to the VLAN and verify IP forwarding and gateway addressing.

Question 77

During production incident triage, engineers observe: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Use a controlled import policy to assign the desired BGP local preference to the selected exit paths.
  2. Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required.
  3. Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes.
  4. Correct the explicitly configured neighbor peer AS to match the authorized remote routing domain and verify the session parameters.

Explanation

Correct Answer

D:

Correct the explicitly configured neighbor peer AS to match the authorized remote routing domain and verify the session parameters. In the live production incident, the reported evidence is: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. The intervention follows the governing fact that BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session. Closure requires the corresponding specific confirmation: Both peers establish an expected eBGP session and the remote AS displayed in session state matches the design.

Incorrect Answers

A:

Use a controlled import policy to assign the desired BGP local preference to the selected exit paths. This action was designed for the separate BGP local preference egress case, not the live production incident being assessed. The present observation is: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. Its governing mechanism is: BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session. The narrower applicable remedy is: Correct the explicitly configured neighbor peer AS to match the authorized remote routing domain and verify the session parameters.

B:

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: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. Its governing mechanism is: BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session. The narrower applicable remedy is: Correct the explicitly configured neighbor peer AS to match the authorized remote routing domain and verify the session parameters.

C:

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: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. Its governing mechanism is: BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session. The narrower applicable remedy is: Correct the explicitly configured neighbor peer AS to match the authorized remote routing domain and verify the session parameters.

Question 78

During production incident triage, engineers observe: One OSPF router has a different LSA sequence or age for a core link and briefly computes a stale path after a topology event. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Set the LAN interface passive within the relevant OSPF area while retaining the intended prefix advertisement.
  2. Place both adjacency interfaces into the intended matching OSPF area, then validate neighbor exchange.
  3. Investigate adjacency stability and LSA flooding, then restore consistent current link-state information before relying on SPF.
  4. Validate stub-area design and use the intended summary or default-route strategy rather than expecting type-5 LSAs in the stub.

Explanation

Correct Answer

C:

Investigate adjacency stability and LSA flooding, then restore consistent current link-state information before relying on SPF. In the live production incident, the reported evidence is: One OSPF router has a different LSA sequence or age for a core link and briefly computes a stale path after a topology event. The intervention follows the governing fact that Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB. Closure requires the corresponding specific confirmation: Both peers show the expected current LSAs with consistent sequence and topology, and the computed path reaches the destination.

Incorrect Answers

A:

Set the LAN interface passive within the relevant OSPF area while retaining the intended prefix advertisement. This action was designed for the separate OSPF passive interface case, not the live production incident being assessed. The present observation is: One OSPF router has a different LSA sequence or age for a core link and briefly computes a stale path after a topology event. Its governing mechanism is: Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB. The narrower applicable remedy is: Investigate adjacency stability and LSA flooding, then restore consistent current link-state information before relying on SPF.

B:

Place both adjacency interfaces into the intended matching OSPF area, then validate neighbor exchange. This action was designed for the separate OSPF area ID mismatch case, not the live production incident being assessed. The present observation is: One OSPF router has a different LSA sequence or age for a core link and briefly computes a stale path after a topology event. Its governing mechanism is: Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB. The narrower applicable remedy is: Investigate adjacency stability and LSA flooding, then restore consistent current link-state information before relying on SPF.

D:

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: One OSPF router has a different LSA sequence or age for a core link and briefly computes a stale path after a topology event. Its governing mechanism is: Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB. The narrower applicable remedy is: Investigate adjacency stability and LSA flooding, then restore consistent current link-state information before relying on SPF.

Question 79

During production incident triage, engineers observe: PE-11 has a configured static route to 198.51.100.0/24, but the specified next hop 192.0.2.14 is not reachable by any active route, and traffic drops. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination.
  2. Restore an active route to the specified next-hop address or replace it with a verified reachable next hop before relying on the static route.
  3. Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change.
  4. Apply a narrowly matched ingress firewall filter action that selects the intended forwarding routing instance and verify its routes.

Explanation

Correct Answer

B:

Restore an active route to the specified next-hop address or replace it with a verified reachable next hop before relying on the static route. In the live production incident, the reported evidence is: PE-11 has a configured static route to 198.51.100.0/24, but the specified next hop 192.0.2.14 is not reachable by any active route, and traffic drops. The intervention follows the governing fact that A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface. Closure requires the corresponding specific confirmation: The static prefix becomes active with a resolved next hop, and a sourced packet test reaches the destination through the intended interface.

Incorrect Answers

A:

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-11 has a configured static route to 198.51.100.0/24, but the specified next hop 192.0.2.14 is not reachable by any active route, and traffic drops. Its governing mechanism is: A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface. The narrower applicable remedy is: Restore an active route to the specified next-hop address or replace it with a verified reachable next hop before relying on the static route.

C:

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-11 has a configured static route to 198.51.100.0/24, but the specified next hop 192.0.2.14 is not reachable by any active route, and traffic drops. Its governing mechanism is: A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface. The narrower applicable remedy is: Restore an active route to the specified next-hop address or replace it with a verified reachable next hop before relying on the static route.

D:

Apply a narrowly matched ingress firewall filter action that selects the intended forwarding routing instance and verify its routes. This action was designed for the separate Filter-based forwarding classification case, not the live production incident being assessed. The present observation is: PE-11 has a configured static route to 198.51.100.0/24, but the specified next hop 192.0.2.14 is not reachable by any active route, and traffic drops. Its governing mechanism is: A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface. The narrower applicable remedy is: Restore an active route to the specified next-hop address or replace it with a verified reachable next hop before relying on the static route.

Question 80

During production incident triage, engineers observe: A provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Apply a narrowly matched ingress firewall filter action that selects the intended forwarding routing instance and verify its routes.
  2. Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design.
  3. Verify the intended contributing routes and activate an eligible more-specific route before depending on the aggregate advertisement.
  4. Inspect the relevant martian and routing-policy configuration and explicitly enforce the authorized treatment of that prefix.

Explanation

Correct Answer

A:

Apply a narrowly matched ingress firewall filter action that selects the intended forwarding routing instance and verify its routes. In the live production incident, the reported evidence is: A provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. The intervention follows the governing fact that Filter-based forwarding selects a routing table based on matched packet fields at the ingress point; the selected table must contain a usable destination route. Closure requires the corresponding specific confirmation: Counters for the targeted match increment, only the intended traffic uses the alternate next hop, and unmatched traffic stays on its original 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 live production incident being assessed. The present observation is: A provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. Its governing mechanism is: Filter-based forwarding selects a routing table based on matched packet fields at the ingress point; the selected table must contain a usable destination route. The narrower applicable remedy is: Apply a narrowly matched ingress firewall filter action that selects the intended forwarding routing instance and verify its routes.

C:

Verify the intended contributing routes and activate an eligible more-specific route before depending on the aggregate advertisement. This action was designed for the separate Aggregate route contribution case, not the live production incident being assessed. The present observation is: A provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. Its governing mechanism is: Filter-based forwarding selects a routing table based on matched packet fields at the ingress point; the selected table must contain a usable destination route. The narrower applicable remedy is: Apply a narrowly matched ingress firewall filter action that selects the intended forwarding routing instance and verify its routes.

D:

Inspect the relevant martian and routing-policy configuration and explicitly enforce the authorized treatment of that prefix. This action was designed for the separate Martian-address acceptance case, not the live production incident being assessed. The present observation is: A provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. Its governing mechanism is: Filter-based forwarding selects a routing table based on matched packet fields at the ingress point; the selected table must contain a usable destination route. The narrower applicable remedy is: Apply a narrowly matched ingress firewall filter action that selects the intended forwarding routing instance and verify its routes.


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.