Juniper JN0-364 Practice Test 11 - 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 11

Question 100

A fictional Junos service-provider engineer encounters this scenario: A provider edge learns an external prefix from another protocol but its OSPF neighbors never receive the intended authorized service route. Distinguishing evidence: Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term. Which bounded approval scope avoids unintended changes to other provider or customer services?

  1. Approve only the bounded change (Compare link-state database reachability with route calculation, preference and active forwarding selection before modifying advertisement filters.) after independently checking (Database entries and active route selection are explainable, and probes follow the intended next hop without falsely requiring every LSA to be an active route.), without quietly widening the provider or customer network scope.
  2. Approve only the bounded change (Apply a precise export filter and route-policy tests for public prefixes, then confirm rejected customer-only routes stay internal.) after independently checking (Upstream advertised-route output contains only approved prefixes and the private customer destination remains available in its intended instance.), without quietly widening the provider or customer network scope.
  3. 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.
  4. Approve only the bounded change (Review the OSPF export policy and prefix scope, then explicitly permit only the approved external destination while preserving other route exclusions.) after independently checking (Neighbor route views receive the approved external prefix and unrelated tenant networks remain unadvertised.), 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 (Compare link-state database reachability with route calculation, preference and active forwarding selection before modifying advertisement filters.) after independently checking (Database entries and active route selection are explainable, and probes follow the intended next hop without falsely requiring every LSA to be an active route.), without quietly widening the provider or customer network scope. The present scope must instead be justified by Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term.

B.

A separate release decision would approve only the bounded change (Apply a precise export filter and route-policy tests for public prefixes, then confirm rejected customer-only routes stay internal.) after independently checking (Upstream advertised-route output contains only approved prefixes and the private customer destination remains available in its intended instance.), without quietly widening the provider or customer network scope. It does not match the current change: Review the OSPF export policy and prefix scope, then explicitly permit only the approved external destination while preserving other route exclusions.

C.

An alternative 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 relevant evidence and acceptance are Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term and Neighbor route views receive the approved external prefix and unrelated tenant networks remain unadvertised, respectively.

D.

The change-control boundary is: Approve only the bounded change (Review the OSPF export policy and prefix scope, then explicitly permit only the approved external destination while preserving other route exclusions.) after independently checking (Neighbor route views receive the approved external prefix and unrelated tenant networks remain unadvertised.), without quietly widening the provider or customer network scope. The evidence for this scope is Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term.

Question 101

A fictional Junos service-provider engineer encounters this scenario: A troubleshooting script reports a remote OSPF branch unreachable even though traffic in a customer virtual router is healthy. Distinguishing evidence: The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance. Which specific bounded Junos routing or switching correction best addresses this service-provider issue?

  1. Bounded remedy: Repeat routing and operational tests explicitly in the correct customer instance and investigate any actual gap without changing global routing.
  2. Bounded remedy: Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance.
  3. Bounded remedy: Compare link-state database reachability with route calculation, preference and active forwarding selection before modifying advertisement filters.
  4. Bounded remedy: Inspect the advertised address-family-specific TLVs and corresponding IPv6 routing table and interface support before changing IS-IS policy.

Answer and Explanation

Correct Answer: A

A.

Routing-instance OSPF diagnostic probes point at the wrong table. The decisive observation is the script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance. The proposed fix is: Repeat routing and operational tests explicitly in the correct customer instance and investigate any actual gap without changing global routing. An observable result is: Route displays and sourced tests from the correct instance explain end-to-end reachability and isolate the false default-table alarm.

B.

Another proposed action is: Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance. It targets a different dependency; the evidence here is the script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance.

C.

Another option proposes: Compare link-state database reachability with route calculation, preference and active forwarding selection before modifying advertisement filters. The specific correction is: Repeat routing and operational tests explicitly in the correct customer instance and investigate any actual gap without changing global routing. The deciding evidence is: The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance.

D.

That alternative concerns: Inspect the advertised address-family-specific TLVs and corresponding IPv6 routing table and interface support before changing IS-IS policy. The relevant evidence is the script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance. The corresponding fix is: Repeat routing and operational tests explicitly in the correct customer instance and investigate any actual gap without changing global routing.

Question 102

A fictional Junos service-provider engineer encounters this scenario: A troubleshooting script reports a remote OSPF branch unreachable even though traffic in a customer virtual router is healthy. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?

  1. Differentiating observation: The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance.
  2. Differentiating observation: OSPF database output includes relevant link-state information, whereas the active route table prefers a more specific or otherwise preferred competing route for the destination.
  3. Differentiating observation: The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway.
  4. 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.

Answer and Explanation

Correct Answer: A

A.

The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance. That fact identifies the relevant dependency, rather than a separate issue. Protocol troubleshooting must use the correct routing-instance and route-table context.

B.

Another proposed finding is: OSPF database output includes relevant link-state information, whereas the active route table prefers a more specific or otherwise preferred competing route for the destination. It is not the recorded discriminator, which is the script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance.

C.

Another piece of evidence concerns the routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway. The current incident instead shows: The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance. This distinction supports the action: Repeat routing and operational tests explicitly in the correct customer instance and investigate any actual gap without changing global routing.

D.

Another alternative would address OSPF neighbor and interface details reveal different hello and dead intervals on the directly connected segment even though addresses and area are aligned as decisive. The actual evidence in this case is the script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance.

Question 103

A fictional Junos service-provider engineer encounters this scenario: A troubleshooting script reports a remote OSPF branch unreachable even though traffic in a customer virtual router is healthy. Distinguishing evidence: The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance. Which Junos networking principle best explains the relevant engineering decision?

  1. Applicable protocol principle: IS-IS LAN DIS election and shortest-path metrics are distinct control-plane mechanisms. Evidence for this case: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths.
  2. Applicable protocol principle: OSPF neighbors require compatible interface-level parameters, including timing behavior. Evidence for this case: OSPF neighbor and interface details reveal different hello and dead intervals on the directly connected segment even though addresses and area are aligned.
  3. Applicable protocol principle: Controlled OSPF route redistribution is governed by route policy and explicit eligible prefix matches. Evidence for this case: Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term.
  4. Applicable protocol principle: Protocol troubleshooting must use the correct routing-instance and route-table context. Evidence for this case: The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance.

Answer and Explanation

Correct Answer: D

A.

The competing option invokes: IS-IS LAN DIS election and shortest-path metrics are distinct control-plane mechanisms. Evidence for this case: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths. The present evidence is: The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance. The case-relevant principle is: Protocol troubleshooting must use the correct routing-instance and route-table context.

B.

That principle concerns another fact pattern: OSPF neighbors require compatible interface-level parameters, including timing behavior. Evidence for this case: OSPF neighbor and interface details reveal different hello and dead intervals on the directly connected segment even though addresses and area are aligned. Here the key fact is: The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance.

C.

A different principle is: Controlled OSPF route redistribution is governed by route policy and explicit eligible prefix matches. Evidence for this case: Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term. The present evidence, however, is the script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance. The relevant rule is: Protocol troubleshooting must use the correct routing-instance and route-table context.

D.

The relevant principle is: Protocol troubleshooting must use the correct routing-instance and route-table context. The case evidence is the script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance. The practical response is: Repeat routing and operational tests explicitly in the correct customer instance and investigate any actual gap without changing global routing.

Question 104

A fictional Junos service-provider engineer encounters this scenario: A troubleshooting script reports a remote OSPF branch unreachable even though traffic in a customer virtual router is healthy. Intended bounded correction: Repeat routing and operational tests explicitly in the correct customer instance and investigate any actual gap without changing global routing. Which independently verifiable test best demonstrates the intended correction worked?

  1. Independent verification: Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero.
  2. Independent verification: Neighbor route views receive the approved external prefix and unrelated tenant networks remain unadvertised.
  3. Independent verification: The designated intermediate system role matches documented circuit priority policy and shortest-path computations remain consistent.
  4. Independent verification: Route displays and sourced tests from the correct instance explain end-to-end reachability and isolate the false default-table alarm.

Answer and Explanation

Correct Answer: D

A.

A different option checks: Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero. The case-specific acceptance condition is instead Route displays and sourced tests from the correct instance explain end-to-end reachability and isolate the false default-table alarm.

B.

Passing that test would not establish resolution of the stated issue. The relevant proof is: Route displays and sourced tests from the correct instance explain end-to-end reachability and isolate the false default-table alarm.

C.

That result would assess another condition: The designated intermediate system role matches documented circuit priority policy and shortest-path computations remain consistent. The correct criterion is directly linked to the finding: The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance.

D.

Route displays and sourced tests from the correct instance explain end-to-end reachability and isolate the false default-table alarm. This verifies the required result rather than merely stating the action; the original issue was the script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance.

Question 105

A fictional Junos service-provider engineer encounters this scenario: A troubleshooting script reports a remote OSPF branch unreachable even though traffic in a customer virtual router is healthy. Distinguishing evidence: The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance. Which material service-availability, routing, switching or security risk most directly needs control?

  1. Meaningful operational caution: Blindly restarting IS-IS on every router can add topology disruption without proving database cause.
  2. Meaningful operational caution: Debugging only the global table can prompt unintended configuration changes to an otherwise healthy customer VPN.
  3. Meaningful operational caution: Adding a blanket export accept can redistribute routes that are not part of the contracted service.
  4. Meaningful operational caution: Treating expected two-way neighbor states as faults can trigger unnecessary election changes and route churn.

Answer and Explanation

Correct Answer: B

A.

Another emphasis concerns: Blindly restarting IS-IS on every router can add topology disruption without proving database cause. The current change is Repeat routing and operational tests explicitly in the correct customer instance and investigate any actual gap without changing global routing; the material limitation is Debugging only the global table can prompt unintended configuration changes to an otherwise healthy customer VPN.

B.

Debugging only the global table can prompt unintended configuration changes to an otherwise healthy customer VPN. That boundary protects the documented change, Repeat routing and operational tests explicitly in the correct customer instance and investigate any actual gap without changing global routing, from introducing an unrelated problem.

C.

Another caution is: Adding a blanket export accept can redistribute routes that are not part of the contracted service. The key risk in this case is: Debugging only the global table can prompt unintended configuration changes to an otherwise healthy customer VPN.

D.

Another emphasis concerns: Treating expected two-way neighbor states as faults can trigger unnecessary election changes and route churn. The current change is Repeat routing and operational tests explicitly in the correct customer instance and investigate any actual gap without changing global routing; the material limitation is Debugging only the global table can prompt unintended configuration changes to an otherwise healthy customer VPN.

Question 106

A fictional Junos service-provider engineer encounters this scenario: A troubleshooting script reports a remote OSPF branch unreachable even though traffic in a customer virtual router is healthy. Distinguishing evidence: The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance. 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: OSPF neighbor and interface details reveal different hello and dead intervals on the directly connected segment even though addresses and area are aligned.
  2. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Next-hop displays show multiple usable forwarding next hops, yet the test repeats one fixed five-tuple that consistently hashes to a single link.
  3. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance.
  4. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: OSPF database output includes relevant link-state information, whereas the active route table prefers a more specific or otherwise preferred competing route for the destination.

Answer and Explanation

Correct Answer: C

A.

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 the script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance. The focused check here is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance.

B.

Another investigation would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Next-hop displays show multiple usable forwarding next hops, yet the test repeats one fixed five-tuple that consistently hashes to a single link. It does not directly establish the reported condition: The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance.

C.

The current finding is the script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance. The specific pre-change check is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance. Use it to distinguish the problem from an unrelated symptom.

D.

Another check would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: OSPF database output includes relevant link-state information, whereas the active route table prefers a more specific or otherwise preferred competing route for the destination. The case observation to isolate is the script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance. The focused check here is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance.

Question 107

A fictional Junos service-provider engineer encounters this scenario: A troubleshooting script reports a remote OSPF branch unreachable even though traffic in a customer virtual router is healthy. Distinguishing evidence: The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance. Which controlled operational implementation sequence best protects the related provider service?

  1. Controlled engineering sequence: First verify the observed failure (Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link.); review and authorize the bounded correction (Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance.); then independently verify the intended outcome (Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero.) before production rollout.
  2. Controlled engineering sequence: First verify the observed failure (The interface is a broadcast multiaccess network with elected DR and BDR and the newcomer has low priority; neighbor output shows full adjacency to elected routers.); review and authorize the bounded correction (Inspect the broadcast network type, priorities and DR election state before changing any OSPF settings; document expected adjacency behavior.); then independently verify the intended outcome (The observed DR and BDR remain legitimate and all routers learn correct routes without forcing unnecessary full mesh adjacencies.) before production rollout.
  3. Controlled engineering sequence: First verify the observed failure (The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix.); review and authorize the bounded correction (Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order.); then independently verify the intended outcome (Packet samples and filter counters confirm only the approved customer flows use the alternate forwarding instance while management remains reachable.) before production rollout.
  4. Controlled engineering sequence: First verify the observed failure (The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance.); review and authorize the bounded correction (Repeat routing and operational tests explicitly in the correct customer instance and investigate any actual gap without changing global routing.); then independently verify the intended outcome (Route displays and sourced tests from the correct instance explain end-to-end reachability and isolate the false default-table alarm.) before production rollout.

Answer and Explanation

Correct Answer: D

A.

Another possible combination is: First verify the observed failure (Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link.); review and authorize the bounded correction (Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance.); then independently verify the intended outcome (Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero.) before production rollout. The current record instead supports Repeat routing and operational tests explicitly in the correct customer instance and investigate any actual gap without changing global routing, verified by Route displays and sourced tests from the correct instance explain end-to-end reachability and isolate the false default-table alarm.

B.

Another potential sequence is: First verify the observed failure (The interface is a broadcast multiaccess network with elected DR and BDR and the newcomer has low priority; neighbor output shows full adjacency to elected routers.); review and authorize the bounded correction (Inspect the broadcast network type, priorities and DR election state before changing any OSPF settings; document expected adjacency behavior.); then independently verify the intended outcome (The observed DR and BDR remain legitimate and all routers learn correct routes without forcing unnecessary full mesh adjacencies.) before production rollout. It has no direct link to the distinguishing evidence: The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance.

C.

Another action-and-check pairing is: First verify the observed failure (The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix.); review and authorize the bounded correction (Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order.); then independently verify the intended outcome (Packet samples and filter counters confirm only the approved customer flows use the alternate forwarding instance while management remains reachable.) before production rollout. The evidence here is the script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance. The required action and proof are Repeat routing and operational tests explicitly in the correct customer instance and investigate any actual gap without changing global routing and Route displays and sourced tests from the correct instance explain end-to-end reachability and isolate the false default-table alarm.

D.

The correction is Repeat routing and operational tests explicitly in the correct customer instance and investigate any actual gap without changing global routing. The matching proof is Route displays and sourced tests from the correct instance explain end-to-end reachability and isolate the false default-table alarm. Both address the finding that the script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance.

Question 108

A fictional Junos service-provider engineer encounters this scenario: A troubleshooting script reports a remote OSPF branch unreachable even though traffic in a customer virtual router is healthy. Distinguishing evidence: The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance. Which set of evidence, limited change and independent validation best justifies authorization?

  1. Approval package: observed evidence (The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance.), limited correction (Repeat routing and operational tests explicitly in the correct customer instance and investigate any actual gap without changing global routing.), independently measurable result (Route displays and sourced tests from the correct instance explain end-to-end reachability and isolate the false default-table alarm.).
  2. Approval package: 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.), limited correction (Check approved liveness requirements and align the interface hello and dead parameters on both adjacent devices before committing.), independently measurable result (The neighbor remains full through several monitored intervals, while routing reconverges predictably on a controlled link loss.).
  3. Approval package: observed evidence (The IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6.), limited correction (Inspect the advertised address-family-specific TLVs and corresponding IPv6 routing table and interface support before changing IS-IS policy.), independently measurable result (Both route-family displays match their advertised TLV data and IPv6 next-hop reachability is verified separately.).
  4. Approval package: observed evidence (The interface is a broadcast multiaccess network with elected DR and BDR and the newcomer has low priority; neighbor output shows full adjacency to elected routers.), limited correction (Inspect the broadcast network type, priorities and DR election state before changing any OSPF settings; document expected adjacency behavior.), independently measurable result (The observed DR and BDR remain legitimate and all routers learn correct routes without forcing unnecessary full mesh adjacencies.).

Answer and Explanation

Correct Answer: A

A.

The approval decision should consider the script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance. The specific proposal is: Observed evidence (The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance.), limited correction (Repeat routing and operational tests explicitly in the correct customer instance and investigate any actual gap without changing global routing.), independently measurable result (Route displays and sourced tests from the correct instance explain end-to-end reachability and isolate the false default-table alarm.). Its measurable outcome is: Route displays and sourced tests from the correct instance explain end-to-end reachability and isolate the false default-table alarm.

B.

Another approval action is: 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.), limited correction (Check approved liveness requirements and align the interface hello and dead parameters on both adjacent devices before committing.), independently measurable result (The neighbor remains full through several monitored intervals, while routing reconverges predictably on a controlled link loss.). The relevant evidence and acceptance are the script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance and Route displays and sourced tests from the correct instance explain end-to-end reachability and isolate the false default-table alarm, respectively.

C.

Another approval package concerns: Observed evidence (The IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6.), limited correction (Inspect the advertised address-family-specific TLVs and corresponding IPv6 routing table and interface support before changing IS-IS policy.), independently measurable result (Both route-family displays match their advertised TLV data and IPv6 next-hop reachability is verified separately.). The present scope must instead be justified by the script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance.

D.

An alternative release decision is: Observed evidence (The interface is a broadcast multiaccess network with elected DR and BDR and the newcomer has low priority; neighbor output shows full adjacency to elected routers.), limited correction (Inspect the broadcast network type, priorities and DR election state before changing any OSPF settings; document expected adjacency behavior.), independently measurable result (The observed DR and BDR remain legitimate and all routers learn correct routes without forcing unnecessary full mesh adjacencies.). It does not match the current change: Repeat routing and operational tests explicitly in the correct customer instance and investigate any actual gap without changing global routing.

Question 109

A fictional Junos service-provider engineer encounters this scenario: A troubleshooting script reports a remote OSPF branch unreachable even though traffic in a customer virtual router is healthy. Distinguishing evidence: The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance. 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 interface is a broadcast multiaccess network with elected DR and BDR and the newcomer has low priority; neighbor output shows full adjacency to elected routers.), restore the last approved safe network state and reassess dr and bdr expectations are confused on shared ethernet.
  2. If testing fails: pause changes, preserve the differentiating evidence (OSPF neighbor and interface details reveal different hello and dead intervals on the directly connected segment even though addresses and area are aligned.), restore the last approved safe network state and reassess hello and dead interval mismatch causes ospf neighbor instability.
  3. If testing fails: pause changes, preserve the differentiating evidence (The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance.), restore the last approved safe network state and reassess routing-instance ospf diagnostic probes point at the wrong table.
  4. If testing fails: pause changes, preserve the differentiating evidence (Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior.), restore the last approved safe network state and reassess ibgp full-mesh assumption breaks after adding a route reflector.

Answer and Explanation

Correct Answer: C

A.

Another recovery route would pause changes, preserve the differentiating evidence (The interface is a broadcast multiaccess network with elected DR and BDR and the newcomer has low priority; neighbor output shows full adjacency to elected routers.), restore the last approved safe network state and reassess dr and bdr expectations are confused on shared ethernet. It does not preserve the condition of this case: The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance. The bounded fallback is: Pause changes, preserve the differentiating evidence (The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance.), restore the last approved safe network state and reassess routing-instance ospf diagnostic probes point at the wrong table.

B.

Another option proposes: Pause changes, preserve the differentiating evidence (OSPF neighbor and interface details reveal different hello and dead intervals on the directly connected segment even though addresses and area are aligned.), restore the last approved safe network state and reassess hello and dead interval mismatch causes ospf neighbor instability. Its assumptions differ from the observed failure; the appropriate recovery is: Pause changes, preserve the differentiating evidence (The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance.), restore the last approved safe network state and reassess routing-instance ospf diagnostic probes point at the wrong table.

C.

A recovery option is to pause changes, preserve the differentiating evidence (The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance.), restore the last approved safe network state and reassess routing-instance ospf diagnostic probes point at the wrong table. The intended change was Repeat routing and operational tests explicitly in the correct customer instance and investigate any actual gap without changing global routing, and acceptance must still be judged against Route displays and sourced tests from the correct instance explain end-to-end reachability and isolate the false default-table alarm.

D.

Another recovery route would pause changes, preserve the differentiating evidence (Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior.), restore the last approved safe network state and reassess ibgp full-mesh assumption breaks after adding a route reflector. It does not preserve the condition of this case: The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance. The bounded fallback is: Pause changes, preserve the differentiating evidence (The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance.), restore the last approved safe network state and reassess routing-instance ospf diagnostic probes point at the wrong table.

Question 110

A fictional Junos service-provider engineer encounters this scenario: A troubleshooting script reports a remote OSPF branch unreachable even though traffic in a customer virtual router is healthy. Distinguishing evidence: The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance. Which bounded approval scope avoids unintended changes to other provider or customer services?

  1. Approve only the bounded change (Inspect the broadcast network type, priorities and DR election state before changing any OSPF settings; document expected adjacency behavior.) after independently checking (The observed DR and BDR remain legitimate and all routers learn correct routes without forcing unnecessary full mesh adjacencies.), without quietly widening the provider or customer network scope.
  2. Approve only the bounded change (Apply a precise export filter and route-policy tests for public prefixes, then confirm rejected customer-only routes stay internal.) after independently checking (Upstream advertised-route output contains only approved prefixes and the private customer destination remains available in its intended instance.), without quietly widening the provider or customer network scope.
  3. Approve only the bounded change (Compare link-state database reachability with route calculation, preference and active forwarding selection before modifying advertisement filters.) after independently checking (Database entries and active route selection are explainable, and probes follow the intended next hop without falsely requiring every LSA to be an active route.), without quietly widening the provider or customer network scope.
  4. Approve only the bounded change (Repeat routing and operational tests explicitly in the correct customer instance and investigate any actual gap without changing global routing.) after independently checking (Route displays and sourced tests from the correct instance explain end-to-end reachability and isolate the false default-table alarm.), without quietly widening the provider or customer network scope.

Answer and Explanation

Correct Answer: D

A.

An alternative approval would approve only the bounded change (Inspect the broadcast network type, priorities and DR election state before changing any OSPF settings; document expected adjacency behavior.) after independently checking (The observed DR and BDR remain legitimate and all routers learn correct routes without forcing unnecessary full mesh adjacencies.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are the script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance and Route displays and sourced tests from the correct instance explain end-to-end reachability and isolate the false default-table alarm, respectively.

B.

Another proposed approval would approve only the bounded change (Apply a precise export filter and route-policy tests for public prefixes, then confirm rejected customer-only routes stay internal.) after independently checking (Upstream advertised-route output contains only approved prefixes and the private customer destination remains available in its intended instance.), without quietly widening the provider or customer network scope. The present scope must instead be justified by the script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance.

C.

A separate release decision would approve only the bounded change (Compare link-state database reachability with route calculation, preference and active forwarding selection before modifying advertisement filters.) after independently checking (Database entries and active route selection are explainable, and probes follow the intended next hop without falsely requiring every LSA to be an active route.), without quietly widening the provider or customer network scope. It does not match the current change: Repeat routing and operational tests explicitly in the correct customer instance and investigate any actual gap without changing global routing.

D.

The bounded proposal is: Approve only the bounded change (Repeat routing and operational tests explicitly in the correct customer instance and investigate any actual gap without changing global routing.) after independently checking (Route displays and sourced tests from the correct instance explain end-to-end reachability and isolate the false default-table alarm.), without quietly widening the provider or customer network scope. The separate acceptance measure remains: Route displays and sourced tests from the correct instance explain end-to-end reachability and isolate the false default-table alarm.

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