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 9

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.

Question 81

During production incident triage, 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. 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 a consistent local BGP source address and ensure both loopbacks are reachable through the IGP or static routing design.
  4. Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes.

Explanation

Correct Answer

D:

Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes. In the live production incident, 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:

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

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

During production incident triage, 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. Tune supported preemption timing or tracking against actual upstream readiness so role recovery follows path health.
  2. Align the member's LACP configuration with the approved peer aggregated Ethernet group and verify partner negotiation.
  3. Choose a supported BFD interval and detection multiplier appropriate for network scale and peer capacity, then test fault response.
  4. Use a supported combination of GRES and NSR or appropriate graceful restart to meet the control-plane continuity target.

Explanation

Correct Answer

A:

Tune supported preemption timing or tracking against actual upstream readiness so role recovery follows path health. In the live production incident, 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

B:

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

C:

Choose a supported BFD interval and detection multiplier appropriate for network scale and peer capacity, then test fault response. This action was designed for the separate BFD detect timer too aggressive case, not the live production incident 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:

Use a supported combination of GRES and NSR or appropriate graceful restart to meet the control-plane continuity target. This action was designed for the separate GRES forwarding versus routing continuity case, not the live production incident being assessed. The present observation is: 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.

Question 83

During production incident triage, engineers observe: An SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls.
  2. Use appropriate segment choices or a supported SR policy when explicit path steering is required, rather than treating a node SID as an exact-hop instruction.
  3. Check the label binding and route resolution and restore the correct MPLS forwarding entry for that FEC.
  4. Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure.

Explanation

Correct Answer

B:

Use appropriate segment choices or a supported SR policy when explicit path steering is required, rather than treating a node SID as an exact-hop instruction. In the live production incident, the reported evidence is: An SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. The intervention follows the governing fact that A node SID typically steers toward its destination using shortest-path IGP forwarding, while explicit adjacency segments can add finer path constraints. Closure requires the corresponding specific confirmation: The observed label stack and forwarding path match the documented shortest path or the specified explicit segment list.

Incorrect Answers

A:

Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls. This action was designed for the separate LDP TCP 646 establishment case, not the live production incident being assessed. The present observation is: An SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. Its governing mechanism is: A node SID typically steers toward its destination using shortest-path IGP forwarding, while explicit adjacency segments can add finer path constraints. The narrower applicable remedy is: Use appropriate segment choices or a supported SR policy when explicit path steering is required, rather than treating a node SID as an exact-hop instruction.

C:

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 live production incident being assessed. The present observation is: An SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. Its governing mechanism is: A node SID typically steers toward its destination using shortest-path IGP forwarding, while explicit adjacency segments can add finer path constraints. The narrower applicable remedy is: Use appropriate segment choices or a supported SR policy when explicit path steering is required, rather than treating a node SID as an exact-hop instruction.

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 live production incident being assessed. The present observation is: An SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. Its governing mechanism is: A node SID typically steers toward its destination using shortest-path IGP forwarding, while explicit adjacency segments can add finer path constraints. The narrower applicable remedy is: Use appropriate segment choices or a supported SR policy when explicit path steering is required, rather than treating a node SID as an exact-hop instruction.

Question 84

During production incident triage, engineers observe: An eBGP peering is established for inet unicast but the provider cannot receive approved IPv6 prefixes because the IPv6 address family is absent. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Enable the intended IS-IS IPv6 address-family or reachability support and validate the IPv6 prefixes in the IS-IS database.
  2. Configure a supported IPv6-over-IPv4 tunnel with reachable outer IPv4 endpoints and correct IPv6 routing into the tunnel.
  3. Permit required ICMPv6 Packet Too Big signaling and align encapsulation MTU with the supported end-to-end path.
  4. Enable and verify the BGP inet6 unicast family with permitted IPv6 export/import policy and resolvable next hops.

Explanation

Correct Answer

D:

Enable and verify the BGP inet6 unicast family with permitted IPv6 export/import policy and resolvable next hops. In the live production incident, the reported evidence is: An eBGP peering is established for inet unicast but the provider cannot receive approved IPv6 prefixes because the IPv6 address family is absent. The intervention follows the governing fact that BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange. Closure requires the corresponding specific confirmation: Approved IPv6 prefixes are received, installed and reachable with the correct inet6.0 next-hop resolution.

Incorrect Answers

A:

Enable the intended IS-IS IPv6 address-family or reachability support and validate the IPv6 prefixes in the IS-IS database. This action was designed for the separate IS-IS IPv6 reachability TLVs case, not the live production incident being assessed. The present observation is: An eBGP peering is established for inet unicast but the provider cannot receive approved IPv6 prefixes because the IPv6 address family is absent. Its governing mechanism is: BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange. The narrower applicable remedy is: Enable and verify the BGP inet6 unicast family with permitted IPv6 export/import policy and resolvable next hops.

B:

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 live production incident being assessed. The present observation is: An eBGP peering is established for inet unicast but the provider cannot receive approved IPv6 prefixes because the IPv6 address family is absent. Its governing mechanism is: BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange. The narrower applicable remedy is: Enable and verify the BGP inet6 unicast family with permitted IPv6 export/import policy and resolvable next hops.

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 live production incident being assessed. The present observation is: An eBGP peering is established for inet unicast but the provider cannot receive approved IPv6 prefixes because the IPv6 address family is absent. Its governing mechanism is: BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange. The narrower applicable remedy is: Enable and verify the BGP inet6 unicast family with permitted IPv6 export/import policy and resolvable next hops.

Question 85

During production incident triage, engineers observe: A router interface carries IPv4 traffic and is listed under IS-IS, but no IS-IS Hello packets form because the required ISO protocol family is absent. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation.
  2. Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended.
  3. Configure a common allowed IS-IS level on the two interfaces in accordance with the area and backbone design.
  4. Allocate unique system identifiers in the NET on each router and refresh the affected IS-IS topology state.

Explanation

Correct Answer

A:

Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation. In the live production incident, the reported evidence is: A router interface carries IPv4 traffic and is listed under IS-IS, but no IS-IS Hello packets form because the required ISO protocol family is absent. The intervention follows the governing fact that Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration. Closure requires the corresponding specific confirmation: IS-IS Hello exchanges appear and the expected level adjacency establishes while IPv4 traffic still functions.

Incorrect Answers

B:

Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended. This action was designed for the separate IS-IS level-one area mismatch case, not the live production incident being assessed. The present observation is: A router interface carries IPv4 traffic and is listed under IS-IS, but no IS-IS Hello packets form because the required ISO protocol family is absent. Its governing mechanism is: Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration. The narrower applicable remedy is: Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation.

C:

Configure a common allowed IS-IS level on the two interfaces in accordance with the area and backbone design. This action was designed for the separate IS-IS level capability mismatch case, not the live production incident being assessed. The present observation is: A router interface carries IPv4 traffic and is listed under IS-IS, but no IS-IS Hello packets form because the required ISO protocol family is absent. Its governing mechanism is: Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration. The narrower applicable remedy is: Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation.

D:

Allocate unique system identifiers in the NET on each router and refresh the affected IS-IS topology state. This action was designed for the separate Duplicate IS-IS system ID case, not the live production incident being assessed. The present observation is: A router interface carries IPv4 traffic and is listed under IS-IS, but no IS-IS Hello packets form because the required ISO protocol family is absent. Its governing mechanism is: Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration. The narrower applicable remedy is: Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation.

Question 86

During production incident triage, engineers observe: A static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Verify the intended contributing routes and activate an eligible more-specific route before depending on the aggregate advertisement.
  2. Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior.
  3. Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure.
  4. Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination.

Explanation

Correct Answer

C:

Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure. In the live production incident, the reported evidence is: A static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. The intervention follows the governing fact that A static next hop may appear link-reachable while the remote end-to-end path is unusable, so a tracking mechanism such as BFD can be necessary. Closure requires the corresponding specific confirmation: With the downstream fault injected, the unsuitable backup route is withdrawn or de-preferred and valid traffic moves to the tested alternate.

Incorrect Answers

A:

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 static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. Its governing mechanism is: A static next hop may appear link-reachable while the remote end-to-end path is unusable, so a tracking mechanism such as BFD can be necessary. The narrower applicable remedy is: Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure.

B:

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 live production incident being assessed. The present observation is: A static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. Its governing mechanism is: A static next hop may appear link-reachable while the remote end-to-end path is unusable, so a tracking mechanism such as BFD can be necessary. The narrower applicable remedy is: Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure.

D:

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: A static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. Its governing mechanism is: A static next hop may appear link-reachable while the remote end-to-end path is unusable, so a tracking mechanism such as BFD can be necessary. The narrower applicable remedy is: Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure.

Question 87

During production incident triage, engineers observe: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. 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. Align the member's LACP configuration with the approved peer aggregated Ethernet group and verify partner negotiation.
  3. Tune supported preemption timing or tracking against actual upstream readiness so role recovery follows path health.
  4. Choose a supported BFD interval and detection multiplier appropriate for network scale and peer capacity, then test fault response.

Explanation

Correct Answer

B:

Align the member's LACP configuration with the approved peer aggregated Ethernet group and verify partner negotiation. In the live production incident, the reported evidence is: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. The intervention follows the governing fact that LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone. Closure requires the corresponding specific confirmation: All intended members show collecting and distributing state in the correct AE bundle and packet forwarding is stable.

Incorrect Answers

A:

Check VRRP virtual-address and group consistency, effective priority and owner/preemption conditions, then restore the intended priority policy. This action was designed for the separate VRRP master priority failover case, not the live production incident being assessed. The present observation is: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. Its governing mechanism is: LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone. The narrower applicable remedy is: Align the member's LACP configuration with the approved peer aggregated Ethernet group and verify partner negotiation.

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 live production incident being assessed. The present observation is: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. Its governing mechanism is: LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone. The narrower applicable remedy is: Align the member's LACP configuration with the approved peer aggregated Ethernet group and verify partner negotiation.

D:

Choose a supported BFD interval and detection multiplier appropriate for network scale and peer capacity, then test fault response. This action was designed for the separate BFD detect timer too aggressive case, not the live production incident being assessed. The present observation is: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. Its governing mechanism is: LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone. The narrower applicable remedy is: Align the member's LACP configuration with the approved peer aggregated Ethernet group and verify partner negotiation.

Question 88

During production incident triage, 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. Validate both route metrics and platform multipath configuration so that two intended next hops are eligible for ECMP.
  2. Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design.
  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

A:

Validate both route metrics and platform multipath configuration so that two intended next hops are eligible for ECMP. In the live production incident, 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

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

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

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

During production incident triage, engineers observe: A designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support.
  2. Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended.
  3. Configure a common allowed IS-IS level on the two interfaces in accordance with the area and backbone design.
  4. Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation.

Explanation

Correct Answer

A:

Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support. In the live production incident, the reported evidence is: A designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. The intervention follows the governing fact that IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering. Closure requires the corresponding specific confirmation: The LSDB advertises compatible wide metrics and SPF selects the intended path across the upgraded links.

Incorrect Answers

B:

Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended. This action was designed for the separate IS-IS level-one area mismatch case, not the live production incident being assessed. The present observation is: A designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. Its governing mechanism is: IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering. The narrower applicable remedy is: Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support.

C:

Configure a common allowed IS-IS level on the two interfaces in accordance with the area and backbone design. This action was designed for the separate IS-IS level capability mismatch case, not the live production incident being assessed. The present observation is: A designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. Its governing mechanism is: IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering. The narrower applicable remedy is: Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support.

D:

Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation. This action was designed for the separate IS-IS ISO family missing case, not the live production incident being assessed. The present observation is: A designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. Its governing mechanism is: IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering. The narrower applicable remedy is: Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support.

Question 90

During production incident triage, engineers observe: On an IS-IS broadcast LAN, an unintended router acts as the designated intermediate system because its interface priority differs from the design. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election.
  2. Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended.
  3. Configure a common allowed IS-IS level on the two interfaces in accordance with the area and backbone design.
  4. Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support.

Explanation

Correct Answer

A:

Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election. In the live production incident, the reported evidence is: On an IS-IS broadcast LAN, an unintended router acts as the designated intermediate system because its interface priority differs from the design. The intervention follows the governing fact that The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design. Closure requires the corresponding specific confirmation: The designated system matches the planned candidate, pseudonode LSPs are coherent, and LAN adjacencies remain stable.

Incorrect Answers

B:

Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended. This action was designed for the separate IS-IS level-one area mismatch case, not the live production incident being assessed. The present observation is: On an IS-IS broadcast LAN, an unintended router acts as the designated intermediate system because its interface priority differs from the design. Its governing mechanism is: The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design. The narrower applicable remedy is: Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election.

C:

Configure a common allowed IS-IS level on the two interfaces in accordance with the area and backbone design. This action was designed for the separate IS-IS level capability mismatch case, not the live production incident being assessed. The present observation is: On an IS-IS broadcast LAN, an unintended router acts as the designated intermediate system because its interface priority differs from the design. Its governing mechanism is: The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design. The narrower applicable remedy is: Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election.

D:

Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support. This action was designed for the separate IS-IS narrow metric ceiling case, not the live production incident being assessed. The present observation is: On an IS-IS broadcast LAN, an unintended router acts as the designated intermediate system because its interface priority differs from the design. Its governing mechanism is: The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design. The narrower applicable remedy is: Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election.


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.