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 46

Question 450

An equal-cost path test sends nearly all flows across one member while both links remain operational. What operational check demonstrates that the intended outcome occurred?

  1. Expected observation: A negative test proves the unrelated customer prefix is absent from the target table.
  2. Verification result: The route is accepted only after the AS-path design is corrected.
  3. Closeout evidence: A documented multi-flow test matches the configured distribution policy.
  4. Acceptance check: The tenant-specific lookup resolves and the same source-based test reaches its destination.

Explanation

Correct Answer

C:

Correct diagnosis: Load sharing should be evaluated with relevant flows rather than one ping stream. The appropriate action is: Validate forwarding load-sharing configuration and run representative multi-flow traffic. The follow-up evidence required is: A documented multi-flow test matches the configured distribution policy.

Incorrect Answers

A:

Route redistribution must be intentionally scoped to prevent cross-tenant leakage describes a neighboring protocol concern. In this case the controlling fact is load sharing should be evaluated with relevant flows rather than one ping stream. A correct remediation would validate forwarding load-sharing configuration and run representative multi-flow traffic and demonstrate: A documented multi-flow test matches the configured distribution policy.

B:

The proposed principle concerns another network fault: BGP AS-path information can prevent routes from looping into an AS. Here, load sharing should be evaluated with relevant flows rather than one ping stream. The most direct correction is to validate forwarding load-sharing configuration and run representative multi-flow traffic, confirmed by a documented multi-flow test matches the configured distribution policy.

D:

This response would target a different source scenario: A provider PE can ping a customer in the master instance but probes in the tenant routing instance fail. It cannot establish the current acceptance requirement, which is: A documented multi-flow test matches the configured distribution policy. The relevant action is: Validate forwarding load-sharing configuration and run representative multi-flow traffic.

Question 451

A router in a nonbackbone area cannot reach a newly connected area through a topology that skips Area 0. Which technical explanation and controlled action address the symptom?

  1. Root issue: OSPF route selection follows each router's synchronized topology view. Correction: Inspect link-state databases and SPF output on affected routers.
  2. Cause: Multi-area OSPF design requires attention to backbone connectivity. Response: Review hierarchical OSPF backbone attachment and area border placement.
  3. Diagnosis: A discard summary can prevent loops but can blackhole traffic when reachability assumptions are wrong. Action: Document the discard behavior and determine whether the aggregate should remain advertised.
  4. Explanation: Passive OSPF interfaces can advertise networks without forming neighbors on that interface. Repair: Review the passive-interface configuration and required active neighbor links.

Explanation

Correct Answer

B:

Underlying cause: Multi-area OSPF design requires attention to backbone connectivity. Corrective action: review hierarchical OSPF backbone attachment and area border placement. Verify the outcome: The planned ABR topology provides verified interarea reachability.

Incorrect Answers

A:

The alternative addresses a site sees different OSPF routes after a topology edit and declares the protocol failed without checking LSDB consistency, not the present root cause. Here the selected correction must reflect multi-area OSPF design requires attention to backbone connectivity. Test for: The planned ABR topology provides verified interarea reachability.

C:

This option overlooks the decisive condition. Its supporting principle is a discard summary can prevent loops but can blackhole traffic when reachability assumptions are wrong, while this scenario depends on multi-area OSPF design requires attention to backbone connectivity. Verify the correction with: The planned ABR topology provides verified interarea reachability.

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 multi-area OSPF design requires attention to backbone connectivity. A correct remediation would review hierarchical OSPF backbone attachment and area border placement and demonstrate: The planned ABR topology provides verified interarea reachability.

Question 452

A peer announces an IPv6 prefix but the operator checks only the IPv4 BGP route family. Which change best corrects the failure without losing the intended design?

  1. Recommended change: Review BGP next-hop reachability and explicit next-hop handling.
  2. Next step: Compare negotiated timers and protocol logs with routing-engine and packet conditions.
  3. Corrective action: Verify negotiated address families and family-specific routing tables.
  4. Apply this control: Differentiate IP underlay reachability from LDP or RSVP control state.

Explanation

Correct Answer

C:

This is the model-intended best choice because bGP transport connectivity does not guarantee every address family is negotiated and active. The targeted correction is to verify negotiated address families and family-specific routing tables. Validate it by observing that the intended inet6 family receives and selects the IPv6 prefix.

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: Verify negotiated address families and family-specific routing tables. The required observed result is: The intended inet6 family receives and selects the IPv6 prefix.

B:

This response would target a different source scenario: An engineer modifies BGP keepalive or hold timers and the session flaps during CPU pressure. It cannot establish the current acceptance requirement, which is: The intended inet6 family receives and selects the IPv6 prefix. The relevant action is: Verify negotiated address families and family-specific routing tables.

D:

The alternative addresses a transport route is reachable through an IP interface but the LSP still fails due to incomplete label distribution, not the present root cause. Here the selected correction must reflect bGP transport connectivity does not guarantee every address family is negotiated and active. Test for: The intended inet6 family receives and selects the IPv6 prefix.

Question 453

Two GRE tunnels share source and destination addresses while the design assumes ordinary routing will distinguish the services automatically. Which corrective action and confirmation pair is most appropriate?

  1. Change: Verify instance ownership and route policy at both tunnel endpoints. Test: Traffic uses the tunnel in the intended customer routing instance only.
  2. Implement: Model endpoint encapsulation and decapsulation for IPv6-over-IPv4 transport. Verify: A tunnel packet is carried over IPv4 and decapsulated to IPv6 at the endpoint.
  3. Control: Distinguish the inner routed payload from outer unicast encapsulation. Accepted result: Underlay traces show the outer endpoint traffic without transit processing of inner routes.
  4. Action: Review tunnel identifiers, endpoint uniqueness and supported platform demultiplexing. Evidence: Each service test packet reaches its assigned tunnel context.

Explanation

Correct Answer

D:

The selected response implements the principle that tunnel identification and routing-instance separation must be explicit in overlapping designs. The engineer should review tunnel identifiers, endpoint uniqueness and supported platform demultiplexing. Successful confirmation means: Each service test packet reaches its assigned tunnel context.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is tunneling transport and customer route isolation are separate configurations, while this scenario depends on tunnel identification and routing-instance separation must be explicit in overlapping designs. Verify the correction with: Each service test packet reaches its assigned tunnel context.

B:

Tunneling carries one protocol over an underlay that may not route that payload natively describes a neighboring protocol concern. In this case the controlling fact is tunnel identification and routing-instance separation must be explicit in overlapping designs. A correct remediation would review tunnel identifiers, endpoint uniqueness and supported platform demultiplexing and demonstrate: Each service test packet reaches its assigned tunnel context.

C:

The proposed principle concerns another network fault: A tunnel can carry inner packet types over an underlay forwarding only the outer header. Here, tunnel identification and routing-instance separation must be explicit in overlapping designs. The most direct correction is to review tunnel identifiers, endpoint uniqueness and supported platform demultiplexing, confirmed by each service test packet reaches its assigned tunnel context.

Question 454

An area border router stops advertising an expected summarized interarea route after a policy change. Which cause-and-remedy pairing reflects the observed problem?

  1. Diagnosis: Layered neighbor troubleshooting should separate transport from OSPF parameter mismatches. Action: Compare area, interface mode, timers, authentication and physical status on both endpoints.
  2. Explanation: Interarea reachability depends on the ABR's view and allowed advertisements. Repair: Inspect ABR area configuration, route export rules and summary policy.
  3. Fault mechanism: IS-IS route dissemination follows hierarchical level boundaries. Remediation: Place the correct L1/L2 boundary and evaluate flooding scope.
  4. Root issue: OSPF network-type and Hello compatibility can prevent adjacency formation. Correction: Verify compatible network and Hello parameters including mask where applicable.

Explanation

Correct Answer

B:

This option addresses the stated case rather than another networking issue. Principle: Interarea reachability depends on the ABR's view and allowed advertisements. Remedy: Inspect ABR area configuration, route export rules and summary policy. Proof: The correct summarized route appears in the receiving area's route table.

Incorrect Answers

A:

Compare area, interface mode, timers, authentication and physical status on both endpoints is a relevant step for the separate scenario in which a new OSPF uplink remains down at the adjacency stage after a router replacement. It does not directly fix this case. Instead inspect ABR area configuration, route export rules and summary policy; verify: The correct summarized route appears in the receiving area's route table.

C:

This answer would be more suitable when a provider uses a Level 1-only router to interconnect two independent IS-IS areas and expects unrestricted cross-area flooding, where the corrective action is to place the correct L1/L2 boundary and evaluate flooding scope. The failure here is different: Interarea reachability depends on the ABR's view and allowed advertisements. Required validation: The correct summarized route appears in the receiving area's route table.

D:

This option overlooks the decisive condition. Its supporting principle is oSPF network-type and Hello compatibility can prevent adjacency formation, while this scenario depends on interarea reachability depends on the ABR's view and allowed advertisements. Verify the correction with: The correct summarized route appears in the receiving area's route table.

Question 455

A remote BGP neighbor uses a different AS number than configured and the session fails during OPEN negotiation. Which underlying Junos networking principle explains the failure?

  1. Underlying principle: Outer and inner labels can have distinct transport and service roles.
  2. Root design issue: Disabling loop prevention can introduce persistent interdomain routing loops.
  3. The governing rule is: iBGP can preserve externally learned next-hop information that internal speakers must resolve.
  4. The key distinction is: BGP OPEN negotiation includes AS identity that must match peering intent.

Explanation

Correct Answer

D:

Underlying cause: BGP OPEN negotiation includes AS identity that must match peering intent. Corrective action: confirm the configured local and peer AS values with the authoritative design. Verify the outcome: The session reaches Established only with the documented correct peer AS.

Incorrect Answers

A:

The proposed principle concerns another network fault: Outer and inner labels can have distinct transport and service roles. Here, bGP OPEN negotiation includes AS identity that must match peering intent. The most direct correction is to confirm the configured local and peer AS values with the authoritative design, confirmed by the session reaches Established only with the documented correct peer AS.

B:

That result would be useful for a different failure, namely: A provider accepts a route with its own AS in the received path after a risky bypass of loop prevention. The current case specifically calls for: Confirm the configured local and peer AS values with the authoritative design. The required observed result is: The session reaches Established only with the documented correct peer AS.

C:

This response would target a different source scenario: A provider's iBGP peer receives a route but cannot resolve the external next hop in its own IGP. 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.

Question 456

A multihop EBGP session is configured like a directly connected neighbor and never establishes across the transit hop. Which next action best resolves this observed routing or switching failure?

  1. Next step: Review EBGP multihop transport reachability and session parameters.
  2. Corrective action: Inspect local preference, export/import inheritance and selected BGP path attributes.
  3. Apply this control: Inspect the incoming label, outgoing label and interface on each affected LSR.
  4. Remediation: Evaluate routing-policy local preference before later BGP path-selection attributes.

Explanation

Correct Answer

A:

This is the model-intended best choice because eBGP speakers separated by intermediate devices require deliberate transport reachability and hop policy. The targeted correction is to review EBGP multihop transport reachability and session parameters. Validate it by observing that the TCP session establishes across the intended transport path.

Incorrect Answers

B:

This option overlooks the decisive condition. Its supporting principle is routing policy changes can override expected primary and backup peering intent, while this scenario depends on eBGP speakers separated by intermediate devices require deliberate transport reachability and hop policy. Verify the correction with: The TCP session establishes across the intended transport path.

C:

Label-switching errors can occur even when control-plane endpoint reachability is good describes a neighboring protocol concern. In this case the controlling fact is eBGP speakers separated by intermediate devices require deliberate transport reachability and hop policy. A correct remediation would review EBGP multihop transport reachability and session parameters and demonstrate: The TCP session establishes across the intended transport path.

D:

The proposed principle concerns another network fault: BGP best-path selection considers higher-priority decision attributes before AS-path length. Here, eBGP speakers separated by intermediate devices require deliberate transport reachability and hop policy. The most direct correction is to review EBGP multihop transport reachability and session parameters, confirmed by the TCP session establishes across the intended transport path.

Question 457

A transport route is reachable through an IP interface but the LSP still fails due to incomplete label distribution. Which statement identifies the key design assumption that failed?

  1. The key distinction is: RSVP-TE path choice can account for configured topology constraints and resources.
  2. Protocol behavior: Label stack changes can be legitimate parts of LSP forwarding design.
  3. Underlying principle: MPLS forwarding requires coordinated label signaling and forwarding entries.
  4. Root design issue: BGP best-path selection considers higher-priority decision attributes before AS-path length.

Explanation

Correct Answer

C:

The critical observation is: MPLS forwarding requires coordinated label signaling and forwarding entries. Correct it by taking this action: Differentiate IP underlay reachability from LDP or RSVP control state. Confirm the outcome with: The label table and LSP state match the intended forwarding path.

Incorrect Answers

A:

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 label table and LSP state match the intended forwarding path. The relevant action is: Differentiate IP underlay reachability from LDP or RSVP control state.

B:

Verify whether PHP or explicit-null behavior is configured and intended is a relevant step for the separate scenario in which an MPLS packet trace shows the outer label is removed earlier than expected and the engineer calls it a malformed packet. It does not directly fix this case. Instead differentiate IP underlay reachability from LDP or RSVP control state; verify: The label table and LSP state match the intended forwarding path.

D:

This answer would be more suitable when two BGP paths have different local preferences and a technician expects the shorter AS path always to win, where the corrective action is to evaluate routing-policy local preference before later BGP path-selection attributes. The failure here is different: MPLS forwarding requires coordinated label signaling and forwarding entries. Required validation: The label table and LSP state match the intended forwarding path.

Question 458

A router sends OSPF Hello packets but remains stuck because the subnet mask differs across neighbors on a broadcast link. What action-and-test pairing directly resolves the case?

  1. Change: Constrain redistribution and test route policy acceptance for the intended prefixes. Test: Only approved external prefixes appear in the OSPF domain.
  2. Implement: Verify compatible network and Hello parameters including mask where applicable. Verify: A controlled neighbor check reaches Full after configuration correction.
  3. Control: Inspect ABR area configuration, route export rules and summary policy. Accepted result: The correct summarized route appears in the receiving area's route table.
  4. Action: Validate forwarding load-sharing configuration and run representative multi-flow traffic. Evidence: A documented multi-flow test matches the configured distribution policy.

Explanation

Correct Answer

B:

This is the model-intended best choice because oSPF network-type and Hello compatibility can prevent adjacency formation. The targeted correction is to verify compatible network and Hello parameters including mask where applicable. Validate it by observing that a controlled neighbor check reaches Full after configuration correction.

Incorrect Answers

A:

Routing policy controls which external reachability is injected into OSPF 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.

C:

That result would be useful for a different failure, namely: An area border router stops advertising an expected summarized interarea route after a policy change. 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.

D:

This response would target a different source scenario: An equal-cost path test sends nearly all flows across one member while both links remain operational. 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 459

A provider STP domain changes root when a customer sends superior BPDUs from an access port. What assessment accurately links the fault to its correction?

  1. Diagnosis: Loop prevention depends on compatible STP participation across redundant Ethernet links. Action: Inspect STP state and enable the approved spanning-tree protocol for that bridge domain.
  2. Explanation: VLAN reassignment must be verified in actual port classification. Repair: Check committed access VLAN settings and operational membership rather than relying on notes.
  3. Fault mechanism: BPDU protection can prevent rogue switching from affecting a designated edge port. Remediation: Apply suitable BPDU protection according to edge-port policy.
  4. Root issue: Customer control traffic must not displace the authorized provider root. Correction: Apply supported root protection at the appropriate customer-facing boundary.

Explanation

Correct Answer

D:

The critical observation is: Customer control traffic must not displace the authorized provider root. Correct it by taking this action: Apply supported root protection at the appropriate customer-facing boundary. Confirm the outcome with: A superior BPDU test preserves the intended root with a logged protective state.

Incorrect Answers

A:

The alternative addresses a new redundant uplink produces a broadcast storm on an access VLAN, not the present root cause. Here the selected correction must reflect customer control traffic must not displace the authorized provider root. Test for: A superior BPDU test preserves the intended root with a logged protective state.

B:

This answer would be more suitable when an access switch forwards untagged traffic into VLAN 20 after a port is moved to VLAN 30, where the corrective action is to check committed access VLAN settings and operational membership rather than relying on notes. The failure here is different: Customer control traffic must not displace the authorized provider root. Required validation: A superior BPDU test preserves the intended root with a logged protective state.

C:

This option overlooks the decisive condition. Its supporting principle is bPDU protection can prevent rogue switching from affecting a designated edge port, while this scenario depends on customer control traffic must not displace the authorized provider root. Verify the correction with: A superior BPDU test preserves the intended root with a logged protective state.

Question 460

A technician tries to diagnose an IS-IS area failure only by inspecting IP multicast Hellos. Which corrective action and confirmation pair is most appropriate?

  1. Action: Recognize IS-IS as a link-layer routing protocol with its own PDUs. Evidence: A link-level packet trace observes the relevant IS-IS PDUs.
  2. Repair: Compare NET area addresses and intended L1 or L2 adjacency mode. Check: A protocol check shows the authorized level and matching adjacency.
  3. Change: Differentiate multiaccess DIS election from point-to-point adjacency behavior. Test: A point-to-point link reaches the expected adjacency state without DIS election.
  4. Implement: Inspect TCP reachability, permitted port 179, and authentication on the transport path. Verify: An authenticated TCP session stays Established after the rule correction.

Explanation

Correct Answer

A:

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

B:

This response would target a different source scenario: Two routers exchange IS-IS Hellos but one rejects the neighbor during area validation. It cannot establish the current acceptance requirement, which is: A link-level packet trace observes the relevant IS-IS PDUs. The relevant action is: Recognize IS-IS as a link-layer routing protocol with its own PDUs.

C:

Differentiate multiaccess DIS election from point-to-point adjacency behavior is a relevant step for the separate scenario in which an engineer expects an IS-IS Designated Intermediate System election on a point-to-point core link. 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.

D:

The alternative addresses an EBGP peer drops repeatedly after a firewall change despite clean interface counters, not the present root cause. Here the selected correction must reflect iS-IS packet exchange and transport differ from OSPF over IP. Test for: A link-level packet trace observes the relevant IS-IS PDUs.

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