Juniper JN0-364 Practice Test 29 - Prepaway
Practice Exams:

Pass Juniper JN0-364 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers!

30 Days Free Updates, Instant Download!

Verified By Experts
Premium File
$69.99 $76.99

JN0-364 Premium ETE File


  • Premium File 69 Questions & Answers. Last Update: Nov 17, 2026
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Juniper JN0-364 Practice Test 29

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?

  1. 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.
  2. 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.
  3. 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.
  4. 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.

Answer and Explanation

Correct Answer: A

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.

B.

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.

C.

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.

D.

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.

Question 281

A fictional Junos service-provider engineer encounters this scenario: An installer finds a customer-facing edge port disabled after attaching a small downstream Ethernet switch and assumes a damaged fiber transceiver. Distinguishing evidence: Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error. Which specific bounded Junos routing or switching correction best addresses this service-provider issue?

  1. Bounded remedy: Confirm the authorized MSTP region, instance mappings and topology design, then align the relevant VLAN-to-instance definitions across participants.
  2. Bounded remedy: Check accepted service VLAN and inner-tag preservation requirements, then correct the intended outer tag translation or service membership.
  3. Bounded remedy: Inspect spanning-tree interface states, alternate paths and convergence behavior and tune only supported Layer 2 features within the validated topology.
  4. Bounded remedy: Validate whether the port must be a genuine edge-facing endpoint and preserve or redesign BPDU protection under approved topology changes.

Answer and Explanation

Correct Answer: D

A.

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: Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error. The more targeted correction is: Validate whether the port must be a genuine edge-facing endpoint and preserve or redesign BPDU protection under approved topology changes.

B.

Another proposed action is: Check accepted service VLAN and inner-tag preservation requirements, then correct the intended outer tag translation or service membership. It targets a different dependency; the evidence here is Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error.

C.

Another option proposes: Inspect spanning-tree interface states, alternate paths and convergence behavior and tune only supported Layer 2 features within the validated topology. The specific correction is: Validate whether the port must be a genuine edge-facing endpoint and preserve or redesign BPDU protection under approved topology changes. The deciding evidence is: Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error.

D.

The evidence is Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error. The relevant principle is that Spanning-tree BPDU protection is a deliberate safety mechanism against unexpected bridge advertisements. The correction is: Validate whether the port must be a genuine edge-facing endpoint and preserve or redesign BPDU protection under approved topology changes. The separate success check is: The approved access segment forwards safely while a repeat unauthorized BPDU test triggers the intended control with an audit trail.

Question 282

A fictional Junos service-provider engineer encounters this scenario: An installer finds a customer-facing edge port disabled after attaching a small downstream Ethernet switch and assumes a damaged fiber transceiver. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?

  1. Differentiating observation: Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable.
  2. Differentiating observation: Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error.
  3. Differentiating observation: 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.
  4. Differentiating observation: RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge.

Answer and Explanation

Correct Answer: B

A.

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: Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error.

B.

The record points to Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error. After confirming the clue, the appropriate response is: Validate whether the port must be a genuine edge-facing endpoint and preserve or redesign BPDU protection under approved topology changes.

C.

Another piece of evidence concerns 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. The current incident instead shows: Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error. This distinction supports the action: Validate whether the port must be a genuine edge-facing endpoint and preserve or redesign BPDU protection under approved topology changes.

D.

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 Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error.

Question 283

A fictional Junos service-provider engineer encounters this scenario: An installer finds a customer-facing edge port disabled after attaching a small downstream Ethernet switch and assumes a damaged fiber transceiver. Distinguishing evidence: Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error. Which Junos networking principle best explains the relevant engineering decision?

  1. Applicable protocol principle: 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.
  2. Applicable protocol principle: Root protection and bridge priority govern safe spanning-tree root election at controlled boundaries. Evidence for this case: RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge.
  3. Applicable protocol principle: 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.
  4. Applicable protocol principle: 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.

Answer and Explanation

Correct Answer: C

A.

The competing option invokes: 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. The present evidence is: Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error. The case-relevant principle is: Spanning-tree BPDU protection is a deliberate safety mechanism against unexpected bridge advertisements.

B.

That principle concerns another fact pattern: Root protection and bridge priority govern safe spanning-tree root election at controlled boundaries. Evidence for this case: RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge. Here the key fact is: Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error.

C.

Spanning-tree BPDU protection is a deliberate safety mechanism against unexpected bridge advertisements. The recorded evidence is: Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error. The corresponding action is: Validate whether the port must be a genuine edge-facing endpoint and preserve or redesign BPDU protection under approved topology changes.

D.

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 Spanning-tree BPDU protection is a deliberate safety mechanism against unexpected bridge advertisements.

Question 284

A fictional Junos service-provider engineer encounters this scenario: An installer finds a customer-facing edge port disabled after attaching a small downstream Ethernet switch and assumes a damaged fiber transceiver. Intended bounded correction: Validate whether the port must be a genuine edge-facing endpoint and preserve or redesign BPDU protection under approved topology changes. Which independently verifiable test best demonstrates the intended correction worked?

  1. Independent verification: The approved access segment forwards safely while a repeat unauthorized BPDU test triggers the intended control with an audit trail.
  2. Independent verification: A link failover test shows stable alternate Layer 2 forwarding without persistent loops and unchanged unrelated BGP routing.
  3. Independent verification: Per-instance operational port states match approved paths and both service VLAN groups retain loop-free reachability during a controlled link failure.
  4. Independent verification: Broadcast and unknown-unicast tests remain isolated to each customer and independent service port traffic follows expected boundaries.

Answer and Explanation

Correct Answer: A

A.

The expected outcome is the approved access segment forwards safely while a repeat unauthorized BPDU test triggers the intended control with an audit trail. It links the scoped action to the documented condition: Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error.

B.

Passing that test would not establish resolution of the stated issue. The relevant proof is: The approved access segment forwards safely while a repeat unauthorized BPDU test triggers the intended control with an audit trail.

C.

That result would assess another condition: Per-instance operational port states match approved paths and both service VLAN groups retain loop-free reachability during a controlled link failure. The correct criterion is directly linked to the finding: Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error.

D.

Another proposed result is: Broadcast and unknown-unicast tests remain isolated to each customer and independent service port traffic follows expected boundaries. It would not independently establish the required outcome: The approved access segment forwards safely while a repeat unauthorized BPDU test triggers the intended control with an audit trail.

Question 285

A fictional Junos service-provider engineer encounters this scenario: An installer finds a customer-facing edge port disabled after attaching a small downstream Ethernet switch and assumes a damaged fiber transceiver. Distinguishing evidence: Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error. Which material service-availability, routing, switching or security risk most directly needs control?

  1. Meaningful operational caution: Blindly disabling BPDU protection on an untrusted edge can open the switching domain to loops and root manipulation.
  2. Meaningful operational caution: Treating every interruption as a routing protocol failure can destabilize healthy control planes and leave a Layer 2 root cause unresolved.
  3. Meaningful operational caution: An unrelated BGP policy adjustment cannot repair a Layer 2 forwarding-table error and may interrupt transit networks.
  4. Meaningful operational caution: Unrestricted changes to every bridge priority can create wide reconvergence and uncontrolled root migration.

Answer and Explanation

Correct Answer: A

A.

The relevant boundary is: Blindly disabling BPDU protection on an untrusted edge can open the switching domain to loops and root manipulation. It matters when applying the specific response: Validate whether the port must be a genuine edge-facing endpoint and preserve or redesign BPDU protection under approved topology changes.

B.

This limitation concerns another setting: Treating every interruption as a routing protocol failure can destabilize healthy control planes and leave a Layer 2 root cause unresolved. The observed facts here make a different caution decisive: Blindly disabling BPDU protection on an untrusted edge can open the switching domain to loops and root manipulation.

C.

Another caution is: An unrelated BGP policy adjustment cannot repair a Layer 2 forwarding-table error and may interrupt transit networks. The key risk in this case is: Blindly disabling BPDU protection on an untrusted edge can open the switching domain to loops and root manipulation.

D.

Another emphasis concerns: Unrestricted changes to every bridge priority can create wide reconvergence and uncontrolled root migration. The current change is Validate whether the port must be a genuine edge-facing endpoint and preserve or redesign BPDU protection under approved topology changes; the material limitation is Blindly disabling BPDU protection on an untrusted edge can open the switching domain to loops and root manipulation.

Question 286

A fictional Junos service-provider engineer encounters this scenario: An installer finds a customer-facing edge port disabled after attaching a small downstream Ethernet switch and assumes a damaged fiber transceiver. Distinguishing evidence: Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error. Which focused investigation is the most useful before modifying the network configuration?

  1. Focused Junos investigation: 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.
  2. Focused Junos investigation: 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.
  3. Focused Junos investigation: 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.
  4. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts.

Answer and Explanation

Correct Answer: C

A.

Another check would 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 case observation to isolate is Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error. The focused check here is: 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.

B.

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: Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error.

C.

The current finding is Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error. The specific pre-change check is: 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. Use it to distinguish the problem from an unrelated symptom.

D.

Another check would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts. The case observation to isolate is Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error. The focused check here is: 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.

Question 287

A fictional Junos service-provider engineer encounters this scenario: An installer finds a customer-facing edge port disabled after attaching a small downstream Ethernet switch and assumes a damaged fiber transceiver. Distinguishing evidence: Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error. Which controlled operational implementation sequence best protects the related provider service?

  1. Controlled engineering sequence: 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.
  2. Controlled engineering sequence: 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.
  3. Controlled engineering sequence: First verify the observed failure (Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error.); review and authorize the bounded correction (Validate whether the port must be a genuine edge-facing endpoint and preserve or redesign BPDU protection under approved topology changes.); then independently verify the intended outcome (The approved access segment forwards safely while a repeat unauthorized BPDU test triggers the intended control with an audit trail.) before production rollout.
  4. Controlled engineering sequence: 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.

Answer and Explanation

Correct Answer: C

A.

Another possible combination 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 current record instead supports Validate whether the port must be a genuine edge-facing endpoint and preserve or redesign BPDU protection under approved topology changes, verified by the approved access segment forwards safely while a repeat unauthorized BPDU test triggers the intended control with an audit trail.

B.

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: Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error.

C.

The case evidence indicates: Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error. Apply the scoped action: Validate whether the port must be a genuine edge-facing endpoint and preserve or redesign BPDU protection under approved topology changes. Confirm its effect independently: The approved access segment forwards safely while a repeat unauthorized BPDU test triggers the intended control with an audit trail.

D.

An alternative plan 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 does not test the case-specific condition: Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error.

Question 288

A fictional Junos service-provider engineer encounters this scenario: An installer finds a customer-facing edge port disabled after attaching a small downstream Ethernet switch and assumes a damaged fiber transceiver. Distinguishing evidence: Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error. Which set of evidence, limited change and independent validation best justifies authorization?

  1. Approval package: 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.).
  2. Approval package: 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.).
  3. Approval package: 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.).
  4. Approval package: observed evidence (Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.), limited correction (Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration.), independently measurable result (Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route.).

Answer and Explanation

Correct Answer: B

A.

An alternative release decision 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.). It does not match the current change: Validate whether the port must be a genuine edge-facing endpoint and preserve or redesign BPDU protection under approved topology changes.

B.

The change-control boundary 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 evidence for this scope is Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error.

C.

Another approval package concerns: 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 present scope must instead be justified by Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error.

D.

An alternative release decision is: Observed evidence (Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.), limited correction (Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration.), independently measurable result (Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route.). It does not match the current change: Validate whether the port must be a genuine edge-facing endpoint and preserve or redesign BPDU protection under approved topology changes.

Question 289

A fictional Junos service-provider engineer encounters this scenario: An installer finds a customer-facing edge port disabled after attaching a small downstream Ethernet switch and assumes a damaged fiber transceiver. Distinguishing evidence: Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error. If the change fails its expected acceptance test, which controlled recovery approach is most appropriate?

  1. If testing fails: pause changes, preserve the differentiating evidence (The route table has the destination IP, but MPLS forwarding-table inspection lacks the expected incoming label operation on the affected transit router.), restore the last approved safe network state and reassess mpls label lookup is confused with an ip route table entry.
  2. If testing fails: pause changes, preserve the differentiating evidence (MSTP instance membership and region parameters show the second VLAN mapped into the first spanning-tree instance and mismatched neighboring regional configuration.), restore the last approved safe network state and reassess mstp instance mapping creates an unexpected blocked path.
  3. If testing fails: 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.
  4. If testing fails: 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.

Answer and Explanation

Correct Answer: C

A.

Another recovery route would pause changes, preserve the differentiating evidence (The route table has the destination IP, but MPLS forwarding-table inspection lacks the expected incoming label operation on the affected transit router.), restore the last approved safe network state and reassess mpls label lookup is confused with an ip route table entry. It does not preserve the condition of this case: Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error. The bounded fallback is: 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.

B.

Another option proposes: Pause changes, preserve the differentiating evidence (MSTP instance membership and region parameters show the second VLAN mapped into the first spanning-tree instance and mismatched neighboring regional configuration.), restore the last approved safe network state and reassess mstp instance mapping creates an unexpected blocked path. Its assumptions differ from the observed failure; the appropriate recovery is: 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.

C.

A recovery option is to 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. The intended change was Validate whether the port must be a genuine edge-facing endpoint and preserve or redesign BPDU protection under approved topology changes, and acceptance must still be judged against the approved access segment forwards safely while a repeat unauthorized BPDU test triggers the intended control with an audit trail.

D.

Another recovery route would 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. It does not preserve the condition of this case: Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error. The bounded fallback is: 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.

Question 290

A fictional Junos service-provider engineer encounters this scenario: An installer finds a customer-facing edge port disabled after attaching a small downstream Ethernet switch and assumes a damaged fiber transceiver. Distinguishing evidence: Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error. Which bounded approval scope avoids unintended changes to other provider or customer services?

  1. 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.
  2. 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.
  3. 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.
  4. 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.

Answer and Explanation

Correct Answer: A

A.

The bounded proposal is: 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 separate acceptance measure remains: The approved access segment forwards safely while a repeat unauthorized BPDU test triggers the intended control with an audit trail.

B.

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 Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error.

C.

A separate release decision 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. It does not match the current change: Validate whether the port must be a genuine edge-facing endpoint and preserve or redesign BPDU protection under approved topology changes.

D.

An alternative approval 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. The relevant evidence and acceptance are Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error and the approved access segment forwards safely while a repeat unauthorized BPDU test triggers the intended control with an audit trail, respectively.

Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests