McAfee-Secured Website

Exam Bundle

Exam Code: 350-501

Exam Name Implementing and Operating Cisco Service Provider Network Core Technologies (SPCOR)

Certification Provider: Cisco

Corresponding Certifications: CCIE Service Provider , CCNP Service Provider

Cisco 350-501 Bundle $28.79

100% Cisco 350-501 Guaranteed Success With Testking Training Materials

Get Real 350-501 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    350-501 Questions & Answers

    528 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual 350-501 exam while allowing you to hone and measure every aspect of your test-taking ability.

  • 350-501 Video Course

    350-501 Video Course

    253 Video Lectures

    350-501 Video Course is developed by Cisco Professionals to help you pass the 350-501 exam.

    Description

    This course will improve your knowledge and skills required to pass Implementing and Operating Cisco Service Provider Network Core Technologies (SPCOR) exam.
  • Study Guide

    350-501 Study Guide

    1160 PDF Pages

    Developed by industry experts, this 1160-page guide spells out in painstaking detail all of the information you need to ace 350-501 exam.

Implementing and Operating Cisco Service Provider Network Core Technologies (SPCOR) (350-501) Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $189.97
Bundle Price: $161.18

Purchase Individually

  • Questions & Answers

    Questions & Answers

    528 Questions

    $124.99
  • 350-501 Video Course

    Video Course

    253 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    1160 PDF Pages

    $24.99

Cisco 350-501 Practice Test 23

Question 220

After addressing: A PIM-SM receiver router has no route to the configured rendezvous point, and (*,G) state never forms for ASM traffic. Which recurring service assurance check is most useful?

  1. Test DR state when changing multicast LAN interfaces.
  2. Monitor RP reachability and failover under multicast service SLAs.
  3. Include both IGMP and MLD listener tests on dual-stack access nodes.
  4. Include stale route and next-hop cleanup in VPN site migrations.

Explanation

Correct Answer

B:

Monitor RP reachability and failover under multicast service SLAs. This helps prevent recurrence of the issue: A PIM-SM receiver router has no route to the configured rendezvous point, and (*,G) state never forms for ASM traffic. Acceptance evidence should be: PIM neighbor and multicast route views show RP reachability and correct shared-tree traffic delivery.

Incorrect Answers

A:

Test DR state when changing multicast LAN interfaces. That is a sensible control for ANOTHER scenario: Two multicast access routers each act as designated router for the same LAN after a timer mismatch and receivers see repeated source register behavior. It is less targeted to this issue than: Monitor RP reachability and failover under multicast service SLAs.

C:

Include both IGMP and MLD listener tests on dual-stack access nodes. That is a sensible control for ANOTHER scenario: An IPv6 multicast receiver joins an MLDv2 group, but the adjacent router polls only IGMP state and reports no listeners. It is less targeted to this issue than: Monitor RP reachability and failover under multicast service SLAs.

D:

Include stale route and next-hop cleanup in VPN site migrations. That is a sensible control for ANOTHER scenario: A carrier moves an enterprise's primary VPN site but retains an old CE static route in the remote VRF, steering packets to the retired PE. It is less targeted to this issue than: Monitor RP reachability and failover under multicast service SLAs.

Question 221

A provider backbone escalation identifies: A traffic shaper is configured with a committed rate lower than the contracted customer rate and drops bursts even though physical uplink capacity is idle. What should the network team implement?

  1. Classify backup traffic into an appropriate weighted queue and limit the priority queue to approved delay-sensitive flows.
  2. Use shaping where buffering is appropriate or retune policing burst allowances to the intended contract.
  3. Apply customer-specific BGP policy reflecting primary/backup preference and validate failure-state reroute.
  4. Recalculate shaping rate and burst parameters from the service contract and platform queue behavior.

Explanation

Correct Answer

D:

Recalculate shaping rate and burst parameters from the service contract and platform queue behavior. This directly addresses the fictional service-provider network case: A traffic shaper is configured with a committed rate lower than the contracted customer rate and drops bursts even though physical uplink capacity is idle. The technical mechanism is: Traffic shaping delays excess traffic to conform to a rate, with behavior shaped by token and queue parameters. Verify success by: A rate-controlled test reaches the agreed throughput while excess traffic is buffered or scheduled within policy.

Incorrect Answers

A:

Classify backup traffic into an appropriate weighted queue and limit the priority queue to approved delay-sensitive flows. This would respond to a DIFFERENT fictional service-provider network issue: A high-volume backup class is placed in the same strict-priority queue as voice, starving the provider's control and ordinary traffic. It does not directly address the current situation: A traffic shaper is configured with a committed rate lower than the contracted customer rate and drops bursts even though physical uplink capacity is idle.

B:

Use shaping where buffering is appropriate or retune policing burst allowances to the intended contract. This would respond to a DIFFERENT fictional service-provider network issue: An access policy applies a strict policer to interactive traffic and expects it to smooth bursts like a shaper, resulting in avoidable packet discards. It does not directly address the current situation: A traffic shaper is configured with a committed rate lower than the contracted customer rate and drops bursts even though physical uplink capacity is idle.

C:

Apply customer-specific BGP policy reflecting primary/backup preference and validate failure-state reroute. This would respond to a DIFFERENT fictional service-provider network issue: A customer VRF needs dual-homed connectivity yet the provider sets local preference to favor the backup for all customer routes, causing avoidable transit cost. It does not directly address the current situation: A traffic shaper is configured with a committed rate lower than the contracted customer rate and drops bursts even though physical uplink capacity is idle.

Question 222

A service-provider operations test targets: A traffic shaper is configured with a committed rate lower than the contracted customer rate and drops bursts even though physical uplink capacity is idle. Which result is required?

  1. A rate-controlled test reaches the agreed throughput while excess traffic is buffered or scheduled within policy.
  2. A test burst within authorized limits traverses with predictable delay and without unnecessary drops.
  3. During deliberate congestion, both sites show the intended class distribution and measurable queuing behavior.
  4. Each tenant can reach its own 10.10.0.0/16 destinations without reaching the other tenant's overlapping addresses.

Explanation

Correct Answer

A:

A rate-controlled test reaches the agreed throughput while excess traffic is buffered or scheduled within policy. This confirms the approved response: Recalculate shaping rate and burst parameters from the service contract and platform queue behavior. It is relevant because: Traffic shaping delays excess traffic to conform to a rate, with behavior shaped by token and queue parameters.

Incorrect Answers

B:

A test burst within authorized limits traverses with predictable delay and without unnecessary drops. This would validate ANOTHER scenario: An access policy applies a strict policer to interactive traffic and expects it to smooth bursts like a shaper, resulting in avoidable packet discards. The specific correction here is: Recalculate shaping rate and burst parameters from the service contract and platform queue behavior.

C:

During deliberate congestion, both sites show the intended class distribution and measurable queuing behavior. This would validate ANOTHER scenario: Two sites use identical DSCP values but only one interface applies a queue scheduler, and the team assumes packet marking alone guarantees bandwidth on both links. The specific correction here is: Recalculate shaping rate and burst parameters from the service contract and platform queue behavior.

D:

Each tenant can reach its own 10.10.0.0/16 destinations without reaching the other tenant's overlapping addresses. This would validate ANOTHER scenario: Two customers use the same 10.10.0.0/16 prefix but a PE leaks VPNv4 routes into its global table, incorrectly merging their routing contexts. The specific correction here is: Recalculate shaping rate and burst parameters from the service contract and platform queue behavior.

Question 223

A provider troubleshooting note states: A traffic shaper is configured with a committed rate lower than the contracted customer rate and drops bursts even though physical uplink capacity is idle. Which mechanism is central?

  1. Policing typically drops or remarks traffic above a threshold, whereas shaping queues traffic to smooth transmission.
  2. Traffic shaping delays excess traffic to conform to a rate, with behavior shaped by token and queue parameters.
  3. Classification and marking label traffic, but congestion handling depends on actual queue and scheduling policies at bottlenecks.
  4. Inter-AS VPN models differ in whether VRFs, labeled IPv4 or VPNv4 NLRI are exchanged at the border.

Explanation

Correct Answer

B:

Traffic shaping delays excess traffic to conform to a rate, with behavior shaped by token and queue parameters. This explains the investigated issue: A traffic shaper is configured with a committed rate lower than the contracted customer rate and drops bursts even though physical uplink capacity is idle. The approved corrective response is: Recalculate shaping rate and burst parameters from the service contract and platform queue behavior.

Incorrect Answers

A:

Policing typically drops or remarks traffic above a threshold, whereas shaping queues traffic to smooth transmission. That explains a DIFFERENT scenario: An access policy applies a strict policer to interactive traffic and expects it to smooth bursts like a shaper, resulting in avoidable packet discards. The mechanism to prioritize for this question is: Traffic shaping delays excess traffic to conform to a rate, with behavior shaped by token and queue parameters.

C:

Classification and marking label traffic, but congestion handling depends on actual queue and scheduling policies at bottlenecks. That explains a DIFFERENT scenario: Two sites use identical DSCP values but only one interface applies a queue scheduler, and the team assumes packet marking alone guarantees bandwidth on both links. The mechanism to prioritize for this question is: Traffic shaping delays excess traffic to conform to a rate, with behavior shaped by token and queue parameters.

D:

Inter-AS VPN models differ in whether VRFs, labeled IPv4 or VPNv4 NLRI are exchanged at the border. That explains a DIFFERENT scenario: An inter-AS L3VPN reaches the first provider but customer prefixes vanish at the AS boundary because VPNv4 routes and label context are not exchanged under the chosen inter-AS model. The mechanism to prioritize for this question is: Traffic shaping delays excess traffic to conform to a rate, with behavior shaped by token and queue parameters.

Question 224

To prevent recurrence of this provider network issue: A traffic shaper is configured with a committed rate lower than the contracted customer rate and drops bursts even though physical uplink capacity is idle. Which control should be retained?

  1. Include untrusted DSCP abuse tests at provider access interfaces.
  2. Test queue fairness and priority traffic caps at oversubscription.
  3. Record shaper configuration and measured burst response for each access product.
  4. Review RPL ownership and ring state during ring expansion.

Explanation

Correct Answer

C:

Record shaper configuration and measured burst response for each access product. This helps prevent recurrence of the issue: A traffic shaper is configured with a committed rate lower than the contracted customer rate and drops bursts even though physical uplink capacity is idle. Acceptance evidence should be: A rate-controlled test reaches the agreed throughput while excess traffic is buffered or scheduled within policy.

Incorrect Answers

A:

Include untrusted DSCP abuse tests at provider access interfaces. That is a sensible control for ANOTHER scenario: A customer sends traffic marked CS6 from its access port and expects unlimited priority throughout the provider despite not purchasing a network-control service class. It is less targeted to this issue than: Record shaper configuration and measured burst response for each access product.

B:

Test queue fairness and priority traffic caps at oversubscription. That is a sensible control for ANOTHER scenario: A high-volume backup class is placed in the same strict-priority queue as voice, starving the provider's control and ordinary traffic. It is less targeted to this issue than: Record shaper configuration and measured burst response for each access product.

D:

Review RPL ownership and ring state during ring expansion. That is a sensible control for ANOTHER scenario: A G.8032 Ethernet ring sees a broadcast storm after a ring protection link is accidentally forwarding on both sides of a stable ring. It is less targeted to this issue than: Record shaper configuration and measured burst response for each access product.

Question 225

At a regional service-provider operations center, an engineering review finds: A controller deploys a single RESTCONF configuration template to devices running different firmware but fails when one model revision lacks the targeted leaf. Which change most directly corrects the service problem?

  1. Negotiate or discover the supported YANG model revision per router before composing the RESTCONF edit.
  2. Select the documented IOS XR model-driven API and matching YANG operational path with authenticated transport.
  3. Use the supported secured REST API scheme, certificate validation and documented authentication for the management service.
  4. Use an appropriate supported state move or resource refactor after reviewing destructive plan actions.

Explanation

Correct Answer

A:

Negotiate or discover the supported YANG model revision per router before composing the RESTCONF edit. This directly addresses the fictional service-provider network case: A controller deploys a single RESTCONF configuration template to devices running different firmware but fails when one model revision lacks the targeted leaf. The technical mechanism is: Model-driven APIs are constrained by actual module and revision support, not just by having an HTTPS listener. Verify success by: A compatibility test only edits leaves present in each device's advertised schema, with unsupported devices safely excluded.

Incorrect Answers

B:

Select the documented IOS XR model-driven API and matching YANG operational path with authenticated transport. This would respond to a DIFFERENT fictional service-provider network issue: A provider telemetry collector expects every IOS XR interface state query to use a generic SNMP community string while the device exposes a supported model-driven operational endpoint. It does not directly address the current situation: A controller deploys a single RESTCONF configuration template to devices running different firmware but fails when one model revision lacks the targeted leaf.

C:

Use the supported secured REST API scheme, certificate validation and documented authentication for the management service. This would respond to a DIFFERENT fictional service-provider network issue: An operations client sends an unencrypted HTTP call to a management endpoint that requires TLS and reports a protocol failure as an unreachable routing prefix. It does not directly address the current situation: A controller deploys a single RESTCONF configuration template to devices running different firmware but fails when one model revision lacks the targeted leaf.

D:

Use an appropriate supported state move or resource refactor after reviewing destructive plan actions. This would respond to a DIFFERENT fictional service-provider network issue: A Terraform plan proposes deleting an NSO integration virtual machine because its resource label was renamed in source code without preserving state identity. It does not directly address the current situation: A controller deploys a single RESTCONF configuration template to devices running different firmware but fails when one model revision lacks the targeted leaf.

Question 226

For a regional service-provider operations center, operators addressed: A controller deploys a single RESTCONF configuration template to devices running different firmware but fails when one model revision lacks the targeted leaf. What is the strongest acceptance evidence?

  1. A controlled request succeeds over authenticated TLS while plaintext attempts are rejected.
  2. A compatibility test only edits leaves present in each device's advertised schema, with unsupported devices safely excluded.
  3. A read-only fixture returns the correct interface counters without changing running configuration.
  4. An authorized monitoring poll succeeds under protected SNMPv3 while an unauthorized v2c request fails.

Explanation

Correct Answer

B:

A compatibility test only edits leaves present in each device's advertised schema, with unsupported devices safely excluded. This confirms the approved response: Negotiate or discover the supported YANG model revision per router before composing the RESTCONF edit. It is relevant because: Model-driven APIs are constrained by actual module and revision support, not just by having an HTTPS listener.

Incorrect Answers

A:

A controlled request succeeds over authenticated TLS while plaintext attempts are rejected. This would validate ANOTHER scenario: An operations client sends an unencrypted HTTP call to a management endpoint that requires TLS and reports a protocol failure as an unreachable routing prefix. The specific correction here is: Negotiate or discover the supported YANG model revision per router before composing the RESTCONF edit.

C:

A read-only fixture returns the correct interface counters without changing running configuration. This would validate ANOTHER scenario: A provider telemetry collector expects every IOS XR interface state query to use a generic SNMP community string while the device exposes a supported model-driven operational endpoint. The specific correction here is: Negotiate or discover the supported YANG model revision per router before composing the RESTCONF edit.

D:

An authorized monitoring poll succeeds under protected SNMPv3 while an unauthorized v2c request fails. This would validate ANOTHER scenario: A provider inventories routers using SNMPv2c with an easily guessed community on a shared management segment and exposes interface inventory to unauthorized clients. The specific correction here is: Negotiate or discover the supported YANG model revision per router before composing the RESTCONF edit.

Question 227

Which network protocol or forwarding behavior explains the following issue: A controller deploys a single RESTCONF configuration template to devices running different firmware but fails when one model revision lacks the targeted leaf.

  1. API endpoint transport and authorization constraints are independent of ordinary IP routing reachability.
  2. Cisco programmability can expose structured state through NETCONF, RESTCONF or streaming telemetry rather than one universal device protocol.
  3. Model-driven APIs are constrained by actual module and revision support, not just by having an HTTPS listener.
  4. Sampled NetFlow/IPFIX requires accounting for sampling to estimate total packet and byte counts.

Explanation

Correct Answer

C:

Model-driven APIs are constrained by actual module and revision support, not just by having an HTTPS listener. This explains the investigated issue: A controller deploys a single RESTCONF configuration template to devices running different firmware but fails when one model revision lacks the targeted leaf. The approved corrective response is: Negotiate or discover the supported YANG model revision per router before composing the RESTCONF edit.

Incorrect Answers

A:

API endpoint transport and authorization constraints are independent of ordinary IP routing reachability. That explains a DIFFERENT scenario: An operations client sends an unencrypted HTTP call to a management endpoint that requires TLS and reports a protocol failure as an unreachable routing prefix. The mechanism to prioritize for this question is: Model-driven APIs are constrained by actual module and revision support, not just by having an HTTPS listener.

B:

Cisco programmability can expose structured state through NETCONF, RESTCONF or streaming telemetry rather than one universal device protocol. That explains a DIFFERENT scenario: A provider telemetry collector expects every IOS XR interface state query to use a generic SNMP community string while the device exposes a supported model-driven operational endpoint. The mechanism to prioritize for this question is: Model-driven APIs are constrained by actual module and revision support, not just by having an HTTPS listener.

D:

Sampled NetFlow/IPFIX requires accounting for sampling to estimate total packet and byte counts. That explains a DIFFERENT scenario: A backbone flow analytics system samples one packet in 100 but its dashboard treats observed packets as complete unsampled volumes. The mechanism to prioritize for this question is: Model-driven APIs are constrained by actual module and revision support, not just by having an HTTPS listener.

Question 228

A core network change board wants to avoid: A controller deploys a single RESTCONF configuration template to devices running different firmware but fails when one model revision lacks the targeted leaf. Which ongoing safeguard fits best?

  1. Validate endpoint scheme, port and trust chain before each API integration rollout.
  2. Discover supported API transports and model revisions during device enrollment.
  3. Inspect writable-state metadata when generating automation forms from YANG models.
  4. Track model-capability inventory and regression-test software upgrades.

Explanation

Correct Answer

D:

Track model-capability inventory and regression-test software upgrades. This helps prevent recurrence of the issue: A controller deploys a single RESTCONF configuration template to devices running different firmware but fails when one model revision lacks the targeted leaf. Acceptance evidence should be: A compatibility test only edits leaves present in each device's advertised schema, with unsupported devices safely excluded.

Incorrect Answers

A:

Validate endpoint scheme, port and trust chain before each API integration rollout. That is a sensible control for ANOTHER scenario: An operations client sends an unencrypted HTTP call to a management endpoint that requires TLS and reports a protocol failure as an unreachable routing prefix. It is less targeted to this issue than: Track model-capability inventory and regression-test software upgrades.

B:

Discover supported API transports and model revisions during device enrollment. That is a sensible control for ANOTHER scenario: A provider telemetry collector expects every IOS XR interface state query to use a generic SNMP community string while the device exposes a supported model-driven operational endpoint. It is less targeted to this issue than: Track model-capability inventory and regression-test software upgrades.

C:

Inspect writable-state metadata when generating automation forms from YANG models. That is a sensible control for ANOTHER scenario: A network operator attempts to PATCH a YANG counter marked `config false`, then blames access control when the edit is rejected. It is less targeted to this issue than: Track model-capability inventory and regression-test software upgrades.

Question 229

A carrier service activation check discovers: A script uses an unscoped POST endpoint and accidentally creates multiple static routes when its retry logic repeats a successful but slow request. Which action best restores the intended behavior?

  1. Serialize the payload using the documented JSON or XML format and matching Content-Type header.
  2. Use the documented idempotent update operation or reconcile existing state before retrying a non-idempotent creation.
  3. Poll the documented task status and verify actual configured state before closing the change.
  4. Include the correct list key in the modeled resource path and validate its encoding.

Explanation

Correct Answer

B:

Use the documented idempotent update operation or reconcile existing state before retrying a non-idempotent creation. This directly addresses the fictional service-provider network case: A script uses an unscoped POST endpoint and accidentally creates multiple static routes when its retry logic repeats a successful but slow request. The technical mechanism is: Network automation retries can create duplicate side effects unless operation identity and idempotency are managed. Verify success by: Two controlled retries leave only one approved route object in the destination configuration.

Incorrect Answers

A:

Serialize the payload using the documented JSON or XML format and matching Content-Type header. This would respond to a DIFFERENT fictional service-provider network issue: An external Python script posts interface descriptions to a router API but uses an incorrect content type and receives 415 Unsupported Media Type. It does not directly address the current situation: A script uses an unscoped POST endpoint and accidentally creates multiple static routes when its retry logic repeats a successful but slow request.

C:

Poll the documented task status and verify actual configured state before closing the change. This would respond to a DIFFERENT fictional service-provider network issue: A controller automation receives HTTP 202 from an IOS XR change job and records completion even though the backend still reports pending work. It does not directly address the current situation: A script uses an unscoped POST endpoint and accidentally creates multiple static routes when its retry logic repeats a successful but slow request.

D:

Include the correct list key in the modeled resource path and validate its encoding. This would respond to a DIFFERENT fictional service-provider network issue: A YANG list declares an interface name as its key but a RESTCONF update sends a request to the list root without an instance identifier, modifying the wrong scope. It does not directly address the current situation: A script uses an unscoped POST endpoint and accidentally creates multiple static routes when its retry logic repeats a successful but slow request.

Question 230

Following a supported configuration correction, the original issue was: A script uses an unscoped POST endpoint and accidentally creates multiple static routes when its retry logic repeats a successful but slow request. Which observation verifies success?

  1. A sandbox edit returns the expected successful response and a readback shows only the intended interface description changed.
  2. A test waits for terminal success and confirms the intended configuration; a failed task remains open for repair.
  3. Two controlled retries leave only one approved route object in the destination configuration.
  4. An authorized monitoring poll succeeds under protected SNMPv3 while an unauthorized v2c request fails.

Explanation

Correct Answer

C:

Two controlled retries leave only one approved route object in the destination configuration. This confirms the approved response: Use the documented idempotent update operation or reconcile existing state before retrying a non-idempotent creation. It is relevant because: Network automation retries can create duplicate side effects unless operation identity and idempotency are managed.

Incorrect Answers

A:

A sandbox edit returns the expected successful response and a readback shows only the intended interface description changed. This would validate ANOTHER scenario: An external Python script posts interface descriptions to a router API but uses an incorrect content type and receives 415 Unsupported Media Type. The specific correction here is: Use the documented idempotent update operation or reconcile existing state before retrying a non-idempotent creation.

B:

A test waits for terminal success and confirms the intended configuration; a failed task remains open for repair. This would validate ANOTHER scenario: A controller automation receives HTTP 202 from an IOS XR change job and records completion even though the backend still reports pending work. The specific correction here is: Use the documented idempotent update operation or reconcile existing state before retrying a non-idempotent creation.

D:

An authorized monitoring poll succeeds under protected SNMPv3 while an unauthorized v2c request fails. This would validate ANOTHER scenario: A provider inventories routers using SNMPv2c with an easily guessed community on a shared management segment and exposes interface inventory to unauthorized clients. The specific correction here is: Use the documented idempotent update operation or reconcile existing state before retrying a non-idempotent creation.