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 29

Question 280

During production incident triage, engineers observe: A router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. A TCP session is established to the correct neighbor address, BGP reaches Established and intended routes are exchanged.
  2. The intended peer receives the route through permitted reflection or a full-mesh session, and next-hop reachability is correct.
  3. The rejected prefix does not appear as an eligible route while approved advertised prefixes remain available.
  4. A route detail comparison shows the relevant AS-path difference and chosen path conforms to approved policy.

Explanation

Correct Answer

B:

The intended peer receives the route through permitted reflection or a full-mesh session, and next-hop reachability is correct. This tests the actual condition identified in the live production incident: A router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. It is meaningful because Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design.

Incorrect Answers

A:

A TCP session is established to the correct neighbor address, BGP reaches Established and intended routes are exchanged. This measurement may prove the unrelated BGP TCP transport blocked condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. A relevant acceptance result here is: The intended peer receives the route through permitted reflection or a full-mesh session, and next-hop reachability is correct.

C:

The rejected prefix does not appear as an eligible route while approved advertised prefixes remain available. This measurement may prove the unrelated BGP import policy leak condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. A relevant acceptance result here is: The intended peer receives the route through permitted reflection or a full-mesh session, and next-hop reachability is correct.

D:

A route detail comparison shows the relevant AS-path difference and chosen path conforms to approved policy. This measurement may prove the unrelated BGP AS-path comparison condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. A relevant acceptance result here is: The intended peer receives the route through permitted reflection or a full-mesh session, and next-hop reachability is correct.

Question 281

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. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. Hosts reach their VLAN gateway, the IRB interface appears active, and inter-VLAN traffic follows the intended security policy.
  2. The MAC stabilizes on its expected port or approved redundancy construct and packet loss disappears.
  3. Per-unit counters and a packet capture demonstrate each authorized VLAN tag reaches its mapped logical interface.
  4. Captured handoff frames carry the agreed outer tag and correct inner VLAN values and pass only the authorized service.

Explanation

Correct Answer

A:

Hosts reach their VLAN gateway, the IRB interface appears active, and inter-VLAN traffic follows the intended security policy. This tests the actual condition identified in the live production incident: 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 is meaningful because An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching.

Incorrect Answers

B:

The MAC stabilizes on its expected port or approved redundancy construct and packet loss disappears. This measurement may prove the unrelated MAC move instability condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault 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. A relevant acceptance result here is: Hosts reach their VLAN gateway, the IRB interface appears active, and inter-VLAN traffic follows the intended security policy.

C:

Per-unit counters and a packet capture demonstrate each authorized VLAN tag reaches its mapped logical interface. This measurement may prove the unrelated Flexible VLAN tagging logical units condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault 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. A relevant acceptance result here is: Hosts reach their VLAN gateway, the IRB interface appears active, and inter-VLAN traffic follows the intended security policy.

D:

Captured handoff frames carry the agreed outer tag and correct inner VLAN values and pass only the authorized service. This measurement may prove the unrelated Q-in-Q outer tag mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault 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. A relevant acceptance result here is: Hosts reach their VLAN gateway, the IRB interface appears active, and inter-VLAN traffic follows the intended security policy.

Question 282

During production incident triage, engineers observe: A newly restarted provider router is marked overloaded and therefore not used as transit despite an up adjacency; operations incorrectly call it an IP link failure. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. Neighbor exchanges succeed without authentication errors and their corresponding LSDB contents are current.
  2. The intended prefix appears at the expected level without management or unrelated customer routes being leaked.
  3. A usable default or intended inter-area reachability is present, and traced traffic exits through the designed L1/L2 router.
  4. Overload state matches the operational plan, and transit path calculations include the router only after successful readiness checks.

Explanation

Correct Answer

D:

Overload state matches the operational plan, and transit path calculations include the router only after successful readiness checks. This tests the actual condition identified in the live production incident: A newly restarted provider router is marked overloaded and therefore not used as transit despite an up adjacency; operations incorrectly call it an IP link failure. It is meaningful because An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up.

Incorrect Answers

A:

Neighbor exchanges succeed without authentication errors and their corresponding LSDB contents are current. This measurement may prove the unrelated IS-IS authentication mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A newly restarted provider router is marked overloaded and therefore not used as transit despite an up adjacency; operations incorrectly call it an IP link failure. A relevant acceptance result here is: Overload state matches the operational plan, and transit path calculations include the router only after successful readiness checks.

B:

The intended prefix appears at the expected level without management or unrelated customer routes being leaked. This measurement may prove the unrelated IS-IS route export scope condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A newly restarted provider router is marked overloaded and therefore not used as transit despite an up adjacency; operations incorrectly call it an IP link failure. A relevant acceptance result here is: Overload state matches the operational plan, and transit path calculations include the router only after successful readiness checks.

C:

A usable default or intended inter-area reachability is present, and traced traffic exits through the designed L1/L2 router. This measurement may prove the unrelated IS-IS Level 1 exit default condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A newly restarted provider router is marked overloaded and therefore not used as transit despite an up adjacency; operations incorrectly call it an IP link failure. A relevant acceptance result here is: Overload state matches the operational plan, and transit path calculations include the router only after successful readiness checks.

Question 283

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. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. LSPs from the peer remain current across normal refresh cycles and SPF paths do not disappear unexpectedly.
  2. The nodes appear with distinct system IDs and no repeated conflicting LSP originator entries in the database.
  3. The LSDB advertises compatible wide metrics and SPF selects the intended path across the upgraded links.
  4. The designated system matches the planned candidate, pseudonode LSPs are coherent, and LAN adjacencies remain stable.

Explanation

Correct Answer

A:

LSPs from the peer remain current across normal refresh cycles and SPF paths do not disappear unexpectedly. This tests the actual condition identified in the live production incident: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. It is meaningful because IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB.

Incorrect Answers

B:

The nodes appear with distinct system IDs and no repeated conflicting LSP originator entries in the database. This measurement may prove the unrelated Duplicate IS-IS system ID condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. A relevant acceptance result here is: LSPs from the peer remain current across normal refresh cycles and SPF paths do not disappear unexpectedly.

C:

The LSDB advertises compatible wide metrics and SPF selects the intended path across the upgraded links. This measurement may prove the unrelated IS-IS narrow metric ceiling condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. A relevant acceptance result here is: LSPs from the peer remain current across normal refresh cycles and SPF paths do not disappear unexpectedly.

D:

The designated system matches the planned candidate, pseudonode LSPs are coherent, and LAN adjacencies remain stable. This measurement may prove the unrelated IS-IS DIS election surprise condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. A relevant acceptance result here is: LSPs from the peer remain current across normal refresh cycles and SPF paths do not disappear unexpectedly.

Question 284

During production incident triage, engineers observe: An engineer sees a route in the routing protocol database and assumes data packets must use it, but the route is hidden or inactive relative to an alternative. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded.
  2. With the downstream fault injected, the unsuitable backup route is withdrawn or de-preferred and valid traffic moves to the tested alternate.
  3. The selected active prefix shows the intended protocol, route preference, and forwarding next hop both before and after a controlled failover.
  4. The chosen route becomes active and the forwarding table points to its resolved next hop; an end-to-end trace follows that path.

Explanation

Correct Answer

D:

The chosen route becomes active and the forwarding table points to its resolved next hop; an end-to-end trace follows that path. This tests the actual condition identified in the live production incident: An engineer sees a route in the routing protocol database and assumes data packets must use it, but the route is hidden or inactive relative to an alternative. It is meaningful because Junos can retain candidate and inactive routes in routing tables while forwarding uses only the selected active route installed in the forwarding information base.

Incorrect Answers

A:

Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded. This measurement may prove the unrelated Per-flow hash expectation condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An engineer sees a route in the routing protocol database and assumes data packets must use it, but the route is hidden or inactive relative to an alternative. A relevant acceptance result here is: The chosen route becomes active and the forwarding table points to its resolved next hop; an end-to-end trace follows that path.

B:

With the downstream fault injected, the unsuitable backup route is withdrawn or de-preferred and valid traffic moves to the tested alternate. This measurement may prove the unrelated Static backup blackhole condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An engineer sees a route in the routing protocol database and assumes data packets must use it, but the route is hidden or inactive relative to an alternative. A relevant acceptance result here is: The chosen route becomes active and the forwarding table points to its resolved next hop; an end-to-end trace follows that path.

C:

The selected active prefix shows the intended protocol, route preference, and forwarding next hop both before and after a controlled failover. This measurement may prove the unrelated Administrative preference overrides static condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An engineer sees a route in the routing protocol database and assumes data packets must use it, but the route is hidden or inactive relative to an alternative. A relevant acceptance result here is: The chosen route becomes active and the forwarding table points to its resolved next hop; an end-to-end trace follows that path.

Question 285

During production incident triage, engineers observe: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. Neighbor exchanges succeed without authentication errors and their corresponding LSDB contents are current.
  2. IS-IS Hello exchanges appear and the expected level adjacency establishes while IPv4 traffic still functions.
  3. The LSDB advertises compatible wide metrics and SPF selects the intended path across the upgraded links.
  4. The designated system matches the planned candidate, pseudonode LSPs are coherent, and LAN adjacencies remain stable.

Explanation

Correct Answer

A:

Neighbor exchanges succeed without authentication errors and their corresponding LSDB contents are current. This tests the actual condition identified in the live production incident: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. It is meaningful because When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted.

Incorrect Answers

B:

IS-IS Hello exchanges appear and the expected level adjacency establishes while IPv4 traffic still functions. This measurement may prove the unrelated IS-IS ISO family missing condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. A relevant acceptance result here is: Neighbor exchanges succeed without authentication errors and their corresponding LSDB contents are current.

C:

The LSDB advertises compatible wide metrics and SPF selects the intended path across the upgraded links. This measurement may prove the unrelated IS-IS narrow metric ceiling condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. A relevant acceptance result here is: Neighbor exchanges succeed without authentication errors and their corresponding LSDB contents are current.

D:

The designated system matches the planned candidate, pseudonode LSPs are coherent, and LAN adjacencies remain stable. This measurement may prove the unrelated IS-IS DIS election surprise condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. A relevant acceptance result here is: Neighbor exchanges succeed without authentication errors and their corresponding LSDB contents are current.

Question 286

During production incident triage, engineers observe: A dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. A controlled RE switchover maintains data-plane forwarding and routing neighbor continuity according to the selected supported feature set.
  2. All intended members show collecting and distributing state in the correct AE bundle and packet forwarding is stable.
  3. The active member count and per-link utilization match service design, and the aggregate handles representative traffic without excessive drops.
  4. The designated router is primary under normal conditions and the backup takes over promptly during an injected outage.

Explanation

Correct Answer

A:

A controlled RE switchover maintains data-plane forwarding and routing neighbor continuity according to the selected supported feature set. This tests the actual condition identified in the live production incident: A dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. It is meaningful because GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions.

Incorrect Answers

B:

All intended members show collecting and distributing state in the correct AE bundle and packet forwarding is stable. This measurement may prove the unrelated LACP partner mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. A relevant acceptance result here is: A controlled RE switchover maintains data-plane forwarding and routing neighbor continuity according to the selected supported feature set.

C:

The active member count and per-link utilization match service design, and the aggregate handles representative traffic without excessive drops. This measurement may prove the unrelated LAG member imbalance after failure condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. A relevant acceptance result here is: A controlled RE switchover maintains data-plane forwarding and routing neighbor continuity according to the selected supported feature set.

D:

The designated router is primary under normal conditions and the backup takes over promptly during an injected outage. This measurement may prove the unrelated VRRP master priority failover condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. A relevant acceptance result here is: A controlled RE switchover maintains data-plane forwarding and routing neighbor continuity according to the selected supported feature set.

Question 287

During production incident triage, engineers observe: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. VLAN 340 MAC learning and tagged traffic are observed on the intended trunk without accidentally carrying other customer VLANs.
  2. The customer MAC and VLAN appear in the correct virtual-switch instance with no leakage into default bridging context.
  3. The MAC stabilizes on its expected port or approved redundancy construct and packet loss disappears.
  4. Hosts reach their VLAN gateway, the IRB interface appears active, and inter-VLAN traffic follows the intended security policy.

Explanation

Correct Answer

A:

VLAN 340 MAC learning and tagged traffic are observed on the intended trunk without accidentally carrying other customer VLANs. This tests the actual condition identified in the live production incident: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. It is meaningful because A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers.

Incorrect Answers

B:

The customer MAC and VLAN appear in the correct virtual-switch instance with no leakage into default bridging context. This measurement may prove the unrelated Virtual switch instance membership condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. A relevant acceptance result here is: VLAN 340 MAC learning and tagged traffic are observed on the intended trunk without accidentally carrying other customer VLANs.

C:

The MAC stabilizes on its expected port or approved redundancy construct and packet loss disappears. This measurement may prove the unrelated MAC move instability condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. A relevant acceptance result here is: VLAN 340 MAC learning and tagged traffic are observed on the intended trunk without accidentally carrying other customer VLANs.

D:

Hosts reach their VLAN gateway, the IRB interface appears active, and inter-VLAN traffic follows the intended security policy. This measurement may prove the unrelated IRB routed gateway missing condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. A relevant acceptance result here is: VLAN 340 MAC learning and tagged traffic are observed on the intended trunk without accidentally carrying other customer VLANs.

Question 288

During production incident triage, engineers observe: An SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. The observed label stack and forwarding path match the documented shortest path or the specified explicit segment list.
  2. An LDP session reaches Operational and displays the intended neighbor label bindings after selective filter correction.
  3. A lookup for the affected incoming label shows the expected output label and interface, and an MPLS trace reaches the egress.
  4. The egress receives the expected payload context and end-to-end service passes despite the absence of a top transport label.

Explanation

Correct Answer

A:

The observed label stack and forwarding path match the documented shortest path or the specified explicit segment list. This tests the actual condition identified in the live production incident: An SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. It is meaningful because A node SID typically steers toward its destination using shortest-path IGP forwarding, while explicit adjacency segments can add finer path constraints.

Incorrect Answers

B:

An LDP session reaches Operational and displays the intended neighbor label bindings after selective filter correction. This measurement may prove the unrelated LDP TCP 646 establishment condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. A relevant acceptance result here is: The observed label stack and forwarding path match the documented shortest path or the specified explicit segment list.

C:

A lookup for the affected incoming label shows the expected output label and interface, and an MPLS trace reaches the egress. This measurement may prove the unrelated Incoming label missing in LFIB condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. A relevant acceptance result here is: The observed label stack and forwarding path match the documented shortest path or the specified explicit segment list.

D:

The egress receives the expected payload context and end-to-end service passes despite the absence of a top transport label. This measurement may prove the unrelated Penultimate hop popping condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. A relevant acceptance result here is: The observed label stack and forwarding path match the documented shortest path or the specified explicit segment list.

Question 289

During production incident triage, engineers observe: Two routers on an engineered point-to-point interface spend time trying to use an unnecessary broadcast DR election process. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. Both peers show the expected current LSAs with consistent sequence and topology, and the computed path reaches the destination.
  2. Authenticated OSPF packet exchange resumes, the neighbor reaches Full and no authentication failures remain in logs.
  3. Each endpoint shows a point-to-point interface and one stable Full neighbor without DR or BDR expectations.
  4. ABRs have the intended area 0 connectivity and inter-area routes are present with correct next hops.

Explanation

Correct Answer

C:

Each endpoint shows a point-to-point interface and one stable Full neighbor without DR or BDR expectations. This tests the actual condition identified in the live production incident: Two routers on an engineered point-to-point interface spend time trying to use an unnecessary broadcast DR election process. It is meaningful because OSPF point-to-point network types use one direct adjacency without broadcast-network DR and BDR election.

Incorrect Answers

A:

Both peers show the expected current LSAs with consistent sequence and topology, and the computed path reaches the destination. This measurement may prove the unrelated OSPF LSDB discrepancy condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two routers on an engineered point-to-point interface spend time trying to use an unnecessary broadcast DR election process. A relevant acceptance result here is: Each endpoint shows a point-to-point interface and one stable Full neighbor without DR or BDR expectations.

B:

Authenticated OSPF packet exchange resumes, the neighbor reaches Full and no authentication failures remain in logs. This measurement may prove the unrelated OSPF authentication key mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two routers on an engineered point-to-point interface spend time trying to use an unnecessary broadcast DR election process. A relevant acceptance result here is: Each endpoint shows a point-to-point interface and one stable Full neighbor without DR or BDR expectations.

D:

ABRs have the intended area 0 connectivity and inter-area routes are present with correct next hops. This measurement may prove the unrelated OSPF backbone connectivity condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two routers on an engineered point-to-point interface spend time trying to use an unnecessary broadcast DR election process. A relevant acceptance result here is: Each endpoint shows a point-to-point interface and one stable Full neighbor without DR or BDR expectations.

Question 290

During production incident triage, engineers observe: PE-11 has a configured static route to 198.51.100.0/24, but the specified next hop 192.0.2.14 is not reachable by any active route, and traffic drops. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. 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.
  2. Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded.
  3. The static prefix becomes active with a resolved next hop, and a sourced packet test reaches the destination through the intended interface.
  4. Counters for the targeted match increment, only the intended traffic uses the alternate next hop, and unmatched traffic stays on its original path.

Explanation

Correct Answer

C:

The static prefix becomes active with a resolved next hop, and a sourced packet test reaches the destination through the intended interface. This tests the actual condition identified in the live production incident: PE-11 has a configured static route to 198.51.100.0/24, but the specified next hop 192.0.2.14 is not reachable by any active route, and traffic drops. It is meaningful because A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface.

Incorrect Answers

A:

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. This measurement may prove the unrelated Aggregate rejection behavior condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: PE-11 has a configured static route to 198.51.100.0/24, but the specified next hop 192.0.2.14 is not reachable by any active route, and traffic drops. A relevant acceptance result here is: The static prefix becomes active with a resolved next hop, and a sourced packet test reaches the destination through the intended interface.

B:

Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded. This measurement may prove the unrelated Per-flow hash expectation condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: PE-11 has a configured static route to 198.51.100.0/24, but the specified next hop 192.0.2.14 is not reachable by any active route, and traffic drops. A relevant acceptance result here is: The static prefix becomes active with a resolved next hop, and a sourced packet test reaches the destination through the intended interface.

D:

Counters for the targeted match increment, only the intended traffic uses the alternate next hop, and unmatched traffic stays on its original path. This measurement may prove the unrelated Filter-based forwarding classification condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: PE-11 has a configured static route to 198.51.100.0/24, but the specified next hop 192.0.2.14 is not reachable by any active route, and traffic drops. A relevant acceptance result here is: The static prefix becomes active with a resolved next hop, and a sourced packet test reaches the destination through the intended interface.


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.