Juniper JN0-364 Practice Test 46 - Prepaway
Practice Exams:

Pass Juniper JN0-364 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers!

30 Days Free Updates, Instant Download!

Verified By Experts
Premium File
$69.99 $76.99

JN0-364 Premium ETE File


  • Premium File 69 Questions & Answers. Last Update: Nov 17, 2026
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Juniper JN0-364 Practice Test 46

Question 450

A fictional Junos service-provider engineer encounters this scenario: A new static route to a GRE tunnel remote endpoint accidentally resolves through the same GRE tunnel interface meant to reach that endpoint. Distinguishing evidence: The route to the GRE remote destination shows the tunnel itself as next hop instead of an ordinary physical underlay path, and decapsulation counters stop increasing. Which bounded approval scope avoids unintended changes to other provider or customer services?

  1. Approve only the bounded change (Inspect the forwarding-table next hops and the Junos load-balancing policy, then measure multiple independent flows and validate the intended per-flow distribution.) after independently checking (A broad representative multi-flow test uses both eligible paths while sessions preserve stable forwarding and loss stays within the agreed threshold.), without quietly widening the provider or customer network scope.
  2. Approve only the bounded change (Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints.) after independently checking (The correct outer source-destination pair appears in captures and inner tunnel routes carry only the intended authorized traffic.), without quietly widening the provider or customer network scope.
  3. Approve only the bounded change (Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately.) after independently checking (The GRE remote destination resolves through the physical transport interface while desired inner prefixes use the tunnel and probes complete.), without quietly widening the provider or customer network scope.
  4. Approve only the bounded change (Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls.) after independently checking (Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped.), without quietly widening the provider or customer network scope.

Answer and Explanation

Correct Answer: C

A.

A separate release decision would approve only the bounded change (Inspect the forwarding-table next hops and the Junos load-balancing policy, then measure multiple independent flows and validate the intended per-flow distribution.) after independently checking (A broad representative multi-flow test uses both eligible paths while sessions preserve stable forwarding and loss stays within the agreed threshold.), without quietly widening the provider or customer network scope. It does not match the current change: Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately.

B.

An alternative approval would approve only the bounded change (Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints.) after independently checking (The correct outer source-destination pair appears in captures and inner tunnel routes carry only the intended authorized traffic.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are the route to the GRE remote destination shows the tunnel itself as next hop instead of an ordinary physical underlay path, and decapsulation counters stop increasing and the GRE remote destination resolves through the physical transport interface while desired inner prefixes use the tunnel and probes complete, respectively.

C.

The bounded proposal is: Approve only the bounded change (Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately.) after independently checking (The GRE remote destination resolves through the physical transport interface while desired inner prefixes use the tunnel and probes complete.), without quietly widening the provider or customer network scope. The separate acceptance measure remains: The GRE remote destination resolves through the physical transport interface while desired inner prefixes use the tunnel and probes complete.

D.

A separate release decision would approve only the bounded change (Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls.) after independently checking (Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped.), without quietly widening the provider or customer network scope. It does not match the current change: Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately.

Question 451

A fictional Junos service-provider engineer encounters this scenario: A provider core chassis reports a backup Routing Engine ready after a software upgrade, but a planned switchover would lose critical interface state continuity. Distinguishing evidence: High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed. Which specific bounded Junos routing or switching correction best addresses this service-provider issue?

  1. Bounded remedy: Check GRES prerequisites, chassis versions and redundancy synchronization before authorizing a controlled Routing Engine switchover.
  2. Bounded remedy: Review VRRP advertisement, tracking and preemption conditions, then restore the documented gateway active-standby policy without forcing an untested outage.
  3. Bounded remedy: Review the OSPF export policy and prefix scope, then explicitly permit only the approved external destination while preserving other route exclusions.
  4. Bounded remedy: Distinguish GR, GRES and NSR supported roles, verify actual chassis and protocol prerequisites and use only approved continuity techniques for the planned event.

Answer and Explanation

Correct Answer: A

A.

High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed. GRES depends on supported synchronized Routing Engine state, not hardware redundancy alone. The appropriate response is: Check GRES prerequisites, chassis versions and redundancy synchronization before authorizing a controlled Routing Engine switchover. Confirm it with: Redundancy status becomes ready and the approved test preserves operational interface state within documented continuity targets.

B.

Another proposed action is: Review VRRP advertisement, tracking and preemption conditions, then restore the documented gateway active-standby policy without forcing an untested outage. It targets a different dependency; the evidence here is High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed.

C.

Another option proposes: Review the OSPF export policy and prefix scope, then explicitly permit only the approved external destination while preserving other route exclusions. The specific correction is: Check GRES prerequisites, chassis versions and redundancy synchronization before authorizing a controlled Routing Engine switchover. The deciding evidence is: High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed.

D.

That alternative concerns: Distinguish GR, GRES and NSR supported roles, verify actual chassis and protocol prerequisites and use only approved continuity techniques for the planned event. The relevant evidence is High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed. The corresponding fix is: Check GRES prerequisites, chassis versions and redundancy synchronization before authorizing a controlled Routing Engine switchover.

Question 452

A fictional Junos service-provider engineer encounters this scenario: A provider core chassis reports a backup Routing Engine ready after a software upgrade, but a planned switchover would lose critical interface state continuity. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?

  1. Differentiating observation: OSPF neighbor and interface details reveal different hello and dead intervals on the directly connected segment even though addresses and area are aligned.
  2. Differentiating observation: Interface bundle detail shows three collecting and distributing members while one physical port is inconsistently selected or has uncorrected errors.
  3. Differentiating observation: VRRP state displays show changed effective priorities, interface tracking, or configured preemption behavior that differs from the approved failback design.
  4. Differentiating observation: High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed.

Answer and Explanation

Correct Answer: D

A.

Another piece of evidence concerns OSPF neighbor and interface details reveal different hello and dead intervals on the directly connected segment even though addresses and area are aligned. The current incident instead shows: High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed. This distinction supports the action: Check GRES prerequisites, chassis versions and redundancy synchronization before authorizing a controlled Routing Engine switchover.

B.

Another alternative would address Interface bundle detail shows three collecting and distributing members while one physical port is inconsistently selected or has uncorrected errors as decisive. The actual evidence in this case is High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed.

C.

This other option describes: VRRP state displays show changed effective priorities, interface tracking, or configured preemption behavior that differs from the approved failback design. The problem to explain is different: High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed.

D.

The record points to High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed. After confirming the clue, the appropriate response is: Check GRES prerequisites, chassis versions and redundancy synchronization before authorizing a controlled Routing Engine switchover.

Question 453

A fictional Junos service-provider engineer encounters this scenario: A provider core chassis reports a backup Routing Engine ready after a software upgrade, but a planned switchover would lose critical interface state continuity. Distinguishing evidence: High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed. Which Junos networking principle best explains the relevant engineering decision?

  1. Applicable protocol principle: IP tunnels require reachable correctly configured outer endpoints independently of the inner routed service. Evidence for this case: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.
  2. Applicable protocol principle: GRES depends on supported synchronized Routing Engine state, not hardware redundancy alone. Evidence for this case: High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed.
  3. Applicable protocol principle: BFD offers fast fault detection but detection intervals must reflect path and platform processing behavior. Evidence for this case: BFD history indicates missed rapid control packets correlated with CPU spikes and peer timer negotiation different from the intended service design.
  4. Applicable protocol principle: GR, GRES and NSR address different aspects of routing and Routing Engine continuity and must be separately verified. Evidence for this case: Change review shows graceful restart configured but NSR or other high-availability capabilities absent and a test exposes a temporary control-plane adjacency resynchronization.

Answer and Explanation

Correct Answer: B

A.

A different principle is: IP tunnels require reachable correctly configured outer endpoints independently of the inner routed service. Evidence for this case: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer. The present evidence, however, is High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed. The relevant rule is: GRES depends on supported synchronized Routing Engine state, not hardware redundancy alone.

B.

The relevant principle is: GRES depends on supported synchronized Routing Engine state, not hardware redundancy alone. The case evidence is High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed. The practical response is: Check GRES prerequisites, chassis versions and redundancy synchronization before authorizing a controlled Routing Engine switchover.

C.

The competing option invokes: BFD offers fast fault detection but detection intervals must reflect path and platform processing behavior. Evidence for this case: BFD history indicates missed rapid control packets correlated with CPU spikes and peer timer negotiation different from the intended service design. The present evidence is: High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed. The case-relevant principle is: GRES depends on supported synchronized Routing Engine state, not hardware redundancy alone.

D.

That principle concerns another fact pattern: GR, GRES and NSR address different aspects of routing and Routing Engine continuity and must be separately verified. Evidence for this case: Change review shows graceful restart configured but NSR or other high-availability capabilities absent and a test exposes a temporary control-plane adjacency resynchronization. Here the key fact is: High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed.

Question 454

A fictional Junos service-provider engineer encounters this scenario: A provider core chassis reports a backup Routing Engine ready after a software upgrade, but a planned switchover would lose critical interface state continuity. Intended bounded correction: Check GRES prerequisites, chassis versions and redundancy synchronization before authorizing a controlled Routing Engine switchover. Which independently verifiable test best demonstrates the intended correction worked?

  1. Independent verification: A sandbox or maintenance test measures the agreed forwarding and neighbor behavior for each configured redundancy feature before production rollout.
  2. Independent verification: Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped.
  3. Independent verification: All intended members participate compatibly and multi-flow traffic crosses the LAG without selective packet loss.
  4. Independent verification: Redundancy status becomes ready and the approved test preserves operational interface state within documented continuity targets.

Answer and Explanation

Correct Answer: D

A.

That result would assess another condition: A sandbox or maintenance test measures the agreed forwarding and neighbor behavior for each configured redundancy feature before production rollout. The correct criterion is directly linked to the finding: High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed.

B.

Another proposed result is: Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped. It would not independently establish the required outcome: Redundancy status becomes ready and the approved test preserves operational interface state within documented continuity targets.

C.

A different option checks: All intended members participate compatibly and multi-flow traffic crosses the LAG without selective packet loss. The case-specific acceptance condition is instead Redundancy status becomes ready and the approved test preserves operational interface state within documented continuity targets.

D.

The independent verification condition is: Redundancy status becomes ready and the approved test preserves operational interface state within documented continuity targets. That result checks whether the original evidence—High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed—has been addressed.

Question 455

A fictional Junos service-provider engineer encounters this scenario: A provider core chassis reports a backup Routing Engine ready after a software upgrade, but a planned switchover would lose critical interface state continuity. Distinguishing evidence: High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed. Which material service-availability, routing, switching or security risk most directly needs control?

  1. Meaningful operational caution: Conflating distinct high-availability features can make unsupported hitless-upgrade promises and lead to unexpected service loss.
  2. Meaningful operational caution: Assuming the presence of two Routing Engines guarantees hitless switchover can cause avoidable outage.
  3. Meaningful operational caution: Changing global route preferences to force a broken next hop can blackhole unrelated customer prefixes.
  4. Meaningful operational caution: Adding capacity without correcting a faulty member can conceal a persistent blackhole for hashed customer flows.

Answer and Explanation

Correct Answer: B

A.

This limitation concerns another setting: Conflating distinct high-availability features can make unsupported hitless-upgrade promises and lead to unexpected service loss. The observed facts here make a different caution decisive: Assuming the presence of two Routing Engines guarantees hitless switchover can cause avoidable outage.

B.

A necessary safeguard is: Assuming the presence of two Routing Engines guarantees hitless switchover can cause avoidable outage. The proposed correction remains: Check GRES prerequisites, chassis versions and redundancy synchronization before authorizing a controlled Routing Engine switchover.

C.

Another emphasis concerns: Changing global route preferences to force a broken next hop can blackhole unrelated customer prefixes. The current change is Check GRES prerequisites, chassis versions and redundancy synchronization before authorizing a controlled Routing Engine switchover; the material limitation is Assuming the presence of two Routing Engines guarantees hitless switchover can cause avoidable outage.

D.

This limitation concerns another setting: Adding capacity without correcting a faulty member can conceal a persistent blackhole for hashed customer flows. The observed facts here make a different caution decisive: Assuming the presence of two Routing Engines guarantees hitless switchover can cause avoidable outage.

Question 456

A fictional Junos service-provider engineer encounters this scenario: A provider core chassis reports a backup Routing Engine ready after a software upgrade, but a planned switchover would lose critical interface state continuity. Distinguishing evidence: High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed. Which focused investigation is the most useful before modifying the network configuration?

  1. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: VRRP state displays show changed effective priorities, interface tracking, or configured preemption behavior that differs from the approved failback design.
  2. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed.
  3. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: OSPF neighbor and interface details reveal different hello and dead intervals on the directly connected segment even though addresses and area are aligned.
  4. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Interface bundle detail shows three collecting and distributing members while one physical port is inconsistently selected or has uncorrected errors.

Answer and Explanation

Correct Answer: B

A.

Another investigation would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: VRRP state displays show changed effective priorities, interface tracking, or configured preemption behavior that differs from the approved failback design. It does not directly establish the reported condition: High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed.

B.

The focused investigation should compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed. It is tied to the observed evidence: High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed. It tests the conditions for this response: Check GRES prerequisites, chassis versions and redundancy synchronization before authorizing a controlled Routing Engine switchover.

C.

Another check would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: OSPF neighbor and interface details reveal different hello and dead intervals on the directly connected segment even though addresses and area are aligned. The case observation to isolate is High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed. The focused check here is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed.

D.

Another investigation would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Interface bundle detail shows three collecting and distributing members while one physical port is inconsistently selected or has uncorrected errors. It does not directly establish the reported condition: High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed.

Question 457

A fictional Junos service-provider engineer encounters this scenario: A provider core chassis reports a backup Routing Engine ready after a software upgrade, but a planned switchover would lose critical interface state continuity. Distinguishing evidence: High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed. Which controlled operational implementation sequence best protects the related provider service?

  1. Controlled engineering sequence: First verify the observed failure (Interface bundle detail shows three collecting and distributing members while one physical port is inconsistently selected or has uncorrected errors.); review and authorize the bounded correction (Inspect LAG member speed, LACP participation and physical health, then repair or isolate the anomalous member under approved redundancy policy.); then independently verify the intended outcome (All intended members participate compatibly and multi-flow traffic crosses the LAG without selective packet loss.) before production rollout.
  2. Controlled engineering sequence: First verify the observed failure (Change review shows graceful restart configured but NSR or other high-availability capabilities absent and a test exposes a temporary control-plane adjacency resynchronization.); review and authorize the bounded correction (Distinguish GR, GRES and NSR supported roles, verify actual chassis and protocol prerequisites and use only approved continuity techniques for the planned event.); then independently verify the intended outcome (A sandbox or maintenance test measures the agreed forwarding and neighbor behavior for each configured redundancy feature before production rollout.) before production rollout.
  3. Controlled engineering sequence: First verify the observed failure (The route to the GRE remote destination shows the tunnel itself as next hop instead of an ordinary physical underlay path, and decapsulation counters stop increasing.); review and authorize the bounded correction (Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately.); then independently verify the intended outcome (The GRE remote destination resolves through the physical transport interface while desired inner prefixes use the tunnel and probes complete.) before production rollout.
  4. Controlled engineering sequence: First verify the observed failure (High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed.); review and authorize the bounded correction (Check GRES prerequisites, chassis versions and redundancy synchronization before authorizing a controlled Routing Engine switchover.); then independently verify the intended outcome (Redundancy status becomes ready and the approved test preserves operational interface state within documented continuity targets.) before production rollout.

Answer and Explanation

Correct Answer: D

A.

Another action-and-check pairing is: First verify the observed failure (Interface bundle detail shows three collecting and distributing members while one physical port is inconsistently selected or has uncorrected errors.); review and authorize the bounded correction (Inspect LAG member speed, LACP participation and physical health, then repair or isolate the anomalous member under approved redundancy policy.); then independently verify the intended outcome (All intended members participate compatibly and multi-flow traffic crosses the LAG without selective packet loss.) before production rollout. The evidence here is High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed. The required action and proof are Check GRES prerequisites, chassis versions and redundancy synchronization before authorizing a controlled Routing Engine switchover and Redundancy status becomes ready and the approved test preserves operational interface state within documented continuity targets.

B.

An alternative plan is: First verify the observed failure (Change review shows graceful restart configured but NSR or other high-availability capabilities absent and a test exposes a temporary control-plane adjacency resynchronization.); review and authorize the bounded correction (Distinguish GR, GRES and NSR supported roles, verify actual chassis and protocol prerequisites and use only approved continuity techniques for the planned event.); then independently verify the intended outcome (A sandbox or maintenance test measures the agreed forwarding and neighbor behavior for each configured redundancy feature before production rollout.) before production rollout. It does not test the case-specific condition: High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed.

C.

Another possible combination is: First verify the observed failure (The route to the GRE remote destination shows the tunnel itself as next hop instead of an ordinary physical underlay path, and decapsulation counters stop increasing.); review and authorize the bounded correction (Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately.); then independently verify the intended outcome (The GRE remote destination resolves through the physical transport interface while desired inner prefixes use the tunnel and probes complete.) before production rollout. The current record instead supports Check GRES prerequisites, chassis versions and redundancy synchronization before authorizing a controlled Routing Engine switchover, verified by Redundancy status becomes ready and the approved test preserves operational interface state within documented continuity targets.

D.

The starting point is High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed. The proposed action and its separate check are Check GRES prerequisites, chassis versions and redundancy synchronization before authorizing a controlled Routing Engine switchover and Redundancy status becomes ready and the approved test preserves operational interface state within documented continuity targets, respectively.

Question 458

A fictional Junos service-provider engineer encounters this scenario: A provider core chassis reports a backup Routing Engine ready after a software upgrade, but a planned switchover would lose critical interface state continuity. Distinguishing evidence: High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed. Which set of evidence, limited change and independent validation best justifies authorization?

  1. Approval package: observed evidence (Route inspection shows several tenant networks imported into a shared routing table through a broad RIB group rather than the single approved resolver route.), limited correction (Constrain the policy and RIB group to the documented destination and routing instances, then review import consequences in a candidate configuration.), independently measurable result (The shared resolver prefix is available to the approved instance while unauthorized customer routes are absent from both route displays and forwarding tests.).
  2. Approval package: observed evidence (Interface bundle detail shows three collecting and distributing members while one physical port is inconsistently selected or has uncorrected errors.), limited correction (Inspect LAG member speed, LACP participation and physical health, then repair or isolate the anomalous member under approved redundancy policy.), independently measurable result (All intended members participate compatibly and multi-flow traffic crosses the LAG without selective packet loss.).
  3. Approval package: observed evidence (BFD history indicates missed rapid control packets correlated with CPU spikes and peer timer negotiation different from the intended service design.), limited correction (Check supported BFD interval, multiplier, processing and path-loss evidence, then align an achievable detection profile and validate actual loss behavior.), independently measurable result (BFD remains stable under representative load and a controlled link failure triggers timely protected-route convergence.).
  4. Approval package: observed evidence (High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed.), limited correction (Check GRES prerequisites, chassis versions and redundancy synchronization before authorizing a controlled Routing Engine switchover.), independently measurable result (Redundancy status becomes ready and the approved test preserves operational interface state within documented continuity targets.).

Answer and Explanation

Correct Answer: D

A.

Another approval action is: Observed evidence (Route inspection shows several tenant networks imported into a shared routing table through a broad RIB group rather than the single approved resolver route.), limited correction (Constrain the policy and RIB group to the documented destination and routing instances, then review import consequences in a candidate configuration.), independently measurable result (The shared resolver prefix is available to the approved instance while unauthorized customer routes are absent from both route displays and forwarding tests.). The relevant evidence and acceptance are High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed and Redundancy status becomes ready and the approved test preserves operational interface state within documented continuity targets, respectively.

B.

Another approval package concerns: Observed evidence (Interface bundle detail shows three collecting and distributing members while one physical port is inconsistently selected or has uncorrected errors.), limited correction (Inspect LAG member speed, LACP participation and physical health, then repair or isolate the anomalous member under approved redundancy policy.), independently measurable result (All intended members participate compatibly and multi-flow traffic crosses the LAG without selective packet loss.). The present scope must instead be justified by High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed.

C.

An alternative release decision is: Observed evidence (BFD history indicates missed rapid control packets correlated with CPU spikes and peer timer negotiation different from the intended service design.), limited correction (Check supported BFD interval, multiplier, processing and path-loss evidence, then align an achievable detection profile and validate actual loss behavior.), independently measurable result (BFD remains stable under representative load and a controlled link failure triggers timely protected-route convergence.). It does not match the current change: Check GRES prerequisites, chassis versions and redundancy synchronization before authorizing a controlled Routing Engine switchover.

D.

The bounded proposal is: Observed evidence (High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed.), limited correction (Check GRES prerequisites, chassis versions and redundancy synchronization before authorizing a controlled Routing Engine switchover.), independently measurable result (Redundancy status becomes ready and the approved test preserves operational interface state within documented continuity targets.). The separate acceptance measure remains: Redundancy status becomes ready and the approved test preserves operational interface state within documented continuity targets.

Question 459

A fictional Junos service-provider engineer encounters this scenario: A provider core chassis reports a backup Routing Engine ready after a software upgrade, but a planned switchover would lose critical interface state continuity. Distinguishing evidence: High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed. If the change fails its expected acceptance test, which controlled recovery approach is most appropriate?

  1. If testing fails: pause changes, preserve the differentiating evidence (The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.), restore the last approved safe network state and reassess gre interface is reachable only from the wrong source address.
  2. If testing fails: pause changes, preserve the differentiating evidence (High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed.), restore the last approved safe network state and reassess dual routing engine gres state is not synchronized.
  3. If testing fails: pause changes, preserve the differentiating evidence (VRRP state displays show changed effective priorities, interface tracking, or configured preemption behavior that differs from the approved failback design.), restore the last approved safe network state and reassess vrrp backup becomes master after an expected preemption check.
  4. If testing fails: pause changes, preserve the differentiating evidence (Change review shows graceful restart configured but NSR or other high-availability capabilities absent and a test exposes a temporary control-plane adjacency resynchronization.), restore the last approved safe network state and reassess nonstop routing expectations are incorrectly inferred from graceful restart.

Answer and Explanation

Correct Answer: B

A.

Another option proposes: Pause changes, preserve the differentiating evidence (The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.), restore the last approved safe network state and reassess gre interface is reachable only from the wrong source address. Its assumptions differ from the observed failure; the appropriate recovery is: Pause changes, preserve the differentiating evidence (High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed.), restore the last approved safe network state and reassess dual routing engine gres state is not synchronized.

B.

If the change fails acceptance, the bounded recovery is: Pause changes, preserve the differentiating evidence (High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed.), restore the last approved safe network state and reassess dual routing engine gres state is not synchronized. The case-specific risk is Assuming the presence of two Routing Engines guarantees hitless switchover can cause avoidable outage. The original evidence remains: High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed.

C.

Another recovery route would pause changes, preserve the differentiating evidence (VRRP state displays show changed effective priorities, interface tracking, or configured preemption behavior that differs from the approved failback design.), restore the last approved safe network state and reassess vrrp backup becomes master after an expected preemption check. It does not preserve the condition of this case: High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed. The bounded fallback is: Pause changes, preserve the differentiating evidence (High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed.), restore the last approved safe network state and reassess dual routing engine gres state is not synchronized.

D.

Another option proposes: Pause changes, preserve the differentiating evidence (Change review shows graceful restart configured but NSR or other high-availability capabilities absent and a test exposes a temporary control-plane adjacency resynchronization.), restore the last approved safe network state and reassess nonstop routing expectations are incorrectly inferred from graceful restart. Its assumptions differ from the observed failure; the appropriate recovery is: Pause changes, preserve the differentiating evidence (High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed.), restore the last approved safe network state and reassess dual routing engine gres state is not synchronized.

Question 460

A fictional Junos service-provider engineer encounters this scenario: A provider core chassis reports a backup Routing Engine ready after a software upgrade, but a planned switchover would lose critical interface state continuity. Distinguishing evidence: High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed. Which bounded approval scope avoids unintended changes to other provider or customer services?

  1. Approve only the bounded change (Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance.) after independently checking (Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero.), without quietly widening the provider or customer network scope.
  2. Approve only the bounded change (Review VRRP advertisement, tracking and preemption conditions, then restore the documented gateway active-standby policy without forcing an untested outage.) after independently checking (Controlled primary failure and recovery show a predictable gateway master role and preserved host connectivity.), without quietly widening the provider or customer network scope.
  3. Approve only the bounded change (Check supported BFD interval, multiplier, processing and path-loss evidence, then align an achievable detection profile and validate actual loss behavior.) after independently checking (BFD remains stable under representative load and a controlled link failure triggers timely protected-route convergence.), without quietly widening the provider or customer network scope.
  4. Approve only the bounded change (Check GRES prerequisites, chassis versions and redundancy synchronization before authorizing a controlled Routing Engine switchover.) after independently checking (Redundancy status becomes ready and the approved test preserves operational interface state within documented continuity targets.), without quietly widening the provider or customer network scope.

Answer and Explanation

Correct Answer: D

A.

Another proposed approval would approve only the bounded change (Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance.) after independently checking (Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero.), without quietly widening the provider or customer network scope. The present scope must instead be justified by High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed.

B.

A separate release decision would approve only the bounded change (Review VRRP advertisement, tracking and preemption conditions, then restore the documented gateway active-standby policy without forcing an untested outage.) after independently checking (Controlled primary failure and recovery show a predictable gateway master role and preserved host connectivity.), without quietly widening the provider or customer network scope. It does not match the current change: Check GRES prerequisites, chassis versions and redundancy synchronization before authorizing a controlled Routing Engine switchover.

C.

An alternative approval would approve only the bounded change (Check supported BFD interval, multiplier, processing and path-loss evidence, then align an achievable detection profile and validate actual loss behavior.) after independently checking (BFD remains stable under representative load and a controlled link failure triggers timely protected-route convergence.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed and Redundancy status becomes ready and the approved test preserves operational interface state within documented continuity targets, respectively.

D.

The change-control boundary is: Approve only the bounded change (Check GRES prerequisites, chassis versions and redundancy synchronization before authorizing a controlled Routing Engine switchover.) after independently checking (Redundancy status becomes ready and the approved test preserves operational interface state within documented continuity targets.), without quietly widening the provider or customer network scope. The evidence for this scope is High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed.

Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests