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 1

Question 1

A summary route is advertised even though the operator expects every more-specific customer route to remain reachable. What remediation is most directly applicable?

  1. Remediation: Distinguish aggregate reachability from specific-route forwarding and test loss of component routes.
  2. Recommended change: Distinguish session negotiation from UPDATE message route advertisements.
  3. Next step: Define the intended route-leaking boundary between the customer's instance and the master routing table.
  4. Corrective action: Compare installed forwarding entries with interface operational status and adjacency resolution.

Explanation

Correct Answer

A:

Underlying cause: Aggregation can hide individual component failures if advertisement policy is not controlled. Corrective action: distinguish aggregate reachability from specific-route forwarding and test loss of component routes. Verify the outcome: The summary is advertised only under the approved component-route conditions.

Incorrect Answers

B:

Distinguish session negotiation from UPDATE message route advertisements is a relevant step for the separate scenario in which a provider engineer treats a BGP OPEN message as if it already advertises reachable customer prefixes. It does not directly fix this case. Instead distinguish aggregate reachability from specific-route forwarding and test loss of component routes; verify: The summary is advertised only under the approved component-route conditions.

C:

The alternative addresses a provider creates a customer routing instance but assumes its routes will automatically be present in the master inet.0 table, not the present root cause. Here the selected correction must reflect aggregation can hide individual component failures if advertisement policy is not controlled. Test for: The summary is advertised only under the approved component-route conditions.

D:

This answer would be more suitable when a route shows as active but the interface destination still drops traffic after an interface move, where the corrective action is to compare installed forwarding entries with interface operational status and adjacency resolution. The failure here is different: Aggregation can hide individual component failures if advertisement policy is not controlled. Required validation: The summary is advertised only under the approved component-route conditions.

Question 2

A route leaked to a second routing table unexpectedly carries a next hop that cannot be resolved there. What remediation is most directly applicable?

  1. Apply this control: Evaluate routing-table relationships and next-hop resolution when using RIB groups.
  2. Remediation: Compare withdrawal and blackhole behavior under a lab failure before changing the safety route.
  3. Recommended change: Distinguish an advertised inbound hint from neighboring-AS route policy decisions.
  4. Next step: Review route preference before considering equivalent forwarding paths.

Explanation

Correct Answer

A:

Because moving route information between tables does not remove the need for a valid forwarding next hop, the best response is to evaluate routing-table relationships and next-hop resolution when using RIB groups. A reviewer can close the technical case only after confirming that the imported route resolves and forwarding behavior matches the intended instance.

Incorrect Answers

B:

The proposed principle concerns another network fault: Discard routes may intentionally bound routing loops while dynamic specifics converge. Here, moving route information between tables does not remove the need for a valid forwarding next hop. The most direct correction is to evaluate routing-table relationships and next-hop resolution when using RIB groups, confirmed by the imported route resolves and forwarding behavior matches the intended instance.

C:

That result would be useful for a different failure, namely: An inbound MED is assumed to control outgoing traffic even though the receiving network has its own path-selection policies. The current case specifically calls for: Evaluate routing-table relationships and next-hop resolution when using RIB groups. The required observed result is: The imported route resolves and forwarding behavior matches the intended instance.

D:

This response would target a different source scenario: Two static routes for the same prefix have unequal preferences and the operator expects both paths to share traffic. It cannot establish the current acceptance requirement, which is: The imported route resolves and forwarding behavior matches the intended instance. The relevant action is: Evaluate routing-table relationships and next-hop resolution when using RIB groups.

Question 3

A provider's LDP neighbors disappear after an IGP outage while physical links remain up. Which root-cause explanation and corrective action fit the case?

  1. Cause: Successful ordinary IP forwarding does not isolate MPLS packet forwarding faults. Response: Compare ingress label imposition with transit LFIB and egress disposition.
  2. Diagnosis: MPLS forwarding relies on label bindings and compatible next-hop state. Action: Distinguish IP RIB entries from label forwarding information and LSP resolution.
  3. Explanation: BGP group-level export policies must preserve customer routing isolation. Repair: Split export policy by authorized customer scope and verify negative advertisements.
  4. Fault mechanism: LDP signaling depends on the routing and transport state of its endpoints. Remediation: Check transport reachability, LDP session state and the relevant IGP routes.

Explanation

Correct Answer

D:

The critical observation is: LDP signaling depends on the routing and transport state of its endpoints. Correct it by taking this action: Check transport reachability, LDP session state and the relevant IGP routes. Confirm the outcome with: LDP sessions recover and labeled FEC bindings reappear after underlay repair.

Incorrect Answers

A:

The alternative addresses one branch reaches a PE over IP but fails when the same traffic is forwarded across the MPLS core, not the present root cause. Here the selected correction must reflect lDP signaling depends on the routing and transport state of its endpoints. Test for: LDP sessions recover and labeled FEC bindings reappear after underlay repair.

B:

This answer would be more suitable when a provider assumes an ordinary IP destination lookup and an MPLS label lookup always use the same forwarding table, where the corrective action is to distinguish IP RIB entries from label forwarding information and LSP resolution. The failure here is different: LDP signaling depends on the routing and transport state of its endpoints. Required validation: LDP sessions recover and labeled FEC bindings reappear after underlay repair.

C:

This option overlooks the decisive condition. Its supporting principle is bGP group-level export policies must preserve customer routing isolation, while this scenario depends on lDP signaling depends on the routing and transport state of its endpoints. Verify the correction with: LDP sessions recover and labeled FEC bindings reappear after underlay repair.

Question 4

An operator assumes OSPFv3 must form using the same interface and address settings as OSPFv2. What observable result most directly verifies the intended configuration?

  1. The test confirms that the planned area topology reaches distant prefixes through eligible Level 2 routing.
  2. Expected observation: The remote PE learns and uses the intended IPv6 prefix.
  3. Verification result: A tunnel packet is carried over IPv4 and decapsulated to IPv6 at the endpoint.
  4. Closeout evidence: The peers exchange the expected IPv6 routes using a valid OSPFv3 adjacency.

Explanation

Correct Answer

D:

Correct diagnosis: OSPFv3 has protocol-specific requirements for neighbor exchange and IPv6 routing. The appropriate action is: Review the IPv6 OSPFv3 address-family and interface adjacency model. The follow-up evidence required is: The peers exchange the expected IPv6 routes using a valid OSPFv3 adjacency.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A provider uses a Level 1-only router to interconnect two independent IS-IS areas and expects unrestricted cross-area flooding. The current case specifically calls for: Review the IPv6 OSPFv3 address-family and interface adjacency model. The required observed result is: The peers exchange the expected IPv6 routes using a valid OSPFv3 adjacency.

B:

This response would target a different source scenario: An IS-IS change carries IPv4 traffic but a new IPv6 prefix is missing from a remote PE. It cannot establish the current acceptance requirement, which is: The peers exchange the expected IPv6 routes using a valid OSPFv3 adjacency. The relevant action is: Review the IPv6 OSPFv3 address-family and interface adjacency model.

C:

Model endpoint encapsulation and decapsulation for IPv6-over-IPv4 transport is a relevant step for the separate scenario in which a service provider tunnels IPv6 over an IPv4 core but expects native IPv6 forwarding at every transit hop. It does not directly fix this case. Instead review the IPv6 OSPFv3 address-family and interface adjacency model; verify: The peers exchange the expected IPv6 routes using a valid OSPFv3 adjacency.

Question 5

An engineer wants to filter routing information at an IS-IS boundary but applies a policy to the wrong routing context. Which corrective action and confirmation pair is most appropriate?

  1. Implement: Apply and verify supported route policy at the intended routing import or export boundary. Verify: The allowed prefixes are present and denied test prefixes are absent.
  2. Control: Distinguish an advertised inbound hint from neighboring-AS route policy decisions. Accepted result: A controlled route lookup confirms the neighbor's actual selected entry path.
  3. Action: Place the correct L1/L2 boundary and evaluate flooding scope. Evidence: The planned area topology reaches distant prefixes through eligible Level 2 routing.
  4. Repair: Inspect route import policy and forwarding selection separately from LSP presence. Check: The route policy and active table agree with the approved advertised prefixes.

Explanation

Correct Answer

A:

The critical observation is: Policy placement determines which prefixes influence a routing table or advertisement. Correct it by taking this action: Apply and verify supported route policy at the intended routing import or export boundary. Confirm the outcome with: The allowed prefixes are present and denied test prefixes are absent.

Incorrect Answers

B:

BGP MED influence is conditional on the receiving network's path selection rules describes a neighboring protocol concern. In this case the controlling fact is policy placement determines which prefixes influence a routing table or advertisement. A correct remediation would apply and verify supported route policy at the intended routing import or export boundary and demonstrate: The allowed prefixes are present and denied test prefixes are absent.

C:

The proposed principle concerns another network fault: IS-IS route dissemination follows hierarchical level boundaries. Here, policy placement determines which prefixes influence a routing table or advertisement. The most direct correction is to apply and verify supported route policy at the intended routing import or export boundary, confirmed by the allowed prefixes are present and denied test prefixes are absent.

D:

That result would be useful for a different failure, namely: An IS-IS route disappears after a policy update while the LSP database still contains the topology. The current case specifically calls for: Apply and verify supported route policy at the intended routing import or export boundary. The required observed result is: The allowed prefixes are present and denied test prefixes are absent.

Question 6

An engineer treats a BGP community value as a standalone forwarding next hop. Which evidence would justify closing this troubleshooting case?

  1. Closeout evidence: The unauthorized customer receives no leaked prefixes in a route advertisement check.
  2. Acceptance check: Policy based on the intended community alters admission or preference as designed.
  3. The test confirms that lDP sessions recover and labeled FEC bindings reappear after underlay repair.
  4. Expected observation: Only approved customer prefixes enter the provider's active routing table.

Explanation

Correct Answer

B:

This option addresses the stated case rather than another networking issue. Principle: Communities are policy signaling metadata and not the packet-forwarding next hop themselves. Remedy: Differentiate community tags from reachability and forwarding attributes. Proof: Policy based on the intended community alters admission or preference as designed.

Incorrect Answers

A:

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 differentiate community tags from reachability and forwarding attributes; verify: Policy based on the intended community alters admission or preference as designed.

C:

This answer would be more suitable when a provider's LDP neighbors disappear after an IGP outage while physical links remain up, where the corrective action is to check transport reachability, LDP session state and the relevant IGP routes. The failure here is different: Communities are policy signaling metadata and not the packet-forwarding next hop themselves. Required validation: Policy based on the intended community alters admission or preference as designed.

D:

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 communities are policy signaling metadata and not the packet-forwarding next hop themselves. Verify the correction with: Policy based on the intended community alters admission or preference as designed.

Question 7

A network operator assumes a GRE tunnel encrypts customer packets merely because they are encapsulated. Which next action best resolves this observed routing or switching failure?

  1. Apply this control: Verify reachability between tunnel source and destination addresses.
  2. Remediation: Inspect the incoming label, outgoing label and interface on each affected LSR.
  3. Recommended change: Distinguish tunneling encapsulation from confidentiality protection.
  4. Next step: Verify instance ownership and route policy at both tunnel endpoints.

Explanation

Correct Answer

C:

The case turns on the distinction that gRE by itself does not provide encryption or authenticated confidentiality. Apply this concrete engineering step: Distinguish tunneling encapsulation from confidentiality protection. An acceptable verification outcome is: The security design adds an appropriate protected transport where needed.

Incorrect Answers

A:

The proposed principle concerns another network fault: Tunnel interfaces depend on a working underlay path between endpoints. 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.

B:

That result would be useful for a different failure, namely: An ingress LSP shows up but transit packets are dropped after one router swaps to an unexpected label. The current case specifically calls for: Distinguish tunneling encapsulation from confidentiality protection. The required observed result is: The security design adds an appropriate protected transport where needed.

D:

Verify instance ownership and route policy at both tunnel endpoints is a relevant step for the separate scenario in which a GRE tunnel is reachable from one routing instance but the remote customer route leaks into a different instance. It does not directly fix this case. Instead distinguish tunneling encapsulation from confidentiality protection; verify: The security design adds an appropriate protected transport where needed.

Question 8

A customer advertises an unauthorized more-specific and the PE propagates it across the provider core. Which protocol behavior most directly determines the correct diagnosis?

  1. Underlying principle: End-to-end signaling state alone cannot pinpoint a data-plane label failure.
  2. Root design issue: BGP edge hygiene protects the routing domain from unauthorized reachability.
  3. The governing rule is: BGP group-level export policies must preserve customer routing isolation.
  4. The key distinction is: EBGP speakers separated by intermediate devices require deliberate transport reachability and hop policy.

Explanation

Correct Answer

B:

Correct diagnosis: BGP edge hygiene protects the routing domain from unauthorized reachability. The appropriate action is: Tighten customer import route filtering and test permitted prefix lengths. The follow-up evidence required is: The unauthorized more-specific is rejected while approved aggregates remain.

Incorrect Answers

A:

This answer would be more suitable when a maintenance change affects MPLS forwarding on just one core hop and the team only checks RSVP session status at ingress, where the corrective action is to collect hop-local LFIB, label forwarding and interface counters along the LSP. The failure here is different: BGP edge hygiene protects the routing domain from unauthorized reachability. Required validation: The unauthorized more-specific is rejected while approved aggregates remain.

C:

BGP group-level export policies must preserve customer routing isolation describes a neighboring protocol concern. In this case the controlling fact is bGP edge hygiene protects the routing domain from unauthorized reachability. A correct remediation would tighten customer import route filtering and test permitted prefix lengths and demonstrate: The unauthorized more-specific is rejected while approved aggregates remain.

D:

The proposed principle concerns another network fault: EBGP speakers separated by intermediate devices require deliberate transport reachability and hop policy. Here, bGP edge hygiene protects the routing domain from unauthorized reachability. The most direct correction is to tighten customer import route filtering and test permitted prefix lengths, confirmed by the unauthorized more-specific is rejected while approved aggregates remain.

Question 9

An engineer expects a designated router to be elected on a point-to-point OSPF circuit. What implementation step and validation result should be selected?

  1. Control: Select the correct network-type behavior and inspect the neighbor-state model. Accepted result: The point-to-point adjacency forms without an unnecessary DR election.
  2. Action: Confirm the explicit cost plan in a failure rehearsal using route and topology outputs. Evidence: When the primary fails the documented backup path is selected without loops.
  3. Repair: Review current DIS election rules for the network and protocol instance. Check: The LAN's DIS and pseudonode LSP match the documented protocol state.
  4. Change: Assign distinct stable router IDs and clear stale protocol state using an approved procedure. Test: Each router is uniquely identified and the link-state database converges.

Explanation

Correct Answer

A:

Underlying cause: DR and BDR elections apply to broadcast or NBMA segments, not ordinary point-to-point links. Corrective action: select the correct network-type behavior and inspect the neighbor-state model. Verify the outcome: The point-to-point adjacency forms without an unnecessary DR election.

Incorrect Answers

B:

Confirm the explicit cost plan in a failure rehearsal using route and topology outputs is a relevant step for the separate scenario in which an OSPF route appears longer than expected after failover because a backup link's cost was never verified. It does not directly fix this case. Instead select the correct network-type behavior and inspect the neighbor-state model; verify: The point-to-point adjacency forms without an unnecessary DR election.

C:

The alternative addresses an IS-IS LAN elects a new DIS and the engineer assumes the result must preempt every existing elected node, not the present root cause. Here the selected correction must reflect dR and BDR elections apply to broadcast or NBMA segments, not ordinary point-to-point links. Test for: The point-to-point adjacency forms without an unnecessary DR election.

D:

This answer would be more suitable when two routers advertise identical OSPF router IDs and their link-state information becomes inconsistent, where the corrective action is to assign distinct stable router IDs and clear stale protocol state using an approved procedure. The failure here is different: DR and BDR elections apply to broadcast or NBMA segments, not ordinary point-to-point links. Required validation: The point-to-point adjacency forms without an unnecessary DR election.

Question 10

A provider STP domain changes root when a customer sends superior BPDUs from an access port. Which protocol behavior most directly determines the correct diagnosis?

  1. The key distinction is: Traditional spanning-tree root election favors the lowest bridge ID.
  2. Protocol behavior: A trunk carries only its configured authorized VLANs.
  3. Underlying principle: Loop prevention depends on compatible STP participation across redundant Ethernet links.
  4. Root design issue: Customer control traffic must not displace the authorized provider root.

Explanation

Correct Answer

D:

This option addresses the stated case rather than another networking issue. Principle: Customer control traffic must not displace the authorized provider root. Remedy: Apply supported root protection at the appropriate customer-facing boundary. Proof: A superior BPDU test preserves the intended root with a logged protective state.

Incorrect Answers

A:

Traditional spanning-tree root election favors the lowest bridge ID describes a neighboring protocol concern. In this case the controlling fact is customer control traffic must not displace the authorized provider root. A correct remediation would apply supported root protection at the appropriate customer-facing boundary and demonstrate: A superior BPDU test preserves the intended root with a logged protective state.

B:

The proposed principle concerns another network fault: A trunk carries only its configured authorized VLANs. Here, customer control traffic must not displace the authorized provider root. The most direct correction is to apply supported root protection at the appropriate customer-facing boundary, confirmed by a superior BPDU test preserves the intended root with a logged protective state.

C:

That result would be useful for a different failure, namely: A new redundant uplink produces a broadcast storm on an access VLAN. The current case specifically calls for: Apply supported root protection at the appropriate customer-facing boundary. The required observed result is: A superior BPDU test preserves the intended root with a logged protective state.

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