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 25

Question 240

To prevent recurrence of this provider network issue: A network operator attempts to PATCH a YANG counter marked `config false`, then blames access control when the edit is rejected. Which control should be retained?

  1. Pin model versions and retain schema-validation fixtures during integration upgrades.
  2. Test list-key encoding and cross-interface isolation for every API client.
  3. Inspect writable-state metadata when generating automation forms from YANG models.
  4. Require read-before-write or idempotency controls on mutating API workflows.

Explanation

Correct Answer

C:

Inspect writable-state metadata when generating automation forms from YANG models. This helps prevent recurrence of the issue: A network operator attempts to PATCH a YANG counter marked `config false`, then blames access control when the edit is rejected. Acceptance evidence should be: Counter retrieval succeeds and a controlled mutation remains rejected by schema or datastore rules.

Incorrect Answers

A:

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: Inspect writable-state metadata when generating automation forms from YANG models.

B:

Test list-key encoding and cross-interface isolation for every API client. That is a sensible control for 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. It is less targeted to this issue than: Inspect writable-state metadata when generating automation forms from YANG models.

D:

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: Inspect writable-state metadata when generating automation forms from YANG models.

Question 241

At a global tier-one IP transit carrier, an engineering review finds: Two Terraform jobs edit the same service-provider cloud network workspace in parallel, creating conflicting route-table state and duplicate resources. Which change most directly corrects the service problem?

  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. Scope inventory groups and host limits to approved lab or PoP devices before network configuration tasks run.
  4. Install a correctly named trusted collector certificate and verify mutual TLS identities where required.

Explanation

Correct Answer

A:

Use a protected shared state backend with locking and a single reviewed apply workflow. This directly addresses the fictional service-provider network case: Two Terraform jobs edit the same service-provider cloud network workspace in parallel, creating conflicting route-table state and duplicate resources. The technical mechanism is: IaC state must be coordinated to prevent concurrent operations from clobbering resource identity and dependencies. Verify success by: The second apply is blocked or serialized until state reconciliation completes and the final plan matches desired topology.

Incorrect Answers

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: Two Terraform jobs edit the same service-provider cloud network workspace in parallel, creating conflicting route-table state and duplicate resources.

C:

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: Two Terraform jobs edit the same service-provider cloud network workspace in parallel, creating conflicting route-table state and duplicate resources.

D:

Install a correctly named trusted collector certificate and verify mutual TLS identities where required. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: Two Terraform jobs edit the same service-provider cloud network workspace in parallel, creating conflicting route-table state and duplicate resources.

Question 242

For a global tier-one IP transit carrier, operators addressed: Two Terraform jobs edit the same service-provider cloud network workspace in parallel, creating conflicting route-table state and duplicate resources. What is the strongest acceptance evidence?

  1. Dry-run output lists only the intended routers and unrelated devices show no changes.
  2. The second apply is blocked or serialized until state reconciliation completes and the final plan matches desired topology.
  3. A revised plan preserves the deployed service VM and updates only the intended metadata.
  4. A fixture containing the two modules resolves both leaf values to their correct models without ambiguity.

Explanation

Correct Answer

B:

The second apply is blocked or serialized until state reconciliation completes and the final plan matches desired topology. This confirms the approved response: Use a protected shared state backend with locking and a single reviewed apply workflow. It is relevant because: IaC state must be coordinated to prevent concurrent operations from clobbering resource identity and dependencies.

Incorrect Answers

A:

Dry-run output lists only the intended routers and unrelated devices show no changes. This would validate ANOTHER scenario: An Ansible network playbook uses `hosts: all` and changes every backbone router though the request approved only an isolated PoP. The specific correction here is: Use a protected shared state backend with locking and a single reviewed apply workflow.

C:

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: Use a protected shared state backend with locking and a single reviewed apply workflow.

D:

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: Use a protected shared state backend with locking and a single reviewed apply workflow.

Question 243

Which network protocol or forwarding behavior explains the following issue: Two Terraform jobs edit the same service-provider cloud network workspace in parallel, creating conflicting route-table state and duplicate resources.

  1. Infrastructure as code maps declarations to state addresses, and renaming an address can look like delete-and-recreate.
  2. Ansible host selection controls deployment blast radius independently of the syntax of the configured tasks.
  3. IaC state must be coordinated to prevent concurrent operations from clobbering resource identity and dependencies.
  4. HTTP API methods require supported representations, and mismatched media types can block configuration before authorization of the actual change.

Explanation

Correct Answer

C:

IaC state must be coordinated to prevent concurrent operations from clobbering resource identity and dependencies. This explains the investigated issue: Two Terraform jobs edit the same service-provider cloud network workspace in parallel, creating conflicting route-table state and duplicate resources. The approved corrective response is: Use a protected shared state backend with locking and a single reviewed apply workflow.

Incorrect Answers

A:

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: IaC state must be coordinated to prevent concurrent operations from clobbering resource identity and dependencies.

B:

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: IaC state must be coordinated to prevent concurrent operations from clobbering resource identity and dependencies.

D:

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: IaC state must be coordinated to prevent concurrent operations from clobbering resource identity and dependencies.

Question 244

A core network change board wants to avoid: Two Terraform jobs edit the same service-provider cloud network workspace in parallel, creating conflicting route-table state and duplicate resources. Which ongoing safeguard fits best?

  1. Gate production Ansible runs on reviewed inventory and diff previews.
  2. Require explicit human approval for any plan that destroys active network service components.
  3. Capacity-test subscription modes against real supported model leaves before large-scale activation.
  4. Audit state locking, encryption and access controls on every workspace.

Explanation

Correct Answer

D:

Audit state locking, encryption and access controls on every workspace. This helps prevent recurrence of the issue: Two Terraform jobs edit the same service-provider cloud network workspace in parallel, creating conflicting route-table state and duplicate resources. Acceptance evidence should be: The second apply is blocked or serialized until state reconciliation completes and the final plan matches desired topology.

Incorrect Answers

A:

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: Audit state locking, encryption and access controls on every workspace.

B:

Require explicit human approval for any plan that destroys active network service components. That is a sensible control for 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. It is less targeted to this issue than: Audit state locking, encryption and access controls on every workspace.

C:

Capacity-test subscription modes against real supported model leaves before large-scale activation. That is a sensible control for ANOTHER scenario: A provider subscribes to a gNMI counter in SAMPLE mode but expects only updates when the value changes, saturating the collector with unnecessary periodic messages. It is less targeted to this issue than: Audit state locking, encryption and access controls on every workspace.

Question 245

A carrier service activation check discovers: A ZTP controller provisions a router using an expired certificate chain and the operations team disables validation globally to make the download succeed. Which action best restores the intended behavior?

  1. Implement secure ZTP with authenticated bootstrapping, image trust and the provider's approved certificate or signed configuration controls.
  2. Renew and install the correct trust chain and verify system time before repeating secure enrollment.
  3. Issue scoped device-specific bootstrap credentials or authenticated identities with lifecycle and revocation controls.
  4. Use the documented idempotent update operation or reconcile existing state before retrying a non-idempotent creation.

Explanation

Correct Answer

B:

Renew and install the correct trust chain and verify system time before repeating secure enrollment. This directly addresses the fictional service-provider network case: A ZTP controller provisions a router using an expired certificate chain and the operations team disables validation globally to make the download succeed. The technical mechanism is: Certificate validity and time synchronization are foundational to secure zero-touch device enrollment. Verify success by: Validly signed bootstrap content loads while expired or untrusted material fails with an explicit recorded error.

Incorrect Answers

A:

Implement secure ZTP with authenticated bootstrapping, image trust and the provider's approved certificate or signed configuration controls. This would respond to a DIFFERENT fictional service-provider network issue: A new PE uses zero-touch provisioning over an untrusted access network but downloads a bootstrap configuration from an unsigned public HTTP server. It does not directly address the current situation: A ZTP controller provisions a router using an expired certificate chain and the operations team disables validation globally to make the download succeed.

C:

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 ZTP controller provisions a router using an expired certificate chain and the operations team disables validation globally to make the download succeed.

D:

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 ZTP controller provisions a router using an expired certificate chain and the operations team disables validation globally to make the download succeed.

Question 246

Following a supported configuration correction, the original issue was: A ZTP controller provisions a router using an expired certificate chain and the operations team disables validation globally to make the download succeed. Which observation verifies success?

  1. A disposable router accepts the authorized bootstrap and rejects a tampered or unsigned configuration.
  2. Revoking one test device prevents its reenrollment while unaffected lab routers enroll normally.
  3. Validly signed bootstrap content loads while expired or untrusted material fails with an explicit recorded error.
  4. A lab connection establishes with expected certificate validation and rejects an endpoint using a mismatched identity.

Explanation

Correct Answer

C:

Validly signed bootstrap content loads while expired or untrusted material fails with an explicit recorded error. This confirms the approved response: Renew and install the correct trust chain and verify system time before repeating secure enrollment. It is relevant because: Certificate validity and time synchronization are foundational to secure zero-touch device enrollment.

Incorrect Answers

A:

A disposable router accepts the authorized bootstrap and rejects a tampered or unsigned configuration. This would validate ANOTHER 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 specific correction here is: Renew and install the correct trust chain and verify system time before repeating secure enrollment.

B:

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: Renew and install the correct trust chain and verify system time before repeating secure enrollment.

D:

A lab connection establishes with expected certificate validation and rejects an endpoint using a mismatched identity. This would validate 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. The specific correction here is: Renew and install the correct trust chain and verify system time before repeating secure enrollment.

Question 247

At a mobile packet-core transport operator, an engineer examines: A ZTP controller provisions a router using an expired certificate chain and the operations team disables validation globally to make the download succeed. Which technical principle is most applicable?

  1. Shared initial-enrollment secrets amplify the impact of a single compromise and undermine device accountability.
  2. ZTP automates initial enrollment and therefore needs strong device and bootstrap-source authenticity to avoid fleet-wide compromise.
  3. IPFIX record interpretation depends on its accompanying template ID and field definitions.
  4. Certificate validity and time synchronization are foundational to secure zero-touch device enrollment.

Explanation

Correct Answer

D:

Certificate validity and time synchronization are foundational to secure zero-touch device enrollment. This explains the investigated issue: A ZTP controller provisions a router using an expired certificate chain and the operations team disables validation globally to make the download succeed. The approved corrective response is: Renew and install the correct trust chain and verify system time before repeating secure enrollment.

Incorrect Answers

A:

Shared initial-enrollment secrets amplify the impact of a single compromise and undermine device accountability. That explains a DIFFERENT 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 mechanism to prioritize for this question is: Certificate validity and time synchronization are foundational to secure zero-touch device enrollment.

B:

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: Certificate validity and time synchronization are foundational to secure zero-touch device enrollment.

C:

IPFIX record interpretation depends on its accompanying template ID and field definitions. That explains a DIFFERENT scenario: A PE exports NetFlow records but a flow collector uses the wrong IPFIX template definition and assigns source ports to destination-address fields. The mechanism to prioritize for this question is: Certificate validity and time synchronization are foundational to secure zero-touch device enrollment.

Question 248

For a mobile packet-core transport operator, the change record describes: A ZTP controller provisions a router using an expired certificate chain and the operations team disables validation globally to make the download succeed. What preventive validation should be standard?

  1. Monitor bootstrap certificate expiry and NTP readiness during staging.
  2. Audit bootstrap credential issuance and retirement per asset.
  3. Test bootstrap signature and certificate failure modes before rolling out a new router model.
  4. Discover supported API transports and model revisions during device enrollment.

Explanation

Correct Answer

A:

Monitor bootstrap certificate expiry and NTP readiness during staging. This helps prevent recurrence of the issue: A ZTP controller provisions a router using an expired certificate chain and the operations team disables validation globally to make the download succeed. Acceptance evidence should be: Validly signed bootstrap content loads while expired or untrusted material fails with an explicit recorded error.

Incorrect Answers

B:

Audit bootstrap credential issuance and retirement per asset. That is a sensible control for 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. It is less targeted to this issue than: Monitor bootstrap certificate expiry and NTP readiness during staging.

C:

Test bootstrap signature and certificate failure modes before rolling out a new router model. That is a sensible control for ANOTHER scenario: A new PE uses zero-touch provisioning over an untrusted access network but downloads a bootstrap configuration from an unsigned public HTTP server. It is less targeted to this issue than: Monitor bootstrap certificate expiry and NTP readiness during staging.

D:

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: Monitor bootstrap certificate expiry and NTP readiness during staging.

Question 249

For a managed VPN service carrier, the failure is: 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. Which authorized correction best addresses it?

  1. Select the appropriate supported ON_CHANGE subscription for eligible leaves or adjust SAMPLE cadence for counters that need periodic sampling.
  2. Install a correctly named trusted collector certificate and verify mutual TLS identities where required.
  3. Configure supported device-initiated gNMI dial-out streaming to an approved collector reachable from the device.
  4. Read operational state using the supported data retrieval API instead of treating a read-only leaf as writable configuration.

Explanation

Correct Answer

C:

Configure supported device-initiated gNMI dial-out streaming to an approved collector reachable from the device. This directly addresses the fictional service-provider network case: 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. The technical mechanism is: Dial-out telemetry originates at the device, whereas dial-in requires the collector to connect to the device endpoint. Verify success by: The router establishes an outbound stream and periodic counter updates arrive without new inbound management openings.

Incorrect Answers

A:

Select the appropriate supported ON_CHANGE subscription for eligible leaves or adjust SAMPLE cadence for counters that need periodic sampling. This would respond to a DIFFERENT fictional service-provider network issue: A provider subscribes to a gNMI counter in SAMPLE mode but expects only updates when the value changes, saturating the collector with unnecessary periodic messages. It does not directly address the current situation: 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.

B:

Install a correctly named trusted collector certificate and verify mutual TLS identities where required. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: 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.

D:

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

Question 250

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

  1. A lab connection establishes with expected certificate validation and rejects an endpoint using a mismatched identity.
  2. A controlled counter sequence generates telemetry at the intended cadence and collector load meets capacity targets.
  3. A fixture flow maps the known five-tuple and byte count without swapping fields.
  4. The router establishes an outbound stream and periodic counter updates arrive without new inbound management openings.

Explanation

Correct Answer

D:

The router establishes an outbound stream and periodic counter updates arrive without new inbound management openings. This confirms the approved response: Configure supported device-initiated gNMI dial-out streaming to an approved collector reachable from the device. It is relevant because: Dial-out telemetry originates at the device, whereas dial-in requires the collector to connect to the device endpoint.

Incorrect Answers

A:

A lab connection establishes with expected certificate validation and rejects an endpoint using a mismatched identity. This would validate 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. The specific correction here is: Configure supported device-initiated gNMI dial-out streaming to an approved collector reachable from the device.

B:

A controlled counter sequence generates telemetry at the intended cadence and collector load meets capacity targets. This would validate ANOTHER scenario: A provider subscribes to a gNMI counter in SAMPLE mode but expects only updates when the value changes, saturating the collector with unnecessary periodic messages. The specific correction here is: Configure supported device-initiated gNMI dial-out streaming to an approved collector reachable from the device.

C:

A fixture flow maps the known five-tuple and byte count without swapping fields. This would validate ANOTHER scenario: A PE exports NetFlow records but a flow collector uses the wrong IPFIX template definition and assigns source ports to destination-address fields. The specific correction here is: Configure supported device-initiated gNMI dial-out streaming to an approved collector reachable from the device.