Pass Juniper JN0-364 Exam in First Attempt Easily
Real Juniper JN0-364 Exam Questions, Accurate & Verified Answers As Experienced in the Actual Test!

Verified by experts

JN0-364 Premium File

  • 69 Questions & Answers
  • Last Update: Nov 4, 2026
$69.99 $76.99

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

Question 460

During provider troubleshooting at Eastvale MetroNet, this symptom is observed: An operator moves one customer port into a new virtual-switch service but continues to inspect the global bridge table, missing the tenant-specific entries. Which targeted inspection should precede remediation?

  1. Capture the actual Ethernet header tags on both sides and inspect ingress VLAN classification and allowed tag configuration.
  2. Inspect ingress interface's virtual-switch instance, instance-specific bridge domains and MAC tables for both tenants.
  3. Inspect bridge-domain MAC counts, moves, aging and storm/loop indications before changing routing protocol configuration.
  4. Inspect the MAC address table for the VLAN and customer MAC, port state and aging or movement counters on the service interfaces.

Correct answer: B

Explanation of each choice

A.

This check may help with another root cause, for example: A migration mixes tagged and untagged handoffs on the same service, and operators cannot explain why traffic falls into an unintended VLAN. It does not test the first failed condition; start with: Inspect ingress interface's virtual-switch instance, instance-specific bridge domains and MAC tables for both tenants.

B.

Inspect ingress interface's virtual-switch instance, instance-specific bridge domains and MAC tables for both tenants. Logical switching separation, not a BGP path preference, is required to isolate overlapping Layer 2 customer services.

C.

The check diagnoses a different layer of service. Its source issue is: A wholesale edge receives far more source MAC addresses than the agreed customer-service limit and unknown-unicast flooding increases. The relevant initial check is: Inspect ingress interface's virtual-switch instance, instance-specific bridge domains and MAC tables for both tenants.

D.

This check may help with another root cause, for example: A provider Ethernet service forwards unicast normally until a customer VM migrates; packets for its MAC continue toward the old attachment port. It does not test the first failed condition; start with: Inspect ingress interface's virtual-switch instance, instance-specific bridge domains and MAC tables for both tenants.

Question 461

A production change request at Ironcrest Payments includes this finding: A carrier must transport a customer's internal VLAN tags across its Metro Ethernet network while isolating each customer service with an outer service tag. What should the engineer change to address it?

  1. Apply provider bridging with correct outer service VLAN tagging and compatible TPID/tag handling, preserving customer inner tags end-to-end.
  2. Restore correct VLAN membership and source-MAC learning on the intended ingress ports, clear only stale entries when justified, and verify the learned destination interfaces.
  3. Align the port's expected tagging mode, VLAN identifier and outer-tag interpretation with the actual Ethernet frames in the service contract.
  4. Verify the logical unit's encapsulation, VLAN/bridge-domain membership and interface counters on both ends of the service.

Correct answer: A

Explanation of each choice

A.

Apply provider bridging with correct outer service VLAN tagging and compatible TPID/tag handling, preserving customer inner tags end-to-end. The case-specific reason is: The service depends on two distinct VLAN tag contexts; ordinary single-tag access mode is insufficient for transparent customer tag transport. A direct acceptance test is: The frame carries the expected service outer tag across the provider, and the customer inner VLAN tag emerges unchanged at the remote handoff.

B.

This action may apply to a different problem, for example: A bridged VLAN experiences unknown-unicast flooding because no valid source MAC entries are learned on the new access interface after a migration. It does not repair the stated failure boundary. The case-specific reason is: The service depends on two distinct VLAN tag contexts; ordinary single-tag access mode is insufficient for transparent customer tag transport.

C.

This action may apply to a different problem, for example: After replacing an edge switch, customer traffic arrives with an unexpected outer tag and the provider places it in the wrong broadcast domain. It does not repair the stated failure boundary. The case-specific reason is: The service depends on two distinct VLAN tag contexts; ordinary single-tag access mode is insufficient for transparent customer tag transport.

D.

The other action is relevant when A port is in the correct trunk mode yet a service still fails because the corresponding bridge domain does not include the logical unit. The current case instead requires: Apply provider bridging with correct outer service VLAN tagging and compatible TPID/tag handling, preserving customer inner tags end-to-end. The distinction is: The service depends on two distinct VLAN tag contexts; ordinary single-tag access mode is insufficient for transparent customer tag transport.

Question 462

After Ironcrest Payments applies its proposed fix to this problem — A carrier must transport a customer's internal VLAN tags across its Metro Ethernet network while isolating each customer service with an outer service tag. — which observation best proves the specific failure has been resolved?

  1. The frame carries the expected service outer tag across the provider, and the customer inner VLAN tag emerges unchanged at the remote handoff.
  2. The bridge table learns the expected customer MAC on its current interface and unicast packets are forwarded to that port instead of flooding or blackholing.
  3. Untagged traffic is classified into the expected VLAN and the endpoint reaches only the approved gateway and local broadcast domain.
  4. Ingress and egress tagged frame counters increase for the correct logical interface and expected MAC entries appear within the bridge domain.

Correct answer: A

Explanation of each choice

A.

The frame carries the expected service outer tag across the provider, and the customer inner VLAN tag emerges unchanged at the remote handoff. The service depends on two distinct VLAN tag contexts; ordinary single-tag access mode is insufficient for transparent customer tag transport.

B.

This would be valid for another situation: A bridged VLAN experiences unknown-unicast flooding because no valid source MAC entries are learned on the new access interface after a migration. It does not establish that the failing boundary in this scenario works; verify: The frame carries the expected service outer tag across the provider, and the customer inner VLAN tag emerges unchanged at the remote handoff.

C.

This would be valid for another situation: A site access port accidentally belongs to the provider management VLAN, so the attached single-VLAN device receives a DHCP address from the wrong segment. It does not establish that the failing boundary in this scenario works; verify: The frame carries the expected service outer tag across the provider, and the customer inner VLAN tag emerges unchanged at the remote handoff.

D.

The observation confirms a different component's behavior. Its source context is: A port is in the correct trunk mode yet a service still fails because the corresponding bridge domain does not include the logical unit. In this case the success criterion is: The frame carries the expected service outer tag across the provider, and the customer inner VLAN tag emerges unchanged at the remote handoff.

Question 463

An architecture review at Ironcrest Payments examines the following symptom: A carrier must transport a customer's internal VLAN tags across its Metro Ethernet network while isolating each customer service with an outer service tag. What Junos or protocol mechanism is most directly responsible?

  1. An access port assigns untagged frames to one configured VLAN and does not ordinarily serve as a multi-VLAN tagged transport.
  2. Q-in-Q stacking adds a provider service tag outside a customer tag so the carrier can transport multiple customer VLANs inside one service context.
  3. An Ethernet trunk carries multiple VLAN-tagged services but still requires explicit matching VLAN membership and compatible tagging configuration.
  4. A virtual-switch instance establishes a distinct Layer 2 forwarding context, permitting overlapping VLAN IDs without a shared global bridge domain.

Correct answer: B

Explanation of each choice

A.

This explains a separate protocol behavior: A site access port accidentally belongs to the provider management VLAN, so the attached single-VLAN device receives a DHCP address from the wrong segment. In the current facts, the controlling mechanism is: Q-in-Q stacking adds a provider service tag outside a customer tag so the carrier can transport multiple customer VLANs inside one service context.

B.

Q-in-Q stacking adds a provider service tag outside a customer tag so the carrier can transport multiple customer VLANs inside one service context. The key distinction is: The service depends on two distinct VLAN tag contexts; ordinary single-tag access mode is insufficient for transparent customer tag transport. Accordingly the remedy is: Apply provider bridging with correct outer service VLAN tagging and compatible TPID/tag handling, preserving customer inner tags end-to-end.

C.

That principle belongs to a different service stage: A provider uplink carries VLAN 100 but drops VLAN 200 traffic because the trunk's allowed membership omits VLAN 200. The directly relevant mechanism is: Q-in-Q stacking adds a provider service tag outside a customer tag so the carrier can transport multiple customer VLANs inside one service context.

D.

This explains a separate protocol behavior: An operator moves one customer port into a new virtual-switch service but continues to inspect the global bridge table, missing the tenant-specific entries. In the current facts, the controlling mechanism is: Q-in-Q stacking adds a provider service tag outside a customer tag so the carrier can transport multiple customer VLANs inside one service context.

Question 464

The team at Ironcrest Payments defers a fix for this condition: A carrier must transport a customer's internal VLAN tags across its Metro Ethernet network while isolating each customer service with an outer service tag. What failure is most likely if no targeted control is applied?

  1. Traffic can cross logical tenant boundaries or be silently discarded by an interface expecting a different tag format.
  2. Broadcast storms and unstable MAC learning can consume bandwidth and interrupt multiple tenants sharing the switched fabric.
  3. The carrier may strip or reinterpret customer tags, merge tenants or drop frames due to inconsistent outer-tag expectations.
  4. The customer can reach a management segment or become isolated from its actual gateway despite the Ethernet link staying up.

Correct answer: C

Explanation of each choice

A.

It is a risk in another topology or protocol state: After replacing an edge switch, customer traffic arrives with an unexpected outer tag and the provider places it in the wrong broadcast domain. Here the most direct failure path is: The carrier may strip or reinterpret customer tags, merge tenants or drop frames due to inconsistent outer-tag expectations.

B.

The concern could occur elsewhere when Two provider-facing switchports both forward the same bridged service and the MAC table shows persistent flapping between ports. For the stated scenario, the immediate risk is: The carrier may strip or reinterpret customer tags, merge tenants or drop frames due to inconsistent outer-tag expectations.

C.

The carrier may strip or reinterpret customer tags, merge tenants or drop frames due to inconsistent outer-tag expectations. The direct mitigation is: Apply provider bridging with correct outer service VLAN tagging and compatible TPID/tag handling, preserving customer inner tags end-to-end.

D.

It is a risk in another topology or protocol state: A customer endpoint sends untagged Ethernet frames but the new interface is configured for the wrong untagged VLAN, preventing communication with its gateway. Here the most direct failure path is: The carrier may strip or reinterpret customer tags, merge tenants or drop frames due to inconsistent outer-tag expectations.

Question 465

During provider troubleshooting at Ironcrest Payments, this symptom is observed: A carrier must transport a customer's internal VLAN tags across its Metro Ethernet network while isolating each customer service with an outer service tag. Which targeted inspection should precede remediation?

  1. Inspect ingress interface's virtual-switch instance, instance-specific bridge domains and MAC tables for both tenants.
  2. Capture ingress and egress Ethernet tag stacks and check provider bridging service VLAN and TPID settings at both edges.
  3. Inspect interface port mode and VLAN membership, then capture untagged frames and verify the learned MAC in the target VLAN.
  4. Compare tagged frame captures with both sides' trunk mode and allowed VLAN list, and inspect per-VLAN MAC tables.

Correct answer: B

Explanation of each choice

A.

The check diagnoses a different layer of service. Its source issue is: Two wholesale L2 customers use overlapping VLAN identifiers; without separation their Ethernet segments are accidentally bridged together. The relevant initial check is: Capture ingress and egress Ethernet tag stacks and check provider bridging service VLAN and TPID settings at both edges.

B.

Capture ingress and egress Ethernet tag stacks and check provider bridging service VLAN and TPID settings at both edges. The service depends on two distinct VLAN tag contexts; ordinary single-tag access mode is insufficient for transparent customer tag transport.

C.

That evidence could be normal while the reported defect persists. It is aimed at: A site access port accidentally belongs to the provider management VLAN, so the attached single-VLAN device receives a DHCP address from the wrong segment. Instead inspect: Capture ingress and egress Ethernet tag stacks and check provider bridging service VLAN and TPID settings at both edges.

D.

The check diagnoses a different layer of service. Its source issue is: A campus-to-provider trunk passes several tagged customer services while a newly provisioned tag fails because the far-end trunk has not allowed it. The relevant initial check is: Capture ingress and egress Ethernet tag stacks and check provider bridging service VLAN and TPID settings at both edges.

Question 466

At Westhaven Software, a service provider router shows this failure: An upstream customer changes its inner VLAN numbers and the carrier wants to preserve those tags without provisioning each inner VLAN individually. What is the best targeted configuration or operations action?

  1. Verify the logical unit's encapsulation, VLAN/bridge-domain membership and interface counters on both ends of the service.
  2. Assign the access interface to the intended VLAN and verify untagged ingress/egress membership without enabling unrelated tagged networks.
  3. Apply provider bridging with correct outer service VLAN tagging and compatible TPID/tag handling, preserving customer inner tags end-to-end.
  4. Restore correct VLAN membership and source-MAC learning on the intended ingress ports, clear only stale entries when justified, and verify the learned destination interfaces.

Correct answer: C

Explanation of each choice

A.

This action may apply to a different problem, for example: A port is in the correct trunk mode yet a service still fails because the corresponding bridge domain does not include the logical unit. It does not repair the stated failure boundary. The case-specific reason is: The service depends on two distinct VLAN tag contexts; ordinary single-tag access mode is insufficient for transparent customer tag transport.

B.

The other action is relevant when A site access port accidentally belongs to the provider management VLAN, so the attached single-VLAN device receives a DHCP address from the wrong segment. The current case instead requires: Apply provider bridging with correct outer service VLAN tagging and compatible TPID/tag handling, preserving customer inner tags end-to-end. The distinction is: The service depends on two distinct VLAN tag contexts; ordinary single-tag access mode is insufficient for transparent customer tag transport.

C.

Apply provider bridging with correct outer service VLAN tagging and compatible TPID/tag handling, preserving customer inner tags end-to-end. The case-specific reason is: The service depends on two distinct VLAN tag contexts; ordinary single-tag access mode is insufficient for transparent customer tag transport. A direct acceptance test is: The frame carries the expected service outer tag across the provider, and the customer inner VLAN tag emerges unchanged at the remote handoff.

D.

This action may apply to a different problem, for example: A provider Ethernet service forwards unicast normally until a customer VM migrates; packets for its MAC continue toward the old attachment port. It does not repair the stated failure boundary. The case-specific reason is: The service depends on two distinct VLAN tag contexts; ordinary single-tag access mode is insufficient for transparent customer tag transport.

Question 467

A change auditor at Westhaven Software must validate remediation of this finding: An upstream customer changes its inner VLAN numbers and the carrier wants to preserve those tags without provisioning each inner VLAN individually. Which test outcome is the strongest acceptance evidence?

  1. Ingress and egress tagged frame counters increase for the correct logical interface and expected MAC entries appear within the bridge domain.
  2. Tagged frames for the approved VLAN pass and MAC learning occurs in the correct bridge domain without extending unauthorized VLANs.
  3. Each tenant's same-numbered VLAN learns MACs and floods traffic only within its intended virtual switch, without sharing another customer's broadcast domain.
  4. The frame carries the expected service outer tag across the provider, and the customer inner VLAN tag emerges unchanged at the remote handoff.

Correct answer: D

Explanation of each choice

A.

This would be valid for another situation: A port is in the correct trunk mode yet a service still fails because the corresponding bridge domain does not include the logical unit. It does not establish that the failing boundary in this scenario works; verify: The frame carries the expected service outer tag across the provider, and the customer inner VLAN tag emerges unchanged at the remote handoff.

B.

The observation confirms a different component's behavior. Its source context is: A provider uplink carries VLAN 100 but drops VLAN 200 traffic because the trunk's allowed membership omits VLAN 200. In this case the success criterion is: The frame carries the expected service outer tag across the provider, and the customer inner VLAN tag emerges unchanged at the remote handoff.

C.

That check proves something else, such as: An operator moves one customer port into a new virtual-switch service but continues to inspect the global bridge table, missing the tenant-specific entries. It could pass while the stated problem remains. The targeted evidence here is: The frame carries the expected service outer tag across the provider, and the customer inner VLAN tag emerges unchanged at the remote handoff.

D.

The frame carries the expected service outer tag across the provider, and the customer inner VLAN tag emerges unchanged at the remote handoff. The service depends on two distinct VLAN tag contexts; ordinary single-tag access mode is insufficient for transparent customer tag transport.

Question 468

The operations training team at Westhaven Software discusses this issue: An upstream customer changes its inner VLAN numbers and the carrier wants to preserve those tags without provisioning each inner VLAN individually. Which technical explanation matches the intended correction?

  1. A virtual-switch instance establishes a distinct Layer 2 forwarding context, permitting overlapping VLAN IDs without a shared global bridge domain.
  2. Bridge forwarding databases and learning controls scope MAC state to the service; unchecked churn stresses memory and floods unknown destinations.
  3. Q-in-Q stacking adds a provider service tag outside a customer tag so the carrier can transport multiple customer VLANs inside one service context.
  4. An integrated routing and bridging interface provides a routed Layer 3 interface for a bridged VLAN or bridge domain.

Correct answer: C

Explanation of each choice

A.

That principle belongs to a different service stage: An operator moves one customer port into a new virtual-switch service but continues to inspect the global bridge table, missing the tenant-specific entries. The directly relevant mechanism is: Q-in-Q stacking adds a provider service tag outside a customer tag so the carrier can transport multiple customer VLANs inside one service context.

B.

This explains a separate protocol behavior: A provider Ethernet handoff suddenly experiences massive MAC-learning churn after a customer loop; unrelated customers share the same switching hardware. In the current facts, the controlling mechanism is: Q-in-Q stacking adds a provider service tag outside a customer tag so the carrier can transport multiple customer VLANs inside one service context.

C.

Q-in-Q stacking adds a provider service tag outside a customer tag so the carrier can transport multiple customer VLANs inside one service context. The key distinction is: The service depends on two distinct VLAN tag contexts; ordinary single-tag access mode is insufficient for transparent customer tag transport. Accordingly the remedy is: Apply provider bridging with correct outer service VLAN tagging and compatible TPID/tag handling, preserving customer inner tags end-to-end.

D.

That principle belongs to a different service stage: Hosts within a VLAN communicate, but traffic to other VLANs fails because the logical Layer 3 gateway is not linked to the bridge VLAN. The directly relevant mechanism is: Q-in-Q stacking adds a provider service tag outside a customer tag so the carrier can transport multiple customer VLANs inside one service context.

Question 469

At Westhaven Software, a service acceptance review considers the unresolved issue: An upstream customer changes its inner VLAN numbers and the carrier wants to preserve those tags without provisioning each inner VLAN individually. Which operational exposure follows most directly?

  1. A physically healthy Ethernet interface can carry no usable service traffic if logical classification or bridge membership is wrong.
  2. One service is blackholed or an unnecessary VLAN is exposed if trunk allowed membership is too narrow or overly broad.
  3. The carrier may strip or reinterpret customer tags, merge tenants or drop frames due to inconsistent outer-tag expectations.
  4. The customer can reach a management segment or become isolated from its actual gateway despite the Ethernet link staying up.

Correct answer: C

Explanation of each choice

A.

That consequence is more closely associated with another deficiency, such as: A port is in the correct trunk mode yet a service still fails because the corresponding bridge domain does not include the logical unit. The described fault instead exposes: The carrier may strip or reinterpret customer tags, merge tenants or drop frames due to inconsistent outer-tag expectations.

B.

It is a risk in another topology or protocol state: A provider uplink carries VLAN 100 but drops VLAN 200 traffic because the trunk's allowed membership omits VLAN 200. Here the most direct failure path is: The carrier may strip or reinterpret customer tags, merge tenants or drop frames due to inconsistent outer-tag expectations.

C.

The carrier may strip or reinterpret customer tags, merge tenants or drop frames due to inconsistent outer-tag expectations. The direct mitigation is: Apply provider bridging with correct outer service VLAN tagging and compatible TPID/tag handling, preserving customer inner tags end-to-end.

D.

That consequence is more closely associated with another deficiency, such as: A site access port accidentally belongs to the provider management VLAN, so the attached single-VLAN device receives a DHCP address from the wrong segment. The described fault instead exposes: The carrier may strip or reinterpret customer tags, merge tenants or drop frames due to inconsistent outer-tag expectations.

Question 470

Before changing configuration at Westhaven Software, an engineer investigates: An upstream customer changes its inner VLAN numbers and the carrier wants to preserve those tags without provisioning each inner VLAN individually. Which first diagnostic most directly tests the suspected cause?

  1. Compare tagged frame captures with both sides' trunk mode and allowed VLAN list, and inspect per-VLAN MAC tables.
  2. Capture ingress and egress Ethernet tag stacks and check provider bridging service VLAN and TPID settings at both edges.
  3. Inspect the MAC address table for the VLAN and customer MAC, port state and aging or movement counters on the service interfaces.
  4. Correlate MAC move counters, spanning-tree port states and broadcast interface counters for the affected VLAN.

Correct answer: B

Explanation of each choice

A.

That evidence could be normal while the reported defect persists. It is aimed at: A campus-to-provider trunk passes several tagged customer services while a newly provisioned tag fails because the far-end trunk has not allowed it. Instead inspect: Capture ingress and egress Ethernet tag stacks and check provider bridging service VLAN and TPID settings at both edges.

B.

Capture ingress and egress Ethernet tag stacks and check provider bridging service VLAN and TPID settings at both edges. The service depends on two distinct VLAN tag contexts; ordinary single-tag access mode is insufficient for transparent customer tag transport.

C.

This check may help with another root cause, for example: A bridged VLAN experiences unknown-unicast flooding because no valid source MAC entries are learned on the new access interface after a migration. It does not test the first failed condition; start with: Capture ingress and egress Ethernet tag stacks and check provider bridging service VLAN and TPID settings at both edges.

D.

That evidence could be normal while the reported defect persists. It is aimed at: A redundant bridged customer ring floods broadcasts after a link change because the blocking/forwarding boundary is misconfigured. Instead inspect: Capture ingress and egress Ethernet tag stacks and check provider bridging service VLAN and TPID settings at both edges.

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

SPECIAL OFFER: GET 10% OFF
This is ONE TIME OFFER

You save
10%

Enter Your Email Address to Receive Your 10% Off Discount Code

SPECIAL OFFER: GET 10% OFF

You save
10%

Use Discount Code:

A confirmation link was sent to your e-mail.

Please check your mailbox for a message from support@examlabs.com and follow the directions.

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

Simply submit your email address below to get started with our interactive software demo of your free trial.

  • Realistic exam simulation and exam editor with preview functions
  • Whole exam in a single file with several different question types
  • Customizable exam-taking mode & detailed score reports