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 43

Question 420

An ingress LSP shows up but transit packets are dropped after one router swaps to an unexpected label. What observable result most directly verifies the intended configuration?

  1. Expected observation: The corrected transit hop forwards the expected incoming label to its planned outgoing label.
  2. Verification result: The repaired hop has the expected swap operation and carries a test packet.
  3. Closeout evidence: A packet decode identifies label fields separately from the carried IP packet.
  4. Acceptance check: The intended local preference policy selects the approved egress.

Explanation

Correct Answer

B:

Because label-switching errors can occur even when control-plane endpoint reachability is good, the best response is to inspect the incoming label, outgoing label and interface on each affected LSR. A reviewer can close the technical case only after confirming that the repaired hop has the expected swap operation and carries a test packet.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A maintenance change affects MPLS forwarding on just one core hop and the team only checks RSVP session status at ingress. The current case specifically calls for: Inspect the incoming label, outgoing label and interface on each affected LSR. The required observed result is: The repaired hop has the expected swap operation and carries a test packet.

C:

Distinguish the MPLS shim label stack from the encapsulated payload is a relevant step for the separate scenario in which an operator expects an MPLS label to represent an entire customer IP packet header. It does not directly fix this case. Instead inspect the incoming label, outgoing label and interface on each affected LSR; verify: The repaired hop has the expected swap operation and carries a test packet.

D:

The alternative addresses two BGP paths have different local preferences and a technician expects the shorter AS path always to win, not the present root cause. Here the selected correction must reflect label-switching errors can occur even when control-plane endpoint reachability is good. Test for: The repaired hop has the expected swap operation and carries a test packet.

Question 421

Small probes pass through GRE but large customer packets are intermittently dropped. Which cause-and-remedy pairing reflects the observed problem?

  1. Root issue: Tunneling transport and customer route isolation are separate configurations. Correction: Verify instance ownership and route policy at both tunnel endpoints.
  2. Cause: GRE encapsulation overhead can expose MTU blackholes for larger payloads. Response: Test effective MTU and path MTU discovery across the encapsulated route.
  3. Diagnosis: Label stack changes can be legitimate parts of LSP forwarding design. Action: Verify whether PHP or explicit-null behavior is configured and intended.
  4. Explanation: A tunnel can carry inner packet types over an underlay forwarding only the outer header. Repair: Distinguish the inner routed payload from outer unicast encapsulation.

Explanation

Correct Answer

B:

The case turns on the distinction that gRE encapsulation overhead can expose MTU blackholes for larger payloads. Apply this concrete engineering step: Test effective MTU and path MTU discovery across the encapsulated route. An acceptable verification outcome is: A controlled large-payload test succeeds after MTU or MSS adjustment.

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 gRE encapsulation overhead can expose MTU blackholes for larger payloads. Verify the correction with: A controlled large-payload test succeeds after MTU or MSS adjustment.

C:

The proposed principle concerns another network fault: Label stack changes can be legitimate parts of LSP forwarding design. Here, gRE encapsulation overhead can expose MTU blackholes for larger payloads. The most direct correction is to test effective MTU and path MTU discovery across the encapsulated route, confirmed by a controlled large-payload test succeeds after MTU or MSS adjustment.

D:

That result would be useful for a different failure, namely: An operator sends a multicast routing-protocol packet over a GRE tunnel and assumes all physical transit routers must process the inner multicast. The current case specifically calls for: Test effective MTU and path MTU discovery across the encapsulated route. The required observed result is: A controlled large-payload test succeeds after MTU or MSS adjustment.

Question 422

A core engineer sees that IPv6 reachability is absent despite IS-IS adjacency and concludes the adjacency itself is broken. What is the most defensible network engineering correction?

  1. Recommended change: Compare area, interface mode, timers, authentication and physical status on both endpoints.
  2. Next step: Recognize IS-IS as a link-layer routing protocol with its own PDUs.
  3. Corrective action: Distinguish IS-IS adjacency from address-family reachability advertisements.
  4. Apply this control: Collect protocol adjacency, LSP and routing-table outputs for the affected route.

Explanation

Correct Answer

C:

Because an adjacency can be operational while a specific family or prefix is not advertised, the best response is to distinguish IS-IS adjacency from address-family reachability advertisements. A reviewer can close the technical case only after confirming that the expected IPv6 prefix appears after family and policy review.

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 distinguish IS-IS adjacency from address-family reachability advertisements; verify: The expected IPv6 prefix appears after family and policy review.

B:

The alternative addresses a technician tries to diagnose an IS-IS area failure only by inspecting IP multicast Hellos, not the present root cause. Here the selected correction must reflect an adjacency can be operational while a specific family or prefix is not advertised. Test for: The expected IPv6 prefix appears after family and policy review.

D:

This option overlooks the decisive condition. Its supporting principle is structured protocol-layer evidence separates link health from routing convergence issues, while this scenario depends on an adjacency can be operational while a specific family or prefix is not advertised. Verify the correction with: The expected IPv6 prefix appears after family and policy review.

Question 423

Two equal-capacity IS-IS links receive unequal metrics and traffic takes an unexpected path. Which evidence would justify closing this troubleshooting case?

  1. Closeout evidence: The forwarding route follows the lowest intended metric path.
  2. Acceptance check: The internal peer has a valid route to the BGP next hop and installs the prefix.
  3. The test confirms that traffic and route lookup follow the documented optimized path.
  4. Expected observation: The planned area topology reaches distant prefixes through eligible Level 2 routing.

Explanation

Correct Answer

A:

The selected response implements the principle that iS-IS path selection is based on link-state topology and metrics. The engineer should compute total advertised IS-IS metrics instead of assuming capacity implies preference. Successful confirmation means: The forwarding route follows the lowest intended metric path.

Incorrect Answers

B:

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: 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.

C:

This response would target a different source scenario: A transit operator changes IS-IS metrics on one interface and later discovers a traffic-engineering imbalance. 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.

D:

Place the correct L1/L2 boundary and evaluate flooding scope is a relevant step for the separate scenario in which a provider uses a Level 1-only router to interconnect two independent IS-IS areas and expects unrestricted cross-area flooding. It does not directly fix this case. Instead compute total advertised IS-IS metrics instead of assuming capacity implies preference; verify: The forwarding route follows the lowest intended metric path.

Question 424

Two Junos routers on the same link have mismatched OSPF area identifiers and never form a neighbor relationship. Which technical explanation and controlled action address the symptom?

  1. Diagnosis: OSPF adjacency requires compatible area and interface parameters. Action: Align the area membership and verify OSPF interface settings on both sides.
  2. Explanation: A configured static route need not become usable forwarding state when its next hop cannot resolve. Repair: Verify recursive next-hop reachability before relying on the static route.
  3. Fault mechanism: OSPF normally prefers the least accumulated metric to a destination. Remediation: Revisit additive path cost and verify SPF outcomes across alternative links.
  4. Root issue: Layered neighbor troubleshooting should separate transport from OSPF parameter mismatches. Correction: Compare area, interface mode, timers, authentication and physical status on both endpoints.

Explanation

Correct Answer

A:

This is the model-intended best choice because oSPF adjacency requires compatible area and interface parameters. The targeted correction is to align the area membership and verify OSPF interface settings on both sides. Validate it by observing that the peers progress to the expected adjacency state and exchange LSAs.

Incorrect Answers

B:

This option overlooks the decisive condition. Its supporting principle is a configured static route need not become usable forwarding state when its next hop cannot resolve, while this scenario depends on oSPF adjacency requires compatible area and interface parameters. Verify the correction with: The peers progress to the expected adjacency state and exchange LSAs.

C:

OSPF normally prefers the least accumulated metric to a destination describes a neighboring protocol concern. In this case the controlling fact is oSPF adjacency requires compatible area and interface parameters. A correct remediation would align the area membership and verify OSPF interface settings on both sides and demonstrate: The peers progress to the expected adjacency state and exchange LSAs.

D:

The proposed principle concerns another network fault: Layered neighbor troubleshooting should separate transport from OSPF parameter mismatches. Here, oSPF adjacency requires compatible area and interface parameters. The most direct correction is to align the area membership and verify OSPF interface settings on both sides, confirmed by the peers progress to the expected adjacency state and exchange LSAs.

Question 425

A new peer sends more customer routes than expected and the team assumes BGP automatically filters unrelated prefixes. What should the operations engineer do first to address the stated fault?

  1. Corrective action: Review BGP next-hop reachability and explicit next-hop handling.
  2. Apply this control: Create explicit import policy and prefix limits aligned to customer contracts.
  3. Remediation: Inspect local preference, export/import inheritance and selected BGP path attributes.
  4. Recommended change: Review explicit or constraint-based path selection against current resource availability.

Explanation

Correct Answer

B:

The selected response implements the principle that bGP route acceptance must be constrained rather than inferred from neighbor identity. The engineer should create explicit import policy and prefix limits aligned to customer contracts. Successful confirmation means: Only approved customer prefixes enter the provider's active routing table.

Incorrect Answers

A:

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: Only approved customer prefixes enter the provider's active routing table. The relevant action is: Create explicit import policy and prefix limits aligned to customer contracts.

C:

The alternative addresses a policy change unexpectedly makes a backup transit provider carry most outbound traffic, 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.

D:

This answer would be more suitable when an RSVP tunnel unexpectedly crosses a low-capacity link after a traffic-engineering policy change, where the corrective action is to review explicit or constraint-based path selection against current resource availability. 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.

Question 426

A Q-in-Q customer service leaks traffic between two tenants after the outer service VLAN is reused incorrectly. Which corrective action and confirmation pair is most appropriate?

  1. Control: Check Q-in-Q input/output encapsulation and rewrite behavior at the handoff. Accepted result: A capture shows the expected outer service tag between provider edges.
  2. Action: Assign distinct service encapsulation and verify edge translation rules. Evidence: Cross-tenant traffic fails while each tenant's inner VLAN passes end to end.
  3. Repair: Apply suitable BPDU protection according to edge-port policy. Check: A controlled BPDU causes the expected protected-port response.
  4. Change: Document VLAN-aware versus flexible tagging and unit classification requirements. Test: Both test logical units classify tagged traffic into their intended bridge domains.

Explanation

Correct Answer

B:

This is the model-intended best choice because provider outer VLAN classification must preserve tenant isolation. The targeted correction is to assign distinct service encapsulation and verify edge translation rules. Validate it by observing that cross-tenant traffic fails while each tenant's inner VLAN passes end to end.

Incorrect Answers

A:

Provider bridging service tags must be applied and removed at the designed boundaries describes a neighboring protocol concern. In this case the controlling fact is provider outer VLAN classification must preserve tenant isolation. A correct remediation would assign distinct service encapsulation and verify edge translation rules and demonstrate: Cross-tenant traffic fails while each tenant's inner VLAN passes end to end.

C:

That result would be useful for a different failure, namely: An edge port connected to a user device unexpectedly receives BPDUs from an unauthorized switch. The current case specifically calls for: Assign distinct service encapsulation and verify edge translation rules. The required observed result is: Cross-tenant traffic fails while each tenant's inner VLAN passes end to end.

D:

This response would target a different source scenario: An Ethernet access design has multiple logical units using one physical port without specifying frame encapsulation. It cannot establish the current acceptance requirement, which is: Cross-tenant traffic fails while each tenant's inner VLAN passes end to end. The relevant action is: Assign distinct service encapsulation and verify edge translation rules.

Question 427

A provider applies an overly broad route import policy and customer prefixes enter an unintended tenant instance. What operational check demonstrates that the intended outcome occurred?

  1. Acceptance check: A documented multi-flow test matches the configured distribution policy.
  2. The test confirms that the session reaches Established only with the documented correct peer AS.
  3. Expected observation: Loss-of-specific-route testing produces the approved withdrawal or discard outcome.
  4. Verification result: A negative test proves the unrelated customer prefix is absent from the target table.

Explanation

Correct Answer

D:

The critical observation is: Route redistribution must be intentionally scoped to prevent cross-tenant leakage. Correct it by taking this action: Restrict routing-policy matches and validate the import and export boundary. Confirm the outcome with: A negative test proves the unrelated customer prefix is absent from the target table.

Incorrect Answers

A:

The alternative addresses an equal-cost path test sends nearly all flows across one member while both links remain operational, not the present root cause. Here the selected correction must reflect route redistribution must be intentionally scoped to prevent cross-tenant leakage. Test for: A negative test proves the unrelated customer prefix is absent from the target table.

B:

This answer would be more suitable when a remote BGP neighbor uses a different AS number than configured and the session fails during OPEN negotiation, where the corrective action is to confirm the configured local and peer AS values with the authoritative design. The failure here is different: Route redistribution must be intentionally scoped to prevent cross-tenant leakage. Required validation: A negative test proves the unrelated customer prefix is absent from the target table.

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 route redistribution must be intentionally scoped to prevent cross-tenant leakage. Verify the correction with: A negative test proves the unrelated customer prefix is absent from the target table.

Question 428

A penultimate router pops a transport label and the egress receives native IP even though the engineer expected a visible final outer label. What should the operations engineer do first to address the stated fault?

  1. Remediation: Recognize penultimate-hop popping as an allowed LSP forwarding behavior.
  2. Recommended change: Compare withdrawal and blackhole behavior under a lab failure before changing the safety route.
  3. Next step: Review LDP dependence on reachability and routing of the transport endpoints.
  4. Corrective action: Review explicit or constraint-based path selection against current resource availability.

Explanation

Correct Answer

A:

This option addresses the stated case rather than another networking issue. Principle: An upstream LSR can remove a label before the egress in an appropriate PHP design. Remedy: Recognize penultimate-hop popping as an allowed LSP forwarding behavior. Proof: A packet trace verifies the intended stack at the penultimate and egress hops.

Incorrect Answers

B:

This response would target a different source scenario: An engineer deletes an aggregate discard without first checking whether it prevents a transient routing loop. It cannot establish the current acceptance requirement, which is: A packet trace verifies the intended stack at the penultimate and egress hops. The relevant action is: Recognize penultimate-hop popping as an allowed LSP forwarding behavior.

C:

Review LDP dependence on reachability and routing of the transport endpoints is a relevant step for the separate scenario in which an LDP-signaled LSP fails when the IGP route to the remote loopback disappears. It does not directly fix this case. Instead recognize penultimate-hop popping as an allowed LSP forwarding behavior; verify: A packet trace verifies the intended stack at the penultimate and egress hops.

D:

The alternative addresses an RSVP tunnel unexpectedly crosses a low-capacity link after a traffic-engineering policy change, not the present root cause. Here the selected correction must reflect an upstream LSR can remove a label before the egress in an appropriate PHP design. Test for: A packet trace verifies the intended stack at the penultimate and egress hops.

Question 429

One customer’s new prefixes are advertised to a second unrelated customer via a shared export group. What remediation is most directly applicable?

  1. Apply this control: Restore standard AS-path checks and review any justified exception with design authority.
  2. Remediation: Verify negotiated address families and family-specific routing tables.
  3. Recommended change: Split export policy by authorized customer scope and verify negative advertisements.
  4. Next step: Verify compatible network and Hello parameters including mask where applicable.

Explanation

Correct Answer

C:

Underlying cause: BGP group-level export policies must preserve customer routing isolation. Corrective action: split export policy by authorized customer scope and verify negative advertisements. Verify the outcome: The unauthorized customer receives no leaked prefixes in a route advertisement check.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is disabling loop prevention can introduce persistent interdomain routing loops, while this scenario depends on bGP group-level export policies must preserve customer routing isolation. Verify the correction with: The unauthorized customer receives no leaked prefixes in a route advertisement check.

B:

BGP transport connectivity does not guarantee every address family is negotiated and active describes a neighboring protocol concern. In this case the controlling fact is bGP group-level export policies must preserve customer routing isolation. A correct remediation would split export policy by authorized customer scope and verify negative advertisements and demonstrate: The unauthorized customer receives no leaked prefixes in a route advertisement check.

D:

That result would be useful for a different failure, namely: A router sends OSPF Hello packets but remains stuck because the subnet mask differs across neighbors on a broadcast link. The current case specifically calls for: Split export policy by authorized customer scope and verify negative advertisements. The required observed result is: The unauthorized customer receives no leaked prefixes in a route advertisement check.

Question 430

An operator accepts a source-address block as an ordinary next-hop network even though the address is classified as martian. Which root-cause explanation and corrective action fit the case?

  1. Cause: Address validity and martian filtering affect which route sources are considered acceptable. Response: Review martian-address treatment and justify any carefully scoped exception.
  2. Diagnosis: A configured static route need not become usable forwarding state when its next hop cannot resolve. Action: Verify recursive next-hop reachability before relying on the static route.
  3. Explanation: Operational route troubleshooting starts with active state and resolution evidence. Repair: Inspect the configuration, active route state and next-hop reachability before changing preference.
  4. Fault mechanism: Disabling loop prevention can introduce persistent interdomain routing loops. Remediation: Restore standard AS-path checks and review any justified exception with design authority.

Explanation

Correct Answer

A:

Correct diagnosis: Address validity and martian filtering affect which route sources are considered acceptable. The appropriate action is: Review martian-address treatment and justify any carefully scoped exception. The follow-up evidence required is: The rejected address remains excluded or a documented narrowly scoped exception is applied.

Incorrect Answers

B:

The alternative addresses a provider router has a static route for a customer prefix but its configured next hop is not reachable through any active route, not the present root cause. Here the selected correction must reflect address validity and martian filtering affect which route sources are considered acceptable. Test for: The rejected address remains excluded or a documented narrowly scoped exception is applied.

C:

This answer would be more suitable when after a maintenance window a configured customer static prefix is missing from active routes despite no syntax errors, where the corrective action is to inspect the configuration, active route state and next-hop reachability before changing preference. The failure here is different: Address validity and martian filtering affect which route sources are considered acceptable. Required validation: The rejected address remains excluded or a documented narrowly scoped exception is applied.

D:

This option overlooks the decisive condition. Its supporting principle is disabling loop prevention can introduce persistent interdomain routing loops, while this scenario depends on address validity and martian filtering affect which route sources are considered acceptable. Verify the correction with: The rejected address remains excluded or a documented narrowly scoped exception is applied.

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