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 15
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.
Question 141
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 specific bounded Junos routing or switching correction best addresses this service-provider issue?
Answer and Explanation
Correct Answer: C
Another proposed action is: Verify the handoff contract and bridge interface port mode, then restore only the intended tag treatment and VLAN membership. That does not directly address the observed condition: The IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6. The more targeted correction is: Inspect the advertised address-family-specific TLVs and corresponding IPv6 routing table and interface support before changing IS-IS policy.
Another proposed action is: Inspect IS-IS LSP flooding, level scope and database synchronization before deciding on targeted refresh or isolation steps. It targets a different dependency; the evidence here is the IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6.
IS-IS TLV interpretation leads to wrong address family test. The decisive observation is the IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6. The proposed fix is: Inspect the advertised address-family-specific TLVs and corresponding IPv6 routing table and interface support before changing IS-IS policy. An observable result is: Both route-family displays match their advertised TLV data and IPv6 next-hop reachability is verified separately.
That alternative concerns: Validate LAN circuit priority and DIS role independently from route metrics; change only the control-plane election setting if the design requires it. The relevant evidence is the IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6. The corresponding fix is: Inspect the advertised address-family-specific TLVs and corresponding IPv6 routing table and interface support before changing IS-IS policy.
Question 142
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. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?
Answer and Explanation
Correct Answer: A
The IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6. That fact identifies the relevant dependency, rather than a separate issue. IS-IS uses TLVs to encode protocol information, and route-family visibility must be checked in the correct RIB.
Another proposed finding is: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths. It is not the recorded discriminator, which is the IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6.
Another piece of evidence concerns Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist. The current incident instead shows: The IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6. This distinction supports the action: Inspect the advertised address-family-specific TLVs and corresponding IPv6 routing table and interface support before changing IS-IS policy.
Another alternative would address Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy as decisive. The actual evidence in this case is the IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6.
Question 143
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 Junos networking principle best explains the relevant engineering decision?
Answer and Explanation
Correct Answer: B
The competing option invokes: BGP hold timers and KEEPALIVE messages provide session liveness independent of accepted route policies. Evidence for this case: Peer history contains hold timer expirations and packet captures show sporadic missing keepalives during a saturated control-plane event. The present evidence is: 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 principle is: IS-IS uses TLVs to encode protocol information, and route-family visibility must be checked in the correct RIB.
IS-IS uses TLVs to encode protocol information, and route-family visibility must be checked in the correct RIB. This distinction accounts for the IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6; another unrelated mechanism would not address the same condition.
A different principle is: 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. The present evidence, however, is the IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6. The relevant rule is: IS-IS uses TLVs to encode protocol information, and route-family visibility must be checked in the correct RIB.
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 uses TLVs to encode protocol information, and route-family visibility must be checked in the correct RIB.
Question 144
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. Intended bounded correction: Inspect the advertised address-family-specific TLVs and corresponding IPv6 routing table and interface support before changing IS-IS policy. Which independently verifiable test best demonstrates the intended correction worked?
Answer and Explanation
Correct Answer: B
A different option checks: The designated intermediate system role matches documented circuit priority policy and shortest-path computations remain consistent. The case-specific acceptance condition is instead Both route-family displays match their advertised TLV data and IPv6 next-hop reachability is verified separately.
The independent verification condition is: Both route-family displays match their advertised TLV data and IPv6 next-hop reachability is verified separately. That result checks whether the original evidence—the IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6—has been addressed.
That result would assess another condition: Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero. The correct criterion is directly linked to the finding: The IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6.
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: Both route-family displays match their advertised TLV data and IPv6 next-hop reachability is verified separately.
Question 145
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 material service-availability, routing, switching or security risk most directly needs control?
Answer and Explanation
Correct Answer: D
Another caution is: Altering link metrics to force a DIS outcome can reroute unrelated customer traffic without changing election priority. The key risk in this case is: Assuming every IS-IS LSP attribute populates every family can misdirect troubleshooting and policy changes.
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 the advertised address-family-specific TLVs and corresponding IPv6 routing table and interface support before changing IS-IS policy; the material limitation is Assuming every IS-IS LSP attribute populates every family can misdirect troubleshooting and policy changes.
This limitation concerns another setting: Debugging only the global table can prompt unintended configuration changes to an otherwise healthy customer VPN. The observed facts here make a different caution decisive: Assuming every IS-IS LSP attribute populates every family can misdirect troubleshooting and policy changes.
A necessary safeguard is: Assuming every IS-IS LSP attribute populates every family can misdirect troubleshooting and policy changes. The proposed correction remains: Inspect the advertised address-family-specific TLVs and corresponding IPv6 routing table and interface support before changing IS-IS policy.
Question 146
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 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: MAC forwarding tables on the access switch show the customer source learned on an unexpected access port and no destination learning for the intended bridge domain. The case-relevant check is: 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.
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 the IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6. The focused check here is: 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 focused investigation should 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. It is tied to the observed evidence: The IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6. It tests the conditions for this response: Inspect the advertised address-family-specific TLVs and corresponding IPv6 routing table and interface support before changing IS-IS policy.
That check concerns a different signal: 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-relevant check is: 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.
Question 147
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 controlled operational implementation sequence best protects the related provider service?
Answer and Explanation
Correct Answer: B
Another possible combination is: First verify the observed failure (Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy.); review and authorize the bounded correction (Inspect applicable BGP best-path attributes and local routing policy before modifying any IGP metric or neighboring AS path.); then independently verify the intended outcome (The chosen path matches the documented policy intent and forwarding probes follow the selected healthy upstream.) before production rollout. The current record instead supports Inspect the advertised address-family-specific TLVs and corresponding IPv6 routing table and interface support before changing IS-IS policy, verified by Both route-family displays match their advertised TLV data and IPv6 next-hop reachability is verified separately.
The starting point is the IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6. The proposed action and its separate check are Inspect the advertised address-family-specific TLVs and corresponding IPv6 routing table and interface support before changing IS-IS policy and Both route-family displays match their advertised TLV data and IPv6 next-hop reachability is verified separately, respectively.
Another action-and-check pairing is: First verify the observed failure (Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist.); review and authorize the bounded correction (Inspect IS-IS LSP flooding, level scope and database synchronization before deciding on targeted refresh or isolation steps.); then independently verify the intended outcome (Peer databases converge on the expected LSP set and the authorized loopback routes become usable without forcing widespread protocol resets.) before production rollout. The evidence here is the IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6. The required action and proof are Inspect the advertised address-family-specific TLVs and corresponding IPv6 routing table and interface support before changing IS-IS policy and Both route-family displays match their advertised TLV data and IPv6 next-hop reachability is verified separately.
An alternative plan 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 does not test the case-specific condition: The IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6.
Question 148
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 set of evidence, limited change and independent validation best justifies authorization?
Answer and Explanation
Correct Answer: C
Another approval package concerns: Observed evidence (The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance.), limited correction (Repeat routing and operational tests explicitly in the correct customer instance and investigate any actual gap without changing global routing.), independently measurable result (Route displays and sourced tests from the correct instance explain end-to-end reachability and isolate the false default-table alarm.). 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.
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: Inspect the advertised address-family-specific TLVs and corresponding IPv6 routing table and interface support before changing IS-IS policy.
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: Observed evidence (The IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6.), limited correction (Inspect the advertised address-family-specific TLVs and corresponding IPv6 routing table and interface support before changing IS-IS policy.), independently measurable result (Both route-family displays match their advertised TLV data and IPv6 next-hop reachability is verified separately.). Its measurable outcome is: Both route-family displays match their advertised TLV data and IPv6 next-hop reachability is verified separately.
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 the IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6.
Question 149
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. If the change fails its expected acceptance test, which controlled recovery approach is most appropriate?
Answer and Explanation
Correct Answer: A
A contingency plan would 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. This preserves control of the change linked to the IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6.
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: The IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6. The bounded fallback is: 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.
Another option proposes: Pause changes, preserve the differentiating evidence (Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link.), restore the last approved safe network state and reassess area mismatch prevents a core ospf neighbor from forming. Its assumptions differ from the observed failure; the appropriate recovery is: Pause changes, preserve the differentiating evidence (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.
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 the IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6.
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?
Answer and Explanation
Correct Answer: D
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.
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.
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.
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.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests
- 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)
- Juniper JN0-364 Practice Test 17 - 10 Questions (Last Reviewed 02-Nov-2026)