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 37

Question 360

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An LDP session remains established but its transport prefix FEC changes next hop after an IGP metric update. Which continuing control best reduces recurrence of this problem?

  1. Review path-switch frequency and traffic impact in maintenance reports.
  2. Continuously validate policy candidate-path resolution and fallback behavior.
  3. Audit steering behavior after metric or topology changes.
  4. Correlate IGP changes with LFIB programming and packet-loss metrics.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: An LDP session remains established but its transport prefix FEC changes next hop after an IGP metric update. The most directly supported response is: Check that newly selected routes still resolve through the correct downstream label bindings. Technical basis: LDP label mappings are tied to FECs while forwarding next hops follow routed reachability. Evidence of success: The LFIB switches labels consistently with the updated IGP shortest path. Ongoing protection: Correlate IGP changes with LFIB programming and packet-loss metrics.

Incorrect Answers

A:

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: LDP label mappings are tied to FECs while forwarding next hops follow routed reachability. Review this instead: Correlate IGP changes with LFIB programming and packet-loss metrics.

B:

An SRTE policy is usable only when its segment instructions resolve through supported topology. Maintaining that control would not track the failure described here. The relevant risk is: LDP label mappings are tied to FECs while forwarding next hops follow routed reachability. Review this instead: Correlate IGP changes with LFIB programming and packet-loss metrics.

C:

An SR node SID typically follows IGP shortest paths, while adjacency SIDs can encode a specific link. Maintaining that control would not track the failure described here. The relevant risk is: LDP label mappings are tied to FECs while forwarding next hops follow routed reachability. Review this instead: Correlate IGP changes with LFIB programming and packet-loss metrics.

Question 361

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: Operators see explicit-null label behavior on one MPLS egress and assume it indicates a corrupted forwarding entry. What is the best authorized corrective or investigative action for this service-provider network operations situation?

  1. Use an appropriate adjacency SID or constrained SR policy segment list for explicit link steering.
  2. Check the negotiated explicit-null and PHP behavior against the intended QoS and egress treatment.
  3. Design local repair paths with actual shared-risk link groups and diversity constraints.
  4. Check whether node SID paths are recalculated by SPF and use adjacency SIDs for fixed link requirements.

Explanation

Correct Answer

B:

For this scenario, the observed situation is: Operators see explicit-null label behavior on one MPLS egress and assume it indicates a corrupted forwarding entry. The most directly supported response is: Check the negotiated explicit-null and PHP behavior against the intended QoS and egress treatment. Technical basis: Explicit-null retains a label to the egress when required, whereas PHP can remove it earlier. Evidence of success: The penultimate hop performs the expected label operation and core QoS markings are preserved as designed. Ongoing protection: Test final-hop label disposition after changing MPLS QoS design.

Incorrect Answers

A:

The proposed option addresses this separate mechanism: An SR node SID typically follows IGP shortest paths, while adjacency SIDs can encode a specific link. The stated problem instead depends on: Explicit-null retains a label to the egress when required, whereas PHP can remove it earlier. The required response is: Check the negotiated explicit-null and PHP behavior against the intended QoS and egress treatment.

C:

The option fits a control for: Traffic engineering protection must consider physical shared-risk groups, not only logical hop diversity. The present failure is caused by a different mechanism: Explicit-null retains a label to the egress when required, whereas PHP can remove it earlier. The targeted implementation is: Check the negotiated explicit-null and PHP behavior against the intended QoS and egress treatment.

D:

The option fits a control for: SR node SIDs represent destinations with shortest-path forwarding and do not pin every intermediate link. The present failure is caused by a different mechanism: Explicit-null retains a label to the egress when required, whereas PHP can remove it earlier. The targeted implementation is: Check the negotiated explicit-null and PHP behavior against the intended QoS and egress treatment.

Question 362

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: Operators see explicit-null label behavior on one MPLS egress and assume it indicates a corrupted forwarding entry. Which observable result most directly verifies that this network issue was resolved?

  1. The penultimate hop performs the expected label operation and core QoS markings are preserved as designed.
  2. Failure injection of the shared conduit no longer disables both primary and backup paths.
  3. The tunnel stays on a stable acceptable path until meaningful resource changes justify a move.
  4. The ingress pushes valid segment labels and transit nodes forward to the intended PE.

Explanation

Correct Answer

A:

For this scenario, the observed situation is: Operators see explicit-null label behavior on one MPLS egress and assume it indicates a corrupted forwarding entry. The most directly supported response is: Check the negotiated explicit-null and PHP behavior against the intended QoS and egress treatment. Technical basis: Explicit-null retains a label to the egress when required, whereas PHP can remove it earlier. Evidence of success: The penultimate hop performs the expected label operation and core QoS markings are preserved as designed. Ongoing protection: Test final-hop label disposition after changing MPLS QoS design.

Incorrect Answers

B:

The proposed test would be relevant to: Traffic engineering protection must consider physical shared-risk groups, not only logical hop diversity. The reported problem follows from: Explicit-null retains a label to the egress when required, whereas PHP can remove it earlier. Instead, verify: The penultimate hop performs the expected label operation and core QoS markings are preserved as designed.

C:

The proposed test would be relevant to: Aggressive TE reoptimization can cause needless path churn even with valid alternate routes. The reported problem follows from: Explicit-null retains a label to the egress when required, whereas PHP can remove it earlier. Instead, verify: The penultimate hop performs the expected label operation and core QoS markings are preserved as designed.

D:

The proposed test would be relevant to: SR-MPLS uses IGP-advertised SIDs with label-index interpretation relative to the SRGB. The reported problem follows from: Explicit-null retains a label to the egress when required, whereas PHP can remove it earlier. Instead, verify: The penultimate hop performs the expected label operation and core QoS markings are preserved as designed.

Question 363

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: Operators see explicit-null label behavior on one MPLS egress and assume it indicates a corrupted forwarding entry. Which underlying network infrastructure principle best explains the situation?

  1. SRv6 micro-segment techniques compress functions but depend on interoperable network behavior.
  2. RSVP-TE signaling can reserve bandwidth and fail when requested resources are unavailable.
  3. Explicit-null retains a label to the egress when required, whereas PHP can remove it earlier.
  4. TI-LFA computes post-convergence-oriented local repair paths for segment-routing networks.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: Operators see explicit-null label behavior on one MPLS egress and assume it indicates a corrupted forwarding entry. The most directly supported response is: Check the negotiated explicit-null and PHP behavior against the intended QoS and egress treatment. Technical basis: Explicit-null retains a label to the egress when required, whereas PHP can remove it earlier. Evidence of success: The penultimate hop performs the expected label operation and core QoS markings are preserved as designed. Ongoing protection: Test final-hop label disposition after changing MPLS QoS design.

Incorrect Answers

A:

The option explains a separate issue: SRv6 micro-segment techniques compress functions but depend on interoperable network behavior. The reported condition instead follows from: Explicit-null retains a label to the egress when required, whereas PHP can remove it earlier.

B:

The option explains a separate issue: RSVP-TE signaling can reserve bandwidth and fail when requested resources are unavailable. The reported condition instead follows from: Explicit-null retains a label to the egress when required, whereas PHP can remove it earlier.

D:

The option explains a separate issue: TI-LFA computes post-convergence-oriented local repair paths for segment-routing networks. The reported condition instead follows from: Explicit-null retains a label to the egress when required, whereas PHP can remove it earlier.

Question 364

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: Operators see explicit-null label behavior on one MPLS egress and assume it indicates a corrupted forwarding entry. Which continuing control best reduces recurrence of this problem?

  1. Test final-hop label disposition after changing MPLS QoS design.
  2. Keep SID inventory and SRGB change validation in backbone configuration review.
  3. Measure burst peaks and reevaluate reservation headroom seasonally.
  4. Audit flex-algo definition consistency and excluded-node handling.

Explanation

Correct Answer

A:

For this scenario, the observed situation is: Operators see explicit-null label behavior on one MPLS egress and assume it indicates a corrupted forwarding entry. The most directly supported response is: Check the negotiated explicit-null and PHP behavior against the intended QoS and egress treatment. Technical basis: Explicit-null retains a label to the egress when required, whereas PHP can remove it earlier. Evidence of success: The penultimate hop performs the expected label operation and core QoS markings are preserved as designed. Ongoing protection: Test final-hop label disposition after changing MPLS QoS design.

Incorrect Answers

B:

The alternative guards against: SR-MPLS uses IGP-advertised SIDs with label-index interpretation relative to the SRGB. The root condition for this case is: Explicit-null retains a label to the egress when required, whereas PHP can remove it earlier. The focused prevention check is: Test final-hop label disposition after changing MPLS QoS design.

C:

The alternative guards against: Bandwidth reservation and queue treatment require traffic profiles that reflect burst demands. The root condition for this case is: Explicit-null retains a label to the egress when required, whereas PHP can remove it earlier. The focused prevention check is: Test final-hop label disposition after changing MPLS QoS design.

D:

That recurring practice manages a separate exposure: SR Flexible Algorithm derives separate constraint-based IGP topologies from shared advertisements. The present case instead depends on: Explicit-null retains a label to the egress when required, whereas PHP can remove it earlier. The suitable ongoing safeguard is: Test final-hop label disposition after changing MPLS QoS design.

Question 365

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A migration keeps legacy LDP transport for some sites and segment-routing transport for others, but border PEs lack working interworking. What is the best authorized corrective or investigative action for this service-provider network operations situation?

  1. Verify SRGB/SID allocation and resulting MPLS labels under the supported SR control-plane design.
  2. Design supported LDP-to-SR transport interworking at the controlled migration boundary.
  3. Assess RSVP-TE capability along every hop and choose a supported path or alternative technology.
  4. Tune reoptimization triggers and hold timers with an acceptable path-quality threshold.

Explanation

Correct Answer

B:

For this scenario, the observed situation is: A migration keeps legacy LDP transport for some sites and segment-routing transport for others, but border PEs lack working interworking. The most directly supported response is: Design supported LDP-to-SR transport interworking at the controlled migration boundary. Technical basis: LDP and segment routing may coexist during migration but require compatible FEC and SID mapping mechanisms. Evidence of success: Routes between legacy and SR-enabled areas maintain labeled reachability without loops. Ongoing protection: Exercise mixed-domain failover and remove stale mappings during cutover.

Incorrect Answers

A:

The option fits a control for: SR-MPLS uses IGP-advertised SIDs with label-index interpretation relative to the SRGB. The present failure is caused by a different mechanism: LDP and segment routing may coexist during migration but require compatible FEC and SID mapping mechanisms. The targeted implementation is: Design supported LDP-to-SR transport interworking at the controlled migration boundary.

C:

RSVP-TE tunnel setup requires compatible signaling and resource support along the chosen route. That principle governs the alternative intervention. The issue described here is different: LDP and segment routing may coexist during migration but require compatible FEC and SID mapping mechanisms. The case-matched corrective action is: Design supported LDP-to-SR transport interworking at the controlled migration boundary.

D:

Aggressive TE reoptimization can cause needless path churn even with valid alternate routes. That principle governs the alternative intervention. The issue described here is different: LDP and segment routing may coexist during migration but require compatible FEC and SID mapping mechanisms. The case-matched corrective action is: Design supported LDP-to-SR transport interworking at the controlled migration boundary.

Question 366

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A migration keeps legacy LDP transport for some sites and segment-routing transport for others, but border PEs lack working interworking. Which observable result most directly verifies that this network issue was resolved?

  1. Routes between legacy and SR-enabled areas maintain labeled reachability without loops.
  2. The headend installs the intended segment list and the FIB resolves every segment.
  3. The TE database receives the expected link resources while ordinary reachability remains intact.
  4. The PCC reports policy state and accepts the delegated candidate path within its permissions.

Explanation

Correct Answer

A:

For this scenario, the observed situation is: A migration keeps legacy LDP transport for some sites and segment-routing transport for others, but border PEs lack working interworking. The most directly supported response is: Design supported LDP-to-SR transport interworking at the controlled migration boundary. Technical basis: LDP and segment routing may coexist during migration but require compatible FEC and SID mapping mechanisms. Evidence of success: Routes between legacy and SR-enabled areas maintain labeled reachability without loops. Ongoing protection: Exercise mixed-domain failover and remove stale mappings during cutover.

Incorrect Answers

B:

That observation tests a different mechanism: An SRTE policy is usable only when its segment instructions resolve through supported topology. It cannot establish this case, whose mechanism is: LDP and segment routing may coexist during migration but require compatible FEC and SID mapping mechanisms. The needed verification is: Routes between legacy and SR-enabled areas maintain labeled reachability without loops.

C:

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: LDP and segment routing may coexist during migration but require compatible FEC and SID mapping mechanisms. The needed verification is: Routes between legacy and SR-enabled areas maintain labeled reachability without loops.

D:

That observation tests a different mechanism: PCE computes paths while PCCs maintain local network forwarding and policy state. It cannot establish this case, whose mechanism is: LDP and segment routing may coexist during migration but require compatible FEC and SID mapping mechanisms. The needed verification is: Routes between legacy and SR-enabled areas maintain labeled reachability without loops.

Question 367

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A migration keeps legacy LDP transport for some sites and segment-routing transport for others, but border PEs lack working interworking. Which underlying network infrastructure principle best explains the situation?

  1. SR node SIDs represent destinations with shortest-path forwarding and do not pin every intermediate link.
  2. Aggressive TE reoptimization can cause needless path churn even with valid alternate routes.
  3. SRv6 SIDs combine routable locators with endpoint behavior encoded in IPv6 addressing.
  4. LDP and segment routing may coexist during migration but require compatible FEC and SID mapping mechanisms.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: A migration keeps legacy LDP transport for some sites and segment-routing transport for others, but border PEs lack working interworking. The most directly supported response is: Design supported LDP-to-SR transport interworking at the controlled migration boundary. Technical basis: LDP and segment routing may coexist during migration but require compatible FEC and SID mapping mechanisms. Evidence of success: Routes between legacy and SR-enabled areas maintain labeled reachability without loops. Ongoing protection: Exercise mixed-domain failover and remove stale mappings during cutover.

Incorrect Answers

A:

The alternative principle describes: SR node SIDs represent destinations with shortest-path forwarding and do not pin every intermediate link. In this question, the decisive mechanism is: LDP and segment routing may coexist during migration but require compatible FEC and SID mapping mechanisms. These are distinct technical causes, even when they share a platform.

B:

The alternative principle describes: Aggressive TE reoptimization can cause needless path churn even with valid alternate routes. In this question, the decisive mechanism is: LDP and segment routing may coexist during migration but require compatible FEC and SID mapping mechanisms. These are distinct technical causes, even when they share a platform.

C:

The alternative principle describes: SRv6 SIDs combine routable locators with endpoint behavior encoded in IPv6 addressing. In this question, the decisive mechanism is: LDP and segment routing may coexist during migration but require compatible FEC and SID mapping mechanisms. These are distinct technical causes, even when they share a platform.

Question 368

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A migration keeps legacy LDP transport for some sites and segment-routing transport for others, but border PEs lack working interworking. Which continuing control best reduces recurrence of this problem?

  1. Continuously validate policy candidate-path resolution and fallback behavior.
  2. Measure burst peaks and reevaluate reservation headroom seasonally.
  3. Exercise mixed-domain failover and remove stale mappings during cutover.
  4. Keep SRLG inventory current and test correlated fiber failures.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: A migration keeps legacy LDP transport for some sites and segment-routing transport for others, but border PEs lack working interworking. The most directly supported response is: Design supported LDP-to-SR transport interworking at the controlled migration boundary. Technical basis: LDP and segment routing may coexist during migration but require compatible FEC and SID mapping mechanisms. Evidence of success: Routes between legacy and SR-enabled areas maintain labeled reachability without loops. Ongoing protection: Exercise mixed-domain failover and remove stale mappings during cutover.

Incorrect Answers

A:

That recurring practice manages a separate exposure: An SRTE policy is usable only when its segment instructions resolve through supported topology. The present case instead depends on: LDP and segment routing may coexist during migration but require compatible FEC and SID mapping mechanisms. The suitable ongoing safeguard is: Exercise mixed-domain failover and remove stale mappings during cutover.

B:

That recurring practice manages a separate exposure: Bandwidth reservation and queue treatment require traffic profiles that reflect burst demands. The present case instead depends on: LDP and segment routing may coexist during migration but require compatible FEC and SID mapping mechanisms. The suitable ongoing safeguard is: Exercise mixed-domain failover and remove stale mappings during cutover.

D:

Traffic engineering protection must consider physical shared-risk groups, not only logical hop diversity. Maintaining that control would not track the failure described here. The relevant risk is: LDP and segment routing may coexist during migration but require compatible FEC and SID mapping mechanisms. Review this instead: Exercise mixed-domain failover and remove stale mappings during cutover.

Question 369

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A provider needs a tunnel that avoids a low-bandwidth shared circuit, yet its engineers rely only on ordinary IGP shortest-path metrics. What is the best authorized corrective or investigative action for this service-provider network operations situation?

  1. Use traffic engineering path constraints with measured link attributes and an explicitly defined headend policy.
  2. Define supported preference-ordered local and controller-provided SR policy candidates.
  3. Restore supported LDP neighbor discovery and label exchange across the transport path before enabling service traffic.
  4. Filter permitted LDP label allocation and advertise only necessary FECs on the supported platform.

Explanation

Correct Answer

A:

For this scenario, the observed situation is: A provider needs a tunnel that avoids a low-bandwidth shared circuit, yet its engineers rely only on ordinary IGP shortest-path metrics. The most directly supported response is: Use traffic engineering path constraints with measured link attributes and an explicitly defined headend policy. Technical basis: Traffic engineering selects paths based on constraints beyond default shortest-path cost. Evidence of success: The engineered tunnel avoids excluded links and meets the required path constraints. Ongoing protection: Refresh TE topology attributes and validate resources after bandwidth changes.

Incorrect Answers

B:

SR policies can support candidate path preference and resilient local control independent of external PCE availability. That principle governs the alternative intervention. The issue described here is different: Traffic engineering selects paths based on constraints beyond default shortest-path cost. The case-matched corrective action is: Use traffic engineering path constraints with measured link attributes and an explicitly defined headend policy.

C:

The proposed option addresses this separate mechanism: MPLS forwarding depends on an end-to-end usable label-switched transport path beneath service labels. The stated problem instead depends on: Traffic engineering selects paths based on constraints beyond default shortest-path cost. The required response is: Use traffic engineering path constraints with measured link attributes and an explicitly defined headend policy.

D:

The proposed option addresses this separate mechanism: LDP bindings associate FECs with labels and can be constrained by control-plane policy. The stated problem instead depends on: Traffic engineering selects paths based on constraints beyond default shortest-path cost. The required response is: Use traffic engineering path constraints with measured link attributes and an explicitly defined headend policy.

Question 370

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A provider needs a tunnel that avoids a low-bandwidth shared circuit, yet its engineers rely only on ordinary IGP shortest-path metrics. Which observable result most directly verifies that this network issue was resolved?

  1. The computed flex-algo path contains only participating nodes and satisfies the defined constraints.
  2. The engineered tunnel avoids excluded links and meets the required path constraints.
  3. The LFIB switches labels consistently with the updated IGP shortest path.
  4. The penultimate hop performs the expected label operation and core QoS markings are preserved as designed.

Explanation

Correct Answer

B:

For this scenario, the observed situation is: A provider needs a tunnel that avoids a low-bandwidth shared circuit, yet its engineers rely only on ordinary IGP shortest-path metrics. The most directly supported response is: Use traffic engineering path constraints with measured link attributes and an explicitly defined headend policy. Technical basis: Traffic engineering selects paths based on constraints beyond default shortest-path cost. Evidence of success: The engineered tunnel avoids excluded links and meets the required path constraints. Ongoing protection: Refresh TE topology attributes and validate resources after bandwidth changes.

Incorrect Answers

A:

That observation tests a different mechanism: SR Flexible Algorithm derives separate constraint-based IGP topologies from shared advertisements. It cannot establish this case, whose mechanism is: Traffic engineering selects paths based on constraints beyond default shortest-path cost. The needed verification is: The engineered tunnel avoids excluded links and meets the required path constraints.

C:

LDP label mappings are tied to FECs while forwarding next hops follow routed reachability. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: Traffic engineering selects paths based on constraints beyond default shortest-path cost. A passing check should show: The engineered tunnel avoids excluded links and meets the required path constraints.

D:

Explicit-null retains a label to the egress when required, whereas PHP can remove it earlier. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: Traffic engineering selects paths based on constraints beyond default shortest-path cost. A passing check should show: The engineered tunnel avoids excluded links and meets the required path constraints.