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 26

Question 250

A provider creates a customer routing instance but assumes its routes will automatically be present in the master inet.0 table. What observable result most directly verifies the intended configuration?

  1. The test confirms that each customer route is visible only in the tables approved by the design.
  2. Expected observation: The imported route resolves and forwarding behavior matches the intended instance.
  3. Verification result: Only the subscriber's approved traffic enters the alternate routing instance.
  4. Closeout evidence: The intended lower-total-cost path wins under steady-state conditions.

Explanation

Correct Answer

A:

Because routing instances isolate routing tables unless explicit import or export mechanisms connect them, the best response is to define the intended route-leaking boundary between the customer's instance and the master routing table. A reviewer can close the technical case only after confirming that each customer route is visible only in the tables approved by the design.

Incorrect Answers

B:

The proposed principle concerns another network fault: Moving route information between tables does not remove the need for a valid forwarding next hop. Here, routing instances isolate routing tables unless explicit import or export mechanisms connect them. The most direct correction is to define the intended route-leaking boundary between the customer's instance and the master routing table, confirmed by each customer route is visible only in the tables approved by the design.

C:

That result would be useful for a different failure, namely: A filter-based forwarding term matching one subscriber address also captures an overlapping shared services subnet. The current case specifically calls for: Define the intended route-leaking boundary between the customer's instance and the master routing table. The required observed result is: Each customer route is visible only in the tables approved by the design.

D:

This response would target a different source scenario: A branch uses a higher OSPF interface cost but expects that branch to remain the preferred primary path. It cannot establish the current acceptance requirement, which is: Each customer route is visible only in the tables approved by the design. The relevant action is: Define the intended route-leaking boundary between the customer's instance and the master routing table.

Question 251

A transport route is reachable through an IP interface but the LSP still fails due to incomplete label distribution. What diagnosis and engineering response are most appropriate?

  1. Fault mechanism: Unresolvable BGP next hops can make received routes unusable. Remediation: Restore appropriate IGP next-hop reachability or approved next-hop-self behavior.
  2. Root issue: LDP and SR-MPLS may coexist but each needs its own valid label/route state. Correction: Check SR label advertisements, segment configuration and installed MPLS forwarding.
  3. Cause: LDP label bindings are useful only with a functional path to the FEC next hop. Response: Review LDP dependence on reachability and routing of the transport endpoints.
  4. Diagnosis: MPLS forwarding requires coordinated label signaling and forwarding entries. Action: Differentiate IP underlay reachability from LDP or RSVP control state.

Explanation

Correct Answer

D:

The critical observation is: MPLS forwarding requires coordinated label signaling and forwarding entries. Correct it by taking this action: Differentiate IP underlay reachability from LDP or RSVP control state. Confirm the outcome with: The label table and LSP state match the intended forwarding path.

Incorrect Answers

A:

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 mPLS forwarding requires coordinated label signaling and forwarding entries. Test for: The label table and LSP state match the intended forwarding path.

B:

This answer would be more suitable when a provider migrates one path from LDP to SR-MPLS but does not verify the segment-routing forwarding state, where the corrective action is to check SR label advertisements, segment configuration and installed MPLS forwarding. The failure here is different: MPLS forwarding requires coordinated label signaling and forwarding entries. Required validation: The label table and LSP state match the intended forwarding path.

C:

This option overlooks the decisive condition. Its supporting principle is lDP label bindings are useful only with a functional path to the FEC next hop, while this scenario depends on mPLS forwarding requires coordinated label signaling and forwarding entries. Verify the correction with: The label table and LSP state match the intended forwarding path.

Question 252

A route import policy accepts more-specific destinations that should remain isolated inside a wholesale tenant. What is the primary routing or switching concept illustrated?

  1. The governing rule is: Route redistribution must be intentionally scoped to prevent cross-tenant leakage.
  2. The key distinction is: Instance-aware troubleshooting prevents a successful master-table probe from masking tenant isolation issues.
  3. Protocol behavior: OSPF neighbor-state interpretation depends on multiaccess election roles.
  4. Underlying principle: Routing policy acceptance must reflect explicitly permitted destinations.

Explanation

Correct Answer

D:

Correct diagnosis: Routing policy acceptance must reflect explicitly permitted destinations. The appropriate action is: Add a precise prefix and instance match, then inspect effective imports. The follow-up evidence required is: The allowed service routes import and the forbidden more-specific prefixes do not.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A provider applies an overly broad route import policy and customer prefixes enter an unintended tenant instance. The current case specifically calls for: Add a precise prefix and instance match, then inspect effective imports. The required observed result is: The allowed service routes import and the forbidden more-specific prefixes do not.

B:

This response would target a different source scenario: A provider PE can ping a customer in the master instance but probes in the tenant routing instance fail. It cannot establish the current acceptance requirement, which is: The allowed service routes import and the forbidden more-specific prefixes do not. The relevant action is: Add a precise prefix and instance match, then inspect effective imports.

C:

Check DR and BDR roles and expected 2-Way peers before changing a healthy segment is a relevant step for the separate scenario in which a broadcast core VLAN has only one Full adjacency and the engineer wants to reset all routers immediately. It does not directly fix this case. Instead add a precise prefix and instance match, then inspect effective imports; verify: The allowed service routes import and the forbidden more-specific prefixes do not.

Question 253

Two Junos routers on the same link have mismatched OSPF area identifiers and never form a neighbor relationship. Which combined repair and acceptance criterion is strongest?

  1. Repair: Select the correct network-type behavior and inspect the neighbor-state model. Check: The point-to-point adjacency forms without an unnecessary DR election.
  2. Change: Apply a safe approved OSPF process refresh and verify advertised router identity. Test: All neighbors record the new unique ID and routing stability is restored.
  3. Implement: Identify TLVs as structured information within IS-IS protocol data units. Verify: A protocol decode identifies the expected advertised TLV information.
  4. Control: Align the area membership and verify OSPF interface settings on both sides. Accepted result: The peers progress to the expected adjacency state and exchange LSAs.

Explanation

Correct Answer

D:

The selected response implements the principle that oSPF adjacency requires compatible area and interface parameters. The engineer should align the area membership and verify OSPF interface settings on both sides. Successful confirmation means: The peers progress to the expected adjacency state and exchange LSAs.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is dR and BDR elections apply to broadcast or NBMA segments, not ordinary point-to-point links, while this scenario depends on oSPF adjacency requires compatible area and interface parameters. Verify the correction with: The peers progress to the expected adjacency state and exchange LSAs.

B:

Changing router identity may require controlled protocol restart or adjacency reestablishment describes a neighboring protocol concern. In this case the controlling fact is oSPF adjacency requires compatible area and interface parameters. A correct remediation would align the area membership and verify OSPF interface settings on both sides and demonstrate: The peers progress to the expected adjacency state and exchange LSAs.

C:

The proposed principle concerns another network fault: IS-IS advertises extensible routing attributes using TLV-encoded fields. Here, oSPF adjacency requires compatible area and interface parameters. The most direct correction is to align the area membership and verify OSPF interface settings on both sides, confirmed by the peers progress to the expected adjacency state and exchange LSAs.

Question 254

A provider tunnels traffic for customer isolation but makes no decision about routing-policy exposure at the tunnel edge. What assessment accurately links the fault to its correction?

  1. Cause: Tunnel endpoint parameters must correspond to actual reachable interfaces. Response: Verify configured tunnel source and destination and their active underlay routing.
  2. Diagnosis: Incorrect label removal can expose payload handling that the egress does not expect. Action: Verify the label action and egress handling for the intended service stack.
  3. Explanation: Encapsulation does not replace explicit customer route filtering and access policy. Repair: Treat tunnel decapsulation as a routing and security boundary.
  4. Fault mechanism: Tunnel identification and routing-instance separation must be explicit in overlapping designs. Remediation: Review tunnel identifiers, endpoint uniqueness and supported platform demultiplexing.

Explanation

Correct Answer

C:

Because encapsulation does not replace explicit customer route filtering and access policy, the best response is to treat tunnel decapsulation as a routing and security boundary. A reviewer can close the technical case only after confirming that only authorized customer prefixes enter or leave the decapsulated routing context.

Incorrect Answers

A:

Verify configured tunnel source and destination and their active underlay routing is a relevant step for the separate scenario in which a GRE tunnel interface exists but its operational state is unreliable because the source interface was changed. It does not directly fix this case. Instead treat tunnel decapsulation as a routing and security boundary; verify: Only authorized customer prefixes enter or leave the decapsulated routing context.

B:

The alternative addresses an MPLS service fails after penultimate-hop popping is changed without reviewing the egress disposition, not the present root cause. Here the selected correction must reflect encapsulation does not replace explicit customer route filtering and access policy. Test for: Only authorized customer prefixes enter or leave the decapsulated routing context.

D:

This option overlooks the decisive condition. Its supporting principle is tunnel identification and routing-instance separation must be explicit in overlapping designs, while this scenario depends on encapsulation does not replace explicit customer route filtering and access policy. Verify the correction with: Only authorized customer prefixes enter or leave the decapsulated routing context.

Question 255

An LDP binding exists for a remote destination but the forwarding interface points to a failed next hop. What is the most defensible network engineering correction?

  1. Next step: Audit aggregate or generated-route contributors and policy conditions.
  2. Corrective action: Compare label bindings with the active IGP next hop and installed forwarding entries.
  3. Apply this control: Check transport reachability, LDP session state and the relevant IGP routes.
  4. Remediation: Review explicit-path or constraint-based RSVP traffic-engineering intent.

Explanation

Correct Answer

B:

The critical observation is: A stale label binding cannot compensate for unusable transport forwarding. Correct it by taking this action: Compare label bindings with the active IGP next hop and installed forwarding entries. Confirm the outcome with: The selected LDP label uses a live next-hop interface after convergence.

Incorrect Answers

A:

The proposed principle concerns another network fault: Summary advertisements require validation against their underlying active route policy. Here, a stale label binding cannot compensate for unusable transport forwarding. The most direct correction is to compare label bindings with the active IGP next hop and installed forwarding entries, confirmed by the selected LDP label uses a live next-hop interface after convergence.

C:

This response would target a different source scenario: A provider's LDP neighbors disappear after an IGP outage while physical links remain up. It cannot establish the current acceptance requirement, which is: The selected LDP label uses a live next-hop interface after convergence. The relevant action is: Compare label bindings with the active IGP next hop and installed forwarding entries.

D:

Review explicit-path or constraint-based RSVP traffic-engineering intent is a relevant step for the separate scenario in which an RSVP LSP needs to avoid a congested link but its path is left to ordinary unconstrained routing. It does not directly fix this case. Instead compare label bindings with the active IGP next hop and installed forwarding entries; verify: The selected LDP label uses a live next-hop interface after convergence.

Question 256

An engineer sees that RSVP signaling succeeded and assumes all reserved bandwidth remains available for other tunnels. Which root-cause explanation and corrective action fit the case?

  1. Fault mechanism: A stale label binding cannot compensate for unusable transport forwarding. Remediation: Compare label bindings with the active IGP next hop and installed forwarding entries.
  2. Root issue: Instance-aware troubleshooting prevents a successful master-table probe from masking tenant isolation issues. Correction: Run route and connectivity checks in the explicitly intended routing instance.
  3. Cause: RSVP resource reservation may affect which additional constrained LSPs can be admitted. Response: Distinguish signaling reservations from physical link speed and admission control.
  4. Diagnosis: Labels have locally significant forwarding meaning on each LSP segment. Action: Explain label swap behavior across transit label switching routers.

Explanation

Correct Answer

C:

This option addresses the stated case rather than another networking issue. Principle: RSVP resource reservation may affect which additional constrained LSPs can be admitted. Remedy: Distinguish signaling reservations from physical link speed and admission control. Proof: A controlled setup respects the approved link reservation policy.

Incorrect Answers

A:

This answer would be more suitable when an LDP binding exists for a remote destination but the forwarding interface points to a failed next hop, where the corrective action is to compare label bindings with the active IGP next hop and installed forwarding entries. The failure here is different: RSVP resource reservation may affect which additional constrained LSPs can be admitted. Required validation: A controlled setup respects the approved link reservation policy.

B:

This option overlooks the decisive condition. Its supporting principle is instance-aware troubleshooting prevents a successful master-table probe from masking tenant isolation issues, while this scenario depends on rSVP resource reservation may affect which additional constrained LSPs can be admitted. Verify the correction with: A controlled setup respects the approved link reservation policy.

D:

The proposed principle concerns another network fault: Labels have locally significant forwarding meaning on each LSP segment. Here, rSVP resource reservation may affect which additional constrained LSPs can be admitted. The most direct correction is to distinguish signaling reservations from physical link speed and admission control, confirmed by a controlled setup respects the approved link reservation policy.

Question 257

An operator plans provider bridging but assumes the customer's C-tag is removed from every frame. Which next action best resolves this observed routing or switching failure?

  1. Remediation: Clarify C-tag preservation and S-tag encapsulation in a Q-in-Q design.
  2. Recommended change: Trace frame classification and virtual-switch bridge-domain association.
  3. Next step: Verify the BPDU protection event and remove the unauthorized bridge rather than blindly disabling safeguards.
  4. Corrective action: Validate the usable VLAN-ID range and reserved tag values.

Explanation

Correct Answer

A:

Underlying cause: Provider bridging can carry customer VLAN tags inside a provider service tag. Corrective action: clarify C-tag preservation and S-tag encapsulation in a Q-in-Q design. Verify the outcome: An ingress-to-egress capture confirms the intended stacked tagging.

Incorrect Answers

B:

Trace frame classification and virtual-switch bridge-domain association is a relevant step for the separate scenario in which a port belongs to a VLAN but traffic to a remote site is forwarded through a different bridge domain. It does not directly fix this case. Instead clarify C-tag preservation and S-tag encapsulation in a Q-in-Q design; verify: An ingress-to-egress capture confirms the intended stacked tagging.

C:

The alternative addresses a customer plugs a small unmanaged switch into a protected edge port and the port disables as soon as BPDUs arrive, not the present root cause. Here the selected correction must reflect provider bridging can carry customer VLAN tags inside a provider service tag. Test for: An ingress-to-egress capture confirms the intended stacked tagging.

D:

This answer would be more suitable when a customer requests VLAN 4096 as an ordinary 802.1Q customer VLAN without checking valid tag IDs, where the corrective action is to validate the usable VLAN-ID range and reserved tag values. The failure here is different: Provider bridging can carry customer VLAN tags inside a provider service tag. Required validation: An ingress-to-egress capture confirms the intended stacked tagging.

Question 258

A policy change unexpectedly makes a backup transit provider carry most outbound traffic. What assessment accurately links the fault to its correction?

  1. Diagnosis: BGP edge hygiene protects the routing domain from unauthorized reachability. Action: Tighten customer import route filtering and test permitted prefix lengths.
  2. Explanation: Routing policy changes can override expected primary and backup peering intent. Repair: Inspect local preference, export/import inheritance and selected BGP path attributes.
  3. Fault mechanism: OSPF network-type and Hello compatibility can prevent adjacency formation. Remediation: Verify compatible network and Hello parameters including mask where applicable.
  4. Root issue: BGP selection is policy-driven and is not equivalent to IGP least-hop routing. Correction: Trace the applicable BGP route-selection steps and local policies.

Explanation

Correct Answer

B:

This is the model-intended best choice because routing policy changes can override expected primary and backup peering intent. The targeted correction is to inspect local preference, export/import inheritance and selected BGP path attributes. Validate it by observing that traffic uses the primary provider until the documented failover condition occurs.

Incorrect Answers

A:

BGP edge hygiene protects the routing domain from unauthorized reachability describes a neighboring protocol concern. In this case the controlling fact is routing policy changes can override expected primary and backup peering intent. A correct remediation would inspect local preference, export/import inheritance and selected BGP path attributes and demonstrate: Traffic uses the primary provider until the documented failover condition occurs.

C:

That result would be useful for a different failure, namely: A router sends OSPF Hello packets but remains stuck because the subnet mask differs across neighbors on a broadcast link. The current case specifically calls for: Inspect local preference, export/import inheritance and selected BGP path attributes. The required observed result is: Traffic uses the primary provider until the documented failover condition occurs.

D:

This response would target a different source scenario: A router learns the same prefix from peers in distinct autonomous systems but the engineer compares only BGP hop count. It cannot establish the current acceptance requirement, which is: Traffic uses the primary provider until the documented failover condition occurs. The relevant action is: Inspect local preference, export/import inheritance and selected BGP path attributes.

Question 259

An RSVP tunnel unexpectedly crosses a low-capacity link after a traffic-engineering policy change. Which change best corrects the failure without losing the intended design?

  1. Corrective action: Tighten customer import route filtering and test permitted prefix lengths.
  2. Apply this control: Compare label bindings with the active IGP next hop and installed forwarding entries.
  3. Remediation: Explain label swap behavior across transit label switching routers.
  4. Recommended change: Review explicit or constraint-based path selection against current resource availability.

Explanation

Correct Answer

D:

The critical observation is: Traffic-engineering intent must be reflected in the signaled operational LSP path. Correct it by taking this action: Review explicit or constraint-based path selection against current resource availability. Confirm the outcome with: An operational path check excludes the unapproved transit link.

Incorrect Answers

A:

The alternative addresses a customer advertises an unauthorized more-specific and the PE propagates it across the provider core, not the present root cause. Here the selected correction must reflect traffic-engineering intent must be reflected in the signaled operational LSP path. Test for: An operational path check excludes the unapproved transit link.

B:

This answer would be more suitable when an LDP binding exists for a remote destination but the forwarding interface points to a failed next hop, where the corrective action is to compare label bindings with the active IGP next hop and installed forwarding entries. The failure here is different: Traffic-engineering intent must be reflected in the signaled operational LSP path. Required validation: An operational path check excludes the unapproved transit link.

C:

This option overlooks the decisive condition. Its supporting principle is labels have locally significant forwarding meaning on each LSP segment, while this scenario depends on traffic-engineering intent must be reflected in the signaled operational LSP path. Verify the correction with: An operational path check excludes the unapproved transit link.

Question 260

An OSPF interface is accidentally set passive on a provider edge and its neighbor never appears. Which test result would best confirm a successful fix?

  1. The test confirms that the peers progress to the expected adjacency state and exchange LSAs.
  2. Expected observation: The routing table exposes the selection reason and the intended route is installed.
  3. Verification result: The corrected circuit shows the expected neighbor and link-state entries.
  4. Closeout evidence: The intended backbone neighbor forms and customer-only passive interfaces remain passive.

Explanation

Correct Answer

D:

Correct diagnosis: Passive OSPF interfaces can advertise networks without forming neighbors on that interface. The appropriate action is: Review the passive-interface configuration and required active neighbor links. The follow-up evidence required is: The intended backbone neighbor forms and customer-only passive interfaces remain passive.

Incorrect Answers

A:

That result would be useful for a different failure, namely: Two Junos routers on the same link have mismatched OSPF area identifiers and never form a neighbor relationship. The current case specifically calls for: Review the passive-interface configuration and required active neighbor links. The required observed result is: The intended backbone neighbor forms and customer-only passive interfaces remain passive.

B:

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: The intended backbone neighbor forms and customer-only passive interfaces remain passive. The relevant action is: Review the passive-interface configuration and required active neighbor links.

C:

Inspect IS-IS interface enablement, levels, area identifiers and link type is a relevant step for the separate scenario in which a Junos router shows no IS-IS adjacency after a circuit migration though the interface is physically up. It does not directly fix this case. Instead review the passive-interface configuration and required active neighbor links; verify: The intended backbone neighbor forms and customer-only passive interfaces remain passive.

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