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 32
Question 310
A fictional Junos service-provider engineer encounters this scenario: A transport customer observes a short Ethernet outage during a switch uplink failure and an engineer plans to change upstream BGP timers to improve restoration. Distinguishing evidence: Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable. Which bounded approval scope avoids unintended changes to other provider or customer services?
Answer and Explanation
Correct Answer: B
Another proposed approval would approve only the bounded change (Confirm both peers' approved IPv6 unicast family configuration and import/export policies before enabling the specific family.) after independently checking (IPv6 routes appear only in the authorized routing tables and scoped IPv6 forwarding succeeds without altering existing IPv4 policy.), without quietly widening the provider or customer network scope. The present scope must instead be justified by Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable.
The bounded proposal is: Approve only the bounded change (Inspect spanning-tree interface states, alternate paths and convergence behavior and tune only supported Layer 2 features within the validated topology.) after independently checking (A link failover test shows stable alternate Layer 2 forwarding without persistent loops and unchanged unrelated BGP routing.), without quietly widening the provider or customer network scope. The separate acceptance measure remains: A link failover test shows stable alternate Layer 2 forwarding without persistent loops and unchanged unrelated BGP routing.
An alternative approval would approve only the bounded change (Confirm the authorized MSTP region, instance mappings and topology design, then align the relevant VLAN-to-instance definitions across participants.) after independently checking (Per-instance operational port states match approved paths and both service VLAN groups retain loop-free reachability during a controlled link failure.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable and a link failover test shows stable alternate Layer 2 forwarding without persistent loops and unchanged unrelated BGP routing, respectively.
Another proposed 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 present scope must instead be justified by Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable.
Question 311
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 specific bounded Junos routing or switching correction best addresses this service-provider issue?
Answer and Explanation
Correct Answer: C
Another proposed action is: Confirm the authorized MSTP region, instance mappings and topology design, then align the relevant VLAN-to-instance definitions across participants. That does not directly address the observed condition: The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped. The more targeted correction is: Check LDP session transport, adjacency and matching labeled next hops before choosing a narrow protocol or underlay correction.
Another proposed action is: Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy. It targets a different dependency; the evidence here is the underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped.
The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped. LDP advertises label bindings and requires appropriate transport and forwarding continuity for labeled paths. The appropriate response is: Check LDP session transport, adjacency and matching labeled next hops before choosing a narrow protocol or underlay correction. Confirm it with: LDP neighbors and label bindings recover for the intended FEC and payload forwarding resumes over the authorized LSP.
That alternative concerns: Compare reserved path constraints and actual underlay topology, then update the approved explicit route and resource availability before signaling again. The relevant evidence is the underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped. The corresponding fix is: Check LDP session transport, adjacency and matching labeled next hops before choosing a narrow protocol or underlay correction.
Question 312
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. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?
Answer and Explanation
Correct Answer: D
Another piece of evidence concerns the route table has the destination IP, but MPLS forwarding-table inspection lacks the expected incoming label operation on the affected transit router. The current incident instead shows: The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped. This distinction supports the action: Check LDP session transport, adjacency and matching labeled next hops before choosing a narrow protocol or underlay correction.
Another alternative would address RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge as decisive. The actual evidence in this case is the underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped.
This other option describes: 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 problem to explain is different: The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped.
The record points to the underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped. After confirming the clue, the appropriate response is: Check LDP session transport, adjacency and matching labeled next hops before choosing a narrow protocol or underlay correction.
Question 313
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 Junos networking principle best explains the relevant engineering decision?
Answer and Explanation
Correct Answer: A
LDP advertises label bindings and requires appropriate transport and forwarding continuity for labeled paths. The recorded evidence is: The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped. The corresponding action is: Check LDP session transport, adjacency and matching labeled next hops before choosing a narrow protocol or underlay correction.
This alternative invokes: 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. The governing distinction for the recorded case is LDP advertises label bindings and requires appropriate transport and forwarding continuity for labeled paths.
The competing option invokes: 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 is: The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped. The case-relevant principle is: LDP advertises label bindings and requires appropriate transport and forwarding continuity for labeled paths.
That principle concerns another fact pattern: RSVP signaling requires feasible path constraints and available resources, distinct from ordinary IP route reachability. Evidence for 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. Here the key fact is: The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped.
Question 314
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. Intended bounded correction: Check LDP session transport, adjacency and matching labeled next hops before choosing a narrow protocol or underlay correction. Which independently verifiable test best demonstrates the intended correction worked?
Answer and Explanation
Correct Answer: B
That result would assess another condition: The MPLS-aware path test and customer service probes agree on a working labeled route without masking unresolved transport problems. The correct criterion is directly linked to the finding: The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped.
LDP neighbors and label bindings recover for the intended FEC and payload forwarding resumes over the authorized LSP. This verifies the required result rather than merely stating the action; the original issue was the underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped.
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 LDP neighbors and label bindings recover for the intended FEC and payload forwarding resumes over the authorized LSP.
Passing that test would not establish resolution of the stated issue. The relevant proof is: LDP neighbors and label bindings recover for the intended FEC and payload forwarding resumes over the authorized LSP.
Question 315
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 material service-availability, routing, switching or security risk most directly needs control?
Answer and Explanation
Correct Answer: D
Another emphasis concerns: Changing IPv6 routes alone cannot repair an unreachable outer IPv4 encapsulation endpoint. The current change is Check LDP session transport, adjacency and matching labeled next hops before choosing a narrow protocol or underlay correction; the material limitation is a reachable IP destination does not prove that the MPLS labeled data path has an active next-hop binding.
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 reachable IP destination does not prove that the MPLS labeled data path has an active next-hop binding.
Another caution is: Conflating underlay IP connectivity and labeled LSP health delays recovery of provider services. The key risk in this case is: A reachable IP destination does not prove that the MPLS labeled data path has an active next-hop binding.
A reachable IP destination does not prove that the MPLS labeled data path has an active next-hop binding. That boundary protects the documented change, Check LDP session transport, adjacency and matching labeled next hops before choosing a narrow protocol or underlay correction, from introducing an unrelated problem.
Question 316
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 focused investigation is the most useful before modifying the network configuration?
Answer and Explanation
Correct Answer: D
Another check 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. The case observation to isolate is the underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped. The focused check here is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped.
Another investigation would compare active Junos routing, protocol and forwarding displays with this differentiating observed 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. It does not directly establish the reported condition: The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped.
That check concerns a different signal: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops. The case-relevant check is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped.
The focused investigation should compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped. It is tied to the observed evidence: The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped. It tests the conditions for this response: Check LDP session transport, adjacency and matching labeled next hops before choosing a narrow protocol or underlay correction.
Question 317
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 controlled operational implementation sequence best protects the related provider service?
Answer and Explanation
Correct Answer: A
The case evidence indicates: The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped. Apply the scoped action: Check LDP session transport, adjacency and matching labeled next hops before choosing a narrow protocol or underlay correction. Confirm its effect independently: LDP neighbors and label bindings recover for the intended FEC and payload forwarding resumes over the authorized LSP.
An alternative plan is: First verify the observed failure (The route table has the destination IP, but MPLS forwarding-table inspection lacks the expected incoming label operation on the affected transit router.); review and authorize the bounded correction (Inspect the label forwarding information base, push-swap-pop behavior and corresponding tunnel state on each relevant hop.); then independently verify the intended outcome (The expected label entry and forwarding action appear at the designated hop and end-to-end customer traffic crosses the intended LSP.) before production rollout. It does not test the case-specific condition: The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped.
Another possible combination is: First verify the observed failure (Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.); review and authorize the bounded correction (Verify label distribution source, FEC identity and session state on adjacent routers, and correct the scoped label protocol fault through normal change control.); then independently verify the intended outcome (The neighboring label bindings and forwarding operations agree and both control-plane and data-plane path verification succeed.) before production rollout. The current record instead supports Check LDP session transport, adjacency and matching labeled next hops before choosing a narrow protocol or underlay correction, verified by LDP neighbors and label bindings recover for the intended FEC and payload forwarding resumes over the authorized LSP.
Another potential sequence is: First verify the observed failure (Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable.); review and authorize the bounded correction (Inspect spanning-tree interface states, alternate paths and convergence behavior and tune only supported Layer 2 features within the validated topology.); then independently verify the intended outcome (A link failover test shows stable alternate Layer 2 forwarding without persistent loops and unchanged unrelated BGP routing.) before production rollout. It has no direct link to the distinguishing evidence: The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped.
Question 318
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 set of evidence, limited change and independent validation best justifies authorization?
Answer and Explanation
Correct Answer: A
The approval decision should consider the underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped. The specific proposal is: Observed evidence (The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped.), limited correction (Check LDP session transport, adjacency and matching labeled next hops before choosing a narrow protocol or underlay correction.), independently measurable result (LDP neighbors and label bindings recover for the intended FEC and payload forwarding resumes over the authorized LSP.). Its measurable outcome is: LDP neighbors and label bindings recover for the intended FEC and payload forwarding resumes over the authorized LSP.
Another approval action is: Observed evidence (The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.), limited correction (Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints.), independently measurable result (The correct outer source-destination pair appears in captures and inner tunnel routes carry only the intended authorized traffic.). 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 approval package concerns: 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 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.
An alternative release decision is: 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.), limited correction (Inspect the label forwarding information base, push-swap-pop behavior and corresponding tunnel state on each relevant hop.), independently measurable result (The expected label entry and forwarding action appear at the designated hop and end-to-end customer traffic crosses the intended LSP.). 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.
Question 319
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. If the change fails its expected acceptance test, which controlled recovery approach is most appropriate?
Answer and Explanation
Correct Answer: A
If the change fails acceptance, the bounded recovery is: Pause 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 case-specific risk is a reachable IP destination does not prove that the MPLS labeled data path has an active next-hop binding. The original evidence remains: The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped.
Another option proposes: Pause changes, preserve the differentiating evidence (The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP.), restore the last approved safe network state and reassess php behavior makes a packet appear unlabeled before the destination. Its assumptions differ from the observed failure; the appropriate recovery is: Pause 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.
Another fallback concerns pausing changes, preserve the differentiating evidence (Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error.), restore the last approved safe network state and reassess bpdu protection disables an unexpected access port. The current change concerns the underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped.
Another recovery route would 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. It does not preserve the condition of this case: The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped. The bounded fallback is: Pause 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.
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.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests
- Juniper JN0-364 Practice Test 30 - 10 Questions (Last Reviewed 20-Oct-2026)
- 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)