mcAfee Secure Website
exam =5
exam =6

Exam Code: JN0-364

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

Certification Provider: Juniper

Juniper JN0-364 Questions & Answers

Reliable & Actual Study Materials for JN0-364 Exam Success

69 Questions & Answers with Testing Engine

"JN0-364: Service Provider Routing and Switching, Specialist (JNCIS-SP)" Testing Engine covers all the knowledge points of the real Juniper JN0-364 exam.

The latest actual JN0-364 Questions & Answers from Pass4sure. Everything you need to prepare and get best score at JN0-364 exam easily and quickly.

exam =7
Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable Juniper Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Was: $137.49
Now: $124.99

Juniper JN0-364 Practice Test 66

Question 650

A provider switch receives an unknown destination MAC and a new engineer expects it to unicast to a random uplink. Which statement identifies the key design assumption that failed?

  1. Root design issue: Layer 3 routing HA does not automatically guarantee L2 bridge-control continuity.
  2. The governing rule is: Ethernet forwarding uses bridge-domain context rather than arbitrary IP-route matching.
  3. The key distinction is: Bridges learn source MAC locations and flood unknown destinations within a permitted domain.
  4. Protocol behavior: Layer 2 bridging does not by itself provide IP intersubnet routing.

Explanation

Correct Answer

C:

Correct diagnosis: Bridges learn source MAC locations and flood unknown destinations within a permitted domain. The appropriate action is: Review MAC learning and unknown-unicast handling within the correct bridge domain. The follow-up evidence required is: A frame trace shows only expected domain members receive the unknown destination.

Incorrect Answers

A:

Layer 3 routing HA does not automatically guarantee L2 bridge-control continuity describes a neighboring protocol concern. In this case the controlling fact is bridges learn source MAC locations and flood unknown destinations within a permitted domain. A correct remediation would review MAC learning and unknown-unicast handling within the correct bridge domain and demonstrate: A frame trace shows only expected domain members receive the unknown destination.

B:

The proposed principle concerns another network fault: Ethernet forwarding uses bridge-domain context rather than arbitrary IP-route matching. Here, bridges learn source MAC locations and flood unknown destinations within a permitted domain. The most direct correction is to review MAC learning and unknown-unicast handling within the correct bridge domain, confirmed by a frame trace shows only expected domain members receive the unknown destination.

D:

This response would target a different source scenario: A VLAN provides local host connectivity but hosts cannot reach a different IP subnet through the bridge domain. It cannot establish the current acceptance requirement, which is: A frame trace shows only expected domain members receive the unknown destination. The relevant action is: Review MAC learning and unknown-unicast handling within the correct bridge domain.

Question 651

An IS-IS backbone forms an adjacency but omits IPv6 reachability when the family is not enabled. Which post-change observation most strongly confirms the correction?

  1. Expected observation: A protocol check shows the authorized level and matching adjacency.
  2. Verification result: A destination lookup chooses the intended most specific valid route.
  3. Closeout evidence: IPv6 destination prefixes become visible without disturbing stable IS-IS neighbors.
  4. Acceptance check: The intended most-specific route changes to a valid next hop during failover.

Explanation

Correct Answer

C:

The selected response implements the principle that iS-IS adjacency and IPv6 prefix exchange are separate operational concerns. The engineer should enable and verify the intended IPv6 address-family reachability advertisements. Successful confirmation means: IPv6 destination prefixes become visible without disturbing stable IS-IS neighbors.

Incorrect Answers

A:

The alternative addresses two routers exchange IS-IS Hellos but one rejects the neighbor during area validation, not the present root cause. Here the selected correction must reflect iS-IS adjacency and IPv6 prefix exchange are separate operational concerns. Test for: IPv6 destination prefixes become visible without disturbing stable IS-IS neighbors.

B:

This answer would be more suitable when an engineer chooses an IPv6 route based on the printed address alone without comparing prefix length, where the corrective action is to apply longest-prefix-match route lookup to the IPv6 destination. The failure here is different: IS-IS adjacency and IPv6 prefix exchange are separate operational concerns. Required validation: IPv6 destination prefixes become visible without disturbing stable IS-IS neighbors.

D:

More-specific routes can override an otherwise healthy IPv6 fallback describes a neighboring protocol concern. In this case the controlling fact is iS-IS adjacency and IPv6 prefix exchange are separate operational concerns. A correct remediation would enable and verify the intended IPv6 address-family reachability advertisements and demonstrate: IPv6 destination prefixes become visible without disturbing stable IS-IS neighbors.

Question 652

A new peer sends more customer routes than expected and the team assumes BGP automatically filters unrelated prefixes. What action-and-test pairing directly resolves the case?

  1. Control: Review BGP next-hop reachability and explicit next-hop handling. Accepted result: The internal peer has a valid route to the BGP next hop and installs the prefix.
  2. Action: Check SR label advertisements, segment configuration and installed MPLS forwarding. Evidence: The intended SR transport path forwards without unintended dependence on the retired LDP path.
  3. Repair: Verify IP reachability, routing instance context, TCP transport and session authentication. Check: The TCP peering session reaches Established and remains stable.
  4. Change: Create explicit import policy and prefix limits aligned to customer contracts. Test: Only approved customer prefixes enter the provider's active routing table.

Explanation

Correct Answer

D:

Correct diagnosis: BGP route acceptance must be constrained rather than inferred from neighbor identity. The appropriate action is: Create explicit import policy and prefix limits aligned to customer contracts. The follow-up evidence required is: Only approved customer prefixes enter the provider's active routing table.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A provider's iBGP peer receives a route but cannot resolve the external next hop in its own IGP. The current case specifically calls for: Create explicit import policy and prefix limits aligned to customer contracts. The required observed result is: Only approved customer prefixes enter the provider's active routing table.

B:

This response would target a different source scenario: A provider migrates one path from LDP to SR-MPLS but does not verify the segment-routing forwarding state. It cannot establish the current acceptance requirement, which is: Only approved customer prefixes enter the provider's active routing table. The relevant action is: Create explicit import policy and prefix limits aligned to customer contracts.

C:

Verify IP reachability, routing instance context, TCP transport and session authentication is a relevant step for the separate scenario in which a BGP peer is stuck in Active after a maintenance window even though the remote address is configured. It does not directly fix this case. Instead create explicit import policy and prefix limits aligned to customer contracts; verify: Only approved customer prefixes enter the provider's active routing table.

Question 653

A failover plan relies on one physical interface carrying several links and calls it a redundant LAG. Which post-change observation most strongly confirms the correction?

  1. Acceptance check: Only the intended master forwards for the virtual gateway under steady state.
  2. The test confirms that a member link failure leaves traffic flowing through a remaining usable member.
  3. Expected observation: A planned switchover test documents forwarding and neighbor behavior against the HA design.
  4. Verification result: A controlled BPDU causes the expected protected-port response.

Explanation

Correct Answer

B:

The case turns on the distinction that link aggregation improves availability only when member links and topology provide meaningful redundancy. Apply this concrete engineering step: Distinguish member-link redundancy from a single physical failure domain. An acceptable verification outcome is: A member link failure leaves traffic flowing through a remaining usable member.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is vRRP provides a master and backup mechanism for a shared virtual default gateway, while this scenario depends on link aggregation improves availability only when member links and topology provide meaningful redundancy. Verify the correction with: A member link failure leaves traffic flowing through a remaining usable member.

C:

The proposed principle concerns another network fault: Forwarding-plane continuity does not prove control-plane routing continuity. Here, link aggregation improves availability only when member links and topology provide meaningful redundancy. The most direct correction is to distinguish member-link redundancy from a single physical failure domain, confirmed by a member link failure leaves traffic flowing through a remaining usable member.

D:

That result would be useful for a different failure, namely: An edge port connected to a user device unexpectedly receives BPDUs from an unauthorized switch. The current case specifically calls for: Distinguish member-link redundancy from a single physical failure domain. The required observed result is: A member link failure leaves traffic flowing through a remaining usable member.

Question 654

A carrier attachment must not allow a customer switch to become the provider's root bridge. Which corrective action and confirmation pair is most appropriate?

  1. Change: Evaluate BFD liveness detection with the associated routing protocol. Test: A controlled forwarding failure is detected within the approved target.
  2. Implement: Align region identity, revision and VLAN mapping as required. Verify: A region status check shows the intended shared instance mapping.
  3. Control: Review root bridge priority and MAC-based bridge identifier comparison. Accepted result: The intended device is root under the tested priorities and tie-breakers.
  4. Action: Review root protection at the provider-facing boundary. Evidence: A superior BPDU test does not move the approved provider root.

Explanation

Correct Answer

D:

This is the model-intended best choice because root protection can prevent undesired superior-root claims from changing root placement. The targeted correction is to review root protection at the provider-facing boundary. Validate it by observing that a superior BPDU test does not move the approved provider root.

Incorrect Answers

A:

Evaluate BFD liveness detection with the associated routing protocol is a relevant step for the separate scenario in which a routing peer detects a dead neighbor too slowly for a real-time service even when the interface stays up. It does not directly fix this case. Instead review root protection at the provider-facing boundary; verify: A superior BPDU test does not move the approved provider root.

B:

The alternative addresses two MSTP switches place the same VLAN into different instances due to region configuration drift, not the present root cause. Here the selected correction must reflect root protection can prevent undesired superior-root claims from changing root placement. Test for: A superior BPDU test does not move the approved provider root.

C:

This answer would be more suitable when a switch operator treats the highest bridge ID as the guaranteed STP root, where the corrective action is to review root bridge priority and MAC-based bridge identifier comparison. The failure here is different: Root protection can prevent undesired superior-root claims from changing root placement. Required validation: A superior BPDU test does not move the approved provider root.

Question 655

An edge port connected to a user device unexpectedly receives BPDUs from an unauthorized switch. Which corrective action and confirmation pair is most appropriate?

  1. Repair: Align region identity, revision and VLAN mapping as required. Check: A region status check shows the intended shared instance mapping.
  2. Change: Review root bridge priority and MAC-based bridge identifier comparison. Test: The intended device is root under the tested priorities and tie-breakers.
  3. Implement: Trace frame classification and virtual-switch bridge-domain association. Verify: A tagged test frame reaches the approved remote port in the same domain.
  4. Control: Apply suitable BPDU protection according to edge-port policy. Accepted result: A controlled BPDU causes the expected protected-port response.

Explanation

Correct Answer

D:

Underlying cause: BPDU protection can prevent rogue switching from affecting a designated edge port. Corrective action: apply suitable BPDU protection according to edge-port policy. Verify the outcome: A controlled BPDU causes the expected protected-port response.

Incorrect Answers

A:

The proposed principle concerns another network fault: MSTP region agreement affects how instances interoperate across links. Here, bPDU protection can prevent rogue switching from affecting a designated edge port. The most direct correction is to apply suitable BPDU protection according to edge-port policy, confirmed by a controlled BPDU causes the expected protected-port response.

B:

That result would be useful for a different failure, namely: A switch operator treats the highest bridge ID as the guaranteed STP root. The current case specifically calls for: Apply suitable BPDU protection according to edge-port policy. The required observed result is: A controlled BPDU causes the expected protected-port response.

C:

This response would target a different source scenario: A port belongs to a VLAN but traffic to a remote site is forwarded through a different bridge domain. It cannot establish the current acceptance requirement, which is: A controlled BPDU causes the expected protected-port response. The relevant action is: Apply suitable BPDU protection according to edge-port policy.

Question 656

Two routers advertise identical OSPF router IDs and their link-state information becomes inconsistent. Which change best corrects the failure without losing the intended design?

  1. Corrective action: Assign distinct stable router IDs and clear stale protocol state using an approved procedure.
  2. Apply this control: Apply a safe approved OSPF process refresh and verify advertised router identity.
  3. Remediation: Verify compatible network and Hello parameters including mask where applicable.
  4. Recommended change: Check import destinations, next-hop resolution and effective routes in every receiving table.

Explanation

Correct Answer

A:

This is the model-intended best choice because oSPF identifies speakers by router ID, which must be unique inside a routing domain. The targeted correction is to assign distinct stable router IDs and clear stale protocol state using an approved procedure. Validate it by observing that each router is uniquely identified and the link-state database converges.

Incorrect Answers

B:

This option overlooks the decisive condition. Its supporting principle is changing router identity may require controlled protocol restart or adjacency reestablishment, while this scenario depends on oSPF identifies speakers by router ID, which must be unique inside a routing domain. Verify the correction with: Each router is uniquely identified and the link-state database converges.

C:

OSPF network-type and Hello compatibility can prevent adjacency formation describes a neighboring protocol concern. In this case the controlling fact is oSPF identifies speakers by router ID, which must be unique inside a routing domain. A correct remediation would assign distinct stable router IDs and clear stale protocol state using an approved procedure and demonstrate: Each router is uniquely identified and the link-state database converges.

D:

The proposed principle concerns another network fault: Imported routes must be validated in the destination lookup context. Here, oSPF identifies speakers by router ID, which must be unique inside a routing domain. The most direct correction is to assign distinct stable router IDs and clear stale protocol state using an approved procedure, confirmed by each router is uniquely identified and the link-state database converges.

Question 657

A BGP peer is stuck in Active after a maintenance window even though the remote address is configured. Which underlying Junos networking principle explains the failure?

  1. Protocol behavior: Neighbor state must be traced through transport before modifying route policy.
  2. Underlying principle: BGP group-level export policies must preserve customer routing isolation.
  3. Root design issue: iBGP can preserve externally learned next-hop information that internal speakers must resolve.
  4. The governing rule is: Labels are generally meaningful within the forwarding context where they are allocated.

Explanation

Correct Answer

A:

Underlying cause: Neighbor state must be traced through transport before modifying route policy. Corrective action: verify IP reachability, routing instance context, TCP transport and session authentication. Verify the outcome: The TCP peering session reaches Established and remains stable.

Incorrect Answers

B:

Split export policy by authorized customer scope and verify negative advertisements is a relevant step for the separate scenario in which one customer’s new prefixes are advertised to a second unrelated customer via a shared export group. It does not directly fix this case. Instead verify IP reachability, routing instance context, TCP transport and session authentication; verify: The TCP peering session reaches Established and remains stable.

C:

The alternative addresses a provider's iBGP peer receives a route but cannot resolve the external next hop in its own IGP, not the present root cause. Here the selected correction must reflect neighbor state must be traced through transport before modifying route policy. Test for: The TCP peering session reaches Established and remains stable.

D:

This answer would be more suitable when an operator assumes MPLS labels are globally unique across the provider network, where the corrective action is to explain local label significance and neighbor label binding. The failure here is different: Neighbor state must be traced through transport before modifying route policy. Required validation: The TCP peering session reaches Established and remains stable.

Question 658

After enabling OSPFv3 a provider sees IPv6 neighbors but no remote IPv6 customer prefixes. What should the operations engineer do first to address the stated fault?

  1. Recommended change: Inspect longest-match results and forwarding routes for the specific destination.
  2. Next step: Test effective MTU and path MTU discovery across the encapsulated route.
  3. Corrective action: Enable and verify the intended IPv6 address-family reachability advertisements.
  4. Apply this control: Check OSPFv3 family enablement, LSAs and routing-policy route acceptance.

Explanation

Correct Answer

D:

This option addresses the stated case rather than another networking issue. Principle: Neighbor establishment is distinct from prefix advertisement and installation. Remedy: Check OSPFv3 family enablement, LSAs and routing-policy route acceptance. Proof: The accepted OSPFv3 IPv6 routes become active in the expected routing table.

Incorrect Answers

A:

More-specific routes can override an otherwise healthy IPv6 fallback describes a neighboring protocol concern. In this case the controlling fact is neighbor establishment is distinct from prefix advertisement and installation. A correct remediation would check OSPFv3 family enablement, LSAs and routing-policy route acceptance and demonstrate: The accepted OSPFv3 IPv6 routes become active in the expected routing table.

B:

The proposed principle concerns another network fault: GRE encapsulation overhead can expose MTU blackholes for larger payloads. Here, neighbor establishment is distinct from prefix advertisement and installation. The most direct correction is to check OSPFv3 family enablement, LSAs and routing-policy route acceptance, confirmed by the accepted OSPFv3 IPv6 routes become active in the expected routing table.

C:

That result would be useful for a different failure, namely: An IS-IS backbone forms an adjacency but omits IPv6 reachability when the family is not enabled. The current case specifically calls for: Check OSPFv3 family enablement, LSAs and routing-policy route acceptance. The required observed result is: The accepted OSPFv3 IPv6 routes become active in the expected routing table.

Question 659

A native untagged VLAN mismatch makes two switches place the same untagged frames into different segments. What should the operations engineer do first to address the stated fault?

  1. Remediation: Trace trunk authorization, bridge-domain membership and MAC learning across the path.
  2. Recommended change: Deploy or validate an integrated routing and bridging L3 interface and gateway.
  3. Next step: Review root bridge priority and MAC-based bridge identifier comparison.
  4. Corrective action: Align untagged or native VLAN behavior with explicit port configuration.

Explanation

Correct Answer

D:

The critical observation is: Untagged frame classification is local to the receiving interface. Correct it by taking this action: Align untagged or native VLAN behavior with explicit port configuration. Confirm the outcome with: The same controlled untagged frame maps to the intended VLAN on both sides.

Incorrect Answers

A:

The alternative addresses a site complains an IRB gateway answers locally but the downstream VLAN has no remote MAC learning, not the present root cause. Here the selected correction must reflect untagged frame classification is local to the receiving interface. Test for: The same controlled untagged frame maps to the intended VLAN on both sides.

B:

This answer would be more suitable when a VLAN provides local host connectivity but hosts cannot reach a different IP subnet through the bridge domain, where the corrective action is to deploy or validate an integrated routing and bridging L3 interface and gateway. The failure here is different: Untagged frame classification is local to the receiving interface. Required validation: The same controlled untagged frame maps to the intended VLAN on both sides.

C:

This option overlooks the decisive condition. Its supporting principle is traditional spanning-tree root election favors the lowest bridge ID, while this scenario depends on untagged frame classification is local to the receiving interface. Verify the correction with: The same controlled untagged frame maps to the intended VLAN on both sides.

Question 660

A Routing Engine switchover retains data-plane traffic briefly but causes OSPF adjacencies to restart. Which corrective action and confirmation pair is most appropriate?

  1. Repair: Check whether GRES is paired with the intended GR or NSR support and verify protocol state. Check: A planned switchover test documents forwarding and neighbor behavior against the HA design.
  2. Change: Check VRRP group, interface, priority, advertisements and tracking conditions. Test: The backup assumes master role and clients retain access to the virtual gateway.
  3. Implement: Review VRRP virtual router roles, priority and failover behavior. Verify: Only the intended master forwards for the virtual gateway under steady state.
  4. Control: Inspect link-state databases and SPF output on affected routers. Accepted result: A shared stable topology produces consistent path computation.

Explanation

Correct Answer

A:

This option addresses the stated case rather than another networking issue. Principle: Forwarding-plane continuity does not prove control-plane routing continuity. Remedy: Check whether GRES is paired with the intended GR or NSR support and verify protocol state. Proof: A planned switchover test documents forwarding and neighbor behavior against the HA design.

Incorrect Answers

B:

This response would target a different source scenario: A VRRP backup router does not take over when the primary gateway interface is disabled. It cannot establish the current acceptance requirement, which is: A planned switchover test documents forwarding and neighbor behavior against the HA design. The relevant action is: Check whether GRES is paired with the intended GR or NSR support and verify protocol state.

C:

Review VRRP virtual router roles, priority and failover behavior is a relevant step for the separate scenario in which two edge routers advertise one gateway service and an engineer expects both to be virtual master without a redundancy plan. It does not directly fix this case. Instead check whether GRES is paired with the intended GR or NSR support and verify protocol state; verify: A planned switchover test documents forwarding and neighbor behavior against the HA design.

D:

The alternative addresses a site sees different OSPF routes after a topology edit and declares the protocol failed without checking LSDB consistency, not the present root cause. Here the selected correction must reflect forwarding-plane continuity does not prove control-plane routing continuity. Test for: A planned switchover test documents forwarding and neighbor behavior against the HA design.

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