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

Question 120

A fictional Junos service-provider engineer encounters this scenario: A backbone Junos node is configured only for level two while a newly installed neighbor is provisioned solely for level one on the same core link. Distinguishing evidence: Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency. Which bounded approval scope avoids unintended changes to other provider or customer services?

  1. Approve only the bounded change (Compare level-specific route metrics and approved traffic-engineering intent, then restore or adjust the scoped metric with a measured failover plan.) after independently checking (Representative destinations use the intended ring path and link utilization remains within the approved operational envelope.), without quietly widening the provider or customer network scope.
  2. Approve only the bounded change (Inspect the advertised address-family-specific TLVs and corresponding IPv6 routing table and interface support before changing IS-IS policy.) after independently checking (Both route-family displays match their advertised TLV data and IPv6 next-hop reachability is verified separately.), without quietly widening the provider or customer network scope.
  3. Approve only the bounded change (Verify domain-level design and configure the approved overlapping IS-IS level on the intended interface and routing instance.) after independently checking (The pair establishes an adjacency at the planned level and corresponding level-specific link-state information is exchanged.), without quietly widening the provider or customer network scope.
  4. Approve only the bounded change (Investigate transport reliability, control-plane load and negotiated timer behavior before adjusting route filters or hold time.) after independently checking (The session remains established over representative monitored intervals and loss testing confirms appropriate recovery behavior.), 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 (Compare level-specific route metrics and approved traffic-engineering intent, then restore or adjust the scoped metric with a measured failover plan.) after independently checking (Representative destinations use the intended ring path and link utilization remains within the approved operational envelope.), without quietly widening the provider or customer network scope. It does not match the current change: Verify domain-level design and configure the approved overlapping IS-IS level on the intended interface and routing instance.

B.

An alternative approval would approve only the bounded change (Inspect the advertised address-family-specific TLVs and corresponding IPv6 routing table and interface support before changing IS-IS policy.) after independently checking (Both route-family displays match their advertised TLV data and IPv6 next-hop reachability is verified separately.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency and the pair establishes an adjacency at the planned level and corresponding level-specific link-state information is exchanged, respectively.

C.

The bounded proposal is: Approve only the bounded change (Verify domain-level design and configure the approved overlapping IS-IS level on the intended interface and routing instance.) after independently checking (The pair establishes an adjacency at the planned level and corresponding level-specific link-state information is exchanged.), without quietly widening the provider or customer network scope. The separate acceptance measure remains: The pair establishes an adjacency at the planned level and corresponding level-specific link-state information is exchanged.

D.

A separate release decision would approve only the bounded change (Investigate transport reliability, control-plane load and negotiated timer behavior before adjusting route filters or hold time.) after independently checking (The session remains established over representative monitored intervals and loss testing confirms appropriate recovery behavior.), without quietly widening the provider or customer network scope. It does not match the current change: Verify domain-level design and configure the approved overlapping IS-IS level on the intended interface and routing instance.

Question 121

A fictional Junos service-provider engineer encounters this scenario: A metro core engineer raises the metric on a link for maintenance but operators observe a different set of customer prefixes choosing the higher-capacity alternate ring. Distinguishing evidence: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path. Which specific bounded Junos routing or switching correction best addresses this service-provider issue?

  1. Bounded remedy: Review the prefix-length and routing-policy terms, allow only the contracted prefix range and verify the actual import result.
  2. Bounded remedy: Verify domain-level design and configure the approved overlapping IS-IS level on the intended interface and routing instance.
  3. Bounded remedy: Inspect the advertised address-family-specific TLVs and corresponding IPv6 routing table and interface support before changing IS-IS policy.
  4. Bounded remedy: Compare level-specific route metrics and approved traffic-engineering intent, then restore or adjust the scoped metric with a measured failover plan.

Answer and Explanation

Correct Answer: D

A.

Another proposed action is: Review the prefix-length and routing-policy terms, allow only the contracted prefix range and verify the actual import result. That does not directly address the observed condition: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path. The more targeted correction is: Compare level-specific route metrics and approved traffic-engineering intent, then restore or adjust the scoped metric with a measured failover plan.

B.

Another proposed action is: Verify domain-level design and configure the approved overlapping IS-IS level on the intended interface and routing instance. It targets a different dependency; the evidence here is IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.

C.

Another option proposes: Inspect the advertised address-family-specific TLVs and corresponding IPv6 routing table and interface support before changing IS-IS policy. The specific correction is: Compare level-specific route metrics and approved traffic-engineering intent, then restore or adjust the scoped metric with a measured failover plan. The deciding evidence is: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.

D.

The observed condition is: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path. This calls for the scoped change: Compare level-specific route metrics and approved traffic-engineering intent, then restore or adjust the scoped metric with a measured failover plan. The acceptance measure is: Representative destinations use the intended ring path and link utilization remains within the approved operational envelope.

Question 122

A fictional Junos service-provider engineer encounters this scenario: A metro core engineer raises the metric on a link for maintenance but operators observe a different set of customer prefixes choosing the higher-capacity alternate ring. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?

  1. Differentiating observation: Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency.
  2. 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.
  3. Differentiating observation: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths.
  4. Differentiating observation: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.

Answer and Explanation

Correct Answer: D

A.

This other option describes: Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency. The problem to explain is different: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.

B.

Another proposed finding is: OSPF neighbor and interface details reveal different hello and dead intervals on the directly connected segment even though addresses and area are aligned. It is not the recorded discriminator, which is IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.

C.

Another piece of evidence concerns LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths. The current incident instead shows: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path. This distinction supports the action: Compare level-specific route metrics and approved traffic-engineering intent, then restore or adjust the scoped metric with a measured failover plan.

D.

The deciding evidence is: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path. This distinguishes the problem because IS-IS path computation follows topology information and relevant link metrics. The response it supports is: Compare level-specific route metrics and approved traffic-engineering intent, then restore or adjust the scoped metric with a measured failover plan.

Question 123

A fictional Junos service-provider engineer encounters this scenario: A metro core engineer raises the metric on a link for maintenance but operators observe a different set of customer prefixes choosing the higher-capacity alternate ring. Distinguishing evidence: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path. Which Junos networking principle best explains the relevant engineering decision?

  1. Applicable protocol principle: IS-IS path computation follows topology information and relevant link metrics. Evidence for this case: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.
  2. Applicable protocol principle: OSPF link-state advertisement data and active routing-table installation are different diagnostic layers. Evidence for this case: 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. 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.
  4. Applicable protocol principle: IS-IS uses TLVs to encode protocol information, and route-family visibility must be checked in the correct RIB. Evidence for this case: The IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6.

Answer and Explanation

Correct Answer: A

A.

The observed evidence is: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path. The governing principle is: IS-IS path computation follows topology information and relevant link metrics. Consequently, the targeted action is: Compare level-specific route metrics and approved traffic-engineering intent, then restore or adjust the scoped metric with a measured failover plan.

B.

That principle concerns another fact pattern: OSPF link-state advertisement data and active routing-table installation are different diagnostic layers. Evidence for this case: 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. Here the key fact is: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.

C.

A different principle is: 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, however, is IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path. The relevant rule is: IS-IS path computation follows topology information and relevant link metrics.

D.

This alternative invokes: IS-IS uses TLVs to encode protocol information, and route-family visibility must be checked in the correct RIB. Evidence for this case: The IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6. The governing distinction for the recorded case is IS-IS path computation follows topology information and relevant link metrics.

Question 124

A fictional Junos service-provider engineer encounters this scenario: A metro core engineer raises the metric on a link for maintenance but operators observe a different set of customer prefixes choosing the higher-capacity alternate ring. Intended bounded correction: Compare level-specific route metrics and approved traffic-engineering intent, then restore or adjust the scoped metric with a measured failover plan. Which independently verifiable test best demonstrates the intended correction worked?

  1. Independent verification: Customer inner VLAN traffic crosses the agreed provider service path with the expected outer encapsulation and isolation from unrelated customers.
  2. Independent verification: Representative destinations use the intended ring path and link utilization remains within the approved operational envelope.
  3. Independent verification: Both route-family displays match their advertised TLV data and IPv6 next-hop reachability is verified separately.
  4. Independent verification: The pair establishes an adjacency at the planned level and corresponding level-specific link-state information is exchanged.

Answer and Explanation

Correct Answer: B

A.

A different option checks: Customer inner VLAN traffic crosses the agreed provider service path with the expected outer encapsulation and isolation from unrelated customers. The case-specific acceptance condition is instead Representative destinations use the intended ring path and link utilization remains within the approved operational envelope.

B.

The independent verification condition is: Representative destinations use the intended ring path and link utilization remains within the approved operational envelope. That result checks whether the original evidence—IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path—has been addressed.

C.

That result would assess another condition: Both route-family displays match their advertised TLV data and IPv6 next-hop reachability is verified separately. The correct criterion is directly linked to the finding: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.

D.

Another proposed result is: The pair establishes an adjacency at the planned level and corresponding level-specific link-state information is exchanged. It would not independently establish the required outcome: Representative destinations use the intended ring path and link utilization remains within the approved operational envelope.

Question 125

A fictional Junos service-provider engineer encounters this scenario: A metro core engineer raises the metric on a link for maintenance but operators observe a different set of customer prefixes choosing the higher-capacity alternate ring. Distinguishing evidence: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path. Which material service-availability, routing, switching or security risk most directly needs control?

  1. Meaningful operational caution: Altering link metrics to force a DIS outcome can reroute unrelated customer traffic without changing election priority.
  2. Meaningful operational caution: Blindly restarting IS-IS on every router can add topology disruption without proving database cause.
  3. Meaningful operational caution: An unrelated BGP policy adjustment cannot repair a Layer 2 forwarding-table error and may interrupt transit networks.
  4. Meaningful operational caution: A topology metric change affects many prefixes and can cause transient congestion beyond the maintenance link.

Answer and Explanation

Correct Answer: D

A.

This limitation concerns another setting: Altering link metrics to force a DIS outcome can reroute unrelated customer traffic without changing election priority. The observed facts here make a different caution decisive: A topology metric change affects many prefixes and can cause transient congestion beyond the maintenance link.

B.

Another caution is: Blindly restarting IS-IS on every router can add topology disruption without proving database cause. The key risk in this case is: A topology metric change affects many prefixes and can cause transient congestion beyond the maintenance link.

C.

Another emphasis concerns: An unrelated BGP policy adjustment cannot repair a Layer 2 forwarding-table error and may interrupt transit networks. The current change is Compare level-specific route metrics and approved traffic-engineering intent, then restore or adjust the scoped metric with a measured failover plan; the material limitation is a topology metric change affects many prefixes and can cause transient congestion beyond the maintenance link.

D.

A necessary safeguard is: A topology metric change affects many prefixes and can cause transient congestion beyond the maintenance link. The proposed correction remains: Compare level-specific route metrics and approved traffic-engineering intent, then restore or adjust the scoped metric with a measured failover plan.

Question 126

A fictional Junos service-provider engineer encounters this scenario: A metro core engineer raises the metric on a link for maintenance but operators observe a different set of customer prefixes choosing the higher-capacity alternate ring. Distinguishing evidence: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path. 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: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths.
  2. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: 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.
  3. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.
  4. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist.

Answer and Explanation

Correct Answer: C

A.

Another investigation would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths. It does not directly establish the reported condition: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.

B.

That check concerns a different signal: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: 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. The case-relevant check is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.

C.

The pre-change check should compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path. That check directly concerns IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.

D.

Another investigation would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist. It does not directly establish the reported condition: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.

Question 127

A fictional Junos service-provider engineer encounters this scenario: A metro core engineer raises the metric on a link for maintenance but operators observe a different set of customer prefixes choosing the higher-capacity alternate ring. Distinguishing evidence: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path. Which controlled operational implementation sequence best protects the related provider service?

  1. Controlled engineering sequence: First verify the observed failure (Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency.); review and authorize the bounded correction (Verify domain-level design and configure the approved overlapping IS-IS level on the intended interface and routing instance.); then independently verify the intended outcome (The pair establishes an adjacency at the planned level and corresponding level-specific link-state information is exchanged.) before production rollout.
  2. Controlled engineering sequence: First verify the observed failure (Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts.); review and authorize the bounded correction (Separate the tenant virtual switches and bridge-domain scopes while preserving the contracted tag translation on each handoff.); then independently verify the intended outcome (Broadcast and unknown-unicast tests remain isolated to each customer and independent service port traffic follows expected boundaries.) before production rollout.
  3. Controlled engineering sequence: First verify the observed failure (IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.); review and authorize the bounded correction (Compare level-specific route metrics and approved traffic-engineering intent, then restore or adjust the scoped metric with a measured failover plan.); then independently verify the intended outcome (Representative destinations use the intended ring path and link utilization remains within the approved operational envelope.) before production rollout.
  4. Controlled engineering sequence: First verify the observed failure (Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist.); review and authorize the bounded correction (Inspect IS-IS LSP flooding, level scope and database synchronization before deciding on targeted refresh or isolation steps.); then independently verify the intended outcome (Peer databases converge on the expected LSP set and the authorized loopback routes become usable without forcing widespread protocol resets.) before production rollout.

Answer and Explanation

Correct Answer: C

A.

Another possible combination is: First verify the observed failure (Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency.); review and authorize the bounded correction (Verify domain-level design and configure the approved overlapping IS-IS level on the intended interface and routing instance.); then independently verify the intended outcome (The pair establishes an adjacency at the planned level and corresponding level-specific link-state information is exchanged.) before production rollout. The current record instead supports Compare level-specific route metrics and approved traffic-engineering intent, then restore or adjust the scoped metric with a measured failover plan, verified by Representative destinations use the intended ring path and link utilization remains within the approved operational envelope.

B.

Another potential sequence is: First verify the observed failure (Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts.); review and authorize the bounded correction (Separate the tenant virtual switches and bridge-domain scopes while preserving the contracted tag translation on each handoff.); then independently verify the intended outcome (Broadcast and unknown-unicast tests remain isolated to each customer and independent service port traffic follows expected boundaries.) before production rollout. It has no direct link to the distinguishing evidence: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.

C.

The case evidence indicates: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path. Apply the scoped action: Compare level-specific route metrics and approved traffic-engineering intent, then restore or adjust the scoped metric with a measured failover plan. Confirm its effect independently: Representative destinations use the intended ring path and link utilization remains within the approved operational envelope.

D.

An alternative plan is: First verify the observed failure (Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist.); review and authorize the bounded correction (Inspect IS-IS LSP flooding, level scope and database synchronization before deciding on targeted refresh or isolation steps.); then independently verify the intended outcome (Peer databases converge on the expected LSP set and the authorized loopback routes become usable without forcing widespread protocol resets.) before production rollout. It does not test the case-specific condition: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.

Question 128

A fictional Junos service-provider engineer encounters this scenario: A metro core engineer raises the metric on a link for maintenance but operators observe a different set of customer prefixes choosing the higher-capacity alternate ring. Distinguishing evidence: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path. Which set of evidence, limited change and independent validation best justifies authorization?

  1. Approval package: observed evidence (LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths.), limited correction (Validate LAN circuit priority and DIS role independently from route metrics; change only the control-plane election setting if the design requires it.), independently measurable result (The designated intermediate system role matches documented circuit priority policy and shortest-path computations remain consistent.).
  2. Approval package: observed evidence (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.), limited correction (Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance.), independently measurable result (Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero.).
  3. Approval package: observed evidence (Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency.), limited correction (Verify domain-level design and configure the approved overlapping IS-IS level on the intended interface and routing instance.), independently measurable result (The pair establishes an adjacency at the planned level and corresponding level-specific link-state information is exchanged.).
  4. Approval package: observed evidence (IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.), limited correction (Compare level-specific route metrics and approved traffic-engineering intent, then restore or adjust the scoped metric with a measured failover plan.), independently measurable result (Representative destinations use the intended ring path and link utilization remains within the approved operational envelope.).

Answer and Explanation

Correct Answer: D

A.

Another approval action is: Observed evidence (LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths.), limited correction (Validate LAN circuit priority and DIS role independently from route metrics; change only the control-plane election setting if the design requires it.), independently measurable result (The designated intermediate system role matches documented circuit priority policy and shortest-path computations remain consistent.). The relevant evidence and acceptance are IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path and Representative destinations use the intended ring path and link utilization remains within the approved operational envelope, respectively.

B.

Another approval package concerns: Observed evidence (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.), limited correction (Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance.), independently measurable result (Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero.). The present scope must instead be justified by IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.

C.

An alternative release decision is: Observed evidence (Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency.), limited correction (Verify domain-level design and configure the approved overlapping IS-IS level on the intended interface and routing instance.), independently measurable result (The pair establishes an adjacency at the planned level and corresponding level-specific link-state information is exchanged.). It does not match the current change: Compare level-specific route metrics and approved traffic-engineering intent, then restore or adjust the scoped metric with a measured failover plan.

D.

The bounded proposal is: Observed evidence (IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.), limited correction (Compare level-specific route metrics and approved traffic-engineering intent, then restore or adjust the scoped metric with a measured failover plan.), independently measurable result (Representative destinations use the intended ring path and link utilization remains within the approved operational envelope.). The separate acceptance measure remains: Representative destinations use the intended ring path and link utilization remains within the approved operational envelope.

Question 129

A fictional Junos service-provider engineer encounters this scenario: A metro core engineer raises the metric on a link for maintenance but operators observe a different set of customer prefixes choosing the higher-capacity alternate ring. Distinguishing evidence: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path. 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 (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.), restore the last approved safe network state and reassess area mismatch prevents a core ospf neighbor from forming.
  2. If testing fails: pause changes, preserve the differentiating evidence (Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency.), restore the last approved safe network state and reassess is-is level configuration prevents adjacency.
  3. If testing fails: pause changes, preserve the differentiating evidence (IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.), restore the last approved safe network state and reassess is-is wide metric change moves traffic unexpectedly.
  4. If testing fails: pause changes, preserve the differentiating evidence (LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths.), restore the last approved safe network state and reassess dis election on a lan is mistaken for shortest-path priority.

Answer and Explanation

Correct Answer: C

A.

Another option proposes: Pause changes, preserve the differentiating evidence (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.), restore the last approved safe network state and reassess area mismatch prevents a core ospf neighbor from forming. Its assumptions differ from the observed failure; the appropriate recovery is: Pause changes, preserve the differentiating evidence (IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.), restore the last approved safe network state and reassess is-is wide metric change moves traffic unexpectedly.

B.

Another fallback concerns pausing changes, preserve the differentiating evidence (Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency.), restore the last approved safe network state and reassess is-is level configuration prevents adjacency. The current change concerns IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.

C.

A contingency plan would pause changes, preserve the differentiating evidence (IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.), restore the last approved safe network state and reassess is-is wide metric change moves traffic unexpectedly. This preserves control of the change linked to IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.

D.

Another option proposes: Pause changes, preserve the differentiating evidence (LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths.), restore the last approved safe network state and reassess dis election on a lan is mistaken for shortest-path priority. Its assumptions differ from the observed failure; the appropriate recovery is: Pause changes, preserve the differentiating evidence (IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.), restore the last approved safe network state and reassess is-is wide metric change moves traffic unexpectedly.

Question 130

A fictional Junos service-provider engineer encounters this scenario: A metro core engineer raises the metric on a link for maintenance but operators observe a different set of customer prefixes choosing the higher-capacity alternate ring. Distinguishing evidence: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path. Which bounded approval scope avoids unintended changes to other provider or customer services?

  1. Approve only the bounded change (Compare level-specific route metrics and approved traffic-engineering intent, then restore or adjust the scoped metric with a measured failover plan.) after independently checking (Representative destinations use the intended ring path and link utilization remains within the approved operational envelope.), without quietly widening the provider or customer network scope.
  2. Approve only the bounded change (Review the prefix-length and routing-policy terms, allow only the contracted prefix range and verify the actual import result.) after independently checking (The authorized customer route becomes usable and adjacent unapproved prefixes remain rejected at the policy boundary.), without quietly widening the provider or customer network scope.
  3. Approve only the bounded change (Inspect IS-IS LSP flooding, level scope and database synchronization before deciding on targeted refresh or isolation steps.) after independently checking (Peer databases converge on the expected LSP set and the authorized loopback routes become usable without forcing widespread protocol resets.), without quietly widening the provider or customer network scope.
  4. Approve only the bounded change (Verify domain-level design and configure the approved overlapping IS-IS level on the intended interface and routing instance.) after independently checking (The pair establishes an adjacency at the planned level and corresponding level-specific link-state information is exchanged.), without quietly widening the provider or customer network scope.

Answer and Explanation

Correct Answer: A

A.

The change-control boundary is: Approve only the bounded change (Compare level-specific route metrics and approved traffic-engineering intent, then restore or adjust the scoped metric with a measured failover plan.) after independently checking (Representative destinations use the intended ring path and link utilization remains within the approved operational envelope.), without quietly widening the provider or customer network scope. The evidence for this scope is IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.

B.

A separate release decision would approve only the bounded change (Review the prefix-length and routing-policy terms, allow only the contracted prefix range and verify the actual import result.) after independently checking (The authorized customer route becomes usable and adjacent unapproved prefixes remain rejected at the policy boundary.), without quietly widening the provider or customer network scope. It does not match the current change: Compare level-specific route metrics and approved traffic-engineering intent, then restore or adjust the scoped metric with a measured failover plan.

C.

An alternative approval would approve only the bounded change (Inspect IS-IS LSP flooding, level scope and database synchronization before deciding on targeted refresh or isolation steps.) after independently checking (Peer databases converge on the expected LSP set and the authorized loopback routes become usable without forcing widespread protocol resets.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path and Representative destinations use the intended ring path and link utilization remains within the approved operational envelope, respectively.

D.

Another proposed approval would approve only the bounded change (Verify domain-level design and configure the approved overlapping IS-IS level on the intended interface and routing instance.) after independently checking (The pair establishes an adjacency at the planned level and corresponding level-specific link-state information is exchanged.), without quietly widening the provider or customer network scope. The present scope must instead be justified by IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.

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