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 19

Question 180

A router selects a route in one routing instance while the forwarding policy sends matching traffic into a different table. Which protocol behavior most directly determines the correct diagnosis?

  1. Root design issue: Policy inheritance and term action order affect BGP route advertisement.
  2. The governing rule is: Control-plane route visibility and installed forwarding state are distinct evidence.
  3. The key distinction is: Filter-based routing policy requires explicit match conditions and a safe default behavior.
  4. Protocol behavior: Policy-based forwarding can select a routing table independently of the destination lookup in the ingress default table.

Explanation

Correct Answer

D:

Correct diagnosis: Policy-based forwarding can select a routing table independently of the destination lookup in the ingress default table. The appropriate action is: Review filter-based forwarding classification and the intended next-table selection. The follow-up evidence required is: A trace of matching and nonmatching packets shows the approved lookup table.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A BGP export policy matches a community but no routes leave the peer after a group-level policy reorder. The current case specifically calls for: Review filter-based forwarding classification and the intended next-table selection. The required observed result is: A trace of matching and nonmatching packets shows the approved lookup table.

B:

This response would target a different source scenario: A route appears in the routing table but an engineer assumes its presence proves it was installed into the forwarding table. It cannot establish the current acceptance requirement, which is: A trace of matching and nonmatching packets shows the approved lookup table. The relevant action is: Review filter-based forwarding classification and the intended next-table selection.

C:

Narrow filter match terms and validate filter-based forwarding for both matched and unmatched probes is a relevant step for the separate scenario in which an input firewall filter diverts all transit traffic to a management routing instance by mistake. It does not directly fix this case. Instead review filter-based forwarding classification and the intended next-table selection; verify: A trace of matching and nonmatching packets shows the approved lookup table.

Question 181

An engineer uses loop protection as if it served the same purpose as BPDU protection on every port. What operational check demonstrates that the intended outcome occurred?

  1. Expected observation: The ring converges with no forwarding loop and sustained connectivity.
  2. Verification result: Each VLAN maps to its intended instance and designated root.
  3. Closeout evidence: The bridge domain and IRB interface share the configured gateway context.
  4. Acceptance check: Separate fault injections trigger the intended protection per port role.

Explanation

Correct Answer

D:

The selected response implements the principle that spanning-tree security mechanisms protect distinct topology and control-plane risks. The engineer should match loop, BPDU and root protection to their different fault conditions. Successful confirmation means: Separate fault injections trigger the intended protection per port role.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is loop prevention depends on compatible STP participation across redundant Ethernet links, while this scenario depends on spanning-tree security mechanisms protect distinct topology and control-plane risks. Verify the correction with: Separate fault injections trigger the intended protection per port role.

B:

MSTP can group VLANs into multiple spanning-tree instances under shared region parameters describes a neighboring protocol concern. In this case the controlling fact is spanning-tree security mechanisms protect distinct topology and control-plane risks. A correct remediation would match loop, BPDU and root protection to their different fault conditions and demonstrate: Separate fault injections trigger the intended protection per port role.

C:

The proposed principle concerns another network fault: Integrated routing bridges a defined L2 domain into an L3 interface when correctly associated. Here, spanning-tree security mechanisms protect distinct topology and control-plane risks. The most direct correction is to match loop, BPDU and root protection to their different fault conditions, confirmed by separate fault injections trigger the intended protection per port role.

Question 182

An operator changes MED and sees no route change because the target AS prioritizes other attributes. Which technical explanation and controlled action address the symptom?

  1. Root issue: BGP transport connectivity does not guarantee every address family is negotiated and active. Correction: Verify negotiated address families and family-specific routing tables.
  2. Cause: MED is not guaranteed to override local policy or earlier attributes. Response: Compare MED use with actual prior BGP decision attributes and neighbor policy.
  3. Diagnosis: Neighbor discovery can succeed even when database exchange parameters prevent completion. Action: Check MTU and interface compatibility and inspect neighbor-state details.
  4. Explanation: Policy evaluation order can short-circuit later intended acceptance. Repair: Evaluate policy terms in effective order and test matching routes.

Explanation

Correct Answer

B:

This option addresses the stated case rather than another networking issue. Principle: MED is not guaranteed to override local policy or earlier attributes. Remedy: Compare MED use with actual prior BGP decision attributes and neighbor policy. Proof: A captured received-path comparison explains which attribute selected the route.

Incorrect Answers

A:

Verify negotiated address families and family-specific routing tables is a relevant step for the separate scenario in which a peer announces an IPv6 prefix but the operator checks only the IPv4 BGP route family. It does not directly fix this case. Instead compare MED use with actual prior BGP decision attributes and neighbor policy; verify: A captured received-path comparison explains which attribute selected the route.

C:

This answer would be more suitable when an OSPF trace shows Hellos received but database synchronization stalls at ExStart or Exchange, where the corrective action is to check MTU and interface compatibility and inspect neighbor-state details. The failure here is different: MED is not guaranteed to override local policy or earlier attributes. Required validation: A captured received-path comparison explains which attribute selected the route.

D:

This option overlooks the decisive condition. Its supporting principle is policy evaluation order can short-circuit later intended acceptance, while this scenario depends on mED is not guaranteed to override local policy or earlier attributes. Verify the correction with: A captured received-path comparison explains which attribute selected the route.

Question 183

A core engineer sees that IPv6 reachability is absent despite IS-IS adjacency and concludes the adjacency itself is broken. What diagnosis and engineering response are most appropriate?

  1. Fault mechanism: Route reflection can fail due to session or policy scope even when the route exists centrally. Remediation: Check client definitions, route-reflector session state and export policy.
  2. Root issue: IS-IS can convey multiple address families with appropriate support. Correction: Check the IPv6 family configuration and advertised reachability rather than rebuilding IPv4 adjacency.
  3. Cause: An adjacency can be operational while a specific family or prefix is not advertised. Response: Distinguish IS-IS adjacency from address-family reachability advertisements.
  4. Diagnosis: The IS-IS DIS concept applies to LANs rather than ordinary point-to-point links. Action: Differentiate multiaccess DIS election from point-to-point adjacency behavior.

Explanation

Correct Answer

C:

The case turns on the distinction that an adjacency can be operational while a specific family or prefix is not advertised. Apply this concrete engineering step: Distinguish IS-IS adjacency from address-family reachability advertisements. An acceptable verification outcome is: The expected IPv6 prefix appears after family and policy review.

Incorrect Answers

A:

The proposed principle concerns another network fault: Route reflection can fail due to session or policy scope even when the route exists centrally. Here, an adjacency can be operational while a specific family or prefix is not advertised. The most direct correction is to distinguish IS-IS adjacency from address-family reachability advertisements, confirmed by the expected IPv6 prefix appears after family and policy review.

B:

That result would be useful for a different failure, namely: IPv4 IS-IS routing works but IPv6 routes do not appear on a dual-stack backbone. The current case specifically calls for: Distinguish IS-IS adjacency from address-family reachability advertisements. The required observed result is: The expected IPv6 prefix appears after family and policy review.

D:

Differentiate multiaccess DIS election from point-to-point adjacency behavior is a relevant step for the separate scenario in which an engineer expects an IS-IS Designated Intermediate System election on a point-to-point core link. It does not directly fix this case. Instead distinguish IS-IS adjacency from address-family reachability advertisements; verify: The expected IPv6 prefix appears after family and policy review.

Question 184

An operator assumes OSPFv3 must form using the same interface and address settings as OSPFv2. What diagnosis and engineering response are most appropriate?

  1. Explanation: Intermediate IPv6 routers do not perform ordinary IPv4-style fragmentation of transit packets. Repair: Review IPv6 path MTU discovery and endpoint fragmentation requirements.
  2. Fault mechanism: OSPFv3 has protocol-specific requirements for neighbor exchange and IPv6 routing. Remediation: Review the IPv6 OSPFv3 address-family and interface adjacency model.
  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: IS-IS packet exchange and transport differ from OSPF over IP. Response: Recognize IS-IS as a link-layer routing protocol with its own PDUs.

Explanation

Correct Answer

B:

Correct diagnosis: OSPFv3 has protocol-specific requirements for neighbor exchange and IPv6 routing. The appropriate action is: Review the IPv6 OSPFv3 address-family and interface adjacency model. The follow-up evidence required is: The peers exchange the expected IPv6 routes using a valid OSPFv3 adjacency.

Incorrect Answers

A:

This answer would be more suitable when an IPv6 packet exceeds an underlay path MTU and the operator expects intermediate IPv6 routers to fragment it, where the corrective action is to review IPv6 path MTU discovery and endpoint fragmentation requirements. The failure here is different: OSPFv3 has protocol-specific requirements for neighbor exchange and IPv6 routing. Required validation: The peers exchange the expected IPv6 routes using a valid OSPFv3 adjacency.

C:

An IPv6 BGP route requires a resolvable eligible next hop for forwarding describes a neighboring protocol concern. In this case the controlling fact is oSPFv3 has protocol-specific requirements for neighbor exchange and IPv6 routing. A correct remediation would review the IPv6 OSPFv3 address-family and interface adjacency model and demonstrate: The peers exchange the expected IPv6 routes using a valid OSPFv3 adjacency.

D:

The proposed principle concerns another network fault: IS-IS packet exchange and transport differ from OSPF over IP. Here, oSPFv3 has protocol-specific requirements for neighbor exchange and IPv6 routing. The most direct correction is to review the IPv6 OSPFv3 address-family and interface adjacency model, confirmed by the peers exchange the expected IPv6 routes using a valid OSPFv3 adjacency.

Question 185

A segment routing node uses a prefix segment but the operator treats it as a local adjacency segment. What diagnosis and engineering response are most appropriate?

  1. Diagnosis: Routing policy acceptance must reflect explicitly permitted destinations. Action: Add a precise prefix and instance match, then inspect effective imports.
  2. Explanation: MPLS forwarding requires coordinated label signaling and forwarding entries. Repair: Differentiate IP underlay reachability from LDP or RSVP control state.
  3. Fault mechanism: Different segment types express different routing or link steering semantics. Remediation: Distinguish prefix-based segment reachability from adjacency-specific forwarding instructions.
  4. Root issue: An LSP cannot follow an unavailable required hop. Correction: Update the engineered path constraints and verify candidate topology availability.

Explanation

Correct Answer

C:

The critical observation is: Different segment types express different routing or link steering semantics. Correct it by taking this action: Distinguish prefix-based segment reachability from adjacency-specific forwarding instructions. Confirm the outcome with: A segment trace follows the desired prefix or explicit adjacency.

Incorrect Answers

A:

This response would target a different source scenario: A route import policy accepts more-specific destinations that should remain isolated inside a wholesale tenant. It cannot establish the current acceptance requirement, which is: A segment trace follows the desired prefix or explicit adjacency. The relevant action is: Distinguish prefix-based segment reachability from adjacency-specific forwarding instructions.

B:

Differentiate IP underlay reachability from LDP or RSVP control state is a relevant step for the separate scenario in which a transport route is reachable through an IP interface but the LSP still fails due to incomplete label distribution. It does not directly fix this case. Instead distinguish prefix-based segment reachability from adjacency-specific forwarding instructions; verify: A segment trace follows the desired prefix or explicit adjacency.

D:

This answer would be more suitable when an operator configured an explicit RSVP path through a link that is now administratively down, where the corrective action is to update the engineered path constraints and verify candidate topology availability. The failure here is different: Different segment types express different routing or link steering semantics. Required validation: A segment trace follows the desired prefix or explicit adjacency.

Question 186

A new Junos edge router can ping IPv4 customers but cannot route IPv6 traffic to the same site. What remediation is most directly applicable?

  1. Corrective action: Verify IPv6 next-hop reachability and Neighbor Discovery on the outgoing path.
  2. Apply this control: Validate IPv6 addressing, neighbor discovery and inet6 routing separately.
  3. Remediation: Review the IPv6 OSPFv3 address-family and interface adjacency model.
  4. Recommended change: Recognize IS-IS as a link-layer routing protocol with its own PDUs.

Explanation

Correct Answer

B:

This is the model-intended best choice because iPv4 operational success does not prove IPv6 forwarding configuration. The targeted correction is to validate IPv6 addressing, neighbor discovery and inet6 routing separately. Validate it by observing that the intended IPv6 neighbor and destination routes appear and traffic succeeds.

Incorrect Answers

A:

An IPv6 BGP route requires a resolvable eligible next hop for forwarding describes a neighboring protocol concern. In this case the controlling fact is iPv4 operational success does not prove IPv6 forwarding configuration. A correct remediation would validate IPv6 addressing, neighbor discovery and inet6 routing separately and demonstrate: The intended IPv6 neighbor and destination routes appear and traffic succeeds.

C:

That result would be useful for a different failure, namely: An operator assumes OSPFv3 must form using the same interface and address settings as OSPFv2. 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.

D:

This response would target a different source scenario: A technician tries to diagnose an IS-IS area failure only by inspecting IP multicast Hellos. 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 187

A failover plan relies on one physical interface carrying several links and calls it a redundant LAG. Which change best corrects the failure without losing the intended design?

  1. Next step: Distinguish member-link redundancy from a single physical failure domain.
  2. Corrective action: Inspect whether nonstop bridging is available and configured for the relevant L2 control plane.
  3. Apply this control: Evaluate MSTP instances and explicit VLAN-to-instance mapping.
  4. Remediation: Differentiate forwarding continuity under GRES from routing-protocol state preservation.

Explanation

Correct Answer

A:

The case turns on the distinction that link aggregation improves availability only when member links and topology provide meaningful redundancy. Apply this concrete engineering step: Distinguish member-link redundancy from a single physical failure domain. An acceptable verification outcome is: A member link failure leaves traffic flowing through a remaining usable member.

Incorrect Answers

B:

This answer would be more suitable when layer 2 forwarding is disrupted during Routing Engine replacement even though high availability was enabled for routing, where the corrective action is to inspect whether nonstop bridging is available and configured for the relevant L2 control plane. The failure here is different: Link aggregation improves availability only when member links and topology provide meaningful redundancy. Required validation: A member link failure leaves traffic flowing through a remaining usable member.

C:

This option overlooks the decisive condition. Its supporting principle is mSTP can group VLANs into multiple spanning-tree instances under shared region parameters, 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.

D:

GRES preserves forwarding and kernel interface state but does not by itself retain the routing control plane 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.

Question 188

A router learns the same prefix from peers in distinct autonomous systems but the engineer compares only BGP hop count. Which cause-and-remedy pairing reflects the observed problem?

  1. 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.
  2. Root issue: BGP selection is policy-driven and is not equivalent to IGP least-hop routing. Correction: Trace the applicable BGP route-selection steps and local policies.
  3. Cause: BGP group inheritance and policy direction govern which advertisements are modified. Response: Map inbound and outbound policy points and confirm the intended communities.
  4. Diagnosis: LDP label bindings are useful only with a functional path to the FEC next hop. Action: Review LDP dependence on reachability and routing of the transport endpoints.

Explanation

Correct Answer

B:

Because bGP selection is policy-driven and is not equivalent to IGP least-hop routing, the best response is to trace the applicable BGP route-selection steps and local policies. A reviewer can close the technical case only after confirming that the chosen path matches the configured preference and applicable attributes.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A provider accepts a route with its own AS in the received path after a risky bypass of loop prevention. The current case specifically calls for: Trace the applicable BGP route-selection steps and local policies. The required observed result is: The chosen path matches the configured preference and applicable attributes.

C:

Map inbound and outbound policy points and confirm the intended communities is a relevant step for the separate scenario in which a service provider tags prefixes for selective export but applies the community-match policy to the wrong neighbor group. It does not directly fix this case. Instead trace the applicable BGP route-selection steps and local policies; verify: The chosen path matches the configured preference and applicable attributes.

D:

The alternative addresses an LDP-signaled LSP fails when the IGP route to the remote loopback disappears, not the present root cause. Here the selected correction must reflect bGP selection is policy-driven and is not equivalent to IGP least-hop routing. Test for: The chosen path matches the configured preference and applicable attributes.

Question 189

Two equal-capacity IS-IS links receive unequal metrics and traffic takes an unexpected path. What is the primary routing or switching concept illustrated?

  1. The governing rule is: IS-IS packet exchange and transport differ from OSPF over IP.
  2. The key distinction is: IS-IS path selection is based on link-state topology and metrics.
  3. Protocol behavior: IS-IS can convey multiple address families with appropriate support.
  4. Underlying principle: MED is not guaranteed to override local policy or earlier attributes.

Explanation

Correct Answer

B:

The case turns on the distinction that iS-IS path selection is based on link-state topology and metrics. Apply this concrete engineering step: Compute total advertised IS-IS metrics instead of assuming capacity implies preference. An acceptable verification outcome is: The forwarding route follows the lowest intended metric path.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is iS-IS packet exchange and transport differ from OSPF over IP, while this scenario depends on iS-IS path selection is based on link-state topology and metrics. Verify the correction with: The forwarding route follows the lowest intended metric path.

C:

The proposed principle concerns another network fault: IS-IS can convey multiple address families with appropriate support. Here, iS-IS path selection is based on link-state topology and metrics. The most direct correction is to compute total advertised IS-IS metrics instead of assuming capacity implies preference, confirmed by the forwarding route follows the lowest intended metric path.

D:

That result would be useful for a different failure, namely: An operator changes MED and sees no route change because the target AS prioritizes other attributes. 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.

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.

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