McAfee Secured

Exam Code: JN0-364

Exam Name: Service Provider Routing and Switching, Specialist (JNCIS-SP)

Certification Provider: Juniper

100% Juniper JN0-364 Guaranteed Success With Testking Training Materials

Get Real JN0-364 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

69 Questions & Answers with Testing Engine

"Service Provider Routing and Switching, Specialist (JNCIS-SP) Exam", also known as JN0-364 exam, is a Juniper certification exam.

Pass your tests with the always up-to-date JN0-364 Exam Engine. Your JN0-364 training materials keep you at the head of the pack!

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Was: $137.49
Now: $124.99

Juniper JN0-364 Practice Test 45

Question 440

In a separate fictional JNCIS-SP lab review for Fairhaven Broadband 110, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: A broad accept term in a BGP policy is evaluated before a specific reject term, letting unwanted routes through. What likely service impact does this condition create?

  1. Undetected route oscillation harms network stability.
  2. IBGP clients lack complete reachability and use inconsistent exits.
  3. A supposedly restrictive policy inadvertently advertises internal routes.
  4. Customers can inject unapproved Layer 2 traffic into the provider bridge.

Explanation

Correct Answer

C:

A supposedly restrictive policy inadvertently advertises internal routes. Place precise deny/accept logic in the intended evaluation order and validate policy results. Junos routing policy is evaluated by terms whose order and matching conditions affect the outcome.

Incorrect Answers

A:

Undetected route oscillation harms network stability. That could help when a prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored; here, a broad accept term in a BGP policy is evaluated before a specific reject term, letting unwanted routes through.

B:

IBGP clients lack complete reachability and use inconsistent exits. This is applicable when an internal client learns routes from another client only intermittently after the route-reflector peering address changes; the present condition is that a broad accept term in a BGP policy is evaluated before a specific reject term, letting unwanted routes through.

D:

Customers can inject unapproved Layer 2 traffic into the provider bridge. This could help if an interface permits every customer VLAN tag despite a contract listing only two approved VLANs, but not when a broad accept term in a BGP policy is evaluated before a specific reject term, letting unwanted routes through.

Question 441

At fictional Cedarwater Transit 111, a regional service-provider network, during a planned PE-to-core handoff, operations observes: An IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled. Which configuration or operational correction most directly addresses this failure?

  1. Inspect AS path and applicable policy before changing unrelated preference settings.
  2. Repair transport routing and source-address selection before modifying BGP policy.
  3. Configure the appropriate BGP IPv6 family on the peers and confirm route exchange.
  4. Synchronize the approved IS-IS authentication configuration across peers and verify secure adjacency.

Explanation

Correct Answer

C:

Configure the appropriate BGP IPv6 family on the peers and confirm route exchange. BGP address-family negotiation determines which network-layer reachability data can be exchanged. IPv6 prefixes appear in the correct BGP table with resolvable next hops.

Incorrect Answers

A:

Inspect AS path and applicable policy before changing unrelated preference settings. This could matter when an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path. In this case, an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled.

B:

Repair transport routing and source-address selection before modifying BGP policy. That could help when a BGP peer has a correct AS number but cannot connect because its TCP transport address is unreachable; here, an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled.

D:

Synchronize the approved IS-IS authentication configuration across peers and verify secure adjacency. It is relevant if a provider IS-IS circuit stops forming neighbors after the authentication key is changed on only one end, but the reported issue is that an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled.

Question 442

At fictional Cedarwater Transit 111, a regional service-provider network, during a planned PE-to-core handoff, operations observes: An IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled. Which Junos forwarding or control-plane rule applies to this case?

  1. BGP address-family negotiation determines which network-layer reachability data can be exchanged.
  2. Junos BGP exports only routes accepted by the applicable export policy.
  3. Higher BGP LOCAL_PREF is favored among otherwise eligible paths within an AS.
  4. A discard route can protect against loops for unallocated portions of an aggregate but must not mask actual reachability.

Explanation

Correct Answer

A:

BGP address-family negotiation determines which network-layer reachability data can be exchanged. Configure the appropriate BGP IPv6 family on the peers and confirm route exchange. IPv6 prefixes appear in the correct BGP table with resolvable next hops.

Incorrect Answers

B:

Junos BGP exports only routes accepted by the applicable export policy. This could matter when a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it. In this case, an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled.

C:

Higher BGP LOCAL_PREF is favored among otherwise eligible paths within an AS. That could help when a customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset; here, an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled.

D:

A discard route can protect against loops for unallocated portions of an aggregate but must not mask actual reachability. This is applicable when a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised; the present condition is that an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled.

Question 443

At fictional Cedarwater Transit 111, a regional service-provider network, during a planned PE-to-core handoff, operations observes: An IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled. What operational evidence best establishes successful remediation?

  1. Peer details show the intended internal AS relationship and routes propagate by design.
  2. The suspect path is explained and only eligible loop-free routes are selected.
  3. IPv6 prefixes appear in the correct BGP table with resolvable next hops.
  4. Neighbors reach Full and relevant LSA identifiers and sequence states agree.

Explanation

Correct Answer

C:

IPv6 prefixes appear in the correct BGP table with resolvable next hops. BGP address-family negotiation determines which network-layer reachability data can be exchanged. Configure the appropriate BGP IPv6 family on the peers and confirm route exchange.

Incorrect Answers

A:

Peer details show the intended internal AS relationship and routes propagate by design. That option concerns an operator configures an internal route-reflector session as EBGP and introduces an unintended AS boundary. The problem here is different: An IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled.

B:

The suspect path is explained and only eligible loop-free routes are selected. It addresses a different problem: An engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path. Here, an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled.

D:

Neighbors reach Full and relevant LSA identifiers and sequence states agree. That could help when two supposed adjacent routers have different views of a backbone link because database synchronization never completes; here, an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled.

Question 444

At fictional Cedarwater Transit 111, a regional service-provider network, during a planned PE-to-core handoff, operations observes: An IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled. Which operational harm would persist without the intended correction?

  1. Undetected route oscillation harms network stability.
  2. Unwanted routes may alter forwarding or create customer traffic leakage.
  3. IPv6 customers lose service even when IPv4 routing remains healthy.
  4. IPv6 customers lose external paths despite healthy IPv4 peering.

Explanation

Correct Answer

D:

IPv6 customers lose external paths despite healthy IPv4 peering. BGP address-family negotiation determines which network-layer reachability data can be exchanged. Configure the appropriate BGP IPv6 family on the peers and confirm route exchange.

Incorrect Answers

A:

Undetected route oscillation harms network stability. The choice would be appropriate if a prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored. Here, an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled.

B:

Unwanted routes may alter forwarding or create customer traffic leakage. That option concerns a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy. The problem here is different: An IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled.

C:

IPv6 customers lose service even when IPv4 routing remains healthy. It addresses a different problem: An IPv6 service prefix is configured with a next-hop address that does not resolve on the intended transit interface. Here, an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled.

Question 445

In a separate fictional JNCIS-SP lab review for Riverstone Networks 112, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: An IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled. What should the Junos specialist change first to resolve this specific fault?

  1. Configure the appropriate BGP IPv6 family on the peers and confirm route exchange.
  2. Review negotiated hold time and keepalive settings alongside transport health, then correct the design.
  3. Align the peer type and AS settings with the intended same-AS design.
  4. Review RSVP path constraints and explicit-route settings, then reestablish the LSP.

Explanation

Correct Answer

A:

Configure the appropriate BGP IPv6 family on the peers and confirm route exchange. IPv6 prefixes appear in the correct BGP table with resolvable next hops. BGP address-family negotiation determines which network-layer reachability data can be exchanged.

Incorrect Answers

B:

Review negotiated hold time and keepalive settings alongside transport health, then correct the design. The choice would be appropriate if a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions. Here, an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled.

C:

Align the peer type and AS settings with the intended same-AS design. That option concerns an operator configures an internal route-reflector session as EBGP and introduces an unintended AS boundary. The problem here is different: An IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled.

D:

Review RSVP path constraints and explicit-route settings, then reestablish the LSP. It addresses a different problem: An RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route. Here, an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled.

Question 446

In a separate fictional JNCIS-SP lab review for Riverstone Networks 112, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: An IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled. What technical principle underlies the right remedy?

  1. BGP address-family negotiation determines which network-layer reachability data can be exchanged.
  2. BGP peers use negotiated timers to detect failed sessions and maintain liveness.
  3. A BGP path cannot be installed for forwarding when its next hop cannot be resolved.
  4. IS-IS neighbors require compatible level participation to exchange link-state information.

Explanation

Correct Answer

A:

BGP address-family negotiation determines which network-layer reachability data can be exchanged. IPv6 prefixes appear in the correct BGP table with resolvable next hops. Configure the appropriate BGP IPv6 family on the peers and confirm route exchange.

Incorrect Answers

B:

BGP peers use negotiated timers to detect failed sessions and maintain liveness. This addresses a situation in which a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions; however, an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled.

C:

A BGP path cannot be installed for forwarding when its next hop cannot be resolved. The choice would be appropriate if an IBGP-learned external prefix is present but inactive because the advertised next-hop address has no IGP reachability. Here, an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled.

D:

IS-IS neighbors require compatible level participation to exchange link-state information. That option concerns two adjacent core routers cannot establish IS-IS because one is configured only for Level 1 and the other only for Level 2. The problem here is different: An IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled.

Question 447

In a separate fictional JNCIS-SP lab review for Riverstone Networks 112, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: An IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled. Which acceptance finding demonstrates the affected service has recovered?

  1. IPv6 prefixes appear in the correct BGP table with resolvable next hops.
  2. Both client sessions stabilize and expected reflected routes reach peers.
  3. The source of withdrawals is identified and the prefix stays available during observation.
  4. Both client MACs appear in the intended VLAN and bidirectional frames traverse the switch.

Explanation

Correct Answer

A:

IPv6 prefixes appear in the correct BGP table with resolvable next hops. Configure the appropriate BGP IPv6 family on the peers and confirm route exchange. BGP address-family negotiation determines which network-layer reachability data can be exchanged.

Incorrect Answers

B:

Both client sessions stabilize and expected reflected routes reach peers. That relates to circumstances in which an internal client learns routes from another client only intermittently after the route-reflector peering address changes. Here the problem is that an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled.

C:

The source of withdrawals is identified and the prefix stays available during observation. This addresses a situation in which an upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route; however, an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled.

D:

Both client MACs appear in the intended VLAN and bidirectional frames traverse the switch. The choice would be appropriate if hosts connected through a service-provider switch cannot exchange traffic because each port references a different VLAN identifier. Here, an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled.

Question 448

In a separate fictional JNCIS-SP lab review for Riverstone Networks 112, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: An IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled. What is the direct residual network risk if the fault remains unresolved?

  1. IPv6 customers lose external paths despite healthy IPv4 peering.
  2. Unwanted routes may alter forwarding or create customer traffic leakage.
  3. Remote networks cannot reach the customer or a broad policy leaks infrastructure routes.
  4. A planned maintenance window causes an avoidable customer outage.

Explanation

Correct Answer

A:

IPv6 customers lose external paths despite healthy IPv4 peering. Configure the appropriate BGP IPv6 family on the peers and confirm route exchange. BGP address-family negotiation determines which network-layer reachability data can be exchanged.

Incorrect Answers

B:

Unwanted routes may alter forwarding or create customer traffic leakage. It is useful for situations where a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy; the reported fault, though, is that an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled.

C:

Remote networks cannot reach the customer or a broad policy leaks infrastructure routes. That relates to circumstances in which a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it. Here the problem is that an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled.

D:

A planned maintenance window causes an avoidable customer outage. This addresses a situation in which a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested; however, an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled.

Question 449

At fictional Windmere Fiber 113, a regional service-provider network, during a two-site transit migration, operations observes: An operator configures an internal route-reflector session as EBGP and introduces an unintended AS boundary. Which targeted remediation best fits the reported behavior?

  1. Align the peer type and AS settings with the intended same-AS design.
  2. Inspect full route attributes and the BGP decision outcome for all candidate paths.
  3. Configure the appropriate BGP IPv6 family on the peers and confirm route exchange.
  4. Enable the intended IPv6 OSPFv3 configuration and verify neighbor and route state.

Explanation

Correct Answer

A:

Align the peer type and AS settings with the intended same-AS design. IBGP connects peers within an AS while EBGP represents inter-AS exchange with different policy expectations. Peer details show the intended internal AS relationship and routes propagate by design.

Incorrect Answers

B:

Inspect full route attributes and the BGP decision outcome for all candidate paths. This relates to a case where a prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored; the current situation is that an operator configures an internal route-reflector session as EBGP and introduces an unintended AS boundary.

C:

Configure the appropriate BGP IPv6 family on the peers and confirm route exchange. It is useful for situations where an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled; the reported fault, though, is that an operator configures an internal route-reflector session as EBGP and introduces an unintended AS boundary.

D:

Enable the intended IPv6 OSPFv3 configuration and verify neighbor and route state. That relates to circumstances in which an IPv6 prefix is missing across a point-to-point link because OSPFv2 was configured but OSPFv3 was omitted. Here the problem is that an operator configures an internal route-reflector session as EBGP and introduces an unintended AS boundary.

Question 450

At fictional Windmere Fiber 113, a regional service-provider network, during a two-site transit migration, operations observes: An operator configures an internal route-reflector session as EBGP and introduces an unintended AS boundary. Why is this particular correction the best fit for the stated defect?

  1. BGP peers need mutually consistent AS and transport/session parameters.
  2. IBGP connects peers within an AS while EBGP represents inter-AS exchange with different policy expectations.
  3. Route reflectors distribute selected IBGP reachability within the configured client topology.
  4. An Ethernet port's VLAN tagging behavior must match the frames it receives.

Explanation

Correct Answer

B:

IBGP connects peers within an AS while EBGP represents inter-AS exchange with different policy expectations. Align the peer type and AS settings with the intended same-AS design. Peer details show the intended internal AS relationship and routes propagate by design.

Incorrect Answers

A:

BGP peers need mutually consistent AS and transport/session parameters. It is relevant if an external BGP session never reaches Established because the local peer definition uses the wrong remote AS, but the reported issue is that an operator configures an internal route-reflector session as EBGP and introduces an unintended AS boundary.

C:

Route reflectors distribute selected IBGP reachability within the configured client topology. This relates to a case where an internal client learns routes from another client only intermittently after the route-reflector peering address changes; the current situation is that an operator configures an internal route-reflector session as EBGP and introduces an unintended AS boundary.

D:

An Ethernet port's VLAN tagging behavior must match the frames it receives. It is useful for situations where a provider access port drops customer tagged frames because it was configured for untagged access mode; the reported fault, though, is that an operator configures an internal route-reflector session as EBGP and introduces an unintended AS boundary.

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