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 51

Question 500

During production incident triage, engineers observe: A blocking switch port abruptly stops receiving BPDUs after a one-way failure and risks moving into forwarding even though a redundant topology still exists. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Compare MSTP region configuration and digests on each addition or VLAN change.
  2. Review spanning-tree instance resource limits and per-VLAN path placement during capacity changes.
  3. Review STP root and backup priorities after device replacement or MAC changes.
  4. Test one-way BPDU loss and protected port-state behavior during redundancy reviews.

Explanation

Correct Answer

D:

Test one-way BPDU loss and protected port-state behavior during redundancy reviews. The current live production incident demonstrates why this check matters: A blocking switch port abruptly stops receiving BPDUs after a one-way failure and risks moving into forwarding even though a redundant topology still exists. It monitors the mechanism that Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection. The continuing safeguard should be correlated with the specific acceptance test: The protected port remains safe during the simulated BPDU loss and returns to normal after signaling is restored.

Incorrect Answers

A:

Compare MSTP region configuration and digests on each addition or VLAN change. This control addresses the distinct MSTP region mismatch operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A blocking switch port abruptly stops receiving BPDUs after a one-way failure and risks moving into forwarding even though a redundant topology still exists. The directly relevant continuing check is: Test one-way BPDU loss and protected port-state behavior during redundancy reviews. The governing mechanism is: Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection.

B:

Review spanning-tree instance resource limits and per-VLAN path placement during capacity changes. This control addresses the distinct Per-VLAN spanning-tree path operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A blocking switch port abruptly stops receiving BPDUs after a one-way failure and risks moving into forwarding even though a redundant topology still exists. The directly relevant continuing check is: Test one-way BPDU loss and protected port-state behavior during redundancy reviews. The governing mechanism is: Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection.

C:

Review STP root and backup priorities after device replacement or MAC changes. This control addresses the distinct Root bridge election priority operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A blocking switch port abruptly stops receiving BPDUs after a one-way failure and risks moving into forwarding even though a redundant topology still exists. The directly relevant continuing check is: Test one-way BPDU loss and protected port-state behavior during redundancy reviews. The governing mechanism is: Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection.

Question 501

During a controlled acceptance rehearsal of the same defect on a separate test network, 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 active LAG members and traffic distribution, then reduce load or restore capacity while preserving forwarding continuity.
  2. Enable and verify supported Nonstop Active Routing with the necessary routing-state synchronization before a controlled switchover.
  3. Validate supported graceful-restart negotiation and helper capability, or choose NSR when helper dependency is unacceptable.
  4. Tune supported preemption timing or tracking against actual upstream readiness so role recovery follows path health.

Explanation

Correct Answer

A:

Check active LAG members and traffic distribution, then reduce load or restore capacity while preserving forwarding continuity. In the controlled acceptance rehearsal, 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

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

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

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

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: IS-IS neighbors are up for IPv4, but IPv6 routes do not appear because the IPv6 reachability information is not advertised in supported IS-IS TLVs. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Configure a supported IPv6-over-IPv4 tunnel with reachable outer IPv4 endpoints and correct IPv6 routing into the tunnel.
  2. Enable the intended IS-IS IPv6 address-family or reachability support and validate the IPv6 prefixes in the IS-IS database.
  3. Permit required ICMPv6 Packet Too Big signaling and align encapsulation MTU with the supported end-to-end path.
  4. Enable and validate OSPFv3 link participation and neighbor exchange using the intended IPv6 link-local connectivity.

Explanation

Correct Answer

B:

Enable the intended IS-IS IPv6 address-family or reachability support and validate the IPv6 prefixes in the IS-IS database. In the controlled acceptance rehearsal, the reported evidence is: IS-IS neighbors are up for IPv4, but IPv6 routes do not appear because the IPv6 reachability information is not advertised in supported IS-IS TLVs. The intervention follows the governing fact that IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information. Closure requires the corresponding specific confirmation: The relevant IPv6 reachability TLVs are present and remote IPv6 prefixes become active in inet6.0.

Incorrect Answers

A:

Configure a supported IPv6-over-IPv4 tunnel with reachable outer IPv4 endpoints and correct IPv6 routing into the tunnel. This action was designed for the separate IPv6 over IPv4 transit tunnel case, not the controlled acceptance rehearsal being assessed. The present observation is: IS-IS neighbors are up for IPv4, but IPv6 routes do not appear because the IPv6 reachability information is not advertised in supported IS-IS TLVs. Its governing mechanism is: IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information. The narrower applicable remedy is: Enable the intended IS-IS IPv6 address-family or reachability support and validate the IPv6 prefixes in the IS-IS database.

C:

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: IS-IS neighbors are up for IPv4, but IPv6 routes do not appear because the IPv6 reachability information is not advertised in supported IS-IS TLVs. Its governing mechanism is: IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information. The narrower applicable remedy is: Enable the intended IS-IS IPv6 address-family or reachability support and validate the IPv6 prefixes in the IS-IS database.

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: IS-IS neighbors are up for IPv4, but IPv6 routes do not appear because the IPv6 reachability information is not advertised in supported IS-IS TLVs. Its governing mechanism is: IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information. The narrower applicable remedy is: Enable the intended IS-IS IPv6 address-family or reachability support and validate the IPv6 prefixes in the IS-IS database.

Question 503

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A BGP feed contains private or customer-specific prefixes that should be rejected but are installed because the receiving policy accepts too broadly. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Configure a consistent local BGP source address and ensure both loopbacks are reachable through the IGP or static routing design.
  2. Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes.
  3. Configure an approved eBGP multihop arrangement with suitable TTL and reachable peer addresses at both ends.
  4. Restore IGP or static reachability for the intended BGP next hop, or apply the correct next-hop policy where design requires it.

Explanation

Correct Answer

B:

Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes. In the controlled acceptance rehearsal, the reported evidence is: A BGP feed contains private or customer-specific prefixes that should be rejected but are installed because the receiving policy accepts too broadly. The intervention follows the governing fact that BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice. Closure requires the corresponding specific confirmation: The rejected prefix does not appear as an eligible route while approved advertised prefixes remain available.

Incorrect Answers

A:

Configure a consistent local BGP source address and ensure both loopbacks are reachable through the IGP or static routing design. This action was designed for the separate IBGP loopback source resolution case, not the controlled acceptance rehearsal being assessed. The present observation is: A BGP feed contains private or customer-specific prefixes that should be rejected but are installed because the receiving policy accepts too broadly. Its governing mechanism is: BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice. The narrower applicable remedy is: Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes.

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 controlled acceptance rehearsal being assessed. The present observation is: A BGP feed contains private or customer-specific prefixes that should be rejected but are installed because the receiving policy accepts too broadly. Its governing mechanism is: BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice. The narrower applicable remedy is: Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes.

D:

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 controlled acceptance rehearsal being assessed. The present observation is: A BGP feed contains private or customer-specific prefixes that should be rejected but are installed because the receiving policy accepts too broadly. Its governing mechanism is: BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice. The narrower applicable remedy is: Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes.

Question 504

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Align intended native VLAN handling on both ends or require explicit tagging according to the approved design.
  2. Place them in distinct approved outer service VLAN contexts while preserving each customer's inner tag.
  3. Correct the interface's supported VLAN tagging and logical-unit encapsulation so each service is matched to the intended tag.
  4. Move the intended logical interface into the correct virtual-switch instance and align its VLAN or bridge-domain membership.

Explanation

Correct Answer

B:

Place them in distinct approved outer service VLAN contexts while preserving each customer's inner tag. In the controlled acceptance rehearsal, the reported evidence is: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. The intervention follows the governing fact that Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers. Closure requires the corresponding specific confirmation: A same-tag packet from one customer cannot reach the other's service, while each customer's traffic traverses its own outer VLAN.

Incorrect Answers

A:

Align intended native VLAN handling on both ends or require explicit tagging according to the approved design. This action was designed for the separate Native VLAN mismatch case, not the controlled acceptance rehearsal being assessed. The present observation is: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. Its governing mechanism is: Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers. The narrower applicable remedy is: Place them in distinct approved outer service VLAN contexts while preserving each customer's inner tag.

C:

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 controlled acceptance rehearsal being assessed. The present observation is: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. Its governing mechanism is: Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers. The narrower applicable remedy is: Place them in distinct approved outer service VLAN contexts while preserving each customer's inner tag.

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 controlled acceptance rehearsal being assessed. The present observation is: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. Its governing mechanism is: Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers. The narrower applicable remedy is: Place them in distinct approved outer service VLAN contexts while preserving each customer's inner tag.

Question 505

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two routers have interface-based GRE tunnels, but the source address on one end does not match the destination configured on the remote end. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself.
  2. Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path.
  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

B:

Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path. In the controlled acceptance rehearsal, the reported evidence is: Two routers have interface-based GRE tunnels, but the source address on one end does not match the destination configured on the remote end. The intervention follows the governing fact that GRE encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel. Closure requires the corresponding specific confirmation: Packet captures show the expected outer GRE addresses and matching decapsulation counts on the peer.

Incorrect Answers

A:

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 controlled acceptance rehearsal being assessed. The present observation is: Two routers have interface-based GRE tunnels, but the source address on one end does not match the destination configured on the remote end. Its governing mechanism is: GRE encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel. The narrower applicable remedy is: Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path.

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 controlled acceptance rehearsal being assessed. The present observation is: Two routers have interface-based GRE tunnels, but the source address on one end does not match the destination configured on the remote end. Its governing mechanism is: GRE encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel. The narrower applicable remedy is: Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path.

D:

Add an appropriate encryption mechanism such as supported IPsec where confidentiality is required, while treating GRE as encapsulation. This action was designed for the separate GRE confidentiality misconception case, not the controlled acceptance rehearsal being assessed. The present observation is: Two routers have interface-based GRE tunnels, but the source address on one end does not match the destination configured on the remote end. Its governing mechanism is: GRE encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel. The narrower applicable remedy is: Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path.

Question 506

During a controlled acceptance rehearsal of the same defect on a separate test network, 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. Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change.
  2. Apply a narrowly matched ingress firewall filter action that selects the intended forwarding routing instance and verify its routes.
  3. Inspect the relevant martian and routing-policy configuration and explicitly enforce the authorized treatment of that prefix.
  4. Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure.

Explanation

Correct Answer

C:

Inspect the relevant martian and routing-policy configuration and explicitly enforce the authorized treatment of that prefix. In the controlled acceptance rehearsal, 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

A:

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

B:

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

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-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 507

During a controlled acceptance rehearsal of the same defect on a separate test network, 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. Inspect the relevant martian and routing-policy configuration and explicitly enforce the authorized treatment of that prefix.
  3. Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change.
  4. Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure.

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

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

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

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

Question 508

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior.
  2. Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change.
  3. Inspect the relevant martian and routing-policy configuration and explicitly enforce the authorized treatment of that prefix.
  4. Configure and test the intended RIB group or specific controlled route import into the appropriate secondary routing table.

Explanation

Correct Answer

B:

Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change. In the controlled acceptance rehearsal, the reported evidence is: A customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. The intervention follows the governing fact that Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths. Closure requires the corresponding specific confirmation: Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded.

Incorrect Answers

A:

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: A customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. Its governing mechanism is: Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths. The narrower applicable remedy is: Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change.

C:

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 controlled acceptance rehearsal being assessed. The present observation is: A customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. Its governing mechanism is: Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths. The narrower applicable remedy is: Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change.

D:

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: A customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. Its governing mechanism is: Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths. The narrower applicable remedy is: Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change.

Question 509

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Correct the relevant OSPF interface costs in line with the approved traffic-engineering design and validate SPF selection.
  2. Correct the actual transport MTU mismatch across the link, then validate database description exchange.
  3. Align the hello and dead intervals on both OSPF interfaces and confirm stable neighbor state.
  4. Add a tightly scoped OSPF export policy for the intended prefix, preserving loop and source restrictions.

Explanation

Correct Answer

C:

Align the hello and dead intervals on both OSPF interfaces and confirm stable neighbor state. In the controlled acceptance rehearsal, the reported evidence is: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. The intervention follows the governing fact that OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance. Closure requires the corresponding specific confirmation: The two interfaces report matching timers and the neighbor stays Full beyond several dead intervals.

Incorrect Answers

A:

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 controlled acceptance rehearsal being assessed. The present observation is: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. Its governing mechanism is: OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance. The narrower applicable remedy is: Align the hello and dead intervals on both OSPF interfaces and confirm stable neighbor state.

B:

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: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. Its governing mechanism is: OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance. The narrower applicable remedy is: Align the hello and dead intervals on both OSPF interfaces and confirm stable neighbor state.

D:

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: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. Its governing mechanism is: OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance. The narrower applicable remedy is: Align the hello and dead intervals on both OSPF interfaces and confirm stable neighbor state.

Question 510

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path.
  2. Validate both route metrics and platform multipath configuration so that two intended next hops are eligible for ECMP.
  3. Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change.
  4. Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure.

Explanation

Correct Answer

A:

Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path. In the controlled acceptance rehearsal, the reported evidence is: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. The intervention follows the governing fact that Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. Closure requires the corresponding specific confirmation: Matched and unmatched packet samples increment their intended counters and resolve to the expected respective routing tables.

Incorrect Answers

B:

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: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. Its governing mechanism is: Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. The narrower applicable remedy is: Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path.

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 controlled acceptance rehearsal being assessed. The present observation is: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. Its governing mechanism is: Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. The narrower applicable remedy is: Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path.

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: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. Its governing mechanism is: Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. The narrower applicable remedy is: Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path.


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.