Pass Juniper JN0-364 Exam in First Attempt Guaranteed!
Get 100% Latest Exam Questions, Accurate & Verified Answers!
30 Days Free Updates, Instant Download!
Juniper JN0-364 Practice Test 14
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?
Answer and Explanation
Correct Answer: 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.
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.
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.
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.
Question 131
A fictional Junos service-provider engineer encounters this scenario: An intermediate Junos router reports an IS-IS adjacency yet several remote loopback routes are missing after a control-plane maintenance event. Distinguishing evidence: Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist. Which specific bounded Junos routing or switching correction best addresses this service-provider issue?
Answer and Explanation
Correct Answer: A
IS-IS circuit has a neighbor but incomplete link-state information. The decisive observation is Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist. The proposed fix is: Inspect IS-IS LSP flooding, level scope and database synchronization before deciding on targeted refresh or isolation steps. An observable result is: Peer databases converge on the expected LSP set and the authorized loopback routes become usable without forcing widespread protocol resets.
Another proposed action is: Inspect the broadcast network type, priorities and DR election state before changing any OSPF settings; document expected adjacency behavior. It targets a different dependency; the evidence here is Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist.
Another option proposes: Verify domain-level design and configure the approved overlapping IS-IS level on the intended interface and routing instance. The specific correction is: Inspect IS-IS LSP flooding, level scope and database synchronization before deciding on targeted refresh or isolation steps. The deciding evidence is: Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist.
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 Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist. The corresponding fix is: Inspect IS-IS LSP flooding, level scope and database synchronization before deciding on targeted refresh or isolation steps.
Question 132
A fictional Junos service-provider engineer encounters this scenario: An intermediate Junos router reports an IS-IS adjacency yet several remote loopback routes are missing after a control-plane maintenance event. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?
Answer and Explanation
Correct Answer: D
Another piece of evidence concerns Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency. The current incident instead shows: Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist. This distinction supports the action: Inspect IS-IS LSP flooding, level scope and database synchronization before deciding on targeted refresh or isolation steps.
Another alternative would address Advertised route inspection lists a private customer prefix that is not present in the approved external export inventory as decisive. The actual evidence in this case is Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist.
This other option describes: The IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6. The problem to explain is different: Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist.
The record points to Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist. After confirming the clue, the appropriate response is: Inspect IS-IS LSP flooding, level scope and database synchronization before deciding on targeted refresh or isolation steps.
Question 133
A fictional Junos service-provider engineer encounters this scenario: An intermediate Junos router reports an IS-IS adjacency yet several remote loopback routes are missing after a control-plane maintenance event. Distinguishing evidence: Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist. Which Junos networking principle best explains the relevant engineering decision?
Answer and Explanation
Correct Answer: B
A different principle is: IBGP route reflection relies on explicit client relationships and correct propagation semantics. Evidence for this case: Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior. The present evidence, however, is Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist. The relevant rule is: IS-IS PDU exchange and link-state database synchronization must be checked independently from adjacency status.
The relevant principle is: IS-IS PDU exchange and link-state database synchronization must be checked independently from adjacency status. The case evidence is Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist. The practical response is: Inspect IS-IS LSP flooding, level scope and database synchronization before deciding on targeted refresh or isolation steps.
The competing option 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 present evidence is: Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist. The case-relevant principle is: IS-IS PDU exchange and link-state database synchronization must be checked independently from adjacency status.
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: Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist.
Question 134
A fictional Junos service-provider engineer encounters this scenario: An intermediate Junos router reports an IS-IS adjacency yet several remote loopback routes are missing after a control-plane maintenance event. Intended bounded correction: Inspect IS-IS LSP flooding, level scope and database synchronization before deciding on targeted refresh or isolation steps. Which independently verifiable test best demonstrates the intended correction worked?
Answer and Explanation
Correct Answer: D
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: Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist.
Another proposed result is: The session remains established over representative monitored intervals and loss testing confirms appropriate recovery behavior. It would not independently establish the required outcome: Peer databases converge on the expected LSP set and the authorized loopback routes become usable without forcing widespread protocol resets.
A different option checks: The pair establishes an adjacency at the planned level and corresponding level-specific link-state information is exchanged. The case-specific acceptance condition is instead Peer databases converge on the expected LSP set and the authorized loopback routes become usable without forcing widespread protocol resets.
The independent verification condition is: Peer databases converge on the expected LSP set and the authorized loopback routes become usable without forcing widespread protocol resets. That result checks whether the original evidence—Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist—has been addressed.
Question 135
A fictional Junos service-provider engineer encounters this scenario: An intermediate Junos router reports an IS-IS adjacency yet several remote loopback routes are missing after a control-plane maintenance event. Distinguishing evidence: Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist. Which material service-availability, routing, switching or security risk most directly needs control?
Answer and Explanation
Correct Answer: A
The risk to retain is: Blindly restarting IS-IS on every router can add topology disruption without proving database cause. The original evidence is Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist; widening the change beyond it is not justified.
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: Blindly restarting IS-IS on every router can add topology disruption without proving database cause.
Another caution is: Replacing selective import policy with accept-all could expose the ISP to untrusted or excess customer routes. The key risk in this case is: Blindly restarting IS-IS on every router can add topology disruption without proving database cause.
Another emphasis concerns: Turning on all levels across an ISP network without design approval can leak reachability or alter SPF topology. The current change is Inspect IS-IS LSP flooding, level scope and database synchronization before deciding on targeted refresh or isolation steps; the material limitation is Blindly restarting IS-IS on every router can add topology disruption without proving database cause.
Question 136
A fictional Junos service-provider engineer encounters this scenario: An intermediate Junos router reports an IS-IS adjacency yet several remote loopback routes are missing after a control-plane maintenance event. Distinguishing evidence: Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist. Which focused investigation is the most useful before modifying the network configuration?
Answer and Explanation
Correct Answer: B
Another check 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. The case observation to isolate is Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist. The focused check here is: 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.
The pre-change check should 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. That check directly concerns Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist.
That check concerns a different signal: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Received-route visibility shows the customer prefix, while the import policy match excludes its approved prefix length and the RIB lacks the route. The case-relevant check is: 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.
Another check would 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. The case observation to isolate is Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist. The focused check here is: 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.
Question 137
A fictional Junos service-provider engineer encounters this scenario: An intermediate Junos router reports an IS-IS adjacency yet several remote loopback routes are missing after a control-plane maintenance event. Distinguishing evidence: Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist. Which controlled operational implementation sequence best protects the related provider service?
Answer and Explanation
Correct Answer: A
The case evidence indicates: Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist. Apply the scoped action: Inspect IS-IS LSP flooding, level scope and database synchronization before deciding on targeted refresh or isolation steps. Confirm its effect independently: Peer databases converge on the expected LSP set and the authorized loopback routes become usable without forcing widespread protocol resets.
An alternative plan is: First verify the observed failure (Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding.); review and authorize the bounded correction (Verify the handoff contract and bridge interface port mode, then restore only the intended tag treatment and VLAN membership.); then independently verify the intended outcome (The customer CE exchanges untagged frames successfully without gaining access to other wholesale service VLANs.) before production rollout. It does not test the case-specific condition: Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist.
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 Inspect IS-IS LSP flooding, level scope and database synchronization before deciding on targeted refresh or isolation steps, verified by Peer databases converge on the expected LSP set and the authorized loopback routes become usable without forcing widespread protocol resets.
Another potential sequence 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 has no direct link to the distinguishing evidence: Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist.
Question 138
A fictional Junos service-provider engineer encounters this scenario: An intermediate Junos router reports an IS-IS adjacency yet several remote loopback routes are missing after a control-plane maintenance event. Distinguishing evidence: Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist. Which set of evidence, limited change and independent validation best justifies authorization?
Answer and Explanation
Correct Answer: D
An alternative release decision is: Observed evidence (Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy.), limited correction (Inspect applicable BGP best-path attributes and local routing policy before modifying any IGP metric or neighboring AS path.), independently measurable result (The chosen path matches the documented policy intent and forwarding probes follow the selected healthy upstream.). It does not match the current change: Inspect IS-IS LSP flooding, level scope and database synchronization before deciding on targeted refresh or isolation steps.
Another approval action 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 relevant evidence and acceptance are Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist and Peer databases converge on the expected LSP set and the authorized loopback routes become usable without forcing widespread protocol resets, respectively.
Another approval package concerns: 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.). The present scope must instead be justified by Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist.
The approval decision should consider Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist. The specific proposal 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.). Its measurable outcome is: Peer databases converge on the expected LSP set and the authorized loopback routes become usable without forcing widespread protocol resets.
Question 139
A fictional Junos service-provider engineer encounters this scenario: An intermediate Junos router reports an IS-IS adjacency yet several remote loopback routes are missing after a control-plane maintenance event. Distinguishing evidence: Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist. If the change fails its expected acceptance test, which controlled recovery approach is most appropriate?
Answer and Explanation
Correct Answer: A
If the change fails acceptance, the bounded recovery is: 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. The case-specific risk is Blindly restarting IS-IS on every router can add topology disruption without proving database cause. The original evidence remains: Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist.
Another option proposes: Pause changes, preserve the differentiating evidence (The IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6.), restore the last approved safe network state and reassess is-is tlv interpretation leads to wrong address family test. Its assumptions differ from the observed failure; the appropriate recovery is: 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.
Another fallback concerns pausing 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. The current change concerns Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist.
Another recovery route would pause changes, preserve the differentiating evidence (Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy.), restore the last approved safe network state and reassess bgp best path differs from an operator's simple metric assumption. It does not preserve the condition of 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 bounded fallback is: 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.
Question 140
A fictional Junos service-provider engineer encounters this scenario: An intermediate Junos router reports an IS-IS adjacency yet several remote loopback routes are missing after a control-plane maintenance event. Distinguishing evidence: Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist. Which bounded approval scope avoids unintended changes to other provider or customer services?
Answer and Explanation
Correct Answer: B
An alternative 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 relevant evidence and acceptance are Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist and Peer databases converge on the expected LSP set and the authorized loopback routes become usable without forcing widespread protocol resets, respectively.
The approval decision should consider Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist. The specific proposal is: 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. Its measurable outcome is: Peer databases converge on the expected LSP set and the authorized loopback routes become usable without forcing widespread protocol resets.
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: Inspect IS-IS LSP flooding, level scope and database synchronization before deciding on targeted refresh or isolation steps.
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 Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist and Peer databases converge on the expected LSP set and the authorized loopback routes become usable without forcing widespread protocol resets, respectively.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests
- Juniper JN0-364 Practice Test 12 - 10 Questions (Last Reviewed 07-Nov-2026)
- Juniper JN0-364 Practice Test 13 - 10 Questions (Last Reviewed 06-Nov-2026)
- Juniper JN0-364 Practice Test 14 - 10 Questions (Last Reviewed 05-Nov-2026)
- Juniper JN0-364 Practice Test 15 - 10 Questions (Last Reviewed 04-Nov-2026)
- Juniper JN0-364 Practice Test 16 - 10 Questions (Last Reviewed 03-Nov-2026)