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 11

Question 100

An OSPF route appears longer than expected after failover because a backup link's cost was never verified. Which combined repair and acceptance criterion is strongest?

  1. Implement: Assign distinct stable router IDs and clear stale protocol state using an approved procedure. Verify: Each router is uniquely identified and the link-state database converges.
  2. Control: Compare area, interface mode, timers, authentication and physical status on both endpoints. Accepted result: The corrected link reaches stable Full adjacency and exchanges the intended routes.
  3. 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.
  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

C:

This is the model-intended best choice because failover paths are governed by their actual configured metrics. The targeted correction is to confirm the explicit cost plan in a failure rehearsal using route and topology outputs. Validate it by observing that when the primary fails the documented backup path is selected without loops.

Incorrect Answers

A:

That result would be useful for a different failure, namely: Two routers advertise identical OSPF router IDs and their link-state information becomes inconsistent. The current case specifically calls for: Confirm the explicit cost plan in a failure rehearsal using route and topology outputs. The required observed result is: When the primary fails the documented backup path is selected without loops.

B:

This response would target a different source scenario: A new OSPF uplink remains down at the adjacency stage after a router replacement. It cannot establish the current acceptance requirement, which is: When the primary fails the documented backup path is selected without loops. The relevant action is: Confirm the explicit cost plan in a failure rehearsal using route and topology outputs.

D:

The alternative addresses an IS-IS route disappears after a policy update while the LSP database still contains the topology, not the present root cause. Here the selected correction must reflect failover paths are governed by their actual configured metrics. Test for: When the primary fails the documented backup path is selected without loops.

Question 101

An operator assumes MPLS labels are globally unique across the provider network. Which root-cause explanation and corrective action fit the case?

  1. Cause: Labels are generally meaningful within the forwarding context where they are allocated. Response: Explain local label significance and neighbor label binding.
  2. Diagnosis: RSVP resource reservation may affect which additional constrained LSPs can be admitted. Action: Distinguish signaling reservations from physical link speed and admission control.
  3. Explanation: Multiple eligible forwarding next hops do not guarantee per-packet round-robin use. Repair: Distinguish equal-cost multipath from the exact traffic-distribution algorithm used by the forwarding plane.
  4. Fault mechanism: A labeled transport next hop must be available to carry the overlay service. Remediation: Inspect Junos MPLS-related next-hop resolution and available LSP endpoints.

Explanation

Correct Answer

A:

The critical observation is: Labels are generally meaningful within the forwarding context where they are allocated. Correct it by taking this action: Explain local label significance and neighbor label binding. Confirm the outcome with: A path test records locally valid incoming and outgoing label mappings.

Incorrect Answers

B:

RSVP resource reservation may affect which additional constrained LSPs can be admitted describes a neighboring protocol concern. In this case the controlling fact is labels are generally meaningful within the forwarding context where they are allocated. A correct remediation would explain local label significance and neighbor label binding and demonstrate: A path test records locally valid incoming and outgoing label mappings.

C:

The proposed principle concerns another network fault: Multiple eligible forwarding next hops do not guarantee per-packet round-robin use. Here, labels are generally meaningful within the forwarding context where they are allocated. The most direct correction is to explain local label significance and neighbor label binding, confirmed by a path test records locally valid incoming and outgoing label mappings.

D:

That result would be useful for a different failure, namely: A route to a service PE resolves in inet.0 but cannot resolve to the expected MPLS transport path. The current case specifically calls for: Explain local label significance and neighbor label binding. The required observed result is: A path test records locally valid incoming and outgoing label mappings.

Question 102

A new peer sends more customer routes than expected and the team assumes BGP automatically filters unrelated prefixes. Which post-change observation most strongly confirms the correction?

  1. The test confirms that only approved customer prefixes enter the provider's active routing table.
  2. Expected observation: A controlled route lookup confirms the neighbor's actual selected entry path.
  3. Verification result: A test packet follows its segment list through installed SR forwarding.
  4. Closeout evidence: A neighbor route view confirms the approved community-tagged routes are sent.

Explanation

Correct Answer

A:

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

Incorrect Answers

B:

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 bGP route acceptance must be constrained rather than inferred from neighbor identity. Test for: Only approved customer prefixes enter the provider's active routing table.

C:

This answer would be more suitable when a provider chooses segment-routing MPLS but assumes every transit hop needs per-LSP RSVP state, where the corrective action is to review segment identifiers and forwarding under SR-MPLS. The failure here is different: BGP route acceptance must be constrained rather than inferred from neighbor identity. Required validation: Only approved customer prefixes enter the provider's active routing table.

D:

This option overlooks the decisive condition. Its supporting principle is policy inheritance and term action order affect BGP route advertisement, while this scenario depends on bGP route acceptance must be constrained rather than inferred from neighbor identity. Verify the correction with: Only approved customer prefixes enter the provider's active routing table.

Question 103

A provider router has a static route for a customer prefix but its configured next hop is not reachable through any active route. What remediation is most directly applicable?

  1. Recommended change: Compare installed forwarding entries with interface operational status and adjacency resolution.
  2. Next step: Verify recursive next-hop reachability before relying on the static route.
  3. Corrective action: Evaluate policy terms in effective order and test matching routes.
  4. Apply this control: Evaluate routing-table relationships and next-hop resolution when using RIB groups.

Explanation

Correct Answer

B:

The critical observation is: A configured static route need not become usable forwarding state when its next hop cannot resolve. Correct it by taking this action: Verify recursive next-hop reachability before relying on the static route. Confirm the outcome with: A route lookup shows an active reachable next hop and traffic reaches the customer.

Incorrect Answers

A:

The proposed principle concerns another network fault: Forwarding-table and interface evidence localize faults beyond RIB reachability. Here, a configured static route need not become usable forwarding state when its next hop cannot resolve. The most direct correction is to verify recursive next-hop reachability before relying on the static route, confirmed by a route lookup shows an active reachable next hop and traffic reaches the customer.

C:

This response would target a different source scenario: A BGP prefix remains rejected after an intended route filter update because an earlier term rejects it. It cannot establish the current acceptance requirement, which is: A route lookup shows an active reachable next hop and traffic reaches the customer. The relevant action is: Verify recursive next-hop reachability before relying on the static route.

D:

Evaluate routing-table relationships and next-hop resolution when using RIB groups is a relevant step for the separate scenario in which a route leaked to a second routing table unexpectedly carries a next hop that cannot be resolved there. It does not directly fix this case. Instead verify recursive next-hop reachability before relying on the static route; verify: A route lookup shows an active reachable next hop and traffic reaches the customer.

Question 104

An engineer expects an IS-IS Designated Intermediate System election on a point-to-point core link. Which post-change observation most strongly confirms the correction?

  1. Closeout evidence: A protocol decode identifies the expected advertised TLV information.
  2. Acceptance check: A captured received-path comparison explains which attribute selected the route.
  3. The test confirms that a point-to-point link reaches the expected adjacency state without DIS election.
  4. Expected observation: The allowed prefixes are present and denied test prefixes are absent.

Explanation

Correct Answer

C:

This option addresses the stated case rather than another networking issue. Principle: The IS-IS DIS concept applies to LANs rather than ordinary point-to-point links. Remedy: Differentiate multiaccess DIS election from point-to-point adjacency behavior. Proof: A point-to-point link reaches the expected adjacency state without DIS election.

Incorrect Answers

A:

This answer would be more suitable when an operator calls an IS-IS TLV a transport packet and ignores its role in link-state information, where the corrective action is to identify TLVs as structured information within IS-IS protocol data units. The failure here is different: The IS-IS DIS concept applies to LANs rather than ordinary point-to-point links. Required validation: A point-to-point link reaches the expected adjacency state without DIS election.

B:

This option overlooks the decisive condition. Its supporting principle is mED is not guaranteed to override local policy or earlier attributes, while this scenario depends on the IS-IS DIS concept applies to LANs rather than ordinary point-to-point links. Verify the correction with: A point-to-point link reaches the expected adjacency state without DIS election.

D:

The proposed principle concerns another network fault: Policy placement determines which prefixes influence a routing table or advertisement. Here, the IS-IS DIS concept applies to LANs rather than ordinary point-to-point links. The most direct correction is to differentiate multiaccess DIS election from point-to-point adjacency behavior, confirmed by a point-to-point link reaches the expected adjacency state without DIS election.

Question 105

A dual-Routing-Engine chassis uses GRES but an engineer assumes routing protocol control state is preserved without any other feature. What remediation is most directly applicable?

  1. Apply this control: Review session type, supported distributed behavior and switchover-appropriate intervals.
  2. Remediation: Compare root priority, bridge identifiers and current STP topology status.
  3. Recommended change: Distinguish member-link redundancy from a single physical failure domain.
  4. Next step: Differentiate forwarding continuity under GRES from routing-protocol state preservation.

Explanation

Correct Answer

D:

The case turns on the distinction that gRES preserves forwarding and kernel interface state but does not by itself retain the routing control plane. Apply this concrete engineering step: Differentiate forwarding continuity under GRES from routing-protocol state preservation. An acceptable verification outcome is: A switchover test assesses both packet forwarding and routing neighbor continuity.

Incorrect Answers

A:

This response would target a different source scenario: A BFD session flaps during Routing Engine switchover after aggressive timer tuning. It cannot establish the current acceptance requirement, which is: A switchover test assesses both packet forwarding and routing neighbor continuity. The relevant action is: Differentiate forwarding continuity under GRES from routing-protocol state preservation.

B:

Compare root priority, bridge identifiers and current STP topology status is a relevant step for the separate scenario in which a planned root bridge migration is configured but the operational root remains on the old switch. It does not directly fix this case. Instead differentiate forwarding continuity under GRES from routing-protocol state preservation; verify: A switchover test assesses both packet forwarding and routing neighbor continuity.

C:

The alternative addresses a failover plan relies on one physical interface carrying several links and calls it a redundant LAG, not the present root cause. Here the selected correction must reflect gRES preserves forwarding and kernel interface state but does not by itself retain the routing control plane. Test for: A switchover test assesses both packet forwarding and routing neighbor continuity.

Question 106

A route shows as active but the interface destination still drops traffic after an interface move. Which next action best resolves this observed routing or switching failure?

  1. Corrective action: Compare installed forwarding entries with interface operational status and adjacency resolution.
  2. Apply this control: Validate forwarding load-sharing configuration and run representative multi-flow traffic.
  3. Remediation: Distinguish internal LSAs from externally originated route information.
  4. Recommended change: Restrict routing-policy matches and validate the import and export boundary.

Explanation

Correct Answer

A:

Because forwarding-table and interface evidence localize faults beyond RIB reachability, the best response is to compare installed forwarding entries with interface operational status and adjacency resolution. A reviewer can close the technical case only after confirming that a test packet follows the expected active forwarding next hop and interface.

Incorrect Answers

B:

The proposed principle concerns another network fault: Load sharing should be evaluated with relevant flows rather than one ping stream. Here, forwarding-table and interface evidence localize faults beyond RIB reachability. The most direct correction is to compare installed forwarding entries with interface operational status and adjacency resolution, confirmed by a test packet follows the expected active forwarding next hop and interface.

C:

That result would be useful for a different failure, namely: A link-state database shows intra-area information but a site expects external routes from an unconfigured redistribution policy. The current case specifically calls for: Compare installed forwarding entries with interface operational status and adjacency resolution. The required observed result is: A test packet follows the expected active forwarding next hop and interface.

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: A test packet follows the expected active forwarding next hop and interface. The relevant action is: Compare installed forwarding entries with interface operational status and adjacency resolution.

Question 107

An IS-IS LAN is unstable after a VLAN move and DIS changes accompany repeated adjacency loss. Which root-cause explanation and corrective action fit the case?

  1. Root issue: IS-IS can convey multiple address families with appropriate support. Correction: Check the IPv6 family configuration and advertised reachability rather than rebuilding IPv4 adjacency.
  2. Cause: Neighbor discovery can succeed even when database exchange parameters prevent completion. Response: Check MTU and interface compatibility and inspect neighbor-state details.
  3. Diagnosis: An adjacency can be operational while a specific family or prefix is not advertised. Action: Distinguish IS-IS adjacency from address-family reachability advertisements.
  4. Explanation: Frequent topology churn can stem from physical and configuration issues rather than DIS alone. Repair: Inspect link quality, interface settings and DIS state before forcing election behavior.

Explanation

Correct Answer

D:

The critical observation is: Frequent topology churn can stem from physical and configuration issues rather than DIS alone. Correct it by taking this action: Inspect link quality, interface settings and DIS state before forcing election behavior. Confirm the outcome with: A stable neighbor and LAN LSP remain after link faults are corrected.

Incorrect Answers

A:

The alternative addresses iPv4 IS-IS routing works but IPv6 routes do not appear on a dual-stack backbone, not the present root cause. Here the selected correction must reflect frequent topology churn can stem from physical and configuration issues rather than DIS alone. Test for: A stable neighbor and LAN LSP remain after link faults are corrected.

B:

This answer would be more suitable when an OSPF trace shows Hellos received but database synchronization stalls at ExStart or Exchange, where the corrective action is to check MTU and interface compatibility and inspect neighbor-state details. The failure here is different: Frequent topology churn can stem from physical and configuration issues rather than DIS alone. Required validation: A stable neighbor and LAN LSP remain after link faults are corrected.

C:

This option overlooks the decisive condition. Its supporting principle is an adjacency can be operational while a specific family or prefix is not advertised, while this scenario depends on frequent topology churn can stem from physical and configuration issues rather than DIS alone. Verify the correction with: A stable neighbor and LAN LSP remain after link faults are corrected.

Question 108

An engineer expects a GRE tunnel to preserve the same maximum payload size as a native Ethernet path. Which protocol behavior most directly determines the correct diagnosis?

  1. The key distinction is: Encapsulation reduces effective payload MTU unless transport accommodates the extra headers.
  2. Protocol behavior: An LSP cannot follow an unavailable required hop.
  3. Underlying principle: GRE has no independent path if its outer transport becomes unreachable.
  4. Root design issue: Tunnel identification and routing-instance separation must be explicit in overlapping designs.

Explanation

Correct Answer

A:

This option addresses the stated case rather than another networking issue. Principle: Encapsulation reduces effective payload MTU unless transport accommodates the extra headers. Remedy: Account for outer IP and GRE header overhead in the MTU design. Proof: A large packet test respects the effective tunnel MTU without unwanted loss.

Incorrect Answers

B:

This response would target a different source scenario: An operator configured an explicit RSVP path through a link that is now administratively down. It cannot establish the current acceptance requirement, which is: A large packet test respects the effective tunnel MTU without unwanted loss. The relevant action is: Account for outer IP and GRE header overhead in the MTU design.

C:

Restore underlay endpoint reachability and then validate the inner tunnel route is a relevant step for the separate scenario in which a GRE tunnel over an IPv4 core stops passing traffic immediately after an underlay route withdraws. It does not directly fix this case. Instead account for outer IP and GRE header overhead in the MTU design; verify: A large packet test respects the effective tunnel MTU without unwanted loss.

D:

The alternative addresses two GRE tunnels share source and destination addresses while the design assumes ordinary routing will distinguish the services automatically, not the present root cause. Here the selected correction must reflect encapsulation reduces effective payload MTU unless transport accommodates the extra headers. Test for: A large packet test respects the effective tunnel MTU without unwanted loss.

Question 109

After a maintenance window a configured customer static prefix is missing from active routes despite no syntax errors. Which statement identifies the key design assumption that failed?

  1. The governing rule is: Operational route troubleshooting starts with active state and resolution evidence.
  2. The key distinction is: A configured static route need not become usable forwarding state when its next hop cannot resolve.
  3. Protocol behavior: Filter-based routing policy requires explicit match conditions and a safe default behavior.
  4. Underlying principle: Failover paths are governed by their actual configured metrics.

Explanation

Correct Answer

A:

The critical observation is: Operational route troubleshooting starts with active state and resolution evidence. Correct it by taking this action: Inspect the configuration, active route state and next-hop reachability before changing preference. Confirm the outcome with: The static route becomes active after the actual next-hop fault is corrected.

Incorrect Answers

B:

A configured static route need not become usable forwarding state when its next hop cannot resolve describes a neighboring protocol concern. In this case the controlling fact is operational route troubleshooting starts with active state and resolution evidence. A correct remediation would inspect the configuration, active route state and next-hop reachability before changing preference and demonstrate: The static route becomes active after the actual next-hop fault is corrected.

C:

The proposed principle concerns another network fault: Filter-based routing policy requires explicit match conditions and a safe default behavior. Here, operational route troubleshooting starts with active state and resolution evidence. The most direct correction is to inspect the configuration, active route state and next-hop reachability before changing preference, confirmed by the static route becomes active after the actual next-hop fault is corrected.

D:

That result would be useful for a different failure, namely: An OSPF route appears longer than expected after failover because a backup link's cost was never verified. The current case specifically calls for: Inspect the configuration, active route state and next-hop reachability before changing preference. The required observed result is: The static route becomes active after the actual next-hop fault is corrected.

Question 110

Two equal-cost next hops exist but a customer assumes every successive packet must alternate between links. Which change best corrects the failure without losing the intended design?

  1. Apply this control: Distinguish equal-cost multipath from the exact traffic-distribution algorithm used by the forwarding plane.
  2. Remediation: Confirm the explicit cost plan in a failure rehearsal using route and topology outputs.
  3. Recommended change: Review filter-based forwarding classification and the intended next-table selection.
  4. Next step: Inspect the configuration, active route state and next-hop reachability before changing preference.

Explanation

Correct Answer

A:

Correct diagnosis: Multiple eligible forwarding next hops do not guarantee per-packet round-robin use. The appropriate action is: Distinguish equal-cost multipath from the exact traffic-distribution algorithm used by the forwarding plane. The follow-up evidence required is: A controlled flow test verifies the selected load-sharing behavior.

Incorrect Answers

B:

The alternative addresses an OSPF route appears longer than expected after failover because a backup link's cost was never verified, not the present root cause. Here the selected correction must reflect multiple eligible forwarding next hops do not guarantee per-packet round-robin use. Test for: A controlled flow test verifies the selected load-sharing behavior.

C:

This answer would be more suitable when a router selects a route in one routing instance while the forwarding policy sends matching traffic into a different table, where the corrective action is to review filter-based forwarding classification and the intended next-table selection. The failure here is different: Multiple eligible forwarding next hops do not guarantee per-packet round-robin use. Required validation: A controlled flow test verifies the selected load-sharing behavior.

D:

This option overlooks the decisive condition. Its supporting principle is operational route troubleshooting starts with active state and resolution evidence, while this scenario depends on multiple eligible forwarding next hops do not guarantee per-packet round-robin use. Verify the correction with: A controlled flow test verifies the selected load-sharing behavior.

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