McAfee Secured

Exam Code: JN0-364

Exam Name: Service Provider Routing and Switching, Specialist (JNCIS-SP)

Certification Provider: Juniper

100% Juniper JN0-364 Guaranteed Success With Testking Training Materials

Get Real JN0-364 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

69 Questions & Answers with Testing Engine

"Service Provider Routing and Switching, Specialist (JNCIS-SP) Exam", also known as JN0-364 exam, is a Juniper certification exam.

Pass your tests with the always up-to-date JN0-364 Exam Engine. Your JN0-364 training materials keep you at the head of the pack!

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Was: $137.49
Now: $124.99

Juniper JN0-364 Practice Test 53

Question 520

In a separate fictional JNCIS-SP lab review for Seabrook Metro 130, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: A customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop. What likely service impact does this condition create?

  1. Unnecessary route changes mask a switching defect and prolong the outage.
  2. Customers can inject unapproved Layer 2 traffic into the provider bridge.
  3. IPv6 traffic is entirely lost due to an unsuitable policy match.
  4. Unnecessary filtering interrupts normal bridged service.

Explanation

Correct Answer

D:

Unnecessary filtering interrupts normal bridged service. Check MAC aging and traffic timing before adding disruptive forwarding restrictions. Dynamic MAC entries may age out and be relearned on subsequent traffic.

Incorrect Answers

A:

Unnecessary route changes mask a switching defect and prolong the outage. This relates to a case where an operator adds an IP route to fix traffic that never leaves a local bridge domain because its destination MAC is unknown; the current situation is that a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop.

B:

Customers can inject unapproved Layer 2 traffic into the provider bridge. It is useful for situations where an interface permits every customer VLAN tag despite a contract listing only two approved VLANs; the reported fault, though, is that a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop.

C:

IPv6 traffic is entirely lost due to an unsuitable policy match. That relates to circumstances in which a prefix-list filter written for IPv4 is applied conceptually to IPv6 routing, and all intended IPv6 routes vanish. Here the problem is that a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop.

Question 521

At fictional Northpoint Access 131, a regional service-provider network, during a planned PE-to-core handoff, operations observes: Provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag. Which configuration or operational correction most directly addresses this failure?

  1. Match the interface VLAN tagging mode to the customer handoff contract and test ingress frames.
  2. Use distinct virtual-switch or bridge-domain contexts with explicit interface membership.
  3. Enable the intended IPv6 OSPFv3 configuration and verify neighbor and route state.
  4. Correct the QinQ service tag mapping and verify the inner customer tag remains intact.

Explanation

Correct Answer

D:

Correct the QinQ service tag mapping and verify the inner customer tag remains intact. Provider bridging can add an outer service VLAN tag while retaining customer VLAN identity. Frame capture shows the intended outer S-tag and unchanged inner customer tag at handoff.

Incorrect Answers

A:

Match the interface VLAN tagging mode to the customer handoff contract and test ingress frames. This could help if a provider access port drops customer tagged frames because it was configured for untagged access mode, but not when provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag.

B:

Use distinct virtual-switch or bridge-domain contexts with explicit interface membership. This relates to a case where two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services; the current situation is that provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag.

C:

Enable the intended IPv6 OSPFv3 configuration and verify neighbor and route state. It is useful for situations where an IPv6 prefix is missing across a point-to-point link because OSPFv2 was configured but OSPFv3 was omitted; the reported fault, though, is that provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag.

Question 522

At fictional Northpoint Access 131, a regional service-provider network, during a planned PE-to-core handoff, operations observes: Provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag. Which Junos forwarding or control-plane rule applies to this case?

  1. Dynamic MAC entries may age out and be relearned on subsequent traffic.
  2. Provider bridging can add an outer service VLAN tag while retaining customer VLAN identity.
  3. Bridge-table observations must be interpreted alongside actual physical and logical port membership.
  4. The IS-IS overload indication can discourage transit use during control-plane recovery.

Explanation

Correct Answer

B:

Provider bridging can add an outer service VLAN tag while retaining customer VLAN identity. Correct the QinQ service tag mapping and verify the inner customer tag remains intact. Frame capture shows the intended outer S-tag and unchanged inner customer tag at handoff.

Incorrect Answers

A:

Dynamic MAC entries may age out and be relearned on subsequent traffic. It is relevant if a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop, but the reported issue is that provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag.

C:

Bridge-table observations must be interpreted alongside actual physical and logical port membership. This relates to a case where a MAC is learned on an unexpected aggregation interface following a customer circuit move; the current situation is that provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag.

D:

The IS-IS overload indication can discourage transit use during control-plane recovery. It is useful for situations where a newly rebooted core router attracts transit traffic while its forwarding state is still being restored; the reported fault, though, is that provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag.

Question 523

At fictional Northpoint Access 131, a regional service-provider network, during a planned PE-to-core handoff, operations observes: Provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag. What operational evidence best establishes successful remediation?

  1. A test frame relearns the source MAC and later packets forward as known unicast.
  2. Tagged customer frames enter the intended VLAN while disallowed tags are rejected.
  3. Protection triggers on test violations and normal subscriber frames still forward.
  4. Frame capture shows the intended outer S-tag and unchanged inner customer tag at handoff.

Explanation

Correct Answer

D:

Frame capture shows the intended outer S-tag and unchanged inner customer tag at handoff. Provider bridging can add an outer service VLAN tag while retaining customer VLAN identity. Correct the QinQ service tag mapping and verify the inner customer tag remains intact.

Incorrect Answers

A:

A test frame relearns the source MAC and later packets forward as known unicast. This is applicable when a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop; the present condition is that provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag.

B:

Tagged customer frames enter the intended VLAN while disallowed tags are rejected. It is relevant if a provider access port drops customer tagged frames because it was configured for untagged access mode, but the reported issue is that provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag.

C:

Protection triggers on test violations and normal subscriber frames still forward. This could help if a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards, but not when provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag.

Question 524

At fictional Northpoint Access 131, a regional service-provider network, during a planned PE-to-core handoff, operations observes: Provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag. Which operational harm would persist without the intended correction?

  1. Unnecessary filtering interrupts normal bridged service.
  2. Customer hosts appear connected yet cannot communicate.
  3. Repeated control-plane resets withdraw customer routes.
  4. Subscriber VLANs collide or customer traffic arrives in the wrong service.

Explanation

Correct Answer

D:

Subscriber VLANs collide or customer traffic arrives in the wrong service. Provider bridging can add an outer service VLAN tag while retaining customer VLAN identity. Correct the QinQ service tag mapping and verify the inner customer tag remains intact.

Incorrect Answers

A:

Unnecessary filtering interrupts normal bridged service. That could help when a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop; here, provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag.

B:

Customer hosts appear connected yet cannot communicate. This is applicable when hosts connected through a service-provider switch cannot exchange traffic because each port references a different VLAN identifier; the present condition is that provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag.

C:

Repeated control-plane resets withdraw customer routes. It is relevant if a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions, but the reported issue is that provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag.

Question 525

In a separate fictional JNCIS-SP lab review for Linden Point 132, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: Provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag. What should the Junos specialist change first to resolve this specific fault?

  1. Create or correct the routed IRB interface and associate it with the intended VLAN and routing instance.
  2. Correct permitted VLAN membership on both logical ports and validate MAC learning in the same broadcast domain.
  3. Assign planned bridge priorities and verify root and alternate port roles.
  4. Correct the QinQ service tag mapping and verify the inner customer tag remains intact.

Explanation

Correct Answer

D:

Correct the QinQ service tag mapping and verify the inner customer tag remains intact. Frame capture shows the intended outer S-tag and unchanged inner customer tag at handoff. Provider bridging can add an outer service VLAN tag while retaining customer VLAN identity.

Incorrect Answers

A:

Create or correct the routed IRB interface and associate it with the intended VLAN and routing instance. This could matter when customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent. In this case, provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag.

B:

Correct permitted VLAN membership on both logical ports and validate MAC learning in the same broadcast domain. That could help when hosts connected through a service-provider switch cannot exchange traffic because each port references a different VLAN identifier; here, provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag.

C:

Assign planned bridge priorities and verify root and alternate port roles. This is applicable when a low-capacity access switch becomes STP root after a new bridge priority setting; the present condition is that provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag.

Question 526

In a separate fictional JNCIS-SP lab review for Linden Point 132, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: Provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag. What technical principle underlies the right remedy?

  1. Dynamic MAC entries may age out and be relearned on subsequent traffic.
  2. Provider bridging can add an outer service VLAN tag while retaining customer VLAN identity.
  3. Unexpected MAC movement often points to changing Layer 2 forwarding topology.
  4. LDP distributes reachability labels while RSVP-TE can enforce explicit traffic-engineering paths.

Explanation

Correct Answer

B:

Provider bridging can add an outer service VLAN tag while retaining customer VLAN identity. Frame capture shows the intended outer S-tag and unchanged inner customer tag at handoff. Correct the QinQ service tag mapping and verify the inner customer tag remains intact.

Incorrect Answers

A:

Dynamic MAC entries may age out and be relearned on subsequent traffic. It addresses a different problem: A customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop. Here, provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag.

C:

Unexpected MAC movement often points to changing Layer 2 forwarding topology. That could help when a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables; here, provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag.

D:

LDP distributes reachability labels while RSVP-TE can enforce explicit traffic-engineering paths. This is applicable when a tunnel intended for RSVP engineering instead uses unconstrained LDP forwarding after a route-resolution change; the present condition is that provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag.

Question 527

In a separate fictional JNCIS-SP lab review for Linden Point 132, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: Provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag. Which acceptance finding demonstrates the affected service has recovered?

  1. Local hosts reach the IRB gateway and authorized routed subnets beyond it.
  2. The tenant VLAN reaches only its intended IRB gateway and routing-instance routes.
  3. The active label operation now uses the recovered egress next hop.
  4. Frame capture shows the intended outer S-tag and unchanged inner customer tag at handoff.

Explanation

Correct Answer

D:

Frame capture shows the intended outer S-tag and unchanged inner customer tag at handoff. Correct the QinQ service tag mapping and verify the inner customer tag remains intact. Provider bridging can add an outer service VLAN tag while retaining customer VLAN identity.

Incorrect Answers

A:

Local hosts reach the IRB gateway and authorized routed subnets beyond it. That option concerns customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent. The problem here is different: Provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag.

B:

The tenant VLAN reaches only its intended IRB gateway and routing-instance routes. It addresses a different problem: An IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. Here, provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag.

C:

The active label operation now uses the recovered egress next hop. This could matter when after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device. In this case, provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag.

Question 528

In a separate fictional JNCIS-SP lab review for Linden Point 132, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: Provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag. What is the direct residual network risk if the fault remains unresolved?

  1. Subscriber VLANs collide or customer traffic arrives in the wrong service.
  2. Excessive flooding consumes bandwidth and exposes traffic across unintended ports.
  3. Traffic leaks or becomes blackholed at the L2/L3 boundary.
  4. Intra-area routes never propagate between connected devices.

Explanation

Correct Answer

A:

Subscriber VLANs collide or customer traffic arrives in the wrong service. Correct the QinQ service tag mapping and verify the inner customer tag remains intact. Provider bridging can add an outer service VLAN tag while retaining customer VLAN identity.

Incorrect Answers

B:

Excessive flooding consumes bandwidth and exposes traffic across unintended ports. That option concerns an edge switch floods ordinary known unicast frames because it never learns the destination MAC on the expected port. The problem here is different: Provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag.

C:

Traffic leaks or becomes blackholed at the L2/L3 boundary. It addresses a different problem: An IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. Here, provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag.

D:

Intra-area routes never propagate between connected devices. This could matter when a Level 1 IS-IS adjacency fails between routers with different area addresses even though the physical link is up. In this case, provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag.

Question 529

At fictional Harborview ISP 133, a regional service-provider network, during a two-site transit migration, operations observes: Customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent. Which targeted remediation best fits the reported behavior?

  1. Create or correct the routed IRB interface and associate it with the intended VLAN and routing instance.
  2. Review bridge-domain membership, MAC learning and aging behavior and correct the affected interface configuration.
  3. Use distinct virtual-switch or bridge-domain contexts with explicit interface membership.
  4. Inspect LSDB sequence and flooding state and repair the affected adjacency.

Explanation

Correct Answer

A:

Create or correct the routed IRB interface and associate it with the intended VLAN and routing instance. Integrated routing and bridging links a bridge domain to an IP routing gateway. Local hosts reach the IRB gateway and authorized routed subnets beyond it.

Incorrect Answers

B:

Review bridge-domain membership, MAC learning and aging behavior and correct the affected interface configuration. The choice would be appropriate if an edge switch floods ordinary known unicast frames because it never learns the destination MAC on the expected port. Here, customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent.

C:

Use distinct virtual-switch or bridge-domain contexts with explicit interface membership. That option concerns two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services. The problem here is different: Customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent.

D:

Inspect LSDB sequence and flooding state and repair the affected adjacency. It addresses a different problem: A remote PE misses a new loopback route because IS-IS link-state flooding is incomplete after an adjacency reset. Here, customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent.

Question 530

At fictional Harborview ISP 133, a regional service-provider network, during a two-site transit migration, operations observes: Customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent. Why is this particular correction the best fit for the stated defect?

  1. Integrated routing and bridging links a bridge domain to an IP routing gateway.
  2. Layer 2 switching forwards traffic within the configured VLAN bridge domain.
  3. Customer VLAN IDs are not globally unique and require deliberate provider separation.
  4. The OSPF router ID uniquely identifies a router in link-state advertisements.

Explanation

Correct Answer

A:

Integrated routing and bridging links a bridge domain to an IP routing gateway. Create or correct the routed IRB interface and associate it with the intended VLAN and routing instance. Local hosts reach the IRB gateway and authorized routed subnets beyond it.

Incorrect Answers

B:

Layer 2 switching forwards traffic within the configured VLAN bridge domain. This addresses a situation in which hosts connected through a service-provider switch cannot exchange traffic because each port references a different VLAN identifier; however, customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent.

C:

Customer VLAN IDs are not globally unique and require deliberate provider separation. The choice would be appropriate if two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge. Here, customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent.

D:

The OSPF router ID uniquely identifies a router in link-state advertisements. That option concerns two routers in the same routing domain advertise the same OSPF router ID after cloning a lab template. The problem here is different: Customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent.

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