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 11

Question 100

During production incident triage, engineers observe: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Enable MPLS on the intended eligible core-facing interface and verify forwarding capability along the path.
  2. Verify FEC route reachability, neighbor label advertisement and the label mapping installed for the specific destination.
  3. Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure.
  4. Configure and validate supported RSVP link protection with a viable bypass for the affected protected link.

Explanation

Correct Answer

D:

Configure and validate supported RSVP link protection with a viable bypass for the affected protected link. In the live production incident, the reported evidence is: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. The intervention follows the governing fact that RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost. Closure requires the corresponding specific confirmation: The bypass LSP is operational before fault injection and protected traffic follows the bypass after the link is disabled.

Incorrect Answers

A:

Enable MPLS on the intended eligible core-facing interface and verify forwarding capability along the path. This action was designed for the separate MPLS interface not enabled case, not the live production incident being assessed. The present observation is: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. Its governing mechanism is: RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost. The narrower applicable remedy is: Configure and validate supported RSVP link protection with a viable bypass for the affected protected link.

B:

Verify FEC route reachability, neighbor label advertisement and the label mapping installed for the specific destination. This action was designed for the separate Missing LDP FEC label mapping case, not the live production incident being assessed. The present observation is: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. Its governing mechanism is: RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost. The narrower applicable remedy is: Configure and validate supported RSVP link protection with a viable bypass for the affected protected link.

C:

Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure. This action was designed for the separate Penultimate hop popping case, not the live production incident being assessed. The present observation is: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. Its governing mechanism is: RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost. The narrower applicable remedy is: Configure and validate supported RSVP link protection with a viable bypass for the affected protected link.

Question 101

During production incident triage, engineers observe: One OSPF router has a different LSA sequence or age for a core link and briefly computes a stale path after a topology event. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB.
  2. Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information.
  3. OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship.
  4. OSPF stub areas intentionally restrict external LSAs and normally rely on appropriate default reachability from an ABR for external destinations.

Explanation

Correct Answer

A:

Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB. This principle directly explains the live production incident: One OSPF router has a different LSA sequence or age for a core link and briefly computes a stale path after a topology event. The aligned engineering response is: Investigate adjacency stability and LSA flooding, then restore consistent current link-state information before relying on SPF. The result should be established through: Both peers show the expected current LSAs with consistent sequence and topology, and the computed path reaches the destination.

Incorrect Answers

B:

Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information. That explanation applies to the different OSPF passive interface scenario rather than this live production incident. The current fault evidence is: One OSPF router has a different LSA sequence or age for a core link and briefly computes a stale path after a topology event. The controlling mechanism is instead: Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB. The correct response would be: Investigate adjacency stability and LSA flooding, then restore consistent current link-state information before relying on SPF.

C:

OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship. That explanation applies to the different OSPF area ID mismatch scenario rather than this live production incident. The current fault evidence is: One OSPF router has a different LSA sequence or age for a core link and briefly computes a stale path after a topology event. The controlling mechanism is instead: Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB. The correct response would be: Investigate adjacency stability and LSA flooding, then restore consistent current link-state information before relying on SPF.

D:

OSPF stub areas intentionally restrict external LSAs and normally rely on appropriate default reachability from an ABR for external destinations. That explanation applies to the different Stub area external LSA expectation scenario rather than this live production incident. The current fault evidence is: One OSPF router has a different LSA sequence or age for a core link and briefly computes a stale path after a topology event. The controlling mechanism is instead: Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB. The correct response would be: Investigate adjacency stability and LSA flooding, then restore consistent current link-state information before relying on SPF.

Question 102

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. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

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

Explanation

Correct Answer

A:

GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls. This principle directly explains 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. The aligned engineering response is: Add an appropriate encryption mechanism such as supported IPsec where confidentiality is required, while treating GRE as encapsulation. The result should be established through: A validated encryption layer protects inner payload on the monitored underlay while GRE routing still functions as designed.

Incorrect Answers

B:

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 live production incident. The current fault evidence is: A provider calls a GRE tunnel secure against eavesdropping merely because customers cannot see its inner packet headers on the underlay. The controlling mechanism is instead: GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls. The correct response would be: Add an appropriate encryption mechanism such as supported IPsec where confidentiality is required, while treating GRE as encapsulation.

C:

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 live production incident. The current fault evidence is: A provider calls a GRE tunnel secure against eavesdropping merely because customers cannot see its inner packet headers on the underlay. The controlling mechanism is instead: GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls. The correct response would be: Add an appropriate encryption mechanism such as supported IPsec where confidentiality is required, while treating GRE as encapsulation.

D:

GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU. That explanation applies to the different GRE encapsulation MTU overhead scenario rather than this live production incident. The current fault evidence is: A provider calls a GRE tunnel secure against eavesdropping merely because customers cannot see its inner packet headers on the underlay. The controlling mechanism is instead: GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls. The correct response would be: Add an appropriate encryption mechanism such as supported IPsec where confidentiality is required, while treating GRE as encapsulation.

Question 103

During production incident triage, engineers observe: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration.
  2. IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering.
  3. The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design.
  4. An IS-IS adjacency needs compatible protocol levels as well as link reachability.

Explanation

Correct Answer

D:

An IS-IS adjacency needs compatible protocol levels as well as link reachability. This principle directly explains the live production incident: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. The aligned engineering response is: Configure a common allowed IS-IS level on the two interfaces in accordance with the area and backbone design. The result should be established through: A shared Level 1 or Level 2 adjacency comes up and the right set of level-specific routes is exchanged.

Incorrect Answers

A:

Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration. That explanation applies to the different IS-IS ISO family missing scenario rather than this live production incident. The current fault evidence is: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. The controlling mechanism is instead: An IS-IS adjacency needs compatible protocol levels as well as link reachability. The correct response would be: Configure a common allowed IS-IS level on the two interfaces in accordance with the area and backbone design.

B:

IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering. That explanation applies to the different IS-IS narrow metric ceiling scenario rather than this live production incident. The current fault evidence is: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. The controlling mechanism is instead: An IS-IS adjacency needs compatible protocol levels as well as link reachability. The correct response would be: Configure a common allowed IS-IS level on the two interfaces in accordance with the area and backbone design.

C:

The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design. That explanation applies to the different IS-IS DIS election surprise scenario rather than this live production incident. The current fault evidence is: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. The controlling mechanism is instead: An IS-IS adjacency needs compatible protocol levels as well as link reachability. The correct response would be: Configure a common allowed IS-IS level on the two interfaces in accordance with the area and backbone design.

Question 104

During production incident triage, engineers observe: A customer CE is connected to an access port configured for VLAN 110, while its service should be VLAN 120, and its frames cannot reach the correct broadcast domain. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping.
  2. An access port classifies untagged received frames into its configured VLAN, which determines Layer 2 forwarding membership.
  3. A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic.
  4. Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned.

Explanation

Correct Answer

B:

An access port classifies untagged received frames into its configured VLAN, which determines Layer 2 forwarding membership. This principle directly explains the live production incident: A customer CE is connected to an access port configured for VLAN 110, while its service should be VLAN 120, and its frames cannot reach the correct broadcast domain. The aligned engineering response is: Move the access port to the approved VLAN and verify logical interface membership and learning. The result should be established through: The CE MAC is learned in VLAN 120 and its frames reach a same-VLAN peer without leaking into VLAN 110.

Incorrect Answers

A:

Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping. That explanation applies to the different Native VLAN mismatch scenario rather than this live production incident. The current fault evidence is: A customer CE is connected to an access port configured for VLAN 110, while its service should be VLAN 120, and its frames cannot reach the correct broadcast domain. The controlling mechanism is instead: An access port classifies untagged received frames into its configured VLAN, which determines Layer 2 forwarding membership. The correct response would be: Move the access port to the approved VLAN and verify logical interface membership and learning.

C:

A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic. That explanation applies to the different Unknown unicast flooding behavior scenario rather than this live production incident. The current fault evidence is: A customer CE is connected to an access port configured for VLAN 110, while its service should be VLAN 120, and its frames cannot reach the correct broadcast domain. The controlling mechanism is instead: An access port classifies untagged received frames into its configured VLAN, which determines Layer 2 forwarding membership. The correct response would be: Move the access port to the approved VLAN and verify logical interface membership and learning.

D:

Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned. That explanation applies to the different Virtual switch instance membership scenario rather than this live production incident. The current fault evidence is: A customer CE is connected to an access port configured for VLAN 110, while its service should be VLAN 120, and its frames cannot reach the correct broadcast domain. The controlling mechanism is instead: An access port classifies untagged received frames into its configured VLAN, which determines Layer 2 forwarding membership. The correct response would be: Move the access port to the approved VLAN and verify logical interface membership and learning.

Question 105

During production incident triage, engineers observe: Hosts in a VLAN can bridge to each other but cannot reach a different subnet because the VLAN has no correctly attached integrated routing and bridging interface. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments.
  2. Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit.
  3. Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags.
  4. An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching.

Explanation

Correct Answer

D:

An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching. This principle directly explains the live production incident: Hosts in a VLAN can bridge to each other but cannot reach a different subnet because the VLAN has no correctly attached integrated routing and bridging interface. The aligned engineering response is: Configure and bind the intended IRB Layer 3 interface to the VLAN and verify IP forwarding and gateway addressing. The result should be established through: Hosts reach their VLAN gateway, the IRB interface appears active, and inter-VLAN traffic follows the intended security policy.

Incorrect Answers

A:

Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments. That explanation applies to the different MAC move instability scenario rather than this live production incident. The current fault evidence is: Hosts in a VLAN can bridge to each other but cannot reach a different subnet because the VLAN has no correctly attached integrated routing and bridging interface. The controlling mechanism is instead: An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching. The correct response would be: Configure and bind the intended IRB Layer 3 interface to the VLAN and verify IP forwarding and gateway addressing.

B:

Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit. That explanation applies to the different Flexible VLAN tagging logical units scenario rather than this live production incident. The current fault evidence is: Hosts in a VLAN can bridge to each other but cannot reach a different subnet because the VLAN has no correctly attached integrated routing and bridging interface. The controlling mechanism is instead: An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching. The correct response would be: Configure and bind the intended IRB Layer 3 interface to the VLAN and verify IP forwarding and gateway addressing.

C:

Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags. That explanation applies to the different Q-in-Q outer tag mismatch scenario rather than this live production incident. The current fault evidence is: Hosts in a VLAN can bridge to each other but cannot reach a different subnet because the VLAN has no correctly attached integrated routing and bridging interface. The controlling mechanism is instead: An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching. The correct response would be: Configure and bind the intended IRB Layer 3 interface to the VLAN and verify IP forwarding and gateway addressing.

Question 106

During production incident triage, engineers observe: An SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment.
  2. MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions.
  3. Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work.
  4. A node SID typically steers toward its destination using shortest-path IGP forwarding, while explicit adjacency segments can add finer path constraints.

Explanation

Correct Answer

D:

A node SID typically steers toward its destination using shortest-path IGP forwarding, while explicit adjacency segments can add finer path constraints. This principle directly explains the live production incident: An SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. The aligned engineering response is: Use appropriate segment choices or a supported SR policy when explicit path steering is required, rather than treating a node SID as an exact-hop instruction. The result should be established through: The observed label stack and forwarding path match the documented shortest path or the specified explicit segment list.

Incorrect Answers

A:

LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment. That explanation applies to the different LDP TCP 646 establishment scenario rather than this live production incident. The current fault evidence is: An SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. The controlling mechanism is instead: A node SID typically steers toward its destination using shortest-path IGP forwarding, while explicit adjacency segments can add finer path constraints. The correct response would be: Use appropriate segment choices or a supported SR policy when explicit path steering is required, rather than treating a node SID as an exact-hop instruction.

B:

MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions. That explanation applies to the different Incoming label missing in LFIB scenario rather than this live production incident. The current fault evidence is: An SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. The controlling mechanism is instead: A node SID typically steers toward its destination using shortest-path IGP forwarding, while explicit adjacency segments can add finer path constraints. The correct response would be: Use appropriate segment choices or a supported SR policy when explicit path steering is required, rather than treating a node SID as an exact-hop instruction.

C:

Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work. That explanation applies to the different Penultimate hop popping scenario rather than this live production incident. The current fault evidence is: An SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. The controlling mechanism is instead: A node SID typically steers toward its destination using shortest-path IGP forwarding, while explicit adjacency segments can add finer path constraints. The correct response would be: Use appropriate segment choices or a supported SR policy when explicit path steering is required, rather than treating a node SID as an exact-hop instruction.

Question 107

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. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas.
  2. An IS-IS adjacency needs compatible protocol levels as well as link reachability.
  3. The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design.
  4. IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering.

Explanation

Correct Answer

C:

The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design. This principle directly explains 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. The aligned engineering response is: Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election. The result should be established through: The designated system matches the planned candidate, pseudonode LSPs are coherent, and LAN adjacencies remain stable.

Incorrect Answers

A:

IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas. That explanation applies to the different IS-IS level-one area mismatch scenario rather than this live production incident. The current fault evidence is: On an IS-IS broadcast LAN, an unintended router acts as the designated intermediate system because its interface priority differs from the design. The controlling mechanism is instead: The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design. The correct response would be: Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election.

B:

An IS-IS adjacency needs compatible protocol levels as well as link reachability. That explanation applies to the different IS-IS level capability mismatch scenario rather than this live production incident. The current fault evidence is: On an IS-IS broadcast LAN, an unintended router acts as the designated intermediate system because its interface priority differs from the design. The controlling mechanism is instead: The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design. The correct response would be: Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election.

D:

IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering. That explanation applies to the different IS-IS narrow metric ceiling scenario rather than this live production incident. The current fault evidence is: On an IS-IS broadcast LAN, an unintended router acts as the designated intermediate system because its interface priority differs from the design. The controlling mechanism is instead: The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design. The correct response would be: Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election.

Question 108

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. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit.
  2. An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching.
  3. Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned.
  4. A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic.

Explanation

Correct Answer

A:

Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit. This principle directly explains 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. The aligned engineering response is: Correct the interface's supported VLAN tagging and logical-unit encapsulation so each service is matched to the intended tag. The result should be established through: Per-unit counters and a packet capture demonstrate each authorized VLAN tag reaches its mapped logical interface.

Incorrect Answers

B:

An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching. That explanation applies to the different IRB routed gateway missing scenario rather than this live production incident. The current fault evidence 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. The controlling mechanism is instead: Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit. The correct response would be: Correct the interface's supported VLAN tagging and logical-unit encapsulation so each service is matched to the intended tag.

C:

Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned. That explanation applies to the different Virtual switch instance membership scenario rather than this live production incident. The current fault evidence 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. The controlling mechanism is instead: Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit. The correct response would be: Correct the interface's supported VLAN tagging and logical-unit encapsulation so each service is matched to the intended tag.

D:

A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic. That explanation applies to the different Unknown unicast flooding behavior scenario rather than this live production incident. The current fault evidence 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. The controlling mechanism is instead: Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit. The correct response would be: Correct the interface's supported VLAN tagging and logical-unit encapsulation so each service is matched to the intended tag.

Question 109

During production incident triage, engineers observe: A router interface carries IPv4 traffic and is listed under IS-IS, but no IS-IS Hello packets form because the required ISO protocol family is absent. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas.
  2. An IS-IS adjacency needs compatible protocol levels as well as link reachability.
  3. Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration.
  4. IS-IS relies on a unique system ID to identify LSP originators and topology nodes.

Explanation

Correct Answer

C:

Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration. This principle directly explains the live production incident: A router interface carries IPv4 traffic and is listed under IS-IS, but no IS-IS Hello packets form because the required ISO protocol family is absent. The aligned engineering response is: Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation. The result should be established through: IS-IS Hello exchanges appear and the expected level adjacency establishes while IPv4 traffic still functions.

Incorrect Answers

A:

IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas. That explanation applies to the different IS-IS level-one area mismatch scenario rather than this live production incident. The current fault evidence is: A router interface carries IPv4 traffic and is listed under IS-IS, but no IS-IS Hello packets form because the required ISO protocol family is absent. The controlling mechanism is instead: Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration. The correct response would be: Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation.

B:

An IS-IS adjacency needs compatible protocol levels as well as link reachability. That explanation applies to the different IS-IS level capability mismatch scenario rather than this live production incident. The current fault evidence is: A router interface carries IPv4 traffic and is listed under IS-IS, but no IS-IS Hello packets form because the required ISO protocol family is absent. The controlling mechanism is instead: Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration. The correct response would be: Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation.

D:

IS-IS relies on a unique system ID to identify LSP originators and topology nodes. That explanation applies to the different Duplicate IS-IS system ID scenario rather than this live production incident. The current fault evidence is: A router interface carries IPv4 traffic and is listed under IS-IS, but no IS-IS Hello packets form because the required ISO protocol family is absent. The controlling mechanism is instead: Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration. The correct response would be: Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation.

Question 110

During production incident triage, engineers observe: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. A static next hop may appear link-reachable while the remote end-to-end path is unusable, so a tracking mechanism such as BFD can be necessary.
  2. Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms.
  3. Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy.
  4. For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference.

Explanation

Correct Answer

C:

Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy. This principle directly explains the live production incident: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. The aligned engineering response is: Tighten the route import/export conditions to the explicitly authorized customer prefixes and verify instance isolation. The result should be established through: Permitted prefixes are visible in the correct tables and an unauthorized destination is absent from the receiving customer's forwarding view.

Incorrect Answers

A:

A static next hop may appear link-reachable while the remote end-to-end path is unusable, so a tracking mechanism such as BFD can be necessary. That explanation applies to the different Static backup blackhole scenario rather than this live production incident. The current fault evidence is: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. The controlling mechanism is instead: Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy. The correct response would be: Tighten the route import/export conditions to the explicitly authorized customer prefixes and verify instance isolation.

B:

Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms. That explanation applies to the different RIB group forwarding copy scenario rather than this live production incident. The current fault evidence is: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. The controlling mechanism is instead: Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy. The correct response would be: Tighten the route import/export conditions to the explicitly authorized customer prefixes and verify instance isolation.

D:

For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference. That explanation applies to the different Administrative preference overrides static scenario rather than this live production incident. The current fault evidence is: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. The controlling mechanism is instead: Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy. The correct response would be: Tighten the route import/export conditions to the explicitly authorized customer prefixes and verify instance isolation.


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.