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 10

Question 90

After fixing the following network problem, what should the team verify: A provider classifies customer voice using DSCP EF at ingress but a later output policy remarks it to best effort, causing jitter under congestion.

  1. A test burst within authorized limits traverses with predictable delay and without unnecessary drops.
  2. Customer test packets receive the contracted class, and provider protocol packets retain protected control priority.
  3. A packet trace to the moved prefix follows the new PE while the retired next hop disappears from service routes.
  4. Peak-load packet captures retain the expected markings and voice delay and loss remain inside the service objective.

Explanation

Correct Answer

D:

Peak-load packet captures retain the expected markings and voice delay and loss remain inside the service objective. This confirms the approved response: Preserve the contracted classification through each applicable policy stage and map EF to the intended low-latency forwarding class. It is relevant because: QoS benefits depend on consistent classification, marking and queue treatment across the full path.

Incorrect Answers

A:

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: Preserve the contracted classification through each applicable policy stage and map EF to the intended low-latency forwarding class.

B:

Customer test packets receive the contracted class, and provider protocol packets retain protected control priority. This would validate 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. The specific correction here is: Preserve the contracted classification through each applicable policy stage and map EF to the intended low-latency forwarding class.

C:

A packet trace to the moved prefix follows the new PE while the retired next hop disappears from service routes. This would validate 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. The specific correction here is: Preserve the contracted classification through each applicable policy stage and map EF to the intended low-latency forwarding class.

Question 91

A carrier root-cause review considers: A provider classifies customer voice using DSCP EF at ingress but a later output policy remarks it to best effort, causing jitter under congestion. What underlying mechanism explains this?

  1. QoS benefits depend on consistent classification, marking and queue treatment across the full path.
  2. Traffic shaping delays excess traffic to conform to a rate, with behavior shaped by token and queue parameters.
  3. Trust boundaries stop customers from impersonating carrier routing and control-plane QoS markings.
  4. Ethernet Ring Protection Switching prevents persistent L2 loops while enabling restoration after single link failures.

Explanation

Correct Answer

A:

QoS benefits depend on consistent classification, marking and queue treatment across the full path. This explains the investigated issue: A provider classifies customer voice using DSCP EF at ingress but a later output policy remarks it to best effort, causing jitter under congestion. The approved corrective response is: Preserve the contracted classification through each applicable policy stage and map EF to the intended low-latency forwarding class.

Incorrect Answers

B:

Traffic shaping delays excess traffic to conform to a rate, with behavior shaped by token and queue parameters. That explains a DIFFERENT scenario: 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 mechanism to prioritize for this question is: QoS benefits depend on consistent classification, marking and queue treatment across the full path.

C:

Trust boundaries stop customers from impersonating carrier routing and control-plane QoS markings. That explains a DIFFERENT 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. The mechanism to prioritize for this question is: QoS benefits depend on consistent classification, marking and queue treatment across the full path.

D:

Ethernet Ring Protection Switching prevents persistent L2 loops while enabling restoration after single link failures. That explains a DIFFERENT 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. The mechanism to prioritize for this question is: QoS benefits depend on consistent classification, marking and queue treatment across the full path.

Question 92

After addressing: A provider classifies customer voice using DSCP EF at ingress but a later output policy remarks it to best effort, causing jitter under congestion. Which recurring service assurance check is most useful?

  1. Test queue fairness and priority traffic caps at oversubscription.
  2. Audit per-hop QoS markings and queue drops during service activation.
  3. Compare policer drops and shaper delay under peak burst profiles.
  4. Review route leaking and label transport boundaries for every wholesale peer.

Explanation

Correct Answer

B:

Audit per-hop QoS markings and queue drops during service activation. This helps prevent recurrence of the issue: A provider classifies customer voice using DSCP EF at ingress but a later output policy remarks it to best effort, causing jitter under congestion. Acceptance evidence should be: Peak-load packet captures retain the expected markings and voice delay and loss remain inside the service objective.

Incorrect Answers

A:

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: Audit per-hop QoS markings and queue drops during service activation.

C:

Compare policer drops and shaper delay under peak burst profiles. That is a sensible control for 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. It is less targeted to this issue than: Audit per-hop QoS markings and queue drops during service activation.

D:

Review route leaking and label transport boundaries for every wholesale peer. That is a sensible control for ANOTHER scenario: A wholesale carrier provides carrier-supporting-carrier transport, but a subcontractor PE advertises customer routes into the infrastructure global table rather than using labeled backbone service separation. It is less targeted to this issue than: Audit per-hop QoS markings and queue drops during service activation.

Question 93

A provider backbone escalation identifies: 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. What should the network team implement?

  1. Negotiate or discover the supported YANG model revision per router before composing the RESTCONF edit.
  2. Use the supported secured REST API scheme, certificate validation and documented authentication for the management service.
  3. Inspect NETCONF capabilities and target an actually supported datastore and commit behavior.
  4. Select the documented IOS XR model-driven API and matching YANG operational path with authenticated transport.

Explanation

Correct Answer

D:

Select the documented IOS XR model-driven API and matching YANG operational path with authenticated transport. This directly addresses the fictional service-provider network case: 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 technical mechanism is: Cisco programmability can expose structured state through NETCONF, RESTCONF or streaming telemetry rather than one universal device protocol. Verify success by: A read-only fixture returns the correct interface counters without changing running configuration.

Incorrect Answers

A:

Negotiate or discover the supported YANG model revision per router before composing the RESTCONF edit. This would respond to a DIFFERENT fictional service-provider network issue: A controller deploys a single RESTCONF configuration template to devices running different firmware but fails when one model revision lacks the targeted leaf. It does not directly address the current situation: 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.

B:

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 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.

C:

Inspect NETCONF capabilities and target an actually supported datastore and commit behavior. This would respond to a DIFFERENT fictional service-provider network issue: A network controller sends NETCONF `edit-config` to a device but selects the candidate datastore on a platform that advertises running-only support. It does not directly address the current situation: 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.

Question 94

A service-provider operations test targets: 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. Which result is required?

  1. A read-only fixture returns the correct interface counters without changing running configuration.
  2. A compatibility test only edits leaves present in each device's advertised schema, with unsupported devices safely excluded.
  3. A controlled request succeeds over authenticated TLS while plaintext attempts are rejected.
  4. The second apply is blocked or serialized until state reconciliation completes and the final plan matches desired topology.

Explanation

Correct Answer

A:

A read-only fixture returns the correct interface counters without changing running configuration. This confirms the approved response: Select the documented IOS XR model-driven API and matching YANG operational path with authenticated transport. It is relevant because: Cisco programmability can expose structured state through NETCONF, RESTCONF or streaming telemetry rather than one universal device protocol.

Incorrect Answers

B:

A compatibility test only edits leaves present in each device's advertised schema, with unsupported devices safely excluded. This would validate ANOTHER scenario: A controller deploys a single RESTCONF configuration template to devices running different firmware but fails when one model revision lacks the targeted leaf. The specific correction here is: Select the documented IOS XR model-driven API and matching YANG operational path with authenticated transport.

C:

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: Select the documented IOS XR model-driven API and matching YANG operational path with authenticated transport.

D:

The second apply is blocked or serialized until state reconciliation completes and the final plan matches desired topology. This would validate ANOTHER scenario: Two Terraform jobs edit the same service-provider cloud network workspace in parallel, creating conflicting route-table state and duplicate resources. The specific correction here is: Select the documented IOS XR model-driven API and matching YANG operational path with authenticated transport.

Question 95

A provider troubleshooting note states: 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. Which mechanism is central?

  1. Model-driven APIs are constrained by actual module and revision support, not just by having an HTTPS listener.
  2. Cisco programmability can expose structured state through NETCONF, RESTCONF or streaming telemetry rather than one universal device protocol.
  3. API endpoint transport and authorization constraints are independent of ordinary IP routing reachability.
  4. ZTP automates initial enrollment and therefore needs strong device and bootstrap-source authenticity to avoid fleet-wide compromise.

Explanation

Correct Answer

B:

Cisco programmability can expose structured state through NETCONF, RESTCONF or streaming telemetry rather than one universal device protocol. This explains the investigated 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. The approved corrective response is: Select the documented IOS XR model-driven API and matching YANG operational path with authenticated transport.

Incorrect Answers

A:

Model-driven APIs are constrained by actual module and revision support, not just by having an HTTPS listener. That explains a DIFFERENT scenario: A controller deploys a single RESTCONF configuration template to devices running different firmware but fails when one model revision lacks the targeted leaf. The mechanism to prioritize for this question is: Cisco programmability can expose structured state through NETCONF, RESTCONF or streaming telemetry rather than one universal device protocol.

C:

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: Cisco programmability can expose structured state through NETCONF, RESTCONF or streaming telemetry rather than one universal device protocol.

D:

ZTP automates initial enrollment and therefore needs strong device and bootstrap-source authenticity to avoid fleet-wide compromise. That explains a DIFFERENT scenario: A new PE uses zero-touch provisioning over an untrusted access network but downloads a bootstrap configuration from an unsigned public HTTP server. The mechanism to prioritize for this question is: Cisco programmability can expose structured state through NETCONF, RESTCONF or streaming telemetry rather than one universal device protocol.

Question 96

To prevent recurrence of this 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. Which control should be retained?

  1. Track model-capability inventory and regression-test software upgrades.
  2. Validate endpoint scheme, port and trust chain before each API integration rollout.
  3. Discover supported API transports and model revisions during device enrollment.
  4. Monitor configuration drift and restrict manual changes to managed service resources.

Explanation

Correct Answer

C:

Discover supported API transports and model revisions during device enrollment. This helps prevent recurrence of the 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. Acceptance evidence should be: A read-only fixture returns the correct interface counters without changing running configuration.

Incorrect Answers

A:

Track model-capability inventory and regression-test software upgrades. That is a sensible control for ANOTHER scenario: A controller deploys a single RESTCONF configuration template to devices running different firmware but fails when one model revision lacks the targeted leaf. It is less targeted to this issue than: Discover supported API transports and model revisions during device enrollment.

B:

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: Discover supported API transports and model revisions during device enrollment.

D:

Monitor configuration drift and restrict manual changes to managed service resources. That is a sensible control for ANOTHER scenario: A service-provider engineer edits generated device CLI directly while NSO still owns the declared service, and reconciliation restores the unwanted old settings overnight. It is less targeted to this issue than: Discover supported API transports and model revisions during device enrollment.

Question 97

At a multi-tenant data transport provider, an engineering review finds: An external Python script posts interface descriptions to a router API but uses an incorrect content type and receives 415 Unsupported Media Type. Which change most directly corrects the service problem?

  1. Serialize the payload using the documented JSON or XML format and matching Content-Type header.
  2. Poll the documented task status and verify actual configured state before closing the change.
  3. Use the documented idempotent update operation or reconcile existing state before retrying a non-idempotent creation.
  4. Bind service parameters to authoritative inventory and validate device identity and service endpoints before committing.

Explanation

Correct Answer

A:

Serialize the payload using the documented JSON or XML format and matching Content-Type header. This directly addresses the fictional service-provider network case: An external Python script posts interface descriptions to a router API but uses an incorrect content type and receives 415 Unsupported Media Type. The technical mechanism is: HTTP API methods require supported representations, and mismatched media types can block configuration before authorization of the actual change. Verify success by: A sandbox edit returns the expected successful response and a readback shows only the intended interface description changed.

Incorrect Answers

B:

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: An external Python script posts interface descriptions to a router API but uses an incorrect content type and receives 415 Unsupported Media Type.

C:

Use the documented idempotent update operation or reconcile existing state before retrying a non-idempotent creation. This would respond to a DIFFERENT fictional service-provider network issue: A script uses an unscoped POST endpoint and accidentally creates multiple static routes when its retry logic repeats a successful but slow request. It does not directly address the current situation: An external Python script posts interface descriptions to a router API but uses an incorrect content type and receives 415 Unsupported Media Type.

D:

Bind service parameters to authoritative inventory and validate device identity and service endpoints before committing. This would respond to a DIFFERENT fictional service-provider network issue: An NSO service template reuses a stale network element device ID, so new customer interface configuration is pushed to the wrong PE. It does not directly address the current situation: An external Python script posts interface descriptions to a router API but uses an incorrect content type and receives 415 Unsupported Media Type.

Question 98

For a multi-tenant data transport provider, operators addressed: An external Python script posts interface descriptions to a router API but uses an incorrect content type and receives 415 Unsupported Media Type. What is the strongest acceptance evidence?

  1. Two controlled retries leave only one approved route object in the destination configuration.
  2. A sandbox edit returns the expected successful response and a readback shows only the intended interface description changed.
  3. A test waits for terminal success and confirms the intended configuration; a failed task remains open for repair.
  4. The second apply is blocked or serialized until state reconciliation completes and the final plan matches desired topology.

Explanation

Correct Answer

B:

A sandbox edit returns the expected successful response and a readback shows only the intended interface description changed. This confirms the approved response: Serialize the payload using the documented JSON or XML format and matching Content-Type header. It is relevant because: HTTP API methods require supported representations, and mismatched media types can block configuration before authorization of the actual change.

Incorrect Answers

A:

Two controlled retries leave only one approved route object in the destination configuration. This would validate ANOTHER scenario: A script uses an unscoped POST endpoint and accidentally creates multiple static routes when its retry logic repeats a successful but slow request. The specific correction here is: Serialize the payload using the documented JSON or XML format and matching Content-Type header.

C:

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: Serialize the payload using the documented JSON or XML format and matching Content-Type header.

D:

The second apply is blocked or serialized until state reconciliation completes and the final plan matches desired topology. This would validate ANOTHER scenario: Two Terraform jobs edit the same service-provider cloud network workspace in parallel, creating conflicting route-table state and duplicate resources. The specific correction here is: Serialize the payload using the documented JSON or XML format and matching Content-Type header.

Question 99

Which network protocol or forwarding behavior explains the following issue: An external Python script posts interface descriptions to a router API but uses an incorrect content type and receives 415 Unsupported Media Type.

  1. Network automation retries can create duplicate side effects unless operation identity and idempotency are managed.
  2. HTTP 202 means the server accepted work, not necessarily that a change has finished or reached forwarding hardware.
  3. HTTP API methods require supported representations, and mismatched media types can block configuration before authorization of the actual change.
  4. YANG `config false` identifies state data not intended for writable configuration transactions.

Explanation

Correct Answer

C:

HTTP API methods require supported representations, and mismatched media types can block configuration before authorization of the actual change. This explains the investigated issue: An external Python script posts interface descriptions to a router API but uses an incorrect content type and receives 415 Unsupported Media Type. The approved corrective response is: Serialize the payload using the documented JSON or XML format and matching Content-Type header.

Incorrect Answers

A:

Network automation retries can create duplicate side effects unless operation identity and idempotency are managed. That explains a DIFFERENT scenario: A script uses an unscoped POST endpoint and accidentally creates multiple static routes when its retry logic repeats a successful but slow request. The mechanism to prioritize for this question is: HTTP API methods require supported representations, and mismatched media types can block configuration before authorization of the actual change.

B:

HTTP 202 means the server accepted work, not necessarily that a change has finished or reached forwarding hardware. That explains a DIFFERENT 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 mechanism to prioritize for this question is: HTTP API methods require supported representations, and mismatched media types can block configuration before authorization of the actual change.

D:

YANG `config false` identifies state data not intended for writable configuration transactions. That explains a DIFFERENT scenario: A network operator attempts to PATCH a YANG counter marked `config false`, then blames access control when the edit is rejected. The mechanism to prioritize for this question is: HTTP API methods require supported representations, and mismatched media types can block configuration before authorization of the actual change.

Question 100

A core network change board wants to avoid: An external Python script posts interface descriptions to a router API but uses an incorrect content type and receives 415 Unsupported Media Type. Which ongoing safeguard fits best?

  1. Define task completion and readback gates for asynchronous API mutations.
  2. Require read-before-write or idempotency controls on mutating API workflows.
  3. Include hostname, expiry and certificate chain tests in gNMI collector deployment.
  4. Contract-test request headers and payload formats against each platform API version.

Explanation

Correct Answer

D:

Contract-test request headers and payload formats against each platform API version. This helps prevent recurrence of the issue: An external Python script posts interface descriptions to a router API but uses an incorrect content type and receives 415 Unsupported Media Type. Acceptance evidence should be: A sandbox edit returns the expected successful response and a readback shows only the intended interface description changed.

Incorrect Answers

A:

Define task completion and readback gates for asynchronous API mutations. That is a sensible control for 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. It is less targeted to this issue than: Contract-test request headers and payload formats against each platform API version.

B:

Require read-before-write or idempotency controls on mutating API workflows. That is a sensible control for ANOTHER scenario: A script uses an unscoped POST endpoint and accidentally creates multiple static routes when its retry logic repeats a successful but slow request. It is less targeted to this issue than: Contract-test request headers and payload formats against each platform API version.

C:

Include hostname, expiry and certificate chain tests in gNMI collector deployment. That is a sensible control for ANOTHER scenario: A router publishes gNMI dial-out telemetry to a collector whose TLS certificate hostname does not match the configured endpoint and fails the handshake. It is less targeted to this issue than: Contract-test request headers and payload formats against each platform API version.