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 1
Question 1
A fictional Junos service-provider engineer encounters this scenario: A regional Junos provider edge begins preferring a manually installed default route after a circuit migration, although the specified next-hop address cannot be resolved through any working connected path. Distinguishing evidence: The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway. Which specific bounded Junos routing or switching correction best addresses this service-provider issue?
Answer and Explanation
Correct Answer: C
Another proposed action is: Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance. That does not directly address the observed condition: The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway. The more targeted correction is: Correct the static next-hop resolution against the verified active transit gateway and confirm the candidate configuration before committing the narrow change.
Another proposed action is: Constrain the policy and RIB group to the documented destination and routing instances, then review import consequences in a candidate configuration. It targets a different dependency; the evidence here is the routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway.
The issue turns on the routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway. The relevant rule is that Static route installation depends on viable next-hop resolution, protocol preference and route-table context. The targeted correction is: Correct the static next-hop resolution against the verified active transit gateway and confirm the candidate configuration before committing the narrow change.
That alternative concerns: Inspect the forwarding-table next hops and the Junos load-balancing policy, then measure multiple independent flows and validate the intended per-flow distribution. The relevant evidence is the routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway. The corresponding fix is: Correct the static next-hop resolution against the verified active transit gateway and confirm the candidate configuration before committing the narrow change.
Question 2
A fictional Junos service-provider engineer encounters this scenario: A regional Junos provider edge begins preferring a manually installed default route after a circuit migration, although the specified next-hop address cannot be resolved through any working connected path. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?
Answer and Explanation
Correct Answer: A
The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway. That fact identifies the relevant dependency, rather than a separate issue. Static route installation depends on viable next-hop resolution, protocol preference and route-table context.
Another proposed finding is: BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails. It is not the recorded discriminator, which is the routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway.
Another piece of evidence concerns Next-hop displays show multiple usable forwarding next hops, yet the test repeats one fixed five-tuple that consistently hashes to a single link. The current incident instead shows: The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway. This distinction supports the action: Correct the static next-hop resolution against the verified active transit gateway and confirm the candidate configuration before committing the narrow change.
Another alternative would address the IS-IS database contains distinct reachability TLV content while the operational command targets only the inet address family rather than inet6 as decisive. The actual evidence in this case is the routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway.
Question 3
A fictional Junos service-provider engineer encounters this scenario: A regional Junos provider edge begins preferring a manually installed default route after a circuit migration, although the specified next-hop address cannot be resolved through any working connected path. Distinguishing evidence: The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway. Which Junos networking principle best explains the relevant engineering decision?
Answer and Explanation
Correct Answer: D
The competing option invokes: Routing instances and RIB groups require explicit route import and forwarding boundaries. Evidence for this case: Route inspection shows several tenant networks imported into a shared routing table through a broad RIB group rather than the single approved resolver route. The present evidence is: The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway. The case-relevant principle is: Static route installation depends on viable next-hop resolution, protocol preference and route-table context.
That principle concerns another fact pattern: Junos forwarding load balancing depends on the configured policy and traffic hashing, and must be validated against suitable flows. Evidence for this case: Next-hop displays show multiple usable forwarding next hops, yet the test repeats one fixed five-tuple that consistently hashes to a single link. Here the key fact is: The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway.
A different principle is: 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, however, is the routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway. The relevant rule is: Static route installation depends on viable next-hop resolution, protocol preference and route-table context.
The relevant principle is: Static route installation depends on viable next-hop resolution, protocol preference and route-table context. The case evidence is the routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway. The practical response is: Correct the static next-hop resolution against the verified active transit gateway and confirm the candidate configuration before committing the narrow change.
Question 4
A fictional Junos service-provider engineer encounters this scenario: A regional Junos provider edge begins preferring a manually installed default route after a circuit migration, although the specified next-hop address cannot be resolved through any working connected path. Intended bounded correction: Correct the static next-hop resolution against the verified active transit gateway and confirm the candidate configuration before committing the narrow change. Which independently verifiable test best demonstrates the intended correction worked?
Answer and Explanation
Correct Answer: A
The expected outcome is a controlled upstream failure and recovery shows the expected active route only while its resolved next hop is reachable and service probes succeed. It links the scoped action to the documented condition: The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway.
Passing that test would not establish resolution of the stated issue. The relevant proof is: A controlled upstream failure and recovery shows the expected active route only while its resolved next hop is reachable and service probes succeed.
That result would assess another condition: A broad representative multi-flow test uses both eligible paths while sessions preserve stable forwarding and loss stays within the agreed threshold. The correct criterion is directly linked to the finding: The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway.
Another proposed result is: The shared resolver prefix is available to the approved instance while unauthorized customer routes are absent from both route displays and forwarding tests. It would not independently establish the required outcome: A controlled upstream failure and recovery shows the expected active route only while its resolved next hop is reachable and service probes succeed.
Question 5
A fictional Junos service-provider engineer encounters this scenario: A regional Junos provider edge begins preferring a manually installed default route after a circuit migration, although the specified next-hop address cannot be resolved through any working connected path. Distinguishing evidence: The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway. Which material service-availability, routing, switching or security risk most directly needs control?
Answer and Explanation
Correct Answer: B
This limitation concerns another setting: A syntactically valid summary can conceal an unreachable constituent when operators rely only on control-plane advertisement. The observed facts here make a different caution decisive: Changing global route preferences to force a broken next hop can blackhole unrelated customer prefixes.
Changing global route preferences to force a broken next hop can blackhole unrelated customer prefixes. That boundary protects the documented change, Correct the static next-hop resolution against the verified active transit gateway and confirm the candidate configuration before committing the narrow change, from introducing an unrelated problem.
Another emphasis concerns: Overbroad route exchange between logical routing tables can break tenant isolation even without any physical link change. The current change is Correct the static next-hop resolution against the verified active transit gateway and confirm the candidate configuration before committing the narrow change; the material limitation is Changing global route preferences to force a broken next hop can blackhole unrelated customer prefixes.
This limitation concerns another setting: Blindly restarting IS-IS on every router can add topology disruption without proving database cause. The observed facts here make a different caution decisive: Changing global route preferences to force a broken next hop can blackhole unrelated customer prefixes.
Question 6
A fictional Junos service-provider engineer encounters this scenario: A regional Junos provider edge begins preferring a manually installed default route after a circuit migration, although the specified next-hop address cannot be resolved through any working connected path. Distinguishing evidence: The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway. Which focused investigation is the most useful before modifying the network configuration?
Answer and Explanation
Correct Answer: D
Another investigation would compare active Junos routing, protocol and forwarding displays with this differentiating 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. It does not directly establish the reported condition: The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway.
That check concerns a different signal: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails. The case-relevant check is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway.
Another check would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Route inspection shows several tenant networks imported into a shared routing table through a broad RIB group rather than the single approved resolver route. The case observation to isolate is the routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway. The focused check here is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway.
The current finding is the routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway. The specific pre-change check is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway. Use it to distinguish the problem from an unrelated symptom.
Question 7
A fictional Junos service-provider engineer encounters this scenario: A regional Junos provider edge begins preferring a manually installed default route after a circuit migration, although the specified next-hop address cannot be resolved through any working connected path. Distinguishing evidence: The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway. 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 (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.); review and authorize the bounded correction (Repeat routing and operational tests explicitly in the correct customer instance and investigate any actual gap without changing global routing.); then independently verify the intended outcome (Route displays and sourced tests from the correct instance explain end-to-end reachability and isolate the false default-table alarm.) before production rollout. The current record instead supports Correct the static next-hop resolution against the verified active transit gateway and confirm the candidate configuration before committing the narrow change, verified by a controlled upstream failure and recovery shows the expected active route only while its resolved next hop is reachable and service probes succeed.
The starting point is the routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway. The proposed action and its separate check are Correct the static next-hop resolution against the verified active transit gateway and confirm the candidate configuration before committing the narrow change and a controlled upstream failure and recovery shows the expected active route only while its resolved next hop is reachable and service probes succeed, respectively.
Another action-and-check pairing is: First verify the observed failure (Next-hop displays show multiple usable forwarding next hops, yet the test repeats one fixed five-tuple that consistently hashes to a single link.); review and authorize the bounded correction (Inspect the forwarding-table next hops and the Junos load-balancing policy, then measure multiple independent flows and validate the intended per-flow distribution.); then independently verify the intended outcome (A broad representative multi-flow test uses both eligible paths while sessions preserve stable forwarding and loss stays within the agreed threshold.) before production rollout. The evidence here is the routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway. The required action and proof are Correct the static next-hop resolution against the verified active transit gateway and confirm the candidate configuration before committing the narrow change and a controlled upstream failure and recovery shows the expected active route only while its resolved next hop is reachable and service probes succeed.
An alternative plan is: First verify the observed failure (Route inspection shows several tenant networks imported into a shared routing table through a broad RIB group rather than the single approved resolver route.); review and authorize the bounded correction (Constrain the policy and RIB group to the documented destination and routing instances, then review import consequences in a candidate configuration.); then independently verify the intended outcome (The shared resolver prefix is available to the approved instance while unauthorized customer routes are absent from both route displays and forwarding tests.) before production rollout. It does not test the case-specific condition: The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway.
Question 8
A fictional Junos service-provider engineer encounters this scenario: A regional Junos provider edge begins preferring a manually installed default route after a circuit migration, although the specified next-hop address cannot be resolved through any working connected path. Distinguishing evidence: The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway. Which set of evidence, limited change and independent validation best justifies authorization?
Answer and Explanation
Correct Answer: C
Another approval action is: 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 relevant evidence and acceptance are the routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway and a controlled upstream failure and recovery shows the expected active route only while its resolved next hop is reachable and service probes succeed, respectively.
Another approval package concerns: Observed evidence (Next-hop displays show multiple usable forwarding next hops, yet the test repeats one fixed five-tuple that consistently hashes to a single link.), limited correction (Inspect the forwarding-table next hops and the Junos load-balancing policy, then measure multiple independent flows and validate the intended per-flow distribution.), independently measurable result (A broad representative multi-flow test uses both eligible paths while sessions preserve stable forwarding and loss stays within the agreed threshold.). The present scope must instead be justified by the routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway.
The change-control boundary is: Observed evidence (The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway.), limited correction (Correct the static next-hop resolution against the verified active transit gateway and confirm the candidate configuration before committing the narrow change.), independently measurable result (A controlled upstream failure and recovery shows the expected active route only while its resolved next hop is reachable and service probes succeed.). The evidence for this scope is the routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway.
Another approval action is: Observed evidence (The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix.), limited correction (Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order.), independently measurable result (Packet samples and filter counters confirm only the approved customer flows use the alternate forwarding instance while management remains reachable.). The relevant evidence and acceptance are the routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway and a controlled upstream failure and recovery shows the expected active route only while its resolved next hop is reachable and service probes succeed, respectively.
Question 9
A fictional Junos service-provider engineer encounters this scenario: A regional Junos provider edge begins preferring a manually installed default route after a circuit migration, although the specified next-hop address cannot be resolved through any working connected path. Distinguishing evidence: The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway. If the change fails its expected acceptance test, which controlled recovery approach is most appropriate?
Answer and Explanation
Correct Answer: B
Another option proposes: Pause changes, preserve the differentiating evidence (Next-hop displays show multiple usable forwarding next hops, yet the test repeats one fixed five-tuple that consistently hashes to a single link.), restore the last approved safe network state and reassess per-flow load balancing creates asymmetric monitoring results. Its assumptions differ from the observed failure; the appropriate recovery is: Pause changes, preserve the differentiating evidence (The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway.), restore the last approved safe network state and reassess static route becomes active despite unreachable ultimate next hop.
If the change fails acceptance, the bounded recovery is: Pause changes, preserve the differentiating evidence (The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway.), restore the last approved safe network state and reassess static route becomes active despite unreachable ultimate next hop. The case-specific risk is Changing global route preferences to force a broken next hop can blackhole unrelated customer prefixes. The original evidence remains: The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway.
Another recovery route would pause changes, preserve the differentiating evidence (Route inspection shows several tenant networks imported into a shared routing table through a broad RIB group rather than the single approved resolver route.), restore the last approved safe network state and reassess route leaking across routing instances is broader than intended. It does not preserve the condition of this case: The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway. The bounded fallback is: Pause changes, preserve the differentiating evidence (The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway.), restore the last approved safe network state and reassess static route becomes active despite unreachable ultimate next hop.
Another option proposes: Pause changes, preserve the differentiating evidence (VRRP state displays show changed effective priorities, interface tracking, or configured preemption behavior that differs from the approved failback design.), restore the last approved safe network state and reassess vrrp backup becomes master after an expected preemption check. Its assumptions differ from the observed failure; the appropriate recovery is: Pause changes, preserve the differentiating evidence (The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway.), restore the last approved safe network state and reassess static route becomes active despite unreachable ultimate next hop.
Question 10
A fictional Junos service-provider engineer encounters this scenario: A regional Junos provider edge begins preferring a manually installed default route after a circuit migration, although the specified next-hop address cannot be resolved through any working connected path. Distinguishing evidence: The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway. Which bounded approval scope avoids unintended changes to other provider or customer services?
Answer and Explanation
Correct Answer: C
Another proposed 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 present scope must instead be justified by the routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway.
A separate release decision would approve only the bounded change (Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order.) after independently checking (Packet samples and filter counters confirm only the approved customer flows use the alternate forwarding instance while management remains reachable.), without quietly widening the provider or customer network scope. It does not match the current change: Correct the static next-hop resolution against the verified active transit gateway and confirm the candidate configuration before committing the narrow change.
The approval decision should consider the routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway. The specific proposal is: Approve only the bounded change (Correct the static next-hop resolution against the verified active transit gateway and confirm the candidate configuration before committing the narrow change.) after independently checking (A controlled upstream failure and recovery shows the expected active route only while its resolved next hop is reachable and service probes succeed.), without quietly widening the provider or customer network scope. Its measurable outcome is: A controlled upstream failure and recovery shows the expected active route only while its resolved next hop is reachable and service probes succeed.
Another proposed approval would approve only the bounded change (Inspect active contributing routes and the aggregation policy, then choose a scoped summary advertisement and appropriate blackhole safeguards that reflect verified forwarding behavior.) after independently checking (Neighbor route reception and end-to-end reachability tests demonstrate the intended covering advertisement without incorrectly promising restored access to the failed branch.), without quietly widening the provider or customer network scope. The present scope must instead be justified by the routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests
- Juniper JN0-364 Practice Test 1 - 10 Questions (Last Reviewed 18-Nov-2026)
- Juniper JN0-364 Practice Test 2 - 10 Questions (Last Reviewed 17-Nov-2026)
- Juniper JN0-364 Practice Test 3 - 10 Questions (Last Reviewed 16-Nov-2026)