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 80

Question 790

An IRB interface is present but an operator assumes it creates a bridge domain automatically. What diagnosis and engineering response are most appropriate?

  1. Root issue: Forwarding-plane continuity does not prove control-plane routing continuity. Correction: Check whether GRES is paired with the intended GR or NSR support and verify protocol state.
  2. Cause: Layer 2 bridging does not by itself provide IP intersubnet routing. Response: Deploy or validate an integrated routing and bridging L3 interface and gateway.
  3. Diagnosis: Junos candidate configuration changes are not active until committed. Action: Compare candidate and committed configurations and confirm actual bridge membership.
  4. Explanation: Integrated routing bridges a defined L2 domain into an L3 interface when correctly associated. Repair: Verify VLAN or bridge-domain membership and its L3 IRB binding.

Explanation

Correct Answer

D:

This is the model-intended best choice because integrated routing bridges a defined L2 domain into an L3 interface when correctly associated. The targeted correction is to verify VLAN or bridge-domain membership and its L3 IRB binding. Validate it by observing that the bridge domain and IRB interface share the configured gateway context.

Incorrect Answers

A:

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 verify VLAN or bridge-domain membership and its L3 IRB binding; verify: The bridge domain and IRB interface share the configured gateway context.

B:

The alternative addresses a VLAN provides local host connectivity but hosts cannot reach a different IP subnet through the bridge domain, not the present root cause. Here the selected correction must reflect integrated routing bridges a defined L2 domain into an L3 interface when correctly associated. Test for: The bridge domain and IRB interface share the configured gateway context.

C:

This answer would be more suitable when a virtual switch forwarding issue persists because customer VLAN configuration was changed but never committed, where the corrective action is to compare candidate and committed configurations and confirm actual bridge membership. The failure here is different: Integrated routing bridges a defined L2 domain into an L3 interface when correctly associated. Required validation: The bridge domain and IRB interface share the configured gateway context.

Question 791

A network design assumes RSVP and LDP use identical path signaling and traffic engineering controls. What assessment accurately links the fault to its correction?

  1. Fault mechanism: Incorrect label removal can expose payload handling that the egress does not expect. Remediation: Verify the label action and egress handling for the intended service stack.
  2. Root issue: Route reflection relies on correct client boundaries and originator or cluster tracking. Correction: Review route-reflector client and cluster design, including loop-prevention attributes.
  3. Cause: An upstream LSR can remove a label before the egress in an appropriate PHP design. Response: Recognize penultimate-hop popping as an allowed LSP forwarding behavior.
  4. Diagnosis: RSVP-TE can signal explicit or constrained paths while ordinary LDP follows routing reachability. Action: Separate RSVP-signaled LSP functions from LDP label distribution.

Explanation

Correct Answer

D:

Underlying cause: RSVP-TE can signal explicit or constrained paths while ordinary LDP follows routing reachability. Corrective action: separate RSVP-signaled LSP functions from LDP label distribution. Verify the outcome: The chosen protocol establishes the intended type of LSP.

Incorrect Answers

A:

The proposed principle concerns another network fault: Incorrect label removal can expose payload handling that the egress does not expect. Here, rSVP-TE can signal explicit or constrained paths while ordinary LDP follows routing reachability. The most direct correction is to separate RSVP-signaled LSP functions from LDP label distribution, confirmed by the chosen protocol establishes the intended type of LSP.

B:

That result would be useful for a different failure, namely: A route reflector advertises routes to the wrong clients after a change in group membership. The current case specifically calls for: Separate RSVP-signaled LSP functions from LDP label distribution. The required observed result is: The chosen protocol establishes the intended type of LSP.

C:

This response would target a different source scenario: A penultimate router pops a transport label and the egress receives native IP even though the engineer expected a visible final outer label. It cannot establish the current acceptance requirement, which is: The chosen protocol establishes the intended type of LSP. The relevant action is: Separate RSVP-signaled LSP functions from LDP label distribution.

Question 792

A network operator assumes a GRE tunnel encrypts customer packets merely because they are encapsulated. Which technical distinction best describes the observed symptom?

  1. The governing rule is: GRE has no independent path if its outer transport becomes unreachable.
  2. The key distinction is: Tunnel interfaces depend on a working underlay path between endpoints.
  3. Protocol behavior: GRE by itself does not provide encryption or authenticated confidentiality.
  4. Underlying principle: A configured IPv6 static route still depends on reachable forwarding next hops.

Explanation

Correct Answer

C:

This option addresses the stated case rather than another networking issue. Principle: GRE by itself does not provide encryption or authenticated confidentiality. Remedy: Distinguish tunneling encapsulation from confidentiality protection. Proof: The security design adds an appropriate protected transport where needed.

Incorrect Answers

A:

This answer would be more suitable when a GRE tunnel over an IPv4 core stops passing traffic immediately after an underlay route withdraws, where the corrective action is to restore underlay endpoint reachability and then validate the inner tunnel route. The failure here is different: GRE by itself does not provide encryption or authenticated confidentiality. Required validation: The security design adds an appropriate protected transport where needed.

B:

This option overlooks the decisive condition. Its supporting principle is tunnel interfaces depend on a working underlay path between endpoints, while this scenario depends on gRE by itself does not provide encryption or authenticated confidentiality. Verify the correction with: The security design adds an appropriate protected transport where needed.

D:

The proposed principle concerns another network fault: A configured IPv6 static route still depends on reachable forwarding next hops. Here, gRE by itself does not provide encryption or authenticated confidentiality. The most direct correction is to distinguish tunneling encapsulation from confidentiality protection, confirmed by the security design adds an appropriate protected transport where needed.

Question 793

A router selects a route in one routing instance while the forwarding policy sends matching traffic into a different table. What should the operations engineer do first to address the stated fault?

  1. Apply this control: Separate route-selection and lookup-table changes and test each with candidate configuration.
  2. Remediation: Review filter-based forwarding classification and the intended next-table selection.
  3. Recommended change: Constrain redistribution and test route policy acceptance for the intended prefixes.
  4. Next step: Document the discard behavior and determine whether the aggregate should remain advertised.

Explanation

Correct Answer

B:

The selected response implements the principle that policy-based forwarding can select a routing table independently of the destination lookup in the ingress default table. The engineer should review filter-based forwarding classification and the intended next-table selection. Successful confirmation means: A trace of matching and nonmatching packets shows the approved lookup table.

Incorrect Answers

A:

This response would target a different source scenario: A policy adjustment changes both routing preference and forwarding instance selection in one unreviewed commit. It cannot establish the current acceptance requirement, which is: A trace of matching and nonmatching packets shows the approved lookup table. The relevant action is: Review filter-based forwarding classification and the intended next-table selection.

C:

The alternative addresses a provider exports an unexpectedly broad set of routes into OSPF after accepting a generic routing policy, not the present root cause. Here the selected correction must reflect policy-based forwarding can select a routing table independently of the destination lookup in the ingress default table. Test for: A trace of matching and nonmatching packets shows the approved lookup table.

D:

This answer would be more suitable when a static discard route intended as a summary safety mechanism becomes the only active route after customer specifics disappear, where the corrective action is to document the discard behavior and determine whether the aggregate should remain advertised. The failure here is different: Policy-based forwarding can select a routing table independently of the destination lookup in the ingress default table. Required validation: A trace of matching and nonmatching packets shows the approved lookup table.

Question 794

Two edge routers advertise one gateway service and an engineer expects both to be virtual master without a redundancy plan. Which evidence would justify closing this troubleshooting case?

  1. Expected observation: A controlled election yields the approved root with documented path changes.
  2. Verification result: Only the intended master forwards for the virtual gateway under steady state.
  3. Closeout evidence: An authorized switchover maintains bridge control state and service reachability.
  4. Acceptance check: The fault is visible and surviving members carry traffic within the approved limits.

Explanation

Correct Answer

B:

This is the model-intended best choice because vRRP provides a master and backup mechanism for a shared virtual default gateway. The targeted correction is to review VRRP virtual router roles, priority and failover behavior. Validate it by observing that only the intended master forwards for the virtual gateway under steady state.

Incorrect Answers

A:

Configuration intent must be verified against the actual elected spanning-tree root describes a neighboring protocol concern. In this case the controlling fact is vRRP provides a master and backup mechanism for a shared virtual default gateway. A correct remediation would review VRRP virtual router roles, priority and failover behavior and demonstrate: Only the intended master forwards for the virtual gateway under steady state.

C:

That result would be useful for a different failure, namely: An Ethernet service must retain bridge state during Routing Engine failover but only Layer 3 HA settings are considered. The current case specifically calls for: Review VRRP virtual router roles, priority and failover behavior. The required observed result is: Only the intended master forwards for the virtual gateway under steady state.

D:

This response would target a different source scenario: One LAG member fails silently and the service loses capacity even though the logical interface remains active. It cannot establish the current acceptance requirement, which is: Only the intended master forwards for the virtual gateway under steady state. The relevant action is: Review VRRP virtual router roles, priority and failover behavior.

Question 795

A BGP peer is stuck in Active after a maintenance window even though the remote address is configured. What operational check demonstrates that the intended outcome occurred?

  1. The test confirms that the TCP peering session reaches Established and remains stable.
  2. Expected observation: The approved route matches an accepting term and the denied route remains denied.
  3. Verification result: A neighbor advertising test shows precisely the allowed tagged prefixes.
  4. Closeout evidence: The neighbor states match expected DR roles and routing converges.

Explanation

Correct Answer

A:

The case turns on the distinction that neighbor state must be traced through transport before modifying route policy. Apply this concrete engineering step: Verify IP reachability, routing instance context, TCP transport and session authentication. An acceptable verification outcome is: The TCP peering session reaches Established and remains stable.

Incorrect Answers

B:

This answer would be more suitable when a BGP prefix remains rejected after an intended route filter update because an earlier term rejects it, where the corrective action is to evaluate policy terms in effective order and test matching routes. The failure here is different: Neighbor state must be traced through transport before modifying route policy. Required validation: The TCP peering session reaches Established and remains stable.

C:

This option overlooks the decisive condition. Its supporting principle is bGP group inheritance and policy direction govern which advertisements are modified, while this scenario depends on neighbor state must be traced through transport before modifying route policy. Verify the correction with: The TCP peering session reaches Established and remains stable.

D:

OSPF broadcast topology reduces unnecessary full adjacency mesh formation describes a neighboring protocol concern. In this case the controlling fact is neighbor state must be traced through transport before modifying route policy. A correct remediation would verify IP reachability, routing instance context, TCP transport and session authentication and demonstrate: The TCP peering session reaches Established and remains stable.

Question 796

A planned root bridge migration is configured but the operational root remains on the old switch. What diagnosis and engineering response are most appropriate?

  1. Fault mechanism: Spanning-tree security mechanisms protect distinct topology and control-plane risks. Remediation: Match loop, BPDU and root protection to their different fault conditions.
  2. Root issue: Nonstop bridging protects relevant Layer 2 control-protocol state during switchover. Correction: Evaluate nonstop bridging together with the supported Routing Engine redundancy design.
  3. Cause: Configuration intent must be verified against the actual elected spanning-tree root. Response: Compare root priority, bridge identifiers and current STP topology status.
  4. Diagnosis: Loop protection can prevent unsafe forwarding when control-plane information is missing. Action: Inspect spanning-tree loop-protection events, root path and link state.

Explanation

Correct Answer

C:

This is the model-intended best choice because configuration intent must be verified against the actual elected spanning-tree root. The targeted correction is to compare root priority, bridge identifiers and current STP topology status. Validate it by observing that a controlled election yields the approved root with documented path changes.

Incorrect Answers

A:

That result would be useful for a different failure, namely: An engineer uses loop protection as if it served the same purpose as BPDU protection on every port. The current case specifically calls for: Compare root priority, bridge identifiers and current STP topology status. The required observed result is: A controlled election yields the approved root with documented path changes.

B:

This response would target a different source scenario: An Ethernet service must retain bridge state during Routing Engine failover but only Layer 3 HA settings are considered. It cannot establish the current acceptance requirement, which is: A controlled election yields the approved root with documented path changes. The relevant action is: Compare root priority, bridge identifiers and current STP topology status.

D:

The alternative addresses an alternate uplink remains blocked after the primary path fails because expected BPDUs disappear, not the present root cause. Here the selected correction must reflect configuration intent must be verified against the actual elected spanning-tree root. Test for: A controlled election yields the approved root with documented path changes.

Question 797

An RSVP LSP needs to avoid a congested link but its path is left to ordinary unconstrained routing. Which test result would best confirm a successful fix?

  1. Closeout evidence: The installed LSP avoids the prohibited link in a failure-free test.
  2. Acceptance check: The test service label is retained and accepted at the target PE.
  3. The test confirms that the chosen protocol establishes the intended type of LSP.
  4. Expected observation: The intended inet6 family receives and selects the IPv6 prefix.

Explanation

Correct Answer

A:

The critical observation is: RSVP-TE path choice can account for configured topology constraints and resources. Correct it by taking this action: Review explicit-path or constraint-based RSVP traffic-engineering intent. Confirm the outcome with: The installed LSP avoids the prohibited link in a failure-free test.

Incorrect Answers

B:

A healthy transport LSP does not guarantee a correct overlay label mapping describes a neighboring protocol concern. In this case the controlling fact is rSVP-TE path choice can account for configured topology constraints and resources. A correct remediation would review explicit-path or constraint-based RSVP traffic-engineering intent and demonstrate: The installed LSP avoids the prohibited link in a failure-free test.

C:

The proposed principle concerns another network fault: RSVP-TE can signal explicit or constrained paths while ordinary LDP follows routing reachability. Here, rSVP-TE path choice can account for configured topology constraints and resources. The most direct correction is to review explicit-path or constraint-based RSVP traffic-engineering intent, confirmed by the installed LSP avoids the prohibited link in a failure-free test.

D:

That result would be useful for a different failure, namely: A peer announces an IPv6 prefix but the operator checks only the IPv4 BGP route family. The current case specifically calls for: Review explicit-path or constraint-based RSVP traffic-engineering intent. The required observed result is: The installed LSP avoids the prohibited link in a failure-free test.

Question 798

A core engineer sees that IPv6 reachability is absent despite IS-IS adjacency and concludes the adjacency itself is broken. What observable result most directly verifies the intended configuration?

  1. Verification result: Each direction's active route matches the documented costs and design.
  2. Closeout evidence: The internal router resolves the next hop and installs the intended route.
  3. Acceptance check: The planned area topology reaches distant prefixes through eligible Level 2 routing.
  4. The test confirms that the expected IPv6 prefix appears after family and policy review.

Explanation

Correct Answer

D:

This is the model-intended best choice because an adjacency can be operational while a specific family or prefix is not advertised. The targeted correction is to distinguish IS-IS adjacency from address-family reachability advertisements. Validate it by observing that the expected IPv6 prefix appears after family and policy review.

Incorrect Answers

A:

Compare path metrics and each router's route selection before altering LSP state is a relevant step for the separate scenario in which an IS-IS link has asymmetric traffic despite synchronized LSPs and the engineer assumes the LSDB itself is corrupted. It does not directly fix this case. Instead distinguish IS-IS adjacency from address-family reachability advertisements; verify: The expected IPv6 prefix appears after family and policy review.

B:

The alternative addresses an iBGP route is hidden because the next hop learned from an edge router is unreachable inside the backbone, not the present root cause. Here the selected correction must reflect an adjacency can be operational while a specific family or prefix is not advertised. Test for: The expected IPv6 prefix appears after family and policy review.

C:

This answer would be more suitable when a provider uses a Level 1-only router to interconnect two independent IS-IS areas and expects unrestricted cross-area flooding, where the corrective action is to place the correct L1/L2 boundary and evaluate flooding scope. The failure here is different: An adjacency can be operational while a specific family or prefix is not advertised. Required validation: The expected IPv6 prefix appears after family and policy review.

Question 799

A dual-stack peer is Established but the IPv6 customer route is absent. Which statement identifies the key design assumption that failed?

  1. Underlying principle: Route reflection relies on correct client boundaries and originator or cluster tracking.
  2. Root design issue: An upstream LSR can remove a label before the egress in an appropriate PHP design.
  3. The governing rule is: Route reflection can fail due to session or policy scope even when the route exists centrally.
  4. The key distinction is: IPv4 BGP session liveness does not prove IPv6 family route exchange.

Explanation

Correct Answer

D:

Underlying cause: IPv4 BGP session liveness does not prove IPv6 family route exchange. Corrective action: inspect inet6 family negotiation, filters and IPv6 next-hop validity. Verify the outcome: The expected IPv6 NLRI is received and becomes an eligible IPv6 route.

Incorrect Answers

A:

The proposed principle concerns another network fault: Route reflection relies on correct client boundaries and originator or cluster tracking. Here, iPv4 BGP session liveness does not prove IPv6 family route exchange. The most direct correction is to inspect inet6 family negotiation, filters and IPv6 next-hop validity, confirmed by the expected IPv6 NLRI is received and becomes an eligible IPv6 route.

B:

That result would be useful for a different failure, namely: A penultimate router pops a transport label and the egress receives native IP even though the engineer expected a visible final outer label. The current case specifically calls for: Inspect inet6 family negotiation, filters and IPv6 next-hop validity. The required observed result is: The expected IPv6 NLRI is received and becomes an eligible IPv6 route.

C:

This response would target a different source scenario: A route reflector receives a new branch prefix but one iBGP client never learns it. It cannot establish the current acceptance requirement, which is: The expected IPv6 NLRI is received and becomes an eligible IPv6 route. The relevant action is: Inspect inet6 family negotiation, filters and IPv6 next-hop validity.

Question 800

A service provider tags prefixes for selective export but applies the community-match policy to the wrong neighbor group. What assessment accurately links the fault to its correction?

  1. Root issue: An upstream LSR can remove a label before the egress in an appropriate PHP design. Correction: Recognize penultimate-hop popping as an allowed LSP forwarding behavior.
  2. Cause: Communities are policy signaling metadata and not the packet-forwarding next hop themselves. Response: Differentiate community tags from reachability and forwarding attributes.
  3. Diagnosis: Route reflection can fail due to session or policy scope even when the route exists centrally. Action: Check client definitions, route-reflector session state and export policy.
  4. Explanation: BGP group inheritance and policy direction govern which advertisements are modified. Repair: Map inbound and outbound policy points and confirm the intended communities.

Explanation

Correct Answer

D:

Because bGP group inheritance and policy direction govern which advertisements are modified, the best response is to map inbound and outbound policy points and confirm the intended communities. A reviewer can close the technical case only after confirming that a neighbor advertising test shows precisely the allowed tagged prefixes.

Incorrect Answers

A:

This answer would be more suitable when a penultimate router pops a transport label and the egress receives native IP even though the engineer expected a visible final outer label, where the corrective action is to recognize penultimate-hop popping as an allowed LSP forwarding behavior. The failure here is different: BGP group inheritance and policy direction govern which advertisements are modified. Required validation: A neighbor advertising test shows precisely the allowed tagged prefixes.

B:

This option overlooks the decisive condition. Its supporting principle is communities are policy signaling metadata and not the packet-forwarding next hop themselves, while this scenario depends on bGP group inheritance and policy direction govern which advertisements are modified. Verify the correction with: A neighbor advertising test shows precisely the allowed tagged prefixes.

C:

Route reflection can fail due to session or policy scope even when the route exists centrally describes a neighboring protocol concern. In this case the controlling fact is bGP group inheritance and policy direction govern which advertisements are modified. A correct remediation would map inbound and outbound policy points and confirm the intended communities and demonstrate: A neighbor advertising test shows precisely the allowed tagged prefixes.

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