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 60

Question 590

In a separate fictional JNCIS-SP lab review for Stonefield Telecom 148, a carrier-edge and core routing team, following a monitored network change window, engineers find: Two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge. What technical principle underlies the right remedy?

  1. Layer 2 switching forwards traffic within the configured VLAN bridge domain.
  2. Bridge-table observations must be interpreted alongside actual physical and logical port membership.
  3. Customer VLAN IDs are not globally unique and require deliberate provider separation.
  4. Route policy controls which eligible nonnative prefixes are intentionally originated into IS-IS.

Explanation

Correct Answer

C:

Customer VLAN IDs are not globally unique and require deliberate provider separation. Two identical inner customer tags remain isolated by separate outer tags or service instances. Use separate outer service tags or forwarding contexts for the distinct customers.

Incorrect Answers

A:

Layer 2 switching forwards traffic within the configured VLAN bridge domain. That relates to circumstances in which hosts connected through a service-provider switch cannot exchange traffic because each port references a different VLAN identifier. Here the problem is that two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge.

B:

Bridge-table observations must be interpreted alongside actual physical and logical port membership. This addresses a situation in which a MAC is learned on an unexpected aggregation interface following a customer circuit move; however, two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge.

D:

Route policy controls which eligible nonnative prefixes are intentionally originated into IS-IS. That option concerns a customer service route never reaches another IS-IS area because the required export policy omits it. The problem here is different: Two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge.

Question 591

In a separate fictional JNCIS-SP lab review for Stonefield Telecom 148, a carrier-edge and core routing team, following a monitored network change window, engineers find: Two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge. Which acceptance finding demonstrates the affected service has recovered?

  1. MAC entries stabilize on the intended interface after repairing the bridge path.
  2. Tagged customer frames enter the intended VLAN while disallowed tags are rejected.
  3. Two identical inner customer tags remain isolated by separate outer tags or service instances.
  4. Remote routers learn intended IPv6 prefixes and forward IPv6 probes end to end.

Explanation

Correct Answer

C:

Two identical inner customer tags remain isolated by separate outer tags or service instances. Use separate outer service tags or forwarding contexts for the distinct customers. Customer VLAN IDs are not globally unique and require deliberate provider separation.

Incorrect Answers

A:

MAC entries stabilize on the intended interface after repairing the bridge path. It is useful for situations where a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables; the reported fault, though, is that two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge.

B:

Tagged customer frames enter the intended VLAN while disallowed tags are rejected. That relates to circumstances in which a provider access port drops customer tagged frames because it was configured for untagged access mode. Here the problem is that two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge.

D:

Remote routers learn intended IPv6 prefixes and forward IPv6 probes end to end. The choice would be appropriate if a core network runs IS-IS for IPv4 but has no IPv6 service reachability after dual-stack activation. Here, two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge.

Question 592

In a separate fictional JNCIS-SP lab review for Stonefield Telecom 148, a carrier-edge and core routing team, following a monitored network change window, engineers find: Two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge. What is the direct residual network risk if the fault remains unresolved?

  1. A repeated VLAN number causes cross-customer broadcast leakage.
  2. Traffic leaks or becomes blackholed at the L2/L3 boundary.
  3. Unnecessary route changes mask a switching defect and prolong the outage.
  4. Packets cannot reach the intended next hop despite a syntactically valid address.

Explanation

Correct Answer

A:

A repeated VLAN number causes cross-customer broadcast leakage. Use separate outer service tags or forwarding contexts for the distinct customers. Customer VLAN IDs are not globally unique and require deliberate provider separation.

Incorrect Answers

B:

Traffic leaks or becomes blackholed at the L2/L3 boundary. It is useful for situations where an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch; the reported fault, though, is that two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge.

C:

Unnecessary route changes mask a switching defect and prolong the outage. That relates to circumstances in which an operator adds an IP route to fix traffic that never leaves a local bridge domain because its destination MAC is unknown. Here the problem is that two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge.

D:

Packets cannot reach the intended next hop despite a syntactically valid address. This addresses a situation in which an IPv6 adjacency uses a link-local next hop, but its interface scope is omitted from the implementation design; however, two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge.

Question 593

At fictional Clearwater Peering 149, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: A MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables. Which targeted remediation best fits the reported behavior?

  1. Check MAC aging and traffic timing before adding disruptive forwarding restrictions.
  2. Reconcile path MTU with the encapsulation overhead and test representative maximum frames.
  3. Investigate Layer 2 topology, bridge membership and possible loop before route-policy changes.
  4. Remove inappropriate edge-port assumptions and verify RSTP role transitions.

Explanation

Correct Answer

C:

Investigate Layer 2 topology, bridge membership and possible loop before route-policy changes. Unexpected MAC movement often points to changing Layer 2 forwarding topology. MAC entries stabilize on the intended interface after repairing the bridge path.

Incorrect Answers

A:

Check MAC aging and traffic timing before adding disruptive forwarding restrictions. This could help if a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop, but not when a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables.

B:

Reconcile path MTU with the encapsulation overhead and test representative maximum frames. This relates to a case where a service-provider QinQ link carries small frames but drops customer frames when the extra VLAN header exceeds the link MTU; the current situation is that a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables.

D:

Remove inappropriate edge-port assumptions and verify RSTP role transitions. That relates to circumstances in which a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior. Here the problem is that a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables.

Question 594

At fictional Clearwater Peering 149, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: A MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables. 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. An Ethernet port's VLAN tagging behavior must match the frames it receives.
  3. A link aggregation group forwards correctly only over members meeting the operational bundle requirements.
  4. Unexpected MAC movement often points to changing Layer 2 forwarding topology.

Explanation

Correct Answer

D:

Unexpected MAC movement often points to changing Layer 2 forwarding topology. Investigate Layer 2 topology, bridge membership and possible loop before route-policy changes. MAC entries stabilize on the intended interface after repairing the bridge path.

Incorrect Answers

A:

Integrated routing and bridging links a bridge domain to an IP routing gateway. It is relevant if customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent, but the reported issue is that a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables.

B:

An Ethernet port's VLAN tagging behavior must match the frames it receives. This could help if a provider access port drops customer tagged frames because it was configured for untagged access mode, but not when a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables.

C:

A link aggregation group forwards correctly only over members meeting the operational bundle requirements. This relates to a case where a bundled uplink has two configured members but only one is usable because the second member's operational parameters differ; the current situation is that a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables.

Question 595

At fictional Clearwater Peering 149, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: A MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables. What direct observation would prove the corrective action worked?

  1. The tenant VLAN reaches only its intended IRB gateway and routing-instance routes.
  2. A test frame relearns the source MAC and later packets forward as known unicast.
  3. MAC entries stabilize on the intended interface after repairing the bridge path.
  4. The unauthorized prefix is absent and approved transit routes remain usable.

Explanation

Correct Answer

C:

MAC entries stabilize on the intended interface after repairing the bridge path. Unexpected MAC movement often points to changing Layer 2 forwarding topology. Investigate Layer 2 topology, bridge membership and possible loop before route-policy changes.

Incorrect Answers

A:

The tenant VLAN reaches only its intended IRB gateway and routing-instance routes. This is applicable when an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch; the present condition is that a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables.

B:

A test frame relearns the source MAC and later packets forward as known unicast. 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 a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables.

D:

The unauthorized prefix is absent and approved transit routes remain usable. This relates to a case where a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy; the current situation is that a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables.

Question 596

At fictional Clearwater Peering 149, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: A MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables. Which failure consequence follows most closely from ignoring this issue?

  1. Repeated flooding and customer frame loss continue despite healthy routes.
  2. Customer hosts appear connected yet cannot communicate.
  3. Traffic leaks or becomes blackholed at the L2/L3 boundary.
  4. A correct label stack is broken by applying the wrong role assumption.

Explanation

Correct Answer

A:

Repeated flooding and customer frame loss continue despite healthy routes. Unexpected MAC movement often points to changing Layer 2 forwarding topology. Investigate Layer 2 topology, bridge membership and possible loop before route-policy changes.

Incorrect Answers

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 a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables.

C:

Traffic leaks or becomes blackholed at the L2/L3 boundary. It is relevant if an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch, but the reported issue is that a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables.

D:

A correct label stack is broken by applying the wrong role assumption. This could help if a network test expects the ingress PE to swap a label that it should actually impose, but not when a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables.

Question 597

In a separate fictional JNCIS-SP lab review for Glenwood Connectivity 150, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: A MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables. What intervention most directly restores the intended routing or switching behavior?

  1. Create or correct the routed IRB interface and associate it with the intended VLAN and routing instance.
  2. Investigate Layer 2 topology, bridge membership and possible loop before route-policy changes.
  3. Use distinct virtual-switch or bridge-domain contexts with explicit interface membership.
  4. Put each tenant's interfaces and routes into the intended routing instances and verify separate lookups.

Explanation

Correct Answer

B:

Investigate Layer 2 topology, bridge membership and possible loop before route-policy changes. MAC entries stabilize on the intended interface after repairing the bridge path. Unexpected MAC movement often points to changing Layer 2 forwarding topology.

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, a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables.

C:

Use distinct virtual-switch or bridge-domain contexts with explicit interface membership. This is applicable when two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services; the present condition is that a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables.

D:

Put each tenant's interfaces and routes into the intended routing instances and verify separate lookups. It is relevant if customer A traffic resolves through Customer B's route because both tenants were inadvertently configured in the same routing table, but the reported issue is that a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables.

Question 598

In a separate fictional JNCIS-SP lab review for Glenwood Connectivity 150, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: A MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables. Which networking principle explains why the proposed correction is appropriate?

  1. Bridge-table observations must be interpreted alongside actual physical and logical port membership.
  2. Unexpected MAC movement often points to changing Layer 2 forwarding topology.
  3. An Ethernet port's VLAN tagging behavior must match the frames it receives.
  4. IS-IS authentication parameters must match for participating routers to exchange protocol information.

Explanation

Correct Answer

B:

Unexpected MAC movement often points to changing Layer 2 forwarding topology. MAC entries stabilize on the intended interface after repairing the bridge path. Investigate Layer 2 topology, bridge membership and possible loop before route-policy changes.

Incorrect Answers

A:

Bridge-table observations must be interpreted alongside actual physical and logical port membership. It addresses a different problem: A MAC is learned on an unexpected aggregation interface following a customer circuit move. Here, a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables.

C:

An Ethernet port's VLAN tagging behavior must match the frames it receives. That could help when a provider access port drops customer tagged frames because it was configured for untagged access mode; here, a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables.

D:

IS-IS authentication parameters must match for participating routers to exchange protocol information. This is applicable when a provider IS-IS circuit stops forming neighbors after the authentication key is changed on only one end; the present condition is that a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables.

Question 599

In a separate fictional JNCIS-SP lab review for Glenwood Connectivity 150, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: A MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables. Which validation result would confirm the design is now functioning?

  1. MAC learning and broadcast tests show separation of the two customers.
  2. MAC entries stabilize on the intended interface after repairing the bridge path.
  3. A correctly sized customer frame traverses the entire provider handoff without drops.
  4. The intended EBGP neighbor becomes Established and exchanges authorized prefixes.

Explanation

Correct Answer

B:

MAC entries stabilize on the intended interface after repairing the bridge path. Investigate Layer 2 topology, bridge membership and possible loop before route-policy changes. Unexpected MAC movement often points to changing Layer 2 forwarding topology.

Incorrect Answers

A:

MAC learning and broadcast tests show separation of the two customers. That option concerns two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services. The problem here is different: A MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables.

C:

A correctly sized customer frame traverses the entire provider handoff without drops. This could matter when a service-provider QinQ link carries small frames but drops customer frames when the extra VLAN header exceeds the link MTU. In this case, a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables.

D:

The intended EBGP neighbor becomes Established and exchanges authorized prefixes. That could help when an external BGP session never reaches Established because the local peer definition uses the wrong remote AS; here, a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables.

Question 600

In a separate fictional JNCIS-SP lab review for Glenwood Connectivity 150, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: A MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables. What likely service impact does this condition create?

  1. Customer broadcasts and potentially sensitive frames cross service boundaries.
  2. Traffic follows an obsolete service path or reaches the wrong customer site.
  3. Repeated flooding and customer frame loss continue despite healthy routes.
  4. Remote sites lose the service route or excessive routes leak into the IGP.

Explanation

Correct Answer

C:

Repeated flooding and customer frame loss continue despite healthy routes. Investigate Layer 2 topology, bridge membership and possible loop before route-policy changes. Unexpected MAC movement often points to changing Layer 2 forwarding topology.

Incorrect Answers

A:

Customer broadcasts and potentially sensitive frames cross service boundaries. The choice would be appropriate if two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services. Here, a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables.

B:

Traffic follows an obsolete service path or reaches the wrong customer site. That option concerns a MAC is learned on an unexpected aggregation interface following a customer circuit move. The problem here is different: A MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables.

D:

Remote sites lose the service route or excessive routes leak into the IGP. This could matter when a static service prefix is missing from OSPF because the export policy was attached but does not match it. In this case, a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables.

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