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 28

Question 270

During production incident triage, engineers observe: A newly connected CE sends traffic to a destination MAC not yet learned in its VLAN, and operators mistake the initial flooding for a routing loop. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. Initial flooding is VLAN-scoped, then subsequent frames to the learned MAC use the correct specific egress port.
  2. The MAC stabilizes on its expected port or approved redundancy construct and packet loss disappears.
  3. The customer MAC and VLAN appear in the correct virtual-switch instance with no leakage into default bridging context.
  4. Captured handoff frames carry the agreed outer tag and correct inner VLAN values and pass only the authorized service.

Explanation

Correct Answer

A:

Initial flooding is VLAN-scoped, then subsequent frames to the learned MAC use the correct specific egress port. This tests the actual condition identified in the live production incident: A newly connected CE sends traffic to a destination MAC not yet learned in its VLAN, and operators mistake the initial flooding for a routing loop. It is meaningful because A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic.

Incorrect Answers

B:

The MAC stabilizes on its expected port or approved redundancy construct and packet loss disappears. This measurement may prove the unrelated MAC move instability condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A newly connected CE sends traffic to a destination MAC not yet learned in its VLAN, and operators mistake the initial flooding for a routing loop. A relevant acceptance result here is: Initial flooding is VLAN-scoped, then subsequent frames to the learned MAC use the correct specific egress port.

C:

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: A newly connected CE sends traffic to a destination MAC not yet learned in its VLAN, and operators mistake the initial flooding for a routing loop. A relevant acceptance result here is: Initial flooding is VLAN-scoped, then subsequent frames to the learned MAC use the correct specific egress port.

D:

Captured handoff frames carry the agreed outer tag and correct inner VLAN values and pass only the authorized service. This measurement may prove the unrelated Q-in-Q outer tag mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A newly connected CE sends traffic to a destination MAC not yet learned in its VLAN, and operators mistake the initial flooding for a routing loop. A relevant acceptance result here is: Initial flooding is VLAN-scoped, then subsequent frames to the learned MAC use the correct specific egress port.

Question 271

During production incident triage, engineers observe: A provider virtual-switch routing instance is configured but one interface remains attached to the default switching context, so tenant MAC learning is fragmented. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. A controlled untagged frame maps to the same intended VLAN on both ends and no unauthorized L2 reachability remains.
  2. Per-unit counters and a packet capture demonstrate each authorized VLAN tag reaches its mapped logical interface.
  3. The customer MAC and VLAN appear in the correct virtual-switch instance with no leakage into default bridging context.
  4. Initial flooding is VLAN-scoped, then subsequent frames to the learned MAC use the correct specific egress port.

Explanation

Correct Answer

C:

The customer MAC and VLAN appear in the correct virtual-switch instance with no leakage into default bridging context. This tests the actual condition identified in the live production incident: A provider virtual-switch routing instance is configured but one interface remains attached to the default switching context, so tenant MAC learning is fragmented. It is meaningful because Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned.

Incorrect Answers

A:

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 provider virtual-switch routing instance is configured but one interface remains attached to the default switching context, so tenant MAC learning is fragmented. A relevant acceptance result here is: The customer MAC and VLAN appear in the correct virtual-switch instance with no leakage into default bridging context.

B:

Per-unit counters and a packet capture demonstrate each authorized VLAN tag reaches its mapped logical interface. This measurement may prove the unrelated Flexible VLAN tagging logical units condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A provider virtual-switch routing instance is configured but one interface remains attached to the default switching context, so tenant MAC learning is fragmented. A relevant acceptance result here is: The customer MAC and VLAN appear in the correct virtual-switch instance with no leakage into default bridging context.

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 provider virtual-switch routing instance is configured but one interface remains attached to the default switching context, so tenant MAC learning is fragmented. A relevant acceptance result here is: The customer MAC and VLAN appear in the correct virtual-switch instance with no leakage into default bridging context.

Question 272

During production incident triage, engineers observe: A provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. 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. Counters for the targeted match increment, only the intended traffic uses the alternate next hop, and unmatched traffic stays on its original path.
  3. The aggregate appears as an active route with contributing prefixes shown, and the permitted summary is advertised to the intended peer.
  4. The prefix is absent from permitted active forwarding while legitimate nearby routes remain reachable and logged rejection evidence matches policy.

Explanation

Correct Answer

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 tests the actual condition identified in the live production incident: A provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. It is meaningful because Filter-based forwarding selects a routing table based on matched packet fields at the ingress point; the selected table must contain a usable destination route.

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 provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. A relevant acceptance result here is: Counters for the targeted match increment, only the intended traffic uses the alternate next hop, and unmatched traffic stays on its original path.

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 provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. A relevant acceptance result here is: Counters for the targeted match increment, only the intended traffic uses the alternate next hop, and unmatched traffic stays on its original path.

D:

The prefix is absent from permitted active forwarding while legitimate nearby routes remain reachable and logged rejection evidence matches policy. This measurement may prove the unrelated Martian-address acceptance condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. A relevant acceptance result here is: Counters for the targeted match increment, only the intended traffic uses the alternate next hop, and unmatched traffic stays on its original path.

Question 273

During production incident triage, 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. Both peers establish an expected eBGP session and the remote AS displayed in session state matches the design.
  2. A TCP session is established to the correct neighbor address, BGP reaches Established and intended routes are exchanged.
  3. The multihop session forms between the designed IP endpoints, TTL is appropriate and only intended neighbors can connect.
  4. A route detail comparison shows the relevant AS-path difference and chosen path conforms to approved policy.

Explanation

Correct Answer

D:

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 live production incident: 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:

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: 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.

B:

A TCP session is established to the correct neighbor address, BGP reaches Established and intended routes are exchanged. This measurement may prove the unrelated BGP TCP transport blocked condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A 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 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 live production incident 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 274

During production incident triage, engineers observe: On an IS-IS broadcast LAN, an unintended router acts as the designated intermediate system because its interface priority differs from the design. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. The two devices show an up adjacency at the intended level and their Level 1 link-state databases exchange reachability.
  2. The designated system matches the planned candidate, pseudonode LSPs are coherent, and LAN adjacencies remain stable.
  3. A shared Level 1 or Level 2 adjacency comes up and the right set of level-specific routes is exchanged.
  4. The LSDB advertises compatible wide metrics and SPF selects the intended path across the upgraded links.

Explanation

Correct Answer

B:

The designated system matches the planned candidate, pseudonode LSPs are coherent, and LAN adjacencies remain stable. This tests the actual condition identified in the live production incident: On an IS-IS broadcast LAN, an unintended router acts as the designated intermediate system because its interface priority differs from the design. It is meaningful because The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design.

Incorrect Answers

A:

The two devices show an up adjacency at the intended level and their Level 1 link-state databases exchange reachability. This measurement may prove the unrelated IS-IS level-one area mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: On an IS-IS broadcast LAN, an unintended router acts as the designated intermediate system because its interface priority differs from the design. A relevant acceptance result here is: The designated system matches the planned candidate, pseudonode LSPs are coherent, and LAN adjacencies remain stable.

C:

A shared Level 1 or Level 2 adjacency comes up and the right set of level-specific routes is exchanged. This measurement may prove the unrelated IS-IS level capability mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: On an IS-IS broadcast LAN, an unintended router acts as the designated intermediate system because its interface priority differs from the design. A relevant acceptance result here is: The designated system matches the planned candidate, pseudonode LSPs are coherent, and LAN adjacencies remain stable.

D:

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: On an IS-IS broadcast LAN, an unintended router acts as the designated intermediate system because its interface priority differs from the design. A relevant acceptance result here is: The designated system matches the planned candidate, pseudonode LSPs are coherent, and LAN adjacencies remain stable.

Question 275

During production incident triage, engineers observe: A provider calls a GRE tunnel secure against eavesdropping merely because customers cannot see its inner packet headers on the underlay. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

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

Explanation

Correct Answer

D:

A validated encryption layer protects inner payload on the monitored underlay while GRE routing still functions as designed. This tests the actual condition identified in the live production incident: A provider calls a GRE tunnel secure against eavesdropping merely because customers cannot see its inner packet headers on the underlay. It is meaningful because GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls.

Incorrect Answers

A:

Packet captures show the expected outer GRE addresses and matching decapsulation counts on the peer. This measurement may prove the unrelated GRE tunnel endpoint mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A provider calls a GRE tunnel secure against eavesdropping merely because customers cannot see its inner packet headers on the underlay. A relevant acceptance result here is: A validated encryption layer protects inner payload on the monitored underlay while GRE routing still functions as designed.

B:

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: A provider calls a GRE tunnel secure against eavesdropping merely because customers cannot see its inner packet headers on the underlay. A relevant acceptance result here is: A validated encryption layer protects inner payload on the monitored underlay while GRE routing still functions as designed.

C:

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: A provider calls a GRE tunnel secure against eavesdropping merely because customers cannot see its inner packet headers on the underlay. A relevant acceptance result here is: A validated encryption layer protects inner payload on the monitored underlay while GRE routing still functions as designed.

Question 276

During production incident triage, engineers observe: IS-IS neighbors are up for IPv4, but IPv6 routes do not appear because the IPv6 reachability information is not advertised in supported IS-IS TLVs. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. The IPv6 route is active in inet6.0 with the correct interface-scoped next hop and test traffic reaches the peer.
  2. Approved IPv6 prefixes are received, installed and reachable with the correct inet6.0 next-hop resolution.
  3. An IPv6 trace crosses the intended tunnel, while outer IPv4 packets reach the peer endpoints and encapsulation counters increment.
  4. The relevant IPv6 reachability TLVs are present and remote IPv6 prefixes become active in inet6.0.

Explanation

Correct Answer

D:

The relevant IPv6 reachability TLVs are present and remote IPv6 prefixes become active in inet6.0. This tests the actual condition identified in the live production incident: IS-IS neighbors are up for IPv4, but IPv6 routes do not appear because the IPv6 reachability information is not advertised in supported IS-IS TLVs. It is meaningful because IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information.

Incorrect Answers

A:

The IPv6 route is active in inet6.0 with the correct interface-scoped next hop and test traffic reaches the peer. This measurement may prove the unrelated IPv6 static link-local next hop condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: IS-IS neighbors are up for IPv4, but IPv6 routes do not appear because the IPv6 reachability information is not advertised in supported IS-IS TLVs. A relevant acceptance result here is: The relevant IPv6 reachability TLVs are present and remote IPv6 prefixes become active in inet6.0.

B:

Approved IPv6 prefixes are received, installed and reachable with the correct inet6.0 next-hop resolution. This measurement may prove the unrelated IPv6 BGP NLRI family omitted condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: IS-IS neighbors are up for IPv4, but IPv6 routes do not appear because the IPv6 reachability information is not advertised in supported IS-IS TLVs. A relevant acceptance result here is: The relevant IPv6 reachability TLVs are present and remote IPv6 prefixes become active in inet6.0.

C:

An IPv6 trace crosses the intended tunnel, while outer IPv4 packets reach the peer endpoints and encapsulation counters increment. This measurement may prove the unrelated IPv6 over IPv4 transit tunnel condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: IS-IS neighbors are up for IPv4, but IPv6 routes do not appear because the IPv6 reachability information is not advertised in supported IS-IS TLVs. A relevant acceptance result here is: The relevant IPv6 reachability TLVs are present and remote IPv6 prefixes become active in inet6.0.

Question 277

During production incident triage, engineers observe: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. Hosts reach their VLAN gateway, the IRB interface appears active, and inter-VLAN traffic follows the intended security policy.
  2. Captured handoff frames carry the agreed outer tag and correct inner VLAN values and pass only the authorized service.
  3. Initial flooding is VLAN-scoped, then subsequent frames to the learned MAC use the correct specific egress port.
  4. The customer MAC and VLAN appear in the correct virtual-switch instance with no leakage into default bridging context.

Explanation

Correct Answer

B:

Captured handoff frames carry the agreed outer tag and correct inner VLAN values and pass only the authorized service. This tests the actual condition identified in the live production incident: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. It is meaningful because Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags.

Incorrect Answers

A:

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 wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. A relevant acceptance result here is: Captured handoff frames carry the agreed outer tag and correct inner VLAN values and pass only the authorized service.

C:

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 wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. A relevant acceptance result here is: Captured handoff frames carry the agreed outer tag and correct inner VLAN values and pass only the authorized service.

D:

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: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. A relevant acceptance result here is: Captured handoff frames carry the agreed outer tag and correct inner VLAN values and pass only the authorized service.

Question 278

During production incident triage, engineers observe: An operator expects the lowest MED to win between paths received from two different neighbor autonomous systems, but the BGP selection does not follow that expectation. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. The session establishes using the intended loopback source and destination and stays up after a physical link fails.
  2. The multihop session forms between the designed IP endpoints, TTL is appropriate and only intended neighbors can connect.
  3. The best path matches the documented MED comparison scope and the selected inbound preference is confirmed with peer attributes.
  4. The authorized prefix appears in the neighbor's received-route view and unrelated infrastructure addresses remain absent.

Explanation

Correct Answer

C:

The best path matches the documented MED comparison scope and the selected inbound preference is confirmed with peer attributes. This tests the actual condition identified in the live production incident: An operator expects the lowest MED to win between paths received from two different neighbor autonomous systems, but the BGP selection does not follow that expectation. It is meaningful because BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking.

Incorrect Answers

A:

The session establishes using the intended loopback source and destination and stays up after a physical link fails. This measurement may prove the unrelated IBGP loopback source resolution condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An operator expects the lowest MED to win between paths received from two different neighbor autonomous systems, but the BGP selection does not follow that expectation. A relevant acceptance result here is: The best path matches the documented MED comparison scope and the selected inbound preference is confirmed with peer attributes.

B:

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 live production incident was resolved. The specific observed fault is: An operator expects the lowest MED to win between paths received from two different neighbor autonomous systems, but the BGP selection does not follow that expectation. A relevant acceptance result here is: The best path matches the documented MED comparison scope and the selected inbound preference is confirmed with peer attributes.

D:

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: An operator expects the lowest MED to win between paths received from two different neighbor autonomous systems, but the BGP selection does not follow that expectation. A relevant acceptance result here is: The best path matches the documented MED comparison scope and the selected inbound preference is confirmed with peer attributes.

Question 279

During production incident triage, engineers observe: A trace shows the penultimate router removing a transport label before handing a packet to the egress, and an engineer assumes the missing final label is a fault. 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. Expected LDP discovery packets and TCP session are present on the correct link, and relevant FEC labels are learned.
  3. An LDP session reaches Operational and displays the intended neighbor label bindings after selective filter correction.
  4. The LSP reserves its intended bandwidth end to end without exceeding the engineered link limits.

Explanation

Correct Answer

A:

The egress receives the expected payload context and end-to-end service passes despite the absence of a top transport label. This tests the actual condition identified in the live production incident: A trace shows the penultimate router removing a transport label before handing a packet to the egress, and an engineer assumes the missing final label is a fault. It is meaningful because Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work.

Incorrect Answers

B:

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 trace shows the penultimate router removing a transport label before handing a packet to the egress, and an engineer assumes the missing final label is a fault. A relevant acceptance result here is: The egress receives the expected payload context and end-to-end service passes despite the absence of a top transport label.

C:

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 trace shows the penultimate router removing a transport label before handing a packet to the egress, and an engineer assumes the missing final label is a fault. A relevant acceptance result here is: The egress receives the expected payload context and end-to-end service passes despite the absence of a top transport label.

D:

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 trace shows the penultimate router removing a transport label before handing a packet to the egress, and an engineer assumes the missing final label is a fault. A relevant acceptance result here is: The egress receives the expected payload context and end-to-end service passes despite the absence of a top transport label.

Question 280

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

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

Explanation

Correct Answer

B:

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

Incorrect Answers

A:

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

C:

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

D:

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


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.