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 51

Question 500

An NSR configuration fails commit after an operator adds graceful restart on the same device. What observable result most directly verifies the intended configuration?

  1. Expected observation: An authorized switchover maintains bridge control state and service reachability.
  2. Verification result: The fault is visible and surviving members carry traffic within the approved limits.
  3. Closeout evidence: The corrected candidate commits and the Routing Engine synchronization check passes.
  4. Acceptance check: A controlled neighbor check reaches Full after configuration correction.

Explanation

Correct Answer

C:

This is the model-intended best choice because conflicting local GR and NSR configuration must be resolved before activation. The targeted correction is to remove the incompatible local mode and validate the supported HA configuration. Validate it by observing that the corrected candidate commits and the Routing Engine synchronization check passes.

Incorrect Answers

A:

That result would be useful for a different failure, namely: An Ethernet service must retain bridge state during Routing Engine failover but only Layer 3 HA settings are considered. The current case specifically calls for: Remove the incompatible local mode and validate the supported HA configuration. The required observed result is: The corrected candidate commits and the Routing Engine synchronization check passes.

B:

This response would target a different source scenario: One LAG member fails silently and the service loses capacity even though the logical interface remains active. It cannot establish the current acceptance requirement, which is: The corrected candidate commits and the Routing Engine synchronization check passes. The relevant action is: Remove the incompatible local mode and validate the supported HA configuration.

D:

The alternative addresses a router sends OSPF Hello packets but remains stuck because the subnet mask differs across neighbors on a broadcast link, not the present root cause. Here the selected correction must reflect conflicting local GR and NSR configuration must be resolved before activation. Test for: The corrected candidate commits and the Routing Engine synchronization check passes.

Question 501

An engineer treats a BGP community value as a standalone forwarding next hop. Which cause-and-remedy pairing reflects the observed problem?

  1. Explanation: Communities are policy signaling metadata and not the packet-forwarding next hop themselves. Repair: Differentiate community tags from reachability and forwarding attributes.
  2. Fault mechanism: Neighbor state must be traced through transport before modifying route policy. Remediation: Verify IP reachability, routing instance context, TCP transport and session authentication.
  3. Root issue: BGP message types have separate roles in session formation and reachability exchange. Correction: Distinguish session negotiation from UPDATE message route advertisements.
  4. Cause: OSPF uses distinct Hello, database description, link state request, update and acknowledgment functions. Response: Differentiate neighbor discovery from database synchronization message types.

Explanation

Correct Answer

A:

The critical observation is: Communities are policy signaling metadata and not the packet-forwarding next hop themselves. Correct it by taking this action: Differentiate community tags from reachability and forwarding attributes. Confirm the outcome with: Policy based on the intended community alters admission or preference as designed.

Incorrect Answers

B:

Neighbor state must be traced through transport before modifying route policy describes a neighboring protocol concern. In this case the controlling fact is communities are policy signaling metadata and not the packet-forwarding next hop themselves. A correct remediation would differentiate community tags from reachability and forwarding attributes and demonstrate: Policy based on the intended community alters admission or preference as designed.

C:

The proposed principle concerns another network fault: BGP message types have separate roles in session formation and reachability exchange. Here, communities are policy signaling metadata and not the packet-forwarding next hop themselves. The most direct correction is to differentiate community tags from reachability and forwarding attributes, confirmed by policy based on the intended community alters admission or preference as designed.

D:

That result would be useful for a different failure, namely: A technician treats an OSPF Link State Request as the same message as a Hello packet. The current case specifically calls for: Differentiate community tags from reachability and forwarding attributes. The required observed result is: Policy based on the intended community alters admission or preference as designed.

Question 502

A provider router has a static route for a customer prefix but its configured next hop is not reachable through any active route. What operational check demonstrates that the intended outcome occurred?

  1. Verification result: A route lookup shows an active reachable next hop and traffic reaches the customer.
  2. Closeout evidence: The selected path and its preference match the intended backup policy.
  3. Acceptance check: The internal router resolves the next hop and installs the intended route.
  4. The test confirms that a primary-link test chooses the expected primary then fails to backup on loss.

Explanation

Correct Answer

A:

Correct diagnosis: A configured static route need not become usable forwarding state when its next hop cannot resolve. The appropriate action is: Verify recursive next-hop reachability before relying on the static route. The follow-up evidence required is: A route lookup shows an active reachable next hop and traffic reaches the customer.

Incorrect Answers

B:

The alternative addresses two static routes for the same prefix have unequal preferences and the operator expects both paths to share traffic, not the present root cause. Here the selected correction must reflect a configured static route need not become usable forwarding state when its next hop cannot resolve. Test for: A route lookup shows an active reachable next hop and traffic reaches the customer.

C:

This answer would be more suitable when an iBGP route is hidden because the next hop learned from an edge router is unreachable inside the backbone, where the corrective action is to restore appropriate IGP next-hop reachability or approved next-hop-self behavior. The failure here is different: A configured static route need not become usable forwarding state when its next hop cannot resolve. Required validation: A route lookup shows an active reachable next hop and traffic reaches the customer.

D:

This option overlooks the decisive condition. Its supporting principle is preference edits can change route selection without any interface outage, while this scenario depends on a configured static route need not become usable forwarding state when its next hop cannot resolve. Verify the correction with: A route lookup shows an active reachable next hop and traffic reaches the customer.

Question 503

A router sends OSPF Hello packets but remains stuck because the subnet mask differs across neighbors on a broadcast link. Which protocol behavior most directly determines the correct diagnosis?

  1. Underlying principle: DR and BDR elections apply to broadcast or NBMA segments, not ordinary point-to-point links.
  2. Root design issue: OSPF forwarding decisions depend on cumulative metric, not interface bandwidth labels alone.
  3. The governing rule is: IS-IS routing levels determine topology knowledge and area reachability.
  4. The key distinction is: OSPF network-type and Hello compatibility can prevent adjacency formation.

Explanation

Correct Answer

D:

Underlying cause: OSPF network-type and Hello compatibility can prevent adjacency formation. Corrective action: verify compatible network and Hello parameters including mask where applicable. Verify the outcome: A controlled neighbor check reaches Full after configuration correction.

Incorrect Answers

A:

The proposed principle concerns another network fault: DR and BDR elections apply to broadcast or NBMA segments, not ordinary point-to-point links. Here, oSPF network-type and Hello compatibility can prevent adjacency formation. The most direct correction is to verify compatible network and Hello parameters including mask where applicable, confirmed by a controlled neighbor check reaches Full after configuration correction.

B:

That result would be useful for a different failure, namely: OSPF route preference changes after a new link is added and a latency-sensitive service takes the wrong path. The current case specifically calls for: Verify compatible network and Hello parameters including mask where applicable. The required observed result is: A controlled neighbor check reaches Full after configuration correction.

C:

This response would target a different source scenario: A router learns a local IS-IS topology but cannot infer reachability in a remote area from its Level 1-only view. It cannot establish the current acceptance requirement, which is: A controlled neighbor check reaches Full after configuration correction. The relevant action is: Verify compatible network and Hello parameters including mask where applicable.

Question 504

An operator calls an IS-IS TLV a transport packet and ignores its role in link-state information. Which next action best resolves this observed routing or switching failure?

  1. Next step: Identify TLVs as structured information within IS-IS protocol data units.
  2. Corrective action: Review route-reflector client and cluster design, including loop-prevention attributes.
  3. Apply this control: Rehearse the failure and inspect active next hops and IS-IS route changes.
  4. Remediation: Verify compatible area membership or use the designed Level 2 boundary.

Explanation

Correct Answer

A:

This is the model-intended best choice because iS-IS advertises extensible routing attributes using TLV-encoded fields. The targeted correction is to identify TLVs as structured information within IS-IS protocol data units. Validate it by observing that a protocol decode identifies the expected advertised TLV information.

Incorrect Answers

B:

This option overlooks the decisive condition. Its supporting principle is route reflection relies on correct client boundaries and originator or cluster tracking, while this scenario depends on iS-IS advertises extensible routing attributes using TLV-encoded fields. Verify the correction with: A protocol decode identifies the expected advertised TLV information.

C:

A backup path requires functional forwarding, not merely topology presence describes a neighboring protocol concern. In this case the controlling fact is iS-IS advertises extensible routing attributes using TLV-encoded fields. A correct remediation would identify TLVs as structured information within IS-IS protocol data units and demonstrate: A protocol decode identifies the expected advertised TLV information.

D:

The proposed principle concerns another network fault: IS-IS Level 1 adjacency formation depends on common area context. Here, iS-IS advertises extensible routing attributes using TLV-encoded fields. The most direct correction is to identify TLVs as structured information within IS-IS protocol data units, confirmed by a protocol decode identifies the expected advertised TLV information.

Question 505

A provider tunnels traffic for customer isolation but makes no decision about routing-policy exposure at the tunnel edge. Which protocol behavior most directly determines the correct diagnosis?

  1. The key distinction is: Encapsulation does not replace explicit customer route filtering and access policy.
  2. Protocol behavior: A tunnel can carry inner packet types over an underlay forwarding only the outer header.
  3. Underlying principle: Tunnel endpoint parameters must correspond to actual reachable interfaces.
  4. Root design issue: IPv6 route selection follows prefix matching and route eligibility, not textual address order.

Explanation

Correct Answer

A:

Underlying cause: Encapsulation does not replace explicit customer route filtering and access policy. Corrective action: treat tunnel decapsulation as a routing and security boundary. Verify the outcome: Only authorized customer prefixes enter or leave the decapsulated routing context.

Incorrect Answers

B:

Distinguish the inner routed payload from outer unicast encapsulation is a relevant step for the separate scenario in which an operator sends a multicast routing-protocol packet over a GRE tunnel and assumes all physical transit routers must process the inner multicast. It does not directly fix this case. Instead treat tunnel decapsulation as a routing and security boundary; verify: Only authorized customer prefixes enter or leave the decapsulated routing context.

C:

The alternative addresses a GRE tunnel interface exists but its operational state is unreliable because the source interface was changed, not the present root cause. Here the selected correction must reflect encapsulation does not replace explicit customer route filtering and access policy. Test for: Only authorized customer prefixes enter or leave the decapsulated routing context.

D:

This answer would be more suitable when an engineer chooses an IPv6 route based on the printed address alone without comparing prefix length, where the corrective action is to apply longest-prefix-match route lookup to the IPv6 destination. The failure here is different: Encapsulation does not replace explicit customer route filtering and access policy. Required validation: Only authorized customer prefixes enter or leave the decapsulated routing context.

Question 506

Two equal-capacity IS-IS links receive unequal metrics and traffic takes an unexpected path. Which root-cause explanation and corrective action fit the case?

  1. Explanation: IS-IS path selection is based on link-state topology and metrics. Repair: Compute total advertised IS-IS metrics instead of assuming capacity implies preference.
  2. Fault mechanism: Communities are policy signaling metadata and not the packet-forwarding next hop themselves. Remediation: Differentiate community tags from reachability and forwarding attributes.
  3. Root issue: A backup path requires functional forwarding, not merely topology presence. Correction: Rehearse the failure and inspect active next hops and IS-IS route changes.
  4. Cause: IS-IS routing levels determine topology knowledge and area reachability. Response: Review Level 1 and Level 2 routing roles and their intended boundaries.

Explanation

Correct Answer

A:

Because iS-IS path selection is based on link-state topology and metrics, the best response is to compute total advertised IS-IS metrics instead of assuming capacity implies preference. A reviewer can close the technical case only after confirming that the forwarding route follows the lowest intended metric path.

Incorrect Answers

B:

The proposed principle concerns another network fault: Communities are policy signaling metadata and not the packet-forwarding next hop themselves. Here, iS-IS path selection is based on link-state topology and metrics. The most direct correction is to compute total advertised IS-IS metrics instead of assuming capacity implies preference, confirmed by the forwarding route follows the lowest intended metric path.

C:

That result would be useful for a different failure, namely: A provider failover exposes an alternate IS-IS path that had never been tested for next-hop resolution. The current case specifically calls for: Compute total advertised IS-IS metrics instead of assuming capacity implies preference. The required observed result is: The forwarding route follows the lowest intended metric path.

D:

This response would target a different source scenario: A router learns a local IS-IS topology but cannot infer reachability in a remote area from its Level 1-only view. It cannot establish the current acceptance requirement, which is: The forwarding route follows the lowest intended metric path. The relevant action is: Compute total advertised IS-IS metrics instead of assuming capacity implies preference.

Question 507

An IS-IS change carries IPv4 traffic but a new IPv6 prefix is missing from a remote PE. Which evidence would justify closing this troubleshooting case?

  1. Verification result: The forwarding route follows the lowest intended metric path.
  2. Closeout evidence: IPv6 test packets traverse the restored tunnel with appropriate MTU handling.
  3. Acceptance check: A tunnel packet is carried over IPv4 and decapsulated to IPv6 at the endpoint.
  4. The test confirms that the remote PE learns and uses the intended IPv6 prefix.

Explanation

Correct Answer

D:

The critical observation is: Dual-stack IS-IS troubleshooting requires family-specific advertisement evidence. Correct it by taking this action: Inspect IPv6 reachability TLVs, family configuration and active inet6 route state. Confirm the outcome with: The remote PE learns and uses the intended IPv6 prefix.

Incorrect Answers

A:

The alternative addresses two equal-capacity IS-IS links receive unequal metrics and traffic takes an unexpected path, not the present root cause. Here the selected correction must reflect dual-stack IS-IS troubleshooting requires family-specific advertisement evidence. Test for: The remote PE learns and uses the intended IPv6 prefix.

B:

This answer would be more suitable when iPv6-over-IPv4 tunnel endpoints reach each other using IPv4 but IPv6 payloads fail after a firewall update, where the corrective action is to verify tunnel protocol allowance, endpoint encapsulation and effective MTU. The failure here is different: Dual-stack IS-IS troubleshooting requires family-specific advertisement evidence. Required validation: The remote PE learns and uses the intended IPv6 prefix.

C:

This option overlooks the decisive condition. Its supporting principle is tunneling carries one protocol over an underlay that may not route that payload natively, while this scenario depends on dual-stack IS-IS troubleshooting requires family-specific advertisement evidence. Verify the correction with: The remote PE learns and uses the intended IPv6 prefix.

Question 508

A route to a service PE resolves in inet.0 but cannot resolve to the expected MPLS transport path. Which technical explanation and controlled action address the symptom?

  1. Cause: A labeled transport next hop must be available to carry the overlay service. Response: Inspect Junos MPLS-related next-hop resolution and available LSP endpoints.
  2. Diagnosis: An upstream LSR can remove a label before the egress in an appropriate PHP design. Action: Recognize penultimate-hop popping as an allowed LSP forwarding behavior.
  3. Explanation: A healthy transport LSP does not guarantee a correct overlay label mapping. Repair: Inspect outer transport and inner service label handling separately.
  4. Fault mechanism: iBGP scaling mechanisms reduce the full-mesh session requirement. Remediation: Evaluate route reflection with defined cluster and client boundaries.

Explanation

Correct Answer

A:

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

B:

This response would target a different source scenario: A penultimate router pops a transport label and the egress receives native IP even though the engineer expected a visible final outer label. It cannot establish the current acceptance requirement, which is: The remote PE service route resolves over the designated LSP. The relevant action is: Inspect Junos MPLS-related next-hop resolution and available LSP endpoints.

C:

Inspect outer transport and inner service label handling separately is a relevant step for the separate scenario in which a customer overlay fails across an MPLS core only for one service label. It does not directly fix this case. Instead inspect Junos MPLS-related next-hop resolution and available LSP endpoints; verify: The remote PE service route resolves over the designated LSP.

D:

The alternative addresses a small full-mesh iBGP design becomes difficult to maintain as dozens of PEs are added, not the present root cause. Here the selected correction must reflect a labeled transport next hop must be available to carry the overlay service. Test for: The remote PE service route resolves over the designated LSP.

Question 509

An access switch forwards untagged traffic into VLAN 20 after a port is moved to VLAN 30. Which root-cause explanation and corrective action fit the case?

  1. Root issue: Provider outer VLAN classification must preserve tenant isolation. Correction: Assign distinct service encapsulation and verify edge translation rules.
  2. Cause: A trunk carries only its configured authorized VLANs. Response: Review allowed VLAN membership on both trunk endpoints.
  3. Diagnosis: Conflicting local GR and NSR configuration must be resolved before activation. Action: Remove the incompatible local mode and validate the supported HA configuration.
  4. Explanation: VLAN reassignment must be verified in actual port classification. Repair: Check committed access VLAN settings and operational membership rather than relying on notes.

Explanation

Correct Answer

D:

The selected response implements the principle that vLAN reassignment must be verified in actual port classification. The engineer should check committed access VLAN settings and operational membership rather than relying on notes. Successful confirmation means: The moved test port places incoming untagged frames only in VLAN 30.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is provider outer VLAN classification must preserve tenant isolation, while this scenario depends on vLAN reassignment must be verified in actual port classification. Verify the correction with: The moved test port places incoming untagged frames only in VLAN 30.

B:

A trunk carries only its configured authorized VLANs describes a neighboring protocol concern. In this case the controlling fact is vLAN reassignment must be verified in actual port classification. A correct remediation would check committed access VLAN settings and operational membership rather than relying on notes and demonstrate: The moved test port places incoming untagged frames only in VLAN 30.

C:

The proposed principle concerns another network fault: Conflicting local GR and NSR configuration must be resolved before activation. Here, vLAN reassignment must be verified in actual port classification. The most direct correction is to check committed access VLAN settings and operational membership rather than relying on notes, confirmed by the moved test port places incoming untagged frames only in VLAN 30.

Question 510

A remote BGP neighbor uses a different AS number than configured and the session fails during OPEN negotiation. What is the most defensible network engineering correction?

  1. Recommended change: Review EBGP multihop transport reachability and session parameters.
  2. Next step: Confirm the configured local and peer AS values with the authoritative design.
  3. Corrective action: Verify IP reachability, routing instance context, TCP transport and session authentication.
  4. Apply this control: Check DR and BDR roles and expected 2-Way peers before changing a healthy segment.

Explanation

Correct Answer

B:

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

A:

Review EBGP multihop transport reachability and session parameters is a relevant step for the separate scenario in which a multihop EBGP session is configured like a directly connected neighbor and never establishes across the transit hop. 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.

C:

This answer would be more suitable when a BGP peer is stuck in Active after a maintenance window even though the remote address is configured, where the corrective action is to verify IP reachability, routing instance context, TCP transport and session authentication. The failure here is different: BGP OPEN negotiation includes AS identity that must match peering intent. Required validation: The session reaches Established only with the documented correct peer AS.

D:

This option overlooks the decisive condition. Its supporting principle is oSPF neighbor-state interpretation depends on multiaccess election roles, while this scenario depends on bGP OPEN negotiation includes AS identity that must match peering intent. Verify the correction with: The session reaches Established only with the documented correct peer AS.

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