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 6

Question 50

During production incident triage, engineers observe: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Use a controlled import policy to assign the desired BGP local preference to the selected exit paths.
  2. Correct the explicitly configured neighbor peer AS to match the authorized remote routing domain and verify the session parameters.
  3. Apply an export policy that permits precisely the required public prefix to the designated neighbor and rejects unrelated routes.
  4. Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes.

Explanation

Correct Answer

A:

Use a controlled import policy to assign the desired BGP local preference to the selected exit paths. In the live production incident, the reported evidence is: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. The intervention follows the governing fact that Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility. Closure requires the corresponding specific confirmation: The designated BGP exit wins best-path selection for the intended prefixes and backup behavior remains correct.

Incorrect Answers

B:

Correct the explicitly configured neighbor peer AS to match the authorized remote routing domain and verify the session parameters. This action was designed for the separate BGP peer autonomous system mismatch case, not the live production incident being assessed. The present observation is: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. Its governing mechanism is: Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility. The narrower applicable remedy is: Use a controlled import policy to assign the desired BGP local preference to the selected exit paths.

C:

Apply an export policy that permits precisely the required public prefix to the designated neighbor and rejects unrelated routes. This action was designed for the separate BGP export policy omission case, not the live production incident being assessed. The present observation is: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. Its governing mechanism is: Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility. The narrower applicable remedy is: Use a controlled import policy to assign the desired BGP local preference to the selected exit paths.

D:

Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes. This action was designed for the separate BGP import policy leak case, not the live production incident being assessed. The present observation is: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. Its governing mechanism is: Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility. The narrower applicable remedy is: Use a controlled import policy to assign the desired BGP local preference to the selected exit paths.

Question 51

During production incident triage, engineers observe: A route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Configure a consistent local BGP source address and ensure both loopbacks are reachable through the IGP or static routing design.
  2. Use a controlled import policy to assign the desired BGP local preference to the selected exit paths.
  3. Validate Junos MED comparison rules and the contributing neighbor AS, then apply an explicit policy only if required by traffic design.
  4. Apply an export policy that permits precisely the required public prefix to the designated neighbor and rejects unrelated routes.

Explanation

Correct Answer

D:

Apply an export policy that permits precisely the required public prefix to the designated neighbor and rejects unrelated routes. In the live production incident, the reported evidence is: A route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. The intervention follows the governing fact that BGP route advertisements are shaped by export routing policy and eligibility rather than the mere presence of a route in inet.0. Closure requires the corresponding specific confirmation: The authorized prefix appears in the neighbor's received-route view and unrelated infrastructure addresses remain absent.

Incorrect Answers

A:

Configure a consistent local BGP source address and ensure both loopbacks are reachable through the IGP or static routing design. This action was designed for the separate IBGP loopback source resolution case, not the live production incident being assessed. The present observation is: A route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. Its governing mechanism is: BGP route advertisements are shaped by export routing policy and eligibility rather than the mere presence of a route in inet.0. The narrower applicable remedy is: Apply an export policy that permits precisely the required public prefix to the designated neighbor and rejects unrelated routes.

B:

Use a controlled import policy to assign the desired BGP local preference to the selected exit paths. This action was designed for the separate BGP local preference egress case, not the live production incident being assessed. The present observation is: A route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. Its governing mechanism is: BGP route advertisements are shaped by export routing policy and eligibility rather than the mere presence of a route in inet.0. The narrower applicable remedy is: Apply an export policy that permits precisely the required public prefix to the designated neighbor and rejects unrelated routes.

C:

Validate Junos MED comparison rules and the contributing neighbor AS, then apply an explicit policy only if required by traffic design. This action was designed for the separate BGP MED comparison scope case, not the live production incident being assessed. The present observation is: A route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. Its governing mechanism is: BGP route advertisements are shaped by export routing policy and eligibility rather than the mere presence of a route in inet.0. The narrower applicable remedy is: Apply an export policy that permits precisely the required public prefix to the designated neighbor and rejects unrelated routes.

Question 52

During production incident triage, engineers observe: A router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Permit the intended peer-to-peer TCP 179 control connection through the applicable filter and verify bidirectional reachability.
  2. Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes.
  3. Use the designed full-mesh or route-reflector topology and validate route reflection where appropriate.
  4. Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required.

Explanation

Correct Answer

C:

Use the designed full-mesh or route-reflector topology and validate route reflection where appropriate. In the live production incident, the reported evidence is: A router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. The intervention follows the governing fact that Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design. Closure requires the corresponding specific confirmation: The intended peer receives the route through permitted reflection or a full-mesh session, and next-hop reachability is correct.

Incorrect Answers

A:

Permit the intended peer-to-peer TCP 179 control connection through the applicable filter and verify bidirectional reachability. This action was designed for the separate BGP TCP transport blocked case, not the live production incident being assessed. The present observation is: A router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. Its governing mechanism is: Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design. The narrower applicable remedy is: Use the designed full-mesh or route-reflector topology and validate route reflection where appropriate.

B:

Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes. This action was designed for the separate BGP import policy leak case, not the live production incident being assessed. The present observation is: A router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. Its governing mechanism is: Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design. The narrower applicable remedy is: Use the designed full-mesh or route-reflector topology and validate route reflection where appropriate.

D:

Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required. This action was designed for the separate BGP AS-path comparison case, not the live production incident being assessed. The present observation is: A router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. Its governing mechanism is: Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design. The narrower applicable remedy is: Use the designed full-mesh or route-reflector topology and validate route reflection where appropriate.

Question 53

During production incident triage, engineers observe: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Ensure appropriate L1/L2 router connectivity and default-reachability design toward the Level 2 backbone.
  2. Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation.
  3. Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support.
  4. Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election.

Explanation

Correct Answer

A:

Ensure appropriate L1/L2 router connectivity and default-reachability design toward the Level 2 backbone. In the live production incident, the reported evidence is: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. The intervention follows the governing fact that Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes. Closure requires the corresponding specific confirmation: A usable default or intended inter-area reachability is present, and traced traffic exits through the designed L1/L2 router.

Incorrect Answers

B:

Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation. This action was designed for the separate IS-IS ISO family missing case, not the live production incident being assessed. The present observation is: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. Its governing mechanism is: Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes. The narrower applicable remedy is: Ensure appropriate L1/L2 router connectivity and default-reachability design toward the Level 2 backbone.

C:

Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support. This action was designed for the separate IS-IS narrow metric ceiling case, not the live production incident being assessed. The present observation is: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. Its governing mechanism is: Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes. The narrower applicable remedy is: Ensure appropriate L1/L2 router connectivity and default-reachability design toward the Level 2 backbone.

D:

Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election. This action was designed for the separate IS-IS DIS election surprise case, not the live production incident being assessed. The present observation is: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. Its governing mechanism is: Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes. The narrower applicable remedy is: Ensure appropriate L1/L2 router connectivity and default-reachability design toward the Level 2 backbone.

Question 54

During production incident triage, engineers observe: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Add an appropriate encryption mechanism such as supported IPsec where confidentiality is required, while treating GRE as encapsulation.
  2. Correct tunnel MTU or MSS considerations and verify fragmentation or PMTU behavior for the specific supported platform.
  3. Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path.
  4. Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself.

Explanation

Correct Answer

D:

Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself. In the live production incident, the reported evidence is: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. The intervention follows the governing fact that GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable. Closure requires the corresponding specific confirmation: An underlay path reaches the outer peer without circular routing and inner GRE packets are successfully decapsulated.

Incorrect Answers

A:

Add an appropriate encryption mechanism such as supported IPsec where confidentiality is required, while treating GRE as encapsulation. This action was designed for the separate GRE confidentiality misconception case, not the live production incident being assessed. The present observation is: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. Its governing mechanism is: GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable. The narrower applicable remedy is: Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself.

B:

Correct tunnel MTU or MSS considerations and verify fragmentation or PMTU behavior for the specific supported platform. This action was designed for the separate GRE encapsulation MTU overhead case, not the live production incident being assessed. The present observation is: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. Its governing mechanism is: GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable. The narrower applicable remedy is: Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself.

C:

Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path. This action was designed for the separate GRE tunnel endpoint mismatch case, not the live production incident being assessed. The present observation is: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. Its governing mechanism is: GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable. The narrower applicable remedy is: Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself.

Question 55

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 narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure.
  2. Configure and test the intended RIB group or specific controlled route import into the appropriate secondary routing table.
  3. Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design.
  4. Tighten the route import/export conditions to the explicitly authorized customer prefixes and verify instance isolation.

Explanation

Correct Answer

D:

Tighten the route import/export conditions to the explicitly authorized customer prefixes and verify instance isolation. In the live production incident, the reported evidence is: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. The intervention follows the governing fact that Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy. Closure requires the corresponding specific confirmation: Permitted prefixes are visible in the correct tables and an unauthorized destination is absent from the receiving customer's forwarding view.

Incorrect Answers

A:

Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure. This action was designed for the separate Static backup blackhole case, not the live production incident being assessed. The present observation is: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. Its governing mechanism is: Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy. The narrower applicable remedy is: Tighten the route import/export conditions to the explicitly authorized customer prefixes and verify instance isolation.

B:

Configure and test the intended RIB group or specific controlled route import into the appropriate secondary routing table. This action was designed for the separate RIB group forwarding copy case, not the live production incident being assessed. The present observation is: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. Its governing mechanism is: Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy. The narrower applicable remedy is: Tighten the route import/export conditions to the explicitly authorized customer prefixes and verify instance isolation.

C:

Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design. This action was designed for the separate Administrative preference overrides static case, not the live production incident being assessed. The present observation is: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. Its governing mechanism is: Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy. The narrower applicable remedy is: Tighten the route import/export conditions to the explicitly authorized customer prefixes and verify instance isolation.

Question 56

During production incident triage, engineers observe: An operator expects the lowest MED to win between paths received from two different neighbor autonomous systems, but the BGP selection does not follow that expectation. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Configure a consistent local BGP source address and ensure both loopbacks are reachable through the IGP or static routing design.
  2. Configure an approved eBGP multihop arrangement with suitable TTL and reachable peer addresses at both ends.
  3. Validate Junos MED comparison rules and the contributing neighbor AS, then apply an explicit policy only if required by traffic design.
  4. Apply an export policy that permits precisely the required public prefix to the designated neighbor and rejects unrelated routes.

Explanation

Correct Answer

C:

Validate Junos MED comparison rules and the contributing neighbor AS, then apply an explicit policy only if required by traffic design. In the live production incident, the reported evidence is: An operator expects the lowest MED to win between paths received from two different neighbor autonomous systems, but the BGP selection does not follow that expectation. The intervention follows the governing fact that BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking. Closure requires the corresponding specific confirmation: The best path matches the documented MED comparison scope and the selected inbound preference is confirmed with peer attributes.

Incorrect Answers

A:

Configure a consistent local BGP source address and ensure both loopbacks are reachable through the IGP or static routing design. This action was designed for the separate IBGP loopback source resolution case, not the live production incident being assessed. The present observation is: An operator expects the lowest MED to win between paths received from two different neighbor autonomous systems, but the BGP selection does not follow that expectation. Its governing mechanism is: BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking. The narrower applicable remedy is: Validate Junos MED comparison rules and the contributing neighbor AS, then apply an explicit policy only if required by traffic design.

B:

Configure an approved eBGP multihop arrangement with suitable TTL and reachable peer addresses at both ends. This action was designed for the separate EBGP multihop peering case, not the live production incident being assessed. The present observation is: An operator expects the lowest MED to win between paths received from two different neighbor autonomous systems, but the BGP selection does not follow that expectation. Its governing mechanism is: BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking. The narrower applicable remedy is: Validate Junos MED comparison rules and the contributing neighbor AS, then apply an explicit policy only if required by traffic design.

D:

Apply an export policy that permits precisely the required public prefix to the designated neighbor and rejects unrelated routes. This action was designed for the separate BGP export policy omission case, not the live production incident being assessed. The present observation is: An operator expects the lowest MED to win between paths received from two different neighbor autonomous systems, but the BGP selection does not follow that expectation. Its governing mechanism is: BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking. The narrower applicable remedy is: Validate Junos MED comparison rules and the contributing neighbor AS, then apply an explicit policy only if required by traffic design.

Question 57

During production incident triage, engineers observe: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. 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. Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls.
  3. Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth.
  4. Verify FEC route reachability, neighbor label advertisement and the label mapping installed for the specific destination.

Explanation

Correct Answer

C:

Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth. In the live production incident, the reported evidence is: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. The intervention follows the governing fact that RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability. Closure requires the corresponding specific confirmation: The LSP reserves its intended bandwidth end to end without exceeding the engineered link limits.

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 new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. Its governing mechanism is: RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability. The narrower applicable remedy is: Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth.

B:

Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls. This action was designed for the separate LDP TCP 646 establishment case, not the live production incident being assessed. The present observation is: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. Its governing mechanism is: RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability. The narrower applicable remedy is: Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth.

D:

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 new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. Its governing mechanism is: RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability. The narrower applicable remedy is: Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth.

Question 58

During production incident triage, engineers observe: A prefix is received from a valid BGP peer but remains unusable because the advertised BGP next hop has no resolving route in the local table. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Permit the intended peer-to-peer TCP 179 control connection through the applicable filter and verify bidirectional reachability.
  2. Configure an approved eBGP multihop arrangement with suitable TTL and reachable peer addresses at both ends.
  3. Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes.
  4. Restore IGP or static reachability for the intended BGP next hop, or apply the correct next-hop policy where design requires it.

Explanation

Correct Answer

D:

Restore IGP or static reachability for the intended BGP next hop, or apply the correct next-hop policy where design requires it. In the live production incident, the reported evidence is: A prefix is received from a valid BGP peer but remains unusable because the advertised BGP next hop has no resolving route in the local table. The intervention follows the governing fact that BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection. Closure requires the corresponding specific confirmation: The received BGP route resolves its next hop, becomes eligible, and forwards over the designed path.

Incorrect Answers

A:

Permit the intended peer-to-peer TCP 179 control connection through the applicable filter and verify bidirectional reachability. This action was designed for the separate BGP TCP transport blocked case, not the live production incident being assessed. The present observation is: A prefix is received from a valid BGP peer but remains unusable because the advertised BGP next hop has no resolving route in the local table. Its governing mechanism is: BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection. The narrower applicable remedy is: Restore IGP or static reachability for the intended BGP next hop, or apply the correct next-hop policy where design requires it.

B:

Configure an approved eBGP multihop arrangement with suitable TTL and reachable peer addresses at both ends. This action was designed for the separate EBGP multihop peering case, not the live production incident being assessed. The present observation is: A prefix is received from a valid BGP peer but remains unusable because the advertised BGP next hop has no resolving route in the local table. Its governing mechanism is: BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection. The narrower applicable remedy is: Restore IGP or static reachability for the intended BGP next hop, or apply the correct next-hop policy where design requires it.

C:

Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes. This action was designed for the separate BGP import policy leak case, not the live production incident being assessed. The present observation is: A prefix is received from a valid BGP peer but remains unusable because the advertised BGP next hop has no resolving route in the local table. Its governing mechanism is: BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection. The narrower applicable remedy is: Restore IGP or static reachability for the intended BGP next hop, or apply the correct next-hop policy where design requires it.

Question 59

During production incident triage, engineers observe: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Align the hello and dead intervals on both OSPF interfaces and confirm stable neighbor state.
  2. Place both adjacency interfaces into the intended matching OSPF area, then validate neighbor exchange.
  3. Add a tightly scoped OSPF export policy for the intended prefix, preserving loop and source restrictions.
  4. Validate stub-area design and use the intended summary or default-route strategy rather than expecting type-5 LSAs in the stub.

Explanation

Correct Answer

C:

Add a tightly scoped OSPF export policy for the intended prefix, preserving loop and source restrictions. In the live production incident, the reported evidence is: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. The intervention follows the governing fact that External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements. Closure requires the corresponding specific confirmation: The specifically allowed customer prefix appears as the expected external route on the peer, while other connected networks stay unadvertised.

Incorrect Answers

A:

Align the hello and dead intervals on both OSPF interfaces and confirm stable neighbor state. This action was designed for the separate OSPF hello dead timer mismatch case, not the live production incident being assessed. The present observation is: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. Its governing mechanism is: External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements. The narrower applicable remedy is: Add a tightly scoped OSPF export policy for the intended prefix, preserving loop and source restrictions.

B:

Place both adjacency interfaces into the intended matching OSPF area, then validate neighbor exchange. This action was designed for the separate OSPF area ID mismatch case, not the live production incident being assessed. The present observation is: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. Its governing mechanism is: External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements. The narrower applicable remedy is: Add a tightly scoped OSPF export policy for the intended prefix, preserving loop and source restrictions.

D:

Validate stub-area design and use the intended summary or default-route strategy rather than expecting type-5 LSAs in the stub. This action was designed for the separate Stub area external LSA expectation case, not the live production incident being assessed. The present observation is: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. Its governing mechanism is: External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements. The narrower applicable remedy is: Add a tightly scoped OSPF export policy for the intended prefix, preserving loop and source restrictions.

Question 60

During production incident triage, engineers observe: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Restore an active route to the specified next-hop address or replace it with a verified reachable next hop before relying on the static route.
  2. Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design.
  3. Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior.
  4. Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination.

Explanation

Correct Answer

D:

Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination. In the live production incident, the reported evidence is: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. The intervention follows the governing fact that An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match. Closure requires the corresponding specific confirmation: A controlled packet to an active more-specific prefix forwards, while a packet to an uncovered address receives the intended reject or silent-discard behavior.

Incorrect Answers

A:

Restore an active route to the specified next-hop address or replace it with a verified reachable next hop before relying on the static route. This action was designed for the separate Recursive next-hop resolution case, not the live production incident being assessed. The present observation is: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. Its governing mechanism is: An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match. The narrower applicable remedy is: Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination.

B:

Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design. This action was designed for the separate Administrative preference overrides static case, not the live production incident being assessed. The present observation is: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. Its governing mechanism is: An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match. The narrower applicable remedy is: Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination.

C:

Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior. This action was designed for the separate Generated default route prerequisite case, not the live production incident being assessed. The present observation is: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. Its governing mechanism is: An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match. The narrower applicable remedy is: Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination.


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.