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 36
Question 350
A fictional Junos service-provider engineer encounters this scenario: An engineer reports an MPLS failure because a capture on the final transit interface shows IP rather than an expected nonbottom service label. Distinguishing evidence: The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP. 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 (Verify the intended root and edge-port topology, then apply supported root protection on the authorized boundary and restore correct bridge priority.) after independently checking (The provider bridge remains legitimate root and a controlled superior-BPDU test is contained without permanent loop formation.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are the penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP and Captured traffic and destination forwarding demonstrate correct reachability with expected label disposition at each hop, respectively.
The approval decision should consider the penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP. The specific proposal is: 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. Its measurable outcome is: Captured traffic and destination forwarding demonstrate correct reachability with expected label disposition at each hop.
A separate release decision would approve only the bounded change (Inspect the label forwarding information base, push-swap-pop behavior and corresponding tunnel state on each relevant hop.) after independently checking (The expected label entry and forwarding action appear at the designated hop and end-to-end customer traffic crosses the intended LSP.), without quietly widening the provider or customer network scope. It does not match the current change: Confirm expected label advertisement and pop operation at the penultimate hop rather than forcing unnecessary labels through every device.
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 penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP and Captured traffic and destination forwarding demonstrate correct reachability with expected label disposition at each hop, respectively.
Question 351
A fictional Junos service-provider engineer encounters this scenario: A provider enables SR-MPLS in a core area but newly commissioned router loopbacks are not reachable through the intended shortest-path LSP. Distinguishing evidence: IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration. 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 spanning-tree interface states, alternate paths and convergence behavior and tune only supported Layer 2 features within the validated topology. That does not directly address the observed condition: 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 more targeted correction is: Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy.
The observed condition is: IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration. This calls for the scoped change: Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy. The acceptance measure is: Node SID and relevant label entries agree across the intended nodes and measured transport follows the computed shortest path.
Another option proposes: Inspect the label forwarding information base, push-swap-pop behavior and corresponding tunnel state on each relevant hop. The specific correction is: Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy. The deciding evidence is: IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration.
That alternative concerns: Verify label distribution source, FEC identity and session state on adjacent routers, and correct the scoped label protocol fault through normal change control. The relevant evidence is 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 corresponding fix is: Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy.
Question 352
A fictional Junos service-provider engineer encounters this scenario: A provider enables SR-MPLS in a core area but newly commissioned router loopbacks are not reachable through the intended shortest-path LSP. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?
Answer and Explanation
Correct Answer: A
Consider this evidence: 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 applicable explanation is: SR-MPLS needs consistent segment information and forwarding entries coordinated with the underlay IGP. The matching response is: Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy.
Another alternative would address 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 as decisive. The actual evidence in this case is IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration.
This other option describes: The route table has the destination IP, but MPLS forwarding-table inspection lacks the expected incoming label operation on the affected transit router. The problem to explain is different: IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration.
Another proposed finding is: The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP. It is not the recorded discriminator, which is IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration.
Question 353
A fictional Junos service-provider engineer encounters this scenario: A provider enables SR-MPLS in a core area but newly commissioned router loopbacks are not reachable through the intended shortest-path LSP. Distinguishing evidence: IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration. Which Junos networking principle best explains the relevant engineering decision?
Answer and Explanation
Correct Answer: B
A different principle is: Spanning-tree BPDU protection is a deliberate safety mechanism against unexpected bridge advertisements. Evidence for this case: Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error. The present evidence, however, is 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 relevant rule is: SR-MPLS needs consistent segment information and forwarding entries coordinated with the underlay IGP.
The relevant principle is: SR-MPLS needs consistent segment information and forwarding entries coordinated with the underlay IGP. The case evidence is 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 practical response is: Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy.
The competing option invokes: MPLS forwarding uses label-specific information and operations alongside underlying routing resolution. Evidence for this case: The route table has the destination IP, but MPLS forwarding-table inspection lacks the expected incoming label operation on the affected transit router. The present evidence is: 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 case-relevant principle is: SR-MPLS needs consistent segment information and forwarding entries coordinated with the underlay IGP.
That principle concerns another fact pattern: LDP advertises label bindings and requires appropriate transport and forwarding continuity for labeled paths. Evidence for this case: The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped. Here the key fact is: IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration.
Question 354
A fictional Junos service-provider engineer encounters this scenario: A provider enables SR-MPLS in a core area but newly commissioned router loopbacks are not reachable through the intended shortest-path LSP. Intended bounded correction: Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy. Which independently verifiable test best demonstrates the intended correction worked?
Answer and Explanation
Correct Answer: A
Confirm the correction by demonstrating: Node SID and relevant label entries agree across the intended nodes and measured transport follows the computed shortest path. This directly tests the intended change, Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy.
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: Node SID and relevant label entries agree across the intended nodes and measured transport follows the computed shortest path.
A different option checks: Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route. The case-specific acceptance condition is instead Node SID and relevant label entries agree across the intended nodes and measured transport follows the computed shortest path.
Passing that test would not establish resolution of the stated issue. The relevant proof is: Node SID and relevant label entries agree across the intended nodes and measured transport follows the computed shortest path.
Question 355
A fictional Junos service-provider engineer encounters this scenario: A provider enables SR-MPLS in a core area but newly commissioned router loopbacks are not reachable through the intended shortest-path LSP. Distinguishing evidence: IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration. Which material service-availability, routing, switching or security risk most directly needs control?
Answer and Explanation
Correct Answer: B
Another caution is: IPv4 route reachability or a single OSPFv3 neighbor state does not establish end-to-end IPv6 prefix routing. The key risk in this case is: A valid IGP route alone is not proof that an SR-MPLS data plane is programmed consistently across the area.
A necessary safeguard is: A valid IGP route alone is not proof that an SR-MPLS data plane is programmed consistently across the area. The proposed correction remains: Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy.
This limitation concerns another setting: Manually assigning arbitrary transport label values can conflict with dynamic label allocation and other customers' services. The observed facts here make a different caution decisive: A valid IGP route alone is not proof that an SR-MPLS data plane is programmed consistently across the area.
Another caution is: Treating normal PHP as corruption can cause disruptive changes and incorrect data-plane conclusions. The key risk in this case is: A valid IGP route alone is not proof that an SR-MPLS data plane is programmed consistently across the area.
Question 356
A fictional Junos service-provider engineer encounters this scenario: A provider enables SR-MPLS in a core area but newly commissioned router loopbacks are not reachable through the intended shortest-path LSP. Distinguishing evidence: IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration. Which focused investigation is the most useful before modifying the network configuration?
Answer and Explanation
Correct Answer: B
That check concerns a different signal: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Session summary is established for the transport, yet address-family negotiation and received route views show no active IPv6 unicast exchange. The case-relevant check is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: 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 finding is 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 specific pre-change check is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration. Use it to distinguish the problem from an unrelated symptom.
Another investigation would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment. It does not directly establish the reported condition: IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration.
That check concerns a different signal: 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-relevant check is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration.
Question 357
A fictional Junos service-provider engineer encounters this scenario: A provider enables SR-MPLS in a core area but newly commissioned router loopbacks are not reachable through the intended shortest-path LSP. Distinguishing evidence: IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration. Which controlled operational implementation sequence best protects the related provider service?
Answer and Explanation
Correct Answer: B
Another action-and-check pairing is: First verify the observed failure (Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error.); review and authorize the bounded correction (Validate whether the port must be a genuine edge-facing endpoint and preserve or redesign BPDU protection under approved topology changes.); then independently verify the intended outcome (The approved access segment forwards safely while a repeat unauthorized BPDU test triggers the intended control with an audit trail.) before production rollout. The evidence here is 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 required action and proof are Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy and Node SID and relevant label entries agree across the intended nodes and measured transport follows the computed shortest path.
The correction is Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy. The matching proof is Node SID and relevant label entries agree across the intended nodes and measured transport follows the computed shortest path. Both address the finding that IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration.
Another possible combination is: First verify the observed failure (The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped.); review and authorize the bounded correction (Check LDP session transport, adjacency and matching labeled next hops before choosing a narrow protocol or underlay correction.); then independently verify the intended outcome (LDP neighbors and label bindings recover for the intended FEC and payload forwarding resumes over the authorized LSP.) before production rollout. The current record instead supports Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy, verified by Node SID and relevant label entries agree across the intended nodes and measured transport follows the computed shortest path.
Another potential sequence is: First verify the observed failure (RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop.); review and authorize the bounded correction (Compare reserved path constraints and actual underlay topology, then update the approved explicit route and resource availability before signaling again.); then independently verify the intended outcome (The RSVP LSP establishes on a feasible approved path and measured forwarding follows its effective label-switched path.) before production rollout. It has no direct link to the distinguishing evidence: IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration.
Question 358
A fictional Junos service-provider engineer encounters this scenario: A provider enables SR-MPLS in a core area but newly commissioned router loopbacks are not reachable through the intended shortest-path LSP. Distinguishing evidence: IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration. Which set of evidence, limited change and independent validation best justifies authorization?
Answer and Explanation
Correct Answer: D
Another approval package concerns: 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 present scope must instead be justified by IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration.
An alternative release decision is: Observed evidence (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.), limited correction (Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association.), independently measurable result (Neighbor discovery and route displays resolve through the correct active interface and IPv6 service probes work over the approved path.). It does not match the current change: Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy.
Another approval action 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.). The relevant evidence and acceptance are IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration and Node SID and relevant label entries agree across the intended nodes and measured transport follows the computed shortest path, respectively.
The change-control boundary is: Observed evidence (IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration.), limited correction (Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy.), independently measurable result (Node SID and relevant label entries agree across the intended nodes and measured transport follows the computed shortest path.). The evidence for this scope is IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration.
Question 359
A fictional Junos service-provider engineer encounters this scenario: A provider enables SR-MPLS in a core area but newly commissioned router loopbacks are not reachable through the intended shortest-path LSP. Distinguishing evidence: IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration. If the change fails its expected acceptance test, which controlled recovery approach is most appropriate?
Answer and Explanation
Correct Answer: B
Another fallback concerns pausing changes, preserve the differentiating evidence (The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped.), restore the last approved safe network state and reassess mpls forwarding stops after an ldp adjacency fails. The current change 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.
A recovery option is to pause changes, preserve the differentiating evidence (IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration.), restore the last approved safe network state and reassess segment routing node-sid advertisement is present but path is absent. The intended change was Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy, and acceptance must still be judged against Node SID and relevant label entries agree across the intended nodes and measured transport follows the computed shortest 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 (IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration.), restore the last approved safe network state and reassess segment routing node-sid advertisement is present but path is absent.
Another fallback concerns pausing changes, preserve the differentiating evidence (The route to the GRE remote destination shows the tunnel itself as next hop instead of an ordinary physical underlay path, and decapsulation counters stop increasing.), restore the last approved safe network state and reassess gre route recursion creates a transport forwarding loop. The current change 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.
Question 360
A fictional Junos service-provider engineer encounters this scenario: A provider enables SR-MPLS in a core area but newly commissioned router loopbacks are not reachable through the intended shortest-path LSP. Distinguishing evidence: IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration. Which bounded approval scope avoids unintended changes to other provider or customer services?
Answer and Explanation
Correct Answer: C
A separate release decision would approve only the bounded change (Inspect the label forwarding information base, push-swap-pop behavior and corresponding tunnel state on each relevant hop.) after independently checking (The expected label entry and forwarding action appear at the designated hop and end-to-end customer traffic crosses the intended LSP.), without quietly widening the provider or customer network scope. It does not match the current change: Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy.
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 IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration and Node SID and relevant label entries agree across the intended nodes and measured transport follows the computed shortest path, respectively.
The bounded proposal is: Approve only the bounded change (Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy.) after independently checking (Node SID and relevant label entries agree across the intended nodes and measured transport follows the computed shortest path.), without quietly widening the provider or customer network scope. The separate acceptance measure remains: Node SID and relevant label entries agree across the intended nodes and measured transport follows the computed shortest path.
A separate release decision would approve only the bounded change (Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints.) after independently checking (The correct outer source-destination pair appears in captures and inner tunnel routes carry only the intended authorized traffic.), without quietly widening the provider or customer network scope. It does not match the current change: Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests
- 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)
- Juniper JN0-364 Practice Test 36 - 10 Questions (Last Reviewed 14-Oct-2026)
- Juniper JN0-364 Practice Test 37 - 10 Questions (Last Reviewed 13-Oct-2026)
- Juniper JN0-364 Practice Test 38 - 10 Questions (Last Reviewed 12-Oct-2026)