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 27
Question 260
A fictional Junos service-provider engineer encounters this scenario: A wholesale Layer 2 customer reports one-way Ethernet delivery even though upstream BGP peers are healthy on the transport provider edge. Distinguishing evidence: 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. Which bounded approval scope avoids unintended changes to other provider or customer services?
Answer and Explanation
Correct Answer: D
An alternative approval would approve only the bounded change (Verify 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 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 and Bidirectional test frames learn on the expected ports and remain within the authorized bridge domain without affecting route peers, respectively.
Another proposed approval would approve only the bounded change (Verify peering transport addresses, configured peer ASN, reachability and authentication, then correct only the approved BGP neighbor endpoint.) after independently checking (The expected external session reaches Established and exchanges only agreed IPv4 routes with stable uptime.), without quietly widening the provider or customer network scope. The present scope must instead be justified by 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.
A separate release decision 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. It does not match the current change: Validate VLAN and virtual-switch boundaries, physical member state and MAC learning before changing upstream BGP sessions.
The bounded proposal is: Approve only the bounded change (Validate VLAN and virtual-switch boundaries, physical member state and MAC learning before changing upstream BGP sessions.) after independently checking (Bidirectional test frames learn on the expected ports and remain within the authorized bridge domain without affecting route peers.), without quietly widening the provider or customer network scope. The separate acceptance measure remains: Bidirectional test frames learn on the expected ports and remain within the authorized bridge domain without affecting route peers.
Question 261
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 specific bounded Junos routing or switching correction best addresses this service-provider issue?
Answer and Explanation
Correct Answer: D
Another proposed action is: Check accepted service VLAN and inner-tag preservation requirements, then correct the intended outer tag translation or service membership. That does not directly address the observed condition: Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts. The more targeted correction is: Separate the tenant virtual switches and bridge-domain scopes while preserving the contracted tag translation on each handoff.
Another proposed action is: Verify the handoff contract and bridge interface port mode, then restore only the intended tag treatment and VLAN membership. It targets a different dependency; the evidence here is Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts.
Another option proposes: Investigate transport reliability, control-plane load and negotiated timer behavior before adjusting route filters or hold time. The specific correction is: Separate the tenant virtual switches and bridge-domain scopes while preserving the contracted tag translation on each handoff. The deciding evidence is: Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts.
The evidence for the issue is Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts. The matching step is: Separate the tenant virtual switches and bridge-domain scopes while preserving the contracted tag translation on each handoff. This follows the principle that Junos virtual-switch and bridge-domain scoping determine the actual Layer 2 forwarding boundary.
Question 262
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. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?
Answer and Explanation
Correct Answer: A
Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts. That fact identifies the relevant dependency, rather than a separate issue. Junos virtual-switch and bridge-domain scoping determine the actual Layer 2 forwarding boundary.
Another proposed finding is: 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. It is not the recorded discriminator, which is Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts.
Another piece of evidence concerns Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding. The current incident instead shows: Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts. This distinction supports the action: Separate the tenant virtual switches and bridge-domain scopes while preserving the contracted tag translation on each handoff.
Another alternative would address Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops as decisive. The actual evidence in this case is Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts.
Question 263
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 Junos networking principle best explains the relevant engineering decision?
Answer and Explanation
Correct Answer: B
The competing option invokes: Integrated routing and bridging requires correct VLAN membership and a corresponding L3 IRB interface. Evidence for this case: 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 present evidence is: Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts. The case-relevant principle is: Junos virtual-switch and bridge-domain scoping determine the actual Layer 2 forwarding boundary.
Junos virtual-switch and bridge-domain scoping determine the actual Layer 2 forwarding boundary. This distinction accounts for Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts; another unrelated mechanism would not address the same condition.
A different principle is: Provider bridging encapsulates customer VLAN traffic using an agreed service VLAN tag boundary. Evidence for this case: Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers. The present evidence, however, is Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts. The relevant rule is: Junos virtual-switch and bridge-domain scoping determine the actual Layer 2 forwarding boundary.
This alternative invokes: MPLS label-switched path tests diagnose forwarding beyond a generic IP connectivity probe. Evidence for this case: Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops. The governing distinction for the recorded case is Junos virtual-switch and bridge-domain scoping determine the actual Layer 2 forwarding boundary.
Question 264
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. Intended bounded correction: Separate the tenant virtual switches and bridge-domain scopes while preserving the contracted tag translation on each handoff. Which independently verifiable test best demonstrates the intended correction worked?
Answer and Explanation
Correct Answer: C
A different option checks: Bidirectional test frames learn on the expected ports and remain within the authorized bridge domain without affecting route peers. The case-specific acceptance condition is instead Broadcast and unknown-unicast tests remain isolated to each customer and independent service port traffic follows expected boundaries.
Passing that test would not establish resolution of the stated issue. The relevant proof is: Broadcast and unknown-unicast tests remain isolated to each customer and independent service port traffic follows expected boundaries.
Confirm the correction by demonstrating: Broadcast and unknown-unicast tests remain isolated to each customer and independent service port traffic follows expected boundaries. This directly tests the intended change, Separate the tenant virtual switches and bridge-domain scopes while preserving the contracted tag translation on each handoff.
Another proposed result is: The customer CE exchanges untagged frames successfully without gaining access to other wholesale service VLANs. It would not independently establish the required outcome: Broadcast and unknown-unicast tests remain isolated to each customer and independent service port traffic follows expected boundaries.
Question 265
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 material service-availability, routing, switching or security risk most directly needs control?
Answer and Explanation
Correct Answer: B
Another caution is: Misaligned port tagging can create a service outage or expose unrelated VLANs through an overly broad trunk. The key risk in this case is: A VLAN number is not sufficient tenant isolation if bridge domains and virtual-switch mappings are incorrectly shared.
A VLAN number is not sufficient tenant isolation if bridge domains and virtual-switch mappings are incorrectly shared. That boundary protects the documented change, Separate the tenant virtual switches and bridge-domain scopes while preserving the contracted tag translation on each handoff, from introducing an unrelated problem.
This limitation concerns another setting: Removing outer tags indiscriminately can merge customer broadcast domains and break provider-bridging isolation. The observed facts here make a different caution decisive: A VLAN number is not sufficient tenant isolation if bridge domains and virtual-switch mappings are incorrectly shared.
Another caution is: Changing ASN or routing policy without verifying the transport endpoint can create a separate outage or route leak. The key risk in this case is: A VLAN number is not sufficient tenant isolation if bridge domains and virtual-switch mappings are incorrectly shared.
Question 266
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 focused investigation is the most useful before modifying the network configuration?
Answer and Explanation
Correct Answer: C
That check concerns a different signal: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers. The case-relevant check is: 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.
Another check would compare active Junos routing, protocol and forwarding displays with this differentiating 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. The case observation to isolate is Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts. The focused check here is: 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 focused investigation should 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. It is tied to the observed evidence: Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts. It tests the conditions for this response: Separate the tenant virtual switches and bridge-domain scopes while preserving the contracted tag translation on each handoff.
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: Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts.
Question 267
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 controlled operational implementation sequence best protects the related provider service?
Answer and Explanation
Correct Answer: C
Another possible combination is: First verify the observed failure (Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers.); review and authorize the bounded correction (Check accepted service VLAN and inner-tag preservation requirements, then correct the intended outer tag translation or service membership.); then independently verify the intended outcome (Customer inner VLAN traffic crosses the agreed provider service path with the expected outer encapsulation and isolation from unrelated customers.) before production rollout. The current record instead supports Separate the tenant virtual switches and bridge-domain scopes while preserving the contracted tag translation on each handoff, verified by Broadcast and unknown-unicast tests remain isolated to each customer and independent service port traffic follows expected boundaries.
Another potential sequence is: First verify the observed failure (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.); review and authorize the bounded correction (Check the VLAN's Layer 3 interface relationship and correct the scoped IRB binding, address family and eligibility.); then independently verify the intended outcome (Hosts in the specified VLAN reach their authorized gateway while isolation and route selection for other VLANs remain intact.) before production rollout. It has no direct link to the distinguishing evidence: Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts.
The case evidence indicates: Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts. Apply the scoped action: Separate the tenant virtual switches and bridge-domain scopes while preserving the contracted tag translation on each handoff. Confirm its effect independently: Broadcast and unknown-unicast tests remain isolated to each customer and independent service port traffic follows expected boundaries.
An alternative plan is: First verify the observed failure (Advertised route inspection lists a private customer prefix that is not present in the approved external export inventory.); review and authorize the bounded correction (Apply a precise export filter and route-policy tests for public prefixes, then confirm rejected customer-only routes stay internal.); then independently verify the intended outcome (Upstream advertised-route output contains only approved prefixes and the private customer destination remains available in its intended instance.) before production rollout. It does not test the case-specific condition: Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts.
Question 268
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 set of evidence, limited change and independent validation best justifies authorization?
Answer and Explanation
Correct Answer: D
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 Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts.
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: Separate the tenant virtual switches and bridge-domain scopes while preserving the contracted tag translation on each handoff.
Another approval action is: Observed evidence (Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding.), limited correction (Verify the handoff contract and bridge interface port mode, then restore only the intended tag treatment and VLAN membership.), independently measurable result (The customer CE exchanges untagged frames successfully without gaining access to other wholesale service VLANs.). The relevant evidence and acceptance are Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts and Broadcast and unknown-unicast tests remain isolated to each customer and independent service port traffic follows expected boundaries, respectively.
The change-control boundary is: Observed evidence (Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts.), limited correction (Separate the tenant virtual switches and bridge-domain scopes while preserving the contracted tag translation on each handoff.), independently measurable result (Broadcast and unknown-unicast tests remain isolated to each customer and independent service port traffic follows expected boundaries.). The evidence for this scope is Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts.
Question 269
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. If the change fails its expected acceptance test, which controlled recovery approach is most appropriate?
Answer and Explanation
Correct Answer: C
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 Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts.
Another recovery route would pause changes, preserve the differentiating 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.), restore the last approved safe network state and reassess irb interface lacks a link to the correct vlan. It does not preserve the condition of this case: Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts. The bounded fallback is: Pause changes, preserve the differentiating evidence (Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts.), restore the last approved safe network state and reassess bridge domain configuration allows duplicate customer identifiers.
If the change fails acceptance, the bounded recovery is: Pause changes, preserve the differentiating evidence (Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts.), restore the last approved safe network state and reassess bridge domain configuration allows duplicate customer identifiers. The case-specific risk is a VLAN number is not sufficient tenant isolation if bridge domains and virtual-switch mappings are incorrectly shared. The original evidence remains: Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts.
Another fallback concerns pausing changes, preserve the differentiating evidence (Peer history contains hold timer expirations and packet captures show sporadic missing keepalives during a saturated control-plane event.), restore the last approved safe network state and reassess bgp keepalive hold-time expectations do not match session state. The current change concerns Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts.
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.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests
- Juniper JN0-364 Practice Test 25 - 10 Questions (Last Reviewed 25-Oct-2026)
- 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)