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 71

Question 700

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU.
  2. GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls.
  3. GRE encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel.
  4. GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable.

Explanation

Correct Answer

A:

GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU. This principle directly explains the controlled acceptance rehearsal: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. The aligned engineering response is: Correct tunnel MTU or MSS considerations and verify fragmentation or PMTU behavior for the specific supported platform. The result should be established through: Large application packets traverse the tunnel without blackholing, and measured payload size respects the underlay capacity.

Incorrect Answers

B:

GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls. That explanation applies to the different GRE confidentiality misconception scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. The controlling mechanism is instead: GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU. The correct response would be: Correct tunnel MTU or MSS considerations and verify fragmentation or PMTU behavior for the specific supported platform.

C:

GRE encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel. That explanation applies to the different GRE tunnel endpoint mismatch scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. The controlling mechanism is instead: GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU. The correct response would be: Correct tunnel MTU or MSS considerations and verify fragmentation or PMTU behavior for the specific supported platform.

D:

GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable. That explanation applies to the different GRE underlay recursive loss scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. The controlling mechanism is instead: GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU. The correct response would be: Correct tunnel MTU or MSS considerations and verify fragmentation or PMTU behavior for the specific supported platform.

Question 701

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An LDP session is operational, but a destination FEC lacks the usable outgoing label that an ingress PE expects to use. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. The bypass LSP is operational before fault injection and protected traffic follows the bypass after the link is disabled.
  2. The observed label stack and forwarding path match the documented shortest path or the specified explicit segment list.
  3. The relevant FEC has a reachable next hop and valid incoming and outgoing label entries along the intended LSP.
  4. A captured or traced packet reaches the egress with the expected explicit-null label and traffic-class handling.

Explanation

Correct Answer

C:

The relevant FEC has a reachable next hop and valid incoming and outgoing label entries along the intended LSP. This tests the actual condition identified in the controlled acceptance rehearsal: An LDP session is operational, but a destination FEC lacks the usable outgoing label that an ingress PE expects to use. It is meaningful because LDP maps forwarding equivalence classes to labels learned from the downstream next hop; a session can be up without an applicable mapping for every FEC.

Incorrect Answers

A:

The bypass LSP is operational before fault injection and protected traffic follows the bypass after the link is disabled. This measurement may prove the unrelated RSVP link protection plan condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: An LDP session is operational, but a destination FEC lacks the usable outgoing label that an ingress PE expects to use. A relevant acceptance result here is: The relevant FEC has a reachable next hop and valid incoming and outgoing label entries along the intended LSP.

B:

The observed label stack and forwarding path match the documented shortest path or the specified explicit segment list. This measurement may prove the unrelated SR-MPLS node-SID shortest path condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: An LDP session is operational, but a destination FEC lacks the usable outgoing label that an ingress PE expects to use. A relevant acceptance result here is: The relevant FEC has a reachable next hop and valid incoming and outgoing label entries along the intended LSP.

D:

A captured or traced packet reaches the egress with the expected explicit-null label and traffic-class handling. This measurement may prove the unrelated Explicit-null forwarding condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: An LDP session is operational, but a destination FEC lacks the usable outgoing label that an ingress PE expects to use. A relevant acceptance result here is: The relevant FEC has a reachable next hop and valid incoming and outgoing label entries along the intended LSP.

Question 702

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. The multihop session forms between the designed IP endpoints, TTL is appropriate and only intended neighbors can connect.
  2. A route detail comparison shows the relevant AS-path difference and chosen path conforms to approved policy.
  3. The rejected prefix does not appear as an eligible route while approved advertised prefixes remain available.
  4. The peer exchanges approved IPv6 routes and their next hops resolve into inet6.0 without exposing unintended prefixes.

Explanation

Correct Answer

B:

A route detail comparison shows the relevant AS-path difference and chosen path conforms to approved policy. This tests the actual condition identified in the controlled acceptance rehearsal: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. It is meaningful because When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers.

Incorrect Answers

A:

The multihop session forms between the designed IP endpoints, TTL is appropriate and only intended neighbors can connect. This measurement may prove the unrelated EBGP multihop peering condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. A relevant acceptance result here is: A route detail comparison shows the relevant AS-path difference and chosen path conforms to approved policy.

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 controlled acceptance rehearsal was resolved. The specific observed fault is: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. A relevant acceptance result here is: A route detail comparison shows the relevant AS-path difference and chosen path conforms to approved policy.

D:

The peer exchanges approved IPv6 routes and their next hops resolve into inet6.0 without exposing unintended prefixes. This measurement may prove the unrelated BGP IPv6 family inactive condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. A relevant acceptance result here is: A route detail comparison shows the relevant AS-path difference and chosen path conforms to approved policy.

Question 703

During a controlled acceptance rehearsal of the same defect on a separate test network, 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. 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. Internal prefixes remain present, the designed default is learned, and external traffic follows that default without type-5 LSAs in the stub.
  4. The specifically allowed customer prefix appears as the expected external route on the peer, while other connected networks stay unadvertised.

Explanation

Correct Answer

C:

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 controlled acceptance rehearsal: 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:

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 controlled acceptance rehearsal 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.

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 controlled acceptance rehearsal 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:

The specifically allowed customer prefix appears as the expected external route on the peer, while other connected networks stay unadvertised. This measurement may prove the unrelated OSPF export policy omission condition, but it does not demonstrate that the current controlled acceptance rehearsal 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 704

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. Calculated path costs and the active next hop match the expected path, and failover still uses a valid alternate.
  2. The specifically allowed customer prefix appears as the expected external route on the peer, while other connected networks stay unadvertised.
  3. The routers advertise distinct IDs, neighbors remain Full and the LSDB no longer shows conflicting origins.
  4. No OSPF neighbors form on the customer LAN, yet core routers still learn the intended LAN prefix.

Explanation

Correct Answer

A:

Calculated path costs and the active next hop match the expected path, and failover still uses a valid alternate. This tests the actual condition identified in the controlled acceptance rehearsal: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. It is meaningful because OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric.

Incorrect Answers

B:

The specifically allowed customer prefix appears as the expected external route on the peer, while other connected networks stay unadvertised. This measurement may prove the unrelated OSPF export policy omission condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. A relevant acceptance result here is: Calculated path costs and the active next hop match the expected path, and failover still uses a valid alternate.

C:

The routers advertise distinct IDs, neighbors remain Full and the LSDB no longer shows conflicting origins. This measurement may prove the unrelated Duplicate OSPF router identifier condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. A relevant acceptance result here is: Calculated path costs and the active next hop match the expected path, and failover still uses a valid alternate.

D:

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 controlled acceptance rehearsal was resolved. The specific observed fault is: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. A relevant acceptance result here is: Calculated path costs and the active next hop match the expected path, and failover still uses a valid alternate.

Question 705

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. The egress receives the expected payload context and end-to-end service passes despite the absence of a top transport label.
  2. The segment identifier is visible in the IGP database, resolves to the correct label, and traffic reaches the selected node.
  3. The LSP reserves its intended bandwidth end to end without exceeding the engineered link limits.
  4. The bypass LSP is operational before fault injection and protected traffic follows the bypass after the link is disabled.

Explanation

Correct Answer

B:

The segment identifier is visible in the IGP database, resolves to the correct label, and traffic reaches the selected node. This tests the actual condition identified in the controlled acceptance rehearsal: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. It is meaningful because SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels.

Incorrect Answers

A:

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 controlled acceptance rehearsal was resolved. The specific observed fault is: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. A relevant acceptance result here is: The segment identifier is visible in the IGP database, resolves to the correct label, and traffic reaches the selected node.

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 controlled acceptance rehearsal was resolved. The specific observed fault is: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. A relevant acceptance result here is: The segment identifier is visible in the IGP database, resolves to the correct label, and traffic reaches the selected node.

D:

The bypass LSP is operational before fault injection and protected traffic follows the bypass after the link is disabled. This measurement may prove the unrelated RSVP link protection plan condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. A relevant acceptance result here is: The segment identifier is visible in the IGP database, resolves to the correct label, and traffic reaches the selected node.

Question 706

During a controlled acceptance rehearsal of the same defect on a separate test network, 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. The violating connection is blocked or alerted according to policy while legitimate host-facing links remain available.
  2. Each VLAN reports its planned root and forwarding links with no loops during a controlled failover.
  3. The protected port remains safe during the simulated BPDU loss and returns to normal after signaling is restored.
  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 controlled acceptance rehearsal: 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:

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 controlled acceptance rehearsal 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:

Each VLAN reports its planned root and forwarding links with no loops during a controlled failover. This measurement may prove the unrelated Per-VLAN spanning-tree path condition, but it does not demonstrate that the current controlled acceptance rehearsal 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 protected port remains safe during the simulated BPDU loss and returns to normal after signaling is restored. This measurement may prove the unrelated Loop protection after BPDU loss condition, but it does not demonstrate that the current controlled acceptance rehearsal 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 707

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. The egress receives the expected payload context and end-to-end service passes despite the absence of a top transport label.
  2. A captured or traced packet reaches the egress with the expected explicit-null label and traffic-class handling.
  3. Expected LDP discovery packets and TCP session are present on the correct link, and relevant FEC labels are learned.
  4. The RSVP LSP becomes operational on the authorized explicit route and reports a complete signaled path.

Explanation

Correct Answer

C:

Expected LDP discovery packets and TCP session are present on the correct link, and relevant FEC labels are learned. This tests the actual condition identified in the controlled acceptance rehearsal: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. It is meaningful because LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation.

Incorrect Answers

A:

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 controlled acceptance rehearsal was resolved. The specific observed fault is: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. A relevant acceptance result here is: Expected LDP discovery packets and TCP session are present on the correct link, and relevant FEC labels are learned.

B:

A captured or traced packet reaches the egress with the expected explicit-null label and traffic-class handling. This measurement may prove the unrelated Explicit-null forwarding condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. A relevant acceptance result here is: Expected LDP discovery packets and TCP session are present on the correct link, and relevant FEC labels are learned.

D:

The RSVP LSP becomes operational on the authorized explicit route and reports a complete signaled path. This measurement may prove the unrelated RSVP-TE constrained path missing condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. A relevant acceptance result here is: Expected LDP discovery packets and TCP session are present on the correct link, and relevant FEC labels are learned.

Question 708

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. Forward and reverse tests each map to separately verified forwarding paths with their intended egress destinations.
  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:

Forward and reverse tests each map to separately verified forwarding paths with their intended egress destinations. This tests the actual condition identified in the controlled acceptance rehearsal: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. It is meaningful because RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP.

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 controlled acceptance rehearsal was resolved. The specific observed fault is: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. A relevant acceptance result here is: Forward and reverse tests each map to separately verified forwarding paths with their intended egress destinations.

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 controlled acceptance rehearsal was resolved. The specific observed fault is: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. A relevant acceptance result here is: Forward and reverse tests each map to separately verified forwarding paths with their intended egress destinations.

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 controlled acceptance rehearsal was resolved. The specific observed fault is: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. A relevant acceptance result here is: Forward and reverse tests each map to separately verified forwarding paths with their intended egress destinations.

Question 709

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. Calculated path costs and the active next hop match the expected path, and failover still uses a valid alternate.
  2. The two interfaces report matching timers and the neighbor stays Full beyond several dead intervals.
  3. Both sides report compatible MTU and move through Exchange to Full with a synchronized LSDB.
  4. The specifically allowed customer prefix appears as the expected external route on the peer, while other connected networks stay unadvertised.

Explanation

Correct Answer

B:

The two interfaces report matching timers and the neighbor stays Full beyond several dead intervals. This tests the actual condition identified in the controlled acceptance rehearsal: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. It is meaningful because OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance.

Incorrect Answers

A:

Calculated path costs and the active next hop match the expected path, and failover still uses a valid alternate. This measurement may prove the unrelated OSPF metric path preference condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. A relevant acceptance result here is: The two interfaces report matching timers and the neighbor stays Full beyond several dead intervals.

C:

Both sides report compatible MTU and move through Exchange to Full with a synchronized LSDB. This measurement may prove the unrelated OSPF MTU ExStart stall condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. A relevant acceptance result here is: The two interfaces report matching timers and the neighbor stays Full beyond several dead intervals.

D:

The specifically allowed customer prefix appears as the expected external route on the peer, while other connected networks stay unadvertised. This measurement may prove the unrelated OSPF export policy omission condition, but it does not demonstrate that the current controlled acceptance rehearsal was resolved. The specific observed fault is: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. A relevant acceptance result here is: The two interfaces report matching timers and the neighbor stays Full beyond several dead intervals.

Question 710

During a controlled acceptance rehearsal of the same defect on a separate test network, 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. The session remains stable during representative load yet detects an injected forwarding fault within the approved interval.
  2. The designated router is primary under normal conditions and the backup takes over promptly during an injected outage.
  3. A controlled RE switchover maintains data-plane forwarding and routing neighbor continuity according to the selected supported feature set.
  4. The standby RE has synchronized routing state and peer sessions stay established through a tested RE switch.

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 controlled acceptance rehearsal: 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:

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 controlled acceptance rehearsal 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:

A controlled RE switchover maintains data-plane forwarding and routing neighbor continuity according to the selected supported feature set. This measurement may prove the unrelated GRES forwarding versus routing continuity condition, but it does not demonstrate that the current controlled acceptance rehearsal 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 standby RE has synchronized routing state and peer sessions stay established through a tested RE switch. This measurement may prove the unrelated NSR backup routing synchronization condition, but it does not demonstrate that the current controlled acceptance rehearsal 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.