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 37

Question 360

For a mobile packet-core transport operator, the change record describes: 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. What preventive validation should be standard?

  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. Track model-capability inventory and regression-test software upgrades.
  4. Require RPC reply and postchange readback checks for configuration jobs.

Explanation

Correct Answer

A:

Validate endpoint scheme, port and trust chain before each API integration rollout. This helps prevent recurrence of the 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. Acceptance evidence should be: A controlled request succeeds over authenticated TLS while plaintext attempts are rejected.

Incorrect Answers

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: Validate endpoint scheme, port and trust chain before each API integration rollout.

C:

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: Validate endpoint scheme, port and trust chain before each API integration rollout.

D:

Require RPC reply and postchange readback checks for configuration jobs. That is a sensible control for ANOTHER scenario: A NETCONF RPC returns an `<rpc-error>` element but a script reports success because the SSH TCP session remained connected. It is less targeted to this issue than: Validate endpoint scheme, port and trust chain before each API integration rollout.

Question 361

For a managed VPN service carrier, the failure is: A controller automation receives HTTP 202 from an IOS XR change job and records completion even though the backend still reports pending work. Which authorized correction best addresses it?

  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. Scope inventory groups and host limits to approved lab or PoP devices before network configuration tasks run.

Explanation

Correct Answer

C:

Poll the documented task status and verify actual configured state before closing the change. This directly addresses the fictional service-provider network case: A controller automation receives HTTP 202 from an IOS XR change job and records completion even though the backend still reports pending work. The technical mechanism is: HTTP 202 means the server accepted work, not necessarily that a change has finished or reached forwarding hardware. Verify success by: A test waits for terminal success and confirms the intended configuration; a failed task remains open for repair.

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 controller automation receives HTTP 202 from an IOS XR change job and records completion even though the backend still reports pending work.

B:

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: A controller automation receives HTTP 202 from an IOS XR change job and records completion even though the backend still reports pending work.

D:

Scope inventory groups and host limits to approved lab or PoP devices before network configuration tasks run. This would respond to a DIFFERENT fictional service-provider network issue: An Ansible network playbook uses `hosts: all` and changes every backbone router though the request approved only an isolated PoP. It does not directly address the current situation: A controller automation receives HTTP 202 from an IOS XR change job and records completion even though the backend still reports pending work.

Question 362

After fixing the following network problem, what should the team verify: A controller automation receives HTTP 202 from an IOS XR change job and records completion even though the backend still reports pending work.

  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 controlled request succeeds over authenticated TLS while plaintext attempts are rejected.
  4. A test waits for terminal success and confirms the intended configuration; a failed task remains open for repair.

Explanation

Correct Answer

D:

A test waits for terminal success and confirms the intended configuration; a failed task remains open for repair. This confirms the approved response: Poll the documented task status and verify actual configured state before closing the change. It is relevant because: HTTP 202 means the server accepted work, not necessarily that a change has finished or reached forwarding hardware.

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: Poll the documented task status and verify actual configured state before closing the change.

B:

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: Poll the documented task status and verify actual configured state before closing the change.

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: Poll the documented task status and verify actual configured state before closing the change.

Question 363

A carrier root-cause review considers: A controller automation receives HTTP 202 from an IOS XR change job and records completion even though the backend still reports pending work. What underlying mechanism explains this?

  1. HTTP 202 means the server accepted work, not necessarily that a change has finished or reached forwarding hardware.
  2. HTTP API methods require supported representations, and mismatched media types can block configuration before authorization of the actual change.
  3. Network automation retries can create duplicate side effects unless operation identity and idempotency are managed.
  4. Ansible host selection controls deployment blast radius independently of the syntax of the configured tasks.

Explanation

Correct Answer

A:

HTTP 202 means the server accepted work, not necessarily that a change has finished or reached forwarding hardware. This explains the investigated issue: A controller automation receives HTTP 202 from an IOS XR change job and records completion even though the backend still reports pending work. The approved corrective response is: Poll the documented task status and verify actual configured state before closing the change.

Incorrect Answers

B:

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

C:

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 202 means the server accepted work, not necessarily that a change has finished or reached forwarding hardware.

D:

Ansible host selection controls deployment blast radius independently of the syntax of the configured tasks. That explains a DIFFERENT scenario: An Ansible network playbook uses `hosts: all` and changes every backbone router though the request approved only an isolated PoP. The mechanism to prioritize for this question is: HTTP 202 means the server accepted work, not necessarily that a change has finished or reached forwarding hardware.

Question 364

After addressing: A controller automation receives HTTP 202 from an IOS XR change job and records completion even though the backend still reports pending work. Which recurring service assurance check is most useful?

  1. Contract-test request headers and payload formats against each platform API version.
  2. Define task completion and readback gates for asynchronous API mutations.
  3. Require read-before-write or idempotency controls on mutating API workflows.
  4. Record firewall direction and streaming mode in each telemetry service definition.

Explanation

Correct Answer

B:

Define task completion and readback gates for asynchronous API mutations. This helps prevent recurrence of the issue: A controller automation receives HTTP 202 from an IOS XR change job and records completion even though the backend still reports pending work. Acceptance evidence should be: A test waits for terminal success and confirms the intended configuration; a failed task remains open for repair.

Incorrect Answers

A:

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

C:

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: Define task completion and readback gates for asynchronous API mutations.

D:

Record firewall direction and streaming mode in each telemetry service definition. That is a sensible control for ANOTHER scenario: A telemetry design requires continuous interface counters from devices behind outbound-only firewalls, but the collector tries to initiate dial-in sessions to inaccessible management addresses. It is less targeted to this issue than: Define task completion and readback gates for asynchronous API mutations.

Question 365

A provider backbone escalation identifies: A service-provider engineer edits generated device CLI directly while NSO still owns the declared service, and reconciliation restores the unwanted old settings overnight. What should the network team implement?

  1. Model the service with a supported Cisco NSO package and transactional orchestration across the participating devices.
  2. Bind service parameters to authoritative inventory and validate device identity and service endpoints before committing.
  3. Align authorized SNMP notification-source addresses and collector access lists with all intended router loopbacks.
  4. Update the source service instance and template and redeploy through the authorized NSO service workflow.

Explanation

Correct Answer

D:

Update the source service instance and template and redeploy through the authorized NSO service workflow. This directly addresses the fictional service-provider network case: A service-provider engineer edits generated device CLI directly while NSO still owns the declared service, and reconciliation restores the unwanted old settings overnight. The technical mechanism is: Model-driven orchestrators can overwrite out-of-band changes because their service model remains authoritative. Verify success by: Device configuration converges to the revised service intent and repeated reconciliation produces no unexpected changes.

Incorrect Answers

A:

Model the service with a supported Cisco NSO package and transactional orchestration across the participating devices. This would respond to a DIFFERENT fictional service-provider network issue: A wholesale provider manages one L3VPN service through separate scripts on five routers and cannot roll back when the third router rejects a policy. It does not directly address the current situation: A service-provider engineer edits generated device CLI directly while NSO still owns the declared service, and reconciliation restores the unwanted old settings overnight.

B:

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: A service-provider engineer edits generated device CLI directly while NSO still owns the declared service, and reconciliation restores the unwanted old settings overnight.

C:

Align authorized SNMP notification-source addresses and collector access lists with all intended router loopbacks. This would respond to a DIFFERENT fictional service-provider network issue: A trap receiver processes authenticationFailure SNMP notifications but drops interfaceDown events because its trap ACL permits only one source subnet. It does not directly address the current situation: A service-provider engineer edits generated device CLI directly while NSO still owns the declared service, and reconciliation restores the unwanted old settings overnight.

Question 366

A service-provider operations test targets: A service-provider engineer edits generated device CLI directly while NSO still owns the declared service, and reconciliation restores the unwanted old settings overnight. Which result is required?

  1. Device configuration converges to the revised service intent and repeated reconciliation produces no unexpected changes.
  2. The dry-run diff lists only the intended PE and interface while the old PE remains unchanged.
  3. A failure-injection test records a coherent service transaction outcome and restores previously changed routers when supported.
  4. An SNMP walk finds the expected instance and polling returns a plausible CPU sample from the correct scope.

Explanation

Correct Answer

A:

Device configuration converges to the revised service intent and repeated reconciliation produces no unexpected changes. This confirms the approved response: Update the source service instance and template and redeploy through the authorized NSO service workflow. It is relevant because: Model-driven orchestrators can overwrite out-of-band changes because their service model remains authoritative.

Incorrect Answers

B:

The dry-run diff lists only the intended PE and interface while the old PE remains unchanged. This would validate ANOTHER scenario: An NSO service template reuses a stale network element device ID, so new customer interface configuration is pushed to the wrong PE. The specific correction here is: Update the source service instance and template and redeploy through the authorized NSO service workflow.

C:

A failure-injection test records a coherent service transaction outcome and restores previously changed routers when supported. This would validate ANOTHER scenario: A wholesale provider manages one L3VPN service through separate scripts on five routers and cannot roll back when the third router rejects a policy. The specific correction here is: Update the source service instance and template and redeploy through the authorized NSO service workflow.

D:

An SNMP walk finds the expected instance and polling returns a plausible CPU sample from the correct scope. This would validate ANOTHER scenario: A monitoring backend discovers no device CPU metric because it queries a nonexistent vendor OID and assumes the router is down. The specific correction here is: Update the source service instance and template and redeploy through the authorized NSO service workflow.

Question 367

A provider troubleshooting note states: A service-provider engineer edits generated device CLI directly while NSO still owns the declared service, and reconciliation restores the unwanted old settings overnight. Which mechanism is central?

  1. Service orchestration correctness depends on accurate device and service inventory bindings.
  2. Model-driven orchestrators can overwrite out-of-band changes because their service model remains authoritative.
  3. NSO can coordinate model-driven multi-device service intent and transaction management beyond independent scripting.
  4. Infrastructure as code maps declarations to state addresses, and renaming an address can look like delete-and-recreate.

Explanation

Correct Answer

B:

Model-driven orchestrators can overwrite out-of-band changes because their service model remains authoritative. This explains the investigated issue: A service-provider engineer edits generated device CLI directly while NSO still owns the declared service, and reconciliation restores the unwanted old settings overnight. The approved corrective response is: Update the source service instance and template and redeploy through the authorized NSO service workflow.

Incorrect Answers

A:

Service orchestration correctness depends on accurate device and service inventory bindings. That explains a DIFFERENT scenario: An NSO service template reuses a stale network element device ID, so new customer interface configuration is pushed to the wrong PE. The mechanism to prioritize for this question is: Model-driven orchestrators can overwrite out-of-band changes because their service model remains authoritative.

C:

NSO can coordinate model-driven multi-device service intent and transaction management beyond independent scripting. That explains a DIFFERENT scenario: A wholesale provider manages one L3VPN service through separate scripts on five routers and cannot roll back when the third router rejects a policy. The mechanism to prioritize for this question is: Model-driven orchestrators can overwrite out-of-band changes because their service model remains authoritative.

D:

Infrastructure as code maps declarations to state addresses, and renaming an address can look like delete-and-recreate. That explains a DIFFERENT scenario: A Terraform plan proposes deleting an NSO integration virtual machine because its resource label was renamed in source code without preserving state identity. The mechanism to prioritize for this question is: Model-driven orchestrators can overwrite out-of-band changes because their service model remains authoritative.

Question 368

To prevent recurrence of this provider network issue: A service-provider engineer edits generated device CLI directly while NSO still owns the declared service, and reconciliation restores the unwanted old settings overnight. Which control should be retained?

  1. Require device-selection signoff and peer review for service model changes.
  2. Exercise service transaction rollback and dry-run before production activation.
  3. Monitor configuration drift and restrict manual changes to managed service resources.
  4. Gate production Ansible runs on reviewed inventory and diff previews.

Explanation

Correct Answer

C:

Monitor configuration drift and restrict manual changes to managed service resources. This helps prevent recurrence of the issue: A service-provider engineer edits generated device CLI directly while NSO still owns the declared service, and reconciliation restores the unwanted old settings overnight. Acceptance evidence should be: Device configuration converges to the revised service intent and repeated reconciliation produces no unexpected changes.

Incorrect Answers

A:

Require device-selection signoff and peer review for service model changes. That is a sensible control for ANOTHER scenario: An NSO service template reuses a stale network element device ID, so new customer interface configuration is pushed to the wrong PE. It is less targeted to this issue than: Monitor configuration drift and restrict manual changes to managed service resources.

B:

Exercise service transaction rollback and dry-run before production activation. That is a sensible control for ANOTHER scenario: A wholesale provider manages one L3VPN service through separate scripts on five routers and cannot roll back when the third router rejects a policy. It is less targeted to this issue than: Monitor configuration drift and restrict manual changes to managed service resources.

D:

Gate production Ansible runs on reviewed inventory and diff previews. That is a sensible control for ANOTHER scenario: An Ansible network playbook uses `hosts: all` and changes every backbone router though the request approved only an isolated PoP. It is less targeted to this issue than: Monitor configuration drift and restrict manual changes to managed service resources.

Question 369

At an optical transport engineering team, an engineering review finds: Two providers exchange YANG model payloads that use identical local leaf names but different module namespaces, so parsing associates traffic counters with the wrong schema. Which change most directly corrects the service problem?

  1. Preserve the full module namespace and revision for each data path and parse namespace-qualified fields.
  2. Read operational state using the supported data retrieval API instead of treating a read-only leaf as writable configuration.
  3. Include the correct list key in the modeled resource path and validate its encoding.
  4. Use the supported secured REST API scheme, certificate validation and documented authentication for the management service.

Explanation

Correct Answer

A:

Preserve the full module namespace and revision for each data path and parse namespace-qualified fields. This directly addresses the fictional service-provider network case: Two providers exchange YANG model payloads that use identical local leaf names but different module namespaces, so parsing associates traffic counters with the wrong schema. The technical mechanism is: YANG namespaces and revisions give modeled nodes meaning beyond their unqualified display names. Verify success by: A fixture containing the two modules resolves both leaf values to their correct models without ambiguity.

Incorrect Answers

B:

Read operational state using the supported data retrieval API instead of treating a read-only leaf as writable configuration. This would respond to a DIFFERENT fictional service-provider network issue: A network operator attempts to PATCH a YANG counter marked `config false`, then blames access control when the edit is rejected. It does not directly address the current situation: Two providers exchange YANG model payloads that use identical local leaf names but different module namespaces, so parsing associates traffic counters with the wrong schema.

C:

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: Two providers exchange YANG model payloads that use identical local leaf names but different module namespaces, so parsing associates traffic counters with the wrong schema.

D:

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: Two providers exchange YANG model payloads that use identical local leaf names but different module namespaces, so parsing associates traffic counters with the wrong schema.

Question 370

For an optical transport engineering team, operators addressed: Two providers exchange YANG model payloads that use identical local leaf names but different module namespaces, so parsing associates traffic counters with the wrong schema. What is the strongest acceptance evidence?

  1. The targeted interface changes while other interfaces remain byte-for-byte unchanged.
  2. A fixture containing the two modules resolves both leaf values to their correct models without ambiguity.
  3. Counter retrieval succeeds and a controlled mutation remains rejected by schema or datastore rules.
  4. A compatibility test only edits leaves present in each device's advertised schema, with unsupported devices safely excluded.

Explanation

Correct Answer

B:

A fixture containing the two modules resolves both leaf values to their correct models without ambiguity. This confirms the approved response: Preserve the full module namespace and revision for each data path and parse namespace-qualified fields. It is relevant because: YANG namespaces and revisions give modeled nodes meaning beyond their unqualified display names.

Incorrect Answers

A:

The targeted interface changes while other interfaces remain byte-for-byte unchanged. This would validate ANOTHER scenario: 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. The specific correction here is: Preserve the full module namespace and revision for each data path and parse namespace-qualified fields.

C:

Counter retrieval succeeds and a controlled mutation remains rejected by schema or datastore rules. This would validate ANOTHER scenario: A network operator attempts to PATCH a YANG counter marked `config false`, then blames access control when the edit is rejected. The specific correction here is: Preserve the full module namespace and revision for each data path and parse namespace-qualified fields.

D:

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: Preserve the full module namespace and revision for each data path and parse namespace-qualified fields.