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 44

Question 430

Before changing configuration at ValleyCross Fiber, an engineer investigates: 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. Which first diagnostic most directly tests the suspected cause?

  1. Inspect the MAC address table for the VLAN and customer MAC, port state and aging or movement counters on the service interfaces.
  2. Compare tagged frame captures with both sides' trunk mode and allowed VLAN list, and inspect per-VLAN MAC tables.
  3. Inspect logical interface configuration, encapsulation, unit VLAN ID, bridge membership and port counters for the exact service.
  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.

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: Compare tagged frame captures with both sides' trunk mode and allowed VLAN list, and inspect per-VLAN MAC tables.

B.

Compare tagged frame captures with both sides' trunk mode and allowed VLAN list, and inspect per-VLAN MAC tables. A trunk can carry multiple tag values, but a tag is not forwarded if its VLAN is not permitted on the participating link.

C.

The check diagnoses a different layer of service. Its source issue 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. The relevant initial check is: Compare tagged frame captures with both sides' trunk mode and allowed VLAN list, and inspect per-VLAN MAC tables.

D.

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: Compare tagged frame captures with both sides' trunk mode and allowed VLAN list, and inspect per-VLAN MAC tables.

Question 431

At Summit Logistics, a service provider router shows this failure: After replacing an edge switch, customer traffic arrives with an unexpected outer tag and the provider places it in the wrong broadcast domain. What is the best targeted configuration or operations action?

  1. Align the port's expected tagging mode, VLAN identifier and outer-tag interpretation with the actual Ethernet frames in the service contract.
  2. Add only the required VLAN tag to the trunk membership on the relevant interfaces and verify consistent tagging at both ends.
  3. Apply provider bridging with correct outer service VLAN tagging and compatible TPID/tag handling, preserving customer inner tags end-to-end.
  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.

Align the port's expected tagging mode, VLAN identifier and outer-tag interpretation with the actual Ethernet frames in the service contract. The case-specific reason is: Tag interpretation is an Ethernet service boundary; OSPF router ID or MPLS path cost cannot compensate for a wrong 802.1Q tag. A direct acceptance test is: Packet captures and bridge tables confirm that each ingress frame's tags select the intended VLAN, with no unexpected native/untagged classification.

B.

That would address a separate configuration fault: 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. This stem identifies a different cause, corrected by: Align the port's expected tagging mode, VLAN identifier and outer-tag interpretation with the actual Ethernet frames in the service contract.

C.

This action may apply to a different problem, for example: 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 does not repair the stated failure boundary. The case-specific reason is: Tag interpretation is an Ethernet service boundary; OSPF router ID or MPLS path cost cannot compensate for a wrong 802.1Q tag.

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: Align the port's expected tagging mode, VLAN identifier and outer-tag interpretation with the actual Ethernet frames in the service contract. The distinction is: Tag interpretation is an Ethernet service boundary; OSPF router ID or MPLS path cost cannot compensate for a wrong 802.1Q tag.

Question 432

A change auditor at Summit Logistics must validate remediation of this finding: After replacing an edge switch, customer traffic arrives with an unexpected outer tag and the provider places it in the wrong broadcast domain. Which test outcome is the strongest acceptance evidence?

  1. Packet captures and bridge tables confirm that each ingress frame's tags select the intended VLAN, with no unexpected native/untagged classification.
  2. Ingress and egress tagged frame counters increase for the correct logical interface and expected MAC entries appear within the bridge domain.
  3. Untagged traffic is classified into the expected VLAN and the endpoint reaches only the approved gateway and local 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: A

Explanation of each choice

A.

Packet captures and bridge tables confirm that each ingress frame's tags select the intended VLAN, with no unexpected native/untagged classification. Tag interpretation is an Ethernet service boundary; OSPF router ID or MPLS path cost cannot compensate for a wrong 802.1Q tag.

B.

That check proves something else, 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. It could pass while the stated problem remains. The targeted evidence here is: Packet captures and bridge tables confirm that each ingress frame's tags select the intended VLAN, with no unexpected native/untagged classification.

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: Packet captures and bridge tables confirm that each ingress frame's tags select the intended VLAN, with no unexpected native/untagged classification.

D.

The observation confirms a different component's behavior. Its source context is: An upstream customer changes its inner VLAN numbers and the carrier wants to preserve those tags without provisioning each inner VLAN individually. In this case the success criterion is: Packet captures and bridge tables confirm that each ingress frame's tags select the intended VLAN, with no unexpected native/untagged classification.

Question 433

The operations training team at Summit Logistics discusses this issue: After replacing an edge switch, customer traffic arrives with an unexpected outer tag and the provider places it in the wrong broadcast domain. Which technical explanation matches the intended correction?

  1. An access port assigns untagged frames to one configured VLAN and does not ordinarily serve as a multi-VLAN tagged transport.
  2. IEEE 802.1Q VLAN tags label a frame's broadcast domain, while untagged handling is determined by ingress port configuration.
  3. Ethernet bridges associate observed source MACs with ingress ports within a broadcast domain and use learned destination MAC entries for unicast forwarding.
  4. An integrated routing and bridging interface provides a routed Layer 3 interface for a bridged VLAN or 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: IEEE 802.1Q VLAN tags label a frame's broadcast domain, while untagged handling is determined by ingress port configuration.

B.

IEEE 802.1Q VLAN tags label a frame's broadcast domain, while untagged handling is determined by ingress port configuration. The key distinction is: Tag interpretation is an Ethernet service boundary; OSPF router ID or MPLS path cost cannot compensate for a wrong 802.1Q tag. Accordingly the remedy is: Align the port's expected tagging mode, VLAN identifier and outer-tag interpretation with the actual Ethernet frames in the service contract.

C.

That principle belongs to a different service stage: A provider Ethernet service forwards unicast normally until a customer VM migrates; packets for its MAC continue toward the old attachment port. The directly relevant mechanism is: IEEE 802.1Q VLAN tags label a frame's broadcast domain, while untagged handling is determined by ingress port configuration.

D.

This explains a separate protocol behavior: A provider moved a gateway address to an IRB logical unit yet the bridge domain has no valid association with that IRB interface. In the current facts, the controlling mechanism is: IEEE 802.1Q VLAN tags label a frame's broadcast domain, while untagged handling is determined by ingress port configuration.

Question 434

At Summit Logistics, a service acceptance review considers the unresolved issue: After replacing an edge switch, customer traffic arrives with an unexpected outer tag and the provider places it in the wrong broadcast domain. 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. Cross-customer broadcast and unknown-unicast traffic can leak between services if same-numbered VLANs share a bridge context.
  3. The carrier may strip or reinterpret customer tags, merge tenants or drop frames due to inconsistent outer-tag expectations.
  4. Traffic can cross logical tenant boundaries or be silently discarded by an interface expecting a different tag format.

Correct answer: D

Explanation of each choice

A.

It is a risk in another topology or protocol state: A logical Ethernet interface is up but no customer frames arrive on the intended VLAN after a maintenance migration. Here the most direct failure path is: Traffic can cross logical tenant boundaries or be silently discarded by an interface expecting a different tag format.

B.

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: Traffic can cross logical tenant boundaries or be silently discarded by an interface expecting a different tag format.

C.

That consequence is more closely associated with another deficiency, 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. The described fault instead exposes: Traffic can cross logical tenant boundaries or be silently discarded by an interface expecting a different tag format.

D.

Traffic can cross logical tenant boundaries or be silently discarded by an interface expecting a different tag format. The direct mitigation is: Align the port's expected tagging mode, VLAN identifier and outer-tag interpretation with the actual Ethernet frames in the service contract.

Question 435

Before changing configuration at Summit Logistics, an engineer investigates: After replacing an edge switch, customer traffic arrives with an unexpected outer tag and the provider places it in the wrong broadcast domain. Which first diagnostic most directly tests the suspected cause?

  1. Inspect logical interface configuration, encapsulation, unit VLAN ID, bridge membership and port counters for the exact service.
  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 interface port mode and VLAN membership, then capture untagged frames and verify the learned MAC in the target VLAN.

Correct answer: B

Explanation of each choice

A.

The check diagnoses a different layer of service. Its source issue is: A logical Ethernet interface is up but no customer frames arrive on the intended VLAN after a maintenance migration. The relevant initial check is: Capture the actual Ethernet header tags on both sides and inspect ingress VLAN classification and allowed tag configuration.

B.

Capture the actual Ethernet header tags on both sides and inspect ingress VLAN classification and allowed tag configuration. Tag interpretation is an Ethernet service boundary; OSPF router ID or MPLS path cost cannot compensate for a wrong 802.1Q tag.

C.

That evidence could be normal while the reported defect persists. It is aimed at: Two wholesale L2 customers use overlapping VLAN identifiers; without separation their Ethernet segments are accidentally bridged together. Instead inspect: Capture the actual Ethernet header tags on both sides and inspect ingress VLAN classification and allowed tag configuration.

D.

The check diagnoses a different layer of service. Its source issue is: A customer endpoint sends untagged Ethernet frames but the new interface is configured for the wrong untagged VLAN, preventing communication with its gateway. The relevant initial check is: Capture the actual Ethernet header tags on both sides and inspect ingress VLAN classification and allowed tag configuration.

Question 436

During a Junos network change at Cedar Coast Telecom, the engineer observes: A migration mixes tagged and untagged handoffs on the same service, and operators cannot explain why traffic falls into an unintended VLAN. Which remediation most directly fixes the described problem?

  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. 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.
  4. Align the port's expected tagging mode, VLAN identifier and outer-tag interpretation with the actual Ethernet frames in the service contract.

Correct answer: D

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: Tag interpretation is an Ethernet service boundary; OSPF router ID or MPLS path cost cannot compensate for a wrong 802.1Q tag.

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: Align the port's expected tagging mode, VLAN identifier and outer-tag interpretation with the actual Ethernet frames in the service contract. The distinction is: Tag interpretation is an Ethernet service boundary; OSPF router ID or MPLS path cost cannot compensate for a wrong 802.1Q tag.

C.

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: Align the port's expected tagging mode, VLAN identifier and outer-tag interpretation with the actual Ethernet frames in the service contract.

D.

Align the port's expected tagging mode, VLAN identifier and outer-tag interpretation with the actual Ethernet frames in the service contract. The case-specific reason is: Tag interpretation is an Ethernet service boundary; OSPF router ID or MPLS path cost cannot compensate for a wrong 802.1Q tag. A direct acceptance test is: Packet captures and bridge tables confirm that each ingress frame's tags select the intended VLAN, with no unexpected native/untagged classification.

Question 437

The Junos team at Cedar Coast Telecom needs a success criterion for this defect: A migration mixes tagged and untagged handoffs on the same service, and operators cannot explain why traffic falls into an unintended VLAN. Which observed result most precisely confirms the intended repair?

  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. Tagged frames for the approved VLAN pass and MAC learning occurs in the correct bridge domain without extending unauthorized VLANs.
  3. 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.
  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: D

Explanation of each choice

A.

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: Packet captures and bridge tables confirm that each ingress frame's tags select the intended VLAN, with no unexpected native/untagged classification.

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: Packet captures and bridge tables confirm that each ingress frame's tags select the intended VLAN, with no unexpected native/untagged classification.

C.

That check proves something else, such as: A bridged VLAN experiences unknown-unicast flooding because no valid source MAC entries are learned on the new access interface after a migration. It could pass while the stated problem remains. The targeted evidence here is: Packet captures and bridge tables confirm that each ingress frame's tags select the intended VLAN, with no unexpected native/untagged classification.

D.

Packet captures and bridge tables confirm that each ingress frame's tags select the intended VLAN, with no unexpected native/untagged classification. Tag interpretation is an Ethernet service boundary; OSPF router ID or MPLS path cost cannot compensate for a wrong 802.1Q tag.

Question 438

While analyzing a service failure at Cedar Coast Telecom, the following is observed: A migration mixes tagged and untagged handoffs on the same service, and operators cannot explain why traffic falls into an unintended VLAN. Which mechanism best explains the underlying control-plane or forwarding behavior?

  1. An integrated routing and bridging interface provides a routed Layer 3 interface for a bridged VLAN or bridge domain.
  2. An Ethernet trunk carries multiple VLAN-tagged services but still requires explicit matching VLAN membership and compatible tagging configuration.
  3. IEEE 802.1Q VLAN tags label a frame's broadcast domain, while untagged handling is determined by ingress port 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: C

Explanation of each choice

A.

That principle belongs to a different service stage: A provider moved a gateway address to an IRB logical unit yet the bridge domain has no valid association with that IRB interface. The directly relevant mechanism is: IEEE 802.1Q VLAN tags label a frame's broadcast domain, while untagged handling is determined by ingress port configuration.

B.

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: IEEE 802.1Q VLAN tags label a frame's broadcast domain, while untagged handling is determined by ingress port configuration.

C.

IEEE 802.1Q VLAN tags label a frame's broadcast domain, while untagged handling is determined by ingress port configuration. The key distinction is: Tag interpretation is an Ethernet service boundary; OSPF router ID or MPLS path cost cannot compensate for a wrong 802.1Q tag. Accordingly the remedy is: Align the port's expected tagging mode, VLAN identifier and outer-tag interpretation with the actual Ethernet frames in the service contract.

D.

That principle belongs to a different service stage: Two wholesale L2 customers use overlapping VLAN identifiers; without separation their Ethernet segments are accidentally bridged together. The directly relevant mechanism is: IEEE 802.1Q VLAN tags label a frame's broadcast domain, while untagged handling is determined by ingress port configuration.

Question 439

The following provider defect remains uncorrected at Cedar Coast Telecom: A migration mixes tagged and untagged handoffs on the same service, and operators cannot explain why traffic falls into an unintended VLAN. What is the most direct service or security risk of leaving it unresolved?

  1. The carrier may strip or reinterpret customer tags, merge tenants or drop frames due to inconsistent outer-tag expectations.
  2. Traffic can cross logical tenant boundaries or be silently discarded by an interface expecting a different tag format.
  3. Broadcast storms and unstable MAC learning can consume bandwidth and interrupt multiple tenants sharing the switched fabric.
  4. One service is blackholed or an unnecessary VLAN is exposed if trunk allowed membership is too narrow or overly broad.

Correct answer: B

Explanation of each choice

A.

That consequence is more closely associated with another deficiency, such as: An upstream customer changes its inner VLAN numbers and the carrier wants to preserve those tags without provisioning each inner VLAN individually. The described fault instead exposes: Traffic can cross logical tenant boundaries or be silently discarded by an interface expecting a different tag format.

B.

Traffic can cross logical tenant boundaries or be silently discarded by an interface expecting a different tag format. The direct mitigation is: Align the port's expected tagging mode, VLAN identifier and outer-tag interpretation with the actual Ethernet frames in the service contract.

C.

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: Traffic can cross logical tenant boundaries or be silently discarded by an interface expecting a different tag format.

D.

That consequence is more closely associated with another deficiency, such as: A provider uplink carries VLAN 100 but drops VLAN 200 traffic because the trunk's allowed membership omits VLAN 200. The described fault instead exposes: Traffic can cross logical tenant boundaries or be silently discarded by an interface expecting a different tag format.

Question 440

A support escalation at Cedar Coast Telecom describes: A migration mixes tagged and untagged handoffs on the same service, and operators cannot explain why traffic falls into an unintended VLAN. Where should the Junos operator look first for decisive evidence?

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

Explanation of each choice

A.

That evidence could be normal while the reported defect persists. It is aimed at: A customer endpoint sends untagged Ethernet frames but the new interface is configured for the wrong untagged VLAN, preventing communication with its gateway. Instead inspect: Capture the actual Ethernet header tags on both sides and inspect ingress VLAN classification and allowed tag configuration.

B.

The check diagnoses a different layer of service. Its source issue is: A provider Ethernet service forwards unicast normally until a customer VM migrates; packets for its MAC continue toward the old attachment port. The relevant initial check is: Capture the actual Ethernet header tags on both sides and inspect ingress VLAN classification and allowed tag configuration.

C.

This check may help with another root cause, for example: A provider moved a gateway address to an IRB logical unit yet the bridge domain has no valid association with that IRB interface. It does not test the first failed condition; start with: Capture the actual Ethernet header tags on both sides and inspect ingress VLAN classification and allowed tag configuration.

D.

Capture the actual Ethernet header tags on both sides and inspect ingress VLAN classification and allowed tag configuration. Tag interpretation is an Ethernet service boundary; OSPF router ID or MPLS path cost cannot compensate for a wrong 802.1Q tag.

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