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 28
Question 270
A fictional Junos service-provider engineer encounters this scenario: A multi-tenant service provider reuses the same customer VLAN number across separate clients but a new aggregation configuration unexpectedly leaks broadcast traffic between them. Distinguishing evidence: Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts. Which bounded approval scope avoids unintended changes to other provider or customer services?
Answer and Explanation
Correct Answer: B
A separate release decision would approve only the bounded change (Verify the handoff contract and bridge interface port mode, then restore only the intended tag treatment and VLAN membership.) after independently checking (The customer CE exchanges untagged frames successfully without gaining access to other wholesale service VLANs.), without quietly widening the provider or customer network scope. It does not match the current change: Separate the tenant virtual switches and bridge-domain scopes while preserving the contracted tag translation on each handoff.
The change-control boundary is: Approve only the bounded change (Separate the tenant virtual switches and bridge-domain scopes while preserving the contracted tag translation on each handoff.) after independently checking (Broadcast and unknown-unicast tests remain isolated to each customer and independent service port traffic follows expected boundaries.), without quietly widening the provider or customer network scope. The evidence for this scope is Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts.
Another proposed approval would approve only the bounded change (Check accepted service VLAN and inner-tag preservation requirements, then correct the intended outer tag translation or service membership.) after independently checking (Customer inner VLAN traffic crosses the agreed provider service path with the expected outer encapsulation and isolation from unrelated customers.), without quietly widening the provider or customer network scope. The present scope must instead be justified by Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts.
A separate release decision would approve only the bounded change (Apply a precise export filter and route-policy tests for public prefixes, then confirm rejected customer-only routes stay internal.) after independently checking (Upstream advertised-route output contains only approved prefixes and the private customer destination remains available in its intended instance.), without quietly widening the provider or customer network scope. It does not match the current change: Separate the tenant virtual switches and bridge-domain scopes while preserving the contracted tag translation on each handoff.
Question 271
A fictional Junos service-provider engineer encounters this scenario: A provider-controlled Layer 2 aggregation VLAN experiences traffic instability immediately after a customer switch with a very low bridge priority is connected. Distinguishing evidence: RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge. Which specific bounded Junos routing or switching correction best addresses this service-provider issue?
Answer and Explanation
Correct Answer: C
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. That does not directly address the observed condition: RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge. The more targeted correction is: Verify the intended root and edge-port topology, then apply supported root protection on the authorized boundary and restore correct bridge priority.
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. It targets a different dependency; the evidence here is RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge.
The issue turns on RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge. The relevant rule is that Root protection and bridge priority govern safe spanning-tree root election at controlled boundaries. The targeted correction is: Verify the intended root and edge-port topology, then apply supported root protection on the authorized boundary and restore correct bridge priority.
That alternative concerns: Validate whether the port must be a genuine edge-facing endpoint and preserve or redesign BPDU protection under approved topology changes. The relevant evidence is RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge. The corresponding fix is: Verify the intended root and edge-port topology, then apply supported root protection on the authorized boundary and restore correct bridge priority.
Question 272
A fictional Junos service-provider engineer encounters this scenario: A provider-controlled Layer 2 aggregation VLAN experiences traffic instability immediately after a customer switch with a very low bridge priority is connected. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?
Answer and Explanation
Correct Answer: D
Another piece of evidence concerns MAC forwarding tables on the access switch show the customer source learned on an unexpected access port and no destination learning for the intended bridge domain. The current incident instead shows: RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge. This distinction supports the action: Verify the intended root and edge-port topology, then apply supported root protection on the authorized boundary and restore correct bridge priority.
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 RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge.
This other option describes: Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable. The problem to explain is different: RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge.
The record points to RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge. After confirming the clue, the appropriate response is: Verify the intended root and edge-port topology, then apply supported root protection on the authorized boundary and restore correct bridge priority.
Question 273
A fictional Junos service-provider engineer encounters this scenario: A provider-controlled Layer 2 aggregation VLAN experiences traffic instability immediately after a customer switch with a very low bridge priority is connected. Distinguishing evidence: RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge. Which Junos networking principle best explains the relevant engineering decision?
Answer and Explanation
Correct Answer: C
A different principle is: LDP and other MPLS signaling must maintain consistent per-hop label bindings for each forwarding equivalence class. Evidence for this case: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment. The present evidence, however, is RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge. The relevant rule is: Root protection and bridge priority govern safe spanning-tree root election at controlled boundaries.
This alternative 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 governing distinction for the recorded case is Root protection and bridge priority govern safe spanning-tree root election at controlled boundaries.
The observed evidence is: RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge. The governing principle is: Root protection and bridge priority govern safe spanning-tree root election at controlled boundaries. Consequently, the targeted action is: Verify the intended root and edge-port topology, then apply supported root protection on the authorized boundary and restore correct bridge priority.
That principle concerns another fact pattern: RSTP convergence depends on port roles, BPDU exchange and a loop-free alternate topology. Evidence for this case: Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable. Here the key fact is: RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge.
Question 274
A fictional Junos service-provider engineer encounters this scenario: A provider-controlled Layer 2 aggregation VLAN experiences traffic instability immediately after a customer switch with a very low bridge priority is connected. Intended bounded correction: Verify the intended root and edge-port topology, then apply supported root protection on the authorized boundary and restore correct bridge priority. Which independently verifiable test best demonstrates the intended correction worked?
Answer and Explanation
Correct Answer: C
That result would assess another condition: The customer CE exchanges untagged frames successfully without gaining access to other wholesale service VLANs. The correct criterion is directly linked to the finding: RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge.
Another proposed result is: A link failover test shows stable alternate Layer 2 forwarding without persistent loops and unchanged unrelated BGP routing. It would not independently establish the required outcome: The provider bridge remains legitimate root and a controlled superior-BPDU test is contained without permanent loop formation.
The expected outcome is the provider bridge remains legitimate root and a controlled superior-BPDU test is contained without permanent loop formation. It links the scoped action to the documented condition: RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge.
Passing that test would not establish resolution of the stated issue. The relevant proof is: The provider bridge remains legitimate root and a controlled superior-BPDU test is contained without permanent loop formation.
Question 275
A fictional Junos service-provider engineer encounters this scenario: A provider-controlled Layer 2 aggregation VLAN experiences traffic instability immediately after a customer switch with a very low bridge priority is connected. Distinguishing evidence: RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge. Which material service-availability, routing, switching or security risk most directly needs control?
Answer and Explanation
Correct Answer: C
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: Unrestricted changes to every bridge priority can create wide reconvergence and uncontrolled root migration.
Another caution is: Treating every interruption as a routing protocol failure can destabilize healthy control planes and leave a Layer 2 root cause unresolved. The key risk in this case is: Unrestricted changes to every bridge priority can create wide reconvergence and uncontrolled root migration.
The relevant boundary is: Unrestricted changes to every bridge priority can create wide reconvergence and uncontrolled root migration. It matters when applying the specific response: Verify the intended root and edge-port topology, then apply supported root protection on the authorized boundary and restore correct bridge priority.
This limitation concerns another setting: Misaligned port tagging can create a service outage or expose unrelated VLANs through an overly broad trunk. The observed facts here make a different caution decisive: Unrestricted changes to every bridge priority can create wide reconvergence and uncontrolled root migration.
Question 276
A fictional Junos service-provider engineer encounters this scenario: A provider-controlled Layer 2 aggregation VLAN experiences traffic instability immediately after a customer switch with a very low bridge priority is connected. Distinguishing evidence: RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge. Which focused investigation is the most useful before modifying the network configuration?
Answer and Explanation
Correct Answer: A
The current finding is RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge. The specific pre-change check is: 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. Use it to distinguish the problem from an unrelated symptom.
That check concerns a different signal: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error. The case-relevant check is: 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.
Another check would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP. The case observation to isolate is RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge. The focused check here is: 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.
Another investigation would 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. It does not directly establish the reported condition: RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge.
Question 277
A fictional Junos service-provider engineer encounters this scenario: A provider-controlled Layer 2 aggregation VLAN experiences traffic instability immediately after a customer switch with a very low bridge priority is connected. Distinguishing evidence: RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge. Which controlled operational implementation sequence best protects the related provider service?
Answer and Explanation
Correct Answer: D
Another action-and-check pairing 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. The evidence here is RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge. The required action and proof are Verify the intended root and edge-port topology, then apply supported root protection on the authorized boundary and restore correct bridge priority and the provider bridge remains legitimate root and a controlled superior-BPDU test is contained without permanent loop formation.
An alternative plan 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 does not test the case-specific condition: RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge.
Another possible combination 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. The current record instead supports Verify the intended root and edge-port topology, then apply supported root protection on the authorized boundary and restore correct bridge priority, verified by the provider bridge remains legitimate root and a controlled superior-BPDU test is contained without permanent loop formation.
The starting point is RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge. The proposed action and its separate check are Verify the intended root and edge-port topology, then apply supported root protection on the authorized boundary and restore correct bridge priority and the provider bridge remains legitimate root and a controlled superior-BPDU test is contained without permanent loop formation, respectively.
Question 278
A fictional Junos service-provider engineer encounters this scenario: A provider-controlled Layer 2 aggregation VLAN experiences traffic instability immediately after a customer switch with a very low bridge priority is connected. Distinguishing evidence: RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge. Which set of evidence, limited change and independent validation best justifies authorization?
Answer and Explanation
Correct Answer: A
The bounded proposal is: Observed evidence (RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge.), limited correction (Verify the intended root and edge-port topology, then apply supported root protection on the authorized boundary and restore correct bridge priority.), independently measurable result (The provider bridge remains legitimate root and a controlled superior-BPDU test is contained without permanent loop formation.). The separate acceptance measure remains: The provider bridge remains legitimate root and a controlled superior-BPDU test is contained without permanent loop formation.
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 RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge.
An alternative release decision 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.). It does not match the current change: Verify the intended root and edge-port topology, then apply supported root protection on the authorized boundary and restore correct bridge priority.
Another approval action is: Observed evidence (MSTP instance membership and region parameters show the second VLAN mapped into the first spanning-tree instance and mismatched neighboring regional configuration.), limited correction (Confirm the authorized MSTP region, instance mappings and topology design, then align the relevant VLAN-to-instance definitions across participants.), independently measurable result (Per-instance operational port states match approved paths and both service VLAN groups retain loop-free reachability during a controlled link failure.). The relevant evidence and acceptance are RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge and the provider bridge remains legitimate root and a controlled superior-BPDU test is contained without permanent loop formation, respectively.
Question 279
A fictional Junos service-provider engineer encounters this scenario: A provider-controlled Layer 2 aggregation VLAN experiences traffic instability immediately after a customer switch with a very low bridge priority is connected. Distinguishing evidence: RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge. If the change fails its expected acceptance test, which controlled recovery approach is most appropriate?
Answer and Explanation
Correct Answer: D
Another option proposes: 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. Its assumptions differ from the observed failure; the appropriate recovery is: 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.
Another fallback concerns pausing changes, preserve the differentiating evidence (OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope.), restore the last approved safe network state and reassess ospfv3 adjacency is healthy but destination ipv6 route is missing. The current change concerns RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge.
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: RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge. The bounded fallback is: 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.
A recovery option is to 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. The intended change was Verify the intended root and edge-port topology, then apply supported root protection on the authorized boundary and restore correct bridge priority, and acceptance must still be judged against the provider bridge remains legitimate root and a controlled superior-BPDU test is contained without permanent loop formation.
Question 280
A fictional Junos service-provider engineer encounters this scenario: A provider-controlled Layer 2 aggregation VLAN experiences traffic instability immediately after a customer switch with a very low bridge priority is connected. Distinguishing evidence: RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge. Which bounded approval scope avoids unintended changes to other provider or customer services?
Answer and Explanation
Correct Answer: A
The change-control boundary is: 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 evidence for this scope is RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge.
A separate release decision would approve only the bounded change (Confirm expected label advertisement and pop operation at the penultimate hop rather than forcing unnecessary labels through every device.) after independently checking (Captured traffic and destination forwarding demonstrate correct reachability with expected label disposition at each hop.), without quietly widening the provider or customer network scope. It does not match the current change: Verify the intended root and edge-port topology, then apply supported root protection on the authorized boundary and restore correct bridge priority.
An alternative approval 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. The relevant evidence and acceptance are RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge and the provider bridge remains legitimate root and a controlled superior-BPDU test is contained without permanent loop formation, respectively.
Another proposed approval would 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 present scope must instead be justified by RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests
- Juniper JN0-364 Practice Test 26 - 10 Questions (Last Reviewed 24-Oct-2026)
- Juniper JN0-364 Practice Test 27 - 10 Questions (Last Reviewed 23-Oct-2026)
- Juniper JN0-364 Practice Test 28 - 10 Questions (Last Reviewed 22-Oct-2026)
- 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)