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 49

Question 480

During production incident triage, engineers observe: A provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Audit LACP partner identity and collecting/distributing state during bundle maintenance.
  2. Validate planned VRRP priorities and failover behavior after router maintenance.
  3. Monitor VRRP failover and preempt events correlated to upstream route health.
  4. Baseline BFD timer settings by platform and monitor false-flap trends.

Explanation

Correct Answer

D:

Baseline BFD timer settings by platform and monitor false-flap trends. The current live production incident demonstrates why this check matters: A provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. It monitors the mechanism that BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure. The continuing safeguard should be correlated with the specific acceptance test: The session remains stable during representative load yet detects an injected forwarding fault within the approved interval.

Incorrect Answers

A:

Audit LACP partner identity and collecting/distributing state during bundle maintenance. This control addresses the distinct LACP partner mismatch operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. The directly relevant continuing check is: Baseline BFD timer settings by platform and monitor false-flap trends. The governing mechanism is: BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure.

B:

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: A provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. The directly relevant continuing check is: Baseline BFD timer settings by platform and monitor false-flap trends. The governing mechanism is: BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure.

C:

Monitor VRRP failover and preempt events correlated to upstream route health. This control addresses the distinct VRRP preemption oscillation operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. The directly relevant continuing check is: Baseline BFD timer settings by platform and monitor false-flap trends. The governing mechanism is: BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure.

Question 481

During production incident triage, engineers observe: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Exercise backup-path liveness detection under downstream and local failure scenarios.
  2. Maintain explicit inter-instance route-leak allowlists and regression tests.
  3. Review import/export scope and route-copy audits when new routing instances are introduced.
  4. Review route-preference conventions for static backups during routing-policy audits.

Explanation

Correct Answer

B:

Maintain explicit inter-instance route-leak allowlists and regression tests. The current live production incident demonstrates why this check matters: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. It monitors the mechanism that Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy. The continuing safeguard should be correlated with the specific acceptance test: Permitted prefixes are visible in the correct tables and an unauthorized destination is absent from the receiving customer's forwarding view.

Incorrect Answers

A:

Exercise backup-path liveness detection under downstream and local failure scenarios. This control addresses the distinct Static backup blackhole operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. The directly relevant continuing check is: Maintain explicit inter-instance route-leak allowlists and regression tests. The governing mechanism is: Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy.

C:

Review import/export scope and route-copy audits when new routing instances are introduced. This control addresses the distinct RIB group forwarding copy operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. The directly relevant continuing check is: Maintain explicit inter-instance route-leak allowlists and regression tests. The governing mechanism is: Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy.

D:

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 customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. The directly relevant continuing check is: Maintain explicit inter-instance route-leak allowlists and regression tests. The governing mechanism is: Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy.

Question 482

During production incident triage, engineers observe: A newly connected CE sends traffic to a destination MAC not yet learned in its VLAN, and operators mistake the initial flooding for a routing loop. 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. Review instance-to-interface memberships during virtual switching changes.
  3. Monitor unknown-unicast rate together with MAC-table learning and churn.
  4. Validate both tag layers at each wholesale handoff and monitor service-tag drift.

Explanation

Correct Answer

C:

Monitor unknown-unicast rate together with MAC-table learning and churn. The current live production incident demonstrates why this check matters: A newly connected CE sends traffic to a destination MAC not yet learned in its VLAN, and operators mistake the initial flooding for a routing loop. It monitors the mechanism that A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic. The continuing safeguard should be correlated with the specific acceptance test: Initial flooding is VLAN-scoped, then subsequent frames to the learned MAC use the correct specific egress port.

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: A newly connected CE sends traffic to a destination MAC not yet learned in its VLAN, and operators mistake the initial flooding for a routing loop. The directly relevant continuing check is: Monitor unknown-unicast rate together with MAC-table learning and churn. The governing mechanism is: A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic.

B:

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 newly connected CE sends traffic to a destination MAC not yet learned in its VLAN, and operators mistake the initial flooding for a routing loop. The directly relevant continuing check is: Monitor unknown-unicast rate together with MAC-table learning and churn. The governing mechanism is: A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic.

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: A newly connected CE sends traffic to a destination MAC not yet learned in its VLAN, and operators mistake the initial flooding for a routing loop. The directly relevant continuing check is: Monitor unknown-unicast rate together with MAC-table learning and churn. The governing mechanism is: A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic.

Question 483

During production incident triage, engineers observe: Two PE routers exchange OSPF Hello packets on the same Ethernet segment but stay Down because one interface belongs to area 0 and the other to area 10. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Document broadcast-segment DR priorities and rehearse controlled elections.
  2. Alert on repeated OSPF adjacency resets and divergent LSA conditions.
  3. Audit external route export allowlists against approved customer prefixes.
  4. Audit paired OSPF interface area assignments with neighbor-state monitoring.

Explanation

Correct Answer

D:

Audit paired OSPF interface area assignments with neighbor-state monitoring. The current live production incident demonstrates why this check matters: Two PE routers exchange OSPF Hello packets on the same Ethernet segment but stay Down because one interface belongs to area 0 and the other to area 10. It monitors the mechanism that OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship. The continuing safeguard should be correlated with the specific acceptance test: Both peers reach Full adjacency in the same area and the intended routes are learned.

Incorrect Answers

A:

Document broadcast-segment DR priorities and rehearse controlled elections. This control addresses the distinct DR priority zero misconception operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: Two PE routers exchange OSPF Hello packets on the same Ethernet segment but stay Down because one interface belongs to area 0 and the other to area 10. The directly relevant continuing check is: Audit paired OSPF interface area assignments with neighbor-state monitoring. The governing mechanism is: OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship.

B:

Alert on repeated OSPF adjacency resets and divergent LSA conditions. This control addresses the distinct OSPF LSDB discrepancy operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: Two PE routers exchange OSPF Hello packets on the same Ethernet segment but stay Down because one interface belongs to area 0 and the other to area 10. The directly relevant continuing check is: Audit paired OSPF interface area assignments with neighbor-state monitoring. The governing mechanism is: OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship.

C:

Audit external route export allowlists against approved customer prefixes. This control addresses the distinct OSPF export policy omission operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: Two PE routers exchange OSPF Hello packets on the same Ethernet segment but stay Down because one interface belongs to area 0 and the other to area 10. The directly relevant continuing check is: Audit paired OSPF interface area assignments with neighbor-state monitoring. The governing mechanism is: OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship.

Question 484

During production incident triage, engineers observe: A service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Verify label disposition and QoS handling at MPLS egress boundaries after policy changes.
  2. Compare LDP-enabled links with IGP core interfaces after changes.
  3. Check LDP session transport filtering as part of control-plane ACL reviews.
  4. Track reserved and unreserved bandwidth on TE links before new LSP provisioning.

Explanation

Correct Answer

A:

Verify label disposition and QoS handling at MPLS egress boundaries after policy changes. The current live production incident demonstrates why this check matters: A service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. It monitors the mechanism that Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping. The continuing safeguard should be correlated with the specific acceptance test: A captured or traced packet reaches the egress with the expected explicit-null label and traffic-class handling.

Incorrect Answers

B:

Compare LDP-enabled links with IGP core interfaces after changes. This control addresses the distinct LDP discovery and IGP mismatch operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. The directly relevant continuing check is: Verify label disposition and QoS handling at MPLS egress boundaries after policy changes. The governing mechanism is: Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping.

C:

Check LDP session transport filtering as part of control-plane ACL reviews. This control addresses the distinct LDP TCP 646 establishment operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. The directly relevant continuing check is: Verify label disposition and QoS handling at MPLS egress boundaries after policy changes. The governing mechanism is: Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping.

D:

Track reserved and unreserved bandwidth on TE links before new LSP provisioning. This control addresses the distinct RSVP reservable bandwidth shortage operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. The directly relevant continuing check is: Verify label disposition and QoS handling at MPLS egress boundaries after policy changes. The governing mechanism is: Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping.

Question 485

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

  1. Audit LACP partner identity and collecting/distributing state during bundle maintenance.
  2. Baseline BFD timer settings by platform and monitor false-flap trends.
  3. Test control-plane and data-plane continuity separately under planned RE switchovers.
  4. Monitor VRRP failover and preempt events correlated to upstream route health.

Explanation

Correct Answer

D:

Monitor VRRP failover and preempt events correlated to upstream route health. The current live production incident demonstrates why this check matters: A recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. It monitors the mechanism that VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic. The continuing safeguard should be correlated with the specific acceptance test: Failback occurs only after verified upstream reachability and virtual gateway traffic remains stable across recovery.

Incorrect Answers

A:

Audit LACP partner identity and collecting/distributing state during bundle maintenance. This control addresses the distinct LACP partner mismatch operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. The directly relevant continuing check is: Monitor VRRP failover and preempt events correlated to upstream route health. The governing mechanism is: VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic.

B:

Baseline BFD timer settings by platform and monitor false-flap trends. This control addresses the distinct BFD detect timer too aggressive operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. The directly relevant continuing check is: Monitor VRRP failover and preempt events correlated to upstream route health. The governing mechanism is: VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic.

C:

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: A recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. The directly relevant continuing check is: Monitor VRRP failover and preempt events correlated to upstream route health. The governing mechanism is: VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic.

Question 486

During production incident triage, engineers observe: PE-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. Which 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. Track ECMP next-hop count and routing-cost drift after transport changes.
  3. Maintain a documented martian and bogon-address policy aligned with assigned network ranges.
  4. Use multi-flow telemetry and documented hashing expectations when evaluating ECMP efficiency.

Explanation

Correct Answer

C:

Maintain a documented martian and bogon-address policy aligned with assigned network ranges. The current live production incident demonstrates why this check matters: PE-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. It monitors the mechanism that Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context. The continuing safeguard should be correlated with the specific acceptance test: The prefix is absent from permitted active forwarding while legitimate nearby routes remain reachable and logged rejection evidence matches policy.

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-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. The directly relevant continuing check is: Maintain a documented martian and bogon-address policy aligned with assigned network ranges. The governing mechanism is: Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context.

B:

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-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. The directly relevant continuing check is: Maintain a documented martian and bogon-address policy aligned with assigned network ranges. The governing mechanism is: Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context.

D:

Use multi-flow telemetry and documented hashing expectations when evaluating ECMP efficiency. This control addresses the distinct Per-flow hash expectation operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: PE-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. The directly relevant continuing check is: Maintain a documented martian and bogon-address policy aligned with assigned network ranges. The governing mechanism is: Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context.

Question 487

During production incident triage, engineers observe: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Monitor unresolved BGP next hops separately from session establishment.
  2. Include AS-path comparisons in periodic interdomain routing audit reports.
  3. Review inbound prefix filtering and max-route thresholds with every peer change.
  4. Check peer-specific TCP reachability and filtering during peering change control.

Explanation

Correct Answer

D:

Check peer-specific TCP reachability and filtering during peering change control. The current live production incident demonstrates why this check matters: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. It monitors the mechanism that BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering. The continuing safeguard should be correlated with the specific acceptance test: A TCP session is established to the correct neighbor address, BGP reaches Established and intended routes are exchanged.

Incorrect Answers

A:

Monitor unresolved BGP next hops separately from session establishment. This control addresses the distinct BGP next-hop inaccessible operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. The directly relevant continuing check is: Check peer-specific TCP reachability and filtering during peering change control. The governing mechanism is: BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering.

B:

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: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. The directly relevant continuing check is: Check peer-specific TCP reachability and filtering during peering change control. The governing mechanism is: BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering.

C:

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: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. The directly relevant continuing check is: Check peer-specific TCP reachability and filtering during peering change control. The governing mechanism is: BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering.

Question 488

During production incident triage, engineers observe: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Audit LACP partner identity and collecting/distributing state during bundle maintenance.
  2. Monitor member count, error rate and utilization separately from AE state.
  3. Validate planned VRRP priorities and failover behavior after router maintenance.
  4. Baseline BFD timer settings by platform and monitor false-flap trends.

Explanation

Correct Answer

C:

Validate planned VRRP priorities and failover behavior after router maintenance. The current live production incident demonstrates why this check matters: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. It monitors the mechanism that VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway. The continuing safeguard should be correlated with the specific acceptance test: The designated router is primary under normal conditions and the backup takes over promptly during an injected outage.

Incorrect Answers

A:

Audit LACP partner identity and collecting/distributing state during bundle maintenance. This control addresses the distinct LACP partner mismatch operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. The directly relevant continuing check is: Validate planned VRRP priorities and failover behavior after router maintenance. The governing mechanism is: VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway.

B:

Monitor member count, error rate and utilization separately from AE state. This control addresses the distinct LAG member imbalance after failure operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. The directly relevant continuing check is: Validate planned VRRP priorities and failover behavior after router maintenance. The governing mechanism is: VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway.

D:

Baseline BFD timer settings by platform and monitor false-flap trends. This control addresses the distinct BFD detect timer too aggressive operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. The directly relevant continuing check is: Validate planned VRRP priorities and failover behavior after router maintenance. The governing mechanism is: VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway.

Question 489

During production incident triage, engineers observe: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Baseline OSPF timer settings per transport class and alert on configuration drift.
  2. Audit paired OSPF interface area assignments with neighbor-state monitoring.
  3. Document stub and normal area policies and validate expected LSA types.
  4. Audit external route export allowlists against approved customer prefixes.

Explanation

Correct Answer

D:

Audit external route export allowlists against approved customer prefixes. The current live production incident demonstrates why this check matters: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. It monitors the mechanism that External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements. The continuing safeguard should be correlated with the specific acceptance test: The specifically allowed customer prefix appears as the expected external route on the peer, while other connected networks stay unadvertised.

Incorrect Answers

A:

Baseline OSPF timer settings per transport class and alert on configuration drift. This control addresses the distinct OSPF hello dead timer mismatch operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. The directly relevant continuing check is: Audit external route export allowlists against approved customer prefixes. The governing mechanism is: External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements.

B:

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: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. The directly relevant continuing check is: Audit external route export allowlists against approved customer prefixes. The governing mechanism is: External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements.

C:

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: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. The directly relevant continuing check is: Audit external route export allowlists against approved customer prefixes. The governing mechanism is: External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements.

Question 490

During production incident triage, engineers observe: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. 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. Maintain unique outer service identifiers for separate tenants and test cross-tenant isolation.
  3. Monitor unknown-unicast rate together with MAC-table learning and churn.
  4. Include native VLAN agreement and negative isolation tests in trunk turn-up procedures.

Explanation

Correct Answer

B:

Maintain unique outer service identifiers for separate tenants and test cross-tenant isolation. The current live production incident demonstrates why this check matters: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. It monitors the mechanism that Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers. The continuing safeguard should be correlated with the specific acceptance test: A same-tag packet from one customer cannot reach the other's service, while each customer's traffic traverses its own outer VLAN.

Incorrect Answers

A:

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: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. The directly relevant continuing check is: Maintain unique outer service identifiers for separate tenants and test cross-tenant isolation. The governing mechanism is: Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers.

C:

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: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. The directly relevant continuing check is: Maintain unique outer service identifiers for separate tenants and test cross-tenant isolation. The governing mechanism is: Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers.

D:

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: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. The directly relevant continuing check is: Maintain unique outer service identifiers for separate tenants and test cross-tenant isolation. The governing mechanism is: Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers.


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.