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 42

Question 410

The on-call engineer at Northshore Utilities receives this fault report: A bridged VLAN experiences unknown-unicast flooding because no valid source MAC entries are learned on the new access interface after a migration. What initial check best isolates the actual failing protocol stage?

  1. Inspect ingress interface's virtual-switch instance, instance-specific bridge domains and MAC tables for both tenants.
  2. Inspect VLAN/bridge-domain IRB association, gateway ARP or neighbor entries and resulting connected routes in the correct instance.
  3. Inspect the MAC address table for the VLAN and customer MAC, port state and aging or movement counters on the service interfaces.
  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.

That evidence could be normal while the reported defect persists. It is aimed at: 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. Instead inspect: Inspect the MAC address table for the VLAN and customer MAC, port state and aging or movement counters on the service interfaces.

B.

The check diagnoses a different layer of service. Its source issue is: 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 relevant initial check is: Inspect the MAC address table for the VLAN and customer MAC, port state and aging or movement counters on the service interfaces.

C.

Inspect the MAC address table for the VLAN and customer MAC, port state and aging or movement counters on the service interfaces. MAC learning concerns Layer 2 location; changing BGP next hop or IGP metric does not select the correct bridged egress port.

D.

That evidence could be normal while the reported defect persists. It is aimed at: After replacing an edge switch, customer traffic arrives with an unexpected outer tag and the provider places it in the wrong broadcast domain. Instead inspect: Inspect the MAC address table for the VLAN and customer MAC, port state and aging or movement counters on the service interfaces.

Question 411

The provider operations team at Canal City University reports: 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. Which implementation decision best corrects the cause?

  1. Add only the required VLAN tag to the trunk membership on the relevant interfaces and verify consistent tagging at both ends.
  2. Verify the logical unit's encapsulation, VLAN/bridge-domain membership and interface counters on both ends of the service.
  3. Assign the access interface to the intended VLAN and verify untagged ingress/egress membership without enabling unrelated tagged networks.
  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.

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: Assign the access interface to the intended VLAN and verify untagged ingress/egress membership without enabling unrelated tagged networks.

B.

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: Untagged ingress classification is controlled by access-port VLAN membership, not by a route-policy community.

C.

Assign the access interface to the intended VLAN and verify untagged ingress/egress membership without enabling unrelated tagged networks. The case-specific reason is: Untagged ingress classification is controlled by access-port VLAN membership, not by a route-policy community. A direct acceptance test is: Untagged traffic is classified into the expected VLAN and the endpoint reaches only the approved gateway and local broadcast domain.

D.

That would address a separate configuration fault: A bridged VLAN experiences unknown-unicast flooding because no valid source MAC entries are learned on the new access interface after a migration. This stem identifies a different cause, corrected by: Assign the access interface to the intended VLAN and verify untagged ingress/egress membership without enabling unrelated tagged networks.

Question 412

During a post-change check at Canal City University, the original condition was: 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. What evidence would validate the corrected behavior?

  1. Untagged traffic is classified into the expected VLAN and the endpoint reaches only the approved gateway and local broadcast 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. Packet captures and bridge tables confirm that each ingress frame's tags select the intended VLAN, with no unexpected native/untagged classification.

Correct answer: A

Explanation of each choice

A.

Untagged traffic is classified into the expected VLAN and the endpoint reaches only the approved gateway and local broadcast domain. Untagged ingress classification is controlled by access-port VLAN membership, not by a route-policy community.

B.

This would be valid for another situation: 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. It does not establish that the failing boundary in this scenario works; verify: Untagged traffic is classified into the expected VLAN and the endpoint reaches only the approved gateway and local broadcast domain.

C.

The observation confirms a different component's behavior. Its source context is: Two wholesale L2 customers use overlapping VLAN identifiers; without separation their Ethernet segments are accidentally bridged together. In this case the success criterion is: Untagged traffic is classified into the expected VLAN and the endpoint reaches only the approved gateway and local broadcast domain.

D.

That check proves something else, such as: A migration mixes tagged and untagged handoffs on the same service, and operators cannot explain why traffic falls into an unintended VLAN. It could pass while the stated problem remains. The targeted evidence here is: Untagged traffic is classified into the expected VLAN and the endpoint reaches only the approved gateway and local broadcast domain.

Question 413

At Canal City University, an engineer is asked to explain this case: 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. Which underlying routing or switching principle accounts for the appropriate solution?

  1. IEEE 802.1Q VLAN tags label a frame's broadcast domain, while untagged handling is determined by ingress port configuration.
  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. An access port assigns untagged frames to one configured VLAN and does not ordinarily serve as a multi-VLAN tagged transport.

Correct answer: D

Explanation of each choice

A.

The statement can be true when After replacing an edge switch, customer traffic arrives with an unexpected outer tag and the provider places it in the wrong broadcast domain. But it does not explain the reported failure. Here: Untagged ingress classification is controlled by access-port VLAN membership, not by a route-policy community.

B.

That principle belongs to a different service stage: An upstream customer changes its inner VLAN numbers and the carrier wants to preserve those tags without provisioning each inner VLAN individually. The directly relevant mechanism is: An access port assigns untagged frames to one configured VLAN and does not ordinarily serve as a multi-VLAN tagged transport.

C.

This explains a separate protocol behavior: A provider uplink carries VLAN 100 but drops VLAN 200 traffic because the trunk's allowed membership omits VLAN 200. In the current facts, the controlling mechanism is: An access port assigns untagged frames to one configured VLAN and does not ordinarily serve as a multi-VLAN tagged transport.

D.

An access port assigns untagged frames to one configured VLAN and does not ordinarily serve as a multi-VLAN tagged transport. The key distinction is: Untagged ingress classification is controlled by access-port VLAN membership, not by a route-policy community. Accordingly the remedy is: Assign the access interface to the intended VLAN and verify untagged ingress/egress membership without enabling unrelated tagged networks.

Question 414

A risk assessment at Canal City University identifies: 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. Which practical consequence is most specifically tied to this failure?

  1. The customer can reach a management segment or become isolated from its actual gateway despite the Ethernet link staying up.
  2. A physically healthy Ethernet interface can carry no usable service traffic if logical classification or bridge membership is wrong.
  3. Local L2 exchanges can succeed while all off-subnet traffic fails at an absent or incorrect default gateway.
  4. Cross-customer broadcast and unknown-unicast traffic can leak between services if same-numbered VLANs share a bridge context.

Correct answer: A

Explanation of each choice

A.

The customer can reach a management segment or become isolated from its actual gateway despite the Ethernet link staying up. The direct mitigation is: Assign the access interface to the intended VLAN and verify untagged ingress/egress membership without enabling unrelated tagged networks.

B.

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 customer can reach a management segment or become isolated from its actual gateway despite the Ethernet link staying up.

C.

It is a risk in another topology or protocol state: Hosts within a VLAN communicate, but traffic to other VLANs fails because the logical Layer 3 gateway is not linked to the bridge VLAN. Here the most direct failure path is: The customer can reach a management segment or become isolated from its actual gateway despite the Ethernet link staying up.

D.

The concern could occur elsewhere when 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. For the stated scenario, the immediate risk is: The customer can reach a management segment or become isolated from its actual gateway despite the Ethernet link staying up.

Question 415

The on-call engineer at Canal City University receives this fault report: 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. What initial check best isolates the actual failing protocol stage?

  1. Correlate MAC move counters, spanning-tree port states and broadcast interface counters for the affected VLAN.
  2. Capture the actual Ethernet header tags on both sides and inspect ingress VLAN classification and allowed tag configuration.
  3. Compare tagged frame captures with both sides' trunk mode and allowed VLAN list, and inspect per-VLAN MAC tables.
  4. Inspect interface port mode and VLAN membership, then capture untagged frames and verify the learned MAC in the target VLAN.

Correct answer: D

Explanation of each choice

A.

This check may help with another root cause, for example: A redundant bridged customer ring floods broadcasts after a link change because the blocking/forwarding boundary is misconfigured. It does not test the first failed condition; start with: Inspect interface port mode and VLAN membership, then capture untagged frames and verify the learned MAC in the target VLAN.

B.

That evidence could be normal while the reported defect persists. It is aimed at: A migration mixes tagged and untagged handoffs on the same service, and operators cannot explain why traffic falls into an unintended VLAN. Instead inspect: Inspect interface port mode and VLAN membership, then capture untagged frames and verify the learned MAC in the target VLAN.

C.

The check diagnoses a different layer of service. Its source issue is: A provider uplink carries VLAN 100 but drops VLAN 200 traffic because the trunk's allowed membership omits VLAN 200. The relevant initial check is: Inspect interface port mode and VLAN membership, then capture untagged frames and verify the learned MAC in the target VLAN.

D.

Inspect interface port mode and VLAN membership, then capture untagged frames and verify the learned MAC in the target VLAN. Untagged ingress classification is controlled by access-port VLAN membership, not by a route-policy community.

Question 416

A production change request at Maple Coast Retail includes this finding: A customer endpoint sends untagged Ethernet frames but the new interface is configured for the wrong untagged VLAN, preventing communication with its gateway. What should the engineer change to address it?

  1. Add only the required VLAN tag to the trunk membership on the relevant interfaces and verify consistent tagging at both ends.
  2. Align the port's expected tagging mode, VLAN identifier and outer-tag interpretation with the actual Ethernet frames in the service contract.
  3. Assign the access interface to the intended VLAN and verify untagged ingress/egress membership without enabling unrelated tagged networks.
  4. Apply provider bridging with correct outer service VLAN tagging and compatible TPID/tag handling, preserving customer inner tags end-to-end.

Correct answer: C

Explanation of each choice

A.

The other action is relevant when 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 current case instead requires: Assign the access interface to the intended VLAN and verify untagged ingress/egress membership without enabling unrelated tagged networks. The distinction is: Untagged ingress classification is controlled by access-port VLAN membership, not by a route-policy community.

B.

That would address a separate configuration fault: After replacing an edge switch, customer traffic arrives with an unexpected outer tag and the provider places it in the wrong broadcast domain. This stem identifies a different cause, corrected by: Assign the access interface to the intended VLAN and verify untagged ingress/egress membership without enabling unrelated tagged networks.

C.

Assign the access interface to the intended VLAN and verify untagged ingress/egress membership without enabling unrelated tagged networks. The case-specific reason is: Untagged ingress classification is controlled by access-port VLAN membership, not by a route-policy community. A direct acceptance test is: Untagged traffic is classified into the expected VLAN and the endpoint reaches only the approved gateway and local broadcast domain.

D.

The other action is relevant when 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. The current case instead requires: Assign the access interface to the intended VLAN and verify untagged ingress/egress membership without enabling unrelated tagged networks. The distinction is: Untagged ingress classification is controlled by access-port VLAN membership, not by a route-policy community.

Question 417

After Maple Coast Retail applies its proposed fix to this problem — A customer endpoint sends untagged Ethernet frames but the new interface is configured for the wrong untagged VLAN, preventing communication with its gateway. — which observation best proves the specific failure has been resolved?

  1. Packet captures and bridge tables confirm that each ingress frame's tags select the intended VLAN, with no unexpected native/untagged classification.
  2. Untagged traffic is classified into the expected VLAN and the endpoint reaches only the approved gateway and local broadcast domain.
  3. The frame carries the expected service outer tag across the provider, and the customer inner VLAN tag emerges unchanged at the remote handoff.
  4. Hosts resolve the expected default gateway MAC and packets are routed between permitted subnets with active connected routes from the IRB.

Correct answer: B

Explanation of each choice

A.

The observation confirms a different component's behavior. Its source context is: A migration mixes tagged and untagged handoffs on the same service, and operators cannot explain why traffic falls into an unintended VLAN. In this case the success criterion is: Untagged traffic is classified into the expected VLAN and the endpoint reaches only the approved gateway and local broadcast domain.

B.

Untagged traffic is classified into the expected VLAN and the endpoint reaches only the approved gateway and local broadcast domain. Untagged ingress classification is controlled by access-port VLAN membership, not by a route-policy community.

C.

This would be valid for another situation: An upstream customer changes its inner VLAN numbers and the carrier wants to preserve those tags without provisioning each inner VLAN individually. It does not establish that the failing boundary in this scenario works; verify: Untagged traffic is classified into the expected VLAN and the endpoint reaches only the approved gateway and local broadcast domain.

D.

The observation confirms a different component's behavior. Its source context is: Hosts within a VLAN communicate, but traffic to other VLANs fails because the logical Layer 3 gateway is not linked to the bridge VLAN. In this case the success criterion is: Untagged traffic is classified into the expected VLAN and the endpoint reaches only the approved gateway and local broadcast domain.

Question 418

An architecture review at Maple Coast Retail examines the following symptom: A customer endpoint sends untagged Ethernet frames but the new interface is configured for the wrong untagged VLAN, preventing communication with its gateway. What Junos or protocol mechanism is most directly responsible?

  1. An Ethernet trunk carries multiple VLAN-tagged services but still requires explicit matching VLAN membership and compatible tagging configuration.
  2. An integrated routing and bridging interface provides a routed Layer 3 interface for a bridged VLAN or bridge domain.
  3. Junos logical Ethernet service units and bridge-domain membership jointly determine how service frames are classified and forwarded.
  4. An access port assigns untagged frames to one configured VLAN and does not ordinarily serve as a multi-VLAN tagged transport.

Correct answer: D

Explanation of each choice

A.

This explains a separate protocol behavior: 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 the current facts, the controlling mechanism is: An access port assigns untagged frames to one configured VLAN and does not ordinarily serve as a multi-VLAN tagged transport.

B.

The statement can be true 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. But it does not explain the reported failure. Here: Untagged ingress classification is controlled by access-port VLAN membership, not by a route-policy community.

C.

That principle belongs to a different service stage: 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 directly relevant mechanism is: An access port assigns untagged frames to one configured VLAN and does not ordinarily serve as a multi-VLAN tagged transport.

D.

An access port assigns untagged frames to one configured VLAN and does not ordinarily serve as a multi-VLAN tagged transport. The key distinction is: Untagged ingress classification is controlled by access-port VLAN membership, not by a route-policy community. Accordingly the remedy is: Assign the access interface to the intended VLAN and verify untagged ingress/egress membership without enabling unrelated tagged networks.

Question 419

The team at Maple Coast Retail defers a fix for this condition: A customer endpoint sends untagged Ethernet frames but the new interface is configured for the wrong untagged VLAN, preventing communication with its gateway. What failure is most likely if no targeted control is applied?

  1. The carrier may strip or reinterpret customer tags, merge tenants or drop frames due to inconsistent outer-tag expectations.
  2. Stale or missing MAC learning leads to unintended flooding, intermittent reachability or delivery to an old attachment port.
  3. Cross-customer broadcast and unknown-unicast traffic can leak between services if same-numbered VLANs share a bridge context.
  4. The customer can reach a management segment or become isolated from its actual gateway despite the Ethernet link staying up.

Correct answer: D

Explanation of each choice

A.

It is a risk in another topology or protocol state: An upstream customer changes its inner VLAN numbers and the carrier wants to preserve those tags without provisioning each inner VLAN individually. Here the most direct failure path is: The customer can reach a management segment or become isolated from its actual gateway despite the Ethernet link staying up.

B.

The concern could occur elsewhere when A provider Ethernet service forwards unicast normally until a customer VM migrates; packets for its MAC continue toward the old attachment port. For the stated scenario, the immediate risk is: The customer can reach a management segment or become isolated from its actual gateway despite the Ethernet link staying up.

C.

That consequence is more closely associated with another deficiency, 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. The described fault instead exposes: The customer can reach a management segment or become isolated from its actual gateway despite the Ethernet link staying up.

D.

The customer can reach a management segment or become isolated from its actual gateway despite the Ethernet link staying up. The direct mitigation is: Assign the access interface to the intended VLAN and verify untagged ingress/egress membership without enabling unrelated tagged networks.

Question 420

During provider troubleshooting at Maple Coast Retail, this symptom is observed: A customer endpoint sends untagged Ethernet frames but the new interface is configured for the wrong untagged VLAN, preventing communication with its gateway. Which targeted inspection should precede remediation?

  1. Correlate MAC move counters, spanning-tree port states and broadcast interface counters for the affected VLAN.
  2. Inspect interface port mode and VLAN membership, then capture untagged frames and verify the learned MAC in the target VLAN.
  3. Capture the actual Ethernet header tags on both sides and inspect ingress VLAN classification and allowed tag configuration.
  4. Inspect ingress interface's virtual-switch instance, instance-specific bridge domains and MAC tables for both tenants.

Correct answer: B

Explanation of each choice

A.

The check diagnoses a different layer of service. Its source issue is: Two provider-facing switchports both forward the same bridged service and the MAC table shows persistent flapping between ports. The relevant initial check is: Inspect interface port mode and VLAN membership, then capture untagged frames and verify the learned MAC in the target VLAN.

B.

Inspect interface port mode and VLAN membership, then capture untagged frames and verify the learned MAC in the target VLAN. Untagged ingress classification is controlled by access-port VLAN membership, not by a route-policy community.

C.

That evidence could be normal while the reported defect persists. It is aimed at: A migration mixes tagged and untagged handoffs on the same service, and operators cannot explain why traffic falls into an unintended VLAN. Instead inspect: Inspect interface port mode and VLAN membership, then capture untagged frames and verify the learned MAC in the target VLAN.

D.

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: Inspect interface port mode and VLAN membership, then capture untagged frames and verify the learned MAC in the target VLAN.

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