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 47

Question 460

A technician tries to diagnose an IS-IS area failure only by inspecting IP multicast Hellos. Which corrective action and confirmation pair is most appropriate?

  1. Action: Recognize IS-IS as a link-layer routing protocol with its own PDUs. Evidence: A link-level packet trace observes the relevant IS-IS PDUs.
  2. Repair: Compare NET area addresses and intended L1 or L2 adjacency mode. Check: A protocol check shows the authorized level and matching adjacency.
  3. Change: Differentiate multiaccess DIS election from point-to-point adjacency behavior. Test: A point-to-point link reaches the expected adjacency state without DIS election.
  4. Implement: Inspect TCP reachability, permitted port 179, and authentication on the transport path. Verify: An authenticated TCP session stays Established after the rule correction.

Explanation

Correct Answer

A:

This option addresses the stated case rather than another networking issue. Principle: IS-IS packet exchange and transport differ from OSPF over IP. Remedy: Recognize IS-IS as a link-layer routing protocol with its own PDUs. Proof: A link-level packet trace observes the relevant IS-IS PDUs.

Incorrect Answers

B:

This response would target a different source scenario: Two routers exchange IS-IS Hellos but one rejects the neighbor during area validation. It cannot establish the current acceptance requirement, which is: A link-level packet trace observes the relevant IS-IS PDUs. The relevant action is: Recognize IS-IS as a link-layer routing protocol with its own PDUs.

C:

Differentiate multiaccess DIS election from point-to-point adjacency behavior is a relevant step for the separate scenario in which an engineer expects an IS-IS Designated Intermediate System election on a point-to-point core link. It does not directly fix this case. Instead recognize IS-IS as a link-layer routing protocol with its own PDUs; verify: A link-level packet trace observes the relevant IS-IS PDUs.

D:

The alternative addresses an EBGP peer drops repeatedly after a firewall change despite clean interface counters, not the present root cause. Here the selected correction must reflect iS-IS packet exchange and transport differ from OSPF over IP. Test for: A link-level packet trace observes the relevant IS-IS PDUs.

Question 461

A provider exports an unexpectedly broad set of routes into OSPF after accepting a generic routing policy. What should the operations engineer do first to address the stated fault?

  1. Next step: Constrain redistribution and test route policy acceptance for the intended prefixes.
  2. Corrective action: Verify compatible network and Hello parameters including mask where applicable.
  3. Apply this control: Compare received LSAs with route selection, area eligibility and next-hop resolution.
  4. Remediation: Validate forwarding load-sharing configuration and run representative multi-flow traffic.

Explanation

Correct Answer

A:

The critical observation is: Routing policy controls which external reachability is injected into OSPF. Correct it by taking this action: Constrain redistribution and test route policy acceptance for the intended prefixes. Confirm the outcome with: Only approved external prefixes appear in the OSPF domain.

Incorrect Answers

B:

OSPF network-type and Hello compatibility can prevent adjacency formation describes a neighboring protocol concern. In this case the controlling fact is routing policy controls which external reachability is injected into OSPF. A correct remediation would constrain redistribution and test route policy acceptance for the intended prefixes and demonstrate: Only approved external prefixes appear in the OSPF domain.

C:

The proposed principle concerns another network fault: Receiving topology data does not guarantee a route becomes active and installed. Here, routing policy controls which external reachability is injected into OSPF. The most direct correction is to constrain redistribution and test route policy acceptance for the intended prefixes, confirmed by only approved external prefixes appear in the OSPF domain.

D:

That result would be useful for a different failure, namely: An equal-cost path test sends nearly all flows across one member while both links remain operational. The current case specifically calls for: Constrain redistribution and test route policy acceptance for the intended prefixes. The required observed result is: Only approved external prefixes appear in the OSPF domain.

Question 462

A maintenance change affects MPLS forwarding on just one core hop and the team only checks RSVP session status at ingress. Which next action best resolves this observed routing or switching failure?

  1. Recommended change: Document the discard behavior and determine whether the aggregate should remain advertised.
  2. Next step: Review LDP dependence on reachability and routing of the transport endpoints.
  3. Corrective action: Collect hop-local LFIB, label forwarding and interface counters along the LSP.
  4. Apply this control: Inspect the incoming label, outgoing label and interface on each affected LSR.

Explanation

Correct Answer

C:

Because end-to-end signaling state alone cannot pinpoint a data-plane label failure, the best response is to collect hop-local LFIB, label forwarding and interface counters along the LSP. A reviewer can close the technical case only after confirming that the corrected transit hop forwards the expected incoming label to its planned outgoing label.

Incorrect Answers

A:

Document the discard behavior and determine whether the aggregate should remain advertised is a relevant step for the separate scenario in which a static discard route intended as a summary safety mechanism becomes the only active route after customer specifics disappear. It does not directly fix this case. Instead collect hop-local LFIB, label forwarding and interface counters along the LSP; verify: The corrected transit hop forwards the expected incoming label to its planned outgoing label.

B:

The alternative addresses an LDP-signaled LSP fails when the IGP route to the remote loopback disappears, not the present root cause. Here the selected correction must reflect end-to-end signaling state alone cannot pinpoint a data-plane label failure. Test for: The corrected transit hop forwards the expected incoming label to its planned outgoing label.

D:

This option overlooks the decisive condition. Its supporting principle is label-switching errors can occur even when control-plane endpoint reachability is good, while this scenario depends on end-to-end signaling state alone cannot pinpoint a data-plane label failure. Verify the correction with: The corrected transit hop forwards the expected incoming label to its planned outgoing label.

Question 463

An RSVP LSP needs to avoid a congested link but its path is left to ordinary unconstrained routing. Which next action best resolves this observed routing or switching failure?

  1. Remediation: Review explicit-path or constraint-based RSVP traffic-engineering intent.
  2. Recommended change: Investigate AS-path loop prevention rather than overriding it without risk review.
  3. Next step: Verify the label action and egress handling for the intended service stack.
  4. Corrective action: Differentiate IP underlay reachability from LDP or RSVP control state.

Explanation

Correct Answer

A:

The selected response implements the principle that rSVP-TE path choice can account for configured topology constraints and resources. The engineer should review explicit-path or constraint-based RSVP traffic-engineering intent. Successful confirmation means: The installed LSP avoids the prohibited link in a failure-free test.

Incorrect Answers

B:

That result would be useful for a different failure, namely: A provider advertises a customer prefix with its own AS number already present in the return AS path. 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.

C:

This response would target a different source scenario: An MPLS service fails after penultimate-hop popping is changed without reviewing the egress disposition. It cannot establish the current acceptance requirement, which is: The installed LSP avoids the prohibited link in a failure-free test. The relevant action is: Review explicit-path or constraint-based RSVP traffic-engineering intent.

D:

Differentiate IP underlay reachability from LDP or RSVP control state is a relevant step for the separate scenario in which a transport route is reachable through an IP interface but the LSP still fails due to incomplete label distribution. It does not directly fix this case. Instead review explicit-path or constraint-based RSVP traffic-engineering intent; verify: The installed LSP avoids the prohibited link in a failure-free test.

Question 464

After enabling OSPFv3 a provider sees IPv6 neighbors but no remote IPv6 customer prefixes. What assessment accurately links the fault to its correction?

  1. Diagnosis: Neighbor establishment is distinct from prefix advertisement and installation. Action: Check OSPFv3 family enablement, LSAs and routing-policy route acceptance.
  2. Explanation: IPv6 link-layer neighbor resolution uses ICMPv6 Neighbor Discovery. Repair: Distinguish IPv6 Neighbor Discovery from IPv4 ARP.
  3. Fault mechanism: An IPv6 BGP route requires a resolvable eligible next hop for forwarding. Remediation: Verify IPv6 next-hop reachability and Neighbor Discovery on the outgoing path.
  4. Root issue: GRE encapsulation overhead can expose MTU blackholes for larger payloads. Correction: Test effective MTU and path MTU discovery across the encapsulated route.

Explanation

Correct Answer

A:

This is the model-intended best choice because neighbor establishment is distinct from prefix advertisement and installation. The targeted correction is to check OSPFv3 family enablement, LSAs and routing-policy route acceptance. Validate it by observing that the accepted OSPFv3 IPv6 routes become active in the expected routing table.

Incorrect Answers

B:

This option overlooks the decisive condition. Its supporting principle is iPv6 link-layer neighbor resolution uses ICMPv6 Neighbor Discovery, while this scenario depends on neighbor establishment is distinct from prefix advertisement and installation. Verify the correction with: The accepted OSPFv3 IPv6 routes become active in the expected routing table.

C:

An IPv6 BGP route requires a resolvable eligible next hop for forwarding describes a neighboring protocol concern. In this case the controlling fact is neighbor establishment is distinct from prefix advertisement and installation. A correct remediation would check OSPFv3 family enablement, LSAs and routing-policy route acceptance and demonstrate: The accepted OSPFv3 IPv6 routes become active in the expected routing table.

D:

The proposed principle concerns another network fault: GRE encapsulation overhead can expose MTU blackholes for larger payloads. Here, neighbor establishment is distinct from prefix advertisement and installation. The most direct correction is to check OSPFv3 family enablement, LSAs and routing-policy route acceptance, confirmed by the accepted OSPFv3 IPv6 routes become active in the expected routing table.

Question 465

Two edge routers advertise one gateway service and an engineer expects both to be virtual master without a redundancy plan. What assessment accurately links the fault to its correction?

  1. Cause: Nonstop bridging protects relevant Layer 2 control-protocol state during switchover. Response: Evaluate nonstop bridging together with the supported Routing Engine redundancy design.
  2. Diagnosis: VRRP provides a master and backup mechanism for a shared virtual default gateway. Action: Review VRRP virtual router roles, priority and failover behavior.
  3. Explanation: Conflicting local GR and NSR configuration must be resolved before activation. Repair: Remove the incompatible local mode and validate the supported HA configuration.
  4. Fault mechanism: Spanning tree prevents forwarding loops by selecting a loop-free active topology. Remediation: Enable the appropriate spanning-tree protection and verify the blocked redundant path.

Explanation

Correct Answer

B:

The selected response implements the principle that vRRP provides a master and backup mechanism for a shared virtual default gateway. The engineer should review VRRP virtual router roles, priority and failover behavior. Successful confirmation means: Only the intended master forwards for the virtual gateway under steady state.

Incorrect Answers

A:

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: 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.

C:

The alternative addresses an NSR configuration fails commit after an operator adds graceful restart on the same device, not the present root cause. Here the selected correction must reflect vRRP provides a master and backup mechanism for a shared virtual default gateway. Test for: Only the intended master forwards for the virtual gateway under steady state.

D:

This answer would be more suitable when a Layer 2 ring floods broadcast frames repeatedly after an extra cable is connected, where the corrective action is to enable the appropriate spanning-tree protection and verify the blocked redundant path. The failure here is different: VRRP provides a master and backup mechanism for a shared virtual default gateway. Required validation: Only the intended master forwards for the virtual gateway under steady state.

Question 466

An engineer expects an IS-IS Designated Intermediate System election on a point-to-point core link. Which next action best resolves this observed routing or switching failure?

  1. Next step: Differentiate multiaccess DIS election from point-to-point adjacency behavior.
  2. Corrective action: Check the IPv6 family configuration and advertised reachability rather than rebuilding IPv4 adjacency.
  3. Apply this control: Place the correct L1/L2 boundary and evaluate flooding scope.
  4. Remediation: Compare received LSAs with route selection, area eligibility and next-hop resolution.

Explanation

Correct Answer

A:

Because the IS-IS DIS concept applies to LANs rather than ordinary point-to-point links, the best response is to differentiate multiaccess DIS election from point-to-point adjacency behavior. A reviewer can close the technical case only after confirming that a point-to-point link reaches the expected adjacency state without DIS election.

Incorrect Answers

B:

The proposed principle concerns another network fault: IS-IS can convey multiple address families with appropriate support. Here, the IS-IS DIS concept applies to LANs rather than ordinary point-to-point links. The most direct correction is to differentiate multiaccess DIS election from point-to-point adjacency behavior, confirmed by a point-to-point link reaches the expected adjacency state without DIS election.

C:

That result would be useful for a different failure, namely: A provider uses a Level 1-only router to interconnect two independent IS-IS areas and expects unrestricted cross-area flooding. The current case specifically calls for: Differentiate multiaccess DIS election from point-to-point adjacency behavior. The required observed result is: A point-to-point link reaches the expected adjacency state without DIS election.

D:

This response would target a different source scenario: An OSPF packet capture shows Link State Updates but the route remains hidden from the active table. It cannot establish the current acceptance requirement, which is: A point-to-point link reaches the expected adjacency state without DIS election. The relevant action is: Differentiate multiaccess DIS election from point-to-point adjacency behavior.

Question 467

An Ethernet access design has multiple logical units using one physical port without specifying frame encapsulation. Which technical distinction best describes the observed symptom?

  1. The key distinction is: BPDU protection can prevent rogue switching from affecting a designated edge port.
  2. Protocol behavior: A trunk carries only its configured authorized VLANs.
  3. Underlying principle: Logical service segmentation requires the physical Ethernet encapsulation to match the intended tag model.
  4. Root design issue: Provider bridging can carry customer VLAN tags inside a provider service tag.

Explanation

Correct Answer

C:

The selected response implements the principle that logical service segmentation requires the physical Ethernet encapsulation to match the intended tag model. The engineer should document VLAN-aware versus flexible tagging and unit classification requirements. Successful confirmation means: Both test logical units classify tagged traffic into their intended bridge domains.

Incorrect Answers

A:

The alternative addresses an edge port connected to a user device unexpectedly receives BPDUs from an unauthorized switch, not the present root cause. Here the selected correction must reflect logical service segmentation requires the physical Ethernet encapsulation to match the intended tag model. Test for: Both test logical units classify tagged traffic into their intended bridge domains.

B:

This answer would be more suitable when a trunk permits VLAN 110 but excludes VLAN 120 while users on VLAN 120 report isolation from the remote switch, where the corrective action is to review allowed VLAN membership on both trunk endpoints. The failure here is different: Logical service segmentation requires the physical Ethernet encapsulation to match the intended tag model. Required validation: Both test logical units classify tagged traffic into their intended bridge domains.

D:

Provider bridging can carry customer VLAN tags inside a provider service tag describes a neighboring protocol concern. In this case the controlling fact is logical service segmentation requires the physical Ethernet encapsulation to match the intended tag model. A correct remediation would document VLAN-aware versus flexible tagging and unit classification requirements and demonstrate: Both test logical units classify tagged traffic into their intended bridge domains.

Question 468

A trunk permits VLAN 110 but excludes VLAN 120 while users on VLAN 120 report isolation from the remote switch. Which protocol behavior most directly determines the correct diagnosis?

  1. The governing rule is: A trunk carries only its configured authorized VLANs.
  2. The key distinction is: Customer-facing encapsulation must match the traffic format at ingress.
  3. Protocol behavior: NSR and graceful restart on the local restarting device are different approaches and can conflict.
  4. Underlying principle: Provider bridging can carry customer VLAN tags inside a provider service tag.

Explanation

Correct Answer

A:

This option addresses the stated case rather than another networking issue. Principle: A trunk carries only its configured authorized VLANs. Remedy: Review allowed VLAN membership on both trunk endpoints. Proof: Both permitted VLAN test flows cross while an explicitly denied VLAN stays blocked.

Incorrect Answers

B:

This response would target a different source scenario: An Ethernet provider transit receives an untagged subscriber frame on a service meant for tagged traffic. It cannot establish the current acceptance requirement, which is: Both permitted VLAN test flows cross while an explicitly denied VLAN stays blocked. The relevant action is: Review allowed VLAN membership on both trunk endpoints.

C:

Review supported mutual exclusivity and select the intended HA control-plane method is a relevant step for the separate scenario in which a provider tries to enable nonstop active routing and graceful-restart mode simultaneously on the same Junos device. It does not directly fix this case. Instead review allowed VLAN membership on both trunk endpoints; verify: Both permitted VLAN test flows cross while an explicitly denied VLAN stays blocked.

D:

The alternative addresses an operator plans provider bridging but assumes the customer's C-tag is removed from every frame, not the present root cause. Here the selected correction must reflect a trunk carries only its configured authorized VLANs. Test for: Both permitted VLAN test flows cross while an explicitly denied VLAN stays blocked.

Question 469

A port belongs to a VLAN but traffic to a remote site is forwarded through a different bridge domain. Which test result would best confirm a successful fix?

  1. Verification result: A source MAC appears on the expected port after a test frame.
  2. Closeout evidence: A tagged test frame reaches the approved remote port in the same domain.
  3. Acceptance check: Each VLAN maps to its intended instance and designated root.
  4. The test confirms that the frame loop is removed and learned MAC locations become stable.

Explanation

Correct Answer

B:

The case turns on the distinction that ethernet forwarding uses bridge-domain context rather than arbitrary IP-route matching. Apply this concrete engineering step: Trace frame classification and virtual-switch bridge-domain association. An acceptable verification outcome is: A tagged test frame reaches the approved remote port in the same domain.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is dynamic MAC tables are populated by observed frames and need not be prefilled, while this scenario depends on ethernet forwarding uses bridge-domain context rather than arbitrary IP-route matching. Verify the correction with: A tagged test frame reaches the approved remote port in the same domain.

C:

The proposed principle concerns another network fault: MSTP can group VLANs into multiple spanning-tree instances under shared region parameters. Here, ethernet forwarding uses bridge-domain context rather than arbitrary IP-route matching. The most direct correction is to trace frame classification and virtual-switch bridge-domain association, confirmed by a tagged test frame reaches the approved remote port in the same domain.

D:

That result would be useful for a different failure, namely: An operator tries to solve a MAC-learning loop by adding a static IP route in the core. The current case specifically calls for: Trace frame classification and virtual-switch bridge-domain association. The required observed result is: A tagged test frame reaches the approved remote port in the same domain.

Question 470

A summary route is advertised even though the operator expects every more-specific customer route to remain reachable. What is the primary routing or switching concept illustrated?

  1. Underlying principle: Aggregation can hide individual component failures if advertisement policy is not controlled.
  2. Root design issue: OSPF adjacency requires compatible area and interface parameters.
  3. The governing rule is: Policy-based forwarding can select a routing table independently of the destination lookup in the ingress default table.
  4. The key distinction is: Operational route troubleshooting starts with active state and resolution evidence.

Explanation

Correct Answer

A:

Correct diagnosis: Aggregation can hide individual component failures if advertisement policy is not controlled. The appropriate action is: Distinguish aggregate reachability from specific-route forwarding and test loss of component routes. The follow-up evidence required is: The summary is advertised only under the approved component-route conditions.

Incorrect Answers

B:

The alternative addresses two Junos routers on the same link have mismatched OSPF area identifiers and never form a neighbor relationship, not the present root cause. Here the selected correction must reflect aggregation can hide individual component failures if advertisement policy is not controlled. Test for: The summary is advertised only under the approved component-route conditions.

C:

This answer would be more suitable when a router selects a route in one routing instance while the forwarding policy sends matching traffic into a different table, where the corrective action is to review filter-based forwarding classification and the intended next-table selection. The failure here is different: Aggregation can hide individual component failures if advertisement policy is not controlled. Required validation: The summary is advertised only under the approved component-route conditions.

D:

This option overlooks the decisive condition. Its supporting principle is operational route troubleshooting starts with active state and resolution evidence, while this scenario depends on aggregation can hide individual component failures if advertisement policy is not controlled. Verify the correction with: The summary is advertised only under the approved component-route conditions.

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