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 46

Question 450

The on-call engineer at Baystone Energy receives this fault report: A provider moved a gateway address to an IRB logical unit yet the bridge domain has no valid association with that IRB interface. What initial check best isolates the actual failing protocol stage?

  1. Inspect bridge-domain MAC counts, moves, aging and storm/loop indications before changing routing protocol configuration.
  2. Inspect the MAC address table for the VLAN and customer MAC, port state and aging or movement counters on the service interfaces.
  3. Inspect VLAN/bridge-domain IRB association, gateway ARP or neighbor entries and resulting connected routes in the correct instance.
  4. Capture the actual Ethernet header tags on both sides and inspect ingress VLAN classification and allowed tag configuration.

Correct answer: C

Explanation of each choice

A.

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 VLAN/bridge-domain IRB association, gateway ARP or neighbor entries and resulting connected routes in the correct instance.

B.

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 VLAN/bridge-domain IRB association, gateway ARP or neighbor entries and resulting connected routes in the correct instance.

C.

Inspect VLAN/bridge-domain IRB association, gateway ARP or neighbor entries and resulting connected routes in the correct instance. A local bridge can work without an IRB, but inter-VLAN routing requires an attached Layer 3 gateway interface.

D.

The check diagnoses a different layer of service. Its source issue is: After replacing an edge switch, customer traffic arrives with an unexpected outer tag and the provider places it in the wrong broadcast domain. The relevant initial check is: Inspect VLAN/bridge-domain IRB association, gateway ARP or neighbor entries and resulting connected routes in the correct instance.

Question 451

The provider operations team at Westhaven Software reports: Two wholesale L2 customers use overlapping VLAN identifiers; without separation their Ethernet segments are accidentally bridged together. Which implementation decision best corrects the cause?

  1. Configure and attach the intended IRB interface/unit to the bridge domain with the correct gateway IP and routing-instance context.
  2. Verify the logical unit's encapsulation, VLAN/bridge-domain membership and interface counters on both ends of the service.
  3. Constrain the appropriate customer service bridge domain and enforce a supported MAC-learning/security control while fixing the upstream loop.
  4. Place customer bridge domains and interfaces into separate intended virtual-switch/routing-instance contexts and validate forwarding boundaries.

Correct answer: D

Explanation of each choice

A.

This action may apply to a different problem, for example: Hosts within a VLAN communicate, but traffic to other VLANs fails because the logical Layer 3 gateway is not linked to the bridge VLAN. It does not repair the stated failure boundary. The case-specific reason is: Logical switching separation, not a BGP path preference, is required to isolate overlapping Layer 2 customer services.

B.

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: Place customer bridge domains and interfaces into separate intended virtual-switch/routing-instance contexts and validate forwarding boundaries. The distinction is: Logical switching separation, not a BGP path preference, is required to isolate overlapping Layer 2 customer services.

C.

That would address a separate configuration fault: A provider Ethernet handoff suddenly experiences massive MAC-learning churn after a customer loop; unrelated customers share the same switching hardware. This stem identifies a different cause, corrected by: Place customer bridge domains and interfaces into separate intended virtual-switch/routing-instance contexts and validate forwarding boundaries.

D.

Place customer bridge domains and interfaces into separate intended virtual-switch/routing-instance contexts and validate forwarding boundaries. The case-specific reason is: Logical switching separation, not a BGP path preference, is required to isolate overlapping Layer 2 customer services. A direct acceptance test is: Each tenant's same-numbered VLAN learns MACs and floods traffic only within its intended virtual switch, without sharing another customer's broadcast domain.

Question 452

During a post-change check at Westhaven Software, the original condition was: Two wholesale L2 customers use overlapping VLAN identifiers; without separation their Ethernet segments are accidentally bridged together. What evidence would validate the corrected behavior?

  1. 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.
  2. Tagged frames for the approved VLAN pass and MAC learning occurs in the correct bridge domain without extending unauthorized VLANs.
  3. Per-service learned MAC count remains within the approved limit and legitimate customer MACs remain reachable without cross-service flooding.
  4. Each tenant's same-numbered VLAN learns MACs and floods traffic only within its intended virtual switch, without sharing another customer's broadcast domain.

Correct answer: D

Explanation of each choice

A.

The observation confirms a different component's behavior. Its source context is: A bridged VLAN experiences unknown-unicast flooding because no valid source MAC entries are learned on the new access interface after a migration. In this case the success criterion is: Each tenant's same-numbered VLAN learns MACs and floods traffic only within its intended virtual switch, without sharing another customer's broadcast domain.

B.

The observation confirms a different component's behavior. Its source context 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. In this case the success criterion is: Each tenant's same-numbered VLAN learns MACs and floods traffic only within its intended virtual switch, without sharing another customer's broadcast domain.

C.

That check proves something else, such as: A provider Ethernet handoff suddenly experiences massive MAC-learning churn after a customer loop; unrelated customers share the same switching hardware. It could pass while the stated problem remains. The targeted evidence here is: Each tenant's same-numbered VLAN learns MACs and floods traffic only within its intended virtual switch, without sharing another customer's broadcast domain.

D.

Each tenant's same-numbered VLAN learns MACs and floods traffic only within its intended virtual switch, without sharing another customer's broadcast domain. Logical switching separation, not a BGP path preference, is required to isolate overlapping Layer 2 customer services.

Question 453

At Westhaven Software, an engineer is asked to explain this case: Two wholesale L2 customers use overlapping VLAN identifiers; without separation their Ethernet segments are accidentally bridged together. Which underlying routing or switching principle accounts for the appropriate solution?

  1. A virtual-switch instance establishes a distinct Layer 2 forwarding context, permitting overlapping VLAN IDs without a shared global bridge domain.
  2. Ethernet bridges associate observed source MACs with ingress ports within a broadcast domain and use learned destination MAC entries for unicast forwarding.
  3. Junos logical Ethernet service units and bridge-domain membership jointly determine how service frames are classified and forwarded.
  4. IEEE 802.1Q VLAN tags label a frame's broadcast domain, while untagged handling is determined by ingress port configuration.

Correct answer: A

Explanation of each choice

A.

A virtual-switch instance establishes a distinct Layer 2 forwarding context, permitting overlapping VLAN IDs without a shared global bridge domain. The key distinction is: Logical switching separation, not a BGP path preference, is required to isolate overlapping Layer 2 customer services. Accordingly the remedy is: Place customer bridge domains and interfaces into separate intended virtual-switch/routing-instance contexts and validate forwarding boundaries.

B.

The statement can be true when A bridged VLAN experiences unknown-unicast flooding because no valid source MAC entries are learned on the new access interface after a migration. But it does not explain the reported failure. Here: Logical switching separation, not a BGP path preference, is required to isolate overlapping Layer 2 customer services.

C.

The statement can be true when A logical Ethernet interface is up but no customer frames arrive on the intended VLAN after a maintenance migration. But it does not explain the reported failure. Here: Logical switching separation, not a BGP path preference, is required to isolate overlapping Layer 2 customer services.

D.

That principle belongs to a different service stage: A migration mixes tagged and untagged handoffs on the same service, and operators cannot explain why traffic falls into an unintended VLAN. The directly relevant mechanism is: A virtual-switch instance establishes a distinct Layer 2 forwarding context, permitting overlapping VLAN IDs without a shared global bridge domain.

Question 454

A risk assessment at Westhaven Software identifies: Two wholesale L2 customers use overlapping VLAN identifiers; without separation their Ethernet segments are accidentally bridged together. Which practical consequence is most specifically tied to this failure?

  1. Cross-customer broadcast and unknown-unicast traffic can leak between services if same-numbered VLANs share a bridge context.
  2. A physically healthy Ethernet interface can carry no usable service traffic if logical classification or bridge membership is wrong.
  3. Traffic can cross logical tenant boundaries or be silently discarded by an interface expecting a different tag format.
  4. Broadcast storms and unstable MAC learning can consume bandwidth and interrupt multiple tenants sharing the switched fabric.

Correct answer: A

Explanation of each choice

A.

Cross-customer broadcast and unknown-unicast traffic can leak between services if same-numbered VLANs share a bridge context. The direct mitigation is: Place customer bridge domains and interfaces into separate intended virtual-switch/routing-instance contexts and validate forwarding boundaries.

B.

It is a risk in another topology or protocol state: A port is in the correct trunk mode yet a service still fails because the corresponding bridge domain does not include the logical unit. Here the most direct failure path is: Cross-customer broadcast and unknown-unicast traffic can leak between services if same-numbered VLANs share a bridge context.

C.

The concern could occur elsewhere when After replacing an edge switch, customer traffic arrives with an unexpected outer tag and the provider places it in the wrong broadcast domain. For the stated scenario, the immediate risk is: Cross-customer broadcast and unknown-unicast traffic can leak between services if same-numbered VLANs share a bridge context.

D.

That consequence is more closely associated with another deficiency, such as: Two provider-facing switchports both forward the same bridged service and the MAC table shows persistent flapping between ports. The described fault instead exposes: Cross-customer broadcast and unknown-unicast traffic can leak between services if same-numbered VLANs share a bridge context.

Question 455

The on-call engineer at Westhaven Software receives this fault report: Two wholesale L2 customers use overlapping VLAN identifiers; without separation their Ethernet segments are accidentally bridged together. What initial check best isolates the actual failing protocol stage?

  1. Inspect VLAN/bridge-domain IRB association, gateway ARP or neighbor entries and resulting connected routes in the correct instance.
  2. Capture the actual Ethernet header tags on both sides and inspect ingress VLAN classification and allowed tag configuration.
  3. Inspect ingress interface's virtual-switch instance, instance-specific bridge domains and MAC tables for both tenants.
  4. Inspect bridge-domain MAC counts, moves, aging and storm/loop indications before changing routing protocol configuration.

Correct answer: C

Explanation of each choice

A.

That evidence could be normal while the reported defect persists. It is aimed at: Hosts within a VLAN communicate, but traffic to other VLANs fails because the logical Layer 3 gateway is not linked to the bridge VLAN. Instead inspect: Inspect ingress interface's virtual-switch instance, instance-specific bridge domains and MAC tables for both tenants.

B.

The check diagnoses a different layer of service. Its source issue is: A migration mixes tagged and untagged handoffs on the same service, and operators cannot explain why traffic falls into an unintended VLAN. The relevant initial check is: Inspect ingress interface's virtual-switch instance, instance-specific bridge domains and MAC tables for both tenants.

C.

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.

D.

That evidence could be normal while the reported defect persists. It is aimed at: A wholesale edge receives far more source MAC addresses than the agreed customer-service limit and unknown-unicast flooding increases. Instead inspect: Inspect ingress interface's virtual-switch instance, instance-specific bridge domains and MAC tables for both tenants.

Question 456

A production change request at Eastvale MetroNet includes this finding: 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. What should the engineer change to address it?

  1. Place customer bridge domains and interfaces into separate intended virtual-switch/routing-instance contexts and validate forwarding boundaries.
  2. Constrain the appropriate customer service bridge domain and enforce a supported MAC-learning/security control while fixing the upstream loop.
  3. Restore a loop-free Layer 2 topology using correct spanning-tree or loop-protection design and verify the affected service forwarding state.
  4. Add only the required VLAN tag to the trunk membership on the relevant interfaces and verify consistent tagging at both ends.

Correct answer: A

Explanation of each choice

A.

Place customer bridge domains and interfaces into separate intended virtual-switch/routing-instance contexts and validate forwarding boundaries. The case-specific reason is: Logical switching separation, not a BGP path preference, is required to isolate overlapping Layer 2 customer services. A direct acceptance test is: Each tenant's same-numbered VLAN learns MACs and floods traffic only within its intended virtual switch, without sharing another customer's broadcast domain.

B.

This action may apply to a different problem, for example: A provider Ethernet handoff suddenly experiences massive MAC-learning churn after a customer loop; unrelated customers share the same switching hardware. It does not repair the stated failure boundary. The case-specific reason is: Logical switching separation, not a BGP path preference, is required to isolate overlapping Layer 2 customer services.

C.

The other action is relevant when Two provider-facing switchports both forward the same bridged service and the MAC table shows persistent flapping between ports. The current case instead requires: Place customer bridge domains and interfaces into separate intended virtual-switch/routing-instance contexts and validate forwarding boundaries. The distinction is: Logical switching separation, not a BGP path preference, is required to isolate overlapping Layer 2 customer services.

D.

That would address a separate configuration fault: A provider uplink carries VLAN 100 but drops VLAN 200 traffic because the trunk's allowed membership omits VLAN 200. This stem identifies a different cause, corrected by: Place customer bridge domains and interfaces into separate intended virtual-switch/routing-instance contexts and validate forwarding boundaries.

Question 457

After Eastvale MetroNet applies its proposed fix to this problem — 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 observation best proves the specific failure has been resolved?

  1. Each tenant's same-numbered VLAN learns MACs and floods traffic only within its intended virtual switch, without sharing another customer's broadcast domain.
  2. Per-service learned MAC count remains within the approved limit and legitimate customer MACs remain reachable without cross-service flooding.
  3. Ingress and egress tagged frame counters increase for the correct logical interface and expected MAC entries appear within the bridge 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: A

Explanation of each choice

A.

Each tenant's same-numbered VLAN learns MACs and floods traffic only within its intended virtual switch, without sharing another customer's broadcast domain. Logical switching separation, not a BGP path preference, is required to isolate overlapping Layer 2 customer services.

B.

This would be valid for another situation: A provider Ethernet handoff suddenly experiences massive MAC-learning churn after a customer loop; unrelated customers share the same switching hardware. It does not establish that the failing boundary in this scenario works; verify: Each tenant's same-numbered VLAN learns MACs and floods traffic only within its intended virtual switch, without sharing another customer's broadcast domain.

C.

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: Each tenant's same-numbered VLAN learns MACs and floods traffic only within its intended virtual switch, without sharing another customer's broadcast domain.

D.

That check proves something else, such as: 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. It could pass while the stated problem remains. The targeted evidence here is: Each tenant's same-numbered VLAN learns MACs and floods traffic only within its intended virtual switch, without sharing another customer's broadcast domain.

Question 458

An architecture review at Eastvale MetroNet examines the following symptom: 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. 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. Bridge forwarding databases and learning controls scope MAC state to the service; unchecked churn stresses memory and floods unknown destinations.
  3. A virtual-switch instance establishes a distinct Layer 2 forwarding context, permitting overlapping VLAN IDs without a shared global bridge domain.
  4. Ethernet bridges associate observed source MACs with ingress ports within a broadcast domain and use learned destination MAC entries for unicast forwarding.

Correct answer: C

Explanation of each choice

A.

That principle belongs to a different service stage: A customer endpoint sends untagged Ethernet frames but the new interface is configured for the wrong untagged VLAN, preventing communication with its gateway. The directly relevant mechanism is: A virtual-switch instance establishes a distinct Layer 2 forwarding context, permitting overlapping VLAN IDs without a shared global bridge domain.

B.

That principle belongs to a different service stage: A provider Ethernet handoff suddenly experiences massive MAC-learning churn after a customer loop; unrelated customers share the same switching hardware. The directly relevant mechanism is: A virtual-switch instance establishes a distinct Layer 2 forwarding context, permitting overlapping VLAN IDs without a shared global bridge domain.

C.

A virtual-switch instance establishes a distinct Layer 2 forwarding context, permitting overlapping VLAN IDs without a shared global bridge domain. The key distinction is: Logical switching separation, not a BGP path preference, is required to isolate overlapping Layer 2 customer services. Accordingly the remedy is: Place customer bridge domains and interfaces into separate intended virtual-switch/routing-instance contexts and validate forwarding boundaries.

D.

The statement can be true when A provider Ethernet service forwards unicast normally until a customer VM migrates; packets for its MAC continue toward the old attachment port. But it does not explain the reported failure. Here: Logical switching separation, not a BGP path preference, is required to isolate overlapping Layer 2 customer services.

Question 459

The team at Eastvale MetroNet defers a fix for this condition: 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. What failure is most likely if no targeted control is applied?

  1. Broadcast storms and unstable MAC learning can consume bandwidth and interrupt multiple tenants sharing the switched fabric.
  2. Cross-customer broadcast and unknown-unicast traffic can leak between services if same-numbered VLANs share a bridge context.
  3. An uncontrolled customer loop can exhaust MAC-table resources or cause excessive flooding that affects other services.
  4. Local L2 exchanges can succeed while all off-subnet traffic fails at an absent or incorrect default gateway.

Correct answer: B

Explanation of each choice

A.

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: Cross-customer broadcast and unknown-unicast traffic can leak between services if same-numbered VLANs share a bridge context.

B.

Cross-customer broadcast and unknown-unicast traffic can leak between services if same-numbered VLANs share a bridge context. The direct mitigation is: Place customer bridge domains and interfaces into separate intended virtual-switch/routing-instance contexts and validate forwarding boundaries.

C.

It is a risk in another topology or protocol state: A wholesale edge receives far more source MAC addresses than the agreed customer-service limit and unknown-unicast flooding increases. Here the most direct failure path is: Cross-customer broadcast and unknown-unicast traffic can leak between services if same-numbered VLANs share a bridge context.

D.

The concern could occur elsewhere when Hosts within a VLAN communicate, but traffic to other VLANs fails because the logical Layer 3 gateway is not linked to the bridge VLAN. For the stated scenario, the immediate risk is: Cross-customer broadcast and unknown-unicast traffic can leak between services if same-numbered VLANs share a bridge context.

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.

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