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 45

Question 440

A GRE tunnel is reachable from one routing instance but the remote customer route leaks into a different instance. Which statement identifies the key design assumption that failed?

  1. Underlying principle: BGP family negotiation and route policy control IPv6 NLRI exchange.
  2. Root design issue: Tunnel identification and routing-instance separation must be explicit in overlapping designs.
  3. The governing rule is: Tunneling transport and customer route isolation are separate configurations.
  4. The key distinction is: GRE encapsulation overhead can expose MTU blackholes for larger payloads.

Explanation

Correct Answer

C:

This option addresses the stated case rather than another networking issue. Principle: Tunneling transport and customer route isolation are separate configurations. Remedy: Verify instance ownership and route policy at both tunnel endpoints. Proof: Traffic uses the tunnel in the intended customer routing instance only.

Incorrect Answers

A:

This answer would be more suitable when a BGP peer carries IPv4 prefixes but the team assumes IPv6 prefixes are automatically shared, where the corrective action is to enable and verify the intended IPv6 BGP family and export policy. The failure here is different: Tunneling transport and customer route isolation are separate configurations. Required validation: Traffic uses the tunnel in the intended customer routing instance only.

B:

This option overlooks the decisive condition. Its supporting principle is tunnel identification and routing-instance separation must be explicit in overlapping designs, while this scenario depends on tunneling transport and customer route isolation are separate configurations. Verify the correction with: Traffic uses the tunnel in the intended customer routing instance only.

D:

The proposed principle concerns another network fault: GRE encapsulation overhead can expose MTU blackholes for larger payloads. Here, tunneling transport and customer route isolation are separate configurations. The most direct correction is to verify instance ownership and route policy at both tunnel endpoints, confirmed by traffic uses the tunnel in the intended customer routing instance only.

Question 441

A provider's LDP neighbors disappear after an IGP outage while physical links remain up. What operational check demonstrates that the intended outcome occurred?

  1. The test confirms that the intended inet6 family receives and selects the IPv6 prefix.
  2. Expected observation: A packet trace verifies the intended stack at the penultimate and egress hops.
  3. Verification result: LDP sessions recover and labeled FEC bindings reappear after underlay repair.
  4. Closeout evidence: The repaired hop has the expected swap operation and carries a test packet.

Explanation

Correct Answer

C:

The critical observation is: LDP signaling depends on the routing and transport state of its endpoints. Correct it by taking this action: Check transport reachability, LDP session state and the relevant IGP routes. Confirm the outcome with: LDP sessions recover and labeled FEC bindings reappear after underlay repair.

Incorrect Answers

A:

This response would target a different source scenario: A peer announces an IPv6 prefix but the operator checks only the IPv4 BGP route family. It cannot establish the current acceptance requirement, which is: LDP sessions recover and labeled FEC bindings reappear after underlay repair. The relevant action is: Check transport reachability, LDP session state and the relevant IGP routes.

B:

Recognize penultimate-hop popping as an allowed LSP forwarding behavior is a relevant step for the separate scenario in which a penultimate router pops a transport label and the egress receives native IP even though the engineer expected a visible final outer label. It does not directly fix this case. Instead check transport reachability, LDP session state and the relevant IGP routes; verify: LDP sessions recover and labeled FEC bindings reappear after underlay repair.

D:

This answer would be more suitable when an ingress LSP shows up but transit packets are dropped after one router swaps to an unexpected label, where the corrective action is to inspect the incoming label, outgoing label and interface on each affected LSR. The failure here is different: LDP signaling depends on the routing and transport state of its endpoints. Required validation: LDP sessions recover and labeled FEC bindings reappear after underlay repair.

Question 442

A Routing Engine switchover retains data-plane traffic briefly but causes OSPF adjacencies to restart. What should the operations engineer do first to address the stated fault?

  1. Recommended change: Check whether GRES is paired with the intended GR or NSR support and verify protocol state.
  2. Next step: Inspect member states, traffic distribution and configured minimum link expectations.
  3. Corrective action: Enable the appropriate spanning-tree protection and verify the blocked redundant path.
  4. Apply this control: Review supported mutual exclusivity and select the intended HA control-plane method.

Explanation

Correct Answer

A:

Because forwarding-plane continuity does not prove control-plane routing continuity, the best response is to check whether GRES is paired with the intended GR or NSR support and verify protocol state. A reviewer can close the technical case only after confirming that a planned switchover test documents forwarding and neighbor behavior against the HA design.

Incorrect Answers

B:

The proposed principle concerns another network fault: Aggregated links need operational member health monitoring and suitable capacity planning. Here, forwarding-plane continuity does not prove control-plane routing continuity. The most direct correction is to check whether GRES is paired with the intended GR or NSR support and verify protocol state, confirmed by a planned switchover test documents forwarding and neighbor behavior against the HA design.

C:

That result would be useful for a different failure, namely: A Layer 2 ring floods broadcast frames repeatedly after an extra cable is connected. The current case specifically calls for: Check whether GRES is paired with the intended GR or NSR support and verify protocol state. The required observed result is: A planned switchover test documents forwarding and neighbor behavior against the HA design.

D:

This response would target a different source scenario: A provider tries to enable nonstop active routing and graceful-restart mode simultaneously on the same Junos device. It cannot establish the current acceptance requirement, which is: A planned switchover test documents forwarding and neighbor behavior against the HA design. The relevant action is: Check whether GRES is paired with the intended GR or NSR support and verify protocol state.

Question 443

An eBGP peer sends frequent KEEPALIVEs but the operator assumes this proves the best route is installed. Which test result would best confirm a successful fix?

  1. Closeout evidence: The session reaches Established only with the documented correct peer AS.
  2. Acceptance check: Only approved customer prefixes enter the provider's active routing table.
  3. The test confirms that both neighbor state and selected prefix route evidence are verified independently.
  4. Expected observation: The routing table exposes the selection reason and the intended route is installed.

Explanation

Correct Answer

C:

The selected response implements the principle that an Established BGP session can exist with zero accepted routes or unusable next hops. The engineer should separate session liveness from prefix acceptance and RIB installation. Successful confirmation means: Both neighbor state and selected prefix route evidence are verified independently.

Incorrect Answers

A:

The alternative addresses a remote BGP neighbor uses a different AS number than configured and the session fails during OPEN negotiation, not the present root cause. Here the selected correction must reflect an Established BGP session can exist with zero accepted routes or unusable next hops. Test for: Both neighbor state and selected prefix route evidence are verified independently.

B:

This answer would be more suitable when a new peer sends more customer routes than expected and the team assumes BGP automatically filters unrelated prefixes, where the corrective action is to create explicit import policy and prefix limits aligned to customer contracts. The failure here is different: An Established BGP session can exist with zero accepted routes or unusable next hops. Required validation: Both neighbor state and selected prefix route evidence are verified independently.

D:

Receiving topology data does not guarantee a route becomes active and installed describes a neighboring protocol concern. In this case the controlling fact is an Established BGP session can exist with zero accepted routes or unusable next hops. A correct remediation would separate session liveness from prefix acceptance and RIB installation and demonstrate: Both neighbor state and selected prefix route evidence are verified independently.

Question 444

A provider configures an IPv6 static route but assumes IPv4 ARP will resolve its IPv6 neighbor. Which post-change observation most strongly confirms the correction?

  1. Verification result: The neighbor cache resolves the IPv6 next hop and traffic passes.
  2. Closeout evidence: The IPv6 FIB resolves the intended next hop and a test packet crosses the link.
  3. Acceptance check: The intended IPv6 neighbor and destination routes appear and traffic succeeds.
  4. The test confirms that both address families display their expected prefixes through the same stable topology.

Explanation

Correct Answer

A:

This option addresses the stated case rather than another networking issue. Principle: IPv6 link-layer neighbor resolution uses ICMPv6 Neighbor Discovery. Remedy: Distinguish IPv6 Neighbor Discovery from IPv4 ARP. Proof: The neighbor cache resolves the IPv6 next hop and traffic passes.

Incorrect Answers

B:

This response would target a different source scenario: A router has an IPv6 default route but no usable next-hop reachability on the egress link. It cannot establish the current acceptance requirement, which is: The neighbor cache resolves the IPv6 next hop and traffic passes. The relevant action is: Distinguish IPv6 Neighbor Discovery from IPv4 ARP.

C:

Validate IPv6 addressing, neighbor discovery and inet6 routing separately is a relevant step for the separate scenario in which a new Junos edge router can ping IPv4 customers but cannot route IPv6 traffic to the same site. It does not directly fix this case. Instead distinguish IPv6 Neighbor Discovery from IPv4 ARP; verify: The neighbor cache resolves the IPv6 next hop and traffic passes.

D:

The alternative addresses iPv4 IS-IS routing works but IPv6 routes do not appear on a dual-stack backbone, not the present root cause. Here the selected correction must reflect iPv6 link-layer neighbor resolution uses ICMPv6 Neighbor Discovery. Test for: The neighbor cache resolves the IPv6 next hop and traffic passes.

Question 445

An OSPF packet capture shows Link State Updates but the route remains hidden from the active table. What is the most defensible network engineering correction?

  1. Corrective action: Verify compatible network and Hello parameters including mask where applicable.
  2. Apply this control: Review the passive-interface configuration and required active neighbor links.
  3. Remediation: Compare received LSAs with route selection, area eligibility and next-hop resolution.
  4. Recommended change: Verify recursive next-hop reachability before relying on the static route.

Explanation

Correct Answer

C:

Underlying cause: Receiving topology data does not guarantee a route becomes active and installed. Corrective action: compare received LSAs with route selection, area eligibility and next-hop resolution. Verify the outcome: The routing table exposes the selection reason and the intended route is installed.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is oSPF network-type and Hello compatibility can prevent adjacency formation, while this scenario depends on receiving topology data does not guarantee a route becomes active and installed. Verify the correction with: The routing table exposes the selection reason and the intended route is installed.

B:

Passive OSPF interfaces can advertise networks without forming neighbors on that interface describes a neighboring protocol concern. In this case the controlling fact is receiving topology data does not guarantee a route becomes active and installed. A correct remediation would compare received LSAs with route selection, area eligibility and next-hop resolution and demonstrate: The routing table exposes the selection reason and the intended route is installed.

D:

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 received LSAs with route selection, area eligibility and next-hop resolution. The required observed result is: The routing table exposes the selection reason and the intended route is installed.

Question 446

A VLAN provides local host connectivity but hosts cannot reach a different IP subnet through the bridge domain. What is the primary routing or switching concept illustrated?

  1. Protocol behavior: Layer 2 bridging does not by itself provide IP intersubnet routing.
  2. Underlying principle: Spanning tree prevents forwarding loops by selecting a loop-free active topology.
  3. Root design issue: Ethernet forwarding uses bridge-domain context rather than arbitrary IP-route matching.
  4. The governing rule is: Untagged frame classification is local to the receiving interface.

Explanation

Correct Answer

A:

Correct diagnosis: Layer 2 bridging does not by itself provide IP intersubnet routing. The appropriate action is: Deploy or validate an integrated routing and bridging L3 interface and gateway. The follow-up evidence required is: A test host reaches its gateway and an authorized remote subnet through IRB.

Incorrect Answers

B:

The alternative addresses a Layer 2 ring floods broadcast frames repeatedly after an extra cable is connected, not the present root cause. Here the selected correction must reflect layer 2 bridging does not by itself provide IP intersubnet routing. Test for: A test host reaches its gateway and an authorized remote subnet through IRB.

C:

This answer would be more suitable when a port belongs to a VLAN but traffic to a remote site is forwarded through a different bridge domain, where the corrective action is to trace frame classification and virtual-switch bridge-domain association. The failure here is different: Layer 2 bridging does not by itself provide IP intersubnet routing. Required validation: A test host reaches its gateway and an authorized remote subnet through IRB.

D:

This option overlooks the decisive condition. Its supporting principle is untagged frame classification is local to the receiving interface, while this scenario depends on layer 2 bridging does not by itself provide IP intersubnet routing. Verify the correction with: A test host reaches its gateway and an authorized remote subnet through IRB.

Question 447

A provider router has a static route for a customer prefix but its configured next hop is not reachable through any active route. What is the primary routing or switching concept illustrated?

  1. The key distinction is: Operational route troubleshooting starts with active state and resolution evidence.
  2. Protocol behavior: BGP sessions require sustained TCP connectivity independent of physical interface health.
  3. Underlying principle: A discard summary can prevent loops but can blackhole traffic when reachability assumptions are wrong.
  4. Root design issue: A configured static route need not become usable forwarding state when its next hop cannot resolve.

Explanation

Correct Answer

D:

Underlying cause: A configured static route need not become usable forwarding state when its next hop cannot resolve. Corrective action: verify recursive next-hop reachability before relying on the static route. Verify the outcome: A route lookup shows an active reachable next hop and traffic reaches the customer.

Incorrect Answers

A:

The proposed principle concerns another network fault: Operational route troubleshooting starts with active state and resolution evidence. Here, a configured static route need not become usable forwarding state when its next hop cannot resolve. The most direct correction is to verify recursive next-hop reachability before relying on the static route, confirmed by a route lookup shows an active reachable next hop and traffic reaches the customer.

B:

That result would be useful for a different failure, namely: An EBGP peer drops repeatedly after a firewall change despite clean interface counters. The current case specifically calls for: Verify recursive next-hop reachability before relying on the static route. The required observed result is: A route lookup shows an active reachable next hop and traffic reaches the customer.

C:

This response would target a different source scenario: A static discard route intended as a summary safety mechanism becomes the only active route after customer specifics disappear. It cannot establish the current acceptance requirement, which is: A route lookup shows an active reachable next hop and traffic reaches the customer. The relevant action is: Verify recursive next-hop reachability before relying on the static route.

Question 448

A Junos router shows no IS-IS adjacency after a circuit migration though the interface is physically up. Which evidence would justify closing this troubleshooting case?

  1. Closeout evidence: Both address families display their expected prefixes through the same stable topology.
  2. Acceptance check: The planned ABR topology provides verified interarea reachability.
  3. The test confirms that the forwarding route follows the lowest intended metric path.
  4. Expected observation: The corrected circuit shows the expected neighbor and link-state entries.

Explanation

Correct Answer

D:

Because an operational interface is not evidence of matching IS-IS protocol configuration, the best response is to inspect IS-IS interface enablement, levels, area identifiers and link type. A reviewer can close the technical case only after confirming that the corrected circuit shows the expected neighbor and link-state entries.

Incorrect Answers

A:

This answer would be more suitable when iPv4 IS-IS routing works but IPv6 routes do not appear on a dual-stack backbone, where the corrective action is to check the IPv6 family configuration and advertised reachability rather than rebuilding IPv4 adjacency. The failure here is different: An operational interface is not evidence of matching IS-IS protocol configuration. Required validation: The corrected circuit shows the expected neighbor and link-state entries.

B:

This option overlooks the decisive condition. Its supporting principle is multi-area OSPF design requires attention to backbone connectivity, while this scenario depends on an operational interface is not evidence of matching IS-IS protocol configuration. Verify the correction with: The corrected circuit shows the expected neighbor and link-state entries.

C:

IS-IS path selection is based on link-state topology and metrics describes a neighboring protocol concern. In this case the controlling fact is an operational interface is not evidence of matching IS-IS protocol configuration. A correct remediation would inspect IS-IS interface enablement, levels, area identifiers and link type and demonstrate: The corrected circuit shows the expected neighbor and link-state entries.

Question 449

A Layer 2 ring floods broadcast frames repeatedly after an extra cable is connected. Which root-cause explanation and corrective action fit the case?

  1. Diagnosis: MSTP can group VLANs into multiple spanning-tree instances under shared region parameters. Action: Evaluate MSTP instances and explicit VLAN-to-instance mapping.
  2. Explanation: Provider outer VLAN classification must preserve tenant isolation. Repair: Assign distinct service encapsulation and verify edge translation rules.
  3. Fault mechanism: Spanning tree prevents forwarding loops by selecting a loop-free active topology. Remediation: Enable the appropriate spanning-tree protection and verify the blocked redundant path.
  4. Root issue: Customer control traffic must not displace the authorized provider root. Correction: Apply supported root protection at the appropriate customer-facing boundary.

Explanation

Correct Answer

C:

The critical observation is: Spanning tree prevents forwarding loops by selecting a loop-free active topology. Correct it by taking this action: Enable the appropriate spanning-tree protection and verify the blocked redundant path. Confirm the outcome with: A topology test leaves one redundant path nonforwarding and traffic remains reachable.

Incorrect Answers

A:

This response would target a different source scenario: A data center needs separate spanning trees for VLAN groupings but the plan uses a single root for every VLAN with no design review. It cannot establish the current acceptance requirement, which is: A topology test leaves one redundant path nonforwarding and traffic remains reachable. The relevant action is: Enable the appropriate spanning-tree protection and verify the blocked redundant path.

B:

Assign distinct service encapsulation and verify edge translation rules is a relevant step for the separate scenario in which a Q-in-Q customer service leaks traffic between two tenants after the outer service VLAN is reused incorrectly. It does not directly fix this case. Instead enable the appropriate spanning-tree protection and verify the blocked redundant path; verify: A topology test leaves one redundant path nonforwarding and traffic remains reachable.

D:

This answer would be more suitable when a provider STP domain changes root when a customer sends superior BPDUs from an access port, where the corrective action is to apply supported root protection at the appropriate customer-facing boundary. The failure here is different: Spanning tree prevents forwarding loops by selecting a loop-free active topology. Required validation: A topology test leaves one redundant path nonforwarding and traffic remains reachable.

Question 450

An equal-cost path test sends nearly all flows across one member while both links remain operational. What operational check demonstrates that the intended outcome occurred?

  1. Expected observation: A negative test proves the unrelated customer prefix is absent from the target table.
  2. Verification result: The route is accepted only after the AS-path design is corrected.
  3. Closeout evidence: A documented multi-flow test matches the configured distribution policy.
  4. Acceptance check: The tenant-specific lookup resolves and the same source-based test reaches its destination.

Explanation

Correct Answer

C:

Correct diagnosis: Load sharing should be evaluated with relevant flows rather than one ping stream. The appropriate action is: Validate forwarding load-sharing configuration and run representative multi-flow traffic. The follow-up evidence required is: A documented multi-flow test matches the configured distribution policy.

Incorrect Answers

A:

Route redistribution must be intentionally scoped to prevent cross-tenant leakage describes a neighboring protocol concern. In this case the controlling fact is load sharing should be evaluated with relevant flows rather than one ping stream. A correct remediation would validate forwarding load-sharing configuration and run representative multi-flow traffic and demonstrate: A documented multi-flow test matches the configured distribution policy.

B:

The proposed principle concerns another network fault: BGP AS-path information can prevent routes from looping into an AS. Here, load sharing should be evaluated with relevant flows rather than one ping stream. The most direct correction is to validate forwarding load-sharing configuration and run representative multi-flow traffic, confirmed by a documented multi-flow test matches the configured distribution policy.

D:

This response would target a different source scenario: A provider PE can ping a customer in the master instance but probes in the tenant routing instance fail. It cannot establish the current acceptance requirement, which is: A documented multi-flow test matches the configured distribution policy. The relevant action is: Validate forwarding load-sharing configuration and run representative multi-flow traffic.

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