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 13

Question 120

A network operator assumes a GRE tunnel encrypts customer packets merely because they are encapsulated. What action-and-test pairing directly resolves the case?

  1. Repair: Restore underlay endpoint reachability and then validate the inner tunnel route. Check: Both outer endpoint probes and inner traffic succeed after repair.
  2. Change: Review IPv6 path MTU discovery and endpoint fragmentation requirements. Test: The sender adapts to a validated path MTU and payload delivery succeeds.
  3. Implement: Distinguish tunneling encapsulation from confidentiality protection. Verify: The security design adds an appropriate protected transport where needed.
  4. Control: Account for outer IP and GRE header overhead in the MTU design. Accepted result: A large packet test respects the effective tunnel MTU without unwanted loss.

Explanation

Correct Answer

C:

This option addresses the stated case rather than another networking issue. Principle: GRE by itself does not provide encryption or authenticated confidentiality. Remedy: Distinguish tunneling encapsulation from confidentiality protection. Proof: The security design adds an appropriate protected transport where needed.

Incorrect Answers

A:

This answer would be more suitable when a GRE tunnel over an IPv4 core stops passing traffic immediately after an underlay route withdraws, where the corrective action is to restore underlay endpoint reachability and then validate the inner tunnel route. The failure here is different: GRE by itself does not provide encryption or authenticated confidentiality. Required validation: The security design adds an appropriate protected transport where needed.

B:

This option overlooks the decisive condition. Its supporting principle is intermediate IPv6 routers do not perform ordinary IPv4-style fragmentation of transit packets, while this scenario depends on gRE by itself does not provide encryption or authenticated confidentiality. Verify the correction with: The security design adds an appropriate protected transport where needed.

D:

The proposed principle concerns another network fault: Encapsulation reduces effective payload MTU unless transport accommodates the extra headers. Here, gRE by itself does not provide encryption or authenticated confidentiality. The most direct correction is to distinguish tunneling encapsulation from confidentiality protection, confirmed by the security design adds an appropriate protected transport where needed.

Question 121

A trunk permits VLAN 110 but excludes VLAN 120 while users on VLAN 120 report isolation from the remote switch. What should the operations engineer do first to address the stated fault?

  1. Corrective action: Evaluate BFD liveness detection with the associated routing protocol.
  2. Apply this control: Verify VLAN or bridge-domain membership and its L3 IRB binding.
  3. Remediation: Review allowed VLAN membership on both trunk endpoints.
  4. Recommended change: Trace Layer 2 topology, learned MACs and spanning-tree or Ethernet loop defenses.

Explanation

Correct Answer

C:

The critical observation is: A trunk carries only its configured authorized VLANs. Correct it by taking this action: Review allowed VLAN membership on both trunk endpoints. Confirm the outcome with: Both permitted VLAN test flows cross while an explicitly denied VLAN stays blocked.

Incorrect Answers

A:

This response would target a different source scenario: A routing peer detects a dead neighbor too slowly for a real-time service even when the interface stays up. It cannot establish the current acceptance requirement, which is: Both permitted VLAN test flows cross while an explicitly denied VLAN stays blocked. The relevant action is: Review allowed VLAN membership on both trunk endpoints.

B:

Verify VLAN or bridge-domain membership and its L3 IRB binding is a relevant step for the separate scenario in which an IRB interface is present but an operator assumes it creates a bridge domain automatically. It does not directly fix this case. Instead review allowed VLAN membership on both trunk endpoints; verify: Both permitted VLAN test flows cross while an explicitly denied VLAN stays blocked.

D:

This answer would be more suitable when an operator tries to solve a MAC-learning loop by adding a static IP route in the core, where the corrective action is to trace Layer 2 topology, learned MACs and spanning-tree or Ethernet loop defenses. The failure here is different: A trunk carries only its configured authorized VLANs. Required validation: Both permitted VLAN test flows cross while an explicitly denied VLAN stays blocked.

Question 122

An IPv6 BGP route is accepted but cannot be forwarded because its next hop lacks neighbor resolution. What assessment accurately links the fault to its correction?

  1. Root issue: IPv4 operational success does not prove IPv6 forwarding configuration. Correction: Validate IPv6 addressing, neighbor discovery and inet6 routing separately.
  2. Cause: The IS-IS DIS concept applies to LANs rather than ordinary point-to-point links. Response: Differentiate multiaccess DIS election from point-to-point adjacency behavior.
  3. Diagnosis: OSPFv3 has protocol-specific requirements for neighbor exchange and IPv6 routing. Action: Review the IPv6 OSPFv3 address-family and interface adjacency model.
  4. Explanation: An IPv6 BGP route requires a resolvable eligible next hop for forwarding. Repair: Verify IPv6 next-hop reachability and Neighbor Discovery on the outgoing path.

Explanation

Correct Answer

D:

This option addresses the stated case rather than another networking issue. Principle: An IPv6 BGP route requires a resolvable eligible next hop for forwarding. Remedy: Verify IPv6 next-hop reachability and Neighbor Discovery on the outgoing path. Proof: The route installs with the expected IPv6 next hop and packet delivery succeeds.

Incorrect Answers

A:

IPv4 operational success does not prove IPv6 forwarding configuration describes a neighboring protocol concern. In this case the controlling fact is an IPv6 BGP route requires a resolvable eligible next hop for forwarding. A correct remediation would verify IPv6 next-hop reachability and Neighbor Discovery on the outgoing path and demonstrate: The route installs with the expected IPv6 next hop and packet delivery succeeds.

B:

The proposed principle concerns another network fault: The IS-IS DIS concept applies to LANs rather than ordinary point-to-point links. Here, an IPv6 BGP route requires a resolvable eligible next hop for forwarding. The most direct correction is to verify IPv6 next-hop reachability and Neighbor Discovery on the outgoing path, confirmed by the route installs with the expected IPv6 next hop and packet delivery succeeds.

C:

That result would be useful for a different failure, namely: An operator assumes OSPFv3 must form using the same interface and address settings as OSPFv2. The current case specifically calls for: Verify IPv6 next-hop reachability and Neighbor Discovery on the outgoing path. The required observed result is: The route installs with the expected IPv6 next hop and packet delivery succeeds.

Question 123

A provider engineer treats a BGP OPEN message as if it already advertises reachable customer prefixes. Which cause-and-remedy pairing reflects the observed problem?

  1. Fault mechanism: IPv4 BGP session liveness does not prove IPv6 family route exchange. Remediation: Inspect inet6 family negotiation, filters and IPv6 next-hop validity.
  2. Root issue: BGP message types have separate roles in session formation and reachability exchange. Correction: Distinguish session negotiation from UPDATE message route advertisements.
  3. Cause: BGP route acceptance must be constrained rather than inferred from neighbor identity. Response: Create explicit import policy and prefix limits aligned to customer contracts.
  4. Diagnosis: Labels are generally meaningful within the forwarding context where they are allocated. Action: Explain local label significance and neighbor label binding.

Explanation

Correct Answer

B:

Underlying cause: BGP message types have separate roles in session formation and reachability exchange. Corrective action: distinguish session negotiation from UPDATE message route advertisements. Verify the outcome: A packet trace shows OPEN and KEEPALIVE before accepted UPDATE information.

Incorrect Answers

A:

The alternative addresses a dual-stack peer is Established but the IPv6 customer route is absent, not the present root cause. Here the selected correction must reflect bGP message types have separate roles in session formation and reachability exchange. Test for: A packet trace shows OPEN and KEEPALIVE before accepted UPDATE information.

C:

This option overlooks the decisive condition. Its supporting principle is bGP route acceptance must be constrained rather than inferred from neighbor identity, while this scenario depends on bGP message types have separate roles in session formation and reachability exchange. Verify the correction with: A packet trace shows OPEN and KEEPALIVE before accepted UPDATE information.

D:

Labels are generally meaningful within the forwarding context where they are allocated describes a neighboring protocol concern. In this case the controlling fact is bGP message types have separate roles in session formation and reachability exchange. A correct remediation would distinguish session negotiation from UPDATE message route advertisements and demonstrate: A packet trace shows OPEN and KEEPALIVE before accepted UPDATE information.

Question 124

A BGP export policy matches a community but no routes leave the peer after a group-level policy reorder. A reviewer requires a remedy and concrete test evidence. Which pairing fits?

  1. Change: Compare MED use with actual prior BGP decision attributes and neighbor policy. Test: A captured received-path comparison explains which attribute selected the route.
  2. Implement: Review reservation constraints and available resources rather than resetting all label sessions. Verify: A compatible bandwidth or path choice allows the target RSVP LSP to establish.
  3. Control: Inspect effective group and neighbor export policy evaluation order. Accepted result: A neighbor route view confirms the approved community-tagged routes are sent.
  4. Action: Distinguish an advertised inbound hint from neighboring-AS route policy decisions. Evidence: A controlled route lookup confirms the neighbor's actual selected entry path.

Explanation

Correct Answer

C:

This is the model-intended best choice because policy inheritance and term action order affect BGP route advertisement. The targeted correction is to inspect effective group and neighbor export policy evaluation order. Validate it by observing that a neighbor route view confirms the approved community-tagged routes are sent.

Incorrect Answers

A:

That result would be useful for a different failure, namely: An operator changes MED and sees no route change because the target AS prioritizes other attributes. The current case specifically calls for: Inspect effective group and neighbor export policy evaluation order. The required observed result is: A neighbor route view confirms the approved community-tagged routes are sent.

B:

This response would target a different source scenario: An RSVP-signaled LSP enters a failed state after a link bandwidth change. It cannot establish the current acceptance requirement, which is: A neighbor route view confirms the approved community-tagged routes are sent. The relevant action is: Inspect effective group and neighbor export policy evaluation order.

D:

The alternative addresses an inbound MED is assumed to control outgoing traffic even though the receiving network has its own path-selection policies, not the present root cause. Here the selected correction must reflect policy inheritance and term action order affect BGP route advertisement. Test for: A neighbor route view confirms the approved community-tagged routes are sent.

Question 125

OSPF route preference changes after a new link is added and a latency-sensitive service takes the wrong path. What remediation is most directly applicable?

  1. Apply this control: Review hierarchical OSPF backbone attachment and area border placement.
  2. Remediation: Compare Hello/Dead event logs with loss and interface errors before tuning timers.
  3. Recommended change: Review filter-based forwarding classification and the intended next-table selection.
  4. Next step: Review each interface's OSPF metric and compare end-to-end computed costs.

Explanation

Correct Answer

D:

The selected response implements the principle that oSPF forwarding decisions depend on cumulative metric, not interface bandwidth labels alone. The engineer should review each interface's OSPF metric and compare end-to-end computed costs. Successful confirmation means: A post-change route view selects the approved shortest path.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is multi-area OSPF design requires attention to backbone connectivity, while this scenario depends on oSPF forwarding decisions depend on cumulative metric, not interface bandwidth labels alone. Verify the correction with: A post-change route view selects the approved shortest path.

B:

Protocol timers need reliable packet delivery and should not mask an unstable link describes a neighboring protocol concern. In this case the controlling fact is oSPF forwarding decisions depend on cumulative metric, not interface bandwidth labels alone. A correct remediation would review each interface's OSPF metric and compare end-to-end computed costs and demonstrate: A post-change route view selects the approved shortest path.

C:

The proposed principle concerns another network fault: Policy-based forwarding can select a routing table independently of the destination lookup in the ingress default table. Here, oSPF forwarding decisions depend on cumulative metric, not interface bandwidth labels alone. The most direct correction is to review each interface's OSPF metric and compare end-to-end computed costs, confirmed by a post-change route view selects the approved shortest path.

Question 126

A data center needs separate spanning trees for VLAN groupings but the plan uses a single root for every VLAN with no design review. Which corrective action and confirmation pair is most appropriate?

  1. Action: Match loop, BPDU and root protection to their different fault conditions. Evidence: Separate fault injections trigger the intended protection per port role.
  2. Repair: Check Q-in-Q input/output encapsulation and rewrite behavior at the handoff. Check: A capture shows the expected outer service tag between provider edges.
  3. Change: Evaluate MSTP instances and explicit VLAN-to-instance mapping. Test: Each VLAN maps to its intended instance and designated root.
  4. Implement: Compare root priority, bridge identifiers and current STP topology status. Verify: A controlled election yields the approved root with documented path changes.

Explanation

Correct Answer

C:

Because mSTP can group VLANs into multiple spanning-tree instances under shared region parameters, the best response is to evaluate MSTP instances and explicit VLAN-to-instance mapping. A reviewer can close the technical case only after confirming that each VLAN maps to its intended instance and designated root.

Incorrect Answers

A:

Match loop, BPDU and root protection to their different fault conditions is a relevant step for the separate scenario in which an engineer uses loop protection as if it served the same purpose as BPDU protection on every port. It does not directly fix this case. Instead evaluate MSTP instances and explicit VLAN-to-instance mapping; verify: Each VLAN maps to its intended instance and designated root.

B:

The alternative addresses tagged frames arrive at the provider edge with the expected inner VLAN but the outer service tag is missing, not the present root cause. Here the selected correction must reflect mSTP can group VLANs into multiple spanning-tree instances under shared region parameters. Test for: Each VLAN maps to its intended instance and designated root.

D:

This option overlooks the decisive condition. Its supporting principle is configuration intent must be verified against the actual elected spanning-tree root, while this scenario depends on mSTP can group VLANs into multiple spanning-tree instances under shared region parameters. Verify the correction with: Each VLAN maps to its intended instance and designated root.

Question 127

An engineer assumes both routers must reach Full with every speaker on a broadcast network. A reviewer requires a remedy and concrete test evidence. Which pairing fits?

  1. Control: Inspect ABR area configuration, route export rules and summary policy. Accepted result: The correct summarized route appears in the receiving area's route table.
  2. Action: Select the correct network-type behavior and inspect the neighbor-state model. Evidence: The point-to-point adjacency forms without an unnecessary DR election.
  3. Repair: Check the expected DR/BDR versus DROther neighbor-state relationships. Check: The neighbor states match expected DR roles and routing converges.
  4. Change: Inspect link quality, interface settings and DIS state before forcing election behavior. Test: A stable neighbor and LAN LSP remain after link faults are corrected.

Explanation

Correct Answer

C:

The case turns on the distinction that oSPF broadcast topology reduces unnecessary full adjacency mesh formation. Apply this concrete engineering step: Check the expected DR/BDR versus DROther neighbor-state relationships. An acceptable verification outcome is: The neighbor states match expected DR roles and routing converges.

Incorrect Answers

A:

The proposed principle concerns another network fault: Interarea reachability depends on the ABR's view and allowed advertisements. Here, oSPF broadcast topology reduces unnecessary full adjacency mesh formation. The most direct correction is to check the expected DR/BDR versus DROther neighbor-state relationships, confirmed by the neighbor states match expected DR roles and routing converges.

B:

That result would be useful for a different failure, namely: An engineer expects a designated router to be elected on a point-to-point OSPF circuit. The current case specifically calls for: Check the expected DR/BDR versus DROther neighbor-state relationships. The required observed result is: The neighbor states match expected DR roles and routing converges.

D:

Inspect link quality, interface settings and DIS state before forcing election behavior is a relevant step for the separate scenario in which an IS-IS LAN is unstable after a VLAN move and DIS changes accompany repeated adjacency loss. It does not directly fix this case. Instead check the expected DR/BDR versus DROther neighbor-state relationships; verify: The neighbor states match expected DR roles and routing converges.

Question 128

A site complains an IRB gateway answers locally but the downstream VLAN has no remote MAC learning. Which combined repair and acceptance criterion is strongest?

  1. Implement: Trace trunk authorization, bridge-domain membership and MAC learning across the path. Verify: Both local and remote MACs learn in the intended bridge domain and hosts communicate.
  2. Control: Distinguish access port traffic from trunk tagging behavior. Accepted result: An end-host packet enters the correct VLAN without requiring endpoint tagging.
  3. Action: Compare the rapid proposal/agreement behavior with traditional timer-dependent transitions. Evidence: A link-failure test shows the supported rapid role transition.
  4. Repair: Generate controlled frames and observe normal learning on the correct bridge domain. Check: A source MAC appears on the expected port after a test frame.

Explanation

Correct Answer

A:

This is the model-intended best choice because a working IRB gateway does not validate all L2 paths and trunk members. The targeted correction is to trace trunk authorization, bridge-domain membership and MAC learning across the path. Validate it by observing that both local and remote MACs learn in the intended bridge domain and hosts communicate.

Incorrect Answers

B:

This option overlooks the decisive condition. Its supporting principle is port mode determines which customer frames are tagged or untagged at the boundary, while this scenario depends on a working IRB gateway does not validate all L2 paths and trunk members. Verify the correction with: Both local and remote MACs learn in the intended bridge domain and hosts communicate.

C:

RSTP can converge faster using explicit roles and handshakes where conditions allow describes a neighboring protocol concern. In this case the controlling fact is a working IRB gateway does not validate all L2 paths and trunk members. A correct remediation would trace trunk authorization, bridge-domain membership and MAC learning across the path and demonstrate: Both local and remote MACs learn in the intended bridge domain and hosts communicate.

D:

The proposed principle concerns another network fault: Dynamic MAC tables are populated by observed frames and need not be prefilled. Here, a working IRB gateway does not validate all L2 paths and trunk members. The most direct correction is to trace trunk authorization, bridge-domain membership and MAC learning across the path, confirmed by both local and remote MACs learn in the intended bridge domain and hosts communicate.

Question 129

A provider chooses segment-routing MPLS but assumes every transit hop needs per-LSP RSVP state. What remediation is most directly applicable?

  1. Remediation: Differentiate IP underlay reachability from LDP or RSVP control state.
  2. Recommended change: Compare RIB selection with forwarding-table installation and next-hop resolution.
  3. Next step: Review segment identifiers and forwarding under SR-MPLS.
  4. Corrective action: Inspect Junos MPLS-related next-hop resolution and available LSP endpoints.

Explanation

Correct Answer

C:

The critical observation is: SR-MPLS can encode forwarding intent using segment labels without per-path RSVP signaling in transit. Correct it by taking this action: Review segment identifiers and forwarding under SR-MPLS. Confirm the outcome with: A test packet follows its segment list through installed SR forwarding.

Incorrect Answers

A:

This response would target a different source scenario: A transport route is reachable through an IP interface but the LSP still fails due to incomplete label distribution. It cannot establish the current acceptance requirement, which is: A test packet follows its segment list through installed SR forwarding. The relevant action is: Review segment identifiers and forwarding under SR-MPLS.

B:

Compare RIB selection with forwarding-table installation and next-hop resolution is a relevant step for the separate scenario in which a route appears in the routing table but an engineer assumes its presence proves it was installed into the forwarding table. It does not directly fix this case. Instead review segment identifiers and forwarding under SR-MPLS; verify: A test packet follows its segment list through installed SR forwarding.

D:

This answer would be more suitable when a route to a service PE resolves in inet.0 but cannot resolve to the expected MPLS transport path, where the corrective action is to inspect Junos MPLS-related next-hop resolution and available LSP endpoints. The failure here is different: SR-MPLS can encode forwarding intent using segment labels without per-path RSVP signaling in transit. Required validation: A test packet follows its segment list through installed SR forwarding.

Question 130

A route policy makes a transport prefix unavailable to the MPLS forwarding context while preserving customer IP routes. Which cause-and-remedy pairing reflects the observed problem?

  1. Diagnosis: MPLS relies on selected underlay transport reachability and policy eligibility. Action: Restore the required transport route and inspect label-signaling and next-hop state.
  2. Explanation: Label stack changes can be legitimate parts of LSP forwarding design. Repair: Verify whether PHP or explicit-null behavior is configured and intended.
  3. Fault mechanism: SR-MPLS can encode forwarding intent using segment labels without per-path RSVP signaling in transit. Remediation: Review segment identifiers and forwarding under SR-MPLS.
  4. Root issue: Route redistribution must be intentionally scoped to prevent cross-tenant leakage. Correction: Restrict routing-policy matches and validate the import and export boundary.

Explanation

Correct Answer

A:

Because mPLS relies on selected underlay transport reachability and policy eligibility, the best response is to restore the required transport route and inspect label-signaling and next-hop state. A reviewer can close the technical case only after confirming that the transport endpoint again resolves and a labeled probe succeeds.

Incorrect Answers

B:

The proposed principle concerns another network fault: Label stack changes can be legitimate parts of LSP forwarding design. Here, mPLS relies on selected underlay transport reachability and policy eligibility. The most direct correction is to restore the required transport route and inspect label-signaling and next-hop state, confirmed by the transport endpoint again resolves and a labeled probe succeeds.

C:

That result would be useful for a different failure, namely: A provider chooses segment-routing MPLS but assumes every transit hop needs per-LSP RSVP state. The current case specifically calls for: Restore the required transport route and inspect label-signaling and next-hop state. The required observed result is: The transport endpoint again resolves and a labeled probe succeeds.

D:

This response would target a different source scenario: A provider applies an overly broad route import policy and customer prefixes enter an unintended tenant instance. It cannot establish the current acceptance requirement, which is: The transport endpoint again resolves and a labeled probe succeeds. The relevant action is: Restore the required transport route and inspect label-signaling and next-hop state.

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