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 20

Question 190

IPv4 IS-IS routing works but IPv6 routes do not appear on a dual-stack backbone. Which protocol behavior most directly determines the correct diagnosis?

  1. Root design issue: An adjacency can be operational while a specific family or prefix is not advertised.
  2. The governing rule is: A learned LSP does not ensure a destination is selected into the active routing table.
  3. The key distinction is: BGP selection is policy-driven and is not equivalent to IGP least-hop routing.
  4. Protocol behavior: IS-IS can convey multiple address families with appropriate support.

Explanation

Correct Answer

D:

This is the model-intended best choice because iS-IS can convey multiple address families with appropriate support. The targeted correction is to check the IPv6 family configuration and advertised reachability rather than rebuilding IPv4 adjacency. Validate it by observing that both address families display their expected prefixes through the same stable topology.

Incorrect Answers

A:

Distinguish IS-IS adjacency from address-family reachability advertisements is a relevant step for the separate scenario in which a core engineer sees that IPv6 reachability is absent despite IS-IS adjacency and concludes the adjacency itself is broken. It does not directly fix this case. Instead check the IPv6 family configuration and advertised reachability rather than rebuilding IPv4 adjacency; verify: Both address families display their expected prefixes through the same stable topology.

B:

The alternative addresses an IS-IS route disappears after a policy update while the LSP database still contains the topology, not the present root cause. Here the selected correction must reflect iS-IS can convey multiple address families with appropriate support. Test for: Both address families display their expected prefixes through the same stable topology.

C:

This answer would be more suitable when a router learns the same prefix from peers in distinct autonomous systems but the engineer compares only BGP hop count, where the corrective action is to trace the applicable BGP route-selection steps and local policies. The failure here is different: IS-IS can convey multiple address families with appropriate support. Required validation: Both address families display their expected prefixes through the same stable topology.

Question 191

A BFD session flaps during Routing Engine switchover after aggressive timer tuning. What remediation is most directly applicable?

  1. Corrective action: Inspect whether nonstop bridging is available and configured for the relevant L2 control plane.
  2. Apply this control: Evaluate BFD liveness detection with the associated routing protocol.
  3. Remediation: Compare the rapid proposal/agreement behavior with traditional timer-dependent transitions.
  4. Recommended change: Review session type, supported distributed behavior and switchover-appropriate intervals.

Explanation

Correct Answer

D:

Underlying cause: BFD HA behavior depends on platform processing placement and timer tolerances. Corrective action: review session type, supported distributed behavior and switchover-appropriate intervals. Verify the outcome: A tested switchover maintains the required liveness behavior without false failure.

Incorrect Answers

A:

The proposed principle concerns another network fault: Layer 3 routing HA does not automatically guarantee L2 bridge-control continuity. Here, bFD HA behavior depends on platform processing placement and timer tolerances. The most direct correction is to review session type, supported distributed behavior and switchover-appropriate intervals, confirmed by a tested switchover maintains the required liveness behavior without false failure.

B:

That result would be useful for a different failure, namely: A routing peer detects a dead neighbor too slowly for a real-time service even when the interface stays up. 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.

C:

This response would target a different source scenario: Two switches have compatible STP but an engineer expects RSTP to use identical convergence procedures as legacy STP. 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.

Question 192

An inbound MED is assumed to control outgoing traffic even though the receiving network has its own path-selection policies. Which test result would best confirm a successful fix?

  1. The test confirms that a controlled route lookup confirms the neighbor's actual selected entry path.
  2. Expected observation: The packet trace shows each message at its appropriate adjacency stage.
  3. Verification result: The intended inet6 family receives and selects the IPv6 prefix.
  4. Closeout evidence: An unwanted looped route is rejected in a lab before production change.

Explanation

Correct Answer

A:

This is the model-intended best choice because bGP MED influence is conditional on the receiving network's path selection rules. The targeted correction is to distinguish an advertised inbound hint from neighboring-AS route policy decisions. Validate it by observing that a controlled route lookup confirms the neighbor's actual selected entry path.

Incorrect Answers

B:

This option overlooks the decisive condition. Its supporting principle is oSPF uses distinct Hello, database description, link state request, update and acknowledgment functions, while this scenario depends on bGP MED influence is conditional on the receiving network's path selection rules. Verify the correction with: A controlled route lookup confirms the neighbor's actual selected entry path.

C:

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 MED influence is conditional on the receiving network's path selection rules. A correct remediation would distinguish an advertised inbound hint from neighboring-AS route policy decisions and demonstrate: A controlled route lookup confirms the neighbor's actual selected entry path.

D:

The proposed principle concerns another network fault: Disabling loop prevention can introduce persistent interdomain routing loops. Here, bGP MED influence is conditional on the receiving network's path selection rules. The most direct correction is to distinguish an advertised inbound hint from neighboring-AS route policy decisions, confirmed by a controlled route lookup confirms the neighbor's actual selected entry path.

Question 193

A BGP prefix redistribution into OSPF causes a flood of routes that were not in the approved design. Which statement identifies the key design assumption that failed?

  1. The key distinction is: External OSPF redistribution must be reviewed for scope and scale.
  2. Protocol behavior: Operational route troubleshooting starts with active state and resolution evidence.
  3. Underlying principle: Interarea reachability depends on the ABR's view and allowed advertisements.
  4. Root design issue: DR and BDR elections apply to broadcast or NBMA segments, not ordinary point-to-point links.

Explanation

Correct Answer

A:

Underlying cause: External OSPF redistribution must be reviewed for scope and scale. Corrective action: restore explicit policy matching and confirm external route advertisements. Verify the outcome: An LSA and route inspection finds only the authorized external prefix set.

Incorrect Answers

B:

Inspect the configuration, active route state and next-hop reachability before changing preference is a relevant step for the separate scenario in which after a maintenance window a configured customer static prefix is missing from active routes despite no syntax errors. It does not directly fix this case. Instead restore explicit policy matching and confirm external route advertisements; verify: An LSA and route inspection finds only the authorized external prefix set.

C:

The alternative addresses an area border router stops advertising an expected summarized interarea route after a policy change, not the present root cause. Here the selected correction must reflect external OSPF redistribution must be reviewed for scope and scale. Test for: An LSA and route inspection finds only the authorized external prefix set.

D:

This answer would be more suitable when an engineer expects a designated router to be elected on a point-to-point OSPF circuit, where the corrective action is to select the correct network-type behavior and inspect the neighbor-state model. The failure here is different: External OSPF redistribution must be reviewed for scope and scale. Required validation: An LSA and route inspection finds only the authorized external prefix set.

Question 194

An OSPF route appears longer than expected after failover because a backup link's cost was never verified. Which evidence would justify closing this troubleshooting case?

  1. Closeout evidence: When the primary fails the documented backup path is selected without loops.
  2. Acceptance check: The point-to-point adjacency forms without an unnecessary DR election.
  3. The test confirms that the correct summarized route appears in the receiving area's route table.
  4. Expected observation: Only approved traffic uses the alternate table while ordinary transit remains on its path.

Explanation

Correct Answer

A:

Because failover paths are governed by their actual configured metrics, the best response is to confirm the explicit cost plan in a failure rehearsal using route and topology outputs. A reviewer can close the technical case only after confirming that when the primary fails the documented backup path is selected without loops.

Incorrect Answers

B:

The proposed principle concerns another network fault: DR and BDR elections apply to broadcast or NBMA segments, not ordinary point-to-point links. Here, failover paths are governed by their actual configured metrics. The most direct correction is to confirm the explicit cost plan in a failure rehearsal using route and topology outputs, confirmed by when the primary fails the documented backup path is selected without loops.

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: Confirm the explicit cost plan in a failure rehearsal using route and topology outputs. The required observed result is: When the primary fails the documented backup path is selected without loops.

D:

This response would target a different source scenario: An input firewall filter diverts all transit traffic to a management routing instance by mistake. It cannot establish the current acceptance requirement, which is: When the primary fails the documented backup path is selected without loops. The relevant action is: Confirm the explicit cost plan in a failure rehearsal using route and topology outputs.

Question 195

An RSVP tunnel unexpectedly crosses a low-capacity link after a traffic-engineering policy change. Which technical explanation and controlled action address the symptom?

  1. Diagnosis: Labels are generally meaningful within the forwarding context where they are allocated. Action: Explain local label significance and neighbor label binding.
  2. Explanation: Traffic-engineering intent must be reflected in the signaled operational LSP path. Repair: Review explicit or constraint-based path selection against current resource availability.
  3. Fault mechanism: MED is not guaranteed to override local policy or earlier attributes. Remediation: Compare MED use with actual prior BGP decision attributes and neighbor policy.
  4. Root issue: A healthy transport LSP does not guarantee a correct overlay label mapping. Correction: Inspect outer transport and inner service label handling separately.

Explanation

Correct Answer

B:

Underlying cause: Traffic-engineering intent must be reflected in the signaled operational LSP path. Corrective action: review explicit or constraint-based path selection against current resource availability. Verify the outcome: An operational path check excludes the unapproved transit link.

Incorrect Answers

A:

The alternative addresses an operator assumes MPLS labels are globally unique across the provider network, not the present root cause. Here the selected correction must reflect traffic-engineering intent must be reflected in the signaled operational LSP path. Test for: An operational path check excludes the unapproved transit link.

C:

This option overlooks the decisive condition. Its supporting principle is mED is not guaranteed to override local policy or earlier attributes, while this scenario depends on traffic-engineering intent must be reflected in the signaled operational LSP path. Verify the correction with: An operational path check excludes the unapproved transit link.

D:

A healthy transport LSP does not guarantee a correct overlay label mapping describes a neighboring protocol concern. In this case the controlling fact is traffic-engineering intent must be reflected in the signaled operational LSP path. A correct remediation would review explicit or constraint-based path selection against current resource availability and demonstrate: An operational path check excludes the unapproved transit link.

Question 196

An ingress router imposes an MPLS label while an engineer expects the same label value to persist unchanged at every hop. What action-and-test pairing directly resolves the case?

  1. Action: Add a precise prefix and instance match, then inspect effective imports. Evidence: The allowed service routes import and the forbidden more-specific prefixes do not.
  2. Repair: Explain label swap behavior across transit label switching routers. Check: A hop trace shows the intended push and swap operations along the path.
  3. Change: Review reservation constraints and available resources rather than resetting all label sessions. Test: A compatible bandwidth or path choice allows the target RSVP LSP to establish.
  4. Implement: Distinguish signaling reservations from physical link speed and admission control. Verify: A controlled setup respects the approved link reservation policy.

Explanation

Correct Answer

B:

Because labels have locally significant forwarding meaning on each LSP segment, the best response is to explain label swap behavior across transit label switching routers. A reviewer can close the technical case only after confirming that a hop trace shows the intended push and swap operations along the path.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A route import policy accepts more-specific destinations that should remain isolated inside a wholesale tenant. The current case specifically calls for: Explain label swap behavior across transit label switching routers. The required observed result is: A hop trace shows the intended push and swap operations along the path.

C:

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 explain label swap behavior across transit label switching routers; verify: A hop trace shows the intended push and swap operations along the path.

D:

The alternative addresses an engineer sees that RSVP signaling succeeded and assumes all reserved bandwidth remains available for other tunnels, not the present root cause. Here the selected correction must reflect labels have locally significant forwarding meaning on each LSP segment. Test for: A hop trace shows the intended push and swap operations along the path.

Question 197

An LDP-signaled LSP fails when the IGP route to the remote loopback disappears. Which combined repair and acceptance criterion is strongest?

  1. Control: Explain local label significance and neighbor label binding. Accepted result: A path test records locally valid incoming and outgoing label mappings.
  2. Action: Restore the required transport route and inspect label-signaling and next-hop state. Evidence: The transport endpoint again resolves and a labeled probe succeeds.
  3. Repair: Differentiate community tags from reachability and forwarding attributes. Check: Policy based on the intended community alters admission or preference as designed.
  4. Change: Review LDP dependence on reachability and routing of the transport endpoints. Test: The restored IGP path permits LDP forwarding to the remote endpoint.

Explanation

Correct Answer

D:

The selected response implements the principle that lDP label bindings are useful only with a functional path to the FEC next hop. The engineer should review LDP dependence on reachability and routing of the transport endpoints. Successful confirmation means: The restored IGP path permits LDP forwarding to the remote endpoint.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is labels are generally meaningful within the forwarding context where they are allocated, while this scenario depends on lDP label bindings are useful only with a functional path to the FEC next hop. Verify the correction with: The restored IGP path permits LDP forwarding to the remote endpoint.

B:

MPLS relies on selected underlay transport reachability and policy eligibility describes a neighboring protocol concern. In this case the controlling fact is lDP label bindings are useful only with a functional path to the FEC next hop. A correct remediation would review LDP dependence on reachability and routing of the transport endpoints and demonstrate: The restored IGP path permits LDP forwarding to the remote endpoint.

C:

The proposed principle concerns another network fault: Communities are policy signaling metadata and not the packet-forwarding next hop themselves. Here, lDP label bindings are useful only with a functional path to the FEC next hop. The most direct correction is to review LDP dependence on reachability and routing of the transport endpoints, confirmed by the restored IGP path permits LDP forwarding to the remote endpoint.

Question 198

A Q-in-Q customer service leaks traffic between two tenants after the outer service VLAN is reused incorrectly. Which cause-and-remedy pairing reflects the observed problem?

  1. Fault mechanism: Logical service segmentation requires the physical Ethernet encapsulation to match the intended tag model. Remediation: Document VLAN-aware versus flexible tagging and unit classification requirements.
  2. Root issue: Failover depends on compatible virtual router configuration and observable primary loss. Correction: Check VRRP group, interface, priority, advertisements and tracking conditions.
  3. Cause: A working IRB gateway does not validate all L2 paths and trunk members. Response: Trace trunk authorization, bridge-domain membership and MAC learning across the path.
  4. Diagnosis: Provider outer VLAN classification must preserve tenant isolation. Action: Assign distinct service encapsulation and verify edge translation rules.

Explanation

Correct Answer

D:

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:

Document VLAN-aware versus flexible tagging and unit classification requirements is a relevant step for the separate scenario in which an Ethernet access design has multiple logical units using one physical port without specifying frame encapsulation. It does not directly fix this case. Instead assign distinct service encapsulation and verify edge translation rules; verify: Cross-tenant traffic fails while each tenant's inner VLAN passes end to end.

B:

The alternative addresses a VRRP backup router does not take over when the primary gateway interface is disabled, not the present root cause. Here the selected correction must reflect provider outer VLAN classification must preserve tenant isolation. Test for: Cross-tenant traffic fails while each tenant's inner VLAN passes end to end.

C:

This answer would be more suitable when a site complains an IRB gateway answers locally but the downstream VLAN has no remote MAC learning, where the corrective action is to trace trunk authorization, bridge-domain membership and MAC learning across the path. The failure here is different: Provider outer VLAN classification must preserve tenant isolation. Required validation: Cross-tenant traffic fails while each tenant's inner VLAN passes end to end.

Question 199

An IPv6 packet exceeds an underlay path MTU and the operator expects intermediate IPv6 routers to fragment it. What diagnosis and engineering response are most appropriate?

  1. Explanation: Encapsulation reduces effective payload MTU unless transport accommodates the extra headers. Repair: Account for outer IP and GRE header overhead in the MTU design.
  2. Fault mechanism: IPv6 route selection follows prefix matching and route eligibility, not textual address order. Remediation: Apply longest-prefix-match route lookup to the IPv6 destination.
  3. Root issue: An IPv6 BGP route requires a resolvable eligible next hop for forwarding. Correction: Verify IPv6 next-hop reachability and Neighbor Discovery on the outgoing path.
  4. Cause: Intermediate IPv6 routers do not perform ordinary IPv4-style fragmentation of transit packets. Response: Review IPv6 path MTU discovery and endpoint fragmentation requirements.

Explanation

Correct Answer

D:

Underlying cause: Intermediate IPv6 routers do not perform ordinary IPv4-style fragmentation of transit packets. Corrective action: review IPv6 path MTU discovery and endpoint fragmentation requirements. Verify the outcome: The sender adapts to a validated path MTU and payload delivery succeeds.

Incorrect Answers

A:

The proposed principle concerns another network fault: Encapsulation reduces effective payload MTU unless transport accommodates the extra headers. Here, intermediate IPv6 routers do not perform ordinary IPv4-style fragmentation of transit packets. The most direct correction is to review IPv6 path MTU discovery and endpoint fragmentation requirements, confirmed by the sender adapts to a validated path MTU and payload delivery succeeds.

B:

That result would be useful for a different failure, namely: An engineer chooses an IPv6 route based on the printed address alone without comparing prefix length. The current case specifically calls for: Review IPv6 path MTU discovery and endpoint fragmentation requirements. The required observed result is: The sender adapts to a validated path MTU and payload delivery succeeds.

C:

This response would target a different source scenario: An IPv6 BGP route is accepted but cannot be forwarded because its next hop lacks neighbor resolution. It cannot establish the current acceptance requirement, which is: The sender adapts to a validated path MTU and payload delivery succeeds. The relevant action is: Review IPv6 path MTU discovery and endpoint fragmentation requirements.

Question 200

A route appears in the routing table but an engineer assumes its presence proves it was installed into the forwarding table. Which corrective action and confirmation pair is most appropriate?

  1. Repair: Review filter-based forwarding classification and the intended next-table selection. Check: A trace of matching and nonmatching packets shows the approved lookup table.
  2. Change: Compare RIB selection with forwarding-table installation and next-hop resolution. Test: The forwarding entry uses the correct next hop for the active route.
  3. Implement: Review each interface's OSPF metric and compare end-to-end computed costs. Verify: A post-change route view selects the approved shortest path.
  4. Control: Inspect the configuration, active route state and next-hop reachability before changing preference. Accepted result: The static route becomes active after the actual next-hop fault is corrected.

Explanation

Correct Answer

B:

Correct diagnosis: Control-plane route visibility and installed forwarding state are distinct evidence. The appropriate action is: Compare RIB selection with forwarding-table installation and next-hop resolution. The follow-up evidence required is: The forwarding entry uses the correct next hop for the active route.

Incorrect Answers

A:

This answer would be more suitable when a router selects a route in one routing instance while the forwarding policy sends matching traffic into a different table, where the corrective action is to review filter-based forwarding classification and the intended next-table selection. The failure here is different: Control-plane route visibility and installed forwarding state are distinct evidence. Required validation: The forwarding entry uses the correct next hop for the active route.

C:

OSPF forwarding decisions depend on cumulative metric, not interface bandwidth labels alone describes a neighboring protocol concern. In this case the controlling fact is control-plane route visibility and installed forwarding state are distinct evidence. A correct remediation would compare RIB selection with forwarding-table installation and next-hop resolution and demonstrate: The forwarding entry uses the correct next hop for the active route.

D:

The proposed principle concerns another network fault: Operational route troubleshooting starts with active state and resolution evidence. Here, control-plane route visibility and installed forwarding state are distinct evidence. The most direct correction is to compare RIB selection with forwarding-table installation and next-hop resolution, confirmed by the forwarding entry uses the correct next hop for the active route.

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