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 30

Question 290

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

  1. A controlled packet to an active more-specific prefix forwards, while a packet to an uncovered address receives the intended reject or silent-discard behavior.
  2. Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded.
  3. The static prefix becomes active with a resolved next hop, and a sourced packet test reaches the destination through the intended interface.
  4. Counters for the targeted match increment, only the intended traffic uses the alternate next hop, and unmatched traffic stays on its original path.

Explanation

Correct Answer

C:

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

Incorrect Answers

A:

A controlled packet to an active more-specific prefix forwards, while a packet to an uncovered address receives the intended reject or silent-discard behavior. This measurement may prove the unrelated Aggregate rejection behavior condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: PE-11 has a configured static route to 198.51.100.0/24, but the specified next hop 192.0.2.14 is not reachable by any active route, and traffic drops. A relevant acceptance result here is: The static prefix becomes active with a resolved next hop, and a sourced packet test reaches the destination through the intended interface.

B:

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

D:

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

Question 291

During production incident triage, engineers observe: A route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. 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 authorized prefix appears in the neighbor's received-route view and unrelated infrastructure addresses remain absent.
  3. The designated BGP exit wins best-path selection for the intended prefixes and backup behavior remains correct.
  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 authorized prefix appears in the neighbor's received-route view and unrelated infrastructure addresses remain absent. This tests the actual condition identified in the live production incident: A route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. It is meaningful because BGP route advertisements are shaped by export routing policy and eligibility rather than the mere presence of a route in inet.0.

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: A route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. A relevant acceptance result here is: The authorized prefix appears in the neighbor's received-route view and unrelated infrastructure addresses remain absent.

C:

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 route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. A relevant acceptance result here is: The authorized prefix appears in the neighbor's received-route view and unrelated infrastructure addresses remain absent.

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 route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. A relevant acceptance result here is: The authorized prefix appears in the neighbor's received-route view and unrelated infrastructure addresses remain absent.

Question 292

During production incident triage, engineers observe: Small IPv6 pings succeed over a provider path but larger sessions stall because an intermediate filter blocks Packet Too Big messages needed by IPv6 Path MTU Discovery. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. Large IPv6 application transfers succeed and Packet Too Big messages reach the source when necessary.
  2. The OSPFv3 neighbor reaches the expected state and learned IPv6 prefixes appear in inet6.0.
  3. The relevant IPv6 reachability TLVs are present and remote IPv6 prefixes become active in inet6.0.
  4. An IPv6 trace crosses the intended tunnel, while outer IPv4 packets reach the peer endpoints and encapsulation counters increment.

Explanation

Correct Answer

A:

Large IPv6 application transfers succeed and Packet Too Big messages reach the source when necessary. This tests the actual condition identified in the live production incident: Small IPv6 pings succeed over a provider path but larger sessions stall because an intermediate filter blocks Packet Too Big messages needed by IPv6 Path MTU Discovery. It is meaningful because IPv6 routers do not fragment transit packets; working Path MTU Discovery relies on ICMPv6 errors when packets exceed a path MTU.

Incorrect Answers

B:

The OSPFv3 neighbor reaches the expected state and learned IPv6 prefixes appear in inet6.0. This measurement may prove the unrelated OSPFv3 neighbor uses link-local condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Small IPv6 pings succeed over a provider path but larger sessions stall because an intermediate filter blocks Packet Too Big messages needed by IPv6 Path MTU Discovery. A relevant acceptance result here is: Large IPv6 application transfers succeed and Packet Too Big messages reach the source when necessary.

C:

The relevant IPv6 reachability TLVs are present and remote IPv6 prefixes become active in inet6.0. This measurement may prove the unrelated IS-IS IPv6 reachability TLVs condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Small IPv6 pings succeed over a provider path but larger sessions stall because an intermediate filter blocks Packet Too Big messages needed by IPv6 Path MTU Discovery. A relevant acceptance result here is: Large IPv6 application transfers succeed and Packet Too Big messages reach the source when necessary.

D:

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: Small IPv6 pings succeed over a provider path but larger sessions stall because an intermediate filter blocks Packet Too Big messages needed by IPv6 Path MTU Discovery. A relevant acceptance result here is: Large IPv6 application transfers succeed and Packet Too Big messages reach the source when necessary.

Question 293

During production incident triage, engineers observe: After a provider switch reboot, the wrong access switch becomes the STP root because its bridge identifier is lower than the intended core root's ID. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. The intended core device is reported as root and a designated backup root is stable after an election test.
  2. The violating connection is blocked or alerted according to policy while legitimate host-facing links remain available.
  3. The protected port remains safe during the simulated BPDU loss and returns to normal after signaling is restored.
  4. A controlled root-port failure causes the expected alternate port to forward without creating a bridging loop.

Explanation

Correct Answer

A:

The intended core device is reported as root and a designated backup root is stable after an election test. This tests the actual condition identified in the live production incident: After a provider switch reboot, the wrong access switch becomes the STP root because its bridge identifier is lower than the intended core root's ID. It is meaningful because Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address.

Incorrect Answers

B:

The violating connection is blocked or alerted according to policy while legitimate host-facing links remain available. This measurement may prove the unrelated Unexpected BPDU on edge port condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: After a provider switch reboot, the wrong access switch becomes the STP root because its bridge identifier is lower than the intended core root's ID. A relevant acceptance result here is: The intended core device is reported as root and a designated backup root is stable after an election test.

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 live production incident was resolved. The specific observed fault is: After a provider switch reboot, the wrong access switch becomes the STP root because its bridge identifier is lower than the intended core root's ID. A relevant acceptance result here is: The intended core device is reported as root and a designated backup root is stable after an election test.

D:

A controlled root-port failure causes the expected alternate port to forward without creating a bridging loop. This measurement may prove the unrelated RSTP alternate port activation condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: After a provider switch reboot, the wrong access switch becomes the STP root because its bridge identifier is lower than the intended core root's ID. A relevant acceptance result here is: The intended core device is reported as root and a designated backup root is stable after an election test.

Question 294

During production incident triage, engineers observe: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. The core interface is MPLS enabled and labeled forwarding entries exist for the expected transport destination.
  2. Expected LDP discovery packets and TCP session are present on the correct link, and relevant FEC labels are learned.
  3. The RSVP LSP becomes operational on the authorized explicit route and reports a complete signaled path.
  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

C:

The RSVP LSP becomes operational on the authorized explicit route and reports a complete signaled path. This tests the actual condition identified in the live production incident: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. It is meaningful because RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange.

Incorrect Answers

A:

The core interface is MPLS enabled and labeled forwarding entries exist for the expected transport destination. This measurement may prove the unrelated MPLS interface not enabled condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. A relevant acceptance result here is: The RSVP LSP becomes operational on the authorized explicit route and reports a complete signaled path.

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: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. A relevant acceptance result here is: The RSVP LSP becomes operational on the authorized explicit route and reports a complete signaled path.

D:

The egress receives the expected payload context and end-to-end service passes despite the absence of a top transport label. This measurement may prove the unrelated Penultimate hop popping condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. A relevant acceptance result here is: The RSVP LSP becomes operational on the authorized explicit route and reports a complete signaled path.

Question 295

During production incident triage, engineers observe: A remote eBGP session must cross an intervening router but was configured as directly connected, so it fails even though both endpoints are routable. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. The received BGP route resolves its next hop, becomes eligible, and forwards over the designed path.
  2. The multihop session forms between the designed IP endpoints, TTL is appropriate and only intended neighbors can connect.
  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 multihop session forms between the designed IP endpoints, TTL is appropriate and only intended neighbors can connect. This tests the actual condition identified in the live production incident: A remote eBGP session must cross an intervening router but was configured as directly connected, so it fails even though both endpoints are routable. It is meaningful because An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers.

Incorrect Answers

A:

The received BGP route resolves its next hop, becomes eligible, and forwards over the designed path. This measurement may prove the unrelated BGP next-hop inaccessible condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A remote eBGP session must cross an intervening router but was configured as directly connected, so it fails even though both endpoints are routable. A relevant acceptance result here is: The multihop session forms between the designed IP endpoints, TTL is appropriate and only intended neighbors can connect.

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 eBGP session must cross an intervening router but was configured as directly connected, so it fails even though both endpoints are routable. A relevant acceptance result here is: The multihop session forms between the designed IP endpoints, TTL is appropriate and only intended neighbors can connect.

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 eBGP session must cross an intervening router but was configured as directly connected, so it fails even though both endpoints are routable. A relevant acceptance result here is: The multihop session forms between the designed IP endpoints, TTL is appropriate and only intended neighbors can connect.

Question 296

During production incident triage, engineers observe: A customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. The intended core device is reported as root and a designated backup root is stable after an election test.
  2. Both switches report the same region digest and expected instance-specific spanning-tree paths.
  3. Each VLAN reports its planned root and forwarding links with no loops during a controlled failover.
  4. The violating connection is blocked or alerted according to policy while legitimate host-facing links remain available.

Explanation

Correct Answer

D:

The violating connection is blocked or alerted according to policy while legitimate host-facing links remain available. This tests the actual condition identified in the live production incident: A customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. It is meaningful because Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action.

Incorrect Answers

A:

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 customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. A relevant acceptance result here is: The violating connection is blocked or alerted according to policy while legitimate host-facing links remain available.

B:

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 customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. A relevant acceptance result here is: The violating connection is blocked or alerted according to policy while legitimate host-facing links remain available.

C:

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 live production incident was resolved. The specific observed fault is: A customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. A relevant acceptance result here is: The violating connection is blocked or alerted according to policy while legitimate host-facing links remain available.

Question 297

During production incident triage, engineers observe: Two switches intended to operate in the same MSTP region treat each other as a boundary because their VLAN-to-instance mapping digests differ. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

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

Explanation

Correct Answer

D:

Both switches report the same region digest and expected instance-specific spanning-tree paths. This tests the actual condition identified in the live production incident: Two switches intended to operate in the same MSTP region treat each other as a boundary because their VLAN-to-instance mapping digests differ. It is meaningful because MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping.

Incorrect Answers

A:

A controlled root-port failure causes the expected alternate port to forward without creating a bridging loop. This measurement may prove the unrelated RSTP alternate port activation condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two switches intended to operate in the same MSTP region treat each other as a boundary because their VLAN-to-instance mapping digests differ. A relevant acceptance result here is: Both switches report the same region digest and expected instance-specific spanning-tree paths.

B:

The violating connection is blocked or alerted according to policy while legitimate host-facing links remain available. This measurement may prove the unrelated Unexpected BPDU on edge port condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: Two switches intended to operate in the same MSTP region treat each other as a boundary because their VLAN-to-instance mapping digests differ. A relevant acceptance result here is: Both switches report the same region digest and expected instance-specific spanning-tree paths.

C:

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: Two switches intended to operate in the same MSTP region treat each other as a boundary because their VLAN-to-instance mapping digests differ. A relevant acceptance result here is: Both switches report the same region digest and expected instance-specific spanning-tree paths.

Question 298

During production incident triage, 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. 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

C:

Large application packets traverse the tunnel without blackholing, and measured payload size respects the underlay capacity. This tests the actual condition identified in the live production incident: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. It is meaningful because GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU.

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 GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. A relevant acceptance result here is: Large application packets traverse the tunnel without blackholing, and measured payload size respects the underlay capacity.

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 GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. A relevant acceptance result here is: Large application packets traverse the tunnel without blackholing, and measured payload size respects the underlay capacity.

D:

A validated encryption layer protects inner payload on the monitored underlay while GRE routing still functions as designed. This measurement may prove the unrelated GRE confidentiality misconception condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. A relevant acceptance result here is: Large application packets traverse the tunnel without blackholing, and measured payload size respects the underlay capacity.

Question 299

During production incident triage, engineers observe: A provider-facing Ethernet port must carry multiple distinct tagged logical units, but one unit uses the wrong VLAN encapsulation and traffic enters the wrong service. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. Hosts reach their VLAN gateway, the IRB interface appears active, and inter-VLAN traffic follows the intended security policy.
  2. The customer MAC and VLAN appear in the correct virtual-switch instance with no leakage into default bridging context.
  3. Per-unit counters and a packet capture demonstrate each authorized VLAN tag reaches its mapped logical interface.
  4. Initial flooding is VLAN-scoped, then subsequent frames to the learned MAC use the correct specific egress port.

Explanation

Correct Answer

C:

Per-unit counters and a packet capture demonstrate each authorized VLAN tag reaches its mapped logical interface. This tests the actual condition identified in the live production incident: A provider-facing Ethernet port must carry multiple distinct tagged logical units, but one unit uses the wrong VLAN encapsulation and traffic enters the wrong service. It is meaningful because Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit.

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 provider-facing Ethernet port must carry multiple distinct tagged logical units, but one unit uses the wrong VLAN encapsulation and traffic enters the wrong service. A relevant acceptance result here is: Per-unit counters and a packet capture demonstrate each authorized VLAN tag reaches its mapped logical interface.

B:

The customer MAC and VLAN appear in the correct virtual-switch instance with no leakage into default bridging context. This measurement may prove the unrelated Virtual switch instance membership condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: A provider-facing Ethernet port must carry multiple distinct tagged logical units, but one unit uses the wrong VLAN encapsulation and traffic enters the wrong service. A relevant acceptance result here is: Per-unit counters and a packet capture demonstrate each authorized VLAN tag reaches its mapped logical interface.

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-facing Ethernet port must carry multiple distinct tagged logical units, but one unit uses the wrong VLAN encapsulation and traffic enters the wrong service. A relevant acceptance result here is: Per-unit counters and a packet capture demonstrate each authorized VLAN tag reaches its mapped logical interface.

Question 300

During production incident triage, 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 segment identifier is visible in the IGP database, resolves to the correct label, and traffic reaches the selected node.
  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 egress receives the expected payload context and end-to-end service passes despite the absence of a top transport label.

Explanation

Correct Answer

A:

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

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

An LDP session reaches Operational and displays the intended neighbor label bindings after selective filter correction. This measurement may prove the unrelated LDP TCP 646 establishment condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An SR-MPLS 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 egress receives the expected payload context and end-to-end service passes despite the absence of a top transport label. This measurement may prove the unrelated Penultimate hop popping condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An SR-MPLS 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.


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.