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 30

Question 290

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A core BGP neighbor restarts gracefully but a provider fails all traffic immediately despite planned stale-route retention. Which observable result most directly verifies that this network issue was resolved?

  1. A controlled primary failure switches eligible traffic to the prepared backup within the objective.
  2. During a controlled restart, forwarding continues within specified stale-route timers without blackholing beyond the budget.
  3. The router remains adjacent but normal transit paths avoid it until maintenance state clears.
  4. The subscriber's allowed IPv4 address/port set follows the configured algorithmic mapping.

Explanation

Correct Answer

B:

For this scenario, the observed situation is: A core BGP neighbor restarts gracefully but a provider fails all traffic immediately despite planned stale-route retention. The most directly supported response is: Enable and verify supported BGP graceful restart behavior and independent next-hop recovery constraints. Technical basis: Graceful restart can preserve routing information temporarily while a control plane reconverges. Evidence of success: During a controlled restart, forwarding continues within specified stale-route timers without blackholing beyond the budget. Ongoing protection: Test stale-route timer expiry and unsupported-peer behavior before relying on graceful restart.

Incorrect Answers

A:

BGP Add-Paths and PIC address different multipath signaling and precomputed backup forwarding aspects. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: Graceful restart can preserve routing information temporarily while a control plane reconverges. A passing check should show: During a controlled restart, forwarding continues within specified stale-route timers without blackholing beyond the budget.

C:

The proposed test would be relevant to: IS-IS overload and high-cost advertisement can drain transit traffic without tearing down every adjacency. The reported problem follows from: Graceful restart can preserve routing information temporarily while a control plane reconverges. Instead, verify: During a controlled restart, forwarding continues within specified stale-route timers without blackholing beyond the budget.

D:

The proposed test would be relevant to: MAP-T supports algorithmic IPv4-to-IPv6 translation and port-set assignment rather than central per-flow NAT state. The reported problem follows from: Graceful restart can preserve routing information temporarily while a control plane reconverges. Instead, verify: During a controlled restart, forwarding continues within specified stale-route timers without blackholing beyond the budget.

Question 291

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A core BGP neighbor restarts gracefully but a provider fails all traffic immediately despite planned stale-route retention. Which underlying network infrastructure principle best explains the situation?

  1. OSPF default cost calculations can lose resolution when link speeds exceed the reference bandwidth.
  2. OSPF adjacency requires compatible hello parameters, not merely Layer 3 reachability.
  3. Graceful restart can preserve routing information temporarily while a control plane reconverges.
  4. IS-IS multitopology can maintain separate route calculations for distinct supported protocol topologies.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: A core BGP neighbor restarts gracefully but a provider fails all traffic immediately despite planned stale-route retention. The most directly supported response is: Enable and verify supported BGP graceful restart behavior and independent next-hop recovery constraints. Technical basis: Graceful restart can preserve routing information temporarily while a control plane reconverges. Evidence of success: During a controlled restart, forwarding continues within specified stale-route timers without blackholing beyond the budget. Ongoing protection: Test stale-route timer expiry and unsupported-peer behavior before relying on graceful restart.

Incorrect Answers

A:

The option explains a separate issue: OSPF default cost calculations can lose resolution when link speeds exceed the reference bandwidth. The reported condition instead follows from: Graceful restart can preserve routing information temporarily while a control plane reconverges.

B:

The option explains a separate issue: OSPF adjacency requires compatible hello parameters, not merely Layer 3 reachability. The reported condition instead follows from: Graceful restart can preserve routing information temporarily while a control plane reconverges.

D:

The option explains a separate issue: IS-IS multitopology can maintain separate route calculations for distinct supported protocol topologies. The reported condition instead follows from: Graceful restart can preserve routing information temporarily while a control plane reconverges.

Question 292

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A core BGP neighbor restarts gracefully but a provider fails all traffic immediately despite planned stale-route retention. Which continuing control best reduces recurrence of this problem?

  1. Maintain area boundary templates and interarea route tests after changes.
  2. Version the reference-bandwidth policy and deploy it consistently across the routing domain.
  3. Check inbound policy, next hop, and route preferences before changing peer attributes.
  4. Test stale-route timer expiry and unsupported-peer behavior before relying on graceful restart.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: A core BGP neighbor restarts gracefully but a provider fails all traffic immediately despite planned stale-route retention. The most directly supported response is: Enable and verify supported BGP graceful restart behavior and independent next-hop recovery constraints. Technical basis: Graceful restart can preserve routing information temporarily while a control plane reconverges. Evidence of success: During a controlled restart, forwarding continues within specified stale-route timers without blackholing beyond the budget. Ongoing protection: Test stale-route timer expiry and unsupported-peer behavior before relying on graceful restart.

Incorrect Answers

A:

The alternative guards against: IS-IS Level-2 provides interarea reachability while Level-1 focuses on intraarea topology. The root condition for this case is: Graceful restart can preserve routing information temporarily while a control plane reconverges. The focused prevention check is: Test stale-route timer expiry and unsupported-peer behavior before relying on graceful restart.

B:

The alternative guards against: OSPF default cost calculations can lose resolution when link speeds exceed the reference bandwidth. The root condition for this case is: Graceful restart can preserve routing information temporarily while a control plane reconverges. The focused prevention check is: Test stale-route timer expiry and unsupported-peer behavior before relying on graceful restart.

C:

The alternative guards against: Reception of BGP NLRI does not necessarily imply RIB or FIB installation. The root condition for this case is: Graceful restart can preserve routing information temporarily while a control plane reconverges. The focused prevention check is: Test stale-route timer expiry and unsupported-peer behavior before relying on graceful restart.

Question 293

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An IOS XR redundancy plan enables NSF but ignores preserving forwarding state and protocol process synchronization during switchover. What is the best authorized corrective or investigative action for this service-provider network operations situation?

  1. Keep external interdomain routes under controlled redistribution with explicit prefix and metric policy.
  2. Validate the platform's NSR or high-availability capabilities and forwarding continuity under a controlled RP failover.
  3. Trace the source protocol, route-map conditions, and possible feedback redistribution loops.
  4. Evaluate supported additional-path advertisement and BGP PIC designs consistent with platform capabilities.

Explanation

Correct Answer

B:

For this scenario, the observed situation is: An IOS XR redundancy plan enables NSF but ignores preserving forwarding state and protocol process synchronization during switchover. The most directly supported response is: Validate the platform's NSR or high-availability capabilities and forwarding continuity under a controlled RP failover. Technical basis: NSR maintains routing protocol state on redundant controllers and differs from neighbor-assisted graceful restart. Evidence of success: Adjacencies and packet forwarding remain within the documented continuity limits during RP switchover. Ongoing protection: Exercise RP switchover and process-state recovery with traffic generators.

Incorrect Answers

A:

The option fits a control for: Unbounded redistribution expands IGP state and can affect convergence and resource use. The present failure is caused by a different mechanism: NSR maintains routing protocol state on redundant controllers and differs from neighbor-assisted graceful restart. The targeted implementation is: Validate the platform's NSR or high-availability capabilities and forwarding continuity under a controlled RP failover.

C:

Redistribution without tagging and filtering can feed learned routes back into their origin domain. That principle governs the alternative intervention. The issue described here is different: NSR maintains routing protocol state on redundant controllers and differs from neighbor-assisted graceful restart. The case-matched corrective action is: Validate the platform's NSR or high-availability capabilities and forwarding continuity under a controlled RP failover.

D:

BGP Add-Paths and PIC address different multipath signaling and precomputed backup forwarding aspects. That principle governs the alternative intervention. The issue described here is different: NSR maintains routing protocol state on redundant controllers and differs from neighbor-assisted graceful restart. The case-matched corrective action is: Validate the platform's NSR or high-availability capabilities and forwarding continuity under a controlled RP failover.

Question 294

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An IOS XR redundancy plan enables NSF but ignores preserving forwarding state and protocol process synchronization during switchover. Which observable result most directly verifies that this network issue was resolved?

  1. Adjacencies and packet forwarding remain within the documented continuity limits during RP switchover.
  2. Multiple subscribers share public IPv4 addresses while logs map sessions to the correct subscriber.
  3. The selected best path matches configured attributes rather than inferred geographic proximity.
  4. The IPv6 routing table receives expected OSPFv3 routes without replacing the IPv4 service unexpectedly.

Explanation

Correct Answer

A:

For this scenario, the observed situation is: An IOS XR redundancy plan enables NSF but ignores preserving forwarding state and protocol process synchronization during switchover. The most directly supported response is: Validate the platform's NSR or high-availability capabilities and forwarding continuity under a controlled RP failover. Technical basis: NSR maintains routing protocol state on redundant controllers and differs from neighbor-assisted graceful restart. Evidence of success: Adjacencies and packet forwarding remain within the documented continuity limits during RP switchover. Ongoing protection: Exercise RP switchover and process-state recovery with traffic generators.

Incorrect Answers

B:

That observation tests a different mechanism: CGNAT multiplexes many private subscribers over limited public IPv4 address space. It cannot establish this case, whose mechanism is: NSR maintains routing protocol state on redundant controllers and differs from neighbor-assisted graceful restart. The needed verification is: Adjacencies and packet forwarding remain within the documented continuity limits during RP switchover.

C:

That observation tests a different mechanism: BGP best-path choice is policy-driven and does not simply select the fewest physical hops. It cannot establish this case, whose mechanism is: NSR maintains routing protocol state on redundant controllers and differs from neighbor-assisted graceful restart. The needed verification is: Adjacencies and packet forwarding remain within the documented continuity limits during RP switchover.

D:

That observation tests a different mechanism: OSPFv3 was designed for IPv6 routing information and has protocol differences from OSPFv2. It cannot establish this case, whose mechanism is: NSR maintains routing protocol state on redundant controllers and differs from neighbor-assisted graceful restart. The needed verification is: Adjacencies and packet forwarding remain within the documented continuity limits during RP switchover.

Question 295

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An IOS XR redundancy plan enables NSF but ignores preserving forwarding state and protocol process synchronization during switchover. Which underlying network infrastructure principle best explains the situation?

  1. NSR maintains routing protocol state on redundant controllers and differs from neighbor-assisted graceful restart.
  2. OSPF area types determine which external and summary LSAs may be flooded.
  3. IS-IS overload and high-cost advertisement can drain transit traffic without tearing down every adjacency.
  4. MAP-T supports algorithmic IPv4-to-IPv6 translation and port-set assignment rather than central per-flow NAT state.

Explanation

Correct Answer

A:

For this scenario, the observed situation is: An IOS XR redundancy plan enables NSF but ignores preserving forwarding state and protocol process synchronization during switchover. The most directly supported response is: Validate the platform's NSR or high-availability capabilities and forwarding continuity under a controlled RP failover. Technical basis: NSR maintains routing protocol state on redundant controllers and differs from neighbor-assisted graceful restart. Evidence of success: Adjacencies and packet forwarding remain within the documented continuity limits during RP switchover. Ongoing protection: Exercise RP switchover and process-state recovery with traffic generators.

Incorrect Answers

B:

The alternative principle describes: OSPF area types determine which external and summary LSAs may be flooded. In this question, the decisive mechanism is: NSR maintains routing protocol state on redundant controllers and differs from neighbor-assisted graceful restart. These are distinct technical causes, even when they share a platform.

C:

The alternative principle describes: IS-IS overload and high-cost advertisement can drain transit traffic without tearing down every adjacency. In this question, the decisive mechanism is: NSR maintains routing protocol state on redundant controllers and differs from neighbor-assisted graceful restart. These are distinct technical causes, even when they share a platform.

D:

The alternative principle describes: MAP-T supports algorithmic IPv4-to-IPv6 translation and port-set assignment rather than central per-flow NAT state. In this question, the decisive mechanism is: NSR maintains routing protocol state on redundant controllers and differs from neighbor-assisted graceful restart. These are distinct technical causes, even when they share a platform.

Question 296

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An IOS XR redundancy plan enables NSF but ignores preserving forwarding state and protocol process synchronization during switchover. Which continuing control best reduces recurrence of this problem?

  1. Test VPN AFI/SAFI and route-target policy during PE provisioning.
  2. Use route-state and next-hop resolution verification in route-reflector troubleshooting.
  3. Exercise RP switchover and process-state recovery with traffic generators.
  4. Review redistribution policy and route limits after adding external peers.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: An IOS XR redundancy plan enables NSF but ignores preserving forwarding state and protocol process synchronization during switchover. The most directly supported response is: Validate the platform's NSR or high-availability capabilities and forwarding continuity under a controlled RP failover. Technical basis: NSR maintains routing protocol state on redundant controllers and differs from neighbor-assisted graceful restart. Evidence of success: Adjacencies and packet forwarding remain within the documented continuity limits during RP switchover. Ongoing protection: Exercise RP switchover and process-state recovery with traffic generators.

Incorrect Answers

A:

That recurring practice manages a separate exposure: BGP address families carry different kinds of NLRI and require explicit peer activation. The present case instead depends on: NSR maintains routing protocol state on redundant controllers and differs from neighbor-assisted graceful restart. The suitable ongoing safeguard is: Exercise RP switchover and process-state recovery with traffic generators.

B:

That recurring practice manages a separate exposure: BGP may retain several path candidates while selecting a subset for best-path and forwarding use. The present case instead depends on: NSR maintains routing protocol state on redundant controllers and differs from neighbor-assisted graceful restart. The suitable ongoing safeguard is: Exercise RP switchover and process-state recovery with traffic generators.

D:

Unbounded redistribution expands IGP state and can affect convergence and resource use. Maintaining that control would not track the failure described here. The relevant risk is: NSR maintains routing protocol state on redundant controllers and differs from neighbor-assisted graceful restart. Review this instead: Exercise RP switchover and process-state recovery with traffic generators.

Question 297

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A provider bundles physical interfaces but forwarding becomes uneven because member links use incompatible speed and LACP settings. What is the best authorized corrective or investigative action for this service-provider network operations situation?

  1. Align supported member speed, duplex, LACP parameters and hash behavior for the bundle.
  2. Configure the correct private-to-public translation boundary at the customer edge.
  3. Review BGP best-path attributes in their selection order, starting with locally relevant preference settings.
  4. Compare BGP accepted NLRI, best-path state, route distance, and installed RIB entries.

Explanation

Correct Answer

A:

For this scenario, the observed situation is: A provider bundles physical interfaces but forwarding becomes uneven because member links use incompatible speed and LACP settings. The most directly supported response is: Align supported member speed, duplex, LACP parameters and hash behavior for the bundle. Technical basis: Link aggregation combines compatible physical members into one logical forwarding interface. Evidence of success: The port-channel reaches the intended member count and distributes eligible flows without errors. Ongoing protection: Monitor member consistency and test single-link failover.

Incorrect Answers

B:

NAT44 rewrites IPv4 addressing across a defined inside and outside interface boundary. That principle governs the alternative intervention. The issue described here is different: Link aggregation combines compatible physical members into one logical forwarding interface. The case-matched corrective action is: Align supported member speed, duplex, LACP parameters and hash behavior for the bundle.

C:

The proposed option addresses this separate mechanism: BGP best-path choice is policy-driven and does not simply select the fewest physical hops. The stated problem instead depends on: Link aggregation combines compatible physical members into one logical forwarding interface. The required response is: Align supported member speed, duplex, LACP parameters and hash behavior for the bundle.

D:

The proposed option addresses this separate mechanism: Reception of BGP NLRI does not necessarily imply RIB or FIB installation. The stated problem instead depends on: Link aggregation combines compatible physical members into one logical forwarding interface. The required response is: Align supported member speed, duplex, LACP parameters and hash behavior for the bundle.

Question 298

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A provider bundles physical interfaces but forwarding becomes uneven because member links use incompatible speed and LACP settings. Which observable result most directly verifies that this network issue was resolved?

  1. The port-channel reaches the intended member count and distributes eligible flows without errors.
  2. Unauthorized more-specific routes are rejected and the authorized aggregate remains accepted.
  3. The BFD session remains stable at a supported detection setting and BGP no longer flaps.
  4. The winning route follows the configured best-path algorithm with origin type considered at its proper stage.

Explanation

Correct Answer

A:

For this scenario, the observed situation is: A provider bundles physical interfaces but forwarding becomes uneven because member links use incompatible speed and LACP settings. The most directly supported response is: Align supported member speed, duplex, LACP parameters and hash behavior for the bundle. Technical basis: Link aggregation combines compatible physical members into one logical forwarding interface. Evidence of success: The port-channel reaches the intended member count and distributes eligible flows without errors. Ongoing protection: Monitor member consistency and test single-link failover.

Incorrect Answers

B:

Prefix-set ge and le bounds determine which subnet lengths a policy can match. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: Link aggregation combines compatible physical members into one logical forwarding interface. A passing check should show: The port-channel reaches the intended member count and distributes eligible flows without errors.

C:

BFD can trigger routing adjacency teardown faster than protocol-native hold timers. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: Link aggregation combines compatible physical members into one logical forwarding interface. A passing check should show: The port-channel reaches the intended member count and distributes eligible flows without errors.

D:

BGP origin is one of several ordered best-path criteria, not a universal primary selector. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: Link aggregation combines compatible physical members into one logical forwarding interface. A passing check should show: The port-channel reaches the intended member count and distributes eligible flows without errors.

Question 299

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A provider bundles physical interfaces but forwarding becomes uneven because member links use incompatible speed and LACP settings. Which underlying network infrastructure principle best explains the situation?

  1. IS-IS multitopology can maintain separate route calculations for distinct supported protocol topologies.
  2. OSPFv3 retains a 32-bit router identifier even though it exchanges IPv6 reachability.
  3. IOS XR RPL has distinct decision syntax and default disposition behavior from IOS route maps.
  4. Link aggregation combines compatible physical members into one logical forwarding interface.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: A provider bundles physical interfaces but forwarding becomes uneven because member links use incompatible speed and LACP settings. The most directly supported response is: Align supported member speed, duplex, LACP parameters and hash behavior for the bundle. Technical basis: Link aggregation combines compatible physical members into one logical forwarding interface. Evidence of success: The port-channel reaches the intended member count and distributes eligible flows without errors. Ongoing protection: Monitor member consistency and test single-link failover.

Incorrect Answers

A:

IS-IS multitopology can maintain separate route calculations for distinct supported protocol topologies. That is not the causal relationship tested by the current facts. The relevant principle is: Link aggregation combines compatible physical members into one logical forwarding interface.

B:

OSPFv3 retains a 32-bit router identifier even though it exchanges IPv6 reachability. That is not the causal relationship tested by the current facts. The relevant principle is: Link aggregation combines compatible physical members into one logical forwarding interface.

C:

IOS XR RPL has distinct decision syntax and default disposition behavior from IOS route maps. That is not the causal relationship tested by the current facts. The relevant principle is: Link aggregation combines compatible physical members into one logical forwarding interface.

Question 300

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A provider bundles physical interfaces but forwarding becomes uneven because member links use incompatible speed and LACP settings. Which continuing control best reduces recurrence of this problem?

  1. Maintain OS-specific routing policy snippets with regression cases.
  2. Test stub and NSSA behavior before deploying common area profiles.
  3. Validate backup next-hop resources and failover under realistic route scale.
  4. Monitor member consistency and test single-link failover.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: A provider bundles physical interfaces but forwarding becomes uneven because member links use incompatible speed and LACP settings. The most directly supported response is: Align supported member speed, duplex, LACP parameters and hash behavior for the bundle. Technical basis: Link aggregation combines compatible physical members into one logical forwarding interface. Evidence of success: The port-channel reaches the intended member count and distributes eligible flows without errors. Ongoing protection: Monitor member consistency and test single-link failover.

Incorrect Answers

A:

Cisco route-policy languages differ across operating systems and cannot always be pasted interchangeably. Maintaining that control would not track the failure described here. The relevant risk is: Link aggregation combines compatible physical members into one logical forwarding interface. Review this instead: Monitor member consistency and test single-link failover.

B:

OSPF area types determine which external and summary LSAs may be flooded. Maintaining that control would not track the failure described here. The relevant risk is: Link aggregation combines compatible physical members into one logical forwarding interface. Review this instead: Monitor member consistency and test single-link failover.

C:

BGP Add-Paths and PIC address different multipath signaling and precomputed backup forwarding aspects. Maintaining that control would not track the failure described here. The relevant risk is: Link aggregation combines compatible physical members into one logical forwarding interface. Review this instead: Monitor member consistency and test single-link failover.