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 47

Question 460

After addressing: A service provider exports VPNv4 labels across multiple autonomous regions but assumes LDP sessions must directly span every access network and interregion core. Which recurring service assurance check is most useful?

  1. Include transport and service-layer OAM in VPN fault playbooks.
  2. Include crossregion label-stack tracing in service acceptance.
  3. Measure end-to-end label-stack MTU at every new pseudowire deployment.
  4. Include TE database completeness checks during IGP maintenance.

Explanation

Correct Answer

B:

Include crossregion label-stack tracing in service acceptance. This helps prevent recurrence of the issue: A service provider exports VPNv4 labels across multiple autonomous regions but assumes LDP sessions must directly span every access network and interregion core. Acceptance evidence should be: A service prefix traverses the core layers with valid outer transport labels and correct VPN label disposition at the egress PE.

Incorrect Answers

A:

Include transport and service-layer OAM in VPN fault playbooks. That is a sensible control for ANOTHER scenario: A provider applies MPLS LSP ping only to the global transport loopback while a customer L3VPN remains broken, then claims VPN reachability is fully proven. It is less targeted to this issue than: Include crossregion label-stack tracing in service acceptance.

C:

Measure end-to-end label-stack MTU at every new pseudowire deployment. That is a sensible control for ANOTHER scenario: An MPLS pseudowire intermittently drops large customer frames after VLAN tagging increases payload size beyond a transit link's supported frame budget. It is less targeted to this issue than: Include crossregion label-stack tracing in service acceptance.

D:

Include TE database completeness checks during IGP maintenance. That is a sensible control for 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. It is less targeted to this issue than: Include crossregion label-stack tracing in service acceptance.

Question 461

A provider backbone escalation identifies: A traffic engineering policy considers only link bandwidth when selecting primary and backup paths, but both use one optical shared-risk group. What should the network team implement?

  1. Configure and verify compatible facility or one-to-one local repair for the critical protected link.
  2. Correct class-type bandwidth model and bandwidth constraints to match the provider's differentiated service policy.
  3. Recalculate the segment list using the current topology and correct adjacency SID advertisements before enabling the policy.
  4. Include available shared-risk link group constraints or explicit path diversity in TE computation.

Explanation

Correct Answer

D:

Include available shared-risk link group constraints or explicit path diversity in TE computation. This directly addresses the fictional service-provider network case: A traffic engineering policy considers only link bandwidth when selecting primary and backup paths, but both use one optical shared-risk group. The technical mechanism is: Topological links can share a lower-layer failure domain that must be represented in TE protection constraints. Verify success by: Simulated loss of one shared optical component leaves the backup LSP on a truly independent facility.

Incorrect Answers

A:

Configure and verify compatible facility or one-to-one local repair for the critical protected link. This would respond to a DIFFERENT fictional service-provider network issue: A primary RSVP-TE tunnel fails and no local FRR detour is active, forcing slow headend reconvergence during a protected fiber cut. It does not directly address the current situation: A traffic engineering policy considers only link bandwidth when selecting primary and backup paths, but both use one optical shared-risk group.

B:

Correct class-type bandwidth model and bandwidth constraints to match the provider's differentiated service policy. This would respond to a DIFFERENT fictional service-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. It does not directly address the current situation: A traffic engineering policy considers only link bandwidth when selecting primary and backup paths, but both use one optical shared-risk group.

C:

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 traffic engineering policy considers only link bandwidth when selecting primary and backup paths, but both use one optical shared-risk group.

Question 462

A service-provider operations test targets: A traffic engineering policy considers only link bandwidth when selecting primary and backup paths, but both use one optical shared-risk group. Which result is required?

  1. Simulated loss of one shared optical component leaves the backup LSP on a truly independent facility.
  2. Available TE reservable bandwidth rises in line with released legitimate reservations without changing the physical capacity.
  3. Traffic remains on an eligible path through small utilization variations and moves only after a meaningful sustained threshold is crossed.
  4. Each router's label forwarding view leads to the same prefix destination despite different permitted local SRGB labels.

Explanation

Correct Answer

A:

Simulated loss of one shared optical component leaves the backup LSP on a truly independent facility. This confirms the approved response: Include available shared-risk link group constraints or explicit path diversity in TE computation. It is relevant because: Topological links can share a lower-layer failure domain that must be represented in TE protection constraints.

Incorrect Answers

B:

Available TE reservable bandwidth rises in line with released legitimate reservations without changing the physical capacity. This would validate ANOTHER scenario: One router reports TE bandwidth exhausted even though link counters show the circuit nearly idle, and operators increase interface speed without investigating reservations. The specific correction here is: Include available shared-risk link group constraints or explicit path diversity in TE computation.

C:

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: Include available shared-risk link group constraints or explicit path diversity in TE computation.

D:

Each router's label forwarding view leads to the same prefix destination despite different permitted local SRGB labels. This would validate 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. The specific correction here is: Include available shared-risk link group constraints or explicit path diversity in TE computation.

Question 463

A provider troubleshooting note states: A traffic engineering policy considers only link bandwidth when selecting primary and backup paths, but both use one optical shared-risk group. Which mechanism is central?

  1. Link-state TE extensions carry topology attributes beyond ordinary SPF metrics for path computation.
  2. Topological links can share a lower-layer failure domain that must be represented in TE protection constraints.
  3. RSVP-TE supports priority-based reservation and preemption to allocate scarce transport resources.
  4. LDP discovery and its subsequent transport session are separate stages with independent failure conditions.

Explanation

Correct Answer

B:

Topological links can share a lower-layer failure domain that must be represented in TE protection constraints. This explains the investigated issue: A traffic engineering policy considers only link bandwidth when selecting primary and backup paths, but both use one optical shared-risk group. The approved corrective response is: Include available shared-risk link group constraints or explicit path diversity in TE computation.

Incorrect Answers

A:

Link-state TE extensions carry topology attributes beyond ordinary SPF metrics for path computation. That explains a DIFFERENT 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 mechanism to prioritize for this question is: Topological links can share a lower-layer failure domain that must be represented in TE protection constraints.

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: Topological links can share a lower-layer failure domain that must be represented in TE protection constraints.

D:

LDP discovery and its subsequent transport session are separate stages with independent failure conditions. That explains a DIFFERENT scenario: Two neighboring MPLS routers use different LDP authentication credentials and fail to form a TCP session even though UDP discovery hellos arrive. The mechanism to prioritize for this question is: Topological links can share a lower-layer failure domain that must be represented in TE protection constraints.

Question 464

To prevent recurrence of this provider network issue: A traffic engineering policy considers only link bandwidth when selecting primary and backup paths, but both use one optical shared-risk group. Which control should be retained?

  1. Validate explicit-route hops against TE capability data before committing.
  2. Verify data-plane steering separately from RSVP session state.
  3. Maintain optical SRLG metadata with core IGP-TE inventory.
  4. Alert on mismatched IGP FEC and LFIB installation counters.

Explanation

Correct Answer

C:

Maintain optical SRLG metadata with core IGP-TE inventory. This helps prevent recurrence of the issue: A traffic engineering policy considers only link bandwidth when selecting primary and backup paths, but both use one optical shared-risk group. Acceptance evidence should be: Simulated loss of one shared optical component leaves the backup LSP on a truly independent facility.

Incorrect Answers

A:

Validate explicit-route hops against TE capability data before committing. That is a sensible control for 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. It is less targeted to this issue than: Maintain optical SRLG metadata with core IGP-TE inventory.

B:

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: Maintain optical SRLG metadata with core IGP-TE inventory.

D:

Alert on mismatched IGP FEC and LFIB installation counters. That is a sensible control for ANOTHER 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. It is less targeted to this issue than: Maintain optical SRLG metadata with core IGP-TE inventory.

Question 465

At a global tier-one IP transit carrier, an engineering review finds: During a P-router failure, Ti-LFA repair is expected but no backup next hop is installed because one adjacent link is excluded from the repair topology. Which change most directly corrects the service problem?

  1. Validate TI-LFA eligibility, link/node protection constraints and the repair path toward the intended destination.
  2. Align Prefix-SID index planning and understand per-node SRGB label calculation so the intended segment resolves correctly.
  3. Bind the service SID's decapsulation and table lookup behavior to the intended customer VRF.
  4. Replace the strict path element with supported TE-capable nodes or adjust the explicit route to a valid engineered path.

Explanation

Correct Answer

A:

Validate TI-LFA eligibility, link/node protection constraints and the repair path toward the intended destination. This directly addresses the fictional service-provider network case: During a P-router failure, Ti-LFA repair is expected but no backup next hop is installed because one adjacent link is excluded from the repair topology. The technical mechanism is: Topology-Independent Loop-Free Alternate mechanisms depend on available SID repair paths and correct topological information. Verify success by: A controlled transit-node failure uses the precomputed repair path within the stated local restoration target.

Incorrect Answers

B:

Align Prefix-SID index planning and understand per-node SRGB label calculation so the intended segment resolves correctly. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: During a P-router failure, Ti-LFA repair is expected but no backup next hop is installed because one adjacent link is excluded from the repair topology.

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: During a P-router failure, Ti-LFA repair is expected but no backup next hop is installed because one adjacent link is excluded from the repair topology.

D:

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: During a P-router failure, Ti-LFA repair is expected but no backup next hop is installed because one adjacent link is excluded from the repair topology.

Question 466

For a global tier-one IP transit carrier, operators addressed: During a P-router failure, Ti-LFA repair is expected but no backup next hop is installed because one adjacent link is excluded from the repair topology. What is the strongest acceptance evidence?

  1. A worst-case policy passes a documented Maximum SID Depth check and forwards test packets end-to-end.
  2. A controlled transit-node failure uses the precomputed repair path within the stated local restoration target.
  3. Policy state selects the highest eligible preference candidate and traffic follows its listed segments.
  4. Available TE reservable bandwidth rises in line with released legitimate reservations without changing the physical capacity.

Explanation

Correct Answer

B:

A controlled transit-node failure uses the precomputed repair path within the stated local restoration target. This confirms the approved response: Validate TI-LFA eligibility, link/node protection constraints and the repair path toward the intended destination. It is relevant because: Topology-Independent Loop-Free Alternate mechanisms depend on available SID repair paths and correct topological information.

Incorrect Answers

A:

A worst-case policy passes a documented Maximum SID Depth check and forwards test packets end-to-end. This would validate ANOTHER scenario: The headend imposes an SR-MPLS list of eight SIDs on a platform supporting only six, causing only complex engineered paths to fail. The specific correction here is: Validate TI-LFA eligibility, link/node protection constraints and the repair path toward the intended destination.

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: Validate TI-LFA eligibility, link/node protection constraints and the repair path toward the intended destination.

D:

Available TE reservable bandwidth rises in line with released legitimate reservations without changing the physical capacity. This would validate ANOTHER scenario: One router reports TE bandwidth exhausted even though link counters show the circuit nearly idle, and operators increase interface speed without investigating reservations. The specific correction here is: Validate TI-LFA eligibility, link/node protection constraints and the repair path toward the intended destination.

Question 467

Which network protocol or forwarding behavior explains the following issue: During a P-router failure, Ti-LFA repair is expected but no backup next hop is installed because one adjacent link is excluded from the repair topology.

  1. Prefix-SID indexes are interpreted through each node's advertised Segment Routing Global Block, not as universally identical label values.
  2. An SR policy defines an engineered path but requires steering to affect user traffic.
  3. Topology-Independent Loop-Free Alternate mechanisms depend on available SID repair paths and correct topological information.
  4. Make-before-break can retain service continuity while TE paths are re-signaled, provided temporary bandwidth and state exist.

Explanation

Correct Answer

C:

Topology-Independent Loop-Free Alternate mechanisms depend on available SID repair paths and correct topological information. This explains the investigated issue: During a P-router failure, Ti-LFA repair is expected but no backup next hop is installed because one adjacent link is excluded from the repair topology. The approved corrective response is: Validate TI-LFA eligibility, link/node protection constraints and the repair path toward the intended destination.

Incorrect Answers

A:

Prefix-SID indexes are interpreted through each node's advertised Segment Routing Global Block, not as universally identical label values. That explains a DIFFERENT 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. The mechanism to prioritize for this question is: Topology-Independent Loop-Free Alternate mechanisms depend on available SID repair paths and correct topological information.

B:

An SR policy defines an engineered path but requires steering to affect user traffic. That explains a DIFFERENT scenario: A Segment Routing policy is installed but no customer route is steered to its binding SID, so measured traffic still follows ordinary IGP shortest paths. The mechanism to prioritize for this question is: Topology-Independent Loop-Free Alternate mechanisms depend on available SID repair paths and correct topological information.

D:

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: Topology-Independent Loop-Free Alternate mechanisms depend on available SID repair paths and correct topological information.

Question 468

A core network change board wants to avoid: During a P-router failure, Ti-LFA repair is expected but no backup next hop is installed because one adjacent link is excluded from the repair topology. Which ongoing safeguard fits best?

  1. Monitor delegated LSP ownership and controller reachability.
  2. Monitor adjacency SID changes and invalidate stale policy segment lists.
  3. Check IGP and LDP FEC consistency at every interregion boundary.
  4. Audit protected-prefix coverage before deploying TI-LFA claims.

Explanation

Correct Answer

D:

Audit protected-prefix coverage before deploying TI-LFA claims. This helps prevent recurrence of the issue: During a P-router failure, Ti-LFA repair is expected but no backup next hop is installed because one adjacent link is excluded from the repair topology. Acceptance evidence should be: A controlled transit-node failure uses the precomputed repair path within the stated local restoration target.

Incorrect Answers

A:

Monitor delegated LSP ownership and controller reachability. That is a sensible control for 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. It is less targeted to this issue than: Audit protected-prefix coverage before deploying TI-LFA claims.

B:

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: Audit protected-prefix coverage before deploying TI-LFA claims.

C:

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: Audit protected-prefix coverage before deploying TI-LFA claims.

Question 469

A carrier service activation check discovers: A wholesale carrier provides carrier-supporting-carrier transport, but a subcontractor PE advertises customer routes into the infrastructure global table rather than using labeled backbone service separation. Which action best restores the intended behavior?

  1. Select the supported Rosen or next-generation mVPN transport model and appropriate provider multicast tree design for the scale.
  2. Use the supported Carrier Supporting Carrier VPN transport design and preserve customer route isolation across the wholesale boundary.
  3. Align Ethernet Segment Identifier, DF election and split-horizon signaling on the multihomed PEs.
  4. Re-mark untrusted customer CS6 traffic according to the provider ingress trust policy while preserving genuine internal control traffic treatment.

Explanation

Correct Answer

B:

Use the supported Carrier Supporting Carrier VPN transport design and preserve customer route isolation across the wholesale boundary. This directly addresses the fictional service-provider network case: A wholesale carrier provides carrier-supporting-carrier transport, but a subcontractor PE advertises customer routes into the infrastructure global table rather than using labeled backbone service separation. The technical mechanism is: CSC designs carry another provider's traffic through a backbone without exposing all downstream customer routes into the carrier core. Verify success by: Customer-specific VPN routes remain in the authorized routing context and other carrier customers cannot import them.

Incorrect Answers

A:

Select the supported Rosen or next-generation mVPN transport model and appropriate provider multicast tree design for the scale. This would respond to a DIFFERENT fictional service-provider network issue: A provider deploys mVPN for an IPTV customer but replicates each source stream individually to every access PE even when a shared provider multicast tree is available. It does not directly address the current situation: A wholesale carrier provides carrier-supporting-carrier transport, but a subcontractor PE advertises customer routes into the infrastructure global table rather than using labeled backbone service separation.

C:

Align Ethernet Segment Identifier, DF election and split-horizon signaling on the multihomed PEs. This would respond to a DIFFERENT fictional service-provider network issue: An EVPN multihoming access service floods duplicates during an all-active ESI failover because designated forwarder election states disagree. It does not directly address the current situation: A wholesale carrier provides carrier-supporting-carrier transport, but a subcontractor PE advertises customer routes into the infrastructure global table rather than using labeled backbone service separation.

D:

Re-mark untrusted customer CS6 traffic according to the provider ingress trust policy while preserving genuine internal control traffic treatment. This would respond to a DIFFERENT fictional service-provider network issue: A customer sends traffic marked CS6 from its access port and expects unlimited priority throughout the provider despite not purchasing a network-control service class. It does not directly address the current situation: A wholesale carrier provides carrier-supporting-carrier transport, but a subcontractor PE advertises customer routes into the infrastructure global table rather than using labeled backbone service separation.

Question 470

Following a supported configuration correction, the original issue was: A wholesale carrier provides carrier-supporting-carrier transport, but a subcontractor PE advertises customer routes into the infrastructure global table rather than using labeled backbone service separation. Which observation verifies success?

  1. Two test customers using the same group address receive only their own authorized source streams.
  2. A remote customer VRF imports the approved prefix and delivers labeled packets across both provider ASes.
  3. Customer-specific VPN routes remain in the authorized routing context and other carrier customers cannot import them.
  4. A double-tagged test from each customer arrives at the correct logical service with its contracted inner VLAN intact.

Explanation

Correct Answer

C:

Customer-specific VPN routes remain in the authorized routing context and other carrier customers cannot import them. This confirms the approved response: Use the supported Carrier Supporting Carrier VPN transport design and preserve customer route isolation across the wholesale boundary. It is relevant because: CSC designs carry another provider's traffic through a backbone without exposing all downstream customer routes into the carrier core.

Incorrect Answers

A:

Two test customers using the same group address receive only their own authorized source streams. This would validate ANOTHER scenario: A multicast VPN customer uses overlapping group addresses with another tenant, and the service provider combines the flows into one global multicast state. The specific correction here is: Use the supported Carrier Supporting Carrier VPN transport design and preserve customer route isolation across the wholesale boundary.

B:

A remote customer VRF imports the approved prefix and delivers labeled packets across both provider ASes. This would validate ANOTHER scenario: An inter-AS L3VPN reaches the first provider but customer prefixes vanish at the AS boundary because VPNv4 routes and label context are not exchanged under the chosen inter-AS model. The specific correction here is: Use the supported Carrier Supporting Carrier VPN transport design and preserve customer route isolation across the wholesale boundary.

D:

A double-tagged test from each customer arrives at the correct logical service with its contracted inner VLAN intact. This would validate ANOTHER scenario: A wholesale Ethernet access provider uses an 802.1ad QinQ handoff but pops both tags before the customer PE, collapsing two independent service instances. The specific correction here is: Use the supported Carrier Supporting Carrier VPN transport design and preserve customer route isolation across the wholesale boundary.