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 11

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.

Question 101

A carrier service activation check discovers: A wholesale provider manages one L3VPN service through separate scripts on five routers and cannot roll back when the third router rejects a policy. Which action best restores the intended behavior?

  1. Bind service parameters to authoritative inventory and validate device identity and service endpoints before committing.
  2. Model the service with a supported Cisco NSO package and transactional orchestration across the participating devices.
  3. Update the source service instance and template and redeploy through the authorized NSO service workflow.
  4. Issue scoped device-specific bootstrap credentials or authenticated identities with lifecycle and revocation controls.

Explanation

Correct Answer

B:

Model the service with a supported Cisco NSO package and transactional orchestration across the participating devices. This directly addresses the fictional service-provider network case: 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 technical mechanism is: NSO can coordinate model-driven multi-device service intent and transaction management beyond independent scripting. Verify success by: A failure-injection test records a coherent service transaction outcome and restores previously changed routers when supported.

Incorrect Answers

A:

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 wholesale provider manages one L3VPN service through separate scripts on five routers and cannot roll back when the third router rejects a policy.

C:

Update the source service instance and template and redeploy through the authorized NSO service workflow. This would respond to a DIFFERENT fictional service-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. It does not directly address the current situation: A wholesale provider manages one L3VPN service through separate scripts on five routers and cannot roll back when the third router rejects a policy.

D:

Issue scoped device-specific bootstrap credentials or authenticated identities with lifecycle and revocation controls. This would respond to a DIFFERENT fictional service-provider network issue: A staging center reuses one bootstrap credential for hundreds of service-provider routers, making it impossible to revoke a single compromised device without disabling the entire fleet. It does not directly address the current situation: A wholesale provider manages one L3VPN service through separate scripts on five routers and cannot roll back when the third router rejects a policy.

Question 102

Following a supported configuration correction, the original issue was: A wholesale provider manages one L3VPN service through separate scripts on five routers and cannot roll back when the third router rejects a policy. Which observation verifies success?

  1. The dry-run diff lists only the intended PE and interface while the old PE remains unchanged.
  2. Device configuration converges to the revised service intent and repeated reconciliation produces no unexpected changes.
  3. A failure-injection test records a coherent service transaction outcome and restores previously changed routers when supported.
  4. A negative test captures the intended operation failure despite healthy transport and leaves the configuration unchanged.

Explanation

Correct Answer

C:

A failure-injection test records a coherent service transaction outcome and restores previously changed routers when supported. This confirms the approved response: Model the service with a supported Cisco NSO package and transactional orchestration across the participating devices. It is relevant because: NSO can coordinate model-driven multi-device service intent and transaction management beyond independent scripting.

Incorrect Answers

A:

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: Model the service with a supported Cisco NSO package and transactional orchestration across the participating devices.

B:

Device configuration converges to the revised service intent and repeated reconciliation produces no unexpected changes. This would validate 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. The specific correction here is: Model the service with a supported Cisco NSO package and transactional orchestration across the participating devices.

D:

A negative test captures the intended operation failure despite healthy transport and leaves the configuration unchanged. This would validate ANOTHER scenario: A NETCONF RPC returns an `<rpc-error>` element but a script reports success because the SSH TCP session remained connected. The specific correction here is: Model the service with a supported Cisco NSO package and transactional orchestration across the participating devices.

Question 103

At an ISP route assurance team, an engineer examines: A wholesale provider manages one L3VPN service through separate scripts on five routers and cannot roll back when the third router rejects a policy. Which technical principle is most applicable?

  1. Model-driven orchestrators can overwrite out-of-band changes because their service model remains authoritative.
  2. Service orchestration correctness depends on accurate device and service inventory bindings.
  3. HTTP API methods require supported representations, and mismatched media types can block configuration before authorization of the actual change.
  4. NSO can coordinate model-driven multi-device service intent and transaction management beyond independent scripting.

Explanation

Correct Answer

D:

NSO can coordinate model-driven multi-device service intent and transaction management beyond independent scripting. This explains the investigated 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. The approved corrective response is: Model the service with a supported Cisco NSO package and transactional orchestration across the participating devices.

Incorrect Answers

A:

Model-driven orchestrators can overwrite out-of-band changes because their service model remains authoritative. That explains a DIFFERENT 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. The mechanism to prioritize for this question is: NSO can coordinate model-driven multi-device service intent and transaction management beyond independent scripting.

B:

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: NSO can coordinate model-driven multi-device service intent and transaction management beyond independent scripting.

C:

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: NSO can coordinate model-driven multi-device service intent and transaction management beyond independent scripting.

Question 104

For an ISP route assurance team, the change record describes: A wholesale provider manages one L3VPN service through separate scripts on five routers and cannot roll back when the third router rejects a policy. What preventive validation should be standard?

  1. Exercise service transaction rollback and dry-run before production activation.
  2. Monitor configuration drift and restrict manual changes to managed service resources.
  3. Require device-selection signoff and peer review for service model changes.
  4. Contract-test request headers and payload formats against each platform API version.

Explanation

Correct Answer

A:

Exercise service transaction rollback and dry-run before production activation. This helps prevent recurrence of the 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. Acceptance evidence should be: A failure-injection test records a coherent service transaction outcome and restores previously changed routers when supported.

Incorrect Answers

B:

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: Exercise service transaction rollback and dry-run before production activation.

C:

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: Exercise service transaction rollback and dry-run before production activation.

D:

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: Exercise service transaction rollback and dry-run before production activation.

Question 105

For a converged broadband aggregation team, the failure is: 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. Which authorized correction best addresses it?

  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. Migrate supported devices to SNMPv3 with appropriate authentication/privacy and restrict manager addresses.

Explanation

Correct Answer

C:

Include the correct list key in the modeled resource path and validate its encoding. This directly addresses the fictional service-provider network case: 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 technical mechanism is: Keyed YANG list entries require instance identification to address one configuration object. Verify success by: The targeted interface changes while other interfaces remain byte-for-byte unchanged.

Incorrect Answers

A:

Preserve the full module namespace and revision for each data path and parse namespace-qualified fields. This would respond to a DIFFERENT fictional service-provider network issue: 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. It does not directly address the current situation: 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.

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

D:

Migrate supported devices to SNMPv3 with appropriate authentication/privacy and restrict manager addresses. This would respond to a DIFFERENT fictional service-provider network issue: A provider inventories routers using SNMPv2c with an easily guessed community on a shared management segment and exposes interface inventory to unauthorized clients. It does not directly address the current situation: 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.

Question 106

After fixing the following network problem, what should the team verify: 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.

  1. A fixture containing the two modules resolves both leaf values to their correct models without ambiguity.
  2. Counter retrieval succeeds and a controlled mutation remains rejected by schema or datastore rules.
  3. Revoking one test device prevents its reenrollment while unaffected lab routers enroll normally.
  4. The targeted interface changes while other interfaces remain byte-for-byte unchanged.

Explanation

Correct Answer

D:

The targeted interface changes while other interfaces remain byte-for-byte unchanged. This confirms the approved response: Include the correct list key in the modeled resource path and validate its encoding. It is relevant because: Keyed YANG list entries require instance identification to address one configuration object.

Incorrect Answers

A:

A fixture containing the two modules resolves both leaf values to their correct models without ambiguity. This would validate ANOTHER scenario: 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 specific correction here is: Include the correct list key in the modeled resource path and validate its encoding.

B:

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: Include the correct list key in the modeled resource path and validate its encoding.

C:

Revoking one test device prevents its reenrollment while unaffected lab routers enroll normally. This would validate ANOTHER scenario: A staging center reuses one bootstrap credential for hundreds of service-provider routers, making it impossible to revoke a single compromised device without disabling the entire fleet. The specific correction here is: Include the correct list key in the modeled resource path and validate its encoding.

Question 107

A carrier root-cause review considers: 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. What underlying mechanism explains this?

  1. Keyed YANG list entries require instance identification to address one configuration object.
  2. YANG namespaces and revisions give modeled nodes meaning beyond their unqualified display names.
  3. YANG `config false` identifies state data not intended for writable configuration transactions.
  4. TLS authenticates remote endpoint identity using chain and name checks, while mTLS can additionally authenticate the router.

Explanation

Correct Answer

A:

Keyed YANG list entries require instance identification to address one configuration object. This explains the investigated 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. The approved corrective response is: Include the correct list key in the modeled resource path and validate its encoding.

Incorrect Answers

B:

YANG namespaces and revisions give modeled nodes meaning beyond their unqualified display names. That explains a DIFFERENT scenario: 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 mechanism to prioritize for this question is: Keyed YANG list entries require instance identification to address one configuration object.

C:

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: Keyed YANG list entries require instance identification to address one configuration object.

D:

TLS authenticates remote endpoint identity using chain and name checks, while mTLS can additionally authenticate the router. That explains a DIFFERENT 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. The mechanism to prioritize for this question is: Keyed YANG list entries require instance identification to address one configuration object.

Question 108

After addressing: 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. Which recurring service assurance check is most useful?

  1. Inspect writable-state metadata when generating automation forms from YANG models.
  2. Test list-key encoding and cross-interface isolation for every API client.
  3. Pin model versions and retain schema-validation fixtures during integration upgrades.
  4. Test alarm-source reachability and permitted OIDs during management network changes.

Explanation

Correct Answer

B:

Test list-key encoding and cross-interface isolation for every API client. This helps prevent recurrence of the 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. Acceptance evidence should be: The targeted interface changes while other interfaces remain byte-for-byte unchanged.

Incorrect Answers

A:

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: Test list-key encoding and cross-interface isolation for every API client.

C:

Pin model versions and retain schema-validation fixtures during integration upgrades. That is a sensible control for ANOTHER scenario: 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. It is less targeted to this issue than: Test list-key encoding and cross-interface isolation for every API client.

D:

Test alarm-source reachability and permitted OIDs during management network changes. That is a sensible control for ANOTHER scenario: A trap receiver processes authenticationFailure SNMP notifications but drops interfaceDown events because its trap ACL permits only one source subnet. It is less targeted to this issue than: Test list-key encoding and cross-interface isolation for every API client.

Question 109

A provider backbone escalation identifies: An Ansible network playbook uses `hosts: all` and changes every backbone router though the request approved only an isolated PoP. What should the network team implement?

  1. Use a protected shared state backend with locking and a single reviewed apply workflow.
  2. Use an appropriate supported state move or resource refactor after reviewing destructive plan actions.
  3. Read operational state using the supported data retrieval API instead of treating a read-only leaf as writable configuration.
  4. Scope inventory groups and host limits to approved lab or PoP devices before network configuration tasks run.

Explanation

Correct Answer

D:

Scope inventory groups and host limits to approved lab or PoP devices before network configuration tasks run. This directly addresses the fictional service-provider network case: An Ansible network playbook uses `hosts: all` and changes every backbone router though the request approved only an isolated PoP. The technical mechanism is: Ansible host selection controls deployment blast radius independently of the syntax of the configured tasks. Verify success by: Dry-run output lists only the intended routers and unrelated devices show no changes.

Incorrect Answers

A:

Use a protected shared state backend with locking and a single reviewed apply workflow. This would respond to a DIFFERENT fictional service-provider network issue: Two Terraform jobs edit the same service-provider cloud network workspace in parallel, creating conflicting route-table state and duplicate resources. It does not directly address the current situation: An Ansible network playbook uses `hosts: all` and changes every backbone router though the request approved only an isolated PoP.

B:

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: An Ansible network playbook uses `hosts: all` and changes every backbone router though the request approved only an isolated PoP.

C:

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: An Ansible network playbook uses `hosts: all` and changes every backbone router though the request approved only an isolated PoP.

Question 110

A service-provider operations test targets: An Ansible network playbook uses `hosts: all` and changes every backbone router though the request approved only an isolated PoP. Which result is required?

  1. Dry-run output lists only the intended routers and unrelated devices show no changes.
  2. A revised plan preserves the deployed service VM and updates only the intended metadata.
  3. The second apply is blocked or serialized until state reconciliation completes and the final plan matches desired topology.
  4. Counter retrieval succeeds and a controlled mutation remains rejected by schema or datastore rules.

Explanation

Correct Answer

A:

Dry-run output lists only the intended routers and unrelated devices show no changes. This confirms the approved response: Scope inventory groups and host limits to approved lab or PoP devices before network configuration tasks run. It is relevant because: Ansible host selection controls deployment blast radius independently of the syntax of the configured tasks.

Incorrect Answers

B:

A revised plan preserves the deployed service VM and updates only the intended metadata. This would validate ANOTHER 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 specific correction here is: Scope inventory groups and host limits to approved lab or PoP devices before network configuration tasks run.

C:

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

D:

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