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 39

Question 380

An engineer wants to filter routing information at an IS-IS boundary but applies a policy to the wrong routing context. What is the most defensible network engineering correction?

  1. Remediation: Verify compatible area membership or use the designed Level 2 boundary.
  2. Recommended change: Compare NET area addresses and intended L1 or L2 adjacency mode.
  3. Next step: Check DR and BDR roles and expected 2-Way peers before changing a healthy segment.
  4. Corrective action: Apply and verify supported route policy at the intended routing import or export boundary.

Explanation

Correct Answer

D:

Correct diagnosis: Policy placement determines which prefixes influence a routing table or advertisement. The appropriate action is: Apply and verify supported route policy at the intended routing import or export boundary. The follow-up evidence required is: The allowed prefixes are present and denied test prefixes are absent.

Incorrect Answers

A:

That result would be useful for a different failure, namely: An IS-IS adjacency between two provider routers fails because their NET addresses encode incompatible area identifiers for a Level 1 relationship. The current case specifically calls for: Apply and verify supported route policy at the intended routing import or export boundary. The required observed result is: The allowed prefixes are present and denied test prefixes are absent.

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: The allowed prefixes are present and denied test prefixes are absent. The relevant action is: Apply and verify supported route policy at the intended routing import or export boundary.

C:

Check DR and BDR roles and expected 2-Way peers before changing a healthy segment is a relevant step for the separate scenario in which a broadcast core VLAN has only one Full adjacency and the engineer wants to reset all routers immediately. It does not directly fix this case. Instead apply and verify supported route policy at the intended routing import or export boundary; verify: The allowed prefixes are present and denied test prefixes are absent.

Question 381

A route policy makes a transport prefix unavailable to the MPLS forwarding context while preserving customer IP routes. Which change best corrects the failure without losing the intended design?

  1. Apply this control: Separate RSVP-signaled LSP functions from LDP label distribution.
  2. Remediation: Tighten customer import route filtering and test permitted prefix lengths.
  3. Recommended change: Restore the required transport route and inspect label-signaling and next-hop state.
  4. Next step: Verify whether PHP or explicit-null behavior is configured and intended.

Explanation

Correct Answer

C:

Underlying cause: MPLS relies on selected underlay transport reachability and policy eligibility. Corrective action: restore the required transport route and inspect label-signaling and next-hop state. Verify the outcome: The transport endpoint again resolves and a labeled probe succeeds.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is rSVP-TE can signal explicit or constrained paths while ordinary LDP follows routing reachability, while this scenario depends on mPLS relies on selected underlay transport reachability and policy eligibility. Verify the correction with: The transport endpoint again resolves and a labeled probe succeeds.

B:

BGP edge hygiene protects the routing domain from unauthorized reachability describes a neighboring protocol concern. In this case the controlling fact is mPLS relies on selected underlay transport reachability and policy eligibility. A correct remediation would restore the required transport route and inspect label-signaling and next-hop state and demonstrate: The transport endpoint again resolves and a labeled probe succeeds.

D:

That result would be useful for a different failure, namely: An MPLS packet trace shows the outer label is removed earlier than expected and the engineer calls it a malformed packet. The current case specifically calls for: Restore the required transport route and inspect label-signaling and next-hop state. The required observed result is: The transport endpoint again resolves and a labeled probe succeeds.

Question 382

Two BGP paths have different local preferences and a technician expects the shorter AS path always to win. What action-and-test pairing directly resolves the case?

  1. Action: Review BGP next-hop reachability and explicit next-hop handling. Evidence: The internal peer has a valid route to the BGP next hop and installs the prefix.
  2. Repair: Compare MED use with actual prior BGP decision attributes and neighbor policy. Check: A captured received-path comparison explains which attribute selected the route.
  3. Change: Evaluate routing-policy local preference before later BGP path-selection attributes. Test: The intended local preference policy selects the approved egress.
  4. Implement: Explain label swap behavior across transit label switching routers. Verify: A hop trace shows the intended push and swap operations along the path.

Explanation

Correct Answer

C:

Because bGP best-path selection considers higher-priority decision attributes before AS-path length, the best response is to evaluate routing-policy local preference before later BGP path-selection attributes. A reviewer can close the technical case only after confirming that the intended local preference policy selects the approved egress.

Incorrect Answers

A:

Review BGP next-hop reachability and explicit next-hop handling is a relevant step for the separate scenario in which a provider's iBGP peer receives a route but cannot resolve the external next hop in its own IGP. It does not directly fix this case. Instead evaluate routing-policy local preference before later BGP path-selection attributes; verify: The intended local preference policy selects the approved egress.

B:

The alternative addresses an operator changes MED and sees no route change because the target AS prioritizes other attributes, not the present root cause. Here the selected correction must reflect bGP best-path selection considers higher-priority decision attributes before AS-path length. Test for: The intended local preference policy selects the approved egress.

D:

This option overlooks the decisive condition. Its supporting principle is labels have locally significant forwarding meaning on each LSP segment, while this scenario depends on bGP best-path selection considers higher-priority decision attributes before AS-path length. Verify the correction with: The intended local preference policy selects the approved egress.

Question 383

A service provider adds a second VLAN tag to customer frames but the downstream switch treats it as an ordinary single tag. What is the primary routing or switching concept illustrated?

  1. Protocol behavior: Stacked VLAN services require compatible tagging interpretation at both ends.
  2. Underlying principle: VRRP provides a master and backup mechanism for a shared virtual default gateway.
  3. Root design issue: IRB depends on both L2 membership and a valid L3 gateway configuration.
  4. The governing rule is: Customer-facing encapsulation must match the traffic format at ingress.

Explanation

Correct Answer

A:

The selected response implements the principle that stacked VLAN services require compatible tagging interpretation at both ends. The engineer should validate outer tag encapsulation and EtherType expectations across the handoff. Successful confirmation means: A packet capture shows the intended outer and inner VLAN tags end to end.

Incorrect Answers

B:

That result would be useful for a different failure, namely: Two edge routers advertise one gateway service and an engineer expects both to be virtual master without a redundancy plan. The current case specifically calls for: Validate outer tag encapsulation and EtherType expectations across the handoff. The required observed result is: A packet capture shows the intended outer and inner VLAN tags end to end.

C:

This response would target a different source scenario: A router-on-a-stick replacement with IRB stops reachability between a bridge domain and an L3 subnet. It cannot establish the current acceptance requirement, which is: A packet capture shows the intended outer and inner VLAN tags end to end. The relevant action is: Validate outer tag encapsulation and EtherType expectations across the handoff.

D:

Set appropriate port mode and tag handling at the service edge is a relevant step for the separate scenario in which an Ethernet provider transit receives an untagged subscriber frame on a service meant for tagged traffic. It does not directly fix this case. Instead validate outer tag encapsulation and EtherType expectations across the handoff; verify: A packet capture shows the intended outer and inner VLAN tags end to end.

Question 384

A customer requests VLAN 4096 as an ordinary 802.1Q customer VLAN without checking valid tag IDs. Which change best corrects the failure without losing the intended design?

  1. Recommended change: Deploy or validate an integrated routing and bridging L3 interface and gateway.
  2. Next step: Verify the BPDU protection event and remove the unauthorized bridge rather than blindly disabling safeguards.
  3. Corrective action: Validate the usable VLAN-ID range and reserved tag values.
  4. Apply this control: Separate customer bridge domains and validate virtual-switch membership.

Explanation

Correct Answer

C:

This option addresses the stated case rather than another networking issue. Principle: 802.1Q VLAN identifiers have reserved values and platform constraints. Remedy: Validate the usable VLAN-ID range and reserved tag values. Proof: The service uses a valid supported customer VLAN ID.

Incorrect Answers

A:

This answer would be more suitable when a VLAN provides local host connectivity but hosts cannot reach a different IP subnet through the bridge domain, where the corrective action is to deploy or validate an integrated routing and bridging L3 interface and gateway. The failure here is different: 802.1Q VLAN identifiers have reserved values and platform constraints. Required validation: The service uses a valid supported customer VLAN ID.

B:

This option overlooks the decisive condition. Its supporting principle is protective edge-port shutdown is evidence of BPDU policy enforcement, while this scenario depends on 802.1Q VLAN identifiers have reserved values and platform constraints. Verify the correction with: The service uses a valid supported customer VLAN ID.

D:

The proposed principle concerns another network fault: Layer 2 isolation depends on bridge-domain and logical switch boundaries. Here, 802.1Q VLAN identifiers have reserved values and platform constraints. The most direct correction is to validate the usable VLAN-ID range and reserved tag values, confirmed by the service uses a valid supported customer VLAN ID.

Question 385

A GRE design includes a virtual tunnel interface but omits routable IPv4 underlay access to the remote endpoint. What is the most defensible network engineering correction?

  1. Remediation: Review the IPv6 OSPFv3 address-family and interface adjacency model.
  2. Recommended change: Account for outer IP and GRE header overhead in the MTU design.
  3. Next step: Verify reachability between tunnel source and destination addresses.
  4. Corrective action: Restore underlay endpoint reachability and then validate the inner tunnel route.

Explanation

Correct Answer

C:

The critical observation is: Tunnel interfaces depend on a working underlay path between endpoints. Correct it by taking this action: Verify reachability between tunnel source and destination addresses. Confirm the outcome with: The remote tunnel endpoint is reachable through the intended underlay.

Incorrect Answers

A:

This response would target a different source scenario: An operator assumes OSPFv3 must form using the same interface and address settings as OSPFv2. It cannot establish the current acceptance requirement, which is: The remote tunnel endpoint is reachable through the intended underlay. The relevant action is: Verify reachability between tunnel source and destination addresses.

B:

Account for outer IP and GRE header overhead in the MTU design is a relevant step for the separate scenario in which an engineer expects a GRE tunnel to preserve the same maximum payload size as a native Ethernet path. It does not directly fix this case. Instead verify reachability between tunnel source and destination addresses; verify: The remote tunnel endpoint is reachable through the intended underlay.

D:

This answer would be more suitable when a GRE tunnel over an IPv4 core stops passing traffic immediately after an underlay route withdraws, where the corrective action is to restore underlay endpoint reachability and then validate the inner tunnel route. The failure here is different: Tunnel interfaces depend on a working underlay path between endpoints. Required validation: The remote tunnel endpoint is reachable through the intended underlay.

Question 386

A provider applies an overly broad route import policy and customer prefixes enter an unintended tenant instance. Which statement identifies the key design assumption that failed?

  1. Root design issue: An Established BGP session can exist with zero accepted routes or unusable next hops.
  2. The governing rule is: Aggregation can hide individual component failures if advertisement policy is not controlled.
  3. The key distinction is: Route redistribution must be intentionally scoped to prevent cross-tenant leakage.
  4. Protocol behavior: Operational route troubleshooting starts with active state and resolution evidence.

Explanation

Correct Answer

C:

Correct diagnosis: Route redistribution must be intentionally scoped to prevent cross-tenant leakage. The appropriate action is: Restrict routing-policy matches and validate the import and export boundary. The follow-up evidence required is: A negative test proves the unrelated customer prefix is absent from the target table.

Incorrect Answers

A:

An Established BGP session can exist with zero accepted routes or unusable next hops describes a neighboring protocol concern. In this case the controlling fact is route redistribution must be intentionally scoped to prevent cross-tenant leakage. A correct remediation would restrict routing-policy matches and validate the import and export boundary and demonstrate: A negative test proves the unrelated customer prefix is absent from the target table.

B:

The proposed principle concerns another network fault: Aggregation can hide individual component failures if advertisement policy is not controlled. Here, route redistribution must be intentionally scoped to prevent cross-tenant leakage. The most direct correction is to restrict routing-policy matches and validate the import and export boundary, confirmed by a negative test proves the unrelated customer prefix is absent from the target table.

D:

This response would target a different source scenario: After a maintenance window a configured customer static prefix is missing from active routes despite no syntax errors. It cannot establish the current acceptance requirement, which is: A negative test proves the unrelated customer prefix is absent from the target table. The relevant action is: Restrict routing-policy matches and validate the import and export boundary.

Question 387

An operator plans provider bridging but assumes the customer's C-tag is removed from every frame. A reviewer requires a remedy and concrete test evidence. Which pairing fits?

  1. Action: Clarify C-tag preservation and S-tag encapsulation in a Q-in-Q design. Evidence: An ingress-to-egress capture confirms the intended stacked tagging.
  2. Repair: Separate customer bridge domains and validate virtual-switch membership. Check: A cross-customer unknown-unicast probe remains isolated from the other tenant.
  3. Change: Deploy or validate an integrated routing and bridging L3 interface and gateway. Test: A test host reaches its gateway and an authorized remote subnet through IRB.
  4. Implement: Verify the BPDU protection event and remove the unauthorized bridge rather than blindly disabling safeguards. Verify: The approved endpoint reconnects without unexpected BPDUs and protection stays enabled.

Explanation

Correct Answer

A:

The case turns on the distinction that provider bridging can carry customer VLAN tags inside a provider service tag. Apply this concrete engineering step: Clarify C-tag preservation and S-tag encapsulation in a Q-in-Q design. An acceptable verification outcome is: An ingress-to-egress capture confirms the intended stacked tagging.

Incorrect Answers

B:

This answer would be more suitable when a customer bridge-domain spans two isolated customers due to reusing a virtual switch without tenant boundaries, where the corrective action is to separate customer bridge domains and validate virtual-switch membership. The failure here is different: Provider bridging can carry customer VLAN tags inside a provider service tag. Required validation: An ingress-to-egress capture confirms the intended stacked tagging.

C:

This option overlooks the decisive condition. Its supporting principle is layer 2 bridging does not by itself provide IP intersubnet routing, while this scenario depends on provider bridging can carry customer VLAN tags inside a provider service tag. Verify the correction with: An ingress-to-egress capture confirms the intended stacked tagging.

D:

Protective edge-port shutdown is evidence of BPDU policy enforcement describes a neighboring protocol concern. In this case the controlling fact is provider bridging can carry customer VLAN tags inside a provider service tag. A correct remediation would clarify C-tag preservation and S-tag encapsulation in a Q-in-Q design and demonstrate: An ingress-to-egress capture confirms the intended stacked tagging.

Question 388

An IS-IS LAN is unstable after a VLAN move and DIS changes accompany repeated adjacency loss. What observable result most directly verifies the intended configuration?

  1. The test confirms that the LAN's DIS and pseudonode LSP match the documented protocol state.
  2. Expected observation: The allowed prefixes are present and denied test prefixes are absent.
  3. Verification result: A stable neighbor and LAN LSP remain after link faults are corrected.
  4. Closeout evidence: The packet trace shows each message at its appropriate adjacency stage.

Explanation

Correct Answer

C:

This is the model-intended best choice because frequent topology churn can stem from physical and configuration issues rather than DIS alone. The targeted correction is to inspect link quality, interface settings and DIS state before forcing election behavior. Validate it by observing that a stable neighbor and LAN LSP remain after link faults are corrected.

Incorrect Answers

A:

That result would be useful for a different failure, namely: An IS-IS LAN elects a new DIS and the engineer assumes the result must preempt every existing elected node. The current case specifically calls for: Inspect link quality, interface settings and DIS state before forcing election behavior. The required observed result is: A stable neighbor and LAN LSP remain after link faults are corrected.

B:

This response would target a different source scenario: An engineer wants to filter routing information at an IS-IS boundary but applies a policy to the wrong routing context. It cannot establish the current acceptance requirement, which is: A stable neighbor and LAN LSP remain after link faults are corrected. The relevant action is: Inspect link quality, interface settings and DIS state before forcing election behavior.

D:

The alternative addresses a technician treats an OSPF Link State Request as the same message as a Hello packet, 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.

Question 389

A failover plan relies on one physical interface carrying several links and calls it a redundant LAG. Which root-cause explanation and corrective action fit the case?

  1. Fault mechanism: BFD HA behavior depends on platform processing placement and timer tolerances. Remediation: Review session type, supported distributed behavior and switchover-appropriate intervals.
  2. Root issue: VRRP provides a master and backup mechanism for a shared virtual default gateway. Correction: Review VRRP virtual router roles, priority and failover behavior.
  3. Cause: Link aggregation improves availability only when member links and topology provide meaningful redundancy. Response: Distinguish member-link redundancy from a single physical failure domain.
  4. Diagnosis: OSPF neighbor-state interpretation depends on multiaccess election roles. Action: Check DR and BDR roles and expected 2-Way peers before changing a healthy segment.

Explanation

Correct Answer

C:

Underlying cause: Link aggregation improves availability only when member links and topology provide meaningful redundancy. Corrective action: distinguish member-link redundancy from a single physical failure domain. Verify the outcome: A member link failure leaves traffic flowing through a remaining usable member.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is bFD HA behavior depends on platform processing placement and timer tolerances, while this scenario depends on link aggregation improves availability only when member links and topology provide meaningful redundancy. Verify the correction with: A member link failure leaves traffic flowing through a remaining usable member.

B:

VRRP provides a master and backup mechanism for a shared virtual default gateway describes a neighboring protocol concern. In this case the controlling fact is link aggregation improves availability only when member links and topology provide meaningful redundancy. A correct remediation would distinguish member-link redundancy from a single physical failure domain and demonstrate: A member link failure leaves traffic flowing through a remaining usable member.

D:

That result would be useful for a different failure, namely: A broadcast core VLAN has only one Full adjacency and the engineer wants to reset all routers immediately. The current case specifically calls for: Distinguish member-link redundancy from a single physical failure domain. The required observed result is: A member link failure leaves traffic flowing through a remaining usable member.

Question 390

A router in a nonbackbone area cannot reach a newly connected area through a topology that skips Area 0. What is the primary routing or switching concept illustrated?

  1. The governing rule is: Protocol timers need reliable packet delivery and should not mask an unstable link.
  2. The key distinction is: Multi-area OSPF design requires attention to backbone connectivity.
  3. Protocol behavior: OSPF uses distinct Hello, database description, link state request, update and acknowledgment functions.
  4. Underlying principle: Policy-based forwarding can select a routing table independently of the destination lookup in the ingress default table.

Explanation

Correct Answer

B:

This option addresses the stated case rather than another networking issue. Principle: Multi-area OSPF design requires attention to backbone connectivity. Remedy: Review hierarchical OSPF backbone attachment and area border placement. Proof: The planned ABR topology provides verified interarea reachability.

Incorrect Answers

A:

Compare Hello/Dead event logs with loss and interface errors before tuning timers is a relevant step for the separate scenario in which several routers report intermittent OSPF neighbor resets on a saturated transit circuit. It does not directly fix this case. Instead review hierarchical OSPF backbone attachment and area border placement; verify: The planned ABR topology provides verified interarea reachability.

C:

This answer would be more suitable when a technician treats an OSPF Link State Request as the same message as a Hello packet, where the corrective action is to differentiate neighbor discovery from database synchronization message types. The failure here is different: Multi-area OSPF design requires attention to backbone connectivity. Required validation: The planned ABR topology provides verified interarea reachability.

D:

This option overlooks the decisive condition. Its supporting principle is policy-based forwarding can select a routing table independently of the destination lookup in the ingress default table, 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.

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