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 62

Question 610

An operator changes MED and sees no route change because the target AS prioritizes other attributes. Which statement identifies the key design assumption that failed?

  1. Root design issue: MED is not guaranteed to override local policy or earlier attributes.
  2. The governing rule is: iBGP scaling mechanisms reduce the full-mesh session requirement.
  3. The key distinction is: OSPF adjacency requires compatible area and interface parameters.
  4. Protocol behavior: BGP sessions require sustained TCP connectivity independent of physical interface health.

Explanation

Correct Answer

A:

Because mED is not guaranteed to override local policy or earlier attributes, the best response is to compare MED use with actual prior BGP decision attributes and neighbor policy. A reviewer can close the technical case only after confirming that a captured received-path comparison explains which attribute selected the route.

Incorrect Answers

B:

The proposed principle concerns another network fault: iBGP scaling mechanisms reduce the full-mesh session requirement. Here, mED is not guaranteed to override local policy or earlier attributes. The most direct correction is to compare MED use with actual prior BGP decision attributes and neighbor policy, confirmed by a captured received-path comparison explains which attribute selected the route.

C:

That result would be useful for a different failure, namely: Two Junos routers on the same link have mismatched OSPF area identifiers and never form a neighbor relationship. The current case specifically calls for: Compare MED use with actual prior BGP decision attributes and neighbor policy. The required observed result is: A captured received-path comparison explains which attribute selected the route.

D:

This response would target a different source scenario: An EBGP peer drops repeatedly after a firewall change despite clean interface counters. It cannot establish the current acceptance requirement, which is: A captured received-path comparison explains which attribute selected the route. The relevant action is: Compare MED use with actual prior BGP decision attributes and neighbor policy.

Question 611

An operator sends a multicast routing-protocol packet over a GRE tunnel and assumes all physical transit routers must process the inner multicast. Which protocol behavior most directly determines the correct diagnosis?

  1. Underlying principle: A tunnel can carry inner packet types over an underlay forwarding only the outer header.
  2. Root design issue: A usable IP path need not supply a suitable MPLS LSP or labeled transport path.
  3. The governing rule is: Tunnel endpoint parameters must correspond to actual reachable interfaces.
  4. The key distinction is: Encapsulation reduces effective payload MTU unless transport accommodates the extra headers.

Explanation

Correct Answer

A:

The case turns on the distinction that a tunnel can carry inner packet types over an underlay forwarding only the outer header. Apply this concrete engineering step: Distinguish the inner routed payload from outer unicast encapsulation. An acceptable verification outcome is: Underlay traces show the outer endpoint traffic without transit processing of inner routes.

Incorrect Answers

B:

This answer would be more suitable when a loopback loses its MPLS-resolvable route but ordinary IP routing to the loopback remains reachable, where the corrective action is to inspect label-switched next-hop resolution separately from generic IP reachability. The failure here is different: A tunnel can carry inner packet types over an underlay forwarding only the outer header. Required validation: Underlay traces show the outer endpoint traffic without transit processing of inner routes.

C:

This option overlooks the decisive condition. Its supporting principle is tunnel endpoint parameters must correspond to actual reachable interfaces, while this scenario depends on a tunnel can carry inner packet types over an underlay forwarding only the outer header. Verify the correction with: Underlay traces show the outer endpoint traffic without transit processing of inner routes.

D:

Encapsulation reduces effective payload MTU unless transport accommodates the extra headers describes a neighboring protocol concern. In this case the controlling fact is a tunnel can carry inner packet types over an underlay forwarding only the outer header. A correct remediation would distinguish the inner routed payload from outer unicast encapsulation and demonstrate: Underlay traces show the outer endpoint traffic without transit processing of inner routes.

Question 612

An ingress LSP shows up but transit packets are dropped after one router swaps to an unexpected label. What assessment accurately links the fault to its correction?

  1. Root issue: End-to-end signaling state alone cannot pinpoint a data-plane label failure. Correction: Collect hop-local LFIB, label forwarding and interface counters along the LSP.
  2. Cause: Label-switching errors can occur even when control-plane endpoint reachability is good. Response: Inspect the incoming label, outgoing label and interface on each affected LSR.
  3. Diagnosis: A configured static route need not become usable forwarding state when its next hop cannot resolve. Action: Verify recursive next-hop reachability before relying on the static route.
  4. Explanation: Labels have locally significant forwarding meaning on each LSP segment. Repair: Explain label swap behavior across transit label switching routers.

Explanation

Correct Answer

B:

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

Incorrect Answers

A:

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

C:

Verify recursive next-hop reachability before relying on the static route is a relevant step for the separate scenario in which a provider router has a static route for a customer prefix but its configured next hop is not reachable through any active route. It does not directly fix this case. Instead inspect the incoming label, outgoing label and interface on each affected LSR; verify: The repaired hop has the expected swap operation and carries a test packet.

D:

The alternative addresses an ingress router imposes an MPLS label while an engineer expects the same label value to persist unchanged at every hop, not the present root cause. Here the selected correction must reflect label-switching errors can occur even when control-plane endpoint reachability is good. Test for: The repaired hop has the expected swap operation and carries a test packet.

Question 613

An operator accepts a source-address block as an ordinary next-hop network even though the address is classified as martian. Which change best corrects the failure without losing the intended design?

  1. Recommended change: Separate route-selection and lookup-table changes and test each with candidate configuration.
  2. Next step: Distinguish an advertised inbound hint from neighboring-AS route policy decisions.
  3. Corrective action: Distinguish equal-cost multipath from the exact traffic-distribution algorithm used by the forwarding plane.
  4. Apply this control: Review martian-address treatment and justify any carefully scoped exception.

Explanation

Correct Answer

D:

The selected response implements the principle that address validity and martian filtering affect which route sources are considered acceptable. The engineer should review martian-address treatment and justify any carefully scoped exception. Successful confirmation means: The rejected address remains excluded or a documented narrowly scoped exception is applied.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is small reversible route-policy changes simplify troubleshooting and rollback, while this scenario depends on address validity and martian filtering affect which route sources are considered acceptable. Verify the correction with: The rejected address remains excluded or a documented narrowly scoped exception is applied.

B:

BGP MED influence is conditional on the receiving network's path selection rules describes a neighboring protocol concern. In this case the controlling fact is address validity and martian filtering affect which route sources are considered acceptable. A correct remediation would review martian-address treatment and justify any carefully scoped exception and demonstrate: The rejected address remains excluded or a documented narrowly scoped exception is applied.

C:

The proposed principle concerns another network fault: Multiple eligible forwarding next hops do not guarantee per-packet round-robin use. Here, address validity and martian filtering affect which route sources are considered acceptable. The most direct correction is to review martian-address treatment and justify any carefully scoped exception, confirmed by the rejected address remains excluded or a documented narrowly scoped exception is applied.

Question 614

An EBGP peer drops repeatedly after a firewall change despite clean interface counters. What assessment accurately links the fault to its correction?

  1. Explanation: BGP MED influence is conditional on the receiving network's path selection rules. Repair: Distinguish an advertised inbound hint from neighboring-AS route policy decisions.
  2. Fault mechanism: BGP edge hygiene protects the routing domain from unauthorized reachability. Remediation: Tighten customer import route filtering and test permitted prefix lengths.
  3. Root issue: OSPF network-type and Hello compatibility can prevent adjacency formation. Correction: Verify compatible network and Hello parameters including mask where applicable.
  4. Cause: BGP sessions require sustained TCP connectivity independent of physical interface health. Response: Inspect TCP reachability, permitted port 179, and authentication on the transport path.

Explanation

Correct Answer

D:

This is the model-intended best choice because bGP sessions require sustained TCP connectivity independent of physical interface health. The targeted correction is to inspect TCP reachability, permitted port 179, and authentication on the transport path. Validate it by observing that an authenticated TCP session stays Established after the rule correction.

Incorrect Answers

A:

Distinguish an advertised inbound hint from neighboring-AS route policy decisions is a relevant step for the separate scenario in which an inbound MED is assumed to control outgoing traffic even though the receiving network has its own path-selection policies. It does not directly fix this case. Instead inspect TCP reachability, permitted port 179, and authentication on the transport path; verify: An authenticated TCP session stays Established after the rule correction.

B:

The alternative addresses a customer advertises an unauthorized more-specific and the PE propagates it across the provider core, not the present root cause. Here the selected correction must reflect bGP sessions require sustained TCP connectivity independent of physical interface health. Test for: An authenticated TCP session stays Established after the rule correction.

C:

This answer would be more suitable when a router sends OSPF Hello packets but remains stuck because the subnet mask differs across neighbors on a broadcast link, where the corrective action is to verify compatible network and Hello parameters including mask where applicable. The failure here is different: BGP sessions require sustained TCP connectivity independent of physical interface health. Required validation: An authenticated TCP session stays Established after the rule correction.

Question 615

A route appears in the routing table but an engineer assumes its presence proves it was installed into the forwarding table. Which test result would best confirm a successful fix?

  1. Verification result: Only approved external prefixes appear in the OSPF domain.
  2. Closeout evidence: A route lookup shows an active reachable next hop and traffic reaches the customer.
  3. Acceptance check: A test packet follows the expected active forwarding next hop and interface.
  4. The test confirms that the forwarding entry uses the correct next hop for the active route.

Explanation

Correct Answer

D:

Underlying cause: Control-plane route visibility and installed forwarding state are distinct evidence. Corrective action: compare RIB selection with forwarding-table installation and next-hop resolution. Verify the outcome: The forwarding entry uses the correct next hop for the active route.

Incorrect Answers

A:

The proposed principle concerns another network fault: Routing policy controls which external reachability is injected into OSPF. 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.

B:

That result would be useful for a different failure, namely: A provider router has a static route for a customer prefix but its configured next hop is not reachable through any active route. The current case specifically calls for: Compare RIB selection with forwarding-table installation and next-hop resolution. The required observed result is: The forwarding entry uses the correct next hop for the active route.

C:

This response would target a different source scenario: A route shows as active but the interface destination still drops traffic after an interface move. It cannot establish the current acceptance requirement, which is: The forwarding entry uses the correct next hop for the active route. The relevant action is: Compare RIB selection with forwarding-table installation and next-hop resolution.

Question 616

An RSVP tunnel unexpectedly crosses a low-capacity link after a traffic-engineering policy change. Which corrective action and confirmation pair is most appropriate?

  1. Action: Review segment identifiers and forwarding under SR-MPLS. Evidence: A test packet follows its segment list through installed SR forwarding.
  2. Repair: Restore the required transport route and inspect label-signaling and next-hop state. Check: The transport endpoint again resolves and a labeled probe succeeds.
  3. Change: Investigate AS-path loop prevention rather than overriding it without risk review. Test: The route is accepted only after the AS-path design is corrected.
  4. Implement: Review explicit or constraint-based path selection against current resource availability. Verify: An operational path check excludes the unapproved transit link.

Explanation

Correct Answer

D:

Because traffic-engineering intent must be reflected in the signaled operational LSP path, the best response is to review explicit or constraint-based path selection against current resource availability. A reviewer can close the technical case only after confirming that an operational path check excludes the unapproved transit link.

Incorrect Answers

A:

This answer would be more suitable when a provider chooses segment-routing MPLS but assumes every transit hop needs per-LSP RSVP state, where the corrective action is to review segment identifiers and forwarding under SR-MPLS. The failure here is different: Traffic-engineering intent must be reflected in the signaled operational LSP path. Required validation: An operational path check excludes the unapproved transit link.

B:

This option overlooks the decisive condition. Its supporting principle is mPLS relies on selected underlay transport reachability and policy eligibility, 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.

C:

BGP AS-path information can prevent routes from looping into an AS 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 617

A provider failover exposes an alternate IS-IS path that had never been tested for next-hop resolution. What remediation is most directly applicable?

  1. Next step: Inspect TCP reachability, permitted port 179, and authentication on the transport path.
  2. Corrective action: Rehearse the failure and inspect active next hops and IS-IS route changes.
  3. Apply this control: Review current DIS election rules for the network and protocol instance.
  4. Remediation: Inspect IS-IS interface enablement, levels, area identifiers and link type.

Explanation

Correct Answer

B:

The selected response implements the principle that a backup path requires functional forwarding, not merely topology presence. The engineer should rehearse the failure and inspect active next hops and IS-IS route changes. Successful confirmation means: The backup next hop resolves and carries test traffic after the primary link fails.

Incorrect Answers

A:

This response would target a different source scenario: An EBGP peer drops repeatedly after a firewall change despite clean interface counters. It cannot establish the current acceptance requirement, which is: The backup next hop resolves and carries test traffic after the primary link fails. The relevant action is: Rehearse the failure and inspect active next hops and IS-IS route changes.

C:

The alternative addresses an IS-IS LAN elects a new DIS and the engineer assumes the result must preempt every existing elected node, not the present root cause. Here the selected correction must reflect a backup path requires functional forwarding, not merely topology presence. Test for: The backup next hop resolves and carries test traffic after the primary link fails.

D:

This answer would be more suitable when a Junos router shows no IS-IS adjacency after a circuit migration though the interface is physically up, where the corrective action is to inspect IS-IS interface enablement, levels, area identifiers and link type. The failure here is different: A backup path requires functional forwarding, not merely topology presence. Required validation: The backup next hop resolves and carries test traffic after the primary link fails.

Question 618

A port belongs to a VLAN but traffic to a remote site is forwarded through a different bridge domain. Which protocol behavior most directly determines the correct diagnosis?

  1. The key distinction is: Untagged frame classification is local to the receiving interface.
  2. Protocol behavior: MSTP region agreement affects how instances interoperate across links.
  3. Underlying principle: A customer VLAN tag can be scoped by access interface and provider service context.
  4. Root design issue: Ethernet forwarding uses bridge-domain context rather than arbitrary IP-route matching.

Explanation

Correct Answer

D:

This option addresses the stated case rather than another networking issue. Principle: Ethernet forwarding uses bridge-domain context rather than arbitrary IP-route matching. Remedy: Trace frame classification and virtual-switch bridge-domain association. Proof: A tagged test frame reaches the approved remote port in the same domain.

Incorrect Answers

A:

Untagged frame classification is local to the receiving interface describes a neighboring protocol concern. In this case the controlling fact is ethernet forwarding uses bridge-domain context rather than arbitrary IP-route matching. A correct remediation would trace frame classification and virtual-switch bridge-domain association and demonstrate: A tagged test frame reaches the approved remote port in the same domain.

B:

The proposed principle concerns another network fault: MSTP region agreement affects how instances interoperate across links. Here, ethernet forwarding uses bridge-domain context rather than arbitrary IP-route matching. The most direct correction is to trace frame classification and virtual-switch bridge-domain association, confirmed by a tagged test frame reaches the approved remote port in the same domain.

C:

That result would be useful for a different failure, namely: Two network services use identical customer VLAN IDs and the team assumes their frames must share one L2 broadcast domain. The current case specifically calls for: Trace frame classification and virtual-switch bridge-domain association. The required observed result is: A tagged test frame reaches the approved remote port in the same domain.

Question 619

A route import policy accepts more-specific destinations that should remain isolated inside a wholesale tenant. Which root-cause explanation and corrective action fit the case?

  1. Explanation: Small reversible route-policy changes simplify troubleshooting and rollback. Repair: Separate route-selection and lookup-table changes and test each with candidate configuration.
  2. 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.
  3. Root issue: Routing policy acceptance must reflect explicitly permitted destinations. Correction: Add a precise prefix and instance match, then inspect effective imports.
  4. Cause: Multiple eligible forwarding next hops do not guarantee per-packet round-robin use. Response: Distinguish equal-cost multipath from the exact traffic-distribution algorithm used by the forwarding plane.

Explanation

Correct Answer

C:

The selected response implements the principle that routing policy acceptance must reflect explicitly permitted destinations. The engineer should add a precise prefix and instance match, then inspect effective imports. Successful confirmation means: The allowed service routes import and the forbidden more-specific prefixes do not.

Incorrect Answers

A:

The alternative addresses a policy adjustment changes both routing preference and forwarding instance selection in one unreviewed commit, not the present root cause. Here the selected correction must reflect routing policy acceptance must reflect explicitly permitted destinations. Test for: The allowed service routes import and the forbidden more-specific prefixes do not.

B:

This answer would be more suitable when an operator changes MED and sees no route change because the target AS prioritizes other attributes, where the corrective action is to compare MED use with actual prior BGP decision attributes and neighbor policy. The failure here is different: Routing policy acceptance must reflect explicitly permitted destinations. Required validation: The allowed service routes import and the forbidden more-specific prefixes do not.

D:

Multiple eligible forwarding next hops do not guarantee per-packet round-robin use describes a neighboring protocol concern. In this case the controlling fact is routing policy acceptance must reflect explicitly permitted destinations. A correct remediation would add a precise prefix and instance match, then inspect effective imports and demonstrate: The allowed service routes import and the forbidden more-specific prefixes do not.

Question 620

An inbound MED is assumed to control outgoing traffic even though the receiving network has its own path-selection policies. Which combined repair and acceptance criterion is strongest?

  1. Repair: Split export policy by authorized customer scope and verify negative advertisements. Check: The unauthorized customer receives no leaked prefixes in a route advertisement check.
  2. Change: Align the area membership and verify OSPF interface settings on both sides. Test: The peers progress to the expected adjacency state and exchange LSAs.
  3. Implement: Distinguish an advertised inbound hint from neighboring-AS route policy decisions. Verify: A controlled route lookup confirms the neighbor's actual selected entry path.
  4. Control: Review BGP next-hop reachability and explicit next-hop handling. Accepted result: The internal peer has a valid route to the BGP next hop and installs the prefix.

Explanation

Correct Answer

C:

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

A:

That result would be useful for a different failure, namely: One customer’s new prefixes are advertised to a second unrelated customer via a shared export group. The current case specifically calls for: Distinguish an advertised inbound hint from neighboring-AS route policy decisions. The required observed result is: A controlled route lookup confirms the neighbor's actual selected entry path.

B:

This response would target a different source scenario: Two Junos routers on the same link have mismatched OSPF area identifiers and never form a neighbor relationship. It cannot establish the current acceptance requirement, which is: A controlled route lookup confirms the neighbor's actual selected entry path. The relevant action is: Distinguish an advertised inbound hint from neighboring-AS route policy decisions.

D:

The alternative addresses a provider's iBGP peer receives a route but cannot resolve the external next hop in its own IGP, not the present root cause. Here the selected correction must reflect bGP MED influence is conditional on the receiving network's path selection rules. Test for: A controlled route lookup confirms the neighbor's actual selected entry path.

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