Pass Juniper JN0-364 Exam in First Attempt Easily
Real Juniper JN0-364 Exam Questions, Accurate & Verified Answers As Experienced in the Actual Test!

Verified by experts

JN0-364 Premium File

  • 69 Questions & Answers
  • Last Update: Nov 4, 2026
$69.99 $76.99

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

Question 40

A support escalation at Crestpoint Research describes: A peer presents a route for an address block treated as martian by the platform; engineers mistakenly troubleshoot export communities rather than the fundamental invalid-prefix classification. Where should the Junos operator look first for decisive evidence?

  1. Inspect route next-hop eligibility and the forwarding-table route for that prefix, then check the load-balancing policy and counters per next hop.
  2. Inspect contributor activity, the generate configuration and generated default in the RIB while deliberately withdrawing and restoring the qualifying contributor.
  3. Inspect the RIB group table list and attached protocols/interfaces, then verify the affected route in both RIBs and check its resolution.
  4. Check the prefix classification, `show route` reason/state and martian configuration before changing protocol preference or BGP export policy.

Correct answer: D

Explanation of each choice

A.

This check may help with another root cause, for example: A provider turns on ECMP routing but the forwarding table still resolves customer flows to just one path and operators mistake RIB entries for per-flow distribution. It does not test the first failed condition; start with: Check the prefix classification, `show route` reason/state and martian configuration before changing protocol preference or BGP export policy.

B.

That evidence could be normal while the reported defect persists. It is aimed at: An edge should install a conditional default only while a qualifying backbone route is reachable, but an unconditional static default currently hides an upstream outage. Instead inspect: Check the prefix classification, `show route` reason/state and martian configuration before changing protocol preference or BGP export policy.

C.

The check diagnoses a different layer of service. Its source issue is: A services router has a valid connected path in the primary instance yet a policy-dependent secondary RIB never receives it after a routing-instance refactor. The relevant initial check is: Check the prefix classification, `show route` reason/state and martian configuration before changing protocol preference or BGP export policy.

D.

Check the prefix classification, `show route` reason/state and martian configuration before changing protocol preference or BGP export policy. Martian filtering precedes ordinary best-path preference and cannot be corrected by simply setting a lower route metric.

Question 41

During a Junos network change at Eastvale MetroNet, the engineer observes: Two wholesale customers use overlapping IPv4 ranges and route lookups occur in the default table, causing one tenant's prefix to shadow the other's. Which remediation most directly fixes the described problem?

  1. Configure and validate the Junos aggregate route and its contributing more-specific active routes, applying appropriate export policy for the intended summary.
  2. Place customer interfaces and their routing policy in the intended separate routing instance, and validate lookups in that instance's RIB.
  3. Build a narrowly matched firewall filter that selects the intended forwarding routing instance and verify the target instance has the necessary route and next-hop resolution.
  4. Use a policy-controlled generated route that becomes active only with the intended qualifying active contributing route, rather than an unconditional default.

Correct answer: B

Explanation of each choice

A.

The other action is relevant when An edge advertises dozens of customer-specific routes instead of the intended summary, and the operations team wants to reduce external route-table size without creating an unsupported more-specific next hop. The current case instead requires: Place customer interfaces and their routing policy in the intended separate routing instance, and validate lookups in that instance's RIB. The distinction is: The defect is routing-table context; changing the prefix length or changing an unrelated OSPF cost would not enforce the needed tenant separation.

B.

Place customer interfaces and their routing policy in the intended separate routing instance, and validate lookups in that instance's RIB. The case-specific reason is: The defect is routing-table context; changing the prefix length or changing an unrelated OSPF cost would not enforce the needed tenant separation. A direct acceptance test is: Each tenant prefix is present in its own instance-specific routing table and traffic exits through that tenant's correct interface without cross-customer leakage.

C.

This action may apply to a different problem, for example: A packet class identified by source address needs to use a dedicated service routing table, but packets still follow the global destination-based path. It does not repair the stated failure boundary. The case-specific reason is: The defect is routing-table context; changing the prefix length or changing an unrelated OSPF cost would not enforce the needed tenant separation.

D.

The other action is relevant when An enterprise receives a transit path that should trigger a conditional route of last resort; when that contributor disappears the default must be removed to avoid a blackhole. The current case instead requires: Place customer interfaces and their routing policy in the intended separate routing instance, and validate lookups in that instance's RIB. The distinction is: The defect is routing-table context; changing the prefix length or changing an unrelated OSPF cost would not enforce the needed tenant separation.

Question 42

The Junos team at Eastvale MetroNet needs a success criterion for this defect: Two wholesale customers use overlapping IPv4 ranges and route lookups occur in the default table, causing one tenant's prefix to shadow the other's. Which observed result most precisely confirms the intended repair?

  1. Each tenant prefix is present in its own instance-specific routing table and traffic exits through that tenant's correct interface without cross-customer leakage.
  2. The forwarding table contains the intended set of usable equal-cost next hops and sampled independent flows use multiple paths without unexpected per-packet reordering.
  3. Only packets matching the defined steering terms are looked up in the intended forwarding table; nonmatching traffic stays on the default path.
  4. Traffic matching real more-specific routes is forwarded normally and packets matching only the protective summary are dropped or rejected as explicitly specified.

Correct answer: A

Explanation of each choice

A.

Each tenant prefix is present in its own instance-specific routing table and traffic exits through that tenant's correct interface without cross-customer leakage. The defect is routing-table context; changing the prefix length or changing an unrelated OSPF cost would not enforce the needed tenant separation.

B.

That check proves something else, such as: A provider turns on ECMP routing but the forwarding table still resolves customer flows to just one path and operators mistake RIB entries for per-flow distribution. It could pass while the stated problem remains. The targeted evidence here is: Each tenant prefix is present in its own instance-specific routing table and traffic exits through that tenant's correct interface without cross-customer leakage.

C.

This would be valid for another situation: A packet class identified by source address needs to use a dedicated service routing table, but packets still follow the global destination-based path. It does not establish that the failing boundary in this scenario works; verify: Each tenant prefix is present in its own instance-specific routing table and traffic exits through that tenant's correct interface without cross-customer leakage.

D.

The observation confirms a different component's behavior. Its source context is: An operations runbook treats discard and reject forwarding actions as interchangeable and fails to explain the expected behavior for unmatched packets. In this case the success criterion is: Each tenant prefix is present in its own instance-specific routing table and traffic exits through that tenant's correct interface without cross-customer leakage.

Question 43

While analyzing a service failure at Eastvale MetroNet, the following is observed: Two wholesale customers use overlapping IPv4 ranges and route lookups occur in the default table, causing one tenant's prefix to shadow the other's. Which mechanism best explains the underlying control-plane or forwarding behavior?

  1. Junos routing instances maintain distinct routing-table contexts so overlapping customer prefixes can be resolved without sharing the same default RIB.
  2. A static route remains eligible based on configured next-hop resolution and route preference; dynamic protocols do not automatically repair an incorrectly pinned route.
  3. Filter-based forwarding applies a routing-instance lookup decision based on a firewall filter rather than relying only on the ordinary destination table.
  4. Martian addresses are prefixes considered invalid for ordinary routing and can be rejected independently of normal policy attribute preferences.

Correct answer: A

Explanation of each choice

A.

Junos routing instances maintain distinct routing-table contexts so overlapping customer prefixes can be resolved without sharing the same default RIB. The key distinction is: The defect is routing-table context; changing the prefix length or changing an unrelated OSPF cost would not enforce the needed tenant separation. Accordingly the remedy is: Place customer interfaces and their routing policy in the intended separate routing instance, and validate lookups in that instance's RIB.

B.

That principle belongs to a different service stage: A service edge was renumbered and its manually configured static next hop still points to the former address, blackholing one customer subnet despite healthy dynamic adjacencies. The directly relevant mechanism is: Junos routing instances maintain distinct routing-table contexts so overlapping customer prefixes can be resolved without sharing the same default RIB.

C.

That principle belongs to a different service stage: A packet class identified by source address needs to use a dedicated service routing table, but packets still follow the global destination-based path. The directly relevant mechanism is: Junos routing instances maintain distinct routing-table contexts so overlapping customer prefixes can be resolved without sharing the same default RIB.

D.

This explains a separate protocol behavior: A peer presents a route for an address block treated as martian by the platform; engineers mistakenly troubleshoot export communities rather than the fundamental invalid-prefix classification. In the current facts, the controlling mechanism is: Junos routing instances maintain distinct routing-table contexts so overlapping customer prefixes can be resolved without sharing the same default RIB.

Question 44

The following provider defect remains uncorrected at Eastvale MetroNet: Two wholesale customers use overlapping IPv4 ranges and route lookups occur in the default table, causing one tenant's prefix to shadow the other's. What is the most direct service or security risk of leaving it unresolved?

  1. The secondary routing process lacks required reachability or inadvertently imports unrelated routes if the RIB group is attached too broadly.
  2. Customer isolation fails and a lookup can select another tenant's similarly numbered prefix or inadvertently expose routing information.
  3. Traffic can bypass the required service path or reach a routing instance with no usable route, creating policy bypass or a blackhole.
  4. Invalid or reserved prefixes can pollute routing tables and create unexpected forwarding or route-leak behavior if exceptions are added without review.

Correct answer: B

Explanation of each choice

A.

It is a risk in another topology or protocol state: A provider expects selected interface routes from an underlay RIB to be available in a second table, but the secondary table has no copied routes. Here the most direct failure path is: Customer isolation fails and a lookup can select another tenant's similarly numbered prefix or inadvertently expose routing information.

B.

Customer isolation fails and a lookup can select another tenant's similarly numbered prefix or inadvertently expose routing information. The direct mitigation is: Place customer interfaces and their routing policy in the intended separate routing instance, and validate lookups in that instance's RIB.

C.

That consequence is more closely associated with another deficiency, such as: A packet class identified by source address needs to use a dedicated service routing table, but packets still follow the global destination-based path. The described fault instead exposes: Customer isolation fails and a lookup can select another tenant's similarly numbered prefix or inadvertently expose routing information.

D.

It is a risk in another topology or protocol state: A peer presents a route for an address block treated as martian by the platform; engineers mistakenly troubleshoot export communities rather than the fundamental invalid-prefix classification. Here the most direct failure path is: Customer isolation fails and a lookup can select another tenant's similarly numbered prefix or inadvertently expose routing information.

Question 45

A support escalation at Eastvale MetroNet describes: Two wholesale customers use overlapping IPv4 ranges and route lookups occur in the default table, causing one tenant's prefix to shadow the other's. Where should the Junos operator look first for decisive evidence?

  1. Identify the ingress logical interface's routing-instance membership and inspect the corresponding instance RIB and forwarding table, not just inet.0.
  2. Inspect route next-hop eligibility and the forwarding-table route for that prefix, then check the load-balancing policy and counters per next hop.
  3. Inspect the RIB group table list and attached protocols/interfaces, then verify the affected route in both RIBs and check its resolution.
  4. Inspect the precise prefix in the routing table and the resolved next-hop/forwarding entry, then compare the active static configuration with the working topology.

Correct answer: A

Explanation of each choice

A.

Identify the ingress logical interface's routing-instance membership and inspect the corresponding instance RIB and forwarding table, not just inet.0. The defect is routing-table context; changing the prefix length or changing an unrelated OSPF cost would not enforce the needed tenant separation.

B.

This check may help with another root cause, for example: A provider turns on ECMP routing but the forwarding table still resolves customer flows to just one path and operators mistake RIB entries for per-flow distribution. It does not test the first failed condition; start with: Identify the ingress logical interface's routing-instance membership and inspect the corresponding instance RIB and forwarding table, not just inet.0.

C.

That evidence could be normal while the reported defect persists. It is aimed at: A provider expects selected interface routes from an underlay RIB to be available in a second table, but the secondary table has no copied routes. Instead inspect: Identify the ingress logical interface's routing-instance membership and inspect the corresponding instance RIB and forwarding table, not just inet.0.

D.

The check diagnoses a different layer of service. Its source issue is: A service edge was renumbered and its manually configured static next hop still points to the former address, blackholing one customer subnet despite healthy dynamic adjacencies. The relevant initial check is: Identify the ingress logical interface's routing-instance membership and inspect the corresponding instance RIB and forwarding table, not just inet.0.

Question 46

The provider operations team at Bridgeway Cloud reports: A provider migrates a service into a separate virtual routing instance but tests only inet.0 and falsely concludes that the tenant route is absent. Which implementation decision best corrects the cause?

  1. Use a policy-controlled generated route that becomes active only with the intended qualifying active contributing route, rather than an unconditional default.
  2. Place customer interfaces and their routing policy in the intended separate routing instance, and validate lookups in that instance's RIB.
  3. Update or remove the stale static route and validate the intended reachable next hop and route preference before restoring forwarding.
  4. Confirm equal eligible next hops and apply the appropriate forwarding-table load-balancing policy, then verify actual forwarding next-hop groups and flow distribution.

Correct answer: B

Explanation of each choice

A.

This action may apply to a different problem, for example: An enterprise receives a transit path that should trigger a conditional route of last resort; when that contributor disappears the default must be removed to avoid a blackhole. It does not repair the stated failure boundary. The case-specific reason is: The defect is routing-table context; changing the prefix length or changing an unrelated OSPF cost would not enforce the needed tenant separation.

B.

Place customer interfaces and their routing policy in the intended separate routing instance, and validate lookups in that instance's RIB. The case-specific reason is: The defect is routing-table context; changing the prefix length or changing an unrelated OSPF cost would not enforce the needed tenant separation. A direct acceptance test is: Each tenant prefix is present in its own instance-specific routing table and traffic exits through that tenant's correct interface without cross-customer leakage.

C.

That would address a separate configuration fault: A service edge was renumbered and its manually configured static next hop still points to the former address, blackholing one customer subnet despite healthy dynamic adjacencies. This stem identifies a different cause, corrected by: Place customer interfaces and their routing policy in the intended separate routing instance, and validate lookups in that instance's RIB.

D.

This action may apply to a different problem, for example: Traffic to one equal-cost destination uses only a single next hop despite two active parallel paths and an approved traffic-sharing requirement. It does not repair the stated failure boundary. The case-specific reason is: The defect is routing-table context; changing the prefix length or changing an unrelated OSPF cost would not enforce the needed tenant separation.

Question 47

During a post-change check at Bridgeway Cloud, the original condition was: A provider migrates a service into a separate virtual routing instance but tests only inet.0 and falsely concludes that the tenant route is absent. What evidence would validate the corrected behavior?

  1. Traffic matching real more-specific routes is forwarded normally and packets matching only the protective summary are dropped or rejected as explicitly specified.
  2. Each tenant prefix is present in its own instance-specific routing table and traffic exits through that tenant's correct interface without cross-customer leakage.
  3. The route is treated according to the documented martian policy, and normal unicast routing is not unintentionally established for reserved or prohibited address space.
  4. The generated route appears while its qualifying active contributor is present and withdraws when the contributor is removed, with the next hop resolved as designed.

Correct answer: B

Explanation of each choice

A.

This would be valid for another situation: An operations runbook treats discard and reject forwarding actions as interchangeable and fails to explain the expected behavior for unmatched packets. It does not establish that the failing boundary in this scenario works; verify: Each tenant prefix is present in its own instance-specific routing table and traffic exits through that tenant's correct interface without cross-customer leakage.

B.

Each tenant prefix is present in its own instance-specific routing table and traffic exits through that tenant's correct interface without cross-customer leakage. The defect is routing-table context; changing the prefix length or changing an unrelated OSPF cost would not enforce the needed tenant separation.

C.

That check proves something else, such as: A peer presents a route for an address block treated as martian by the platform; engineers mistakenly troubleshoot export communities rather than the fundamental invalid-prefix classification. It could pass while the stated problem remains. The targeted evidence here is: Each tenant prefix is present in its own instance-specific routing table and traffic exits through that tenant's correct interface without cross-customer leakage.

D.

This would be valid for another situation: An edge should install a conditional default only while a qualifying backbone route is reachable, but an unconditional static default currently hides an upstream outage. It does not establish that the failing boundary in this scenario works; verify: Each tenant prefix is present in its own instance-specific routing table and traffic exits through that tenant's correct interface without cross-customer leakage.

Question 48

At Bridgeway Cloud, an engineer is asked to explain this case: A provider migrates a service into a separate virtual routing instance but tests only inet.0 and falsely concludes that the tenant route is absent. Which underlying routing or switching principle accounts for the appropriate solution?

  1. Filter-based forwarding applies a routing-instance lookup decision based on a firewall filter rather than relying only on the ordinary destination table.
  2. Junos route selection and export to the forwarding table are distinct; ECMP forwarding requires eligible paths and policy behavior that installs them.
  3. Junos routing instances maintain distinct routing-table contexts so overlapping customer prefixes can be resolved without sharing the same default RIB.
  4. A discard route silently drops packets; a reject route drops them while sending an unreachable response when supported, and longest-prefix matching still favors specifics.

Correct answer: C

Explanation of each choice

A.

That principle belongs to a different service stage: A provider's firewall filter counts customer steering matches yet tagged traffic goes to the ordinary next hop because the `then routing-instance` forwarding path was not verified. The directly relevant mechanism is: Junos routing instances maintain distinct routing-table contexts so overlapping customer prefixes can be resolved without sharing the same default RIB.

B.

This explains a separate protocol behavior: Traffic to one equal-cost destination uses only a single next hop despite two active parallel paths and an approved traffic-sharing requirement. In the current facts, the controlling mechanism is: Junos routing instances maintain distinct routing-table contexts so overlapping customer prefixes can be resolved without sharing the same default RIB.

C.

Junos routing instances maintain distinct routing-table contexts so overlapping customer prefixes can be resolved without sharing the same default RIB. The key distinction is: The defect is routing-table context; changing the prefix length or changing an unrelated OSPF cost would not enforce the needed tenant separation. Accordingly the remedy is: Place customer interfaces and their routing policy in the intended separate routing instance, and validate lookups in that instance's RIB.

D.

That principle belongs to a different service stage: A provider intends a protective summary for address space with sparse more-specific destinations but needs unmatched traffic to be dropped predictably rather than looped. The directly relevant mechanism is: Junos routing instances maintain distinct routing-table contexts so overlapping customer prefixes can be resolved without sharing the same default RIB.

Question 49

A risk assessment at Bridgeway Cloud identifies: A provider migrates a service into a separate virtual routing instance but tests only inet.0 and falsely concludes that the tenant route is absent. Which practical consequence is most specifically tied to this failure?

  1. Customer isolation fails and a lookup can select another tenant's similarly numbered prefix or inadvertently expose routing information.
  2. Invalid or reserved prefixes can pollute routing tables and create unexpected forwarding or route-leak behavior if exceptions are added without review.
  3. Unmatched traffic can loop or provoke inappropriate error traffic if the route's terminal next-hop behavior is not designed explicitly.
  4. Traffic for the specific prefix continues to follow the dead or incorrect next hop instead of recovering through an available alternate path.

Correct answer: A

Explanation of each choice

A.

Customer isolation fails and a lookup can select another tenant's similarly numbered prefix or inadvertently expose routing information. The direct mitigation is: Place customer interfaces and their routing policy in the intended separate routing instance, and validate lookups in that instance's RIB.

B.

It is a risk in another topology or protocol state: A routing policy change appears to accept a reserved loopback or multicast source as an ordinary Internet destination, and the team needs to separate policy bugs from invalid route treatment. Here the most direct failure path is: Customer isolation fails and a lookup can select another tenant's similarly numbered prefix or inadvertently expose routing information.

C.

The concern could occur elsewhere when An operations runbook treats discard and reject forwarding actions as interchangeable and fails to explain the expected behavior for unmatched packets. For the stated scenario, the immediate risk is: Customer isolation fails and a lookup can select another tenant's similarly numbered prefix or inadvertently expose routing information.

D.

That consequence is more closely associated with another deficiency, such as: A maintenance circuit has been retired but an old static route still directs a private customer prefix toward its unresponsive next hop, even while a learned backup route exists. The described fault instead exposes: Customer isolation fails and a lookup can select another tenant's similarly numbered prefix or inadvertently expose routing information.

Question 50

The on-call engineer at Bridgeway Cloud receives this fault report: A provider migrates a service into a separate virtual routing instance but tests only inet.0 and falsely concludes that the tenant route is absent. What initial check best isolates the actual failing protocol stage?

  1. Identify the ingress logical interface's routing-instance membership and inspect the corresponding instance RIB and forwarding table, not just inet.0.
  2. Inspect route next-hop eligibility and the forwarding-table route for that prefix, then check the load-balancing policy and counters per next hop.
  3. Inspect the RIB group table list and attached protocols/interfaces, then verify the affected route in both RIBs and check its resolution.
  4. Inspect contributor activity, the generate configuration and generated default in the RIB while deliberately withdrawing and restoring the qualifying contributor.

Correct answer: A

Explanation of each choice

A.

Identify the ingress logical interface's routing-instance membership and inspect the corresponding instance RIB and forwarding table, not just inet.0. The defect is routing-table context; changing the prefix length or changing an unrelated OSPF cost would not enforce the needed tenant separation.

B.

The check diagnoses a different layer of service. Its source issue is: Traffic to one equal-cost destination uses only a single next hop despite two active parallel paths and an approved traffic-sharing requirement. The relevant initial check is: Identify the ingress logical interface's routing-instance membership and inspect the corresponding instance RIB and forwarding table, not just inet.0.

C.

This check may help with another root cause, for example: A services router has a valid connected path in the primary instance yet a policy-dependent secondary RIB never receives it after a routing-instance refactor. It does not test the first failed condition; start with: Identify the ingress logical interface's routing-instance membership and inspect the corresponding instance RIB and forwarding table, not just inet.0.

D.

That evidence could be normal while the reported defect persists. It is aimed at: An edge should install a conditional default only while a qualifying backbone route is reachable, but an unconditional static default currently hides an upstream outage. Instead inspect: Identify the ingress logical interface's routing-instance membership and inspect the corresponding instance RIB and forwarding table, not just inet.0.

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

SPECIAL OFFER: GET 10% OFF
This is ONE TIME OFFER

You save
10%

Enter Your Email Address to Receive Your 10% Off Discount Code

SPECIAL OFFER: GET 10% OFF

You save
10%

Use Discount Code:

A confirmation link was sent to your e-mail.

Please check your mailbox for a message from support@examlabs.com and follow the directions.

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

Simply submit your email address below to get started with our interactive software demo of your free trial.

  • Realistic exam simulation and exam editor with preview functions
  • Whole exam in a single file with several different question types
  • Customizable exam-taking mode & detailed score reports