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 40

Question 390

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A maintenance engineer sets RSVP administrative affinity to exclude maintenance links but leaves affinities undocumented on new links. Which observable result most directly verifies that this network issue was resolved?

  1. Constraint-based path calculations avoid links with the forbidden maintenance attribute.
  2. A controlled trace identifies the failing hop without falsely blaming customer IP TTL.
  3. The computed flex-algo path contains only participating nodes and satisfies the defined constraints.
  4. The label database contains intended FEC mappings and unauthorized allocations stop appearing.

Explanation

Correct Answer

A:

For this scenario, the observed situation is: A maintenance engineer sets RSVP administrative affinity to exclude maintenance links but leaves affinities undocumented on new links. The most directly supported response is: Encode intended resource affinities consistently and apply the correct inclusion/exclusion constraints. Technical basis: TE affinity constraints select links according to defined administrative groups. Evidence of success: Constraint-based path calculations avoid links with the forbidden maintenance attribute. Ongoing protection: Review affinity assignments in link build checklists.

Incorrect Answers

B:

That observation tests a different mechanism: MPLS TTL handling influences transit expiration and visibility in MPLS traceroute. It cannot establish this case, whose mechanism is: TE affinity constraints select links according to defined administrative groups. The needed verification is: Constraint-based path calculations avoid links with the forbidden maintenance attribute.

C:

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: TE affinity constraints select links according to defined administrative groups. The needed verification is: Constraint-based path calculations avoid links with the forbidden maintenance attribute.

D:

That observation tests a different mechanism: LDP bindings associate FECs with labels and can be constrained by control-plane policy. It cannot establish this case, whose mechanism is: TE affinity constraints select links according to defined administrative groups. The needed verification is: Constraint-based path calculations avoid links with the forbidden maintenance attribute.

Question 391

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A maintenance engineer sets RSVP administrative affinity to exclude maintenance links but leaves affinities undocumented on new links. Which underlying network infrastructure principle best explains the situation?

  1. LDP and segment routing may coexist during migration but require compatible FEC and SID mapping mechanisms.
  2. SR node SIDs represent destinations with shortest-path forwarding and do not pin every intermediate link.
  3. PCE computes paths while PCCs maintain local network forwarding and policy state.
  4. TE affinity constraints select links according to defined administrative groups.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: A maintenance engineer sets RSVP administrative affinity to exclude maintenance links but leaves affinities undocumented on new links. The most directly supported response is: Encode intended resource affinities consistently and apply the correct inclusion/exclusion constraints. Technical basis: TE affinity constraints select links according to defined administrative groups. Evidence of success: Constraint-based path calculations avoid links with the forbidden maintenance attribute. Ongoing protection: Review affinity assignments in link build checklists.

Incorrect Answers

A:

The alternative principle describes: LDP and segment routing may coexist during migration but require compatible FEC and SID mapping mechanisms. In this question, the decisive mechanism is: TE affinity constraints select links according to defined administrative groups. These are distinct technical causes, even when they share a platform.

B:

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: TE affinity constraints select links according to defined administrative groups. These are distinct technical causes, even when they share a platform.

C:

The alternative principle describes: PCE computes paths while PCCs maintain local network forwarding and policy state. In this question, the decisive mechanism is: TE affinity constraints select links according to defined administrative groups. These are distinct technical causes, even when they share a platform.

Question 392

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A maintenance engineer sets RSVP administrative affinity to exclude maintenance links but leaves affinities undocumented on new links. Which continuing control best reduces recurrence of this problem?

  1. Run layered transport and service validation before declaring turn-up complete.
  2. Check LDP session state and outgoing-label resolution during PE activation.
  3. Review affinity assignments in link build checklists.
  4. Keep SID inventory and SRGB change validation in backbone configuration review.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: A maintenance engineer sets RSVP administrative affinity to exclude maintenance links but leaves affinities undocumented on new links. The most directly supported response is: Encode intended resource affinities consistently and apply the correct inclusion/exclusion constraints. Technical basis: TE affinity constraints select links according to defined administrative groups. Evidence of success: Constraint-based path calculations avoid links with the forbidden maintenance attribute. Ongoing protection: Review affinity assignments in link build checklists.

Incorrect Answers

A:

That recurring practice manages a separate exposure: MPLS transport OAM proves a labeled path but does not automatically prove service VPN import and forwarding. The present case instead depends on: TE affinity constraints select links according to defined administrative groups. The suitable ongoing safeguard is: Review affinity assignments in link build checklists.

B:

That recurring practice manages a separate exposure: MPLS forwarding depends on an end-to-end usable label-switched transport path beneath service labels. The present case instead depends on: TE affinity constraints select links according to defined administrative groups. The suitable ongoing safeguard is: Review affinity assignments in link build checklists.

D:

SR-MPLS uses IGP-advertised SIDs with label-index interpretation relative to the SRGB. Maintaining that control would not track the failure described here. The relevant risk is: TE affinity constraints select links according to defined administrative groups. Review this instead: Review affinity assignments in link build checklists.

Question 393

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A TE headend repeatedly reoptimizes a tunnel between two near-equal paths, creating traffic disruption. What is the best authorized corrective or investigative action for this service-provider network operations situation?

  1. Check that newly selected routes still resolve through the correct downstream label bindings.
  2. Establish the supported PCEP PCC-PCE relationship and authorize the intended path control.
  3. Verify SRGB/SID allocation and resulting MPLS labels under the supported SR control-plane design.
  4. Tune reoptimization triggers and hold timers with an acceptable path-quality threshold.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: A TE headend repeatedly reoptimizes a tunnel between two near-equal paths, creating traffic disruption. The most directly supported response is: Tune reoptimization triggers and hold timers with an acceptable path-quality threshold. Technical basis: Aggressive TE reoptimization can cause needless path churn even with valid alternate routes. Evidence of success: The tunnel stays on a stable acceptable path until meaningful resource changes justify a move. Ongoing protection: Review path-switch frequency and traffic impact in maintenance reports.

Incorrect Answers

A:

LDP label mappings are tied to FECs while forwarding next hops follow routed reachability. That principle governs the alternative intervention. The issue described here is different: Aggressive TE reoptimization can cause needless path churn even with valid alternate routes. The case-matched corrective action is: Tune reoptimization triggers and hold timers with an acceptable path-quality threshold.

B:

PCE computes paths while PCCs maintain local network forwarding and policy state. That principle governs the alternative intervention. The issue described here is different: Aggressive TE reoptimization can cause needless path churn even with valid alternate routes. The case-matched corrective action is: Tune reoptimization triggers and hold timers with an acceptable path-quality threshold.

C:

The proposed option addresses this separate mechanism: SR-MPLS uses IGP-advertised SIDs with label-index interpretation relative to the SRGB. The stated problem instead depends on: Aggressive TE reoptimization can cause needless path churn even with valid alternate routes. The required response is: Tune reoptimization triggers and hold timers with an acceptable path-quality threshold.

Question 394

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A TE headend repeatedly reoptimizes a tunnel between two near-equal paths, creating traffic disruption. Which observable result most directly verifies that this network issue was resolved?

  1. The SRv6 packet reaches the correct locator and executes the intended endpoint function.
  2. The tunnel stays on a stable acceptable path until meaningful resource changes justify a move.
  3. A cross-domain service packet traverses the gateway and retains correct customer isolation.
  4. The LFIB switches labels consistently with the updated IGP shortest path.

Explanation

Correct Answer

B:

For this scenario, the observed situation is: A TE headend repeatedly reoptimizes a tunnel between two near-equal paths, creating traffic disruption. The most directly supported response is: Tune reoptimization triggers and hold timers with an acceptable path-quality threshold. Technical basis: Aggressive TE reoptimization can cause needless path churn even with valid alternate routes. Evidence of success: The tunnel stays on a stable acceptable path until meaningful resource changes justify a move. Ongoing protection: Review path-switch frequency and traffic impact in maintenance reports.

Incorrect Answers

A:

That observation tests a different mechanism: SRv6 SIDs combine routable locators with endpoint behavior encoded in IPv6 addressing. It cannot establish this case, whose mechanism is: Aggressive TE reoptimization can cause needless path churn even with valid alternate routes. The needed verification is: The tunnel stays on a stable acceptable path until meaningful resource changes justify a move.

C:

SR-MPLS labels and SRv6 SID functions are different forwarding representations requiring explicit interworking. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: Aggressive TE reoptimization can cause needless path churn even with valid alternate routes. A passing check should show: The tunnel stays on a stable acceptable path until meaningful resource changes justify a move.

D:

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: Aggressive TE reoptimization can cause needless path churn even with valid alternate routes. A passing check should show: The tunnel stays on a stable acceptable path until meaningful resource changes justify a move.

Question 395

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A TE headend repeatedly reoptimizes a tunnel between two near-equal paths, creating traffic disruption. Which underlying network infrastructure principle best explains the situation?

  1. LDP session protection can retain a session across certain directly connected link disruptions.
  2. Aggressive TE reoptimization can cause needless path churn even with valid alternate routes.
  3. MPLS TTL handling influences transit expiration and visibility in MPLS traceroute.
  4. SR-MPLS uses IGP-advertised SIDs with label-index interpretation relative to the SRGB.

Explanation

Correct Answer

B:

For this scenario, the observed situation is: A TE headend repeatedly reoptimizes a tunnel between two near-equal paths, creating traffic disruption. The most directly supported response is: Tune reoptimization triggers and hold timers with an acceptable path-quality threshold. Technical basis: Aggressive TE reoptimization can cause needless path churn even with valid alternate routes. Evidence of success: The tunnel stays on a stable acceptable path until meaningful resource changes justify a move. Ongoing protection: Review path-switch frequency and traffic impact in maintenance reports.

Incorrect Answers

A:

LDP session protection can retain a session across certain directly connected link disruptions. That is not the causal relationship tested by the current facts. The relevant principle is: Aggressive TE reoptimization can cause needless path churn even with valid alternate routes.

C:

MPLS TTL handling influences transit expiration and visibility in MPLS traceroute. That is not the causal relationship tested by the current facts. The relevant principle is: Aggressive TE reoptimization can cause needless path churn even with valid alternate routes.

D:

SR-MPLS uses IGP-advertised SIDs with label-index interpretation relative to the SRGB. That is not the causal relationship tested by the current facts. The relevant principle is: Aggressive TE reoptimization can cause needless path churn even with valid alternate routes.

Question 396

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A TE headend repeatedly reoptimizes a tunnel between two near-equal paths, creating traffic disruption. Which continuing control best reduces recurrence of this problem?

  1. Test final-hop label disposition after changing MPLS QoS design.
  2. Exercise mixed-domain failover and remove stale mappings during cutover.
  3. Audit flex-algo definition consistency and excluded-node handling.
  4. Review path-switch frequency and traffic impact in maintenance reports.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: A TE headend repeatedly reoptimizes a tunnel between two near-equal paths, creating traffic disruption. The most directly supported response is: Tune reoptimization triggers and hold timers with an acceptable path-quality threshold. Technical basis: Aggressive TE reoptimization can cause needless path churn even with valid alternate routes. Evidence of success: The tunnel stays on a stable acceptable path until meaningful resource changes justify a move. Ongoing protection: Review path-switch frequency and traffic impact in maintenance reports.

Incorrect Answers

A:

Explicit-null retains a label to the egress when required, whereas PHP can remove it earlier. Maintaining that control would not track the failure described here. The relevant risk is: Aggressive TE reoptimization can cause needless path churn even with valid alternate routes. Review this instead: Review path-switch frequency and traffic impact in maintenance reports.

B:

LDP and segment routing may coexist during migration but require compatible FEC and SID mapping mechanisms. Maintaining that control would not track the failure described here. The relevant risk is: Aggressive TE reoptimization can cause needless path churn even with valid alternate routes. Review this instead: Review path-switch frequency and traffic impact in maintenance reports.

C:

SR Flexible Algorithm derives separate constraint-based IGP topologies from shared advertisements. Maintaining that control would not track the failure described here. The relevant risk is: Aggressive TE reoptimization can cause needless path churn even with valid alternate routes. Review this instead: Review path-switch frequency and traffic impact in maintenance reports.

Question 397

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An IS-IS backbone distributes reachability successfully but PCE calculations cannot account for link delay because the measurements are absent. What is the best authorized corrective or investigative action for this service-provider network operations situation?

  1. Supply supported TE delay or performance attributes to the topology and ensure they reach path computation.
  2. Implement documented interworking gateway behavior preserving VPN identifiers and forwarding intent.
  3. Activate the supported MPLS forwarding and LDP interface configuration on both endpoints.
  4. Test both the transport label-switched path and the VPN-specific service label disposition.

Explanation

Correct Answer

A:

For this scenario, the observed situation is: An IS-IS backbone distributes reachability successfully but PCE calculations cannot account for link delay because the measurements are absent. The most directly supported response is: Supply supported TE delay or performance attributes to the topology and ensure they reach path computation. Technical basis: Path computation depends on the attributes advertised or otherwise provided to its topology database. Evidence of success: The computed constrained path reflects measured delay differences between candidate links. Ongoing protection: Calibrate delay telemetry and revalidate stale path information.

Incorrect Answers

B:

The proposed option addresses this separate mechanism: SR-MPLS labels and SRv6 SID functions are different forwarding representations requiring explicit interworking. The stated problem instead depends on: Path computation depends on the attributes advertised or otherwise provided to its topology database. The required response is: Supply supported TE delay or performance attributes to the topology and ensure they reach path computation.

C:

The option fits a control for: An IP routed adjacency does not itself establish an MPLS label-distribution session. The present failure is caused by a different mechanism: Path computation depends on the attributes advertised or otherwise provided to its topology database. The targeted implementation is: Supply supported TE delay or performance attributes to the topology and ensure they reach path computation.

D:

The option fits a control for: MPLS transport OAM proves a labeled path but does not automatically prove service VPN import and forwarding. The present failure is caused by a different mechanism: Path computation depends on the attributes advertised or otherwise provided to its topology database. The targeted implementation is: Supply supported TE delay or performance attributes to the topology and ensure they reach path computation.

Question 398

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An IS-IS backbone distributes reachability successfully but PCE calculations cannot account for link delay because the measurements are absent. Which observable result most directly verifies that this network issue was resolved?

  1. LDP session state survives eligible short link outages under the designed protection interval.
  2. The observed path change aligns with IGP shortest paths while any strict adjacency steering remains stable.
  3. The computed constrained path reflects measured delay differences between candidate links.
  4. After PCE unavailability, traffic follows the documented eligible local fallback path.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: An IS-IS backbone distributes reachability successfully but PCE calculations cannot account for link delay because the measurements are absent. The most directly supported response is: Supply supported TE delay or performance attributes to the topology and ensure they reach path computation. Technical basis: Path computation depends on the attributes advertised or otherwise provided to its topology database. Evidence of success: The computed constrained path reflects measured delay differences between candidate links. Ongoing protection: Calibrate delay telemetry and revalidate stale path information.

Incorrect Answers

A:

LDP session protection can retain a session across certain directly connected link disruptions. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: Path computation depends on the attributes advertised or otherwise provided to its topology database. A passing check should show: The computed constrained path reflects measured delay differences between candidate links.

B:

The proposed test would be relevant to: SR node SIDs represent destinations with shortest-path forwarding and do not pin every intermediate link. The reported problem follows from: Path computation depends on the attributes advertised or otherwise provided to its topology database. Instead, verify: The computed constrained path reflects measured delay differences between candidate links.

D:

The proposed test would be relevant to: SR policies can support candidate path preference and resilient local control independent of external PCE availability. The reported problem follows from: Path computation depends on the attributes advertised or otherwise provided to its topology database. Instead, verify: The computed constrained path reflects measured delay differences between candidate links.

Question 399

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An IS-IS backbone distributes reachability successfully but PCE calculations cannot account for link delay because the measurements are absent. Which underlying network infrastructure principle best explains the situation?

  1. SRv6 SIDs combine routable locators with endpoint behavior encoded in IPv6 addressing.
  2. Path computation depends on the attributes advertised or otherwise provided to its topology database.
  3. SR node SIDs represent destinations with shortest-path forwarding and do not pin every intermediate link.
  4. LDP and segment routing may coexist during migration but require compatible FEC and SID mapping mechanisms.

Explanation

Correct Answer

B:

For this scenario, the observed situation is: An IS-IS backbone distributes reachability successfully but PCE calculations cannot account for link delay because the measurements are absent. The most directly supported response is: Supply supported TE delay or performance attributes to the topology and ensure they reach path computation. Technical basis: Path computation depends on the attributes advertised or otherwise provided to its topology database. Evidence of success: The computed constrained path reflects measured delay differences between candidate links. Ongoing protection: Calibrate delay telemetry and revalidate stale path information.

Incorrect Answers

A:

The option explains a separate issue: SRv6 SIDs combine routable locators with endpoint behavior encoded in IPv6 addressing. The reported condition instead follows from: Path computation depends on the attributes advertised or otherwise provided to its topology database.

C:

The option explains a separate issue: SR node SIDs represent destinations with shortest-path forwarding and do not pin every intermediate link. The reported condition instead follows from: Path computation depends on the attributes advertised or otherwise provided to its topology database.

D:

The option explains a separate issue: LDP and segment routing may coexist during migration but require compatible FEC and SID mapping mechanisms. The reported condition instead follows from: Path computation depends on the attributes advertised or otherwise provided to its topology database.

Question 400

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An IS-IS backbone distributes reachability successfully but PCE calculations cannot account for link delay because the measurements are absent. Which continuing control best reduces recurrence of this problem?

  1. Test bidirectional VPN connectivity and tenant separation during mixed-domain migration.
  2. Check LDP session state and outgoing-label resolution during PE activation.
  3. Test final-hop label disposition after changing MPLS QoS design.
  4. Calibrate delay telemetry and revalidate stale path information.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: An IS-IS backbone distributes reachability successfully but PCE calculations cannot account for link delay because the measurements are absent. The most directly supported response is: Supply supported TE delay or performance attributes to the topology and ensure they reach path computation. Technical basis: Path computation depends on the attributes advertised or otherwise provided to its topology database. Evidence of success: The computed constrained path reflects measured delay differences between candidate links. Ongoing protection: Calibrate delay telemetry and revalidate stale path information.

Incorrect Answers

A:

The alternative guards against: SR-MPLS labels and SRv6 SID functions are different forwarding representations requiring explicit interworking. The root condition for this case is: Path computation depends on the attributes advertised or otherwise provided to its topology database. The focused prevention check is: Calibrate delay telemetry and revalidate stale path information.

B:

The alternative guards against: MPLS forwarding depends on an end-to-end usable label-switched transport path beneath service labels. The root condition for this case is: Path computation depends on the attributes advertised or otherwise provided to its topology database. The focused prevention check is: Calibrate delay telemetry and revalidate stale path information.

C:

The alternative guards against: Explicit-null retains a label to the egress when required, whereas PHP can remove it earlier. The root condition for this case is: Path computation depends on the attributes advertised or otherwise provided to its topology database. The focused prevention check is: Calibrate delay telemetry and revalidate stale path information.