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 47

Question 460

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 ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Review passive-interface policy whenever a customer-facing segment is added.
  2. Document stub and normal area policies and validate expected LSA types.
  3. Periodically compare intended and observed SPF cost paths after bandwidth changes.
  4. Reserve router IDs in an inventory and audit uniqueness during device provisioning.

Explanation

Correct Answer

D:

Reserve router IDs in an inventory and audit uniqueness during device provisioning. The current live production incident demonstrates why this check matters: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. It monitors the mechanism that OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain. The continuing safeguard should be correlated with the specific acceptance test: The routers advertise distinct IDs, neighbors remain Full and the LSDB no longer shows conflicting origins.

Incorrect Answers

A:

Review passive-interface policy whenever a customer-facing segment is added. This control addresses the distinct OSPF passive interface operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. The directly relevant continuing check is: Reserve router IDs in an inventory and audit uniqueness during device provisioning. The governing mechanism is: OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain.

B:

Document stub and normal area policies and validate expected LSA types. This control addresses the distinct Stub area external LSA expectation operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. The directly relevant continuing check is: Reserve router IDs in an inventory and audit uniqueness during device provisioning. The governing mechanism is: OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain.

C:

Periodically compare intended and observed SPF cost paths after bandwidth changes. This control addresses the distinct OSPF metric path preference operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. The directly relevant continuing check is: Reserve router IDs in an inventory and audit uniqueness during device provisioning. The governing mechanism is: OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain.

Question 461

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 ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Review route-preference conventions for static backups during routing-policy audits.
  2. Check classifier counters, filter attachment and target-table availability after changes.
  3. Monitor aggregate active state and contributor counts before each upstream announcement change.
  4. Maintain a documented martian and bogon-address policy aligned with assigned network ranges.

Explanation

Correct Answer

B:

Check classifier counters, filter attachment and target-table availability after changes. The current live production incident demonstrates why this check matters: 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. It monitors the mechanism 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. The continuing safeguard should be correlated with the specific acceptance test: 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

A:

Review route-preference conventions for static backups during routing-policy audits. This control addresses the distinct Administrative preference overrides static operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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 directly relevant continuing check is: Check classifier counters, filter attachment and target-table availability after changes. The 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.

C:

Monitor aggregate active state and contributor counts before each upstream announcement change. This control addresses the distinct Aggregate route contribution operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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 directly relevant continuing check is: Check classifier counters, filter attachment and target-table availability after changes. The 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.

D:

Maintain a documented martian and bogon-address policy aligned with assigned network ranges. This control addresses the distinct Martian-address acceptance operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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 directly relevant continuing check is: Check classifier counters, filter attachment and target-table availability after changes. The 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.

Question 462

During production incident triage, engineers observe: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Inspect both protocol levels' IPv6 TLV propagation during dual-stack deployments.
  2. Test both outer IPv4 reachability and inner IPv6 routes during tunnel maintenance.
  3. Exercise large-packet IPv6 and PMTU tests through tunneled or low-MTU paths.
  4. Check IPv6 static routes for proper next-hop scope after link renumbering.

Explanation

Correct Answer

D:

Check IPv6 static routes for proper next-hop scope after link renumbering. The current live production incident demonstrates why this check matters: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. It monitors the mechanism that An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop. The continuing safeguard should be correlated with the specific acceptance test: The IPv6 route is active in inet6.0 with the correct interface-scoped next hop and test traffic reaches the peer.

Incorrect Answers

A:

Inspect both protocol levels' IPv6 TLV propagation during dual-stack deployments. This control addresses the distinct IS-IS IPv6 reachability TLVs operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. The directly relevant continuing check is: Check IPv6 static routes for proper next-hop scope after link renumbering. The governing mechanism is: An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop.

B:

Test both outer IPv4 reachability and inner IPv6 routes during tunnel maintenance. This control addresses the distinct IPv6 over IPv4 transit tunnel operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. The directly relevant continuing check is: Check IPv6 static routes for proper next-hop scope after link renumbering. The governing mechanism is: An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop.

C:

Exercise large-packet IPv6 and PMTU tests through tunneled or low-MTU paths. This control addresses the distinct ICMPv6 packet-too-big handling operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. The directly relevant continuing check is: Check IPv6 static routes for proper next-hop scope after link renumbering. The governing mechanism is: An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop.

Question 463

During production incident triage, 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 ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Audit next-hop reachability and route-active state after every underlay change.
  2. Use multi-flow telemetry and documented hashing expectations when evaluating ECMP efficiency.
  3. Monitor aggregate active state and contributor counts before each upstream announcement change.
  4. Review generated-route contributors and policy conditions whenever edge reachability changes.

Explanation

Correct Answer

B:

Use multi-flow telemetry and documented hashing expectations when evaluating ECMP efficiency. The current live production incident demonstrates why this check matters: 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. It monitors the mechanism 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. The continuing safeguard should be correlated with the specific acceptance test: Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded.

Incorrect Answers

A:

Audit next-hop reachability and route-active state after every underlay change. This control addresses the distinct Recursive next-hop resolution operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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 directly relevant continuing check is: Use multi-flow telemetry and documented hashing expectations when evaluating ECMP efficiency. The 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.

C:

Monitor aggregate active state and contributor counts before each upstream announcement change. This control addresses the distinct Aggregate route contribution operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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 directly relevant continuing check is: Use multi-flow telemetry and documented hashing expectations when evaluating ECMP efficiency. The 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.

D:

Review generated-route contributors and policy conditions whenever edge reachability changes. This control addresses the distinct Generated default route prerequisite operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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 directly relevant continuing check is: Use multi-flow telemetry and documented hashing expectations when evaluating ECMP efficiency. The 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.

Question 464

During production incident triage, engineers observe: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Include encapsulation overhead in tunnel MTU and traffic acceptance tests.
  2. Audit source/destination tunnel-pair symmetry during new GRE turn-ups.
  3. Monitor underlay reachability independently from tunnel interface administrative state.
  4. Document encryption requirements separately from GRE connectivity requirements.

Explanation

Correct Answer

A:

Include encapsulation overhead in tunnel MTU and traffic acceptance tests. The current live production incident demonstrates why this check matters: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. It monitors the mechanism that GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU. The continuing safeguard should be correlated with the specific acceptance test: Large application packets traverse the tunnel without blackholing, and measured payload size respects the underlay capacity.

Incorrect Answers

B:

Audit source/destination tunnel-pair symmetry during new GRE turn-ups. This control addresses the distinct GRE tunnel endpoint mismatch operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. The directly relevant continuing check is: Include encapsulation overhead in tunnel MTU and traffic acceptance tests. The governing mechanism is: GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU.

C:

Monitor underlay reachability independently from tunnel interface administrative state. This control addresses the distinct GRE underlay recursive loss operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. The directly relevant continuing check is: Include encapsulation overhead in tunnel MTU and traffic acceptance tests. The governing mechanism is: GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU.

D:

Document encryption requirements separately from GRE connectivity requirements. This control addresses the distinct GRE confidentiality misconception operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. The directly relevant continuing check is: Include encapsulation overhead in tunnel MTU and traffic acceptance tests. The governing mechanism is: GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU.

Question 465

During production incident triage, engineers observe: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Review passive-interface policy whenever a customer-facing segment is added.
  2. Document broadcast-segment DR priorities and rehearse controlled elections.
  3. Audit paired OSPF interface area assignments with neighbor-state monitoring.
  4. Document stub and normal area policies and validate expected LSA types.

Explanation

Correct Answer

B:

Document broadcast-segment DR priorities and rehearse controlled elections. The current live production incident demonstrates why this check matters: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. It monitors the mechanism that OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links. The continuing safeguard should be correlated with the specific acceptance test: An appropriate eligible router becomes DR or BDR after a controlled election and neighbor adjacency remains stable.

Incorrect Answers

A:

Review passive-interface policy whenever a customer-facing segment is added. This control addresses the distinct OSPF passive interface operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. The directly relevant continuing check is: Document broadcast-segment DR priorities and rehearse controlled elections. The governing mechanism is: OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links.

C:

Audit paired OSPF interface area assignments with neighbor-state monitoring. This control addresses the distinct OSPF area ID mismatch operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. The directly relevant continuing check is: Document broadcast-segment DR priorities and rehearse controlled elections. The governing mechanism is: OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links.

D:

Document stub and normal area policies and validate expected LSA types. This control addresses the distinct Stub area external LSA expectation operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. The directly relevant continuing check is: Document broadcast-segment DR priorities and rehearse controlled elections. The governing mechanism is: OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links.

Question 466

During production incident triage, engineers observe: VLAN 100 and VLAN 200 are intended to use different roots, but a single shared spanning-tree topology sends both over the same constrained link. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Audit edge-port BPDU protection and alerts during customer endpoint changes.
  2. Review spanning-tree instance resource limits and per-VLAN path placement during capacity changes.
  3. Test one-way BPDU loss and protected port-state behavior during redundancy reviews.
  4. Review STP root and backup priorities after device replacement or MAC changes.

Explanation

Correct Answer

B:

Review spanning-tree instance resource limits and per-VLAN path placement during capacity changes. The current live production incident demonstrates why this check matters: VLAN 100 and VLAN 200 are intended to use different roots, but a single shared spanning-tree topology sends both over the same constrained link. It monitors the mechanism that VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits. The continuing safeguard should be correlated with the specific acceptance test: Each VLAN reports its planned root and forwarding links with no loops during a controlled failover.

Incorrect Answers

A:

Audit edge-port BPDU protection and alerts during customer endpoint changes. This control addresses the distinct Unexpected BPDU on edge port operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: VLAN 100 and VLAN 200 are intended to use different roots, but a single shared spanning-tree topology sends both over the same constrained link. The directly relevant continuing check is: Review spanning-tree instance resource limits and per-VLAN path placement during capacity changes. The governing mechanism is: VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits.

C:

Test one-way BPDU loss and protected port-state behavior during redundancy reviews. This control addresses the distinct Loop protection after BPDU loss operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: VLAN 100 and VLAN 200 are intended to use different roots, but a single shared spanning-tree topology sends both over the same constrained link. The directly relevant continuing check is: Review spanning-tree instance resource limits and per-VLAN path placement during capacity changes. The governing mechanism is: VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits.

D:

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: VLAN 100 and VLAN 200 are intended to use different roots, but a single shared spanning-tree topology sends both over the same constrained link. The directly relevant continuing check is: Review spanning-tree instance resource limits and per-VLAN path placement during capacity changes. The governing mechanism is: VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits.

Question 467

During production incident triage, engineers observe: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Include native VLAN agreement and negative isolation tests in trunk turn-up procedures.
  2. Audit VLAN-to-IRB bindings and routed interfaces during new service activation.
  3. Alert on MAC move spikes and review customer redundancy topology before accepting dual links.
  4. Monitor unknown-unicast rate together with MAC-table learning and churn.

Explanation

Correct Answer

C:

Alert on MAC move spikes and review customer redundancy topology before accepting dual links. The current live production incident demonstrates why this check matters: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. It monitors the mechanism that Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments. The continuing safeguard should be correlated with the specific acceptance test: The MAC stabilizes on its expected port or approved redundancy construct and packet loss disappears.

Incorrect Answers

A:

Include native VLAN agreement and negative isolation tests in trunk turn-up procedures. This control addresses the distinct Native VLAN mismatch operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. The directly relevant continuing check is: Alert on MAC move spikes and review customer redundancy topology before accepting dual links. The governing mechanism is: Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments.

B:

Audit VLAN-to-IRB bindings and routed interfaces during new service activation. This control addresses the distinct IRB routed gateway missing operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. The directly relevant continuing check is: Alert on MAC move spikes and review customer redundancy topology before accepting dual links. The governing mechanism is: Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments.

D:

Monitor unknown-unicast rate together with MAC-table learning and churn. This control addresses the distinct Unknown unicast flooding behavior operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. The directly relevant continuing check is: Alert on MAC move spikes and review customer redundancy topology before accepting dual links. The governing mechanism is: Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments.

Question 468

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 ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Inspect both protocol levels' IPv6 TLV propagation during dual-stack deployments.
  2. Check BGP families, IPv6 route filters and next-hop resolution on each dual-stack peer.
  3. Test both outer IPv4 reachability and inner IPv6 routes during tunnel maintenance.
  4. Exercise large-packet IPv6 and PMTU tests through tunneled or low-MTU paths.

Explanation

Correct Answer

B:

Check BGP families, IPv6 route filters and next-hop resolution on each dual-stack peer. The current live production incident demonstrates why this check matters: An eBGP peering is established for inet unicast but the provider cannot receive approved IPv6 prefixes because the IPv6 address family is absent. It monitors the mechanism that BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange. The continuing safeguard should be correlated with the specific acceptance test: Approved IPv6 prefixes are received, installed and reachable with the correct inet6.0 next-hop resolution.

Incorrect Answers

A:

Inspect both protocol levels' IPv6 TLV propagation during dual-stack deployments. This control addresses the distinct IS-IS IPv6 reachability TLVs operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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 directly relevant continuing check is: Check BGP families, IPv6 route filters and next-hop resolution on each dual-stack peer. The governing mechanism is: BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange.

C:

Test both outer IPv4 reachability and inner IPv6 routes during tunnel maintenance. This control addresses the distinct IPv6 over IPv4 transit tunnel operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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 directly relevant continuing check is: Check BGP families, IPv6 route filters and next-hop resolution on each dual-stack peer. The governing mechanism is: BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange.

D:

Exercise large-packet IPv6 and PMTU tests through tunneled or low-MTU paths. This control addresses the distinct ICMPv6 packet-too-big handling operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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 directly relevant continuing check is: Check BGP families, IPv6 route filters and next-hop resolution on each dual-stack peer. The governing mechanism is: BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange.

Question 469

During production incident triage, engineers observe: PE-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Test covered and uncovered address samples as part of aggregate change validation.
  2. Review route-preference conventions for static backups during routing-policy audits.
  3. Track ECMP next-hop count and routing-cost drift after transport changes.
  4. Check classifier counters, filter attachment and target-table availability after changes.

Explanation

Correct Answer

B:

Review route-preference conventions for static backups during routing-policy audits. The current live production incident demonstrates why this check matters: PE-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. It monitors the mechanism that For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference. The continuing safeguard should be correlated with the specific acceptance test: The selected active prefix shows the intended protocol, route preference, and forwarding next hop both before and after a controlled failover.

Incorrect Answers

A:

Test covered and uncovered address samples as part of aggregate change validation. This control addresses the distinct Aggregate rejection behavior operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: PE-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. The directly relevant continuing check is: Review route-preference conventions for static backups during routing-policy audits. The governing mechanism is: For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference.

C:

Track ECMP next-hop count and routing-cost drift after transport changes. This control addresses the distinct Equal-cost multipath eligibility operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: PE-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. The directly relevant continuing check is: Review route-preference conventions for static backups during routing-policy audits. The governing mechanism is: For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference.

D:

Check classifier counters, filter attachment and target-table availability after changes. This control addresses the distinct Filter-based forwarding classification operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: PE-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. The directly relevant continuing check is: Review route-preference conventions for static backups during routing-policy audits. The governing mechanism is: For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference.

Question 470

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 ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Audit peer AS numbers during carrier handoffs and AS migration work.
  2. Audit local-preference policy for consistency across ingress points.
  3. Include AS-path comparisons in periodic interdomain routing audit reports.
  4. Review inbound prefix filtering and max-route thresholds with every peer change.

Explanation

Correct Answer

A:

Audit peer AS numbers during carrier handoffs and AS migration work. The current live production incident demonstrates why this check matters: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. It monitors the mechanism that BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session. The continuing safeguard should be correlated with the specific acceptance test: Both peers establish an expected eBGP session and the remote AS displayed in session state matches the design.

Incorrect Answers

B:

Audit local-preference policy for consistency across ingress points. This control addresses the distinct BGP local preference egress operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. The directly relevant continuing check is: Audit peer AS numbers during carrier handoffs and AS migration work. The governing mechanism is: BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session.

C:

Include AS-path comparisons in periodic interdomain routing audit reports. This control addresses the distinct BGP AS-path comparison operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. The directly relevant continuing check is: Audit peer AS numbers during carrier handoffs and AS migration work. The governing mechanism is: BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session.

D:

Review inbound prefix filtering and max-route thresholds with every peer change. This control addresses the distinct BGP import policy leak operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. The directly relevant continuing check is: Audit peer AS numbers during carrier handoffs and AS migration work. The governing mechanism is: BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session.


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.