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 31

Question 300

A Junos router shows no IS-IS adjacency after a circuit migration though the interface is physically up. Which protocol behavior most directly determines the correct diagnosis?

  1. Protocol behavior: A backup path requires functional forwarding, not merely topology presence.
  2. Underlying principle: IS-IS routing levels determine topology knowledge and area reachability.
  3. Root design issue: Layered neighbor troubleshooting should separate transport from OSPF parameter mismatches.
  4. The governing rule is: An operational interface is not evidence of matching IS-IS protocol configuration.

Explanation

Correct Answer

D:

Correct diagnosis: An operational interface is not evidence of matching IS-IS protocol configuration. The appropriate action is: Inspect IS-IS interface enablement, levels, area identifiers and link type. The follow-up evidence required is: The corrected circuit shows the expected neighbor and link-state entries.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A provider failover exposes an alternate IS-IS path that had never been tested for next-hop resolution. The current case specifically calls for: Inspect IS-IS interface enablement, levels, area identifiers and link type. The required observed result is: The corrected circuit shows the expected neighbor and link-state entries.

B:

This response would target a different source scenario: A router learns a local IS-IS topology but cannot infer reachability in a remote area from its Level 1-only view. It cannot establish the current acceptance requirement, which is: The corrected circuit shows the expected neighbor and link-state entries. The relevant action is: Inspect IS-IS interface enablement, levels, area identifiers and link type.

C:

Compare area, interface mode, timers, authentication and physical status on both endpoints is a relevant step for the separate scenario in which a new OSPF uplink remains down at the adjacency stage after a router replacement. It does not directly fix this case. Instead inspect IS-IS interface enablement, levels, area identifiers and link type; verify: The corrected circuit shows the expected neighbor and link-state entries.

Question 301

A broadcast core VLAN has only one Full adjacency and the engineer wants to reset all routers immediately. Which protocol behavior most directly determines the correct diagnosis?

  1. Root design issue: OSPF neighbor-state interpretation depends on multiaccess election roles.
  2. The governing rule is: OSPF route type and LSA scope depend on where routing information originates.
  3. The key distinction is: Structured protocol-layer evidence separates link health from routing convergence issues.
  4. Protocol behavior: Passive OSPF interfaces can advertise networks without forming neighbors on that interface.

Explanation

Correct Answer

A:

The critical observation is: OSPF neighbor-state interpretation depends on multiaccess election roles. Correct it by taking this action: Check DR and BDR roles and expected 2-Way peers before changing a healthy segment. Confirm the outcome with: The segment passes route and database tests with the expected neighbor states.

Incorrect Answers

B:

OSPF route type and LSA scope depend on where routing information originates describes a neighboring protocol concern. In this case the controlling fact is oSPF neighbor-state interpretation depends on multiaccess election roles. A correct remediation would check DR and BDR roles and expected 2-Way peers before changing a healthy segment and demonstrate: The segment passes route and database tests with the expected neighbor states.

C:

The proposed principle concerns another network fault: Structured protocol-layer evidence separates link health from routing convergence issues. Here, oSPF neighbor-state interpretation depends on multiaccess election roles. The most direct correction is to check DR and BDR roles and expected 2-Way peers before changing a healthy segment, confirmed by the segment passes route and database tests with the expected neighbor states.

D:

That result would be useful for a different failure, namely: An OSPF interface is accidentally set passive on a provider edge and its neighbor never appears. The current case specifically calls for: Check DR and BDR roles and expected 2-Way peers before changing a healthy segment. The required observed result is: The segment passes route and database tests with the expected neighbor states.

Question 302

A maintenance change affects MPLS forwarding on just one core hop and the team only checks RSVP session status at ingress. A reviewer requires a remedy and concrete test evidence. Which pairing fits?

  1. Action: Inspect inet6 family negotiation, filters and IPv6 next-hop validity. Evidence: The expected IPv6 NLRI is received and becomes an eligible IPv6 route.
  2. Repair: Restore the required transport route and inspect label-signaling and next-hop state. Check: The transport endpoint again resolves and a labeled probe succeeds.
  3. Change: Distinguish prefix-based segment reachability from adjacency-specific forwarding instructions. Test: A segment trace follows the desired prefix or explicit adjacency.
  4. Implement: 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.

Explanation

Correct Answer

D:

This is the model-intended best choice because end-to-end signaling state alone cannot pinpoint a data-plane label failure. The targeted correction is to collect hop-local LFIB, label forwarding and interface counters along the LSP. Validate it by observing that the corrected transit hop forwards the expected incoming label to its planned outgoing label.

Incorrect Answers

A:

Inspect inet6 family negotiation, filters and IPv6 next-hop validity is a relevant step for the separate scenario in which a dual-stack peer is Established but the IPv6 customer route is absent. 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 a route policy makes a transport prefix unavailable to the MPLS forwarding context while preserving customer IP routes, 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.

C:

This answer would be more suitable when a segment routing node uses a prefix segment but the operator treats it as a local adjacency segment, where the corrective action is to distinguish prefix-based segment reachability from adjacency-specific forwarding instructions. The failure here is different: End-to-end signaling state alone cannot pinpoint a data-plane label failure. Required validation: The corrected transit hop forwards the expected incoming label to its planned outgoing label.

Question 303

A provider uses a Level 1-only router to interconnect two independent IS-IS areas and expects unrestricted cross-area flooding. Which post-change observation most strongly confirms the correction?

  1. The test confirms that a neighbor route view confirms the approved community-tagged routes are sent.
  2. Expected observation: Both address families display their expected prefixes through the same stable topology.
  3. Verification result: The intended Level 1 or Level 2 adjacency forms with the expected topology scope.
  4. Closeout evidence: The planned area topology reaches distant prefixes through eligible Level 2 routing.

Explanation

Correct Answer

D:

Underlying cause: IS-IS route dissemination follows hierarchical level boundaries. Corrective action: place the correct L1/L2 boundary and evaluate flooding scope. Verify the outcome: The planned area topology reaches distant prefixes through eligible Level 2 routing.

Incorrect Answers

A:

The proposed principle concerns another network fault: Policy inheritance and term action order affect BGP route advertisement. Here, iS-IS route dissemination follows hierarchical level boundaries. The most direct correction is to place the correct L1/L2 boundary and evaluate flooding scope, confirmed by the planned area topology reaches distant prefixes through eligible Level 2 routing.

B:

That result would be useful for a different failure, namely: IPv4 IS-IS routing works but IPv6 routes do not appear on a dual-stack backbone. The current case specifically calls for: Place the correct L1/L2 boundary and evaluate flooding scope. The required observed result is: The planned area topology reaches distant prefixes through eligible Level 2 routing.

C:

This response would target a different source scenario: An IS-IS adjacency between two provider routers fails because their NET addresses encode incompatible area identifiers for a Level 1 relationship. It cannot establish the current acceptance requirement, which is: The planned area topology reaches distant prefixes through eligible Level 2 routing. The relevant action is: Place the correct L1/L2 boundary and evaluate flooding scope.

Question 304

An Ethernet provider transit receives an untagged subscriber frame on a service meant for tagged traffic. Which next action best resolves this observed routing or switching failure?

  1. Recommended change: Separate provider service identification from customer VLAN identifiers.
  2. Next step: Deploy or validate an integrated routing and bridging L3 interface and gateway.
  3. Corrective action: Set appropriate port mode and tag handling at the service edge.
  4. Apply this control: Inspect interface faults and control-plane events before changing STP timers.

Explanation

Correct Answer

C:

This option addresses the stated case rather than another networking issue. Principle: Customer-facing encapsulation must match the traffic format at ingress. Remedy: Set appropriate port mode and tag handling at the service edge. Proof: The test frame is accepted only under the approved tagging plan.

Incorrect Answers

A:

This answer would be more suitable when two network services use identical customer VLAN IDs and the team assumes their frames must share one L2 broadcast domain, where the corrective action is to separate provider service identification from customer VLAN identifiers. The failure here is different: Customer-facing encapsulation must match the traffic format at ingress. Required validation: The test frame is accepted only under the approved tagging plan.

B:

This option overlooks the decisive condition. Its supporting principle is layer 2 bridging does not by itself provide IP intersubnet routing, while this scenario depends on customer-facing encapsulation must match the traffic format at ingress. Verify the correction with: The test frame is accepted only under the approved tagging plan.

D:

The proposed principle concerns another network fault: STP instability can be secondary to physical link churn. Here, customer-facing encapsulation must match the traffic format at ingress. The most direct correction is to set appropriate port mode and tag handling at the service edge, confirmed by the test frame is accepted only under the approved tagging plan.

Question 305

An eBGP peer sends frequent KEEPALIVEs but the operator assumes this proves the best route is installed. Which cause-and-remedy pairing reflects the observed problem?

  1. Explanation: An Established BGP session can exist with zero accepted routes or unusable next hops. Repair: Separate session liveness from prefix acceptance and RIB installation.
  2. Fault mechanism: End-to-end signaling state alone cannot pinpoint a data-plane label failure. Remediation: Collect hop-local LFIB, label forwarding and interface counters along the LSP.
  3. Root issue: BGP group inheritance and policy direction govern which advertisements are modified. Correction: Map inbound and outbound policy points and confirm the intended communities.
  4. Cause: BGP sessions require sustained TCP connectivity independent of physical interface health. Response: Inspect TCP reachability, permitted port 179, and authentication on the transport path.

Explanation

Correct Answer

A:

Underlying cause: An Established BGP session can exist with zero accepted routes or unusable next hops. Corrective action: separate session liveness from prefix acceptance and RIB installation. Verify the outcome: Both neighbor state and selected prefix route evidence are verified independently.

Incorrect Answers

B:

Collect hop-local LFIB, label forwarding and interface counters along the LSP is a relevant step for the separate scenario in which a maintenance change affects MPLS forwarding on just one core hop and the team only checks RSVP session status at ingress. It does not directly fix this case. Instead separate session liveness from prefix acceptance and RIB installation; verify: Both neighbor state and selected prefix route evidence are verified independently.

C:

The alternative addresses a service provider tags prefixes for selective export but applies the community-match policy to the wrong neighbor group, not the present root cause. Here the selected correction must reflect an Established BGP session can exist with zero accepted routes or unusable next hops. Test for: Both neighbor state and selected prefix route evidence are verified independently.

D:

This answer would be more suitable when an EBGP peer drops repeatedly after a firewall change despite clean interface counters, where the corrective action is to inspect TCP reachability, permitted port 179, and authentication on the transport path. The failure here is different: An Established BGP session can exist with zero accepted routes or unusable next hops. Required validation: Both neighbor state and selected prefix route evidence are verified independently.

Question 306

Several routers report intermittent OSPF neighbor resets on a saturated transit circuit. Which change best corrects the failure without losing the intended design?

  1. Apply this control: Constrain redistribution and test route policy acceptance for the intended prefixes.
  2. Remediation: Compare Hello/Dead event logs with loss and interface errors before tuning timers.
  3. Recommended change: Check MTU and interface compatibility and inspect neighbor-state details.
  4. Next step: Compare RIB selection with forwarding-table installation and next-hop resolution.

Explanation

Correct Answer

B:

This is the model-intended best choice because protocol timers need reliable packet delivery and should not mask an unstable link. The targeted correction is to compare Hello/Dead event logs with loss and interface errors before tuning timers. Validate it by observing that a measured link-quality improvement stabilizes OSPF adjacencies.

Incorrect Answers

A:

Routing policy controls which external reachability is injected into OSPF describes a neighboring protocol concern. In this case the controlling fact is protocol timers need reliable packet delivery and should not mask an unstable link. A correct remediation would compare Hello/Dead event logs with loss and interface errors before tuning timers and demonstrate: A measured link-quality improvement stabilizes OSPF adjacencies.

C:

That result would be useful for a different failure, namely: An OSPF trace shows Hellos received but database synchronization stalls at ExStart or Exchange. The current case specifically calls for: Compare Hello/Dead event logs with loss and interface errors before tuning timers. The required observed result is: A measured link-quality improvement stabilizes OSPF adjacencies.

D:

This response would target a different source scenario: A route appears in the routing table but an engineer assumes its presence proves it was installed into the forwarding table. It cannot establish the current acceptance requirement, which is: A measured link-quality improvement stabilizes OSPF adjacencies. The relevant action is: Compare Hello/Dead event logs with loss and interface errors before tuning timers.

Question 307

An ingress router imposes an MPLS label while an engineer expects the same label value to persist unchanged at every hop. Which root-cause explanation and corrective action fit the case?

  1. Cause: MPLS forwarding relies on label bindings and compatible next-hop state. Response: Distinguish IP RIB entries from label forwarding information and LSP resolution.
  2. Diagnosis: Labels have locally significant forwarding meaning on each LSP segment. Action: Explain label swap behavior across transit label switching routers.
  3. Explanation: End-to-end signaling state alone cannot pinpoint a data-plane label failure. Repair: Collect hop-local LFIB, label forwarding and interface counters along the LSP.
  4. Fault mechanism: iBGP can preserve externally learned next-hop information that internal speakers must resolve. Remediation: Review BGP next-hop reachability and explicit next-hop handling.

Explanation

Correct Answer

B:

Underlying cause: Labels have locally significant forwarding meaning on each LSP segment. Corrective action: explain label swap behavior across transit label switching routers. Verify the outcome: A hop trace shows the intended push and swap operations along the path.

Incorrect Answers

A:

The alternative addresses a provider assumes an ordinary IP destination lookup and an MPLS label lookup always use the same forwarding table, not the present root cause. Here the selected correction must reflect labels have locally significant forwarding meaning on each LSP segment. Test for: A hop trace shows the intended push and swap operations along the path.

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 labels have locally significant forwarding meaning on each LSP segment. Verify the correction with: A hop trace shows the intended push and swap operations along the path.

D:

iBGP can preserve externally learned next-hop information that internal speakers must resolve describes a neighboring protocol concern. In this case the controlling fact is labels have locally significant forwarding meaning on each LSP segment. A correct remediation would explain label swap behavior across transit label switching routers and demonstrate: A hop trace shows the intended push and swap operations along the path.

Question 308

A technician treats an OSPF Link State Request as the same message as a Hello packet. What is the primary routing or switching concept illustrated?

  1. Protocol behavior: OSPF uses distinct Hello, database description, link state request, update and acknowledgment functions.
  2. Underlying principle: Route redistribution must be intentionally scoped to prevent cross-tenant leakage.
  3. Root design issue: Protocol timers need reliable packet delivery and should not mask an unstable link.
  4. The governing rule is: Routing policy controls which external reachability is injected into OSPF.

Explanation

Correct Answer

A:

This option addresses the stated case rather than another networking issue. Principle: OSPF uses distinct Hello, database description, link state request, update and acknowledgment functions. Remedy: Differentiate neighbor discovery from database synchronization message types. Proof: The packet trace shows each message at its appropriate adjacency stage.

Incorrect Answers

B:

This response would target a different source scenario: A provider applies an overly broad route import policy and customer prefixes enter an unintended tenant instance. It cannot establish the current acceptance requirement, which is: The packet trace shows each message at its appropriate adjacency stage. The relevant action is: Differentiate neighbor discovery from database synchronization message types.

C:

Compare Hello/Dead event logs with loss and interface errors before tuning timers is a relevant step for the separate scenario in which several routers report intermittent OSPF neighbor resets on a saturated transit circuit. It does not directly fix this case. Instead differentiate neighbor discovery from database synchronization message types; verify: The packet trace shows each message at its appropriate adjacency stage.

D:

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 oSPF uses distinct Hello, database description, link state request, update and acknowledgment functions. Test for: The packet trace shows each message at its appropriate adjacency stage.

Question 309

Two edge routers advertise one gateway service and an engineer expects both to be virtual master without a redundancy plan. Which statement identifies the key design assumption that failed?

  1. The key distinction is: STP instability can be secondary to physical link churn.
  2. Protocol behavior: Conflicting local GR and NSR configuration must be resolved before activation.
  3. Underlying principle: NSR and graceful restart on the local restarting device are different approaches and can conflict.
  4. Root design issue: VRRP provides a master and backup mechanism for a shared virtual default gateway.

Explanation

Correct Answer

D:

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 option overlooks the decisive condition. Its supporting principle is sTP instability can be secondary to physical link churn, while this scenario depends on vRRP provides a master and backup mechanism for a shared virtual default gateway. Verify the correction with: Only the intended master forwards for the virtual gateway under steady state.

B:

Conflicting local GR and NSR configuration must be resolved before activation 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:

The proposed principle concerns another network fault: NSR and graceful restart on the local restarting device are different approaches and can conflict. Here, vRRP provides a master and backup mechanism for a shared virtual default gateway. The most direct correction is to review VRRP virtual router roles, priority and failover behavior, confirmed by only the intended master forwards for the virtual gateway under steady state.

Question 310

A provider PE can ping a customer in the master instance but probes in the tenant routing instance fail. Which technical distinction best describes the observed symptom?

  1. The governing rule is: Policy inheritance and term action order affect BGP route advertisement.
  2. The key distinction is: Summary advertisements require validation against their underlying active route policy.
  3. Protocol behavior: Instance-aware troubleshooting prevents a successful master-table probe from masking tenant isolation issues.
  4. Underlying principle: Aggregation can hide individual component failures if advertisement policy is not controlled.

Explanation

Correct Answer

C:

Because instance-aware troubleshooting prevents a successful master-table probe from masking tenant isolation issues, the best response is to run route and connectivity checks in the explicitly intended routing instance. A reviewer can close the technical case only after confirming that the tenant-specific lookup resolves and the same source-based test reaches its destination.

Incorrect Answers

A:

Inspect effective group and neighbor export policy evaluation order is a relevant step for the separate scenario in which a BGP export policy matches a community but no routes leave the peer after a group-level policy reorder. It does not directly fix this case. Instead run route and connectivity checks in the explicitly intended routing instance; verify: The tenant-specific lookup resolves and the same source-based test reaches its destination.

B:

The alternative addresses an aggregated customer advertisement persists while all contributing specifics have withdrawn, not the present root cause. Here the selected correction must reflect instance-aware troubleshooting prevents a successful master-table probe from masking tenant isolation issues. Test for: The tenant-specific lookup resolves and the same source-based test reaches its destination.

D:

This option overlooks the decisive condition. Its supporting principle is aggregation can hide individual component failures if advertisement policy is not controlled, 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.

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