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 12
Question 110
A fictional Junos service-provider engineer encounters this scenario: A troubleshooting script reports a remote OSPF branch unreachable even though traffic in a customer virtual router is healthy. Distinguishing evidence: The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance. Which bounded approval scope avoids unintended changes to other provider or customer services?
Answer and Explanation
Correct Answer: D
An alternative approval would approve only the bounded change (Inspect the broadcast network type, priorities and DR election state before changing any OSPF settings; document expected adjacency behavior.) after independently checking (The observed DR and BDR remain legitimate and all routers learn correct routes without forcing unnecessary full mesh adjacencies.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are the script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance and Route displays and sourced tests from the correct instance explain end-to-end reachability and isolate the false default-table alarm, respectively.
Another proposed approval would approve only the bounded change (Apply a precise export filter and route-policy tests for public prefixes, then confirm rejected customer-only routes stay internal.) after independently checking (Upstream advertised-route output contains only approved prefixes and the private customer destination remains available in its intended instance.), without quietly widening the provider or customer network scope. The present scope must instead be justified by the script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance.
A separate release decision would approve only the bounded change (Compare link-state database reachability with route calculation, preference and active forwarding selection before modifying advertisement filters.) after independently checking (Database entries and active route selection are explainable, and probes follow the intended next hop without falsely requiring every LSA to be an active route.), without quietly widening the provider or customer network scope. It does not match the current change: Repeat routing and operational tests explicitly in the correct customer instance and investigate any actual gap without changing global routing.
The bounded proposal is: Approve only the bounded change (Repeat routing and operational tests explicitly in the correct customer instance and investigate any actual gap without changing global routing.) after independently checking (Route displays and sourced tests from the correct instance explain end-to-end reachability and isolate the false default-table alarm.), without quietly widening the provider or customer network scope. The separate acceptance measure remains: Route displays and sourced tests from the correct instance explain end-to-end reachability and isolate the false default-table alarm.
Question 111
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 specific bounded Junos routing or switching correction best addresses this service-provider issue?
Answer and Explanation
Correct Answer: D
Another proposed action is: Inspect applicable BGP best-path attributes and local routing policy before modifying any IGP metric or neighboring AS path. That does not directly address the observed condition: Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency. The more targeted correction is: Verify domain-level design and configure the approved overlapping IS-IS level on the intended interface and routing instance.
Another proposed action is: Inspect the advertised address-family-specific TLVs and corresponding IPv6 routing table and interface support before changing IS-IS policy. It targets a different dependency; the evidence here is Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency.
Another option proposes: Inspect IS-IS LSP flooding, level scope and database synchronization before deciding on targeted refresh or isolation steps. The specific correction is: Verify domain-level design and configure the approved overlapping IS-IS level on the intended interface and routing instance. The deciding evidence is: Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency.
The evidence for the issue is Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency. The matching step is: Verify domain-level design and configure the approved overlapping IS-IS level on the intended interface and routing instance. This follows the principle that IS-IS adjacencies depend on compatible level operation as well as link connectivity.
Question 112
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. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?
Answer and Explanation
Correct Answer: A
Consider this evidence: Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency. The applicable explanation is: IS-IS adjacencies depend on compatible level operation as well as link connectivity. The matching response is: Verify domain-level design and configure the approved overlapping IS-IS level on the intended interface and routing instance.
Another alternative would address Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist as decisive. The actual evidence in this case is Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency.
This other option describes: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths. The problem to explain is different: Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency.
Another proposed finding is: OSPF database output includes relevant link-state information, whereas the active route table prefers a more specific or otherwise preferred competing route for the destination. It is not the recorded discriminator, which is Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency.
Question 113
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 Junos networking principle best explains the relevant engineering decision?
Answer and Explanation
Correct Answer: B
A different principle is: BGP peering requires correctly addressed reachable transport endpoints and compatible session parameters. Evidence for this case: The neighboring router advertises a different source address from the one in the local configured BGP neighbor statement and logs show connection attempts to the obsolete IP. The present evidence, however, is Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency. The relevant rule is: IS-IS adjacencies depend on compatible level operation as well as link connectivity.
The relevant principle is: IS-IS adjacencies depend on compatible level operation as well as link connectivity. The case evidence is Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency. The practical response is: Verify domain-level design and configure the approved overlapping IS-IS level on the intended interface and routing instance.
The competing option 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 present evidence is: Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency. The case-relevant principle is: IS-IS adjacencies depend on compatible level operation as well as link connectivity.
That principle concerns another fact pattern: 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. Here the key fact is: Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency.
Question 114
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. Intended bounded correction: Verify domain-level design and configure the approved overlapping IS-IS level on the intended interface and routing instance. Which independently verifiable test best demonstrates the intended correction worked?
Answer and Explanation
Correct Answer: A
Confirm the correction by demonstrating: The pair establishes an adjacency at the planned level and corresponding level-specific link-state information is exchanged. This directly tests the intended change, Verify domain-level design and configure the approved overlapping IS-IS level on the intended interface and routing instance.
Another proposed result is: Peer databases converge on the expected LSP set and the authorized loopback routes become usable without forcing widespread protocol resets. It would not independently establish the required outcome: The pair establishes an adjacency at the planned level and corresponding level-specific link-state information is exchanged.
A different option checks: Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero. The case-specific acceptance condition is instead the pair establishes an adjacency at the planned level and corresponding level-specific link-state information is exchanged.
Passing that test would not establish resolution of the stated issue. The relevant proof is: The pair establishes an adjacency at the planned level and corresponding level-specific link-state information is exchanged.
Question 115
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 material service-availability, routing, switching or security risk most directly needs control?
Answer and Explanation
Correct Answer: A
The risk to retain is: Turning on all levels across an ISP network without design approval can leak reachability or alter SPF topology. The original evidence is Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency; widening the change beyond it is not justified.
Another emphasis concerns: Altering link metrics to force a DIS outcome can reroute unrelated customer traffic without changing election priority. The current change is Verify domain-level design and configure the approved overlapping IS-IS level on the intended interface and routing instance; the material limitation is Turning on all levels across an ISP network without design approval can leak reachability or alter SPF topology.
This limitation concerns another setting: A topology metric change affects many prefixes and can cause transient congestion beyond the maintenance link. The observed facts here make a different caution decisive: Turning on all levels across an ISP network without design approval can leak reachability or alter SPF topology.
Another caution is: Adding a blanket export accept can redistribute routes that are not part of the contracted service. The key risk in this case is: Turning on all levels across an ISP network without design approval can leak reachability or alter SPF topology.
Question 116
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 focused investigation is the most useful before modifying the network configuration?
Answer and Explanation
Correct Answer: C
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: Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency.
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 Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency. The focused check here is: 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 focused investigation should 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 is tied to the observed evidence: Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency. It tests the conditions for this response: Verify domain-level design and configure the approved overlapping IS-IS level on the intended interface and routing instance.
That check concerns a different signal: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding. The case-relevant check is: 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.
Question 117
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 controlled operational implementation sequence best protects the related provider service?
Answer and Explanation
Correct Answer: B
Another action-and-check pairing 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. The evidence here is Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency. The required action and proof are Verify domain-level design and configure the approved overlapping IS-IS level on the intended interface and routing instance and the pair establishes an adjacency at the planned level and corresponding level-specific link-state information is exchanged.
The correction is Verify domain-level design and configure the approved overlapping IS-IS level on the intended interface and routing instance. The matching proof is the pair establishes an adjacency at the planned level and corresponding level-specific link-state information is exchanged. Both address the finding that Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency.
Another possible combination is: 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. The current record instead supports Verify domain-level design and configure the approved overlapping IS-IS level on the intended interface and routing instance, verified by the pair establishes an adjacency at the planned level and corresponding level-specific link-state information is exchanged.
Another potential sequence is: 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. It has no direct link to the distinguishing evidence: Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency.
Question 118
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 set of evidence, limited change and independent validation best justifies authorization?
Answer and Explanation
Correct Answer: D
Another approval package concerns: 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 present scope must instead be justified by Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency.
An alternative release decision 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.). 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.
Another approval action is: Observed evidence (Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts.), limited correction (Separate the tenant virtual switches and bridge-domain scopes while preserving the contracted tag translation on each handoff.), independently measurable result (Broadcast and unknown-unicast tests remain isolated to each customer and independent service port traffic follows expected boundaries.). 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.
The change-control boundary 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.). The evidence for this scope is Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency.
Question 119
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. If the change fails its expected acceptance test, which controlled recovery approach is most appropriate?
Answer and Explanation
Correct Answer: C
Another fallback concerns pausing changes, preserve the differentiating evidence (Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior.), restore the last approved safe network state and reassess ibgp full-mesh assumption breaks after adding a route reflector. The current change concerns Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency.
Another recovery route 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. It does not preserve the condition of this case: Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency. The bounded fallback is: 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.
If the change fails acceptance, the bounded recovery is: 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. The case-specific risk is Turning on all levels across an ISP network without design approval can leak reachability or alter SPF topology. The original evidence remains: Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency.
Another fallback concerns pausing 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 current change concerns Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency.
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?
Answer and Explanation
Correct Answer: C
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.
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.
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.
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.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests
- Juniper JN0-364 Practice Test 10 - 10 Questions (Last Reviewed 09-Nov-2026)
- Juniper JN0-364 Practice Test 11 - 10 Questions (Last Reviewed 08-Nov-2026)
- 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)