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 31
Question 300
A fictional Junos service-provider engineer encounters this scenario: A provider switching ring is designed to use different forwarding paths for two service VLAN groups but both services unexpectedly select one blocked uplink. Distinguishing evidence: MSTP instance membership and region parameters show the second VLAN mapped into the first spanning-tree instance and mismatched neighboring regional 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 (Validate interface family inet6, OSPFv3 topology and policy controlling IPv6 reachability before modifying the relevant scope.) after independently checking (The advertised customer IPv6 prefix installs in the intended table and a scoped IPv6 path test completes with correct next-hop resolution.), without quietly widening the provider or customer network scope. It does not match the current change: Confirm the authorized MSTP region, instance mappings and topology design, then align the relevant VLAN-to-instance definitions across participants.
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 MSTP instance membership and region parameters show the second VLAN mapped into the first spanning-tree instance and mismatched neighboring regional configuration and Per-instance operational port states match approved paths and both service VLAN groups retain loop-free reachability during a controlled link failure, respectively.
The bounded proposal is: 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 separate acceptance measure remains: Per-instance operational port states match approved paths and both service VLAN groups retain loop-free reachability during a controlled link failure.
A separate release decision would approve only the bounded change (Validate whether the port must be a genuine edge-facing endpoint and preserve or redesign BPDU protection under approved topology changes.) after independently checking (The approved access segment forwards safely while a repeat unauthorized BPDU test triggers the intended control with an audit trail.), without quietly widening the provider or customer network scope. It does not match the current change: Confirm the authorized MSTP region, instance mappings and topology design, then align the relevant VLAN-to-instance definitions across participants.
Question 301
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 specific bounded Junos routing or switching correction best addresses this service-provider issue?
Answer and Explanation
Correct Answer: D
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: Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable. The more targeted correction is: Inspect spanning-tree interface states, alternate paths and convergence behavior and tune only supported Layer 2 features within the validated topology.
Another proposed action is: Verify label distribution source, FEC identity and session state on adjacent routers, and correct the scoped label protocol fault through normal change control. It targets a different dependency; the evidence here is Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable.
Another option proposes: Validate whether the port must be a genuine edge-facing endpoint and preserve or redesign BPDU protection under approved topology changes. The specific correction is: Inspect spanning-tree interface states, alternate paths and convergence behavior and tune only supported Layer 2 features within the validated topology. The deciding evidence is: Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable.
The observed condition is: Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable. This calls for the scoped change: Inspect spanning-tree interface states, alternate paths and convergence behavior and tune only supported Layer 2 features within the validated topology. The acceptance measure is: A link failover test shows stable alternate Layer 2 forwarding without persistent loops and unchanged unrelated BGP routing.
Question 302
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. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?
Answer and Explanation
Correct Answer: C
This other option describes: 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 problem to explain is different: Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable.
Another proposed finding is: RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge. It is not the recorded discriminator, which is Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable.
Consider this evidence: Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable. The applicable explanation is: RSTP convergence depends on port roles, BPDU exchange and a loop-free alternate topology. The matching response is: Inspect spanning-tree interface states, alternate paths and convergence behavior and tune only supported Layer 2 features within the validated topology.
Another alternative would address Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error as decisive. The actual evidence in this case is Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable.
Question 303
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 Junos networking principle best explains the relevant engineering decision?
Answer and Explanation
Correct Answer: C
The competing option invokes: MSTP carries multiple VLANs in controlled spanning-tree instances and requires consistent region configuration. Evidence for this case: MSTP instance membership and region parameters show the second VLAN mapped into the first spanning-tree instance and mismatched neighboring regional configuration. The present evidence is: Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable. The case-relevant principle is: RSTP convergence depends on port roles, BPDU exchange and a loop-free alternate topology.
That principle concerns another fact pattern: 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. Here the key fact is: Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable.
RSTP convergence depends on port roles, BPDU exchange and a loop-free alternate topology. The recorded evidence is: Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable. The corresponding action is: Inspect spanning-tree interface states, alternate paths and convergence behavior and tune only supported Layer 2 features within the validated topology.
This alternative invokes: 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. The governing distinction for the recorded case is RSTP convergence depends on port roles, BPDU exchange and a loop-free alternate topology.
Question 304
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. Intended bounded correction: Inspect spanning-tree interface states, alternate paths and convergence behavior and tune only supported Layer 2 features within the validated topology. Which independently verifiable test best demonstrates the intended correction worked?
Answer and Explanation
Correct Answer: D
A different option checks: Per-instance operational port states match approved paths and both service VLAN groups retain loop-free reachability during a controlled link failure. The case-specific acceptance condition is instead a link failover test shows stable alternate Layer 2 forwarding without persistent loops and unchanged unrelated BGP routing.
Passing that test would not establish resolution of the stated issue. The relevant proof is: A link failover test shows stable alternate Layer 2 forwarding without persistent loops and unchanged unrelated BGP routing.
That result would assess another condition: The provider bridge remains legitimate root and a controlled superior-BPDU test is contained without permanent loop formation. The correct criterion is directly linked to the finding: Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable.
A link failover test shows stable alternate Layer 2 forwarding without persistent loops and unchanged unrelated BGP routing. This verifies the required result rather than merely stating the action; the original issue was Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable.
Question 305
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 material service-availability, routing, switching or security risk most directly needs control?
Answer and Explanation
Correct Answer: C
This limitation concerns another setting: Unrestricted changes to every bridge priority can create wide reconvergence and uncontrolled root migration. The observed facts here make a different caution decisive: Treating every interruption as a routing protocol failure can destabilize healthy control planes and leave a Layer 2 root cause unresolved.
Another caution is: Changing IPv6 routes alone cannot repair an unreachable outer IPv4 encapsulation endpoint. The key risk in this case is: Treating every interruption as a routing protocol failure can destabilize healthy control planes and leave a Layer 2 root cause unresolved.
The risk to retain is: Treating every interruption as a routing protocol failure can destabilize healthy control planes and leave a Layer 2 root cause unresolved. The original evidence is Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable; widening the change beyond it is not justified.
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: Treating every interruption as a routing protocol failure can destabilize healthy control planes and leave a Layer 2 root cause unresolved.
Question 306
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 focused investigation is the most useful before modifying the network configuration?
Answer and Explanation
Correct Answer: D
Another investigation would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge. It does not directly establish the reported condition: Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable.
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: Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable.
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 Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable. The focused check here is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable.
The current finding is Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable. The specific pre-change check is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable. Use it to distinguish the problem from an unrelated symptom.
Question 307
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 controlled operational implementation sequence best protects the related provider service?
Answer and Explanation
Correct Answer: D
Another possible combination is: First verify the observed failure (RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge.); review and authorize the bounded correction (Verify the intended root and edge-port topology, then apply supported root protection on the authorized boundary and restore correct bridge priority.); then independently verify the intended outcome (The provider bridge remains legitimate root and a controlled superior-BPDU test is contained without permanent loop formation.) before production rollout. The current record instead supports Inspect spanning-tree interface states, alternate paths and convergence behavior and tune only supported Layer 2 features within the validated topology, verified by a link failover test shows stable alternate Layer 2 forwarding without persistent loops and unchanged unrelated BGP routing.
Another potential sequence is: First verify the observed failure (MSTP instance membership and region parameters show the second VLAN mapped into the first spanning-tree instance and mismatched neighboring regional configuration.); review and authorize the bounded correction (Confirm the authorized MSTP region, instance mappings and topology design, then align the relevant VLAN-to-instance definitions across participants.); then independently verify the intended outcome (Per-instance operational port states match approved paths and both service VLAN groups retain loop-free reachability during a controlled link failure.) before production rollout. It has no direct link to the distinguishing evidence: Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable.
Another action-and-check pairing is: First verify the observed failure (OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope.); review and authorize the bounded correction (Validate interface family inet6, OSPFv3 topology and policy controlling IPv6 reachability before modifying the relevant scope.); then independently verify the intended outcome (The advertised customer IPv6 prefix installs in the intended table and a scoped IPv6 path test completes with correct next-hop resolution.) before production rollout. The evidence here is Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable. The required action and proof are Inspect spanning-tree interface states, alternate paths and convergence behavior and tune only supported Layer 2 features within the validated topology and a link failover test shows stable alternate Layer 2 forwarding without persistent loops and unchanged unrelated BGP routing.
The correction is Inspect spanning-tree interface states, alternate paths and convergence behavior and tune only supported Layer 2 features within the validated topology. The matching proof is a link failover test shows stable alternate Layer 2 forwarding without persistent loops and unchanged unrelated BGP routing. Both address the finding that Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable.
Question 308
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 set of evidence, limited change and independent validation best justifies authorization?
Answer and Explanation
Correct Answer: A
The bounded proposal is: Observed evidence (Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable.), limited correction (Inspect spanning-tree interface states, alternate paths and convergence behavior and tune only supported Layer 2 features within the validated topology.), independently measurable result (A link failover test shows stable alternate Layer 2 forwarding without persistent loops and unchanged unrelated BGP routing.). The separate acceptance measure remains: A link failover test shows stable alternate Layer 2 forwarding without persistent loops and unchanged unrelated BGP routing.
Another approval package concerns: 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 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.
An alternative release decision is: Observed evidence (MAC learning within the broadcast domain is healthy while the IRB logical interface or VLAN-to-IRB binding is missing or mapped to another tenant VLAN.), limited correction (Check the VLAN's Layer 3 interface relationship and correct the scoped IRB binding, address family and eligibility.), independently measurable result (Hosts in the specified VLAN reach their authorized gateway while isolation and route selection for other VLANs remain intact.). It does not match the current change: Inspect spanning-tree interface states, alternate paths and convergence behavior and tune only supported Layer 2 features within the validated topology.
Another approval action is: Observed evidence (Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error.), limited correction (Validate whether the port must be a genuine edge-facing endpoint and preserve or redesign BPDU protection under approved topology changes.), independently measurable result (The approved access segment forwards safely while a repeat unauthorized BPDU test triggers the intended control with an audit trail.). 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.
Question 309
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. If the change fails its expected acceptance test, which controlled recovery approach is most appropriate?
Answer and Explanation
Correct Answer: A
A recovery option is to pause changes, preserve the differentiating evidence (Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable.), restore the last approved safe network state and reassess rstp convergence is blamed on an unrelated route policy. The intended change was Inspect spanning-tree interface states, alternate paths and convergence behavior and tune only supported Layer 2 features within the validated topology, and acceptance must still be judged against a link failover test shows stable alternate Layer 2 forwarding without persistent loops and unchanged unrelated BGP routing.
Another fallback concerns pausing changes, preserve the differentiating evidence (Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding.), restore the last approved safe network state and reassess access port is accidentally configured to carry multiple tagged services. The current change concerns Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable.
Another recovery route would pause 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. It does not preserve the condition of this case: Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable. The bounded fallback is: Pause changes, preserve the differentiating evidence (Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable.), restore the last approved safe network state and reassess rstp convergence is blamed on an unrelated route policy.
Another option proposes: Pause 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. Its assumptions differ from the observed failure; the appropriate recovery is: Pause changes, preserve the differentiating evidence (Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable.), restore the last approved safe network state and reassess rstp convergence is blamed on an unrelated route policy.
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.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests
- Juniper JN0-364 Practice Test 29 - 10 Questions (Last Reviewed 21-Oct-2026)
- 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)