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 4

Question 30

A BGP prefix remains rejected after an intended route filter update because an earlier term rejects it. What diagnosis and engineering response are most appropriate?

  1. Fault mechanism: Policy evaluation order can short-circuit later intended acceptance. Remediation: Evaluate policy terms in effective order and test matching routes.
  2. Root issue: Unresolvable BGP next hops can make received routes unusable. Correction: Restore appropriate IGP next-hop reachability or approved next-hop-self behavior.
  3. Cause: BGP message types have separate roles in session formation and reachability exchange. Response: Distinguish session negotiation from UPDATE message route advertisements.
  4. Diagnosis: OSPF broadcast topology reduces unnecessary full adjacency mesh formation. Action: Check the expected DR/BDR versus DROther neighbor-state relationships.

Explanation

Correct Answer

A:

Correct diagnosis: Policy evaluation order can short-circuit later intended acceptance. The appropriate action is: Evaluate policy terms in effective order and test matching routes. The follow-up evidence required is: The approved route matches an accepting term and the denied route remains denied.

Incorrect Answers

B:

The alternative addresses an iBGP route is hidden because the next hop learned from an edge router is unreachable inside the backbone, not the present root cause. Here the selected correction must reflect policy evaluation order can short-circuit later intended acceptance. Test for: The approved route matches an accepting term and the denied route remains denied.

C:

This answer would be more suitable when a provider engineer treats a BGP OPEN message as if it already advertises reachable customer prefixes, where the corrective action is to distinguish session negotiation from UPDATE message route advertisements. The failure here is different: Policy evaluation order can short-circuit later intended acceptance. Required validation: The approved route matches an accepting term and the denied route remains denied.

D:

This option overlooks the decisive condition. Its supporting principle is oSPF broadcast topology reduces unnecessary full adjacency mesh formation, while this scenario depends on policy evaluation order can short-circuit later intended acceptance. Verify the correction with: The approved route matches an accepting term and the denied route remains denied.

Question 31

A new Junos edge router can ping IPv4 customers but cannot route IPv6 traffic to the same site. Which post-change observation most strongly confirms the correction?

  1. Closeout evidence: The route policy and active table agree with the approved advertised prefixes.
  2. Acceptance check: A tunnel packet is carried over IPv4 and decapsulated to IPv6 at the endpoint.
  3. The test confirms that the remote PE learns and uses the intended IPv6 prefix.
  4. Expected observation: The intended IPv6 neighbor and destination routes appear and traffic succeeds.

Explanation

Correct Answer

D:

Underlying cause: IPv4 operational success does not prove IPv6 forwarding configuration. Corrective action: validate IPv6 addressing, neighbor discovery and inet6 routing separately. Verify the outcome: The intended IPv6 neighbor and destination routes appear and traffic succeeds.

Incorrect Answers

A:

The proposed principle concerns another network fault: A learned LSP does not ensure a destination is selected into the active routing table. Here, iPv4 operational success does not prove IPv6 forwarding configuration. The most direct correction is to validate IPv6 addressing, neighbor discovery and inet6 routing separately, confirmed by the intended IPv6 neighbor and destination routes appear and traffic succeeds.

B:

That result would be useful for a different failure, namely: A service provider tunnels IPv6 over an IPv4 core but expects native IPv6 forwarding at every transit hop. The current case specifically calls for: Validate IPv6 addressing, neighbor discovery and inet6 routing separately. The required observed result is: The intended IPv6 neighbor and destination routes appear and traffic succeeds.

C:

This response would target a different source scenario: An IS-IS change carries IPv4 traffic but a new IPv6 prefix is missing from a remote PE. It cannot establish the current acceptance requirement, which is: The intended IPv6 neighbor and destination routes appear and traffic succeeds. The relevant action is: Validate IPv6 addressing, neighbor discovery and inet6 routing separately.

Question 32

A carrier attachment must not allow a customer switch to become the provider's root bridge. What assessment accurately links the fault to its correction?

  1. Diagnosis: Root protection can prevent undesired superior-root claims from changing root placement. Action: Review root protection at the provider-facing boundary.
  2. Explanation: Traditional spanning-tree root election favors the lowest bridge ID. Repair: Review root bridge priority and MAC-based bridge identifier comparison.
  3. Fault mechanism: Nonstop bridging protects relevant Layer 2 control-protocol state during switchover. Remediation: Evaluate nonstop bridging together with the supported Routing Engine redundancy design.
  4. Root issue: STP instability can be secondary to physical link churn. Correction: Inspect interface faults and control-plane events before changing STP timers.

Explanation

Correct Answer

A:

This is the model-intended best choice because root protection can prevent undesired superior-root claims from changing root placement. The targeted correction is to review root protection at the provider-facing boundary. Validate it by observing that a superior BPDU test does not move the approved provider root.

Incorrect Answers

B:

This option overlooks the decisive condition. Its supporting principle is traditional spanning-tree root election favors the lowest bridge ID, while this scenario depends on root protection can prevent undesired superior-root claims from changing root placement. Verify the correction with: A superior BPDU test does not move the approved provider root.

C:

Nonstop bridging protects relevant Layer 2 control-protocol state during switchover describes a neighboring protocol concern. In this case the controlling fact is root protection can prevent undesired superior-root claims from changing root placement. A correct remediation would review root protection at the provider-facing boundary and demonstrate: A superior BPDU test does not move the approved provider root.

D:

The proposed principle concerns another network fault: STP instability can be secondary to physical link churn. Here, root protection can prevent undesired superior-root claims from changing root placement. The most direct correction is to review root protection at the provider-facing boundary, confirmed by a superior BPDU test does not move the approved provider root.

Question 33

A provider engineer treats a BGP OPEN message as if it already advertises reachable customer prefixes. What should the operations engineer do first to address the stated fault?

  1. Corrective action: Review router priorities and the nonpreemptive properties of DR elections.
  2. Apply this control: Evaluate route reflection with defined cluster and client boundaries.
  3. Remediation: Distinguish session negotiation from UPDATE message route advertisements.
  4. Recommended change: Split export policy by authorized customer scope and verify negative advertisements.

Explanation

Correct Answer

C:

The critical observation is: BGP message types have separate roles in session formation and reachability exchange. Correct it by taking this action: Distinguish session negotiation from UPDATE message route advertisements. Confirm the outcome with: A packet trace shows OPEN and KEEPALIVE before accepted UPDATE information.

Incorrect Answers

A:

This response would target a different source scenario: A broadcast OSPF segment experiences repeated DR elections after interface priority changes. It cannot establish the current acceptance requirement, which is: A packet trace shows OPEN and KEEPALIVE before accepted UPDATE information. The relevant action is: Distinguish session negotiation from UPDATE message route advertisements.

B:

Evaluate route reflection with defined cluster and client boundaries is a relevant step for the separate scenario in which a small full-mesh iBGP design becomes difficult to maintain as dozens of PEs are added. It does not directly fix this case. Instead distinguish session negotiation from UPDATE message route advertisements; verify: A packet trace shows OPEN and KEEPALIVE before accepted UPDATE information.

D:

This answer would be more suitable when one customer’s new prefixes are advertised to a second unrelated customer via a shared export group, where the corrective action is to split export policy by authorized customer scope and verify negative advertisements. The failure here is different: BGP message types have separate roles in session formation and reachability exchange. Required validation: A packet trace shows OPEN and KEEPALIVE before accepted UPDATE information.

Question 34

An IS-IS change carries IPv4 traffic but a new IPv6 prefix is missing from a remote PE. Which technical explanation and controlled action address the symptom?

  1. Root issue: Underlying endpoint reachability does not guarantee permitted encapsulated payloads. Correction: Verify tunnel protocol allowance, endpoint encapsulation and effective MTU.
  2. Cause: IS-IS Level 1 adjacency formation depends on common area context. Response: Verify compatible area membership or use the designed Level 2 boundary.
  3. Diagnosis: Dual-stack IS-IS troubleshooting requires family-specific advertisement evidence. Action: Inspect IPv6 reachability TLVs, family configuration and active inet6 route state.
  4. Explanation: IS-IS adjacency and IPv6 prefix exchange are separate operational concerns. Repair: Enable and verify the intended IPv6 address-family reachability advertisements.

Explanation

Correct Answer

C:

Correct diagnosis: Dual-stack IS-IS troubleshooting requires family-specific advertisement evidence. The appropriate action is: Inspect IPv6 reachability TLVs, family configuration and active inet6 route state. The follow-up evidence required is: The remote PE learns and uses the intended IPv6 prefix.

Incorrect Answers

A:

Underlying endpoint reachability does not guarantee permitted encapsulated payloads describes a neighboring protocol concern. In this case the controlling fact is dual-stack IS-IS troubleshooting requires family-specific advertisement evidence. A correct remediation would inspect IPv6 reachability TLVs, family configuration and active inet6 route state and demonstrate: The remote PE learns and uses the intended IPv6 prefix.

B:

The proposed principle concerns another network fault: IS-IS Level 1 adjacency formation depends on common area context. Here, dual-stack IS-IS troubleshooting requires family-specific advertisement evidence. The most direct correction is to inspect IPv6 reachability TLVs, family configuration and active inet6 route state, confirmed by the remote PE learns and uses the intended IPv6 prefix.

D:

This response would target a different source scenario: An IS-IS backbone forms an adjacency but omits IPv6 reachability when the family is not enabled. It cannot establish the current acceptance requirement, which is: The remote PE learns and uses the intended IPv6 prefix. The relevant action is: Inspect IPv6 reachability TLVs, family configuration and active inet6 route state.

Question 35

A provider creates a customer routing instance but assumes its routes will automatically be present in the master inet.0 table. Which next action best resolves this observed routing or switching failure?

  1. Recommended change: Narrow filter match terms and validate filter-based forwarding for both matched and unmatched probes.
  2. Next step: Define the intended route-leaking boundary between the customer's instance and the master routing table.
  3. Corrective action: Evaluate policy terms in effective order and test matching routes.
  4. Apply this control: Distinguish aggregate reachability from specific-route forwarding and test loss of component routes.

Explanation

Correct Answer

B:

Underlying cause: Routing instances isolate routing tables unless explicit import or export mechanisms connect them. Corrective action: define the intended route-leaking boundary between the customer's instance and the master routing table. Verify the outcome: Each customer route is visible only in the tables approved by the design.

Incorrect Answers

A:

The alternative addresses an input firewall filter diverts all transit traffic to a management routing instance by mistake, not the present root cause. Here the selected correction must reflect routing instances isolate routing tables unless explicit import or export mechanisms connect them. Test for: Each customer route is visible only in the tables approved by the design.

C:

This option overlooks the decisive condition. Its supporting principle is policy evaluation order can short-circuit later intended acceptance, while this scenario depends on routing instances isolate routing tables unless explicit import or export mechanisms connect them. Verify the correction with: Each customer route is visible only in the tables approved by the design.

D:

Aggregation can hide individual component failures if advertisement policy is not controlled describes a neighboring protocol concern. In this case the controlling fact is routing instances isolate routing tables unless explicit import or export mechanisms connect them. A correct remediation would define the intended route-leaking boundary between the customer's instance and the master routing table and demonstrate: Each customer route is visible only in the tables approved by the design.

Question 36

A BFD session flaps during Routing Engine switchover after aggressive timer tuning. What action-and-test pairing directly resolves the case?

  1. Change: Differentiate forwarding continuity under GRES from routing-protocol state preservation. Test: A switchover test assesses both packet forwarding and routing neighbor continuity.
  2. Implement: Review router priorities and the nonpreemptive properties of DR elections. Verify: The elected DR and BDR align with the tested election conditions.
  3. Control: Inspect whether nonstop bridging is available and configured for the relevant L2 control plane. Accepted result: A controlled switchover retains the expected bridge state and host connectivity.
  4. Action: Review session type, supported distributed behavior and switchover-appropriate intervals. Evidence: A tested switchover maintains the required liveness behavior without false failure.

Explanation

Correct Answer

D:

Correct diagnosis: BFD HA behavior depends on platform processing placement and timer tolerances. The appropriate action is: Review session type, supported distributed behavior and switchover-appropriate intervals. The follow-up evidence required is: A tested switchover maintains the required liveness behavior without false failure.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A dual-Routing-Engine chassis uses GRES but an engineer assumes routing protocol control state is preserved without any other feature. The current case specifically calls for: Review session type, supported distributed behavior and switchover-appropriate intervals. The required observed result is: A tested switchover maintains the required liveness behavior without false failure.

B:

This response would target a different source scenario: A broadcast OSPF segment experiences repeated DR elections after interface priority changes. It cannot establish the current acceptance requirement, which is: A tested switchover maintains the required liveness behavior without false failure. The relevant action is: Review session type, supported distributed behavior and switchover-appropriate intervals.

C:

Inspect whether nonstop bridging is available and configured for the relevant L2 control plane is a relevant step for the separate scenario in which layer 2 forwarding is disrupted during Routing Engine replacement even though high availability was enabled for routing. It does not directly fix this case. Instead review session type, supported distributed behavior and switchover-appropriate intervals; verify: A tested switchover maintains the required liveness behavior without false failure.

Question 37

A router-on-a-stick replacement with IRB stops reachability between a bridge domain and an L3 subnet. What implementation step and validation result should be selected?

  1. Repair: Align untagged or native VLAN behavior with explicit port configuration. Check: The same controlled untagged frame maps to the intended VLAN on both sides.
  2. Change: Verify VLAN-to-IRB interface binding, addresses and active route entries. Test: A test host ARPs or discovers its gateway and routes to the intended subnet.
  3. Implement: Inspect VLAN membership and tagging on both ends and verify per-VLAN MAC learning. Verify: Separate tagged tests pass in both permitted VLANs.
  4. Control: Inspect interface faults and control-plane events before changing STP timers. Accepted result: After fiber repair the port converges and remains in a stable role.

Explanation

Correct Answer

B:

The case turns on the distinction that iRB depends on both L2 membership and a valid L3 gateway configuration. Apply this concrete engineering step: Verify VLAN-to-IRB interface binding, addresses and active route entries. An acceptable verification outcome is: A test host ARPs or discovers its gateway and routes to the intended subnet.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is untagged frame classification is local to the receiving interface, while this scenario depends on iRB depends on both L2 membership and a valid L3 gateway configuration. Verify the correction with: A test host ARPs or discovers its gateway and routes to the intended subnet.

C:

The proposed principle concerns another network fault: MAC table visibility alone does not prove trunk authorization for every VLAN. Here, iRB depends on both L2 membership and a valid L3 gateway configuration. The most direct correction is to verify VLAN-to-IRB interface binding, addresses and active route entries, confirmed by a test host ARPs or discovers its gateway and routes to the intended subnet.

D:

That result would be useful for a different failure, namely: An RSTP uplink continues to flap between discarding and forwarding after an unstable fiber replacement. The current case specifically calls for: Verify VLAN-to-IRB interface binding, addresses and active route entries. The required observed result is: A test host ARPs or discovers its gateway and routes to the intended subnet.

Question 38

A trunk permits VLAN 110 but excludes VLAN 120 while users on VLAN 120 report isolation from the remote switch. What action-and-test pairing directly resolves the case?

  1. Action: Review allowed VLAN membership on both trunk endpoints. Evidence: Both permitted VLAN test flows cross while an explicitly denied VLAN stays blocked.
  2. Repair: Inspect whether nonstop bridging is available and configured for the relevant L2 control plane. Check: A controlled switchover retains the expected bridge state and host connectivity.
  3. Change: Clarify C-tag preservation and S-tag encapsulation in a Q-in-Q design. Test: An ingress-to-egress capture confirms the intended stacked tagging.
  4. Implement: Distinguish access port traffic from trunk tagging behavior. Verify: An end-host packet enters the correct VLAN without requiring endpoint tagging.

Explanation

Correct Answer

A:

Correct diagnosis: A trunk carries only its configured authorized VLANs. The appropriate action is: Review allowed VLAN membership on both trunk endpoints. The follow-up evidence required is: Both permitted VLAN test flows cross while an explicitly denied VLAN stays blocked.

Incorrect Answers

B:

The alternative addresses layer 2 forwarding is disrupted during Routing Engine replacement even though high availability was enabled for routing, not the present root cause. Here the selected correction must reflect a trunk carries only its configured authorized VLANs. Test for: Both permitted VLAN test flows cross while an explicitly denied VLAN stays blocked.

C:

This answer would be more suitable when an operator plans provider bridging but assumes the customer's C-tag is removed from every frame, where the corrective action is to clarify C-tag preservation and S-tag encapsulation in a Q-in-Q design. The failure here is different: A trunk carries only its configured authorized VLANs. Required validation: Both permitted VLAN test flows cross while an explicitly denied VLAN stays blocked.

D:

This option overlooks the decisive condition. Its supporting principle is port mode determines which customer frames are tagged or untagged at the boundary, while this scenario depends on a trunk carries only its configured authorized VLANs. Verify the correction with: Both permitted VLAN test flows cross while an explicitly denied VLAN stays blocked.

Question 39

One branch reaches a PE over IP but fails when the same traffic is forwarded across the MPLS core. What diagnosis and engineering response are most appropriate?

  1. Root issue: Successful ordinary IP forwarding does not isolate MPLS packet forwarding faults. Correction: Compare ingress label imposition with transit LFIB and egress disposition.
  2. Cause: Communities are policy signaling metadata and not the packet-forwarding next hop themselves. Response: Differentiate community tags from reachability and forwarding attributes.
  3. Diagnosis: Different segment types express different routing or link steering semantics. Action: Distinguish prefix-based segment reachability from adjacency-specific forwarding instructions.
  4. Explanation: RSVP LSP setup can fail resource or path constraints even with valid IP reachability. Repair: Review reservation constraints and available resources rather than resetting all label sessions.

Explanation

Correct Answer

A:

The selected response implements the principle that successful ordinary IP forwarding does not isolate MPLS packet forwarding faults. The engineer should compare ingress label imposition with transit LFIB and egress disposition. Successful confirmation means: A hop-by-hop labeled test locates and corrects the failing label action.

Incorrect Answers

B:

That result would be useful for a different failure, namely: An engineer treats a BGP community value as a standalone forwarding next hop. The current case specifically calls for: Compare ingress label imposition with transit LFIB and egress disposition. The required observed result is: A hop-by-hop labeled test locates and corrects the failing label action.

C:

This response would target a different source scenario: A segment routing node uses a prefix segment but the operator treats it as a local adjacency segment. It cannot establish the current acceptance requirement, which is: A hop-by-hop labeled test locates and corrects the failing label action. The relevant action is: Compare ingress label imposition with transit LFIB and egress disposition.

D:

Review reservation constraints and available resources rather than resetting all label sessions is a relevant step for the separate scenario in which an RSVP-signaled LSP enters a failed state after a link bandwidth change. It does not directly fix this case. Instead compare ingress label imposition with transit LFIB and egress disposition; verify: A hop-by-hop labeled test locates and corrects the failing label action.

Question 40

An engineer sees that RSVP signaling succeeded and assumes all reserved bandwidth remains available for other tunnels. Which protocol behavior most directly determines the correct diagnosis?

  1. The key distinction is: BGP MED influence is conditional on the receiving network's path selection rules.
  2. Protocol behavior: A stale label binding cannot compensate for unusable transport forwarding.
  3. Underlying principle: RSVP resource reservation may affect which additional constrained LSPs can be admitted.
  4. Root design issue: A usable IP path need not supply a suitable MPLS LSP or labeled transport path.

Explanation

Correct Answer

C:

This option addresses the stated case rather than another networking issue. Principle: RSVP resource reservation may affect which additional constrained LSPs can be admitted. Remedy: Distinguish signaling reservations from physical link speed and admission control. Proof: A controlled setup respects the approved link reservation policy.

Incorrect Answers

A:

This answer would be more suitable when an inbound MED is assumed to control outgoing traffic even though the receiving network has its own path-selection policies, where the corrective action is to distinguish an advertised inbound hint from neighboring-AS route policy decisions. The failure here is different: RSVP resource reservation may affect which additional constrained LSPs can be admitted. Required validation: A controlled setup respects the approved link reservation policy.

B:

This option overlooks the decisive condition. Its supporting principle is a stale label binding cannot compensate for unusable transport forwarding, while this scenario depends on rSVP resource reservation may affect which additional constrained LSPs can be admitted. Verify the correction with: A controlled setup respects the approved link reservation policy.

D:

The proposed principle concerns another network fault: A usable IP path need not supply a suitable MPLS LSP or labeled transport path. Here, rSVP resource reservation may affect which additional constrained LSPs can be admitted. The most direct correction is to distinguish signaling reservations from physical link speed and admission control, confirmed by a controlled setup respects the approved link reservation policy.

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