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 21

Question 200

During production incident triage, engineers observe: A prefix is received from a valid BGP peer but remains unusable because the advertised BGP next hop has no resolving route in the local table. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering.
  2. BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection.
  3. An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers.
  4. BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice.

Explanation

Correct Answer

B:

BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection. This principle directly explains the live production incident: A prefix is received from a valid BGP peer but remains unusable because the advertised BGP next hop has no resolving route in the local table. The aligned engineering response is: Restore IGP or static reachability for the intended BGP next hop, or apply the correct next-hop policy where design requires it. The result should be established through: The received BGP route resolves its next hop, becomes eligible, and forwards over the designed path.

Incorrect Answers

A:

BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering. That explanation applies to the different BGP TCP transport blocked scenario rather than this live production incident. The current fault evidence is: A prefix is received from a valid BGP peer but remains unusable because the advertised BGP next hop has no resolving route in the local table. The controlling mechanism is instead: BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection. The correct response would be: Restore IGP or static reachability for the intended BGP next hop, or apply the correct next-hop policy where design requires it.

C:

An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers. That explanation applies to the different EBGP multihop peering scenario rather than this live production incident. The current fault evidence is: A prefix is received from a valid BGP peer but remains unusable because the advertised BGP next hop has no resolving route in the local table. The controlling mechanism is instead: BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection. The correct response would be: Restore IGP or static reachability for the intended BGP next hop, or apply the correct next-hop policy where design requires it.

D:

BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice. That explanation applies to the different BGP import policy leak scenario rather than this live production incident. The current fault evidence is: A prefix is received from a valid BGP peer but remains unusable because the advertised BGP next hop has no resolving route in the local table. The controlling mechanism is instead: BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection. The correct response would be: Restore IGP or static reachability for the intended BGP next hop, or apply the correct next-hop policy where design requires it.

Question 201

During production incident triage, engineers observe: PE-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. 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. Counters for the targeted match increment, only the intended traffic uses the alternate next hop, and unmatched traffic stays on its original path.
  3. Matched and unmatched packet samples increment their intended counters and resolve to the expected respective routing tables.
  4. The aggregate appears as an active route with contributing prefixes shown, and the permitted summary is advertised to the intended peer.

Explanation

Correct Answer

D:

The aggregate appears as an active route with contributing prefixes shown, and the permitted summary is advertised to the intended peer. This tests the actual condition identified in the live production incident: PE-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. It is meaningful because A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active.

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: PE-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. A relevant acceptance result here is: The aggregate appears as an active route with contributing prefixes shown, and the permitted summary is advertised to the intended peer.

B:

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-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. A relevant acceptance result here is: The aggregate appears as an active route with contributing prefixes shown, and the permitted summary is advertised to the intended peer.

C:

Matched and unmatched packet samples increment their intended counters and resolve to the expected respective routing tables. This measurement may prove the unrelated Filter policy overmatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: PE-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. A relevant acceptance result here is: The aggregate appears as an active route with contributing prefixes shown, and the permitted summary is advertised to the intended peer.

Question 202

During production incident triage, engineers observe: PE-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. The selected active prefix shows the intended protocol, route preference, and forwarding next hop both before and after a controlled failover.
  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. The forwarding table shows both expected next hops and representative flows use the authorized paths without loop or asymmetry problems.
  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

A:

The selected active prefix shows the intended protocol, route preference, and forwarding next hop both before and after a controlled failover. This tests the actual condition identified in the live production incident: PE-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. It is meaningful because For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference.

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: PE-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. A relevant acceptance result here is: The selected active prefix shows the intended protocol, route preference, and forwarding next hop both before and after a controlled failover.

C:

The forwarding table shows both expected next hops and representative flows use the authorized paths without loop or asymmetry problems. This measurement may prove the unrelated Equal-cost multipath eligibility condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: PE-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. A relevant acceptance result here is: The selected active prefix shows the intended protocol, route preference, and forwarding next hop both before and after a controlled failover.

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-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. A relevant acceptance result here is: The selected active prefix shows the intended protocol, route preference, and forwarding next hop both before and after a controlled failover.

Question 203

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

  1. Expected LDP discovery packets and TCP session are present on the correct link, and relevant FEC labels are learned.
  2. An LDP session reaches Operational and displays the intended neighbor label bindings after selective filter correction.
  3. The LSP reserves its intended bandwidth end to end without exceeding the engineered link limits.
  4. A captured or traced packet reaches the egress with the expected explicit-null label and traffic-class handling.

Explanation

Correct Answer

D:

A captured or traced packet reaches the egress with the expected explicit-null label and traffic-class handling. This tests the actual condition identified in the live production incident: A service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. It is meaningful because Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping.

Incorrect Answers

A:

Expected LDP discovery packets and TCP session are present on the correct link, and relevant FEC labels are learned. This measurement may prove the unrelated LDP discovery and IGP mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. A relevant acceptance result here is: A captured or traced packet reaches the egress with the expected explicit-null label and traffic-class handling.

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: A service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. A relevant acceptance result here is: A captured or traced packet reaches the egress with the expected explicit-null label and traffic-class handling.

C:

The LSP reserves its intended bandwidth end to end without exceeding the engineered link limits. This measurement may prove the unrelated RSVP reservable bandwidth shortage condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. A relevant acceptance result here is: A captured or traced packet reaches the egress with the expected explicit-null label and traffic-class handling.

Question 204

During production incident triage, engineers observe: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. Both peers establish an expected eBGP session and the remote AS displayed in session state matches the design.
  2. The designated BGP exit wins best-path selection for the intended prefixes and backup behavior remains correct.
  3. A route detail comparison shows the relevant AS-path difference and chosen path conforms to approved policy.
  4. The rejected prefix does not appear as an eligible route while approved advertised prefixes remain available.

Explanation

Correct Answer

A:

Both peers establish an expected eBGP session and the remote AS displayed in session state matches the design. This tests the actual condition identified in the live production incident: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. It is meaningful because BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session.

Incorrect Answers

B:

The designated BGP exit wins best-path selection for the intended prefixes and backup behavior remains correct. This measurement may prove the unrelated BGP local preference egress condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. A relevant acceptance result here is: Both peers establish an expected eBGP session and the remote AS displayed in session state matches the design.

C:

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: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. A relevant acceptance result here is: Both peers establish an expected eBGP session and the remote AS displayed in session state matches the design.

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: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. A relevant acceptance result here is: Both peers establish an expected eBGP session and the remote AS displayed in session state matches the design.

Question 205

During production incident triage, engineers observe: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. No OSPF neighbors form on the customer LAN, yet core routers still learn the intended LAN prefix.
  2. Both peers reach Full adjacency in the same area and the intended routes are learned.
  3. An appropriate eligible router becomes DR or BDR after a controlled election and neighbor adjacency remains stable.
  4. Internal prefixes remain present, the designed default is learned, and external traffic follows that default without type-5 LSAs in the stub.

Explanation

Correct Answer

C:

An appropriate eligible router becomes DR or BDR after a controlled election and neighbor adjacency remains stable. This tests the actual condition identified in the live production incident: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. It is meaningful because OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links.

Incorrect Answers

A:

No OSPF neighbors form on the customer LAN, yet core routers still learn the intended LAN prefix. This measurement may prove the unrelated OSPF passive interface condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. A relevant acceptance result here is: An appropriate eligible router becomes DR or BDR after a controlled election and neighbor adjacency remains stable.

B:

Both peers reach Full adjacency in the same area and the intended routes are learned. This measurement may prove the unrelated OSPF area ID mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. A relevant acceptance result here is: An appropriate eligible router becomes DR or BDR after a controlled election and neighbor adjacency remains stable.

D:

Internal prefixes remain present, the designed default is learned, and external traffic follows that default without type-5 LSAs in the stub. This measurement may prove the unrelated Stub area external LSA expectation condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. A relevant acceptance result here is: An appropriate eligible router becomes DR or BDR after a controlled election and neighbor adjacency remains stable.

Question 206

During production incident triage, engineers observe: A redundant link should resume traffic when the active path fails, but the switch stays blocked because engineers confuse RSTP alternate and edge port roles. 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 intended core device is reported as root and a designated backup root is stable after an election test.
  4. The port enters the documented root-prevented state for superior BPDUs and recovers when the rogue advertisement stops.

Explanation

Correct Answer

B:

A controlled root-port failure causes the expected alternate port to forward without creating a bridging loop. This tests the actual condition identified in the live production incident: A redundant link should resume traffic when the active path fails, but the switch stays blocked because engineers confuse RSTP alternate and edge port roles. It is meaningful because RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails.

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 redundant link should resume traffic when the active path fails, but the switch stays blocked because engineers confuse RSTP alternate and edge port roles. A relevant acceptance result here is: A controlled root-port failure causes the expected alternate port to forward without creating a bridging loop.

C:

The intended core device is reported as root and a designated backup root is stable after an election test. This measurement may prove the unrelated Root bridge election priority condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A redundant link should resume traffic when the active path fails, but the switch stays blocked because engineers confuse RSTP alternate and edge port roles. A relevant acceptance result here is: A controlled root-port failure causes the expected alternate port to forward without creating a bridging loop.

D:

The port enters the documented root-prevented state for superior BPDUs and recovers when the rogue advertisement stops. This measurement may prove the unrelated Root protection against rogue core condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A redundant link should resume traffic when the active path fails, but the switch stays blocked because engineers confuse RSTP alternate and edge port roles. A relevant acceptance result here is: A controlled root-port failure causes the expected alternate port to forward without creating a bridging loop.

Question 207

During production incident triage, engineers observe: A remote BGP peer repeatedly closes sessions after sporadic delays, and operations incorrectly assume the configured hold timers on both routers must be identical even though negotiation occurs. 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. The negotiated hold time is visible and the session remains Established under representative transport jitter without spurious expiry.
  3. A route detail comparison shows the relevant AS-path difference and chosen path conforms to approved policy.
  4. The best path matches the documented MED comparison scope and the selected inbound preference is confirmed with peer attributes.

Explanation

Correct Answer

B:

The negotiated hold time is visible and the session remains Established under representative transport jitter without spurious expiry. This tests the actual condition identified in the live production incident: A remote BGP peer repeatedly closes sessions after sporadic delays, and operations incorrectly assume the configured hold timers on both routers must be identical even though negotiation occurs. It is meaningful because BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long.

Incorrect Answers

A:

The designated BGP exit wins best-path selection for the intended prefixes and backup behavior remains correct. This measurement may prove the unrelated BGP local preference egress condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A remote BGP peer repeatedly closes sessions after sporadic delays, and operations incorrectly assume the configured hold timers on both routers must be identical even though negotiation occurs. A relevant acceptance result here is: The negotiated hold time is visible and the session remains Established under representative transport jitter without spurious expiry.

C:

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 remote BGP peer repeatedly closes sessions after sporadic delays, and operations incorrectly assume the configured hold timers on both routers must be identical even though negotiation occurs. A relevant acceptance result here is: The negotiated hold time is visible and the session remains Established under representative transport jitter without spurious expiry.

D:

The best path matches the documented MED comparison scope and the selected inbound preference is confirmed with peer attributes. This measurement may prove the unrelated BGP MED comparison scope condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A remote BGP peer repeatedly closes sessions after sporadic delays, and operations incorrectly assume the configured hold timers on both routers must be identical even though negotiation occurs. A relevant acceptance result here is: The negotiated hold time is visible and the session remains Established under representative transport jitter without spurious expiry.

Question 208

During production incident triage, engineers observe: An operations team expects a type-5 external route inside an OSPF stub area and reports the absence as an interface failure. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. The two interfaces report matching timers and the neighbor stays Full beyond several dead intervals.
  2. Internal prefixes remain present, the designed default is learned, and external traffic follows that default without type-5 LSAs in the stub.
  3. An appropriate eligible router becomes DR or BDR after a controlled election and neighbor adjacency remains stable.
  4. Both peers show the expected current LSAs with consistent sequence and topology, and the computed path reaches the destination.

Explanation

Correct Answer

B:

Internal prefixes remain present, the designed default is learned, and external traffic follows that default without type-5 LSAs in the stub. This tests the actual condition identified in the live production incident: An operations team expects a type-5 external route inside an OSPF stub area and reports the absence as an interface failure. It is meaningful because OSPF stub areas intentionally restrict external LSAs and normally rely on appropriate default reachability from an ABR for external destinations.

Incorrect Answers

A:

The two interfaces report matching timers and the neighbor stays Full beyond several dead intervals. This measurement may prove the unrelated OSPF hello dead timer mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An operations team expects a type-5 external route inside an OSPF stub area and reports the absence as an interface failure. A relevant acceptance result here is: Internal prefixes remain present, the designed default is learned, and external traffic follows that default without type-5 LSAs in the stub.

C:

An appropriate eligible router becomes DR or BDR after a controlled election and neighbor adjacency remains stable. This measurement may prove the unrelated DR priority zero misconception condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An operations team expects a type-5 external route inside an OSPF stub area and reports the absence as an interface failure. A relevant acceptance result here is: Internal prefixes remain present, the designed default is learned, and external traffic follows that default without type-5 LSAs in the stub.

D:

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: An operations team expects a type-5 external route inside an OSPF stub area and reports the absence as an interface failure. A relevant acceptance result here is: Internal prefixes remain present, the designed default is learned, and external traffic follows that default without type-5 LSAs in the stub.

Question 209

During production incident triage, engineers observe: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. The selected active prefix shows the intended protocol, route preference, and forwarding next hop both before and after a controlled failover.
  2. Matched and unmatched packet samples increment their intended counters and resolve to the expected respective routing tables.
  3. The aggregate appears as an active route with contributing prefixes shown, and the permitted summary is advertised to the intended peer.
  4. The forwarding table shows both expected next hops and representative flows use the authorized paths without loop or asymmetry problems.

Explanation

Correct Answer

B:

Matched and unmatched packet samples increment their intended counters and resolve to the expected respective routing tables. This tests the actual condition identified in the live production incident: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. It is meaningful because Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules.

Incorrect Answers

A:

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: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. A relevant acceptance result here is: Matched and unmatched packet samples increment their intended counters and resolve to the expected respective routing tables.

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 filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. A relevant acceptance result here is: Matched and unmatched packet samples increment their intended counters and resolve to the expected respective routing tables.

D:

The forwarding table shows both expected next hops and representative flows use the authorized paths without loop or asymmetry problems. This measurement may prove the unrelated Equal-cost multipath eligibility condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. A relevant acceptance result here is: Matched and unmatched packet samples increment their intended counters and resolve to the expected respective routing tables.

Question 210

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. 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 active member count and per-link utilization match service design, and the aggregate handles representative traffic without excessive drops.
  4. The session remains stable during representative load yet detects an injected forwarding fault within the approved interval.

Explanation

Correct Answer

B:

The designated router is primary under normal conditions and the backup takes over promptly during an injected outage. This tests the actual condition identified in the live production incident: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. It is meaningful because VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway.

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: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. A relevant acceptance result here is: The designated router is primary under normal conditions and the backup takes over promptly during an injected outage.

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: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. A relevant acceptance result here is: The designated router is primary under normal conditions and the backup takes over promptly during an injected outage.

D:

The session remains stable during representative load yet detects an injected forwarding fault within the approved interval. This measurement may prove the unrelated BFD detect timer too aggressive condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. A relevant acceptance result here is: The designated router is primary under normal conditions and the backup takes over promptly during an injected outage.


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.