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 25

Question 240

Two routers advertise identical OSPF router IDs and their link-state information becomes inconsistent. Which statement identifies the key design assumption that failed?

  1. Protocol behavior: OSPF adjacency requires compatible area and interface parameters.
  2. Underlying principle: Summary advertisements require validation against their underlying active route policy.
  3. Root design issue: Layered neighbor troubleshooting should separate transport from OSPF parameter mismatches.
  4. The governing rule is: OSPF identifies speakers by router ID, which must be unique inside a routing domain.

Explanation

Correct Answer

D:

Because oSPF identifies speakers by router ID, which must be unique inside a routing domain, the best response is to assign distinct stable router IDs and clear stale protocol state using an approved procedure. A reviewer can close the technical case only after confirming that each router is uniquely identified and the link-state database converges.

Incorrect Answers

A:

This answer would be more suitable when two Junos routers on the same link have mismatched OSPF area identifiers and never form a neighbor relationship, where the corrective action is to align the area membership and verify OSPF interface settings on both sides. The failure here is different: OSPF identifies speakers by router ID, which must be unique inside a routing domain. Required validation: Each router is uniquely identified and the link-state database converges.

B:

This option overlooks the decisive condition. Its supporting principle is summary advertisements require validation against their underlying active route policy, 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:

Layered neighbor troubleshooting should separate transport from OSPF parameter mismatches 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.

Question 241

One customer’s new prefixes are advertised to a second unrelated customer via a shared export group. What diagnosis and engineering response are most appropriate?

  1. Fault mechanism: BGP MED influence is conditional on the receiving network's path selection rules. Remediation: Distinguish an advertised inbound hint from neighboring-AS route policy decisions.
  2. Root issue: IPv4 BGP session liveness does not prove IPv6 family route exchange. Correction: Inspect inet6 family negotiation, filters and IPv6 next-hop validity.
  3. Cause: RSVP-TE path choice can account for configured topology constraints and resources. Response: Review explicit-path or constraint-based RSVP traffic-engineering intent.
  4. Diagnosis: BGP group-level export policies must preserve customer routing isolation. Action: Split export policy by authorized customer scope and verify negative advertisements.

Explanation

Correct Answer

D:

The case turns on the distinction that bGP group-level export policies must preserve customer routing isolation. Apply this concrete engineering step: Split export policy by authorized customer scope and verify negative advertisements. An acceptable verification outcome is: The unauthorized customer receives no leaked prefixes in a route advertisement check.

Incorrect Answers

A:

This response would target a different source scenario: An inbound MED is assumed to control outgoing traffic even though the receiving network has its own path-selection policies. It cannot establish the current acceptance requirement, which is: The unauthorized customer receives no leaked prefixes in a route advertisement check. The relevant action is: Split export policy by authorized customer scope and verify negative advertisements.

B:

Inspect inet6 family negotiation, filters and IPv6 next-hop validity is a relevant step for the separate scenario in which a dual-stack peer is Established but the IPv6 customer route is absent. It does not directly fix this case. Instead split export policy by authorized customer scope and verify negative advertisements; verify: The unauthorized customer receives no leaked prefixes in a route advertisement check.

C:

The alternative addresses an RSVP LSP needs to avoid a congested link but its path is left to ordinary unconstrained routing, not the present root cause. Here the selected correction must reflect bGP group-level export policies must preserve customer routing isolation. Test for: The unauthorized customer receives no leaked prefixes in a route advertisement check.

Question 242

An engineer chooses an IPv6 route based on the printed address alone without comparing prefix length. What assessment accurately links the fault to its correction?

  1. Explanation: IS-IS advertises extensible routing attributes using TLV-encoded fields. Repair: Identify TLVs as structured information within IS-IS protocol data units.
  2. Fault mechanism: IPv6 route selection follows prefix matching and route eligibility, not textual address order. Remediation: Apply longest-prefix-match route lookup to the IPv6 destination.
  3. Root issue: An IPv6 BGP route requires a resolvable eligible next hop for forwarding. Correction: Verify IPv6 next-hop reachability and Neighbor Discovery on the outgoing path.
  4. Cause: BGP family negotiation and route policy control IPv6 NLRI exchange. Response: Enable and verify the intended IPv6 BGP family and export policy.

Explanation

Correct Answer

B:

This is the model-intended best choice because iPv6 route selection follows prefix matching and route eligibility, not textual address order. The targeted correction is to apply longest-prefix-match route lookup to the IPv6 destination. Validate it by observing that a destination lookup chooses the intended most specific valid route.

Incorrect Answers

A:

IS-IS advertises extensible routing attributes using TLV-encoded fields describes a neighboring protocol concern. In this case the controlling fact is iPv6 route selection follows prefix matching and route eligibility, not textual address order. A correct remediation would apply longest-prefix-match route lookup to the IPv6 destination and demonstrate: A destination lookup chooses the intended most specific valid route.

C:

That result would be useful for a different failure, namely: An IPv6 BGP route is accepted but cannot be forwarded because its next hop lacks neighbor resolution. The current case specifically calls for: Apply longest-prefix-match route lookup to the IPv6 destination. The required observed result is: A destination lookup chooses the intended most specific valid route.

D:

This response would target a different source scenario: A BGP peer carries IPv4 prefixes but the team assumes IPv6 prefixes are automatically shared. It cannot establish the current acceptance requirement, which is: A destination lookup chooses the intended most specific valid route. The relevant action is: Apply longest-prefix-match route lookup to the IPv6 destination.

Question 243

A router sends OSPF Hello packets but remains stuck because the subnet mask differs across neighbors on a broadcast link. What remediation is most directly applicable?

  1. Apply this control: Verify compatible network and Hello parameters including mask where applicable.
  2. Remediation: Run route and connectivity checks in the explicitly intended routing instance.
  3. Recommended change: Review router priorities and the nonpreemptive properties of DR elections.
  4. Next step: Review the passive-interface configuration and required active neighbor links.

Explanation

Correct Answer

A:

The case turns on the distinction that oSPF network-type and Hello compatibility can prevent adjacency formation. Apply this concrete engineering step: Verify compatible network and Hello parameters including mask where applicable. An acceptable verification outcome is: A controlled neighbor check reaches Full after configuration correction.

Incorrect Answers

B:

This answer would be more suitable when a provider PE can ping a customer in the master instance but probes in the tenant routing instance fail, where the corrective action is to run route and connectivity checks in the explicitly intended routing instance. The failure here is different: OSPF network-type and Hello compatibility can prevent adjacency formation. Required validation: A controlled neighbor check reaches Full after configuration correction.

C:

This option overlooks the decisive condition. Its supporting principle is oSPF DR selection depends on eligible routers and the current election event, while this scenario depends on oSPF network-type and Hello compatibility can prevent adjacency formation. Verify the correction with: A controlled neighbor check reaches Full after configuration correction.

D:

Passive OSPF interfaces can advertise networks without forming neighbors on that interface describes a neighboring protocol concern. In this case the controlling fact is oSPF network-type and Hello compatibility can prevent adjacency formation. A correct remediation would verify compatible network and Hello parameters including mask where applicable and demonstrate: A controlled neighbor check reaches Full after configuration correction.

Question 244

A BFD session flaps during Routing Engine switchover after aggressive timer tuning. Which cause-and-remedy pairing reflects the observed problem?

  1. Cause: Layer 3 routing HA does not automatically guarantee L2 bridge-control continuity. Response: Inspect whether nonstop bridging is available and configured for the relevant L2 control plane.
  2. Diagnosis: BFD HA behavior depends on platform processing placement and timer tolerances. Action: Review session type, supported distributed behavior and switchover-appropriate intervals.
  3. Explanation: DR and BDR elections apply to broadcast or NBMA segments, not ordinary point-to-point links. Repair: Select the correct network-type behavior and inspect the neighbor-state model.
  4. Fault mechanism: NSR and graceful restart on the local restarting device are different approaches and can conflict. Remediation: Review supported mutual exclusivity and select the intended HA control-plane method.

Explanation

Correct Answer

B:

Because bFD HA behavior depends on platform processing placement and timer tolerances, the best response is to review session type, supported distributed behavior and switchover-appropriate intervals. A reviewer can close the technical case only after confirming that a tested switchover maintains the required liveness behavior without false failure.

Incorrect Answers

A:

That result would be useful for a different failure, namely: Layer 2 forwarding is disrupted during Routing Engine replacement even though high availability was enabled for routing. The current case specifically calls for: Review session type, supported distributed behavior and switchover-appropriate intervals. The required observed result is: A tested switchover maintains the required liveness behavior without false failure.

C:

Select the correct network-type behavior and inspect the neighbor-state model is a relevant step for the separate scenario in which an engineer expects a designated router to be elected on a point-to-point OSPF circuit. It does not directly fix this case. Instead review session type, supported distributed behavior and switchover-appropriate intervals; verify: A tested switchover maintains the required liveness behavior without false failure.

D:

The alternative addresses a provider tries to enable nonstop active routing and graceful-restart mode simultaneously on the same Junos device, not the present root cause. Here the selected correction must reflect bFD HA behavior depends on platform processing placement and timer tolerances. Test for: A tested switchover maintains the required liveness behavior without false failure.

Question 245

An aggregated customer advertisement persists while all contributing specifics have withdrawn. Which corrective action and confirmation pair is most appropriate?

  1. Control: Audit aggregate or generated-route contributors and policy conditions. Accepted result: A loss-of-last-contributor test causes the intended summary behavior.
  2. Action: Coordinate authentication parameters and test the key change under maintenance controls. Evidence: Authenticated adjacency returns and no fallback to unauthenticated operation occurs.
  3. Repair: Run route and connectivity checks in the explicitly intended routing instance. Check: The tenant-specific lookup resolves and the same source-based test reaches its destination.
  4. Change: Restrict routing-policy matches and validate the import and export boundary. Test: A negative test proves the unrelated customer prefix is absent from the target table.

Explanation

Correct Answer

A:

The critical observation is: Summary advertisements require validation against their underlying active route policy. Correct it by taking this action: Audit aggregate or generated-route contributors and policy conditions. Confirm the outcome with: A loss-of-last-contributor test causes the intended summary behavior.

Incorrect Answers

B:

Authentication mismatches can reject otherwise valid OSPF protocol packets describes a neighboring protocol concern. In this case the controlling fact is summary advertisements require validation against their underlying active route policy. A correct remediation would audit aggregate or generated-route contributors and policy conditions and demonstrate: A loss-of-last-contributor test causes the intended summary behavior.

C:

The proposed principle concerns another network fault: Instance-aware troubleshooting prevents a successful master-table probe from masking tenant isolation issues. Here, summary advertisements require validation against their underlying active route policy. The most direct correction is to audit aggregate or generated-route contributors and policy conditions, confirmed by a loss-of-last-contributor test causes the intended summary behavior.

D:

That result would be useful for a different failure, namely: A provider applies an overly broad route import policy and customer prefixes enter an unintended tenant instance. The current case specifically calls for: Audit aggregate or generated-route contributors and policy conditions. The required observed result is: A loss-of-last-contributor test causes the intended summary behavior.

Question 246

A policy adjustment changes both routing preference and forwarding instance selection in one unreviewed commit. What remediation is most directly applicable?

  1. Recommended change: Document the discard behavior and determine whether the aggregate should remain advertised.
  2. Next step: Add a precise prefix and instance match, then inspect effective imports.
  3. Corrective action: Separate route-selection and lookup-table changes and test each with candidate configuration.
  4. Apply this control: Inspect inet6 family negotiation, filters and IPv6 next-hop validity.

Explanation

Correct Answer

C:

Because small reversible route-policy changes simplify troubleshooting and rollback, the best response is to separate route-selection and lookup-table changes and test each with candidate configuration. A reviewer can close the technical case only after confirming that the rollback and candidate checks show the exact intended RIB and FIB outcomes.

Incorrect Answers

A:

Document the discard behavior and determine whether the aggregate should remain advertised is a relevant step for the separate scenario in which a static discard route intended as a summary safety mechanism becomes the only active route after customer specifics disappear. It does not directly fix this case. Instead separate route-selection and lookup-table changes and test each with candidate configuration; verify: The rollback and candidate checks show the exact intended RIB and FIB outcomes.

B:

The alternative addresses a route import policy accepts more-specific destinations that should remain isolated inside a wholesale tenant, not the present root cause. Here the selected correction must reflect small reversible route-policy changes simplify troubleshooting and rollback. Test for: The rollback and candidate checks show the exact intended RIB and FIB outcomes.

D:

This option overlooks the decisive condition. Its supporting principle is iPv4 BGP session liveness does not prove IPv6 family route exchange, while this scenario depends on small reversible route-policy changes simplify troubleshooting and rollback. Verify the correction with: The rollback and candidate checks show the exact intended RIB and FIB outcomes.

Question 247

An ingress router imposes an MPLS label while an engineer expects the same label value to persist unchanged at every hop. What is the most defensible network engineering correction?

  1. Remediation: Explain label swap behavior across transit label switching routers.
  2. Recommended change: Review explicit-path or constraint-based RSVP traffic-engineering intent.
  3. Next step: Inspect Junos MPLS-related next-hop resolution and available LSP endpoints.
  4. Corrective action: Review BGP next-hop reachability and explicit next-hop handling.

Explanation

Correct Answer

A:

The selected response implements the principle that labels have locally significant forwarding meaning on each LSP segment. The engineer should explain label swap behavior across transit label switching routers. Successful confirmation means: A hop trace shows the intended push and swap operations along the path.

Incorrect Answers

B:

That result would be useful for a different failure, namely: An RSVP LSP needs to avoid a congested link but its path is left to ordinary unconstrained routing. The current case specifically calls for: Explain label swap behavior across transit label switching routers. The required observed result is: A hop trace shows the intended push and swap operations along the path.

C:

This response would target a different source scenario: A route to a service PE resolves in inet.0 but cannot resolve to the expected MPLS transport path. It cannot establish the current acceptance requirement, which is: A hop trace shows the intended push and swap operations along the path. The relevant action is: Explain label swap behavior across transit label switching routers.

D:

Review BGP next-hop reachability and explicit next-hop handling is a relevant step for the separate scenario in which a provider's iBGP peer receives a route but cannot resolve the external next hop in its own IGP. It does not directly fix this case. Instead explain label swap behavior across transit label switching routers; verify: A hop trace shows the intended push and swap operations along the path.

Question 248

A route to a service PE resolves in inet.0 but cannot resolve to the expected MPLS transport path. Which post-change observation most strongly confirms the correction?

  1. Verification result: The rollback and candidate checks show the exact intended RIB and FIB outcomes.
  2. Closeout evidence: The test service label is retained and accepted at the target PE.
  3. Acceptance check: The remote PE service route resolves over the designated LSP.
  4. The test confirms that the installed LSP avoids the prohibited link in a failure-free test.

Explanation

Correct Answer

C:

This option addresses the stated case rather than another networking issue. Principle: A labeled transport next hop must be available to carry the overlay service. Remedy: Inspect Junos MPLS-related next-hop resolution and available LSP endpoints. Proof: The remote PE service route resolves over the designated LSP.

Incorrect Answers

A:

This answer would be more suitable when a policy adjustment changes both routing preference and forwarding instance selection in one unreviewed commit, where the corrective action is to separate route-selection and lookup-table changes and test each with candidate configuration. The failure here is different: A labeled transport next hop must be available to carry the overlay service. Required validation: The remote PE service route resolves over the designated LSP.

B:

This option overlooks the decisive condition. Its supporting principle is a healthy transport LSP does not guarantee a correct overlay label mapping, while this scenario depends on a labeled transport next hop must be available to carry the overlay service. Verify the correction with: The remote PE service route resolves over the designated LSP.

D:

The proposed principle concerns another network fault: RSVP-TE path choice can account for configured topology constraints and resources. Here, a labeled transport next hop must be available to carry the overlay service. The most direct correction is to inspect Junos MPLS-related next-hop resolution and available LSP endpoints, confirmed by the remote PE service route resolves over the designated LSP.

Question 249

An IPv6 BGP route is accepted but cannot be forwarded because its next hop lacks neighbor resolution. What is the most defensible network engineering correction?

  1. Corrective action: Inspect longest-match results and forwarding routes for the specific destination.
  2. Apply this control: Inspect IS-IS interface enablement, levels, area identifiers and link type.
  3. Remediation: Distinguish IPv6 Neighbor Discovery from IPv4 ARP.
  4. Recommended change: Verify IPv6 next-hop reachability and Neighbor Discovery on the outgoing path.

Explanation

Correct Answer

D:

The case turns on the distinction that an IPv6 BGP route requires a resolvable eligible next hop for forwarding. Apply this concrete engineering step: Verify IPv6 next-hop reachability and Neighbor Discovery on the outgoing path. An acceptable verification outcome is: The route installs with the expected IPv6 next hop and packet delivery succeeds.

Incorrect Answers

A:

This response would target a different source scenario: A new IPv6 static backup route is configured but a more-specific route points into a blackhole. It cannot establish the current acceptance requirement, which is: The route installs with the expected IPv6 next hop and packet delivery succeeds. The relevant action is: Verify IPv6 next-hop reachability and Neighbor Discovery on the outgoing path.

B:

Inspect IS-IS interface enablement, levels, area identifiers and link type is a relevant step for the separate scenario in which a Junos router shows no IS-IS adjacency after a circuit migration though the interface is physically up. It does not directly fix this case. Instead verify IPv6 next-hop reachability and Neighbor Discovery on the outgoing path; verify: The route installs with the expected IPv6 next hop and packet delivery succeeds.

C:

The alternative addresses a provider configures an IPv6 static route but assumes IPv4 ARP will resolve its IPv6 neighbor, not the present root cause. Here the selected correction must reflect an IPv6 BGP route requires a resolvable eligible next hop for forwarding. Test for: The route installs with the expected IPv6 next hop and packet delivery succeeds.

Question 250

A provider creates a customer routing instance but assumes its routes will automatically be present in the master inet.0 table. What observable result most directly verifies the intended configuration?

  1. The test confirms that each customer route is visible only in the tables approved by the design.
  2. Expected observation: The imported route resolves and forwarding behavior matches the intended instance.
  3. Verification result: Only the subscriber's approved traffic enters the alternate routing instance.
  4. Closeout evidence: The intended lower-total-cost path wins under steady-state conditions.

Explanation

Correct Answer

A:

Because routing instances isolate routing tables unless explicit import or export mechanisms connect them, the best response is to define the intended route-leaking boundary between the customer's instance and the master routing table. A reviewer can close the technical case only after confirming that each customer route is visible only in the tables approved by the design.

Incorrect Answers

B:

The proposed principle concerns another network fault: Moving route information between tables does not remove the need for a valid forwarding next hop. Here, routing instances isolate routing tables unless explicit import or export mechanisms connect them. The most direct correction is to define the intended route-leaking boundary between the customer's instance and the master routing table, confirmed by each customer route is visible only in the tables approved by the design.

C:

That result would be useful for a different failure, namely: A filter-based forwarding term matching one subscriber address also captures an overlapping shared services subnet. The current case specifically calls for: Define the intended route-leaking boundary between the customer's instance and the master routing table. The required observed result is: Each customer route is visible only in the tables approved by the design.

D:

This response would target a different source scenario: A branch uses a higher OSPF interface cost but expects that branch to remain the preferred primary path. It cannot establish the current acceptance requirement, which is: Each customer route is visible only in the tables approved by the design. The relevant action is: Define the intended route-leaking boundary between the customer's instance and the master routing table.

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