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 23

Question 220

During production incident triage, engineers observe: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. IS-IS Hello exchanges appear and the expected level adjacency establishes while IPv4 traffic still functions.
  2. The LSDB advertises compatible wide metrics and SPF selects the intended path across the upgraded links.
  3. A shared Level 1 or Level 2 adjacency comes up and the right set of level-specific routes is exchanged.
  4. The designated system matches the planned candidate, pseudonode LSPs are coherent, and LAN adjacencies remain stable.

Explanation

Correct Answer

C:

A shared Level 1 or Level 2 adjacency comes up and the right set of level-specific routes is exchanged. This tests the actual condition identified in the live production incident: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. It is meaningful because An IS-IS adjacency needs compatible protocol levels as well as link reachability.

Incorrect Answers

A:

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: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. A relevant acceptance result here is: A shared Level 1 or Level 2 adjacency comes up and the right set of level-specific routes is exchanged.

B:

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: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. A relevant acceptance result here is: A shared Level 1 or Level 2 adjacency comes up and the right set of level-specific routes is exchanged.

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: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. A relevant acceptance result here is: A shared Level 1 or Level 2 adjacency comes up and the right set of level-specific routes is exchanged.

Question 221

During production incident triage, engineers observe: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. The MAC stabilizes on its expected port or approved redundancy construct and packet loss disappears.
  2. A controlled untagged frame maps to the same intended VLAN on both ends and no unauthorized L2 reachability remains.
  3. Hosts reach their VLAN gateway, the IRB interface appears active, and inter-VLAN traffic follows the intended security policy.
  4. Initial flooding is VLAN-scoped, then subsequent frames to the learned MAC use the correct specific egress port.

Explanation

Correct Answer

A:

The MAC stabilizes on its expected port or approved redundancy construct and packet loss disappears. This tests the actual condition identified in the live production incident: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. It is meaningful because Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments.

Incorrect Answers

B:

A controlled untagged frame maps to the same intended VLAN on both ends and no unauthorized L2 reachability remains. This measurement may prove the unrelated Native VLAN mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. A relevant acceptance result here is: The MAC stabilizes on its expected port or approved redundancy construct and packet loss disappears.

C:

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: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. A relevant acceptance result here is: The MAC stabilizes on its expected port or approved redundancy construct and packet loss disappears.

D:

Initial flooding is VLAN-scoped, then subsequent frames to the learned MAC use the correct specific egress port. This measurement may prove the unrelated Unknown unicast flooding behavior condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. A relevant acceptance result here is: The MAC stabilizes on its expected port or approved redundancy construct and packet loss disappears.

Question 222

During production incident triage, engineers observe: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. The MAC stabilizes on its expected port or approved redundancy construct and packet loss disappears.
  2. The customer MAC and VLAN appear in the correct virtual-switch instance with no leakage into default bridging context.
  3. A controlled untagged frame maps to the same intended VLAN on both ends and no unauthorized L2 reachability remains.
  4. The CE MAC is learned in VLAN 120 and its frames reach a same-VLAN peer without leaking into VLAN 110.

Explanation

Correct Answer

C:

A controlled untagged frame maps to the same intended VLAN on both ends and no unauthorized L2 reachability remains. This tests the actual condition identified in the live production incident: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. It is meaningful because Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping.

Incorrect Answers

A:

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: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. A relevant acceptance result here is: A controlled untagged frame maps to the same intended VLAN on both ends and no unauthorized L2 reachability remains.

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: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. A relevant acceptance result here is: A controlled untagged frame maps to the same intended VLAN on both ends and no unauthorized L2 reachability remains.

D:

The CE MAC is learned in VLAN 120 and its frames reach a same-VLAN peer without leaking into VLAN 110. This measurement may prove the unrelated Access VLAN membership condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. A relevant acceptance result here is: A controlled untagged frame maps to the same intended VLAN on both ends and no unauthorized L2 reachability remains.

Question 223

During production incident triage, engineers observe: A downstream tenant switch begins sending superior BPDUs toward the provider's designated port and threatens to become root for the provider spanning tree. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. Both switches report the same region digest and expected instance-specific spanning-tree paths.
  2. A controlled root-port failure causes the expected alternate port to forward without creating a bridging loop.
  3. The violating connection is blocked or alerted according to policy while legitimate host-facing links remain available.
  4. The port enters the documented root-prevented state for superior BPDUs and recovers when the rogue advertisement stops.

Explanation

Correct Answer

D:

The port enters the documented root-prevented state for superior BPDUs and recovers when the rogue advertisement stops. This tests the actual condition identified in the live production incident: A downstream tenant switch begins sending superior BPDUs toward the provider's designated port and threatens to become root for the provider spanning tree. It is meaningful because Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path.

Incorrect Answers

A:

Both switches report the same region digest and expected instance-specific spanning-tree paths. This measurement may prove the unrelated MSTP region mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A downstream tenant switch begins sending superior BPDUs toward the provider's designated port and threatens to become root for the provider spanning tree. A relevant acceptance result here is: The port enters the documented root-prevented state for superior BPDUs and recovers when the rogue advertisement stops.

B:

A controlled root-port failure causes the expected alternate port to forward without creating a bridging loop. This measurement may prove the unrelated RSTP alternate port activation condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A downstream tenant switch begins sending superior BPDUs toward the provider's designated port and threatens to become root for the provider spanning tree. A relevant acceptance result here is: The port enters the documented root-prevented state for superior BPDUs and recovers when the rogue advertisement stops.

C:

The violating connection is blocked or alerted according to policy while legitimate host-facing links remain available. This measurement may prove the unrelated Unexpected BPDU on edge port condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A downstream tenant switch begins sending superior BPDUs toward the provider's designated port and threatens to become root for the provider spanning tree. A relevant acceptance result here is: The port enters the documented root-prevented state for superior BPDUs and recovers when the rogue advertisement stops.

Question 224

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

  1. All intended members show collecting and distributing state in the correct AE bundle and packet forwarding is stable.
  2. The designated router is primary under normal conditions and the backup takes over promptly during an injected outage.
  3. The session remains stable during representative load yet detects an injected forwarding fault within the approved interval.
  4. Failback occurs only after verified upstream reachability and virtual gateway traffic remains stable across recovery.

Explanation

Correct Answer

C:

The session remains stable during representative load yet detects an injected forwarding fault within the approved interval. This tests the actual condition identified in the live production incident: A provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. It is meaningful because BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure.

Incorrect Answers

A:

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 provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. A relevant acceptance result here is: The session remains stable during representative load yet detects an injected forwarding fault within the approved interval.

B:

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 provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. A relevant acceptance result here is: The session remains stable during representative load yet detects an injected forwarding fault within the approved interval.

D:

Failback occurs only after verified upstream reachability and virtual gateway traffic remains stable across recovery. This measurement may prove the unrelated VRRP preemption oscillation condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. A relevant acceptance result here is: The session remains stable during representative load yet detects an injected forwarding fault within the approved interval.

Question 225

During production incident triage, engineers observe: A redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. All intended members show collecting and distributing state in the correct AE bundle and packet forwarding is stable.
  2. The active member count and per-link utilization match service design, and the aggregate handles representative traffic without excessive drops.
  3. The standby RE has synchronized routing state and peer sessions stay established through a tested RE switch.
  4. The designated router is primary under normal conditions and the backup takes over promptly during an injected outage.

Explanation

Correct Answer

C:

The standby RE has synchronized routing state and peer sessions stay established through a tested RE switch. This tests the actual condition identified in the live production incident: A redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. It is meaningful because NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers.

Incorrect Answers

A:

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 redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. A relevant acceptance result here is: The standby RE has synchronized routing state and peer sessions stay established through a tested RE switch.

B:

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 redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. A relevant acceptance result here is: The standby RE has synchronized routing state and peer sessions stay established through a tested RE switch.

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 redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. A relevant acceptance result here is: The standby RE has synchronized routing state and peer sessions stay established through a tested RE switch.

Question 226

During production incident triage, engineers observe: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. The designated BGP exit wins best-path selection for the intended prefixes and backup behavior remains correct.
  2. Both peers establish an expected eBGP session and the remote AS displayed in session state matches the design.
  3. The authorized prefix appears in the neighbor's received-route view and unrelated infrastructure addresses remain absent.
  4. The rejected prefix does not appear as an eligible route while approved advertised prefixes remain available.

Explanation

Correct Answer

A:

The designated BGP exit wins best-path selection for the intended prefixes and backup behavior remains correct. This tests the actual condition identified in the live production incident: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. It is meaningful because Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility.

Incorrect Answers

B:

Both peers establish an expected eBGP session and the remote AS displayed in session state matches the design. This measurement may prove the unrelated BGP peer autonomous system mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. A relevant acceptance result here is: The designated BGP exit wins best-path selection for the intended prefixes and backup behavior remains correct.

C:

The authorized prefix appears in the neighbor's received-route view and unrelated infrastructure addresses remain absent. This measurement may prove the unrelated BGP export policy omission condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. A relevant acceptance result here is: The designated BGP exit wins best-path selection for the intended prefixes and backup behavior remains correct.

D:

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: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. A relevant acceptance result here is: The designated BGP exit wins best-path selection for the intended prefixes and backup behavior remains correct.

Question 227

During production incident triage, engineers observe: A generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. The generated default becomes active with the expected next hop only when the qualifying contributor exists.
  2. 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.
  3. Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded.
  4. With the downstream fault injected, the unsuitable backup route is withdrawn or de-preferred and valid traffic moves to the tested alternate.

Explanation

Correct Answer

A:

The generated default becomes active with the expected next hop only when the qualifying contributor exists. This tests the actual condition identified in the live production incident: A generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. It is meaningful because Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text.

Incorrect Answers

B:

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: A generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. A relevant acceptance result here is: The generated default becomes active with the expected next hop only when the qualifying contributor exists.

C:

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: A generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. A relevant acceptance result here is: The generated default becomes active with the expected next hop only when the qualifying contributor exists.

D:

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: A generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. A relevant acceptance result here is: The generated default becomes active with the expected next hop only when the qualifying contributor exists.

Question 228

During production incident triage, engineers observe: Two cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. The nodes appear with distinct system IDs and no repeated conflicting LSP originator entries in the database.
  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. LSPs from the peer remain current across normal refresh cycles and SPF paths do not disappear unexpectedly.

Explanation

Correct Answer

A:

The nodes appear with distinct system IDs and no repeated conflicting LSP originator entries in the database. This tests the actual condition identified in the live production incident: Two cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. It is meaningful because IS-IS relies on a unique system ID to identify LSP originators and topology nodes.

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 cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. A relevant acceptance result here is: The nodes appear with distinct system IDs and no repeated conflicting LSP originator entries in the database.

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 cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. A relevant acceptance result here is: The nodes appear with distinct system IDs and no repeated conflicting LSP originator entries in the database.

D:

LSPs from the peer remain current across normal refresh cycles and SPF paths do not disappear unexpectedly. This measurement may prove the unrelated IS-IS LSP lifetime anomaly condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. A relevant acceptance result here is: The nodes appear with distinct system IDs and no repeated conflicting LSP originator entries in the database.

Question 229

During production incident triage, engineers observe: Two routers have interface-based GRE tunnels, but the source address on one end does not match the destination configured on the remote end. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. Large application packets traverse the tunnel without blackholing, and measured payload size respects the underlay capacity.
  2. A validated encryption layer protects inner payload on the monitored underlay while GRE routing still functions as designed.
  3. An underlay path reaches the outer peer without circular routing and inner GRE packets are successfully decapsulated.
  4. Packet captures show the expected outer GRE addresses and matching decapsulation counts on the peer.

Explanation

Correct Answer

D:

Packet captures show the expected outer GRE addresses and matching decapsulation counts on the peer. This tests the actual condition identified in the live production incident: Two routers have interface-based GRE tunnels, but the source address on one end does not match the destination configured on the remote end. It is meaningful because GRE encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel.

Incorrect Answers

A:

Large application packets traverse the tunnel without blackholing, and measured payload size respects the underlay capacity. This measurement may prove the unrelated GRE encapsulation MTU overhead condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two routers have interface-based GRE tunnels, but the source address on one end does not match the destination configured on the remote end. A relevant acceptance result here is: Packet captures show the expected outer GRE addresses and matching decapsulation counts on the peer.

B:

A validated encryption layer protects inner payload on the monitored underlay while GRE routing still functions as designed. This measurement may prove the unrelated GRE confidentiality misconception condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two routers have interface-based GRE tunnels, but the source address on one end does not match the destination configured on the remote end. A relevant acceptance result here is: Packet captures show the expected outer GRE addresses and matching decapsulation counts on the peer.

C:

An underlay path reaches the outer peer without circular routing and inner GRE packets are successfully decapsulated. This measurement may prove the unrelated GRE underlay recursive loss condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two routers have interface-based GRE tunnels, but the source address on one end does not match the destination configured on the remote end. A relevant acceptance result here is: Packet captures show the expected outer GRE addresses and matching decapsulation counts on the peer.

Question 230

During production incident triage, engineers observe: A customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. The static prefix becomes active with a resolved next hop, and a sourced packet test reaches the destination through the intended interface.
  2. Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded.
  3. The aggregate appears as an active route with contributing prefixes shown, and the permitted summary is advertised to the intended peer.
  4. The generated default becomes active with the expected next hop only when the qualifying contributor exists.

Explanation

Correct Answer

B:

Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded. This tests the actual condition identified in the live production incident: A customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. It is meaningful because Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths.

Incorrect Answers

A:

The static prefix becomes active with a resolved next hop, and a sourced packet test reaches the destination through the intended interface. This measurement may prove the unrelated Recursive next-hop resolution condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. A relevant acceptance result here is: Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded.

C:

The aggregate appears as an active route with contributing prefixes shown, and the permitted summary is advertised to the intended peer. This measurement may prove the unrelated Aggregate route contribution condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. A relevant acceptance result here is: Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded.

D:

The generated default becomes active with the expected next hop only when the qualifying contributor exists. This measurement may prove the unrelated Generated default route prerequisite condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. A relevant acceptance result here is: Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded.


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.