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 12

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.

Question 111

During production incident triage, engineers observe: Two cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. IS-IS relies on a unique system ID to identify LSP originators and topology nodes.
  2. Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration.
  3. IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering.
  4. IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB.

Explanation

Correct Answer

A:

IS-IS relies on a unique system ID to identify LSP originators and topology nodes. This principle directly explains the live production incident: Two cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. The aligned engineering response is: Allocate unique system identifiers in the NET on each router and refresh the affected IS-IS topology state. The result should be established through: The nodes appear with distinct system IDs and no repeated conflicting LSP originator entries in the database.

Incorrect Answers

B:

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: Two cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. The controlling mechanism is instead: IS-IS relies on a unique system ID to identify LSP originators and topology nodes. The correct response would be: Allocate unique system identifiers in the NET on each router and refresh the affected IS-IS topology state.

C:

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: Two cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. The controlling mechanism is instead: IS-IS relies on a unique system ID to identify LSP originators and topology nodes. The correct response would be: Allocate unique system identifiers in the NET on each router and refresh the affected IS-IS topology state.

D:

IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB. That explanation applies to the different IS-IS LSP lifetime anomaly scenario rather than this live production incident. The current fault evidence is: Two cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. The controlling mechanism is instead: IS-IS relies on a unique system ID to identify LSP originators and topology nodes. The correct response would be: Allocate unique system identifiers in the NET on each router and refresh the affected IS-IS topology state.

Question 112

During production incident triage, engineers observe: An engineer sees a route in the routing protocol database and assumes data packets must use it, but the route is hidden or inactive relative to an alternative. 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. Junos can retain candidate and inactive routes in routing tables while forwarding uses only the selected active route installed in the forwarding information base.
  3. 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.
  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

B:

Junos can retain candidate and inactive routes in routing tables while forwarding uses only the selected active route installed in the forwarding information base. This principle directly explains the live production incident: An engineer sees a route in the routing protocol database and assumes data packets must use it, but the route is hidden or inactive relative to an alternative. The aligned engineering response is: Inspect the active route and forwarding-table next hop, then resolve the preference, policy or next-hop condition suppressing the expected path. The result should be established through: The chosen route becomes active and the forwarding table points to its resolved next hop; an end-to-end trace follows that path.

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: An engineer sees a route in the routing protocol database and assumes data packets must use it, but the route is hidden or inactive relative to an alternative. The controlling mechanism is instead: Junos can retain candidate and inactive routes in routing tables while forwarding uses only the selected active route installed in the forwarding information base. The correct response would be: Inspect the active route and forwarding-table next hop, then resolve the preference, policy or next-hop condition suppressing the expected path.

C:

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: An engineer sees a route in the routing protocol database and assumes data packets must use it, but the route is hidden or inactive relative to an alternative. The controlling mechanism is instead: Junos can retain candidate and inactive routes in routing tables while forwarding uses only the selected active route installed in the forwarding information base. The correct response would be: Inspect the active route and forwarding-table next hop, then resolve the preference, policy or next-hop condition suppressing the expected path.

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: An engineer sees a route in the routing protocol database and assumes data packets must use it, but the route is hidden or inactive relative to an alternative. The controlling mechanism is instead: Junos can retain candidate and inactive routes in routing tables while forwarding uses only the selected active route installed in the forwarding information base. The correct response would be: Inspect the active route and forwarding-table next hop, then resolve the preference, policy or next-hop condition suppressing the expected path.

Question 113

During production incident triage, engineers observe: A dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone.
  2. A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime.
  3. GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions.
  4. VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway.

Explanation

Correct Answer

C:

GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions. This principle directly explains the live production incident: A dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. The aligned engineering response is: Use a supported combination of GRES and NSR or appropriate graceful restart to meet the control-plane continuity target. The result should be established through: A controlled RE switchover maintains data-plane forwarding and routing neighbor continuity according to the selected supported feature set.

Incorrect Answers

A:

LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone. That explanation applies to the different LACP partner mismatch scenario rather than this live production incident. The current fault evidence is: A dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. The controlling mechanism is instead: GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions. The correct response would be: Use a supported combination of GRES and NSR or appropriate graceful restart to meet the control-plane continuity target.

B:

A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime. That explanation applies to the different LAG member imbalance after failure scenario rather than this live production incident. The current fault evidence is: A dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. The controlling mechanism is instead: GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions. The correct response would be: Use a supported combination of GRES and NSR or appropriate graceful restart to meet the control-plane continuity target.

D:

VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway. That explanation applies to the different VRRP master priority failover scenario rather than this live production incident. The current fault evidence is: A dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. The controlling mechanism is instead: GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions. The correct response would be: Use a supported combination of GRES and NSR or appropriate graceful restart to meet the control-plane continuity target.

Question 114

During production incident triage, engineers observe: A static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active.
  2. Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text.
  3. An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match.
  4. 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.

Explanation

Correct Answer

D:

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. This principle directly explains the live production incident: A static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. The aligned engineering response is: Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure. The result should be established through: With the downstream fault injected, the unsuitable backup route is withdrawn or de-preferred and valid traffic moves to the tested alternate.

Incorrect Answers

A:

A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active. That explanation applies to the different Aggregate route contribution scenario rather than this live production incident. The current fault evidence is: A static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. The controlling mechanism is instead: 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. The correct response would be: Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure.

B:

Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text. That explanation applies to the different Generated default route prerequisite scenario rather than this live production incident. The current fault evidence is: A static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. The controlling mechanism is instead: 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. The correct response would be: Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure.

C:

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: A static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. The controlling mechanism is instead: 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. The correct response would be: Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure.

Question 115

During production incident triage, engineers observe: A service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping.
  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 admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability.

Explanation

Correct Answer

A:

Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping. This principle directly explains the live production incident: A service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. The aligned engineering response is: Apply supported explicit-null disposition where the QoS design requires a labeled packet to reach the egress. The result should be established through: A captured or traced packet reaches the egress with the expected explicit-null label and traffic-class handling.

Incorrect Answers

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 service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. The controlling mechanism is instead: Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping. The correct response would be: Apply supported explicit-null disposition where the QoS design requires a labeled packet to reach the egress.

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 service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. The controlling mechanism is instead: Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping. The correct response would be: Apply supported explicit-null disposition where the QoS design requires a labeled packet to reach the egress.

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 service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. The controlling mechanism is instead: Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping. The correct response would be: Apply supported explicit-null disposition where the QoS design requires a labeled packet to reach the egress.

Question 116

During production incident triage, engineers observe: IS-IS neighbors are up for IPv4, but IPv6 routes do not appear because the IPv6 reachability information is not advertised in supported IS-IS TLVs. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop.
  2. IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information.
  3. BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange.
  4. An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct.

Explanation

Correct Answer

B:

IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information. This principle directly explains the live production incident: IS-IS neighbors are up for IPv4, but IPv6 routes do not appear because the IPv6 reachability information is not advertised in supported IS-IS TLVs. The aligned engineering response is: Enable the intended IS-IS IPv6 address-family or reachability support and validate the IPv6 prefixes in the IS-IS database. The result should be established through: The relevant IPv6 reachability TLVs are present and remote IPv6 prefixes become active in inet6.0.

Incorrect Answers

A:

An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop. That explanation applies to the different IPv6 static link-local next hop scenario rather than this live production incident. The current fault evidence is: IS-IS neighbors are up for IPv4, but IPv6 routes do not appear because the IPv6 reachability information is not advertised in supported IS-IS TLVs. The controlling mechanism is instead: IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information. The correct response would be: Enable the intended IS-IS IPv6 address-family or reachability support and validate the IPv6 prefixes in the IS-IS database.

C:

BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange. That explanation applies to the different IPv6 BGP NLRI family omitted scenario rather than this live production incident. The current fault evidence is: IS-IS neighbors are up for IPv4, but IPv6 routes do not appear because the IPv6 reachability information is not advertised in supported IS-IS TLVs. The controlling mechanism is instead: IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information. The correct response would be: Enable the intended IS-IS IPv6 address-family or reachability support and validate the IPv6 prefixes in the IS-IS database.

D:

An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct. That explanation applies to the different IPv6 over IPv4 transit tunnel scenario rather than this live production incident. The current fault evidence is: IS-IS neighbors are up for IPv4, but IPv6 routes do not appear because the IPv6 reachability information is not advertised in supported IS-IS TLVs. The controlling mechanism is instead: IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information. The correct response would be: Enable the intended IS-IS IPv6 address-family or reachability support and validate the IPv6 prefixes in the IS-IS database.

Question 117

During production incident triage, engineers observe: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection.
  2. When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers.
  3. BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering.
  4. BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice.

Explanation

Correct Answer

C:

BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering. This principle directly explains the live production incident: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. The aligned engineering response is: Permit the intended peer-to-peer TCP 179 control connection through the applicable filter and verify bidirectional reachability. The result should be established through: A TCP session is established to the correct neighbor address, BGP reaches Established and intended routes are exchanged.

Incorrect Answers

A:

BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection. That explanation applies to the different BGP next-hop inaccessible scenario rather than this live production incident. The current fault evidence is: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. The controlling mechanism is instead: BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering. The correct response would be: Permit the intended peer-to-peer TCP 179 control connection through the applicable filter and verify bidirectional reachability.

B:

When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers. That explanation applies to the different BGP AS-path comparison scenario rather than this live production incident. The current fault evidence is: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. The controlling mechanism is instead: BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering. The correct response would be: Permit the intended peer-to-peer TCP 179 control connection through the applicable filter and verify bidirectional reachability.

D:

BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice. That explanation applies to the different BGP import policy leak scenario rather than this live production incident. The current fault evidence is: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. The controlling mechanism is instead: BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering. The correct response would be: Permit the intended peer-to-peer TCP 179 control connection through the applicable filter and verify bidirectional reachability.

Question 118

During production incident triage, engineers observe: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference.
  2. A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active.
  3. ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds.
  4. Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules.

Explanation

Correct Answer

D:

Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. This principle directly explains the live production incident: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. The aligned engineering response is: Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path. The result should be established through: Matched and unmatched packet samples increment their intended counters and resolve to the expected respective routing tables.

Incorrect Answers

A:

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 filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. The controlling mechanism is instead: Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. The correct response would be: Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path.

B:

A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active. That explanation applies to the different Aggregate route contribution scenario rather than this live production incident. The current fault evidence is: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. The controlling mechanism is instead: Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. The correct response would be: Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path.

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: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. The controlling mechanism is instead: Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. The correct response would be: Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path.

Question 119

During production incident triage, engineers observe: A generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text.
  2. An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match.
  3. Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths.
  4. 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.

Explanation

Correct Answer

A:

Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text. This principle directly explains the live production incident: A generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. The aligned engineering response is: Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior. The result should be established through: The generated default becomes active with the expected next hop only when the qualifying contributor exists.

Incorrect Answers

B:

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: A generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. The controlling mechanism is instead: Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text. The correct response would be: Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior.

C:

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: A generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. The controlling mechanism is instead: Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text. The correct response would be: Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior.

D:

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 generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. The controlling mechanism is instead: Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text. The correct response would be: Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior.

Question 120

During production incident triage, engineers observe: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. 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. IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas.
  4. The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design.

Explanation

Correct Answer

C:

IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas. This principle directly explains the live production incident: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. The aligned engineering response is: Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended. The result should be established through: The two devices show an up adjacency at the intended level and their Level 1 link-state databases exchange reachability.

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: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. The controlling mechanism is instead: IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas. The correct response would be: Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended.

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: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. The controlling mechanism is instead: IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas. The correct response would be: Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended.

D:

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: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. The controlling mechanism is instead: IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas. The correct response would be: Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended.


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.