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 44

Question 430

An operator accepts a source-address block as an ordinary next-hop network even though the address is classified as martian. Which root-cause explanation and corrective action fit the case?

  1. Cause: Address validity and martian filtering affect which route sources are considered acceptable. Response: Review martian-address treatment and justify any carefully scoped exception.
  2. 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.
  3. Explanation: Operational route troubleshooting starts with active state and resolution evidence. Repair: Inspect the configuration, active route state and next-hop reachability before changing preference.
  4. 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.

Explanation

Correct Answer

A:

Correct diagnosis: Address validity and martian filtering affect which route sources are considered acceptable. The appropriate action is: Review martian-address treatment and justify any carefully scoped exception. The follow-up evidence required is: The rejected address remains excluded or a documented narrowly scoped exception is applied.

Incorrect Answers

B:

The alternative addresses a provider router has a static route for a customer prefix but its configured next hop is not reachable through any active route, not the present root cause. Here the selected correction must reflect address validity and martian filtering affect which route sources are considered acceptable. Test for: The rejected address remains excluded or a documented narrowly scoped exception is applied.

C:

This answer would be more suitable when after a maintenance window a configured customer static prefix is missing from active routes despite no syntax errors, where the corrective action is to inspect the configuration, active route state and next-hop reachability before changing preference. The failure here is different: Address validity and martian filtering affect which route sources are considered acceptable. Required validation: The rejected address remains excluded or a documented narrowly scoped exception is applied.

D:

This option overlooks the decisive condition. Its supporting principle is disabling loop prevention can introduce persistent interdomain routing loops, 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.

Question 431

A carrier attachment must not allow a customer switch to become the provider's root bridge. Which evidence would justify closing this troubleshooting case?

  1. The test confirms that a topology test leaves one redundant path nonforwarding and traffic remains reachable.
  2. Expected observation: A superior BPDU test does not move the approved provider root.
  3. Verification result: A superior BPDU test preserves the intended root with a logged protective state.
  4. Closeout evidence: A planned switchover test documents forwarding and neighbor behavior against the HA design.

Explanation

Correct Answer

B:

The critical observation is: Root protection can prevent undesired superior-root claims from changing root placement. Correct it by taking this action: Review root protection at the provider-facing boundary. Confirm the outcome with: A superior BPDU test does not move the approved provider root.

Incorrect Answers

A:

The proposed principle concerns another network fault: Spanning tree prevents forwarding loops by selecting a loop-free active topology. Here, root protection can prevent undesired superior-root claims from changing root placement. The most direct correction is to review root protection at the provider-facing boundary, confirmed by a superior BPDU test does not move the approved provider root.

C:

This response would target a different source scenario: A provider STP domain changes root when a customer sends superior BPDUs from an access port. It cannot establish the current acceptance requirement, which is: A superior BPDU test does not move the approved provider root. The relevant action is: Review root protection at the provider-facing boundary.

D:

Check whether GRES is paired with the intended GR or NSR support and verify protocol state is a relevant step for the separate scenario in which a Routing Engine switchover retains data-plane traffic briefly but causes OSPF adjacencies to restart. It does not directly fix this case. Instead review root protection at the provider-facing boundary; verify: A superior BPDU test does not move the approved provider root.

Question 432

A filter-based forwarding term matching one subscriber address also captures an overlapping shared services subnet. A reviewer requires a remedy and concrete test evidence. Which pairing fits?

  1. Implement: Create explicit import policy and prefix limits aligned to customer contracts. Verify: Only approved customer prefixes enter the provider's active routing table.
  2. Control: Review martian-address treatment and justify any carefully scoped exception. Accepted result: The rejected address remains excluded or a documented narrowly scoped exception is applied.
  3. Action: Compare withdrawal and blackhole behavior under a lab failure before changing the safety route. Evidence: The test demonstrates loop prevention without advertising false service reachability.
  4. Repair: Tighten the filter match and verify the next-table lookup with explicit positive and negative examples. Check: Only the subscriber's approved traffic enters the alternate routing instance.

Explanation

Correct Answer

D:

Because overlapping address classification makes precise route-filter and policy terms essential, the best response is to tighten the filter match and verify the next-table lookup with explicit positive and negative examples. A reviewer can close the technical case only after confirming that only the subscriber's approved traffic enters the alternate routing instance.

Incorrect Answers

A:

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: Overlapping address classification makes precise route-filter and policy terms essential. Required validation: Only the subscriber's approved traffic enters the alternate routing instance.

B:

This option overlooks the decisive condition. Its supporting principle is address validity and martian filtering affect which route sources are considered acceptable, while this scenario depends on overlapping address classification makes precise route-filter and policy terms essential. Verify the correction with: Only the subscriber's approved traffic enters the alternate routing instance.

C:

Discard routes may intentionally bound routing loops while dynamic specifics converge describes a neighboring protocol concern. In this case the controlling fact is overlapping address classification makes precise route-filter and policy terms essential. A correct remediation would tighten the filter match and verify the next-table lookup with explicit positive and negative examples and demonstrate: Only the subscriber's approved traffic enters the alternate routing instance.

Question 433

An access switch forwards untagged traffic into VLAN 20 after a port is moved to VLAN 30. Which protocol behavior most directly determines the correct diagnosis?

  1. The governing rule is: VLAN reassignment must be verified in actual port classification.
  2. The key distinction is: Provider outer VLAN classification must preserve tenant isolation.
  3. Protocol behavior: Forwarding-plane continuity does not prove control-plane routing continuity.
  4. Underlying principle: Layer 2 bridging does not by itself provide IP intersubnet routing.

Explanation

Correct Answer

A:

Underlying cause: VLAN reassignment must be verified in actual port classification. Corrective action: check committed access VLAN settings and operational membership rather than relying on notes. Verify the outcome: The moved test port places incoming untagged frames only in VLAN 30.

Incorrect Answers

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 check committed access VLAN settings and operational membership rather than relying on notes; verify: The moved test port places incoming untagged frames only in VLAN 30.

C:

The alternative addresses a Routing Engine switchover retains data-plane traffic briefly but causes OSPF adjacencies to restart, not the present root cause. Here the selected correction must reflect vLAN reassignment must be verified in actual port classification. Test for: The moved test port places incoming untagged frames only in VLAN 30.

D:

This answer would be more suitable when a VLAN provides local host connectivity but hosts cannot reach a different IP subnet through the bridge domain, where the corrective action is to deploy or validate an integrated routing and bridging L3 interface and gateway. The failure here is different: VLAN reassignment must be verified in actual port classification. Required validation: The moved test port places incoming untagged frames only in VLAN 30.

Question 434

A new redundant uplink produces a broadcast storm on an access VLAN. What assessment accurately links the fault to its correction?

  1. Diagnosis: Loop prevention depends on compatible STP participation across redundant Ethernet links. Action: Inspect STP state and enable the approved spanning-tree protocol for that bridge domain.
  2. Explanation: MSTP can group VLANs into multiple spanning-tree instances under shared region parameters. Repair: Evaluate MSTP instances and explicit VLAN-to-instance mapping.
  3. Fault mechanism: Protective edge-port shutdown is evidence of BPDU policy enforcement. Remediation: Verify the BPDU protection event and remove the unauthorized bridge rather than blindly disabling safeguards.
  4. Root issue: Layer 2 bridging does not by itself provide IP intersubnet routing. Correction: Deploy or validate an integrated routing and bridging L3 interface and gateway.

Explanation

Correct Answer

A:

Because loop prevention depends on compatible STP participation across redundant Ethernet links, the best response is to inspect STP state and enable the approved spanning-tree protocol for that bridge domain. A reviewer can close the technical case only after confirming that the ring converges with no forwarding loop and sustained connectivity.

Incorrect Answers

B:

The proposed principle concerns another network fault: MSTP can group VLANs into multiple spanning-tree instances under shared region parameters. Here, loop prevention depends on compatible STP participation across redundant Ethernet links. The most direct correction is to inspect STP state and enable the approved spanning-tree protocol for that bridge domain, confirmed by the ring converges with no forwarding loop and sustained connectivity.

C:

That result would be useful for a different failure, namely: A customer plugs a small unmanaged switch into a protected edge port and the port disables as soon as BPDUs arrive. The current case specifically calls for: Inspect STP state and enable the approved spanning-tree protocol for that bridge domain. The required observed result is: The ring converges with no forwarding loop and sustained connectivity.

D:

This response would target a different source scenario: A VLAN provides local host connectivity but hosts cannot reach a different IP subnet through the bridge domain. It cannot establish the current acceptance requirement, which is: The ring converges with no forwarding loop and sustained connectivity. The relevant action is: Inspect STP state and enable the approved spanning-tree protocol for that bridge domain.

Question 435

An operator sends a multicast routing-protocol packet over a GRE tunnel and assumes all physical transit routers must process the inner multicast. Which change best corrects the failure without losing the intended design?

  1. Corrective action: Review tunnel identifiers, endpoint uniqueness and supported platform demultiplexing.
  2. Apply this control: Distinguish the inner routed payload from outer unicast encapsulation.
  3. Remediation: Collect hop-local LFIB, label forwarding and interface counters along the LSP.
  4. Recommended change: Test effective MTU and path MTU discovery across the encapsulated route.

Explanation

Correct Answer

B:

Underlying cause: A tunnel can carry inner packet types over an underlay forwarding only the outer header. Corrective action: distinguish the inner routed payload from outer unicast encapsulation. Verify the outcome: Underlay traces show the outer endpoint traffic without transit processing of inner routes.

Incorrect Answers

A:

The alternative addresses two GRE tunnels share source and destination addresses while the design assumes ordinary routing will distinguish the services automatically, not the present root cause. Here the selected correction must reflect a tunnel can carry inner packet types over an underlay forwarding only the outer header. Test for: Underlay traces show the outer endpoint traffic without transit processing of inner routes.

C:

This option overlooks the decisive condition. Its supporting principle is end-to-end signaling state alone cannot pinpoint a data-plane label failure, 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:

GRE encapsulation overhead can expose MTU blackholes for larger payloads 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 436

An operator changes MED and sees no route change because the target AS prioritizes other attributes. What operational check demonstrates that the intended outcome occurred?

  1. The test confirms that a shared stable topology produces consistent path computation.
  2. Expected observation: Both neighbor state and selected prefix route evidence are verified independently.
  3. Verification result: An unwanted looped route is rejected in a lab before production change.
  4. Closeout evidence: A captured received-path comparison explains which attribute selected the route.

Explanation

Correct Answer

D:

Correct diagnosis: MED is not guaranteed to override local policy or earlier attributes. The appropriate action is: Compare MED use with actual prior BGP decision attributes and neighbor policy. The follow-up evidence required is: A captured received-path comparison explains which attribute selected the route.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A site sees different OSPF routes after a topology edit and declares the protocol failed without checking LSDB consistency. 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.

B:

This response would target a different source scenario: An eBGP peer sends frequent KEEPALIVEs but the operator assumes this proves the best route is installed. 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.

C:

Restore standard AS-path checks and review any justified exception with design authority is a relevant step for the separate scenario in which a provider accepts a route with its own AS in the received path after a risky bypass of loop prevention. 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.

Question 437

A provider PE can ping a customer in the master instance but probes in the tenant routing instance fail. What assessment accurately links the fault to its correction?

  1. Fault mechanism: Overlapping address classification makes precise route-filter and policy terms essential. Remediation: Tighten the filter match and verify the next-table lookup with explicit positive and negative examples.
  2. Root issue: Aggregation can hide individual component failures if advertisement policy is not controlled. Correction: Distinguish aggregate reachability from specific-route forwarding and test loss of component routes.
  3. Cause: BGP OPEN negotiation includes AS identity that must match peering intent. Response: Confirm the configured local and peer AS values with the authoritative design.
  4. Diagnosis: Instance-aware troubleshooting prevents a successful master-table probe from masking tenant isolation issues. Action: Run route and connectivity checks in the explicitly intended routing instance.

Explanation

Correct Answer

D:

The selected response implements the principle that instance-aware troubleshooting prevents a successful master-table probe from masking tenant isolation issues. The engineer should run route and connectivity checks in the explicitly intended routing instance. Successful confirmation means: The tenant-specific lookup resolves and the same source-based test reaches its destination.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is overlapping address classification makes precise route-filter and policy terms essential, while this scenario depends on instance-aware troubleshooting prevents a successful master-table probe from masking tenant isolation issues. Verify the correction with: The tenant-specific lookup resolves and the same source-based test reaches its destination.

B:

Aggregation can hide individual component failures if advertisement policy is not controlled describes a neighboring protocol concern. In this case the controlling fact is instance-aware troubleshooting prevents a successful master-table probe from masking tenant isolation issues. A correct remediation would run route and connectivity checks in the explicitly intended routing instance and demonstrate: The tenant-specific lookup resolves and the same source-based test reaches its destination.

C:

The proposed principle concerns another network fault: BGP OPEN negotiation includes AS identity that must match peering intent. Here, instance-aware troubleshooting prevents a successful master-table probe from masking tenant isolation issues. The most direct correction is to run route and connectivity checks in the explicitly intended routing instance, confirmed by the tenant-specific lookup resolves and the same source-based test reaches its destination.

Question 438

An MPLS service fails after penultimate-hop popping is changed without reviewing the egress disposition. Which change best corrects the failure without losing the intended design?

  1. Remediation: Recognize penultimate-hop popping as an allowed LSP forwarding behavior.
  2. Recommended change: Verify the label action and egress handling for the intended service stack.
  3. Next step: Check transport reachability, LDP session state and the relevant IGP routes.
  4. Corrective action: Validate forwarding load-sharing configuration and run representative multi-flow traffic.

Explanation

Correct Answer

B:

This option addresses the stated case rather than another networking issue. Principle: Incorrect label removal can expose payload handling that the egress does not expect. Remedy: Verify the label action and egress handling for the intended service stack. Proof: A traced packet arrives at egress with the correct remaining stack or payload.

Incorrect Answers

A:

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 verify the label action and egress handling for the intended service stack; verify: A traced packet arrives at egress with the correct remaining stack or payload.

C:

This answer would be more suitable when a provider's LDP neighbors disappear after an IGP outage while physical links remain up, where the corrective action is to check transport reachability, LDP session state and the relevant IGP routes. The failure here is different: Incorrect label removal can expose payload handling that the egress does not expect. Required validation: A traced packet arrives at egress with the correct remaining stack or payload.

D:

This option overlooks the decisive condition. Its supporting principle is load sharing should be evaluated with relevant flows rather than one ping stream, while this scenario depends on incorrect label removal can expose payload handling that the egress does not expect. Verify the correction with: A traced packet arrives at egress with the correct remaining stack or payload.

Question 439

A new Junos edge router can ping IPv4 customers but cannot route IPv6 traffic to the same site. Which cause-and-remedy pairing reflects the observed problem?

  1. Diagnosis: Tunnel identification and routing-instance separation must be explicit in overlapping designs. Action: Review tunnel identifiers, endpoint uniqueness and supported platform demultiplexing.
  2. Explanation: IPv4 operational success does not prove IPv6 forwarding configuration. Repair: Validate IPv6 addressing, neighbor discovery and inet6 routing separately.
  3. Fault mechanism: IPv6 link-layer neighbor resolution uses ICMPv6 Neighbor Discovery. Remediation: Distinguish IPv6 Neighbor Discovery from IPv4 ARP.
  4. Root issue: Neighbor establishment is distinct from prefix advertisement and installation. Correction: Check OSPFv3 family enablement, LSAs and routing-policy route acceptance.

Explanation

Correct Answer

B:

The critical observation is: IPv4 operational success does not prove IPv6 forwarding configuration. Correct it by taking this action: Validate IPv6 addressing, neighbor discovery and inet6 routing separately. Confirm the outcome with: The intended IPv6 neighbor and destination routes appear and traffic succeeds.

Incorrect Answers

A:

The proposed principle concerns another network fault: Tunnel identification and routing-instance separation must be explicit in overlapping designs. Here, iPv4 operational success does not prove IPv6 forwarding configuration. The most direct correction is to validate IPv6 addressing, neighbor discovery and inet6 routing separately, confirmed by the intended IPv6 neighbor and destination routes appear and traffic succeeds.

C:

This response would target a different source scenario: A provider configures an IPv6 static route but assumes IPv4 ARP will resolve its IPv6 neighbor. 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.

D:

Check OSPFv3 family enablement, LSAs and routing-policy route acceptance is a relevant step for the separate scenario in which after enabling OSPFv3 a provider sees IPv6 neighbors but no remote IPv6 customer prefixes. It does not directly fix this case. Instead validate IPv6 addressing, neighbor discovery and inet6 routing separately; verify: The intended IPv6 neighbor and destination routes appear and traffic succeeds.

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.

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