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 15

Question 140

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

  1. MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path.
  2. LDP maps forwarding equivalence classes to labels learned from the downstream next hop; a session can be up without an applicable mapping for every FEC.
  3. RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost.
  4. Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work.

Explanation

Correct Answer

C:

RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost. This principle directly explains the live production incident: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. The aligned engineering response is: Configure and validate supported RSVP link protection with a viable bypass for the affected protected link. The result should be established through: The bypass LSP is operational before fault injection and protected traffic follows the bypass after the link is disabled.

Incorrect Answers

A:

MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path. That explanation applies to the different MPLS interface not enabled scenario rather than this live production incident. The current fault 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 controlling mechanism is instead: RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost. The correct response would be: Configure and validate supported RSVP link protection with a viable bypass for the affected protected link.

B:

LDP maps forwarding equivalence classes to labels learned from the downstream next hop; a session can be up without an applicable mapping for every FEC. That explanation applies to the different Missing LDP FEC label mapping scenario rather than this live production incident. The current fault 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 controlling mechanism is instead: RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost. The correct response would be: Configure and validate supported RSVP link protection with a viable bypass for the affected protected link.

D:

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: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. The controlling mechanism is instead: RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost. The correct response would be: Configure and validate supported RSVP link protection with a viable bypass for the affected protected link.

Question 141

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

  1. LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation.
  2. LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment.
  3. Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work.
  4. RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability.

Explanation

Correct Answer

C:

Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work. This principle directly explains 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. The aligned engineering response is: Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure. The result should be established through: The egress receives the expected payload context and end-to-end service passes despite the absence of a top transport label.

Incorrect Answers

A:

LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation. That explanation applies to the different LDP discovery and IGP mismatch scenario rather than this live production incident. The current fault evidence 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. The controlling mechanism is instead: Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work. The correct response would be: Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure.

B:

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: 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. The controlling mechanism is instead: Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work. The correct response would be: Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure.

D:

RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability. That explanation applies to the different RSVP reservable bandwidth shortage scenario rather than this live production incident. The current fault evidence 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. The controlling mechanism is instead: Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work. The correct response would be: Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure.

Question 142

During production incident triage, engineers observe: PE-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match.
  2. For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference.
  3. ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds.
  4. 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.

Explanation

Correct Answer

B:

For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference. This principle directly explains the live production incident: PE-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. The aligned engineering response is: Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design. The result should be established through: The selected active prefix shows the intended protocol, route preference, and forwarding next hop both before and after a controlled failover.

Incorrect Answers

A:

An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match. That explanation applies to the different Aggregate rejection behavior scenario rather than this live production incident. The current fault evidence is: PE-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. The controlling mechanism is instead: For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference. The correct response would be: Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design.

C:

ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds. That explanation applies to the different Equal-cost multipath eligibility scenario rather than this live production incident. The current fault evidence is: PE-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. The controlling mechanism is instead: For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference. The correct response would be: Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design.

D:

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. That explanation applies to the different Filter-based forwarding classification scenario rather than this live production incident. The current fault evidence is: PE-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. The controlling mechanism is instead: For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference. The correct response would be: Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design.

Question 143

During production incident triage, engineers observe: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path.
  2. LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation.
  3. LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment.
  4. RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP.

Explanation

Correct Answer

D:

RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP. This principle directly explains the live production incident: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. The aligned engineering response is: Provision and verify a separate return LSP or alternate reverse forwarding mechanism consistent with the service design. The result should be established through: Forward and reverse tests each map to separately verified forwarding paths with their intended egress destinations.

Incorrect Answers

A:

MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path. That explanation applies to the different MPLS interface not enabled scenario rather than this live production incident. The current fault evidence is: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. The controlling mechanism is instead: RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP. The correct response would be: Provision and verify a separate return LSP or alternate reverse forwarding mechanism consistent with the service design.

B:

LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation. That explanation applies to the different LDP discovery and IGP mismatch scenario rather than this live production incident. The current fault evidence is: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. The controlling mechanism is instead: RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP. The correct response would be: Provision and verify a separate return LSP or alternate reverse forwarding mechanism consistent with the service design.

C:

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: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. The controlling mechanism is instead: RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP. The correct response would be: Provision and verify a separate return LSP or alternate reverse forwarding mechanism consistent with the service design.

Question 144

During production incident triage, engineers observe: VLAN 100 and VLAN 200 are intended to use different roots, but a single shared spanning-tree topology sends both over the same constrained link. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action.
  2. VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits.
  3. Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection.
  4. Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address.

Explanation

Correct Answer

B:

VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits. This principle directly explains the live production incident: VLAN 100 and VLAN 200 are intended to use different roots, but a single shared spanning-tree topology sends both over the same constrained link. The aligned engineering response is: Choose and configure an appropriate supported per-VLAN STP approach with documented root assignment for each VLAN. The result should be established through: Each VLAN reports its planned root and forwarding links with no loops during a controlled failover.

Incorrect Answers

A:

Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action. That explanation applies to the different Unexpected BPDU on edge port scenario rather than this live production incident. The current fault evidence is: VLAN 100 and VLAN 200 are intended to use different roots, but a single shared spanning-tree topology sends both over the same constrained link. The controlling mechanism is instead: VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits. The correct response would be: Choose and configure an appropriate supported per-VLAN STP approach with documented root assignment for each VLAN.

C:

Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection. That explanation applies to the different Loop protection after BPDU loss scenario rather than this live production incident. The current fault evidence is: VLAN 100 and VLAN 200 are intended to use different roots, but a single shared spanning-tree topology sends both over the same constrained link. The controlling mechanism is instead: VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits. The correct response would be: Choose and configure an appropriate supported per-VLAN STP approach with documented root assignment for each VLAN.

D:

Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address. That explanation applies to the different Root bridge election priority scenario rather than this live production incident. The current fault evidence is: VLAN 100 and VLAN 200 are intended to use different roots, but a single shared spanning-tree topology sends both over the same constrained link. The controlling mechanism is instead: VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits. The correct response would be: Choose and configure an appropriate supported per-VLAN STP approach with documented root assignment for each VLAN.

Question 145

During production incident triage, engineers observe: A redundant link should resume traffic when the active path fails, but the switch stays blocked because engineers confuse RSTP alternate and edge port roles. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping.
  2. Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address.
  3. RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails.
  4. Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path.

Explanation

Correct Answer

C:

RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails. This principle directly explains the live production incident: A redundant link should resume traffic when the active path fails, but the switch stays blocked because engineers confuse RSTP alternate and edge port roles. The aligned engineering response is: Validate RSTP root and alternate port roles and point-to-point link conditions before testing rapid alternate-port transition. The result should be established through: A controlled root-port failure causes the expected alternate port to forward without creating a bridging loop.

Incorrect Answers

A:

MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping. That explanation applies to the different MSTP region mismatch scenario rather than this live production incident. The current fault evidence is: A redundant link should resume traffic when the active path fails, but the switch stays blocked because engineers confuse RSTP alternate and edge port roles. The controlling mechanism is instead: RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails. The correct response would be: Validate RSTP root and alternate port roles and point-to-point link conditions before testing rapid alternate-port transition.

B:

Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address. That explanation applies to the different Root bridge election priority scenario rather than this live production incident. The current fault evidence is: A redundant link should resume traffic when the active path fails, but the switch stays blocked because engineers confuse RSTP alternate and edge port roles. The controlling mechanism is instead: RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails. The correct response would be: Validate RSTP root and alternate port roles and point-to-point link conditions before testing rapid alternate-port transition.

D:

Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path. That explanation applies to the different Root protection against rogue core scenario rather than this live production incident. The current fault evidence is: A redundant link should resume traffic when the active path fails, but the switch stays blocked because engineers confuse RSTP alternate and edge port roles. The controlling mechanism is instead: RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails. The correct response would be: Validate RSTP root and alternate port roles and point-to-point link conditions before testing rapid alternate-port transition.

Question 146

During production incident triage, engineers observe: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links.
  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:

OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links. This principle directly explains the live production incident: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. The aligned engineering response is: Set a nonzero eligible interface priority where DR candidacy is intended and re-evaluate election behavior with the network design. The result should be established through: An appropriate eligible router becomes DR or BDR after a controlled election and neighbor adjacency remains stable.

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: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. The controlling mechanism is instead: OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links. The correct response would be: Set a nonzero eligible interface priority where DR candidacy is intended and re-evaluate election behavior with the network design.

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: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. The controlling mechanism is instead: OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links. The correct response would be: Set a nonzero eligible interface priority where DR candidacy is intended and re-evaluate election behavior with the network design.

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: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. The controlling mechanism is instead: OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links. The correct response would be: Set a nonzero eligible interface priority where DR candidacy is intended and re-evaluate election behavior with the network design.

Question 147

During production incident triage, engineers observe: An ingress router has routes to the LSP egress but its core-facing interface is not participating in MPLS, so label forwarding is absent. 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 label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path.
  3. RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange.
  4. RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability.

Explanation

Correct Answer

B:

MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path. This principle directly explains the live production incident: An ingress router has routes to the LSP egress but its core-facing interface is not participating in MPLS, so label forwarding is absent. The aligned engineering response is: Enable MPLS on the intended eligible core-facing interface and verify forwarding capability along the path. The result should be established through: The core interface is MPLS enabled and labeled forwarding entries exist for the expected transport destination.

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 ingress router has routes to the LSP egress but its core-facing interface is not participating in MPLS, so label forwarding is absent. The controlling mechanism is instead: MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path. The correct response would be: Enable MPLS on the intended eligible core-facing interface and verify forwarding capability along the path.

C:

RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange. That explanation applies to the different RSVP-TE constrained path missing scenario rather than this live production incident. The current fault evidence is: An ingress router has routes to the LSP egress but its core-facing interface is not participating in MPLS, so label forwarding is absent. The controlling mechanism is instead: MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path. The correct response would be: Enable MPLS on the intended eligible core-facing interface and verify forwarding capability along the path.

D:

RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability. That explanation applies to the different RSVP reservable bandwidth shortage scenario rather than this live production incident. The current fault evidence is: An ingress router has routes to the LSP egress but its core-facing interface is not participating in MPLS, so label forwarding is absent. The controlling mechanism is instead: MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path. The correct response would be: Enable MPLS on the intended eligible core-facing interface and verify forwarding capability along the path.

Question 148

During production incident triage, engineers observe: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain.
  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 stub areas intentionally restrict external LSAs and normally rely on appropriate default reachability from an ABR for external destinations.
  4. OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric.

Explanation

Correct Answer

A:

OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain. This principle directly explains the live production incident: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. The aligned engineering response is: Assign and verify a unique stable OSPF router ID for each router, then refresh affected neighbor state. The result should be established through: The routers advertise distinct IDs, neighbors remain Full and the LSDB no longer shows conflicting origins.

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: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. The controlling mechanism is instead: OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain. The correct response would be: Assign and verify a unique stable OSPF router ID for each router, then refresh affected neighbor state.

C:

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: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. The controlling mechanism is instead: OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain. The correct response would be: Assign and verify a unique stable OSPF router ID for each router, then refresh affected neighbor state.

D:

OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric. That explanation applies to the different OSPF metric path preference scenario rather than this live production incident. The current fault evidence is: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. The controlling mechanism is instead: OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain. The correct response would be: Assign and verify a unique stable OSPF router ID for each router, then refresh affected neighbor state.

Question 149

During production incident triage, engineers observe: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance.
  2. OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links.
  3. Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB.
  4. Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information.

Explanation

Correct Answer

D:

Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information. This principle directly explains the live production incident: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. The aligned engineering response is: Set the LAN interface passive within the relevant OSPF area while retaining the intended prefix advertisement. The result should be established through: No OSPF neighbors form on the customer LAN, yet core routers still learn the intended LAN prefix.

Incorrect Answers

A:

OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance. That explanation applies to the different OSPF hello dead timer mismatch scenario rather than this live production incident. The current fault evidence is: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. The controlling mechanism is instead: Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information. The correct response would be: Set the LAN interface passive within the relevant OSPF area while retaining the intended prefix advertisement.

B:

OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links. That explanation applies to the different DR priority zero misconception scenario rather than this live production incident. The current fault evidence is: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. The controlling mechanism is instead: Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information. The correct response would be: Set the LAN interface passive within the relevant OSPF area while retaining the intended prefix advertisement.

C:

Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB. That explanation applies to the different OSPF LSDB discrepancy scenario rather than this live production incident. The current fault evidence is: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. The controlling mechanism is instead: Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information. The correct response would be: Set the LAN interface passive within the relevant OSPF area while retaining the intended prefix advertisement.

Question 150

During production incident triage, engineers observe: PE-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths.
  2. 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.
  3. Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules.
  4. A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active.

Explanation

Correct Answer

D:

A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active. This principle directly explains the live production incident: PE-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. The aligned engineering response is: Verify the intended contributing routes and activate an eligible more-specific route before depending on the aggregate advertisement. The result should be established through: The aggregate appears as an active route with contributing prefixes shown, and the permitted summary is advertised to the intended peer.

Incorrect Answers

A:

Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths. That explanation applies to the different Per-flow hash expectation scenario rather than this live production incident. The current fault evidence is: PE-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. The controlling mechanism is instead: A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active. The correct response would be: Verify the intended contributing routes and activate an eligible more-specific route before depending on the aggregate advertisement.

B:

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. That explanation applies to the different Filter-based forwarding classification scenario rather than this live production incident. The current fault evidence is: PE-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. The controlling mechanism is instead: A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active. The correct response would be: Verify the intended contributing routes and activate an eligible more-specific route before depending on the aggregate advertisement.

C:

Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. That explanation applies to the different Filter policy overmatch scenario rather than this live production incident. The current fault evidence is: PE-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. The controlling mechanism is instead: A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active. The correct response would be: Verify the intended contributing routes and activate an eligible more-specific route before depending on the aggregate advertisement.


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.