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 33
Question 320
A fictional Junos service-provider engineer encounters this scenario: An IP transit LSP stops carrying customer payload after a core peer's LDP transport reachability changes during maintenance. Distinguishing evidence: The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped. 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 (Verify label distribution source, FEC identity and session state on adjacent routers, and correct the scoped label protocol fault through normal change control.) after independently checking (The neighboring label bindings and forwarding operations agree and both control-plane and data-plane path verification succeed.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are the underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped and LDP neighbors and label bindings recover for the intended FEC and payload forwarding resumes over the authorized LSP, respectively.
Another proposed approval would approve only the bounded change (Use LSP-aware OAM and node label-table checks at the actual affected hop, while retaining separate underlay reachability evidence.) after independently checking (The MPLS-aware path test and customer service probes agree on a working labeled route without masking unresolved transport problems.), without quietly widening the provider or customer network scope. The present scope must instead be justified by the underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped.
A separate release decision would approve only the bounded change (Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association.) after independently checking (Neighbor discovery and route displays resolve through the correct active interface and IPv6 service probes work over the approved path.), without quietly widening the provider or customer network scope. It does not match the current change: Check LDP session transport, adjacency and matching labeled next hops before choosing a narrow protocol or underlay correction.
The bounded proposal is: Approve only the bounded change (Check LDP session transport, adjacency and matching labeled next hops before choosing a narrow protocol or underlay correction.) after independently checking (LDP neighbors and label bindings recover for the intended FEC and payload forwarding resumes over the authorized LSP.), without quietly widening the provider or customer network scope. The separate acceptance measure remains: LDP neighbors and label bindings recover for the intended FEC and payload forwarding resumes over the authorized LSP.
Question 321
A fictional Junos service-provider engineer encounters this scenario: A core provider provisions an RSVP LSP around a crowded ring but the operational path still traverses an unavailable reservation hop. Distinguishing evidence: RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop. Which specific bounded Junos routing or switching correction best addresses this service-provider issue?
Answer and Explanation
Correct Answer: B
Another proposed action is: Inspect the label forwarding information base, push-swap-pop behavior and corresponding tunnel state on each relevant hop. That does not directly address the observed condition: RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop. The more targeted correction is: Compare reserved path constraints and actual underlay topology, then update the approved explicit route and resource availability before signaling again.
The observed condition is: RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop. This calls for the scoped change: Compare reserved path constraints and actual underlay topology, then update the approved explicit route and resource availability before signaling again. The acceptance measure is: The RSVP LSP establishes on a feasible approved path and measured forwarding follows its effective label-switched path.
Another option proposes: Check LDP session transport, adjacency and matching labeled next hops before choosing a narrow protocol or underlay correction. The specific correction is: Compare reserved path constraints and actual underlay topology, then update the approved explicit route and resource availability before signaling again. The deciding evidence is: RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop.
That alternative concerns: Confirm the authorized MSTP region, instance mappings and topology design, then align the relevant VLAN-to-instance definitions across participants. The relevant evidence is RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop. The corresponding fix is: Compare reserved path constraints and actual underlay topology, then update the approved explicit route and resource availability before signaling again.
Question 322
A fictional Junos service-provider engineer encounters this scenario: A core provider provisions an RSVP LSP around a crowded ring but the operational path still traverses an unavailable reservation hop. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?
Answer and Explanation
Correct Answer: A
RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop. That fact identifies the relevant dependency, rather than a separate issue. RSVP signaling requires feasible path constraints and available resources, distinct from ordinary IP route reachability.
Another proposed finding is: The configured IPv6 link-local next hop exists on multiple segments but operational route resolution references the former interface rather than the active neighbor link. It is not the recorded discriminator, which is RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop.
Another piece of evidence concerns IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration. The current incident instead shows: RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop. This distinction supports the action: Compare reserved path constraints and actual underlay topology, then update the approved explicit route and resource availability before signaling again.
Another alternative would address the route table has the destination IP, but MPLS forwarding-table inspection lacks the expected incoming label operation on the affected transit router as decisive. The actual evidence in this case is RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop.
Question 323
A fictional Junos service-provider engineer encounters this scenario: A core provider provisions an RSVP LSP around a crowded ring but the operational path still traverses an unavailable reservation hop. Distinguishing evidence: RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop. Which Junos networking principle best explains the relevant engineering decision?
Answer and Explanation
Correct Answer: C
The competing option invokes: OSPFv3 adjacency and IPv6 route advertisement require appropriate address-family topology and routing state. Evidence for this case: OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope. The present evidence is: RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop. The case-relevant principle is: RSVP signaling requires feasible path constraints and available resources, distinct from ordinary IP route reachability.
That principle concerns another fact pattern: MPLS label stack handling may include penultimate-hop popping as part of legitimate forwarding. Evidence for this case: The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP. Here the key fact is: RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop.
RSVP signaling requires feasible path constraints and available resources, distinct from ordinary IP route reachability. The recorded evidence is: RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop. The corresponding action is: Compare reserved path constraints and actual underlay topology, then update the approved explicit route and resource availability before signaling again.
This alternative invokes: LDP and other MPLS signaling must maintain consistent per-hop label bindings for each forwarding equivalence class. Evidence for this case: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment. The governing distinction for the recorded case is RSVP signaling requires feasible path constraints and available resources, distinct from ordinary IP route reachability.
Question 324
A fictional Junos service-provider engineer encounters this scenario: A core provider provisions an RSVP LSP around a crowded ring but the operational path still traverses an unavailable reservation hop. Intended bounded correction: Compare reserved path constraints and actual underlay topology, then update the approved explicit route and resource availability before signaling again. Which independently verifiable test best demonstrates the intended correction worked?
Answer and Explanation
Correct Answer: A
The expected outcome is the RSVP LSP establishes on a feasible approved path and measured forwarding follows its effective label-switched path. It links the scoped action to the documented condition: RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop.
Passing that test would not establish resolution of the stated issue. The relevant proof is: The RSVP LSP establishes on a feasible approved path and measured forwarding follows its effective label-switched path.
That result would assess another condition: The expected label entry and forwarding action appear at the designated hop and end-to-end customer traffic crosses the intended LSP. The correct criterion is directly linked to the finding: RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop.
Another proposed result is: Captured traffic and destination forwarding demonstrate correct reachability with expected label disposition at each hop. It would not independently establish the required outcome: The RSVP LSP establishes on a feasible approved path and measured forwarding follows its effective label-switched path.
Question 325
A fictional Junos service-provider engineer encounters this scenario: A core provider provisions an RSVP LSP around a crowded ring but the operational path still traverses an unavailable reservation hop. Distinguishing evidence: RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop. Which material service-availability, routing, switching or security risk most directly needs control?
Answer and Explanation
Correct Answer: B
Another caution is: A valid IGP route alone is not proof that an SR-MPLS data plane is programmed consistently across the area. The key risk in this case is: Relaxing all RSVP admission constraints can displace other bandwidth-reserved customer traffic.
Relaxing all RSVP admission constraints can displace other bandwidth-reserved customer traffic. That boundary protects the documented change, Compare reserved path constraints and actual underlay topology, then update the approved explicit route and resource availability before signaling again, from introducing an unrelated problem.
This limitation concerns another setting: Blindly disabling BPDU protection on an untrusted edge can open the switching domain to loops and root manipulation. The observed facts here make a different caution decisive: Relaxing all RSVP admission constraints can displace other bandwidth-reserved customer traffic.
Another caution is: Conflating underlay IP connectivity and labeled LSP health delays recovery of provider services. The key risk in this case is: Relaxing all RSVP admission constraints can displace other bandwidth-reserved customer traffic.
Question 326
A fictional Junos service-provider engineer encounters this scenario: A core provider provisions an RSVP LSP around a crowded ring but the operational path still traverses an unavailable reservation hop. Distinguishing evidence: RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop. 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 penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP. The case-relevant check is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop.
Another check would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The route table has the destination IP, but MPLS forwarding-table inspection lacks the expected incoming label operation on the affected transit router. The case observation to isolate is RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop. The focused check here is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop.
The focused investigation should compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop. It is tied to the observed evidence: RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop. It tests the conditions for this response: Compare reserved path constraints and actual underlay topology, then update the approved explicit route and resource availability before signaling again.
That check concerns a different signal: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: MSTP instance membership and region parameters show the second VLAN mapped into the first spanning-tree instance and mismatched neighboring regional configuration. The case-relevant check is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop.
Question 327
A fictional Junos service-provider engineer encounters this scenario: A core provider provisions an RSVP LSP around a crowded ring but the operational path still traverses an unavailable reservation hop. Distinguishing evidence: RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop. Which controlled operational implementation sequence best protects the related provider service?
Answer and Explanation
Correct Answer: A
RSVP signaling requires feasible path constraints and available resources, distinct from ordinary IP route reachability. For this issue, the appropriate bounded intervention is: Compare reserved path constraints and actual underlay topology, then update the approved explicit route and resource availability before signaling again. The acceptance test is: The RSVP LSP establishes on a feasible approved path and measured forwarding follows its effective label-switched path.
Another potential sequence is: First verify the observed failure (The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP.); review and authorize the bounded correction (Confirm expected label advertisement and pop operation at the penultimate hop rather than forcing unnecessary labels through every device.); then independently verify the intended outcome (Captured traffic and destination forwarding demonstrate correct reachability with expected label disposition at each hop.) before production rollout. It has no direct link to the distinguishing evidence: RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop.
Another action-and-check pairing is: First verify the observed failure (Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops.); review and authorize the bounded correction (Use LSP-aware OAM and node label-table checks at the actual affected hop, while retaining separate underlay reachability evidence.); then independently verify the intended outcome (The MPLS-aware path test and customer service probes agree on a working labeled route without masking unresolved transport problems.) before production rollout. The evidence here is RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop. The required action and proof are Compare reserved path constraints and actual underlay topology, then update the approved explicit route and resource availability before signaling again and the RSVP LSP establishes on a feasible approved path and measured forwarding follows its effective label-switched path.
An alternative plan is: First verify the observed failure (Session summary is established for the transport, yet address-family negotiation and received route views show no active IPv6 unicast exchange.); review and authorize the bounded correction (Confirm both peers' approved IPv6 unicast family configuration and import/export policies before enabling the specific family.); then independently verify the intended outcome (IPv6 routes appear only in the authorized routing tables and scoped IPv6 forwarding succeeds without altering existing IPv4 policy.) before production rollout. It does not test the case-specific condition: RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop.
Question 328
A fictional Junos service-provider engineer encounters this scenario: A core provider provisions an RSVP LSP around a crowded ring but the operational path still traverses an unavailable reservation hop. Distinguishing evidence: RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop. Which set of evidence, limited change and independent validation best justifies authorization?
Answer and Explanation
Correct Answer: D
Another approval package concerns: Observed evidence (Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops.), limited correction (Use LSP-aware OAM and node label-table checks at the actual affected hop, while retaining separate underlay reachability evidence.), independently measurable result (The MPLS-aware path test and customer service probes agree on a working labeled route without masking unresolved transport problems.). The present scope must instead be justified by RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop.
An alternative release decision is: Observed evidence (The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP.), limited correction (Confirm expected label advertisement and pop operation at the penultimate hop rather than forcing unnecessary labels through every device.), independently measurable result (Captured traffic and destination forwarding demonstrate correct reachability with expected label disposition at each hop.). It does not match the current change: Compare reserved path constraints and actual underlay topology, then update the approved explicit route and resource availability before signaling again.
Another approval action is: Observed evidence (MSTP instance membership and region parameters show the second VLAN mapped into the first spanning-tree instance and mismatched neighboring regional configuration.), limited correction (Confirm the authorized MSTP region, instance mappings and topology design, then align the relevant VLAN-to-instance definitions across participants.), independently measurable result (Per-instance operational port states match approved paths and both service VLAN groups retain loop-free reachability during a controlled link failure.). The relevant evidence and acceptance are RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop and the RSVP LSP establishes on a feasible approved path and measured forwarding follows its effective label-switched path, respectively.
The change-control boundary is: Observed evidence (RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop.), limited correction (Compare reserved path constraints and actual underlay topology, then update the approved explicit route and resource availability before signaling again.), independently measurable result (The RSVP LSP establishes on a feasible approved path and measured forwarding follows its effective label-switched path.). The evidence for this scope is RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop.
Question 329
A fictional Junos service-provider engineer encounters this scenario: A core provider provisions an RSVP LSP around a crowded ring but the operational path still traverses an unavailable reservation hop. Distinguishing evidence: RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop. 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 (RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop.), restore the last approved safe network state and reassess rsvp-signaled lsp does not match its expected traffic-engineering path. This preserves control of the change linked to RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop.
Another recovery route would pause changes, preserve the differentiating evidence (Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.), restore the last approved safe network state and reassess a core change advertises the wrong label to a downstream router. It does not preserve the condition of this case: RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop. The bounded fallback is: Pause changes, preserve the differentiating evidence (RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop.), restore the last approved safe network state and reassess rsvp-signaled lsp does not match its expected traffic-engineering path.
Another option proposes: Pause changes, preserve the differentiating evidence (The route table has the destination IP, but MPLS forwarding-table inspection lacks the expected incoming label operation on the affected transit router.), restore the last approved safe network state and reassess mpls label lookup is confused with an ip route table entry. Its assumptions differ from the observed failure; the appropriate recovery is: Pause changes, preserve the differentiating evidence (RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop.), restore the last approved safe network state and reassess rsvp-signaled lsp does not match its expected traffic-engineering path.
Another fallback concerns pausing changes, preserve the differentiating evidence (RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge.), restore the last approved safe network state and reassess rstp root role changes after an unauthorized low-priority bridge joins. The current change concerns RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop.
Question 330
A fictional Junos service-provider engineer encounters this scenario: A core provider provisions an RSVP LSP around a crowded ring but the operational path still traverses an unavailable reservation hop. Distinguishing evidence: RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop. Which bounded approval scope avoids unintended changes to other provider or customer services?
Answer and Explanation
Correct Answer: B
A separate release decision would approve only the bounded change (Use LSP-aware OAM and node label-table checks at the actual affected hop, while retaining separate underlay reachability evidence.) after independently checking (The MPLS-aware path test and customer service probes agree on a working labeled route without masking unresolved transport problems.), without quietly widening the provider or customer network scope. It does not match the current change: Compare reserved path constraints and actual underlay topology, then update the approved explicit route and resource availability before signaling again.
The change-control boundary is: Approve only the bounded change (Compare reserved path constraints and actual underlay topology, then update the approved explicit route and resource availability before signaling again.) after independently checking (The RSVP LSP establishes on a feasible approved path and measured forwarding follows its effective label-switched path.), without quietly widening the provider or customer network scope. The evidence for this scope is RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop.
Another proposed approval would approve only the bounded change (Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration.) after independently checking (Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route.), without quietly widening the provider or customer network scope. The present scope must instead be justified by RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop.
A separate release decision would approve only the bounded change (Confirm expected label advertisement and pop operation at the penultimate hop rather than forcing unnecessary labels through every device.) after independently checking (Captured traffic and destination forwarding demonstrate correct reachability with expected label disposition at each hop.), without quietly widening the provider or customer network scope. It does not match the current change: Compare reserved path constraints and actual underlay topology, then update the approved explicit route and resource availability before signaling again.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests
- Juniper JN0-364 Practice Test 31 - 10 Questions (Last Reviewed 19-Oct-2026)
- Juniper JN0-364 Practice Test 32 - 10 Questions (Last Reviewed 18-Oct-2026)
- Juniper JN0-364 Practice Test 33 - 10 Questions (Last Reviewed 17-Oct-2026)
- Juniper JN0-364 Practice Test 34 - 10 Questions (Last Reviewed 16-Oct-2026)
- Juniper JN0-364 Practice Test 35 - 10 Questions (Last Reviewed 15-Oct-2026)