McAfee-Secured Website

Exam Bundle

Exam Code: 350-501

Exam Name Implementing and Operating Cisco Service Provider Network Core Technologies (SPCOR)

Certification Provider: Cisco

Corresponding Certifications: CCIE Service Provider , CCNP Service Provider

Cisco 350-501 Bundle $28.79

100% Cisco 350-501 Guaranteed Success With Testking Training Materials

Get Real 350-501 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    350-501 Questions & Answers

    528 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual 350-501 exam while allowing you to hone and measure every aspect of your test-taking ability.

  • 350-501 Video Course

    350-501 Video Course

    253 Video Lectures

    350-501 Video Course is developed by Cisco Professionals to help you pass the 350-501 exam.

    Description

    This course will improve your knowledge and skills required to pass Implementing and Operating Cisco Service Provider Network Core Technologies (SPCOR) exam.
  • Study Guide

    350-501 Study Guide

    1160 PDF Pages

    Developed by industry experts, this 1160-page guide spells out in painstaking detail all of the information you need to ace 350-501 exam.

Implementing and Operating Cisco Service Provider Network Core Technologies (SPCOR) (350-501) Practice Tests

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
Total Cost: $189.97
Bundle Price: $161.18

Purchase Individually

  • Questions & Answers

    Questions & Answers

    528 Questions

    $124.99
  • 350-501 Video Course

    Video Course

    253 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    1160 PDF Pages

    $24.99

Cisco 350-501 Practice Test 77

Question 760

For a regional peering-exchange operator, the change record describes: An enterprise customer is promised IPv6 VPN reachability but the PE provisions only VPNv4 MP-BGP and v4 VRF interfaces. What preventive validation should be standard?

  1. Validate VPNv4 and VPNv6 service route counts independently.
  2. Validate CE route reception, VPN export and remote import as three separate checks.
  3. Require overlapping-address negative tests before new VPN attachments.
  4. Review RPL ownership and ring state during ring expansion.

Explanation

Correct Answer

A:

Validate VPNv4 and VPNv6 service route counts independently. This helps prevent recurrence of the issue: An enterprise customer is promised IPv6 VPN reachability but the PE provisions only VPNv4 MP-BGP and v4 VRF interfaces. Acceptance evidence should be: An IPv6 test prefix reaches the remote customer site without unintended mixing with IPv4-only service routing.

Incorrect Answers

B:

Validate CE route reception, VPN export and remote import as three separate checks. That is a sensible control for ANOTHER scenario: A CE-PE BGP session successfully exchanges routes but a newly provisioned customer VRF has no route targets and none of its routes propagate to distant PEs. It is less targeted to this issue than: Validate VPNv4 and VPNv6 service route counts independently.

C:

Require overlapping-address negative tests before new VPN attachments. That is a sensible control for ANOTHER scenario: Two customers use the same 10.10.0.0/16 prefix but a PE leaks VPNv4 routes into its global table, incorrectly merging their routing contexts. It is less targeted to this issue than: Validate VPNv4 and VPNv6 service route counts independently.

D:

Review RPL ownership and ring state during ring expansion. That is a sensible control for ANOTHER scenario: A G.8032 Ethernet ring sees a broadcast storm after a ring protection link is accidentally forwarding on both sides of a stable ring. It is less targeted to this issue than: Validate VPNv4 and VPNv6 service route counts independently.

Question 761

For an optical transport engineering team, the failure is: A core node imposes two service labels on an access interface with a hardware label-stack depth limit below the engineered VPN service, causing selective drops. Which authorized correction best addresses it?

  1. Reconcile LDP label mapping with current IGP FEC reachability and refresh only the impacted forwarding state through supported procedures.
  2. Validate transport versus service label stacking and make sure penultimate-hop popping applies only to the intended outer transport label.
  3. Recalculate supported label depth and adjust service transport or platform selection to the hardware maximum.
  4. Align the requested bypass protection type with available disjoint repair paths and verify coverage for the protected node or link.

Explanation

Correct Answer

C:

Recalculate supported label depth and adjust service transport or platform selection to the hardware maximum. This directly addresses the fictional service-provider network case: A core node imposes two service labels on an access interface with a hardware label-stack depth limit below the engineered VPN service, causing selective drops. The technical mechanism is: MPLS forwarding hardware may limit the number of imposed or inspected labels per packet. Verify success by: A maximal permitted label-stack test forwards across the planned platform while an unsupported stack is rejected during provisioning.

Incorrect Answers

A:

Reconcile LDP label mapping with current IGP FEC reachability and refresh only the impacted forwarding state through supported procedures. This would respond to a DIFFERENT fictional service-provider network issue: Label advertisement remains present for a withdrawn IGP FEC due to a stale forwarding cache, producing a short-lived blackhole after a route-policy rollback. It does not directly address the current situation: A core node imposes two service labels on an access interface with a hardware label-stack depth limit below the engineered VPN service, causing selective drops.

B:

Validate transport versus service label stacking and make sure penultimate-hop popping applies only to the intended outer transport label. This would respond to a DIFFERENT fictional service-provider network issue: A transit router keeps unexpectedly popping a provider's VPN label one hop before the target PE, sending customer traffic toward the global routing table. It does not directly address the current situation: A core node imposes two service labels on an access interface with a hardware label-stack depth limit below the engineered VPN service, causing selective drops.

D:

Align the requested bypass protection type with available disjoint repair paths and verify coverage for the protected node or link. This would respond to a DIFFERENT fictional service-provider network issue: An MPLS TE bypass tunnel is administratively configured but the protected service shows no local protection because node protection was requested and only link protection is available. It does not directly address the current situation: A core node imposes two service labels on an access interface with a hardware label-stack depth limit below the engineered VPN service, causing selective drops.

Question 762

After fixing the following network problem, what should the team verify: A core node imposes two service labels on an access interface with a hardware label-stack depth limit below the engineered VPN service, causing selective drops.

  1. During a single-link failure the session remains protected through the alternative route and bound FECs recover safely.
  2. LDP TCP session establishes and advertises expected label mappings without including unapproved neighbor IDs.
  3. The TE database contains capacity and administrative-group information for all selected links and the constraint solver returns a valid route.
  4. A maximal permitted label-stack test forwards across the planned platform while an unsupported stack is rejected during provisioning.

Explanation

Correct Answer

D:

A maximal permitted label-stack test forwards across the planned platform while an unsupported stack is rejected during provisioning. This confirms the approved response: Recalculate supported label depth and adjust service transport or platform selection to the hardware maximum. It is relevant because: MPLS forwarding hardware may limit the number of imposed or inspected labels per packet.

Incorrect Answers

A:

During a single-link failure the session remains protected through the alternative route and bound FECs recover safely. This would validate ANOTHER scenario: An LDP transport session disappears whenever the direct router-to-router interface flaps, despite an alternate routed path existing between stable loopbacks. The specific correction here is: Recalculate supported label depth and adjust service transport or platform selection to the hardware maximum.

B:

LDP TCP session establishes and advertises expected label mappings without including unapproved neighbor IDs. This would validate ANOTHER scenario: Two neighboring MPLS routers use different LDP authentication credentials and fail to form a TCP session even though UDP discovery hellos arrive. The specific correction here is: Recalculate supported label depth and adjust service transport or platform selection to the hardware maximum.

C:

The TE database contains capacity and administrative-group information for all selected links and the constraint solver returns a valid route. This would validate ANOTHER scenario: A backbone planner expects constrained TE to calculate alternate paths while the IGP advertises only basic reachability and no extended TE link attributes. The specific correction here is: Recalculate supported label depth and adjust service transport or platform selection to the hardware maximum.

Question 763

A carrier root-cause review considers: A core node imposes two service labels on an access interface with a hardware label-stack depth limit below the engineered VPN service, causing selective drops. What underlying mechanism explains this?

  1. MPLS forwarding hardware may limit the number of imposed or inspected labels per packet.
  2. A label binding without reachable next-hop context is insufficient to deliver a usable MPLS transport LSP.
  3. IP routing alone does not ensure MPLS forwarding entries are established for a label-switched core.
  4. Adjacency segments steer traffic over specific local links, unlike more abstract prefix segments.

Explanation

Correct Answer

A:

MPLS forwarding hardware may limit the number of imposed or inspected labels per packet. This explains the investigated issue: A core node imposes two service labels on an access interface with a hardware label-stack depth limit below the engineered VPN service, causing selective drops. The approved corrective response is: Recalculate supported label depth and adjust service transport or platform selection to the hardware maximum.

Incorrect Answers

B:

A label binding without reachable next-hop context is insufficient to deliver a usable MPLS transport LSP. That explains a DIFFERENT scenario: A remote PE receives an LDP label binding but the advertised transport loopback is absent from the IGP, making forwarding unresolved. The mechanism to prioritize for this question is: MPLS forwarding hardware may limit the number of imposed or inspected labels per packet.

C:

IP routing alone does not ensure MPLS forwarding entries are established for a label-switched core. That explains a DIFFERENT scenario: Two P routers forward IPv4 internet traffic but no MPLS labels appear for PE loopbacks because one interface has LDP disabled. The mechanism to prioritize for this question is: MPLS forwarding hardware may limit the number of imposed or inspected labels per packet.

D:

Adjacency segments steer traffic over specific local links, unlike more abstract prefix segments. That explains a DIFFERENT scenario: A headend constructs an SR policy from adjacency SIDs but one adjacency SID identifies the wrong outbound interface after topology maintenance. The mechanism to prioritize for this question is: MPLS forwarding hardware may limit the number of imposed or inspected labels per packet.

Question 764

After addressing: A core node imposes two service labels on an access interface with a hardware label-stack depth limit below the engineered VPN service, causing selective drops. Which recurring service assurance check is most useful?

  1. Check IGP and LDP FEC consistency at every interregion boundary.
  2. Track per-platform maximum label-stack depth in service design inventory.
  3. Inspect label-stack depth and disposition at each egress after LDP or BGP changes.
  4. Verify data-plane steering separately from RSVP session state.

Explanation

Correct Answer

B:

Track per-platform maximum label-stack depth in service design inventory. This helps prevent recurrence of the issue: A core node imposes two service labels on an access interface with a hardware label-stack depth limit below the engineered VPN service, causing selective drops. Acceptance evidence should be: A maximal permitted label-stack test forwards across the planned platform while an unsupported stack is rejected during provisioning.

Incorrect Answers

A:

Check IGP and LDP FEC consistency at every interregion boundary. That is a sensible control for ANOTHER scenario: A remote PE receives an LDP label binding but the advertised transport loopback is absent from the IGP, making forwarding unresolved. It is less targeted to this issue than: Track per-platform maximum label-stack depth in service design inventory.

C:

Inspect label-stack depth and disposition at each egress after LDP or BGP changes. That is a sensible control for ANOTHER scenario: A transit router keeps unexpectedly popping a provider's VPN label one hop before the target PE, sending customer traffic toward the global routing table. It is less targeted to this issue than: Track per-platform maximum label-stack depth in service design inventory.

D:

Verify data-plane steering separately from RSVP session state. That is a sensible control for ANOTHER scenario: The route processor shows an RSVP-TE tunnel Up, but a live traffic test still traverses native IGP forwarding because the tunnel is not selected for the destination. It is less targeted to this issue than: Track per-platform maximum label-stack depth in service design inventory.

Question 765

A provider backbone escalation identifies: Two DS-TE class types share one link, but one tunnel consumes the other class's reserved budget due to a misconfigured bandwidth constraint allocation. What should the network team implement?

  1. Replace the strict path element with supported TE-capable nodes or adjust the explicit route to a valid engineered path.
  2. Install the intended route or autoroute steering policy into the established TE tunnel without affecting unrelated prefixes.
  3. Use IGP-distributed SIDs and supported SR policy steering without imposing unnecessary per-LSP RSVP signaling state.
  4. Correct class-type bandwidth model and bandwidth constraints to match the provider's differentiated service policy.

Explanation

Correct Answer

D:

Correct class-type bandwidth model and bandwidth constraints to match the provider's differentiated service policy. This directly addresses the fictional service-provider network case: Two DS-TE class types share one link, but one tunnel consumes the other class's reserved budget due to a misconfigured bandwidth constraint allocation. The technical mechanism is: DS-TE extends traffic engineering reservation concepts with class-type-aware bandwidth controls. Verify success by: A stress test admits or rejects reservations according to the per-class budget without starving the protected class.

Incorrect Answers

A:

Replace the strict path element with supported TE-capable nodes or adjust the explicit route to a valid engineered path. This would respond to a DIFFERENT fictional service-provider network issue: A provider changes an RSVP-TE tunnel to use an explicit path containing a router that lacks TE extensions, leaving the tunnel down despite IP reachability. It does not directly address the current situation: Two DS-TE class types share one link, but one tunnel consumes the other class's reserved budget due to a misconfigured bandwidth constraint allocation.

B:

Install the intended route or autoroute steering policy into the established TE tunnel without affecting unrelated prefixes. This would respond to a DIFFERENT fictional service-provider network issue: The route processor shows an RSVP-TE tunnel Up, but a live traffic test still traverses native IGP forwarding because the tunnel is not selected for the destination. It does not directly address the current situation: Two DS-TE class types share one link, but one tunnel consumes the other class's reserved budget due to a misconfigured bandwidth constraint allocation.

C:

Use IGP-distributed SIDs and supported SR policy steering without imposing unnecessary per-LSP RSVP signaling state. This would respond to a DIFFERENT fictional service-provider network issue: A provider enables SR-MPLS forwarding but assumes each SR-TE path requires RSVP-TE state on every transit router, blocking deployment when RSVP is disabled. It does not directly address the current situation: Two DS-TE class types share one link, but one tunnel consumes the other class's reserved budget due to a misconfigured bandwidth constraint allocation.

Question 766

A service-provider operations test targets: Two DS-TE class types share one link, but one tunnel consumes the other class's reserved budget due to a misconfigured bandwidth constraint allocation. Which result is required?

  1. A stress test admits or rejects reservations according to the per-class budget without starving the protected class.
  2. RSVP PATH and RESV state establish across the intended nodes and the LSP forwards test traffic.
  3. The replacement LSP becomes usable before the previous one is torn down in an acceptance test.
  4. The VPN transport path becomes operational only after both IGP recursion and the corresponding label are present.

Explanation

Correct Answer

A:

A stress test admits or rejects reservations according to the per-class budget without starving the protected class. This confirms the approved response: Correct class-type bandwidth model and bandwidth constraints to match the provider's differentiated service policy. It is relevant because: DS-TE extends traffic engineering reservation concepts with class-type-aware bandwidth controls.

Incorrect Answers

B:

RSVP PATH and RESV state establish across the intended nodes and the LSP forwards test traffic. This would validate ANOTHER scenario: A provider changes an RSVP-TE tunnel to use an explicit path containing a router that lacks TE extensions, leaving the tunnel down despite IP reachability. The specific correction here is: Correct class-type bandwidth model and bandwidth constraints to match the provider's differentiated service policy.

C:

The replacement LSP becomes usable before the previous one is torn down in an acceptance test. This would validate ANOTHER scenario: A provisioning system attempts to reoptimize an RSVP LSP using a new path but drops the existing path before the replacement is established, causing service interruption. The specific correction here is: Correct class-type bandwidth model and bandwidth constraints to match the provider's differentiated service policy.

D:

The VPN transport path becomes operational only after both IGP recursion and the corresponding label are present. This would validate ANOTHER scenario: A remote PE receives an LDP label binding but the advertised transport loopback is absent from the IGP, making forwarding unresolved. The specific correction here is: Correct class-type bandwidth model and bandwidth constraints to match the provider's differentiated service policy.

Question 767

A provider troubleshooting note states: Two DS-TE class types share one link, but one tunnel consumes the other class's reserved budget due to a misconfigured bandwidth constraint allocation. Which mechanism is central?

  1. Make-before-break can retain service continuity while TE paths are re-signaled, provided temporary bandwidth and state exist.
  2. DS-TE extends traffic engineering reservation concepts with class-type-aware bandwidth controls.
  3. RSVP-TE supports priority-based reservation and preemption to allocate scarce transport resources.
  4. Segment Routing can encode forwarding instructions in the packet and reduce dependency on per-tunnel transit RSVP state.

Explanation

Correct Answer

B:

DS-TE extends traffic engineering reservation concepts with class-type-aware bandwidth controls. This explains the investigated issue: Two DS-TE class types share one link, but one tunnel consumes the other class's reserved budget due to a misconfigured bandwidth constraint allocation. The approved corrective response is: Correct class-type bandwidth model and bandwidth constraints to match the provider's differentiated service policy.

Incorrect Answers

A:

Make-before-break can retain service continuity while TE paths are re-signaled, provided temporary bandwidth and state exist. That explains a DIFFERENT scenario: A provisioning system attempts to reoptimize an RSVP LSP using a new path but drops the existing path before the replacement is established, causing service interruption. The mechanism to prioritize for this question is: DS-TE extends traffic engineering reservation concepts with class-type-aware bandwidth controls.

C:

RSVP-TE supports priority-based reservation and preemption to allocate scarce transport resources. That explains a DIFFERENT scenario: A provider enables RSVP bandwidth reservation but leaves all tunnels with one identical setup and holding priority, making critical voice LSP preemption unpredictable. The mechanism to prioritize for this question is: DS-TE extends traffic engineering reservation concepts with class-type-aware bandwidth controls.

D:

Segment Routing can encode forwarding instructions in the packet and reduce dependency on per-tunnel transit RSVP state. That explains a DIFFERENT scenario: A provider enables SR-MPLS forwarding but assumes each SR-TE path requires RSVP-TE state on every transit router, blocking deployment when RSVP is disabled. The mechanism to prioritize for this question is: DS-TE extends traffic engineering reservation concepts with class-type-aware bandwidth controls.

Question 768

To prevent recurrence of this provider network issue: Two DS-TE class types share one link, but one tunnel consumes the other class's reserved budget due to a misconfigured bandwidth constraint allocation. Which control should be retained?

  1. Record reoptimization stability and path-change rate in monitoring.
  2. Test preemption conditions and impact warnings before new tunnel activation.
  3. Track class-type utilization and validate reservation boundaries after QoS changes.
  4. Monitor adjacency SID changes and invalidate stale policy segment lists.

Explanation

Correct Answer

C:

Track class-type utilization and validate reservation boundaries after QoS changes. This helps prevent recurrence of the issue: Two DS-TE class types share one link, but one tunnel consumes the other class's reserved budget due to a misconfigured bandwidth constraint allocation. Acceptance evidence should be: A stress test admits or rejects reservations according to the per-class budget without starving the protected class.

Incorrect Answers

A:

Record reoptimization stability and path-change rate in monitoring. That is a sensible control for ANOTHER scenario: A tunnel between regional PEs oscillates because an optimizer recomputes explicit paths on every small telemetry fluctuation. It is less targeted to this issue than: Track class-type utilization and validate reservation boundaries after QoS changes.

B:

Test preemption conditions and impact warnings before new tunnel activation. That is a sensible control for ANOTHER scenario: A provider enables RSVP bandwidth reservation but leaves all tunnels with one identical setup and holding priority, making critical voice LSP preemption unpredictable. It is less targeted to this issue than: Track class-type utilization and validate reservation boundaries after QoS changes.

D:

Monitor adjacency SID changes and invalidate stale policy segment lists. That is a sensible control for ANOTHER scenario: A headend constructs an SR policy from adjacency SIDs but one adjacency SID identifies the wrong outbound interface after topology maintenance. It is less targeted to this issue than: Track class-type utilization and validate reservation boundaries after QoS changes.

Question 769

At a multi-tenant data transport provider, an engineering review finds: A router advertises a Prefix-SID for a loopback but another node's policy interprets the index as an adjacency segment and sends traffic out an unrelated interface. Which change most directly corrects the service problem?

  1. Identify segment types from the advertised IGP/BGP SID attributes and construct the policy with the correct Prefix-SID and adjacency-SID semantics.
  2. Recalculate the segment list using the current topology and correct adjacency SID advertisements before enabling the policy.
  3. Use IGP-distributed SIDs and supported SR policy steering without imposing unnecessary per-LSP RSVP signaling state.
  4. Configure consistent MPLS TTL propagation behavior appropriate to the private or visible core design.

Explanation

Correct Answer

A:

Identify segment types from the advertised IGP/BGP SID attributes and construct the policy with the correct Prefix-SID and adjacency-SID semantics. This directly addresses the fictional service-provider network case: A router advertises a Prefix-SID for a loopback but another node's policy interprets the index as an adjacency segment and sends traffic out an unrelated interface. The technical mechanism is: Prefix and adjacency segments have different endpoint and scope semantics in SR-MPLS forwarding. Verify success by: A route trace follows the destination node for the prefix segment and only the intended local link for adjacency segments.

Incorrect Answers

B:

Recalculate the segment list using the current topology and correct adjacency SID advertisements before enabling the policy. This would respond to a DIFFERENT fictional service-provider network issue: A headend constructs an SR policy from adjacency SIDs but one adjacency SID identifies the wrong outbound interface after topology maintenance. It does not directly address the current situation: A router advertises a Prefix-SID for a loopback but another node's policy interprets the index as an adjacency segment and sends traffic out an unrelated interface.

C:

Use IGP-distributed SIDs and supported SR policy steering without imposing unnecessary per-LSP RSVP signaling state. This would respond to a DIFFERENT fictional service-provider network issue: A provider enables SR-MPLS forwarding but assumes each SR-TE path requires RSVP-TE state on every transit router, blocking deployment when RSVP is disabled. It does not directly address the current situation: A router advertises a Prefix-SID for a loopback but another node's policy interprets the index as an adjacency segment and sends traffic out an unrelated interface.

D:

Configure consistent MPLS TTL propagation behavior appropriate to the private or visible core design. This would respond to a DIFFERENT fictional service-provider network issue: A router's MPLS TTL propagation policy differs from its neighboring core nodes, and traceroute unexpectedly exposes or hides provider hops relative to the service contract. It does not directly address the current situation: A router advertises a Prefix-SID for a loopback but another node's policy interprets the index as an adjacency segment and sends traffic out an unrelated interface.

Question 770

For a multi-tenant data transport provider, operators addressed: A router advertises a Prefix-SID for a loopback but another node's policy interprets the index as an adjacency segment and sends traffic out an unrelated interface. What is the strongest acceptance evidence?

  1. Policy state selects the highest eligible preference candidate and traffic follows its listed segments.
  2. A route trace follows the destination node for the prefix segment and only the intended local link for adjacency segments.
  3. The PCC installs only approved delegated candidates and reports their active state back to the PCE.
  4. RSVP PATH and RESV state establish across the intended nodes and the LSP forwards test traffic.

Explanation

Correct Answer

B:

A route trace follows the destination node for the prefix segment and only the intended local link for adjacency segments. This confirms the approved response: Identify segment types from the advertised IGP/BGP SID attributes and construct the policy with the correct Prefix-SID and adjacency-SID semantics. It is relevant because: Prefix and adjacency segments have different endpoint and scope semantics in SR-MPLS forwarding.

Incorrect Answers

A:

Policy state selects the highest eligible preference candidate and traffic follows its listed segments. This would validate ANOTHER scenario: A carrier configures multiple SR policy candidate paths and expects the smallest latency metric to always win, but an explicitly higher-preference candidate overrides it. The specific correction here is: Identify segment types from the advertised IGP/BGP SID attributes and construct the policy with the correct Prefix-SID and adjacency-SID semantics.

C:

The PCC installs only approved delegated candidates and reports their active state back to the PCE. This would validate ANOTHER scenario: A PCE computes a low-latency SR-TE candidate, but the PCC ignores it because the PCEP session lacks authorization for delegated policy control. The specific correction here is: Identify segment types from the advertised IGP/BGP SID attributes and construct the policy with the correct Prefix-SID and adjacency-SID semantics.

D:

RSVP PATH and RESV state establish across the intended nodes and the LSP forwards test traffic. This would validate ANOTHER scenario: A provider changes an RSVP-TE tunnel to use an explicit path containing a router that lacks TE extensions, leaving the tunnel down despite IP reachability. The specific correction here is: Identify segment types from the advertised IGP/BGP SID attributes and construct the policy with the correct Prefix-SID and adjacency-SID semantics.