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 71

Question 700

A provider PE can ping a customer in the master instance but probes in the tenant routing instance fail. What observable result most directly verifies the intended configuration?

  1. Verification result: The internal peer has a valid route to the BGP next hop and installs the prefix.
  2. Closeout evidence: A route lookup shows an active reachable next hop and traffic reaches the customer.
  3. Acceptance check: The tenant-specific lookup resolves and the same source-based test reaches its destination.
  4. The test confirms that a test packet follows the expected active forwarding next hop and interface.

Explanation

Correct Answer

C:

This is the model-intended best choice because instance-aware troubleshooting prevents a successful master-table probe from masking tenant isolation issues. The targeted correction is to run route and connectivity checks in the explicitly intended routing instance. Validate it by observing that the tenant-specific lookup resolves and the same source-based test reaches its destination.

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: Run route and connectivity checks in the explicitly intended routing instance. The required observed result is: The tenant-specific lookup resolves and the same source-based test reaches its destination.

B:

This response would target a different source scenario: A provider router has a static route for a customer prefix but its configured next hop is not reachable through any active route. It cannot establish the current acceptance requirement, which is: The tenant-specific lookup resolves and the same source-based test reaches its destination. The relevant action is: Run route and connectivity checks in the explicitly intended routing instance.

D:

The alternative addresses a route shows as active but the interface destination still drops traffic after an interface move, not the present root cause. Here the selected correction must reflect instance-aware troubleshooting prevents a successful master-table probe from masking tenant isolation issues. Test for: The tenant-specific lookup resolves and the same source-based test reaches its destination.

Question 701

A transit operator changes IS-IS metrics on one interface and later discovers a traffic-engineering imbalance. What assessment accurately links the fault to its correction?

  1. Fault mechanism: Common topology information can still produce direction-dependent shortest paths. Remediation: Compare path metrics and each router's route selection before altering LSP state.
  2. Root issue: BGP AS-path information can prevent routes from looping into an AS. Correction: Investigate AS-path loop prevention rather than overriding it without risk review.
  3. Cause: IS-IS shortest-path output depends on effective metrics across the route. Response: Measure end-to-end route choices and review configured interface metrics.
  4. Diagnosis: IS-IS packet exchange and transport differ from OSPF over IP. Action: Recognize IS-IS as a link-layer routing protocol with its own PDUs.

Explanation

Correct Answer

C:

Underlying cause: IS-IS shortest-path output depends on effective metrics across the route. Corrective action: measure end-to-end route choices and review configured interface metrics. Verify the outcome: Traffic and route lookup follow the documented optimized path.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is common topology information can still produce direction-dependent shortest paths, while this scenario depends on iS-IS shortest-path output depends on effective metrics across the route. Verify the correction with: Traffic and route lookup follow the documented optimized path.

B:

BGP AS-path information can prevent routes from looping into an AS describes a neighboring protocol concern. In this case the controlling fact is iS-IS shortest-path output depends on effective metrics across the route. A correct remediation would measure end-to-end route choices and review configured interface metrics and demonstrate: Traffic and route lookup follow the documented optimized path.

D:

That result would be useful for a different failure, namely: A technician tries to diagnose an IS-IS area failure only by inspecting IP multicast Hellos. The current case specifically calls for: Measure end-to-end route choices and review configured interface metrics. The required observed result is: Traffic and route lookup follow the documented optimized path.

Question 702

A technician tries to diagnose an IS-IS area failure only by inspecting IP multicast Hellos. Which evidence would justify closing this troubleshooting case?

  1. Closeout evidence: The backup next hop resolves and carries test traffic after the primary link fails.
  2. Acceptance check: A link-level packet trace observes the relevant IS-IS PDUs.
  3. The test confirms that the LAN's DIS and pseudonode LSP match the documented protocol state.
  4. Expected observation: A neighbor advertising test shows precisely the allowed tagged prefixes.

Explanation

Correct Answer

B:

This option addresses the stated case rather than another networking issue. Principle: IS-IS packet exchange and transport differ from OSPF over IP. Remedy: Recognize IS-IS as a link-layer routing protocol with its own PDUs. Proof: A link-level packet trace observes the relevant IS-IS PDUs.

Incorrect Answers

A:

Rehearse the failure and inspect active next hops and IS-IS route changes is a relevant step for the separate scenario in which a provider failover exposes an alternate IS-IS path that had never been tested for next-hop resolution. It does not directly fix this case. Instead recognize IS-IS as a link-layer routing protocol with its own PDUs; verify: A link-level packet trace observes the relevant IS-IS PDUs.

C:

This answer would be more suitable when an IS-IS LAN elects a new DIS and the engineer assumes the result must preempt every existing elected node, where the corrective action is to review current DIS election rules for the network and protocol instance. The failure here is different: IS-IS packet exchange and transport differ from OSPF over IP. Required validation: A link-level packet trace observes the relevant IS-IS PDUs.

D:

This option overlooks the decisive condition. Its supporting principle is bGP group inheritance and policy direction govern which advertisements are modified, while this scenario depends on iS-IS packet exchange and transport differ from OSPF over IP. Verify the correction with: A link-level packet trace observes the relevant IS-IS PDUs.

Question 703

A branch uses a higher OSPF interface cost but expects that branch to remain the preferred primary path. Which corrective action and confirmation pair is most appropriate?

  1. Repair: Compare NET area addresses and intended L1 or L2 adjacency mode. Check: A protocol check shows the authorized level and matching adjacency.
  2. Change: Check MTU and interface compatibility and inspect neighbor-state details. Test: The adjacency advances through database synchronization to Full.
  3. Implement: Revisit additive path cost and verify SPF outcomes across alternative links. Verify: The intended lower-total-cost path wins under steady-state conditions.
  4. Control: Check the expected DR/BDR versus DROther neighbor-state relationships. Accepted result: The neighbor states match expected DR roles and routing converges.

Explanation

Correct Answer

C:

The case turns on the distinction that oSPF normally prefers the least accumulated metric to a destination. Apply this concrete engineering step: Revisit additive path cost and verify SPF outcomes across alternative links. An acceptable verification outcome is: The intended lower-total-cost path wins under steady-state conditions.

Incorrect Answers

A:

The proposed principle concerns another network fault: Area mismatch can affect Level 1 adjacency even when packets are received. Here, oSPF normally prefers the least accumulated metric to a destination. The most direct correction is to revisit additive path cost and verify SPF outcomes across alternative links, confirmed by the intended lower-total-cost path wins under steady-state conditions.

B:

That result would be useful for a different failure, namely: An OSPF trace shows Hellos received but database synchronization stalls at ExStart or Exchange. The current case specifically calls for: Revisit additive path cost and verify SPF outcomes across alternative links. The required observed result is: The intended lower-total-cost path wins under steady-state conditions.

D:

Check the expected DR/BDR versus DROther neighbor-state relationships is a relevant step for the separate scenario in which an engineer assumes both routers must reach Full with every speaker on a broadcast network. It does not directly fix this case. Instead revisit additive path cost and verify SPF outcomes across alternative links; verify: The intended lower-total-cost path wins under steady-state conditions.

Question 704

A route to a service PE resolves in inet.0 but cannot resolve to the expected MPLS transport path. Which underlying Junos networking principle explains the failure?

  1. Underlying principle: A stale label binding cannot compensate for unusable transport forwarding.
  2. Root design issue: Summary advertisements require validation against their underlying active route policy.
  3. The governing rule is: A labeled transport next hop must be available to carry the overlay service.
  4. The key distinction is: An upstream LSR can remove a label before the egress in an appropriate PHP design.

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 an LDP binding exists for a remote destination but the forwarding interface points to a failed next hop, where the corrective action is to compare label bindings with the active IGP next hop and installed forwarding entries. 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 summary advertisements require validation against their underlying active route policy, 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: An upstream LSR can remove a label before the egress in an appropriate PHP design. 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 705

A BGP prefix redistribution into OSPF causes a flood of routes that were not in the approved design. Which post-change observation most strongly confirms the correction?

  1. The test confirms that the elected DR and BDR align with the tested election conditions.
  2. Expected observation: An LSA and route inspection finds only the authorized external prefix set.
  3. Verification result: A trace of matching and nonmatching packets shows the approved lookup table.
  4. Closeout evidence: When the primary fails the documented backup path is selected without loops.

Explanation

Correct Answer

B:

The selected response implements the principle that external OSPF redistribution must be reviewed for scope and scale. The engineer should restore explicit policy matching and confirm external route advertisements. Successful confirmation means: An LSA and route inspection finds only the authorized external prefix set.

Incorrect Answers

A:

This response would target a different source scenario: A broadcast OSPF segment experiences repeated DR elections after interface priority changes. It cannot establish the current acceptance requirement, which is: An LSA and route inspection finds only the authorized external prefix set. The relevant action is: Restore explicit policy matching and confirm external route advertisements.

C:

The alternative addresses a router selects a route in one routing instance while the forwarding policy sends matching traffic into a different table, not the present root cause. Here the selected correction must reflect external OSPF redistribution must be reviewed for scope and scale. Test for: An LSA and route inspection finds only the authorized external prefix set.

D:

This answer would be more suitable when an OSPF route appears longer than expected after failover because a backup link's cost was never verified, where the corrective action is to confirm the explicit cost plan in a failure rehearsal using route and topology outputs. The failure here is different: External OSPF redistribution must be reviewed for scope and scale. Required validation: An LSA and route inspection finds only the authorized external prefix set.

Question 706

A route import policy accepts more-specific destinations that should remain isolated inside a wholesale tenant. What implementation step and validation result should be selected?

  1. Implement: Add a precise prefix and instance match, then inspect effective imports. Verify: The allowed service routes import and the forbidden more-specific prefixes do not.
  2. Control: Evaluate routing-policy local preference before later BGP path-selection attributes. Accepted result: The intended local preference policy selects the approved egress.
  3. Action: Tighten the filter match and verify the next-table lookup with explicit positive and negative examples. Evidence: Only the subscriber's approved traffic enters the alternate routing instance.
  4. Repair: Verify route contribution and the conditions for route generation. Check: The generated prefix appears only when the required contributing route is active.

Explanation

Correct Answer

A:

Because routing policy acceptance must reflect explicitly permitted destinations, the best response is to add a precise prefix and instance match, then inspect effective imports. A reviewer can close the technical case only after confirming that the allowed service routes import and the forbidden more-specific prefixes do not.

Incorrect Answers

B:

The proposed principle concerns another network fault: BGP best-path selection considers higher-priority decision attributes before AS-path length. Here, routing policy acceptance must reflect explicitly permitted destinations. The most direct correction is to add a precise prefix and instance match, then inspect effective imports, confirmed by the allowed service routes import and the forbidden more-specific prefixes do not.

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: Add a precise prefix and instance match, then inspect effective imports. The required observed result is: The allowed service routes import and the forbidden more-specific prefixes do not.

D:

This response would target a different source scenario: A generated route is configured but its expected contributing route is absent from the routing table. It cannot establish the current acceptance requirement, which is: The allowed service routes import and the forbidden more-specific prefixes do not. The relevant action is: Add a precise prefix and instance match, then inspect effective imports.

Question 707

After enabling OSPFv3 a provider sees IPv6 neighbors but no remote IPv6 customer prefixes. Which technical distinction best describes the observed symptom?

  1. The governing rule is: An IPv6 BGP route requires a resolvable eligible next hop for forwarding.
  2. The key distinction is: A configured IPv6 static route still depends on reachable forwarding next hops.
  3. Protocol behavior: Neighbor establishment is distinct from prefix advertisement and installation.
  4. Underlying principle: IS-IS packet exchange and transport differ from OSPF over IP.

Explanation

Correct Answer

C:

The selected response implements the principle that neighbor establishment is distinct from prefix advertisement and installation. The engineer should check OSPFv3 family enablement, LSAs and routing-policy route acceptance. Successful confirmation means: The accepted OSPFv3 IPv6 routes become active in the expected routing table.

Incorrect Answers

A:

The alternative addresses an IPv6 BGP route is accepted but cannot be forwarded because its next hop lacks neighbor resolution, not the present root cause. Here the selected correction must reflect neighbor establishment is distinct from prefix advertisement and installation. Test for: The accepted OSPFv3 IPv6 routes become active in the expected routing table.

B:

This answer would be more suitable when a router has an IPv6 default route but no usable next-hop reachability on the egress link, where the corrective action is to confirm the IPv6 next-hop adjacency and active routing entry. The failure here is different: Neighbor establishment is distinct from prefix advertisement and installation. Required validation: The accepted OSPFv3 IPv6 routes become active in the expected routing table.

D:

IS-IS packet exchange and transport differ from OSPF over IP 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.

Question 708

A remote BGP neighbor uses a different AS number than configured and the session fails during OPEN negotiation. What operational check demonstrates that the intended outcome occurred?

  1. Verification result: The session reaches Established only with the documented correct peer AS.
  2. Closeout evidence: The installed LSP avoids the prohibited link in a failure-free test.
  3. Acceptance check: A test prefix reaches permitted clients without cycling through reflector clusters.
  4. The test confirms that the internal router resolves the next hop and installs the intended route.

Explanation

Correct Answer

A:

This option addresses the stated case rather than another networking issue. Principle: BGP OPEN negotiation includes AS identity that must match peering intent. Remedy: Confirm the configured local and peer AS values with the authoritative design. Proof: The session reaches Established only with the documented correct peer AS.

Incorrect Answers

B:

This response would target a different source scenario: An RSVP LSP needs to avoid a congested link but its path is left to ordinary unconstrained routing. It cannot establish the current acceptance requirement, which is: The session reaches Established only with the documented correct peer AS. The relevant action is: Confirm the configured local and peer AS values with the authoritative design.

C:

Review route-reflector client and cluster design, including loop-prevention attributes is a relevant step for the separate scenario in which a route reflector advertises routes to the wrong clients after a change in group membership. It does not directly fix this case. Instead confirm the configured local and peer AS values with the authoritative design; verify: The session reaches Established only with the documented correct peer AS.

D:

The alternative addresses an iBGP route is hidden because the next hop learned from an edge router is unreachable inside the backbone, not the present root cause. Here the selected correction must reflect bGP OPEN negotiation includes AS identity that must match peering intent. Test for: The session reaches Established only with the documented correct peer AS.

Question 709

An IS-IS link has asymmetric traffic despite synchronized LSPs and the engineer assumes the LSDB itself is corrupted. Which underlying Junos networking principle explains the failure?

  1. Underlying principle: Policy placement determines which prefixes influence a routing table or advertisement.
  2. Root design issue: Common topology information can still produce direction-dependent shortest paths.
  3. The governing rule is: The IS-IS DIS concept applies to LANs rather than ordinary point-to-point links.
  4. The key distinction is: BGP AS-path information can prevent routes from looping into an AS.

Explanation

Correct Answer

B:

The case turns on the distinction that common topology information can still produce direction-dependent shortest paths. Apply this concrete engineering step: Compare path metrics and each router's route selection before altering LSP state. An acceptable verification outcome is: Each direction's active route matches the documented costs and design.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is policy placement determines which prefixes influence a routing table or advertisement, while this scenario depends on common topology information can still produce direction-dependent shortest paths. Verify the correction with: Each direction's active route matches the documented costs and design.

C:

The proposed principle concerns another network fault: The IS-IS DIS concept applies to LANs rather than ordinary point-to-point links. Here, common topology information can still produce direction-dependent shortest paths. The most direct correction is to compare path metrics and each router's route selection before altering LSP state, confirmed by each direction's active route matches the documented costs and design.

D:

That result would be useful for a different failure, namely: A provider advertises a customer prefix with its own AS number already present in the return AS path. The current case specifically calls for: Compare path metrics and each router's route selection before altering LSP state. The required observed result is: Each direction's active route matches the documented costs and design.

Question 710

One LAG member fails silently and the service loses capacity even though the logical interface remains active. Which cause-and-remedy pairing reflects the observed problem?

  1. Root issue: VRRP provides a master and backup mechanism for a shared virtual default gateway. Correction: Review VRRP virtual router roles, priority and failover behavior.
  2. Cause: Forwarding-plane continuity does not prove control-plane routing continuity. Response: Check whether GRES is paired with the intended GR or NSR support and verify protocol state.
  3. Diagnosis: Aggregated links need operational member health monitoring and suitable capacity planning. Action: Inspect member states, traffic distribution and configured minimum link expectations.
  4. Explanation: Interarea reachability depends on the ABR's view and allowed advertisements. Repair: Inspect ABR area configuration, route export rules and summary policy.

Explanation

Correct Answer

C:

Because aggregated links need operational member health monitoring and suitable capacity planning, the best response is to inspect member states, traffic distribution and configured minimum link expectations. A reviewer can close the technical case only after confirming that the fault is visible and surviving members carry traffic within the approved limits.

Incorrect Answers

A:

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 inspect member states, traffic distribution and configured minimum link expectations; verify: The fault is visible and surviving members carry traffic within the approved limits.

B:

The alternative addresses a Routing Engine switchover retains data-plane traffic briefly but causes OSPF adjacencies to restart, not the present root cause. Here the selected correction must reflect aggregated links need operational member health monitoring and suitable capacity planning. Test for: The fault is visible and surviving members carry traffic within the approved limits.

D:

This option overlooks the decisive condition. Its supporting principle is interarea reachability depends on the ABR's view and allowed advertisements, while this scenario depends on aggregated links need operational member health monitoring and suitable capacity planning. Verify the correction with: The fault is visible and surviving members carry traffic within the approved limits.

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