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

Question 150

A fictional Junos service-provider engineer encounters this scenario: An engineer expects an IPv6 reachability advertisement to appear in IPv4-only IS-IS route output after enabling multi-protocol operation. Distinguishing evidence: The IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6. 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 (Validate LAN circuit priority and DIS role independently from route metrics; change only the control-plane election setting if the design requires it.) after independently checking (The designated intermediate system role matches documented circuit priority policy and shortest-path computations remain consistent.), without quietly widening the provider or customer network scope.
  3. Approve only the bounded change (Verify peering transport addresses, configured peer ASN, reachability and authentication, then correct only the approved BGP neighbor endpoint.) after independently checking (The expected external session reaches Established and exchanges only agreed IPv4 routes with stable uptime.), without quietly widening the provider or customer network scope.
  4. 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.

Answer and Explanation

Correct Answer: D

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: Inspect the advertised address-family-specific TLVs and corresponding IPv6 routing table and interface support before changing IS-IS policy.

B.

An alternative approval would approve only the bounded change (Validate LAN circuit priority and DIS role independently from route metrics; change only the control-plane election setting if the design requires it.) after independently checking (The designated intermediate system role matches documented circuit priority policy and shortest-path computations remain consistent.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are the IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6 and Both route-family displays match their advertised TLV data and IPv6 next-hop reachability is verified separately, respectively.

C.

Another proposed approval would approve only the bounded change (Verify peering transport addresses, configured peer ASN, reachability and authentication, then correct only the approved BGP neighbor endpoint.) after independently checking (The expected external session reaches Established and exchanges only agreed IPv4 routes with stable uptime.), without quietly widening the provider or customer network scope. The present scope must instead be justified by the IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6.

D.

The approval decision should consider the IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6. The specific proposal is: 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. Its measurable outcome is: Both route-family displays match their advertised TLV data and IPv6 next-hop reachability is verified separately.

Question 151

A fictional Junos service-provider engineer encounters this scenario: A shared service-provider Ethernet segment elects an IS-IS DIS different from the router with the lowest configured path metric. Distinguishing evidence: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths. Which specific bounded Junos routing or switching correction best addresses this service-provider issue?

  1. Bounded remedy: Inspect IS-IS LSP flooding, level scope and database synchronization before deciding on targeted refresh or isolation steps.
  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: Validate LAN circuit priority and DIS role independently from route metrics; change only the control-plane election setting if the design requires it.
  4. Bounded remedy: Compare link-state database reachability with route calculation, preference and active forwarding selection before modifying advertisement filters.

Answer and Explanation

Correct Answer: C

A.

Another proposed action is: Inspect IS-IS LSP flooding, level scope and database synchronization before deciding on targeted refresh or isolation steps. That does not directly address the observed condition: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths. The more targeted correction is: Validate LAN circuit priority and DIS role independently from route metrics; change only the control-plane election setting if the design requires it.

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 LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths.

C.

The issue turns on LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths. The relevant rule is that IS-IS LAN DIS election and shortest-path metrics are distinct control-plane mechanisms. The targeted correction is: Validate LAN circuit priority and DIS role independently from route metrics; change only the control-plane election setting if the design requires it.

D.

That alternative concerns: Compare link-state database reachability with route calculation, preference and active forwarding selection before modifying advertisement filters. The relevant evidence is LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths. The corresponding fix is: Validate LAN circuit priority and DIS role independently from route metrics; change only the control-plane election setting if the design requires it.

Question 152

A fictional Junos service-provider engineer encounters this scenario: A shared service-provider Ethernet segment elects an IS-IS DIS different from the router with the lowest configured path metric. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?

  1. Differentiating observation: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths.
  2. 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.
  3. Differentiating observation: Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist.
  4. Differentiating observation: Peer history contains hold timer expirations and packet captures show sporadic missing keepalives during a saturated control-plane event.

Answer and Explanation

Correct Answer: A

A.

Consider this evidence: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths. The applicable explanation is: IS-IS LAN DIS election and shortest-path metrics are distinct control-plane mechanisms. The matching response is: Validate LAN circuit priority and DIS role independently from route metrics; change only the control-plane election setting if the design requires it.

B.

Another alternative would address IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path as decisive. The actual evidence in this case is LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths.

C.

This other option describes: Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist. The problem to explain is different: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths.

D.

Another proposed finding is: Peer history contains hold timer expirations and packet captures show sporadic missing keepalives during a saturated control-plane event. It is not the recorded discriminator, which is LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths.

Question 153

A fictional Junos service-provider engineer encounters this scenario: A shared service-provider Ethernet segment elects an IS-IS DIS different from the router with the lowest configured path metric. Distinguishing evidence: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths. Which Junos networking principle best explains the relevant engineering decision?

  1. 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.
  2. Applicable protocol principle: IS-IS PDU exchange and link-state database synchronization must be checked independently from adjacency status. Evidence for this case: Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist.
  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 adjacencies depend on compatible level operation as well as link connectivity. Evidence for this case: Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency.

Answer and Explanation

Correct Answer: C

A.

A different principle is: 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. The present evidence, however, is LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths. The relevant rule is: IS-IS LAN DIS election and shortest-path metrics are distinct control-plane mechanisms.

B.

This alternative invokes: IS-IS PDU exchange and link-state database synchronization must be checked independently from adjacency status. Evidence for this case: Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist. The governing distinction for the recorded case is IS-IS LAN DIS election and shortest-path metrics are distinct control-plane mechanisms.

C.

The observed evidence is: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths. The governing principle is: IS-IS LAN DIS election and shortest-path metrics are distinct control-plane mechanisms. Consequently, the targeted action is: Validate LAN circuit priority and DIS role independently from route metrics; change only the control-plane election setting if the design requires it.

D.

That principle concerns another fact pattern: IS-IS adjacencies depend on compatible level operation as well as link connectivity. Evidence for this case: Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency. Here the key fact is: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths.

Question 154

A fictional Junos service-provider engineer encounters this scenario: A shared service-provider Ethernet segment elects an IS-IS DIS different from the router with the lowest configured path metric. Intended bounded correction: Validate LAN circuit priority and DIS role independently from route metrics; change only the control-plane election setting if the design requires it. Which independently verifiable test best demonstrates the intended correction worked?

  1. Independent verification: Representative destinations use the intended ring path and link utilization remains within the approved operational envelope.
  2. Independent verification: The neighbor remains full through several monitored intervals, while routing reconverges predictably on a controlled link loss.
  3. Independent verification: The designated intermediate system role matches documented circuit priority policy and shortest-path computations remain consistent.
  4. Independent verification: Both route-family displays match their advertised TLV data and IPv6 next-hop reachability is verified separately.

Answer and Explanation

Correct Answer: C

A.

That result would assess another condition: Representative destinations use the intended ring path and link utilization remains within the approved operational envelope. The correct criterion is directly linked to the finding: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths.

B.

Another proposed result is: The neighbor remains full through several monitored intervals, while routing reconverges predictably on a controlled link loss. It would not independently establish the required outcome: The designated intermediate system role matches documented circuit priority policy and shortest-path computations remain consistent.

C.

The expected outcome is the designated intermediate system role matches documented circuit priority policy and shortest-path computations remain consistent. It links the scoped action to the documented condition: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths.

D.

Passing that test would not establish resolution of the stated issue. The relevant proof is: The designated intermediate system role matches documented circuit priority policy and shortest-path computations remain consistent.

Question 155

A fictional Junos service-provider engineer encounters this scenario: A shared service-provider Ethernet segment elects an IS-IS DIS different from the router with the lowest configured path metric. Distinguishing evidence: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths. 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: An unrelated BGP policy adjustment cannot repair a Layer 2 forwarding-table error and may interrupt transit networks.
  3. Meaningful operational caution: Assuming every IS-IS LSP attribute populates every family can misdirect troubleshooting and policy changes.
  4. Meaningful operational caution: Altering link metrics to force a DIS outcome can reroute unrelated customer traffic without changing election priority.

Answer and Explanation

Correct Answer: D

A.

This limitation concerns another setting: Blindly restarting IS-IS on every router can add topology disruption without proving database cause. The observed facts here make a different caution decisive: Altering link metrics to force a DIS outcome can reroute unrelated customer traffic without changing election priority.

B.

Another caution is: An unrelated BGP policy adjustment cannot repair a Layer 2 forwarding-table error and may interrupt transit networks. The key risk in this case is: Altering link metrics to force a DIS outcome can reroute unrelated customer traffic without changing election priority.

C.

Another emphasis concerns: Assuming every IS-IS LSP attribute populates every family can misdirect troubleshooting and policy changes. The current change is Validate LAN circuit priority and DIS role independently from route metrics; change only the control-plane election setting if the design requires it; the material limitation is Altering link metrics to force a DIS outcome can reroute unrelated customer traffic without changing election priority.

D.

Altering link metrics to force a DIS outcome can reroute unrelated customer traffic without changing election priority. That boundary protects the documented change, Validate LAN circuit priority and DIS role independently from route metrics; change only the control-plane election setting if the design requires it, from introducing an unrelated problem.

Question 156

A fictional Junos service-provider engineer encounters this scenario: A shared service-provider Ethernet segment elects an IS-IS DIS different from the router with the lowest configured path metric. Distinguishing evidence: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths. 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: Advertised route inspection lists a private customer prefix that is not present in the approved external export inventory.
  2. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6.
  3. 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.
  4. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency.

Answer and Explanation

Correct Answer: C

A.

Another investigation would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Advertised route inspection lists a private customer prefix that is not present in the approved external export inventory. It does not directly establish the reported condition: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths.

B.

That check concerns a different signal: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6. The case-relevant check is: 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.

C.

The pre-change check should 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. That check directly concerns LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths.

D.

Another investigation would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency. It does not directly establish the reported condition: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths.

Question 157

A fictional Junos service-provider engineer encounters this scenario: A shared service-provider Ethernet segment elects an IS-IS DIS different from the router with the lowest configured path metric. Distinguishing evidence: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths. Which controlled operational implementation sequence best protects the related provider service?

  1. Controlled engineering sequence: First verify the observed failure (LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths.); review and authorize the bounded correction (Validate LAN circuit priority and DIS role independently from route metrics; change only the control-plane election setting if the design requires it.); then independently verify the intended outcome (The designated intermediate system role matches documented circuit priority policy and shortest-path computations remain consistent.) before production rollout.
  2. Controlled engineering sequence: First verify the observed failure (The IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6.); review and authorize the bounded correction (Inspect the advertised address-family-specific TLVs and corresponding IPv6 routing table and interface support before changing IS-IS policy.); then independently verify the intended outcome (Both route-family displays match their advertised TLV data and IPv6 next-hop reachability is verified separately.) before production rollout.
  3. 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.
  4. Controlled engineering sequence: First verify the observed failure (MAC learning within the broadcast domain is healthy while the IRB logical interface or VLAN-to-IRB binding is missing or mapped to another tenant VLAN.); review and authorize the bounded correction (Check the VLAN's Layer 3 interface relationship and correct the scoped IRB binding, address family and eligibility.); then independently verify the intended outcome (Hosts in the specified VLAN reach their authorized gateway while isolation and route selection for other VLANs remain intact.) before production rollout.

Answer and Explanation

Correct Answer: A

A.

The case evidence indicates: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths. Apply the scoped action: Validate LAN circuit priority and DIS role independently from route metrics; change only the control-plane election setting if the design requires it. Confirm its effect independently: The designated intermediate system role matches documented circuit priority policy and shortest-path computations remain consistent.

B.

An alternative plan is: First verify the observed failure (The IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6.); review and authorize the bounded correction (Inspect the advertised address-family-specific TLVs and corresponding IPv6 routing table and interface support before changing IS-IS policy.); then independently verify the intended outcome (Both route-family displays match their advertised TLV data and IPv6 next-hop reachability is verified separately.) before production rollout. It does not test the case-specific condition: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths.

C.

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 Validate LAN circuit priority and DIS role independently from route metrics; change only the control-plane election setting if the design requires it, verified by the designated intermediate system role matches documented circuit priority policy and shortest-path computations remain consistent.

D.

Another potential sequence is: First verify the observed failure (MAC learning within the broadcast domain is healthy while the IRB logical interface or VLAN-to-IRB binding is missing or mapped to another tenant VLAN.); review and authorize the bounded correction (Check the VLAN's Layer 3 interface relationship and correct the scoped IRB binding, address family and eligibility.); then independently verify the intended outcome (Hosts in the specified VLAN reach their authorized gateway while isolation and route selection for other VLANs remain intact.) before production rollout. It has no direct link to the distinguishing evidence: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths.

Question 158

A fictional Junos service-provider engineer encounters this scenario: A shared service-provider Ethernet segment elects an IS-IS DIS different from the router with the lowest configured path metric. Distinguishing evidence: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths. 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 (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.).
  3. Approval package: observed evidence (MAC learning within the broadcast domain is healthy while the IRB logical interface or VLAN-to-IRB binding is missing or mapped to another tenant VLAN.), limited correction (Check the VLAN's Layer 3 interface relationship and correct the scoped IRB binding, address family and eligibility.), independently measurable result (Hosts in the specified VLAN reach their authorized gateway while isolation and route selection for other VLANs remain intact.).
  4. Approval package: observed evidence (Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist.), limited correction (Inspect IS-IS LSP flooding, level scope and database synchronization before deciding on targeted refresh or isolation steps.), independently measurable result (Peer databases converge on the expected LSP set and the authorized loopback routes become usable without forcing widespread protocol resets.).

Answer and Explanation

Correct Answer: A

A.

The bounded proposal 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 separate acceptance measure remains: The designated intermediate system role matches documented circuit priority policy and shortest-path computations remain consistent.

B.

Another approval package concerns: 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 present scope must instead be justified by LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths.

C.

An alternative release decision is: Observed evidence (MAC learning within the broadcast domain is healthy while the IRB logical interface or VLAN-to-IRB binding is missing or mapped to another tenant VLAN.), limited correction (Check the VLAN's Layer 3 interface relationship and correct the scoped IRB binding, address family and eligibility.), independently measurable result (Hosts in the specified VLAN reach their authorized gateway while isolation and route selection for other VLANs remain intact.). It does not match the current change: Validate LAN circuit priority and DIS role independently from route metrics; change only the control-plane election setting if the design requires it.

D.

Another approval action is: Observed evidence (Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist.), limited correction (Inspect IS-IS LSP flooding, level scope and database synchronization before deciding on targeted refresh or isolation steps.), independently measurable result (Peer databases converge on the expected LSP set and the authorized loopback routes become usable without forcing widespread protocol resets.). The relevant evidence and acceptance are LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths and the designated intermediate system role matches documented circuit priority policy and shortest-path computations remain consistent, respectively.

Question 159

A fictional Junos service-provider engineer encounters this scenario: A shared service-provider Ethernet segment elects an IS-IS DIS different from the router with the lowest configured path metric. Distinguishing evidence: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths. 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 (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.
  2. If testing fails: pause changes, preserve the differentiating evidence (Advertised route inspection lists a private customer prefix that is not present in the approved external export inventory.), restore the last approved safe network state and reassess bgp export policy reveals a customer-only route to transit.
  3. 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.
  4. If testing fails: pause changes, preserve the differentiating evidence (Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist.), restore the last approved safe network state and reassess is-is circuit has a neighbor but incomplete link-state information.

Answer and Explanation

Correct Answer: A

A.

A recovery option is to 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. The intended change was Validate LAN circuit priority and DIS role independently from route metrics; change only the control-plane election setting if the design requires it, and acceptance must still be judged against the designated intermediate system role matches documented circuit priority policy and shortest-path computations remain consistent.

B.

Another fallback concerns pausing changes, preserve the differentiating evidence (Advertised route inspection lists a private customer prefix that is not present in the approved external export inventory.), restore the last approved safe network state and reassess bgp export policy reveals a customer-only route to transit. The current change concerns LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths.

C.

Another recovery route would 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. It does not preserve the condition of this case: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths. The bounded fallback is: 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.

D.

Another option proposes: Pause changes, preserve the differentiating evidence (Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist.), restore the last approved safe network state and reassess is-is circuit has a neighbor but incomplete link-state information. Its assumptions differ from the observed failure; the appropriate recovery is: 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.

Question 160

A fictional Junos service-provider engineer encounters this scenario: A shared service-provider Ethernet segment elects an IS-IS DIS different from the router with the lowest configured path metric. Distinguishing evidence: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths. Which bounded approval scope avoids unintended changes to other provider or customer services?

  1. 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.
  2. Approve only the bounded change (Validate LAN circuit priority and DIS role independently from route metrics; change only the control-plane election setting if the design requires it.) after independently checking (The designated intermediate system role matches documented circuit priority policy and shortest-path computations remain consistent.), 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 (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.

Answer and Explanation

Correct Answer: B

A.

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 LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths.

B.

The bounded proposal is: Approve only the bounded change (Validate LAN circuit priority and DIS role independently from route metrics; change only the control-plane election setting if the design requires it.) after independently checking (The designated intermediate system role matches documented circuit priority policy and shortest-path computations remain consistent.), without quietly widening the provider or customer network scope. The separate acceptance measure remains: The designated intermediate system role matches documented circuit priority policy and shortest-path computations remain consistent.

C.

An alternative 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 relevant evidence and acceptance are LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths and the designated intermediate system role matches documented circuit priority policy and shortest-path computations remain consistent, respectively.

D.

Another proposed approval 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. The present scope must instead be justified by LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths.

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