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 41

Question 400

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. An engineer suggests the shortcut: "Add an extra IPv4 secondary address as a substitute for ISO interface support." Which critique explains the specific risk of that shortcut?

  1. An IP subnet change alone cannot resolve IS-IS Level 1 NET area incompatibility.
  2. Route preference affects installation of received routes, not which IS-IS levels can form an adjacency.
  3. Additional IPv4 addresses do not provide the ISO interface family needed for IS-IS signaling.
  4. Changing interface labels cannot repair conflicting protocol system identities.

Explanation

Correct Answer

C:

Additional IPv4 addresses do not provide the ISO interface family needed for IS-IS signaling. In this live production incident the shortcut was explicitly proposed as: Add an extra IPv4 secondary address as a substitute for ISO interface support. It fails to resolve the underlying problem that Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration. A sound alternative is the targeted engineering action: Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation.

Incorrect Answers

A:

An IP subnet change alone cannot resolve IS-IS Level 1 NET area incompatibility. That critique concerns a shortcut from the unrelated IS-IS level-one area mismatch case. The shortcut actually proposed in this live production incident is: Add an extra IPv4 secondary address as a substitute for ISO interface support. It should be rejected for the narrower reason that Additional IPv4 addresses do not provide the ISO interface family needed for IS-IS signaling. This distinction matters because Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration.

B:

Route preference affects installation of received routes, not which IS-IS levels can form an adjacency. That critique concerns a shortcut from the unrelated IS-IS level capability mismatch case. The shortcut actually proposed in this live production incident is: Add an extra IPv4 secondary address as a substitute for ISO interface support. It should be rejected for the narrower reason that Additional IPv4 addresses do not provide the ISO interface family needed for IS-IS signaling. This distinction matters because Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration.

D:

Changing interface labels cannot repair conflicting protocol system identities. That critique concerns a shortcut from the unrelated Duplicate IS-IS system ID case. The shortcut actually proposed in this live production incident is: Add an extra IPv4 secondary address as a substitute for ISO interface support. It should be rejected for the narrower reason that Additional IPv4 addresses do not provide the ISO interface family needed for IS-IS signaling. This distinction matters because Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration.

Question 401

During production incident triage, engineers observe: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Check MPLS interface participation during each core link turn-up.
  2. Rehearse RSVP protection paths during maintenance and monitor bypass readiness.
  3. Sample FEC label bindings and forwarding resolution after prefix or IGP changes.
  4. Document expected label stacks at ingress, transit and penultimate hop for key services.

Explanation

Correct Answer

B:

Rehearse RSVP protection paths during maintenance and monitor bypass readiness. The current live production incident demonstrates why this check matters: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. It monitors the mechanism that RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost. The continuing safeguard should be correlated with the specific acceptance test: The bypass LSP is operational before fault injection and protected traffic follows the bypass after the link is disabled.

Incorrect Answers

A:

Check MPLS interface participation during each core link turn-up. This control addresses the distinct MPLS interface not enabled operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. The directly relevant continuing check is: Rehearse RSVP protection paths during maintenance and monitor bypass readiness. The governing mechanism is: RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost.

C:

Sample FEC label bindings and forwarding resolution after prefix or IGP changes. This control addresses the distinct Missing LDP FEC label mapping operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. The directly relevant continuing check is: Rehearse RSVP protection paths during maintenance and monitor bypass readiness. The governing mechanism is: RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost.

D:

Document expected label stacks at ingress, transit and penultimate hop for key services. This control addresses the distinct Penultimate hop popping operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. The directly relevant continuing check is: Rehearse RSVP protection paths during maintenance and monitor bypass readiness. The governing mechanism is: RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost.

Question 402

During production incident triage, engineers observe: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Maintain a registry of ISO NET system IDs across every area and lab clone.
  2. Baseline metric-style compatibility before area-wide IS-IS cost adjustments.
  3. Alert on unusual LSP aging patterns and repeated adjacency churn.
  4. Record DIS priorities and pseudonode behavior in service-provider switching design reviews.

Explanation

Correct Answer

C:

Alert on unusual LSP aging patterns and repeated adjacency churn. The current live production incident demonstrates why this check matters: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. It monitors the mechanism that IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB. The continuing safeguard should be correlated with the specific acceptance test: LSPs from the peer remain current across normal refresh cycles and SPF paths do not disappear unexpectedly.

Incorrect Answers

A:

Maintain a registry of ISO NET system IDs across every area and lab clone. This control addresses the distinct Duplicate IS-IS system ID operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. The directly relevant continuing check is: Alert on unusual LSP aging patterns and repeated adjacency churn. The governing mechanism is: IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB.

B:

Baseline metric-style compatibility before area-wide IS-IS cost adjustments. This control addresses the distinct IS-IS narrow metric ceiling operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. The directly relevant continuing check is: Alert on unusual LSP aging patterns and repeated adjacency churn. The governing mechanism is: IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB.

D:

Record DIS priorities and pseudonode behavior in service-provider switching design reviews. This control addresses the distinct IS-IS DIS election surprise operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. The directly relevant continuing check is: Alert on unusual LSP aging patterns and repeated adjacency churn. The governing mechanism is: IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB.

Question 403

During production incident triage, engineers observe: A customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Review STP root and backup priorities after device replacement or MAC changes.
  2. Compare MSTP region configuration and digests on each addition or VLAN change.
  3. Audit edge-port BPDU protection and alerts during customer endpoint changes.
  4. Review spanning-tree instance resource limits and per-VLAN path placement during capacity changes.

Explanation

Correct Answer

C:

Audit edge-port BPDU protection and alerts during customer endpoint changes. The current live production incident demonstrates why this check matters: A customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. It monitors the mechanism that Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action. The continuing safeguard should be correlated with the specific acceptance test: The violating connection is blocked or alerted according to policy while legitimate host-facing links remain available.

Incorrect Answers

A:

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 customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. The directly relevant continuing check is: Audit edge-port BPDU protection and alerts during customer endpoint changes. The governing mechanism is: Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action.

B:

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 customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. The directly relevant continuing check is: Audit edge-port BPDU protection and alerts during customer endpoint changes. The governing mechanism is: Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action.

D:

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 customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. The directly relevant continuing check is: Audit edge-port BPDU protection and alerts during customer endpoint changes. The governing mechanism is: Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action.

Question 404

During production incident triage, engineers observe: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. Which 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. Check peer-specific TCP reachability and filtering during peering change control.
  3. Include AS-path comparisons in periodic interdomain routing audit reports.
  4. Document peer distance, TTL, and authorized transport path for remote eBGP sessions.

Explanation

Correct Answer

C:

Include AS-path comparisons in periodic interdomain routing audit reports. The current live production incident demonstrates why this check matters: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. It monitors the mechanism that When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers. The continuing safeguard should be correlated with the specific acceptance test: A route detail comparison shows the relevant AS-path difference and chosen path conforms to approved policy.

Incorrect Answers

A:

Audit peer AS numbers during carrier handoffs and AS migration work. This control addresses the distinct BGP peer autonomous system mismatch operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. The directly relevant continuing check is: Include AS-path comparisons in periodic interdomain routing audit reports. The governing mechanism is: When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers.

B:

Check peer-specific TCP reachability and filtering during peering change control. This control addresses the distinct BGP TCP transport blocked operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. The directly relevant continuing check is: Include AS-path comparisons in periodic interdomain routing audit reports. The governing mechanism is: When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers.

D:

Document peer distance, TTL, and authorized transport path for remote eBGP sessions. This control addresses the distinct EBGP multihop peering operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. The directly relevant continuing check is: Include AS-path comparisons in periodic interdomain routing audit reports. The governing mechanism is: When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers.

Question 405

During production incident triage, engineers observe: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Audit VLAN-to-IRB bindings and routed interfaces during new service activation.
  2. Monitor unknown-unicast rate together with MAC-table learning and churn.
  3. Validate both tag layers at each wholesale handoff and monitor service-tag drift.
  4. Review instance-to-interface memberships during virtual switching changes.

Explanation

Correct Answer

C:

Validate both tag layers at each wholesale handoff and monitor service-tag drift. The current live production incident demonstrates why this check matters: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. It monitors the mechanism that Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags. The continuing safeguard should be correlated with the specific acceptance test: Captured handoff frames carry the agreed outer tag and correct inner VLAN values and pass only the authorized service.

Incorrect Answers

A:

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 wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. The directly relevant continuing check is: Validate both tag layers at each wholesale handoff and monitor service-tag drift. The governing mechanism is: Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags.

B:

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 wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. The directly relevant continuing check is: Validate both tag layers at each wholesale handoff and monitor service-tag drift. The governing mechanism is: Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags.

D:

Review instance-to-interface memberships during virtual switching changes. This control addresses the distinct Virtual switch instance membership operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. The directly relevant continuing check is: Validate both tag layers at each wholesale handoff and monitor service-tag drift. The governing mechanism is: Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags.

Question 406

During production incident triage, engineers observe: Hosts in a VLAN can bridge to each other but cannot reach a different subnet because the VLAN has no correctly attached integrated routing and bridging interface. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Alert on MAC move spikes and review customer redundancy topology before accepting dual links.
  2. Audit VLAN-to-IRB bindings and routed interfaces during new service activation.
  3. Verify logical-unit VLAN IDs and encapsulation during each additional service turn-up.
  4. Validate both tag layers at each wholesale handoff and monitor service-tag drift.

Explanation

Correct Answer

B:

Audit VLAN-to-IRB bindings and routed interfaces during new service activation. The current live production incident demonstrates why this check matters: Hosts in a VLAN can bridge to each other but cannot reach a different subnet because the VLAN has no correctly attached integrated routing and bridging interface. It monitors the mechanism that An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching. The continuing safeguard should be correlated with the specific acceptance test: Hosts reach their VLAN gateway, the IRB interface appears active, and inter-VLAN traffic follows the intended security policy.

Incorrect Answers

A:

Alert on MAC move spikes and review customer redundancy topology before accepting dual links. This control addresses the distinct MAC move instability operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: Hosts in a VLAN can bridge to each other but cannot reach a different subnet because the VLAN has no correctly attached integrated routing and bridging interface. The directly relevant continuing check is: Audit VLAN-to-IRB bindings and routed interfaces during new service activation. The governing mechanism is: An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching.

C:

Verify logical-unit VLAN IDs and encapsulation during each additional service turn-up. This control addresses the distinct Flexible VLAN tagging logical units operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: Hosts in a VLAN can bridge to each other but cannot reach a different subnet because the VLAN has no correctly attached integrated routing and bridging interface. The directly relevant continuing check is: Audit VLAN-to-IRB bindings and routed interfaces during new service activation. The governing mechanism is: An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching.

D:

Validate both tag layers at each wholesale handoff and monitor service-tag drift. This control addresses the distinct Q-in-Q outer tag mismatch operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: Hosts in a VLAN can bridge to each other but cannot reach a different subnet because the VLAN has no correctly attached integrated routing and bridging interface. The directly relevant continuing check is: Audit VLAN-to-IRB bindings and routed interfaces during new service activation. The governing mechanism is: An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching.

Question 407

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

  1. Validate planned VRRP priorities and failover behavior after router maintenance.
  2. Test control-plane and data-plane continuity separately under planned RE switchovers.
  3. Monitor member count, error rate and utilization separately from AE state.
  4. Audit NSR state and replicate routing databases before maintenance windows.

Explanation

Correct Answer

C:

Monitor member count, error rate and utilization separately from AE state. The current live production incident demonstrates why this check matters: An AE bundle loses one physical member but monitoring still shows the logical interface up, and traffic exceeds the remaining member's capacity. It monitors the mechanism that A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime. The continuing safeguard should be correlated with the specific acceptance test: The active member count and per-link utilization match service design, and the aggregate handles representative traffic without excessive drops.

Incorrect Answers

A:

Validate planned VRRP priorities and failover behavior after router maintenance. This control addresses the distinct VRRP master priority failover operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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 directly relevant continuing check is: Monitor member count, error rate and utilization separately from AE state. The governing mechanism is: A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime.

B:

Test control-plane and data-plane continuity separately under planned RE switchovers. This control addresses the distinct GRES forwarding versus routing continuity operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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 directly relevant continuing check is: Monitor member count, error rate and utilization separately from AE state. The governing mechanism is: A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime.

D:

Audit NSR state and replicate routing databases before maintenance windows. This control addresses the distinct NSR backup routing synchronization operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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 directly relevant continuing check is: Monitor member count, error rate and utilization separately from AE state. The governing mechanism is: A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime.

Question 408

During production incident triage, engineers observe: Small IPv6 pings succeed over a provider path but larger sessions stall because an intermediate filter blocks Packet Too Big messages needed by IPv6 Path MTU Discovery. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Monitor OSPFv2 and OSPFv3 neighbor health independently on dual-stack links.
  2. Exercise large-packet IPv6 and PMTU tests through tunneled or low-MTU paths.
  3. Inspect both protocol levels' IPv6 TLV propagation during dual-stack deployments.
  4. Test both outer IPv4 reachability and inner IPv6 routes during tunnel maintenance.

Explanation

Correct Answer

B:

Exercise large-packet IPv6 and PMTU tests through tunneled or low-MTU paths. The current live production incident demonstrates why this check matters: Small IPv6 pings succeed over a provider path but larger sessions stall because an intermediate filter blocks Packet Too Big messages needed by IPv6 Path MTU Discovery. It monitors the mechanism that IPv6 routers do not fragment transit packets; working Path MTU Discovery relies on ICMPv6 errors when packets exceed a path MTU. The continuing safeguard should be correlated with the specific acceptance test: Large IPv6 application transfers succeed and Packet Too Big messages reach the source when necessary.

Incorrect Answers

A:

Monitor OSPFv2 and OSPFv3 neighbor health independently on dual-stack links. This control addresses the distinct OSPFv3 neighbor uses link-local operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: Small IPv6 pings succeed over a provider path but larger sessions stall because an intermediate filter blocks Packet Too Big messages needed by IPv6 Path MTU Discovery. The directly relevant continuing check is: Exercise large-packet IPv6 and PMTU tests through tunneled or low-MTU paths. The governing mechanism is: IPv6 routers do not fragment transit packets; working Path MTU Discovery relies on ICMPv6 errors when packets exceed a path MTU.

C:

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: Small IPv6 pings succeed over a provider path but larger sessions stall because an intermediate filter blocks Packet Too Big messages needed by IPv6 Path MTU Discovery. The directly relevant continuing check is: Exercise large-packet IPv6 and PMTU tests through tunneled or low-MTU paths. The governing mechanism is: IPv6 routers do not fragment transit packets; working Path MTU Discovery relies on ICMPv6 errors when packets exceed a path MTU.

D:

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: Small IPv6 pings succeed over a provider path but larger sessions stall because an intermediate filter blocks Packet Too Big messages needed by IPv6 Path MTU Discovery. The directly relevant continuing check is: Exercise large-packet IPv6 and PMTU tests through tunneled or low-MTU paths. The governing mechanism is: IPv6 routers do not fragment transit packets; working Path MTU Discovery relies on ICMPv6 errors when packets exceed a path MTU.

Question 409

During production incident triage, engineers observe: An operator expects the lowest MED to win between paths received from two different neighbor autonomous systems, but the BGP selection does not follow that expectation. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Validate loopback reachability, source address and peer configuration during IBGP rollout.
  2. Document peer distance, TTL, and authorized transport path for remote eBGP sessions.
  3. Verify prefix-level export allowlists during customer peering acceptance.
  4. Document intended MED comparison scope and test different-neighbor-AS cases.

Explanation

Correct Answer

D:

Document intended MED comparison scope and test different-neighbor-AS cases. The current live production incident demonstrates why this check matters: An operator expects the lowest MED to win between paths received from two different neighbor autonomous systems, but the BGP selection does not follow that expectation. It monitors the mechanism that BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking. The continuing safeguard should be correlated with the specific acceptance test: The best path matches the documented MED comparison scope and the selected inbound preference is confirmed with peer attributes.

Incorrect Answers

A:

Validate loopback reachability, source address and peer configuration during IBGP rollout. This control addresses the distinct IBGP loopback source resolution operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: An operator expects the lowest MED to win between paths received from two different neighbor autonomous systems, but the BGP selection does not follow that expectation. The directly relevant continuing check is: Document intended MED comparison scope and test different-neighbor-AS cases. The governing mechanism is: BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking.

B:

Document peer distance, TTL, and authorized transport path for remote eBGP sessions. This control addresses the distinct EBGP multihop peering operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: An operator expects the lowest MED to win between paths received from two different neighbor autonomous systems, but the BGP selection does not follow that expectation. The directly relevant continuing check is: Document intended MED comparison scope and test different-neighbor-AS cases. The governing mechanism is: BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking.

C:

Verify prefix-level export allowlists during customer peering acceptance. This control addresses the distinct BGP export policy omission operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: An operator expects the lowest MED to win between paths received from two different neighbor autonomous systems, but the BGP selection does not follow that expectation. The directly relevant continuing check is: Document intended MED comparison scope and test different-neighbor-AS cases. The governing mechanism is: BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking.

Question 410

During production incident triage, engineers observe: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. 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. Review route-preference conventions for static backups during routing-policy audits.
  3. Review generated-route contributors and policy conditions whenever edge reachability changes.
  4. Test covered and uncovered address samples as part of aggregate change validation.

Explanation

Correct Answer

D:

Test covered and uncovered address samples as part of aggregate change validation. The current live production incident demonstrates why this check matters: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. It monitors the mechanism that An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match. The continuing safeguard should be correlated with the specific acceptance test: A controlled packet to an active more-specific prefix forwards, while a packet to an uncovered address receives the intended reject or silent-discard behavior.

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: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. The directly relevant continuing check is: Test covered and uncovered address samples as part of aggregate change validation. The governing mechanism is: An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match.

B:

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: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. The directly relevant continuing check is: Test covered and uncovered address samples as part of aggregate change validation. The governing mechanism is: An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match.

C:

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: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. The directly relevant continuing check is: Test covered and uncovered address samples as part of aggregate change validation. The governing mechanism is: An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match.


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.