McAfee Secure

Cisco 350-501 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 Training 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

    Training Course

    253 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    1160 PDF Pages

    $24.99

Cisco 350-501 Practice Test 43

Question 420

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A policy wants packets to cross a preferred metro link that SPF would bypass, but engineers use only a remote node SID. Which continuing control best reduces recurrence of this problem?

  1. Record TTL propagation policy and perform approved MPLS path tracing after changes.
  2. Review path-switch frequency and traffic impact in maintenance reports.
  3. Validate link-restoration timing for both IGP and LDP after planned interruptions.
  4. Audit steering behavior after metric or topology changes.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: A policy wants packets to cross a preferred metro link that SPF would bypass, but engineers use only a remote node SID. The most directly supported response is: Use an appropriate adjacency SID or constrained SR policy segment list for explicit link steering. Technical basis: An SR node SID typically follows IGP shortest paths, while adjacency SIDs can encode a specific link. Evidence of success: Test packets traverse the intended adjacency rather than the default node shortest path. Ongoing protection: Audit steering behavior after metric or topology changes.

Incorrect Answers

A:

MPLS TTL handling influences transit expiration and visibility in MPLS traceroute. Maintaining that control would not track the failure described here. The relevant risk is: An SR node SID typically follows IGP shortest paths, while adjacency SIDs can encode a specific link. Review this instead: Audit steering behavior after metric or topology changes.

B:

Aggressive TE reoptimization can cause needless path churn even with valid alternate routes. Maintaining that control would not track the failure described here. The relevant risk is: An SR node SID typically follows IGP shortest paths, while adjacency SIDs can encode a specific link. Review this instead: Audit steering behavior after metric or topology changes.

C:

LDP-IGP synchronization coordinates packet-routing preference with label distribution readiness. Maintaining that control would not track the failure described here. The relevant risk is: An SR node SID typically follows IGP shortest paths, while adjacency SIDs can encode a specific link. Review this instead: Audit steering behavior after metric or topology changes.

Question 421

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An SR policy uses a valid segment list but ignores an SR-aware router's failure to resolve one required SID. What is the best authorized corrective or investigative action for this service-provider network operations situation?

  1. Assess RSVP-TE capability along every hop and choose a supported path or alternative technology.
  2. Repair SID advertisement and next-hop resolution before binding customer traffic to the policy.
  3. Configure supported FRR facility or one-to-one protection consistent with tunnel topology.
  4. Review MPLS TTL propagation and actual label stack processing across the provider core.

Explanation

Correct Answer

B:

For this scenario, the observed situation is: An SR policy uses a valid segment list but ignores an SR-aware router's failure to resolve one required SID. The most directly supported response is: Repair SID advertisement and next-hop resolution before binding customer traffic to the policy. Technical basis: An SRTE policy is usable only when its segment instructions resolve through supported topology. Evidence of success: The headend installs the intended segment list and the FIB resolves every segment. Ongoing protection: Continuously validate policy candidate-path resolution and fallback behavior.

Incorrect Answers

A:

The proposed option addresses this separate mechanism: RSVP-TE tunnel setup requires compatible signaling and resource support along the chosen route. The stated problem instead depends on: An SRTE policy is usable only when its segment instructions resolve through supported topology. The required response is: Repair SID advertisement and next-hop resolution before binding customer traffic to the policy.

C:

The option fits a control for: RSVP-TE FRR uses preplanned local bypass or detour paths for fast repair. The present failure is caused by a different mechanism: An SRTE policy is usable only when its segment instructions resolve through supported topology. The targeted implementation is: Repair SID advertisement and next-hop resolution before binding customer traffic to the policy.

D:

The option fits a control for: MPLS TTL handling influences transit expiration and visibility in MPLS traceroute. The present failure is caused by a different mechanism: An SRTE policy is usable only when its segment instructions resolve through supported topology. The targeted implementation is: Repair SID advertisement and next-hop resolution before binding customer traffic to the policy.

Question 422

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An SR policy uses a valid segment list but ignores an SR-aware router's failure to resolve one required SID. Which observable result most directly verifies that this network issue was resolved?

  1. The label database contains intended FEC mappings and unauthorized allocations stop appearing.
  2. A controlled protected-link failure reroutes the tunnel inside the engineered repair target.
  3. The LFIB switches labels consistently with the updated IGP shortest path.
  4. The headend installs the intended segment list and the FIB resolves every segment.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: An SR policy uses a valid segment list but ignores an SR-aware router's failure to resolve one required SID. The most directly supported response is: Repair SID advertisement and next-hop resolution before binding customer traffic to the policy. Technical basis: An SRTE policy is usable only when its segment instructions resolve through supported topology. Evidence of success: The headend installs the intended segment list and the FIB resolves every segment. Ongoing protection: Continuously validate policy candidate-path resolution and fallback behavior.

Incorrect Answers

A:

LDP bindings associate FECs with labels and can be constrained by control-plane policy. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: An SRTE policy is usable only when its segment instructions resolve through supported topology. A passing check should show: The headend installs the intended segment list and the FIB resolves every segment.

B:

The proposed test would be relevant to: RSVP-TE FRR uses preplanned local bypass or detour paths for fast repair. The reported problem follows from: An SRTE policy is usable only when its segment instructions resolve through supported topology. Instead, verify: The headend installs the intended segment list and the FIB resolves every segment.

C:

The proposed test would be relevant to: LDP label mappings are tied to FECs while forwarding next hops follow routed reachability. The reported problem follows from: An SRTE policy is usable only when its segment instructions resolve through supported topology. Instead, verify: The headend installs the intended segment list and the FIB resolves every segment.

Question 423

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An SR policy uses a valid segment list but ignores an SR-aware router's failure to resolve one required SID. Which underlying network infrastructure principle best explains the situation?

  1. LDP label mappings are tied to FECs while forwarding next hops follow routed reachability.
  2. Traffic engineering selects paths based on constraints beyond default shortest-path cost.
  3. Traffic engineering protection must consider physical shared-risk groups, not only logical hop diversity.
  4. An SRTE policy is usable only when its segment instructions resolve through supported topology.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: An SR policy uses a valid segment list but ignores an SR-aware router's failure to resolve one required SID. The most directly supported response is: Repair SID advertisement and next-hop resolution before binding customer traffic to the policy. Technical basis: An SRTE policy is usable only when its segment instructions resolve through supported topology. Evidence of success: The headend installs the intended segment list and the FIB resolves every segment. Ongoing protection: Continuously validate policy candidate-path resolution and fallback behavior.

Incorrect Answers

A:

The option explains a separate issue: LDP label mappings are tied to FECs while forwarding next hops follow routed reachability. The reported condition instead follows from: An SRTE policy is usable only when its segment instructions resolve through supported topology.

B:

The option explains a separate issue: Traffic engineering selects paths based on constraints beyond default shortest-path cost. The reported condition instead follows from: An SRTE policy is usable only when its segment instructions resolve through supported topology.

C:

The option explains a separate issue: Traffic engineering protection must consider physical shared-risk groups, not only logical hop diversity. The reported condition instead follows from: An SRTE policy is usable only when its segment instructions resolve through supported topology.

Question 424

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An SR policy uses a valid segment list but ignores an SR-aware router's failure to resolve one required SID. Which continuing control best reduces recurrence of this problem?

  1. Validate per-hop feature support before allocating customer TE products.
  2. Continuously validate policy candidate-path resolution and fallback behavior.
  3. Keep SRLG inventory current and test correlated fiber failures.
  4. Test final-hop label disposition after changing MPLS QoS design.

Explanation

Correct Answer

B:

For this scenario, the observed situation is: An SR policy uses a valid segment list but ignores an SR-aware router's failure to resolve one required SID. The most directly supported response is: Repair SID advertisement and next-hop resolution before binding customer traffic to the policy. Technical basis: An SRTE policy is usable only when its segment instructions resolve through supported topology. Evidence of success: The headend installs the intended segment list and the FIB resolves every segment. Ongoing protection: Continuously validate policy candidate-path resolution and fallback behavior.

Incorrect Answers

A:

The alternative guards against: RSVP-TE tunnel setup requires compatible signaling and resource support along the chosen route. The root condition for this case is: An SRTE policy is usable only when its segment instructions resolve through supported topology. The focused prevention check is: Continuously validate policy candidate-path resolution and fallback behavior.

C:

The alternative guards against: Traffic engineering protection must consider physical shared-risk groups, not only logical hop diversity. The root condition for this case is: An SRTE policy is usable only when its segment instructions resolve through supported topology. The focused prevention check is: Continuously validate policy candidate-path resolution and fallback behavior.

D:

That recurring practice manages a separate exposure: Explicit-null retains a label to the egress when required, whereas PHP can remove it earlier. The present case instead depends on: An SRTE policy is usable only when its segment instructions resolve through supported topology. The suitable ongoing safeguard is: Continuously validate policy candidate-path resolution and fallback behavior.

Question 425

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A backbone plans TI-LFA protection but the failed link's alternate path is not loop-free in the topology. What is the best authorized corrective or investigative action for this service-provider network operations situation?

  1. Assess RSVP-TE capability along every hop and choose a supported path or alternative technology.
  2. Check that newly selected routes still resolve through the correct downstream label bindings.
  3. Plan transport segmentation and labeled next-hop reachability across areas under a unified MPLS design.
  4. Compute a supported topology-independent loop-free alternate repair path for the protected destination.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: A backbone plans TI-LFA protection but the failed link's alternate path is not loop-free in the topology. The most directly supported response is: Compute a supported topology-independent loop-free alternate repair path for the protected destination. Technical basis: TI-LFA computes post-convergence-oriented local repair paths for segment-routing networks. Evidence of success: Failure testing shows packets avoid microloops and recover through the planned repair within target. Ongoing protection: Test protected-link and node failures with real traffic traces.

Incorrect Answers

A:

The option fits a control for: RSVP-TE tunnel setup requires compatible signaling and resource support along the chosen route. The present failure is caused by a different mechanism: TI-LFA computes post-convergence-oriented local repair paths for segment-routing networks. The targeted implementation is: Compute a supported topology-independent loop-free alternate repair path for the protected destination.

B:

The option fits a control for: LDP label mappings are tied to FECs while forwarding next hops follow routed reachability. The present failure is caused by a different mechanism: TI-LFA computes post-convergence-oriented local repair paths for segment-routing networks. The targeted implementation is: Compute a supported topology-independent loop-free alternate repair path for the protected destination.

C:

Unified MPLS extends labeled reachability across routing domains using supported BGP and IGP transport techniques. That principle governs the alternative intervention. The issue described here is different: TI-LFA computes post-convergence-oriented local repair paths for segment-routing networks. The case-matched corrective action is: Compute a supported topology-independent loop-free alternate repair path for the protected destination.

Question 426

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A backbone plans TI-LFA protection but the failed link's alternate path is not loop-free in the topology. Which observable result most directly verifies that this network issue was resolved?

  1. IGP cost returns to normal after LDP forms and initial VPN packets avoid the unlabeled link.
  2. Hop-by-hop LFIB entries exist along the route and test VPN packets reach the remote PE.
  3. Failure testing shows packets avoid microloops and recover through the planned repair within target.
  4. The TE database receives the expected link resources while ordinary reachability remains intact.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: A backbone plans TI-LFA protection but the failed link's alternate path is not loop-free in the topology. The most directly supported response is: Compute a supported topology-independent loop-free alternate repair path for the protected destination. Technical basis: TI-LFA computes post-convergence-oriented local repair paths for segment-routing networks. Evidence of success: Failure testing shows packets avoid microloops and recover through the planned repair within target. Ongoing protection: Test protected-link and node failures with real traffic traces.

Incorrect Answers

A:

The proposed test would be relevant to: LDP-IGP synchronization coordinates packet-routing preference with label distribution readiness. The reported problem follows from: TI-LFA computes post-convergence-oriented local repair paths for segment-routing networks. Instead, verify: Failure testing shows packets avoid microloops and recover through the planned repair within target.

B:

That observation tests a different mechanism: MPLS forwarding depends on an end-to-end usable label-switched transport path beneath service labels. It cannot establish this case, whose mechanism is: TI-LFA computes post-convergence-oriented local repair paths for segment-routing networks. The needed verification is: Failure testing shows packets avoid microloops and recover through the planned repair within target.

D:

That observation tests a different mechanism: IGP traffic engineering extensions advertise resource attributes distinct from normal SPF reachability. It cannot establish this case, whose mechanism is: TI-LFA computes post-convergence-oriented local repair paths for segment-routing networks. The needed verification is: Failure testing shows packets avoid microloops and recover through the planned repair within target.

Question 427

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A backbone plans TI-LFA protection but the failed link's alternate path is not loop-free in the topology. Which underlying network infrastructure principle best explains the situation?

  1. Explicit-null retains a label to the egress when required, whereas PHP can remove it earlier.
  2. TI-LFA computes post-convergence-oriented local repair paths for segment-routing networks.
  3. TE affinity constraints select links according to defined administrative groups.
  4. MPLS TTL handling influences transit expiration and visibility in MPLS traceroute.

Explanation

Correct Answer

B:

For this scenario, the observed situation is: A backbone plans TI-LFA protection but the failed link's alternate path is not loop-free in the topology. The most directly supported response is: Compute a supported topology-independent loop-free alternate repair path for the protected destination. Technical basis: TI-LFA computes post-convergence-oriented local repair paths for segment-routing networks. Evidence of success: Failure testing shows packets avoid microloops and recover through the planned repair within target. Ongoing protection: Test protected-link and node failures with real traffic traces.

Incorrect Answers

A:

The alternative principle describes: Explicit-null retains a label to the egress when required, whereas PHP can remove it earlier. In this question, the decisive mechanism is: TI-LFA computes post-convergence-oriented local repair paths for segment-routing networks. These are distinct technical causes, even when they share a platform.

C:

The alternative principle describes: TE affinity constraints select links according to defined administrative groups. In this question, the decisive mechanism is: TI-LFA computes post-convergence-oriented local repair paths for segment-routing networks. These are distinct technical causes, even when they share a platform.

D:

The alternative principle describes: MPLS TTL handling influences transit expiration and visibility in MPLS traceroute. In this question, the decisive mechanism is: TI-LFA computes post-convergence-oriented local repair paths for segment-routing networks. These are distinct technical causes, even when they share a platform.

Question 428

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A backbone plans TI-LFA protection but the failed link's alternate path is not loop-free in the topology. Which continuing control best reduces recurrence of this problem?

  1. Include MPLS enablement checks in core link turn-up tests.
  2. Test protection timers and alternate IP reachability during outages.
  3. Keep SRLG inventory current and test correlated fiber failures.
  4. Test protected-link and node failures with real traffic traces.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: A backbone plans TI-LFA protection but the failed link's alternate path is not loop-free in the topology. The most directly supported response is: Compute a supported topology-independent loop-free alternate repair path for the protected destination. Technical basis: TI-LFA computes post-convergence-oriented local repair paths for segment-routing networks. Evidence of success: Failure testing shows packets avoid microloops and recover through the planned repair within target. Ongoing protection: Test protected-link and node failures with real traffic traces.

Incorrect Answers

A:

That recurring practice manages a separate exposure: An IP routed adjacency does not itself establish an MPLS label-distribution session. The present case instead depends on: TI-LFA computes post-convergence-oriented local repair paths for segment-routing networks. The suitable ongoing safeguard is: Test protected-link and node failures with real traffic traces.

B:

That recurring practice manages a separate exposure: LDP session protection can retain a session across certain directly connected link disruptions. The present case instead depends on: TI-LFA computes post-convergence-oriented local repair paths for segment-routing networks. The suitable ongoing safeguard is: Test protected-link and node failures with real traffic traces.

C:

That recurring practice manages a separate exposure: Traffic engineering protection must consider physical shared-risk groups, not only logical hop diversity. The present case instead depends on: TI-LFA computes post-convergence-oriented local repair paths for segment-routing networks. The suitable ongoing safeguard is: Test protected-link and node failures with real traffic traces.

Question 429

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A PCE sends a recommended SR path to a headend that has not registered the required PCC session or delegation permission. What is the best authorized corrective or investigative action for this service-provider network operations situation?

  1. Establish the supported PCEP PCC-PCE relationship and authorize the intended path control.
  2. Trace the LFIB and IGP next-hop mapping to repair the underlying transport path.
  3. Design local repair paths with actual shared-risk link groups and diversity constraints.
  4. Review MPLS TTL propagation and actual label stack processing across the provider core.

Explanation

Correct Answer

A:

For this scenario, the observed situation is: A PCE sends a recommended SR path to a headend that has not registered the required PCC session or delegation permission. The most directly supported response is: Establish the supported PCEP PCC-PCE relationship and authorize the intended path control. Technical basis: PCE computes paths while PCCs maintain local network forwarding and policy state. Evidence of success: The PCC reports policy state and accepts the delegated candidate path within its permissions. Ongoing protection: Monitor PCEP sessions and revoke stale delegation after controller changes.

Incorrect Answers

B:

An MPLS forwarding entry includes a label action and a next-hop path that must both be valid. That principle governs the alternative intervention. The issue described here is different: PCE computes paths while PCCs maintain local network forwarding and policy state. The case-matched corrective action is: Establish the supported PCEP PCC-PCE relationship and authorize the intended path control.

C:

The proposed option addresses this separate mechanism: Traffic engineering protection must consider physical shared-risk groups, not only logical hop diversity. The stated problem instead depends on: PCE computes paths while PCCs maintain local network forwarding and policy state. The required response is: Establish the supported PCEP PCC-PCE relationship and authorize the intended path control.

D:

The proposed option addresses this separate mechanism: MPLS TTL handling influences transit expiration and visibility in MPLS traceroute. The stated problem instead depends on: PCE computes paths while PCCs maintain local network forwarding and policy state. The required response is: Establish the supported PCEP PCC-PCE relationship and authorize the intended path control.

Question 430

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A PCE sends a recommended SR path to a headend that has not registered the required PCC session or delegation permission. Which observable result most directly verifies that this network issue was resolved?

  1. The PCC reports policy state and accepts the delegated candidate path within its permissions.
  2. Transport LSP tests and end-to-end customer VRF forwarding are independently verified.
  3. Peak load tests remain within the allocated service limits without unexpected tunnel rejection.
  4. IGP cost returns to normal after LDP forms and initial VPN packets avoid the unlabeled link.

Explanation

Correct Answer

A:

For this scenario, the observed situation is: A PCE sends a recommended SR path to a headend that has not registered the required PCC session or delegation permission. The most directly supported response is: Establish the supported PCEP PCC-PCE relationship and authorize the intended path control. Technical basis: PCE computes paths while PCCs maintain local network forwarding and policy state. Evidence of success: The PCC reports policy state and accepts the delegated candidate path within its permissions. Ongoing protection: Monitor PCEP sessions and revoke stale delegation after controller changes.

Incorrect Answers

B:

MPLS transport OAM proves a labeled path but does not automatically prove service VPN import and forwarding. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: PCE computes paths while PCCs maintain local network forwarding and policy state. A passing check should show: The PCC reports policy state and accepts the delegated candidate path within its permissions.

C:

Bandwidth reservation and queue treatment require traffic profiles that reflect burst demands. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: PCE computes paths while PCCs maintain local network forwarding and policy state. A passing check should show: The PCC reports policy state and accepts the delegated candidate path within its permissions.

D:

LDP-IGP synchronization coordinates packet-routing preference with label distribution readiness. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: PCE computes paths while PCCs maintain local network forwarding and policy state. A passing check should show: The PCC reports policy state and accepts the delegated candidate path within its permissions.