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 83

Question 820

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. An engineer suggests the shortcut: "Configure only an RSVP bandwidth request without addressing missing SR segment information." Which critique explains the specific risk of that shortcut?

  1. RSVP reservable bandwidth is independent of whether the source has a valid SR-MPLS SID mapping.
  2. PHP is a normal label disposition behavior and not evidence that the entire LSP should be removed.
  3. Packet size settings cannot create capacity for an RSVP admission request.
  4. Suppressing alarms cannot provide a precomputed alternate label-switched route.

Explanation

Correct Answer

A:

RSVP reservable bandwidth is independent of whether the source has a valid SR-MPLS SID mapping. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Configure only an RSVP bandwidth request without addressing missing SR segment information. It fails to resolve the underlying problem that SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels. A sound alternative is the targeted engineering action: Verify the intended node or prefix SID advertisement in the participating IGP and the label allocation on the source and transit routers.

Incorrect Answers

B:

PHP is a normal label disposition behavior and not evidence that the entire LSP should be removed. That critique concerns a shortcut from the unrelated Penultimate hop popping case. The shortcut actually proposed in this controlled acceptance rehearsal is: Configure only an RSVP bandwidth request without addressing missing SR segment information. It should be rejected for the narrower reason that RSVP reservable bandwidth is independent of whether the source has a valid SR-MPLS SID mapping. This distinction matters because SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels.

C:

Packet size settings cannot create capacity for an RSVP admission request. That critique concerns a shortcut from the unrelated RSVP reservable bandwidth shortage case. The shortcut actually proposed in this controlled acceptance rehearsal is: Configure only an RSVP bandwidth request without addressing missing SR segment information. It should be rejected for the narrower reason that RSVP reservable bandwidth is independent of whether the source has a valid SR-MPLS SID mapping. This distinction matters because SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels.

D:

Suppressing alarms cannot provide a precomputed alternate label-switched route. That critique concerns a shortcut from the unrelated RSVP link protection plan case. The shortcut actually proposed in this controlled acceptance rehearsal is: Configure only an RSVP bandwidth request without addressing missing SR segment information. It should be rejected for the narrower reason that RSVP reservable bandwidth is independent of whether the source has a valid SR-MPLS SID mapping. This distinction matters because SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels.

Question 821

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An AE bundle loses one physical member but monitoring still shows the logical interface up, and traffic exceeds the remaining member's capacity. An engineer suggests the shortcut: "Judge success solely from the AE interface's up status while ignoring member utilization." Which critique explains the specific risk of that shortcut?

  1. LAG link redundancy cannot substitute for backup RE routing protocol state synchronization.
  2. Peer implementations and configuration differ; lack of helper cooperation can invalidate preserved-routing expectations.
  3. Logical link state does not certify available bandwidth after a partial member failure.
  4. Aggressive preemption repeats the same transient blackhole while the upstream path remains unready.

Explanation

Correct Answer

C:

Logical link state does not certify available bandwidth after a partial member failure. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Judge success solely from the AE interface's up status while ignoring member utilization. It fails to resolve the underlying problem that A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime. A sound alternative is the targeted engineering action: Check active LAG members and traffic distribution, then reduce load or restore capacity while preserving forwarding continuity.

Incorrect Answers

A:

LAG link redundancy cannot substitute for backup RE routing protocol state synchronization. That critique concerns a shortcut from the unrelated NSR backup routing synchronization case. The shortcut actually proposed in this controlled acceptance rehearsal is: Judge success solely from the AE interface's up status while ignoring member utilization. It should be rejected for the narrower reason that Logical link state does not certify available bandwidth after a partial member failure. This distinction matters because A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime.

B:

Peer implementations and configuration differ; lack of helper cooperation can invalidate preserved-routing expectations. That critique concerns a shortcut from the unrelated Graceful restart helper expectations case. The shortcut actually proposed in this controlled acceptance rehearsal is: Judge success solely from the AE interface's up status while ignoring member utilization. It should be rejected for the narrower reason that Logical link state does not certify available bandwidth after a partial member failure. This distinction matters because A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime.

D:

Aggressive preemption repeats the same transient blackhole while the upstream path remains unready. That critique concerns a shortcut from the unrelated VRRP preemption oscillation case. The shortcut actually proposed in this controlled acceptance rehearsal is: Judge success solely from the AE interface's up status while ignoring member utilization. It should be rejected for the narrower reason that Logical link state does not certify available bandwidth after a partial member failure. This distinction matters because A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime.

Question 822

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. An engineer suggests the shortcut: "Set an unrelated BGP MED and assume LDP sessions will use the RSVP LSP." Which critique explains the specific risk of that shortcut?

  1. BGP route advertisement hints do not turn on LDP tunneling over a particular RSVP LSP.
  2. Suppressing alarms cannot provide a precomputed alternate label-switched route.
  3. IP addressing does not repair the label operation needed at a transit LSR.
  4. RSVP reservable bandwidth is independent of whether the source has a valid SR-MPLS SID mapping.

Explanation

Correct Answer

A:

BGP route advertisement hints do not turn on LDP tunneling over a particular RSVP LSP. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Set an unrelated BGP MED and assume LDP sessions will use the RSVP LSP. It fails to resolve the underlying problem that LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport. A sound alternative is the targeted engineering action: Configure supported LDP-over-RSVP tunneling for the intended LSP and validate the resulting label-stack and FEC resolution.

Incorrect Answers

B:

Suppressing alarms cannot provide a precomputed alternate label-switched route. That critique concerns a shortcut from the unrelated RSVP link protection plan case. The shortcut actually proposed in this controlled acceptance rehearsal is: Set an unrelated BGP MED and assume LDP sessions will use the RSVP LSP. It should be rejected for the narrower reason that BGP route advertisement hints do not turn on LDP tunneling over a particular RSVP LSP. This distinction matters because LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport.

C:

IP addressing does not repair the label operation needed at a transit LSR. That critique concerns a shortcut from the unrelated Incoming label missing in LFIB case. The shortcut actually proposed in this controlled acceptance rehearsal is: Set an unrelated BGP MED and assume LDP sessions will use the RSVP LSP. It should be rejected for the narrower reason that BGP route advertisement hints do not turn on LDP tunneling over a particular RSVP LSP. This distinction matters because LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport.

D:

RSVP reservable bandwidth is independent of whether the source has a valid SR-MPLS SID mapping. That critique concerns a shortcut from the unrelated Segment routing SID advertisement case. The shortcut actually proposed in this controlled acceptance rehearsal is: Set an unrelated BGP MED and assume LDP sessions will use the RSVP LSP. It should be rejected for the narrower reason that BGP route advertisement hints do not turn on LDP tunneling over a particular RSVP LSP. This distinction matters because LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport.

Question 823

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An operations team expects a type-5 external route inside an OSPF stub area and reports the absence as an interface failure. An engineer suggests the shortcut: "Force external LSAs into the stub by indiscriminate route export." Which critique explains the specific risk of that shortcut?

  1. A static workaround can mask an unresolved control-plane synchronization problem and fail during another topology change.
  2. Unilateral removal of authentication does not establish a trusted matching configuration and weakens control-plane protection.
  3. Blanket redistribution can expose management and unrelated customer networks and create routing instability.
  4. Blindly redistributing external information conflicts with the intended stub-area containment model.

Explanation

Correct Answer

D:

Blindly redistributing external information conflicts with the intended stub-area containment model. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Force external LSAs into the stub by indiscriminate route export. It fails to resolve the underlying problem that OSPF stub areas intentionally restrict external LSAs and normally rely on appropriate default reachability from an ABR for external destinations. A sound alternative is the targeted engineering action: Validate stub-area design and use the intended summary or default-route strategy rather than expecting type-5 LSAs in the stub.

Incorrect Answers

A:

A static workaround can mask an unresolved control-plane synchronization problem and fail during another topology change. That critique concerns a shortcut from the unrelated OSPF LSDB discrepancy case. The shortcut actually proposed in this controlled acceptance rehearsal is: Force external LSAs into the stub by indiscriminate route export. It should be rejected for the narrower reason that Blindly redistributing external information conflicts with the intended stub-area containment model. This distinction matters because OSPF stub areas intentionally restrict external LSAs and normally rely on appropriate default reachability from an ABR for external destinations.

B:

Unilateral removal of authentication does not establish a trusted matching configuration and weakens control-plane protection. That critique concerns a shortcut from the unrelated OSPF authentication key mismatch case. The shortcut actually proposed in this controlled acceptance rehearsal is: Force external LSAs into the stub by indiscriminate route export. It should be rejected for the narrower reason that Blindly redistributing external information conflicts with the intended stub-area containment model. This distinction matters because OSPF stub areas intentionally restrict external LSAs and normally rely on appropriate default reachability from an ABR for external destinations.

C:

Blanket redistribution can expose management and unrelated customer networks and create routing instability. That critique concerns a shortcut from the unrelated OSPF export policy omission case. The shortcut actually proposed in this controlled acceptance rehearsal is: Force external LSAs into the stub by indiscriminate route export. It should be rejected for the narrower reason that Blindly redistributing external information conflicts with the intended stub-area containment model. This distinction matters because OSPF stub areas intentionally restrict external LSAs and normally rely on appropriate default reachability from an ABR for external destinations.

Question 824

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. An engineer suggests the shortcut: "Increase interface descriptions on both links until they look symmetric." Which critique explains the specific risk of that shortcut?

  1. Administrative descriptions and physical speeds do not establish equal routing cost or multipath eligibility.
  2. Hostname changes do not import a route between separate routing information bases.
  3. Changing accounting counters does not change first-match classification or forwarding decisions.
  4. Physical link-up does not establish downstream forwarding correctness beyond the adjacent hop.

Explanation

Correct Answer

A:

Administrative descriptions and physical speeds do not establish equal routing cost or multipath eligibility. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Increase interface descriptions on both links until they look symmetric. It fails to resolve the underlying problem that ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds. A sound alternative is the targeted engineering action: Validate both route metrics and platform multipath configuration so that two intended next hops are eligible for ECMP.

Incorrect Answers

B:

Hostname changes do not import a route between separate routing information bases. That critique concerns a shortcut from the unrelated RIB group forwarding copy case. The shortcut actually proposed in this controlled acceptance rehearsal is: Increase interface descriptions on both links until they look symmetric. It should be rejected for the narrower reason that Administrative descriptions and physical speeds do not establish equal routing cost or multipath eligibility. This distinction matters because ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds.

C:

Changing accounting counters does not change first-match classification or forwarding decisions. That critique concerns a shortcut from the unrelated Filter policy overmatch case. The shortcut actually proposed in this controlled acceptance rehearsal is: Increase interface descriptions on both links until they look symmetric. It should be rejected for the narrower reason that Administrative descriptions and physical speeds do not establish equal routing cost or multipath eligibility. This distinction matters because ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds.

D:

Physical link-up does not establish downstream forwarding correctness beyond the adjacent hop. That critique concerns a shortcut from the unrelated Static backup blackhole case. The shortcut actually proposed in this controlled acceptance rehearsal is: Increase interface descriptions on both links until they look symmetric. It should be rejected for the narrower reason that Administrative descriptions and physical speeds do not establish equal routing cost or multipath eligibility. This distinction matters because ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds.

Question 825

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An area border router carries area 20 routes, but traffic between area 20 and area 30 is missing because backbone attachment is broken. An engineer suggests the shortcut: "Redistribute every OSPF route into BGP to conceal the broken area hierarchy." Which critique explains the specific risk of that shortcut?

  1. Unilateral removal of authentication does not establish a trusted matching configuration and weakens control-plane protection.
  2. A process reset can temporarily restart negotiation but leaves the same incompatibility in place.
  3. Blanket redistribution can expose management and unrelated customer networks and create routing instability.
  4. Uncontrolled redistribution does not restore the designed OSPF backbone and can create loops or route leaks.

Explanation

Correct Answer

D:

Uncontrolled redistribution does not restore the designed OSPF backbone and can create loops or route leaks. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Redistribute every OSPF route into BGP to conceal the broken area hierarchy. It fails to resolve the underlying problem that Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers. A sound alternative is the targeted engineering action: Restore the intended area 0 backbone connectivity for the affected ABRs and verify inter-area summaries.

Incorrect Answers

A:

Unilateral removal of authentication does not establish a trusted matching configuration and weakens control-plane protection. That critique concerns a shortcut from the unrelated OSPF authentication key mismatch case. The shortcut actually proposed in this controlled acceptance rehearsal is: Redistribute every OSPF route into BGP to conceal the broken area hierarchy. It should be rejected for the narrower reason that Uncontrolled redistribution does not restore the designed OSPF backbone and can create loops or route leaks. This distinction matters because Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers.

B:

A process reset can temporarily restart negotiation but leaves the same incompatibility in place. That critique concerns a shortcut from the unrelated OSPF MTU ExStart stall case. The shortcut actually proposed in this controlled acceptance rehearsal is: Redistribute every OSPF route into BGP to conceal the broken area hierarchy. It should be rejected for the narrower reason that Uncontrolled redistribution does not restore the designed OSPF backbone and can create loops or route leaks. This distinction matters because Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers.

C:

Blanket redistribution can expose management and unrelated customer networks and create routing instability. That critique concerns a shortcut from the unrelated OSPF export policy omission case. The shortcut actually proposed in this controlled acceptance rehearsal is: Redistribute every OSPF route into BGP to conceal the broken area hierarchy. It should be rejected for the narrower reason that Uncontrolled redistribution does not restore the designed OSPF backbone and can create loops or route leaks. This distinction matters because Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers.

Question 826

During a controlled acceptance rehearsal of the same defect on a separate test network, 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. An engineer suggests the shortcut: "Increase the BGP keepalive rate and assume the route will be forwarded." Which critique explains the specific risk of that shortcut?

  1. OSPF LAN DR election settings do not modify the BGP path attributes being compared.
  2. Routing policy is evaluated for routes after a session forms; it cannot make an invalid peer-AS OPEN exchange acceptable.
  3. Router IDs are late tie-breakers and duplicating them cannot replace proper MED comparison or policy.
  4. Session liveness timers do not change IBGP route propagation rules.

Explanation

Correct Answer

D:

Session liveness timers do not change IBGP route propagation rules. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Increase the BGP keepalive rate and assume the route will be forwarded. It fails to resolve the underlying problem that Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design. A sound alternative is the targeted engineering action: Use the designed full-mesh or route-reflector topology and validate route reflection where appropriate.

Incorrect Answers

A:

OSPF LAN DR election settings do not modify the BGP path attributes being compared. That critique concerns a shortcut from the unrelated BGP AS-path comparison case. The shortcut actually proposed in this controlled acceptance rehearsal is: Increase the BGP keepalive rate and assume the route will be forwarded. It should be rejected for the narrower reason that Session liveness timers do not change IBGP route propagation rules. This distinction matters because Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design.

B:

Routing policy is evaluated for routes after a session forms; it cannot make an invalid peer-AS OPEN exchange acceptable. That critique concerns a shortcut from the unrelated BGP peer autonomous system mismatch case. The shortcut actually proposed in this controlled acceptance rehearsal is: Increase the BGP keepalive rate and assume the route will be forwarded. It should be rejected for the narrower reason that Session liveness timers do not change IBGP route propagation rules. This distinction matters because Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design.

C:

Router IDs are late tie-breakers and duplicating them cannot replace proper MED comparison or policy. That critique concerns a shortcut from the unrelated BGP MED comparison scope case. The shortcut actually proposed in this controlled acceptance rehearsal is: Increase the BGP keepalive rate and assume the route will be forwarded. It should be rejected for the narrower reason that Session liveness timers do not change IBGP route propagation rules. This distinction matters because Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design.

Question 827

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: After a provider switch reboot, the wrong access switch becomes the STP root because its bridge identifier is lower than the intended core root's ID. An engineer suggests the shortcut: "Increase OSPF router ID on the core switch to influence the STP root." Which critique explains the specific risk of that shortcut?

  1. Making redundant ports forward simultaneously can introduce a Layer 2 loop and broadcast storm.
  2. Descriptions do not participate in MSTP region identification or instance mapping.
  3. OSPF router identity is unrelated to the Layer 2 bridge ID used in STP root election.
  4. Layer 3 route preference does not determine Layer 2 spanning-tree root or port roles.

Explanation

Correct Answer

C:

OSPF router identity is unrelated to the Layer 2 bridge ID used in STP root election. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Increase OSPF router ID on the core switch to influence the STP root. It fails to resolve the underlying problem that Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address. A sound alternative is the targeted engineering action: Set a lower appropriate bridge priority for the approved root switch and validate the redundant root hierarchy.

Incorrect Answers

A:

Making redundant ports forward simultaneously can introduce a Layer 2 loop and broadcast storm. That critique concerns a shortcut from the unrelated RSTP alternate port activation case. The shortcut actually proposed in this controlled acceptance rehearsal is: Increase OSPF router ID on the core switch to influence the STP root. It should be rejected for the narrower reason that OSPF router identity is unrelated to the Layer 2 bridge ID used in STP root election. This distinction matters because Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address.

B:

Descriptions do not participate in MSTP region identification or instance mapping. That critique concerns a shortcut from the unrelated MSTP region mismatch case. The shortcut actually proposed in this controlled acceptance rehearsal is: Increase OSPF router ID on the core switch to influence the STP root. It should be rejected for the narrower reason that OSPF router identity is unrelated to the Layer 2 bridge ID used in STP root election. This distinction matters because Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address.

D:

Layer 3 route preference does not determine Layer 2 spanning-tree root or port roles. That critique concerns a shortcut from the unrelated Per-VLAN spanning-tree path case. The shortcut actually proposed in this controlled acceptance rehearsal is: Increase OSPF router ID on the core switch to influence the STP root. It should be rejected for the narrower reason that OSPF router identity is unrelated to the Layer 2 bridge ID used in STP root election. This distinction matters because Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address.

Question 828

During a controlled acceptance rehearsal of the same defect on a separate test network, 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. An engineer suggests the shortcut: "Manually advertise an unrelated default without fixing generation conditions." Which critique explains the specific risk of that shortcut?

  1. Physical link-up does not establish downstream forwarding correctness beyond the adjacent hop.
  2. An unconditional default masks missing prerequisites and may direct traffic into an unintended path.
  3. More routes in the original table do not implement selective forwarding through a different routing table.
  4. Hostname changes do not import a route between separate routing information bases.

Explanation

Correct Answer

B:

An unconditional default masks missing prerequisites and may direct traffic into an unintended path. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Manually advertise an unrelated default without fixing generation conditions. It fails to resolve the underlying problem that Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text. A sound alternative is the targeted engineering action: Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior.

Incorrect Answers

A:

Physical link-up does not establish downstream forwarding correctness beyond the adjacent hop. That critique concerns a shortcut from the unrelated Static backup blackhole case. The shortcut actually proposed in this controlled acceptance rehearsal is: Manually advertise an unrelated default without fixing generation conditions. It should be rejected for the narrower reason that An unconditional default masks missing prerequisites and may direct traffic into an unintended path. This distinction matters because Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text.

C:

More routes in the original table do not implement selective forwarding through a different routing table. That critique concerns a shortcut from the unrelated Filter-based forwarding classification case. The shortcut actually proposed in this controlled acceptance rehearsal is: Manually advertise an unrelated default without fixing generation conditions. It should be rejected for the narrower reason that An unconditional default masks missing prerequisites and may direct traffic into an unintended path. This distinction matters because Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text.

D:

Hostname changes do not import a route between separate routing information bases. That critique concerns a shortcut from the unrelated RIB group forwarding copy case. The shortcut actually proposed in this controlled acceptance rehearsal is: Manually advertise an unrelated default without fixing generation conditions. It should be rejected for the narrower reason that An unconditional default masks missing prerequisites and may direct traffic into an unintended path. This distinction matters because Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text.

Question 829

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: PE-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. An engineer suggests the shortcut: "Turn off all routing-policy checks globally to allow the questionable prefix." Which critique explains the specific risk of that shortcut?

  1. Forcing packets of one flow onto different paths can reorder packets and harm transport performance.
  2. Global relaxation hides a routing or addressing error and exposes unrelated prefixes to the same risk.
  3. More routes in the original table do not implement selective forwarding through a different routing table.
  4. Physical link-up does not establish downstream forwarding correctness beyond the adjacent hop.

Explanation

Correct Answer

B:

Global relaxation hides a routing or addressing error and exposes unrelated prefixes to the same risk. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Turn off all routing-policy checks globally to allow the questionable prefix. It fails to resolve the underlying problem that Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context. A sound alternative is the targeted engineering action: Inspect the relevant martian and routing-policy configuration and explicitly enforce the authorized treatment of that prefix.

Incorrect Answers

A:

Forcing packets of one flow onto different paths can reorder packets and harm transport performance. That critique concerns a shortcut from the unrelated Per-flow hash expectation case. The shortcut actually proposed in this controlled acceptance rehearsal is: Turn off all routing-policy checks globally to allow the questionable prefix. It should be rejected for the narrower reason that Global relaxation hides a routing or addressing error and exposes unrelated prefixes to the same risk. This distinction matters because Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context.

C:

More routes in the original table do not implement selective forwarding through a different routing table. That critique concerns a shortcut from the unrelated Filter-based forwarding classification case. The shortcut actually proposed in this controlled acceptance rehearsal is: Turn off all routing-policy checks globally to allow the questionable prefix. It should be rejected for the narrower reason that Global relaxation hides a routing or addressing error and exposes unrelated prefixes to the same risk. This distinction matters because Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context.

D:

Physical link-up does not establish downstream forwarding correctness beyond the adjacent hop. That critique concerns a shortcut from the unrelated Static backup blackhole case. The shortcut actually proposed in this controlled acceptance rehearsal is: Turn off all routing-policy checks globally to allow the questionable prefix. It should be rejected for the narrower reason that Global relaxation hides a routing or addressing error and exposes unrelated prefixes to the same risk. This distinction matters because Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context.

Question 830

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. An engineer suggests the shortcut: "Enable only interface-level LAG protection and assume routing processes synchronize automatically." Which critique explains the specific risk of that shortcut?

  1. Routing metrics in OSPF do not directly determine VRRP primary election.
  2. Aggressive preemption repeats the same transient blackhole while the upstream path remains unready.
  3. Unreasonably small intervals can cause false liveness failures and repeated routing churn.
  4. LAG link redundancy cannot substitute for backup RE routing protocol state synchronization.

Explanation

Correct Answer

D:

LAG link redundancy cannot substitute for backup RE routing protocol state synchronization. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Enable only interface-level LAG protection and assume routing processes synchronize automatically. It fails to resolve the underlying problem that NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers. A sound alternative is the targeted engineering action: Enable and verify supported Nonstop Active Routing with the necessary routing-state synchronization before a controlled switchover.

Incorrect Answers

A:

Routing metrics in OSPF do not directly determine VRRP primary election. That critique concerns a shortcut from the unrelated VRRP master priority failover case. The shortcut actually proposed in this controlled acceptance rehearsal is: Enable only interface-level LAG protection and assume routing processes synchronize automatically. It should be rejected for the narrower reason that LAG link redundancy cannot substitute for backup RE routing protocol state synchronization. This distinction matters because NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers.

B:

Aggressive preemption repeats the same transient blackhole while the upstream path remains unready. That critique concerns a shortcut from the unrelated VRRP preemption oscillation case. The shortcut actually proposed in this controlled acceptance rehearsal is: Enable only interface-level LAG protection and assume routing processes synchronize automatically. It should be rejected for the narrower reason that LAG link redundancy cannot substitute for backup RE routing protocol state synchronization. This distinction matters because NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers.

C:

Unreasonably small intervals can cause false liveness failures and repeated routing churn. That critique concerns a shortcut from the unrelated BFD detect timer too aggressive case. The shortcut actually proposed in this controlled acceptance rehearsal is: Enable only interface-level LAG protection and assume routing processes synchronize automatically. It should be rejected for the narrower reason that LAG link redundancy cannot substitute for backup RE routing protocol state synchronization. This distinction matters because NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers.


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.