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 76

Question 750

A service-provider operations test targets: 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. Which result is required?

  1. The tunnel's protection state indicates the intended scope and a targeted failure test uses the proper bypass.
  2. Traffic remains on an eligible path through small utilization variations and moves only after a meaningful sustained threshold is crossed.
  3. The replacement LSP becomes usable before the previous one is torn down in an acceptance test.
  4. During a single-link failure the session remains protected through the alternative route and bound FECs recover safely.

Explanation

Correct Answer

A:

The tunnel's protection state indicates the intended scope and a targeted failure test uses the proper bypass. This confirms the approved response: Align the requested bypass protection type with available disjoint repair paths and verify coverage for the protected node or link. It is relevant because: Local protection for a link and local protection for a full node require different bypass topology constraints.

Incorrect Answers

B:

Traffic remains on an eligible path through small utilization variations and moves only after a meaningful sustained threshold is crossed. This would validate ANOTHER scenario: A tunnel between regional PEs oscillates because an optimizer recomputes explicit paths on every small telemetry fluctuation. The specific correction here is: Align the requested bypass protection type with available disjoint repair paths and verify coverage for the protected node or link.

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: Align the requested bypass protection type with available disjoint repair paths and verify coverage for the protected node or link.

D:

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: Align the requested bypass protection type with available disjoint repair paths and verify coverage for the protected node or link.

Question 751

A provider troubleshooting note states: 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. Which mechanism is central?

  1. MPLS TE Fast Reroute prepares local bypass forwarding before a failure is detected.
  2. Local protection for a link and local protection for a full node require different bypass topology constraints.
  3. RSVP-TE explicit routing requires nodes along the selected path to support the signaling and advertised TE topology.
  4. A label binding without reachable next-hop context is insufficient to deliver a usable MPLS transport LSP.

Explanation

Correct Answer

B:

Local protection for a link and local protection for a full node require different bypass topology constraints. This explains the investigated 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. The approved corrective response is: Align the requested bypass protection type with available disjoint repair paths and verify coverage for the protected node or link.

Incorrect Answers

A:

MPLS TE Fast Reroute prepares local bypass forwarding before a failure is detected. That explains a DIFFERENT scenario: A primary RSVP-TE tunnel fails and no local FRR detour is active, forcing slow headend reconvergence during a protected fiber cut. The mechanism to prioritize for this question is: Local protection for a link and local protection for a full node require different bypass topology constraints.

C:

RSVP-TE explicit routing requires nodes along the selected path to support the signaling and advertised TE topology. That explains a DIFFERENT 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 mechanism to prioritize for this question is: Local protection for a link and local protection for a full node require different bypass topology constraints.

D:

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: Local protection for a link and local protection for a full node require different bypass topology constraints.

Question 752

To prevent recurrence of this 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. Which control should be retained?

  1. Maintain optical SRLG metadata with core IGP-TE inventory.
  2. Track class-type utilization and validate reservation boundaries after QoS changes.
  3. Test the exact failure class named in each protection service objective.
  4. Validate SID index and SRGB advertisements during node onboarding.

Explanation

Correct Answer

C:

Test the exact failure class named in each protection service objective. This helps prevent recurrence of the 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. Acceptance evidence should be: The tunnel's protection state indicates the intended scope and a targeted failure test uses the proper bypass.

Incorrect Answers

A:

Maintain optical SRLG metadata with core IGP-TE inventory. That is a sensible control for ANOTHER scenario: A traffic engineering policy considers only link bandwidth when selecting primary and backup paths, but both use one optical shared-risk group. It is less targeted to this issue than: Test the exact failure class named in each protection service objective.

B:

Track class-type utilization and validate reservation boundaries after QoS changes. That is a sensible control for ANOTHER scenario: 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. It is less targeted to this issue than: Test the exact failure class named in each protection service objective.

D:

Validate SID index and SRGB advertisements during node onboarding. That is a sensible control for ANOTHER scenario: An operator configures an SR-MPLS Prefix-SID for a PE loopback, but different routers assign inconsistent SID indexes relative to their SRGB ranges, causing label misinterpretation. It is less targeted to this issue than: Test the exact failure class named in each protection service objective.

Question 753

At a managed VPN service carrier, an engineering review finds: The headend imposes an SR-MPLS list of eight SIDs on a platform supporting only six, causing only complex engineered paths to fail. Which change most directly corrects the service problem?

  1. Shorten the policy with supported binding SIDs or select hardware capable of the required maximum SID depth.
  2. Align PCE-PCC session capabilities and authenticated delegated SR policy configuration with the provider's control rules.
  3. Bind the service SID's decapsulation and table lookup behavior to the intended customer VRF.
  4. Align authorized LDP session authentication and transport addresses on the intended peers.

Explanation

Correct Answer

A:

Shorten the policy with supported binding SIDs or select hardware capable of the required maximum SID depth. This directly addresses the fictional service-provider network case: The headend imposes an SR-MPLS list of eight SIDs on a platform supporting only six, causing only complex engineered paths to fail. The technical mechanism is: Segment Routing policy feasibility is constrained by how many segment labels the headend or transit hardware can impose. Verify success by: A worst-case policy passes a documented Maximum SID Depth check and forwards test packets end-to-end.

Incorrect Answers

B:

Align PCE-PCC session capabilities and authenticated delegated SR policy configuration with the provider's control rules. This would respond to a DIFFERENT fictional service-provider network issue: A PCE computes a low-latency SR-TE candidate, but the PCC ignores it because the PCEP session lacks authorization for delegated policy control. It does not directly address the current situation: The headend imposes an SR-MPLS list of eight SIDs on a platform supporting only six, causing only complex engineered paths to fail.

C:

Bind the service SID's decapsulation and table lookup behavior to the intended customer VRF. This would respond to a DIFFERENT fictional service-provider network issue: An SRv6 egress router discards traffic because a local End.DT4 service SID is placed in the wrong VRF context, even though the locator is reachable. It does not directly address the current situation: The headend imposes an SR-MPLS list of eight SIDs on a platform supporting only six, causing only complex engineered paths to fail.

D:

Align authorized LDP session authentication and transport addresses on the intended peers. This would respond to a DIFFERENT fictional service-provider network issue: Two neighboring MPLS routers use different LDP authentication credentials and fail to form a TCP session even though UDP discovery hellos arrive. It does not directly address the current situation: The headend imposes an SR-MPLS list of eight SIDs on a platform supporting only six, causing only complex engineered paths to fail.

Question 754

For a managed VPN service carrier, operators addressed: The headend imposes an SR-MPLS list of eight SIDs on a platform supporting only six, causing only complex engineered paths to fail. What is the strongest acceptance evidence?

  1. The PCC installs only approved delegated candidates and reports their active state back to the PCE.
  2. A worst-case policy passes a documented Maximum SID Depth check and forwards test packets end-to-end.
  3. Policy state selects the highest eligible preference candidate and traffic follows its listed segments.
  4. Test traceroutes and MPLS packet TTL values match the intended customer visibility policy across the path.

Explanation

Correct Answer

B:

A worst-case policy passes a documented Maximum SID Depth check and forwards test packets end-to-end. This confirms the approved response: Shorten the policy with supported binding SIDs or select hardware capable of the required maximum SID depth. It is relevant because: Segment Routing policy feasibility is constrained by how many segment labels the headend or transit hardware can impose.

Incorrect Answers

A:

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: Shorten the policy with supported binding SIDs or select hardware capable of the required maximum SID depth.

C:

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: Shorten the policy with supported binding SIDs or select hardware capable of the required maximum SID depth.

D:

Test traceroutes and MPLS packet TTL values match the intended customer visibility policy across the path. This would validate ANOTHER scenario: 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. The specific correction here is: Shorten the policy with supported binding SIDs or select hardware capable of the required maximum SID depth.

Question 755

Which network protocol or forwarding behavior explains the following issue: The headend imposes an SR-MPLS list of eight SIDs on a platform supporting only six, causing only complex engineered paths to fail.

  1. Prefix and adjacency segments have different endpoint and scope semantics in SR-MPLS forwarding.
  2. Segment Routing can encode forwarding instructions in the packet and reduce dependency on per-tunnel transit RSVP state.
  3. Segment Routing policy feasibility is constrained by how many segment labels the headend or transit hardware can impose.
  4. MPLS label forwarding depends on consistency among route reachability, label bindings and hardware forwarding entries.

Explanation

Correct Answer

C:

Segment Routing policy feasibility is constrained by how many segment labels the headend or transit hardware can impose. This explains the investigated issue: The headend imposes an SR-MPLS list of eight SIDs on a platform supporting only six, causing only complex engineered paths to fail. The approved corrective response is: Shorten the policy with supported binding SIDs or select hardware capable of the required maximum SID depth.

Incorrect Answers

A:

Prefix and adjacency segments have different endpoint and scope semantics in SR-MPLS forwarding. That explains a DIFFERENT scenario: 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 mechanism to prioritize for this question is: Segment Routing policy feasibility is constrained by how many segment labels the headend or transit hardware can impose.

B:

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: Segment Routing policy feasibility is constrained by how many segment labels the headend or transit hardware can impose.

D:

MPLS label forwarding depends on consistency among route reachability, label bindings and hardware forwarding entries. That explains a DIFFERENT scenario: 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. The mechanism to prioritize for this question is: Segment Routing policy feasibility is constrained by how many segment labels the headend or transit hardware can impose.

Question 756

A core network change board wants to avoid: The headend imposes an SR-MPLS list of eight SIDs on a platform supporting only six, causing only complex engineered paths to fail. Which ongoing safeguard fits best?

  1. Keep segment-type validation with path computation requests.
  2. Verify local SID behaviors and VRF bindings during VPN service provisioning.
  3. Verify LDP discovery, transport and authentication status during peer certification.
  4. Include MSD capability checks in every SR policy computation.

Explanation

Correct Answer

D:

Include MSD capability checks in every SR policy computation. This helps prevent recurrence of the issue: The headend imposes an SR-MPLS list of eight SIDs on a platform supporting only six, causing only complex engineered paths to fail. Acceptance evidence should be: A worst-case policy passes a documented Maximum SID Depth check and forwards test packets end-to-end.

Incorrect Answers

A:

Keep segment-type validation with path computation requests. That is a sensible control for ANOTHER scenario: 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. It is less targeted to this issue than: Include MSD capability checks in every SR policy computation.

B:

Verify local SID behaviors and VRF bindings during VPN service provisioning. That is a sensible control for ANOTHER scenario: An SRv6 egress router discards traffic because a local End.DT4 service SID is placed in the wrong VRF context, even though the locator is reachable. It is less targeted to this issue than: Include MSD capability checks in every SR policy computation.

C:

Verify LDP discovery, transport and authentication status during peer certification. That is a sensible control for ANOTHER scenario: Two neighboring MPLS routers use different LDP authentication credentials and fail to form a TCP session even though UDP discovery hellos arrive. It is less targeted to this issue than: Include MSD capability checks in every SR policy computation.

Question 757

A carrier service activation check discovers: An enterprise customer is promised IPv6 VPN reachability but the PE provisions only VPNv4 MP-BGP and v4 VRF interfaces. Which action best restores the intended behavior?

  1. Assign service-specific route targets and restrict import policy to the approved tenant set.
  2. Enable supported IPv6 VRF address family and VPNv6 route exchange with matching route targets.
  3. Update the PE-CE routing and VPNv4 advertisement then withdraw obsolete routes after reachability validation.
  4. Terminate the provider backbone encapsulation at the correct I-component/B-component service edge.

Explanation

Correct Answer

B:

Enable supported IPv6 VRF address family and VPNv6 route exchange with matching route targets. This directly addresses the fictional service-provider network case: An enterprise customer is promised IPv6 VPN reachability but the PE provisions only VPNv4 MP-BGP and v4 VRF interfaces. The technical mechanism is: Dual-stack VPN services require address-family-specific interfaces and MP-BGP signaling. Verify success by: An IPv6 test prefix reaches the remote customer site without unintended mixing with IPv4-only service routing.

Incorrect Answers

A:

Assign service-specific route targets and restrict import policy to the approved tenant set. This would respond to a DIFFERENT fictional service-provider network issue: A provider advertises the same extranet shared-services prefix into two tenants, but a third tenant unexpectedly imports it because a generic RT is reused globally. It does not directly address the current situation: An enterprise customer is promised IPv6 VPN reachability but the PE provisions only VPNv4 MP-BGP and v4 VRF interfaces.

C:

Update the PE-CE routing and VPNv4 advertisement then withdraw obsolete routes after reachability validation. This would respond to a DIFFERENT fictional service-provider network issue: A carrier moves an enterprise's primary VPN site but retains an old CE static route in the remote VRF, steering packets to the retired PE. It does not directly address the current situation: An enterprise customer is promised IPv6 VPN reachability but the PE provisions only VPNv4 MP-BGP and v4 VRF interfaces.

D:

Terminate the provider backbone encapsulation at the correct I-component/B-component service edge. This would respond to a DIFFERENT fictional service-provider network issue: A carrier backbone applies provider bridging with 802.1ah MAC-in-MAC but its edge fails to strip the outer backbone header, so customer switches receive unknown backbone addresses. It does not directly address the current situation: An enterprise customer is promised IPv6 VPN reachability but the PE provisions only VPNv4 MP-BGP and v4 VRF interfaces.

Question 758

Following a supported configuration correction, the original issue was: An enterprise customer is promised IPv6 VPN reachability but the PE provisions only VPNv4 MP-BGP and v4 VRF interfaces. Which observation verifies success?

  1. A packet trace to the moved prefix follows the new PE while the retired next hop disappears from service routes.
  2. Customers reach the approved DNS endpoint but cross-customer reachability tests fail.
  3. An IPv6 test prefix reaches the remote customer site without unintended mixing with IPv4-only service routing.
  4. Peak-load packet captures retain the expected markings and voice delay and loss remain inside the service objective.

Explanation

Correct Answer

C:

An IPv6 test prefix reaches the remote customer site without unintended mixing with IPv4-only service routing. This confirms the approved response: Enable supported IPv6 VRF address family and VPNv6 route exchange with matching route targets. It is relevant because: Dual-stack VPN services require address-family-specific interfaces and MP-BGP signaling.

Incorrect Answers

A:

A packet trace to the moved prefix follows the new PE while the retired next hop disappears from service routes. This would validate ANOTHER scenario: A carrier moves an enterprise's primary VPN site but retains an old CE static route in the remote VRF, steering packets to the retired PE. The specific correction here is: Enable supported IPv6 VRF address family and VPNv6 route exchange with matching route targets.

B:

Customers reach the approved DNS endpoint but cross-customer reachability tests fail. This would validate ANOTHER scenario: A shared-services DNS VRF must serve three customer VRFs, but engineers import full customer route tables into the DNS VRF and unintentionally create broad extranet connectivity. The specific correction here is: Enable supported IPv6 VRF address family and VPNv6 route exchange with matching route targets.

D:

Peak-load packet captures retain the expected markings and voice delay and loss remain inside the service objective. This would validate ANOTHER scenario: A provider classifies customer voice using DSCP EF at ingress but a later output policy remarks it to best effort, causing jitter under congestion. The specific correction here is: Enable supported IPv6 VRF address family and VPNv6 route exchange with matching route targets.

Question 759

At a regional peering-exchange operator, an engineer examines: An enterprise customer is promised IPv6 VPN reachability but the PE provisions only VPNv4 MP-BGP and v4 VRF interfaces. Which technical principle is most applicable?

  1. L3VPN shared services are built with intentional route leaking and must not automatically merge entire tenant routing tables.
  2. VPN routing can preserve stale more-specific or static routes that override newly learned paths.
  3. EVPN all-active multihoming relies on consistent Ethernet segment membership and designated forwarder behavior for BUM traffic.
  4. Dual-stack VPN services require address-family-specific interfaces and MP-BGP signaling.

Explanation

Correct Answer

D:

Dual-stack VPN services require address-family-specific interfaces and MP-BGP signaling. This explains the investigated issue: An enterprise customer is promised IPv6 VPN reachability but the PE provisions only VPNv4 MP-BGP and v4 VRF interfaces. The approved corrective response is: Enable supported IPv6 VRF address family and VPNv6 route exchange with matching route targets.

Incorrect Answers

A:

L3VPN shared services are built with intentional route leaking and must not automatically merge entire tenant routing tables. That explains a DIFFERENT scenario: A shared-services DNS VRF must serve three customer VRFs, but engineers import full customer route tables into the DNS VRF and unintentionally create broad extranet connectivity. The mechanism to prioritize for this question is: Dual-stack VPN services require address-family-specific interfaces and MP-BGP signaling.

B:

VPN routing can preserve stale more-specific or static routes that override newly learned paths. That explains a DIFFERENT scenario: A carrier moves an enterprise's primary VPN site but retains an old CE static route in the remote VRF, steering packets to the retired PE. The mechanism to prioritize for this question is: Dual-stack VPN services require address-family-specific interfaces and MP-BGP signaling.

C:

EVPN all-active multihoming relies on consistent Ethernet segment membership and designated forwarder behavior for BUM traffic. That explains a DIFFERENT scenario: An EVPN multihoming access service floods duplicates during an all-active ESI failover because designated forwarder election states disagree. The mechanism to prioritize for this question is: Dual-stack VPN services require address-family-specific interfaces and MP-BGP signaling.

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.