McAfee Secure

Cisco 350-501 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 Training 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

    Training Course

    253 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    1160 PDF Pages

    $24.99

Cisco 350-501 Practice Test 61

Question 600

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A service-provider automation client polls CLI text for interface state even though the PE supports structured model-driven configuration APIs. Which continuing control best reduces recurrence of this problem?

  1. Track YANG module versions and API capability discovery for every platform.
  2. Verify flow direction and certificate roles before deploying new telemetry sites.
  3. Test template refresh and exporter reboot behavior before relying on analytics.
  4. Rotate SNMPv3 credentials and audit authorized MIB views.

Explanation

Correct Answer

A:

For this scenario, the observed situation is: A service-provider automation client polls CLI text for interface state even though the PE supports structured model-driven configuration APIs. The most directly supported response is: Select a supported RESTCONF or NETCONF interface with the advertised YANG operational model. Technical basis: Model-driven network APIs encode data according to a schema rather than terminal display formatting. Evidence of success: The client retrieves a structured interface-state object without brittle screen scraping. Ongoing protection: Track YANG module versions and API capability discovery for every platform.

Incorrect Answers

B:

Dial-out and dial-in determine which endpoint originates the telemetry transport session. Maintaining that control would not track the failure described here. The relevant risk is: Model-driven network APIs encode data according to a schema rather than terminal display formatting. Review this instead: Track YANG module versions and API capability discovery for every platform.

C:

IPFIX supports template-defined flow fields whose interpretation can change by exporter. Maintaining that control would not track the failure described here. The relevant risk is: Model-driven network APIs encode data according to a schema rather than terminal display formatting. Review this instead: Track YANG module versions and API capability discovery for every platform.

D:

The alternative guards against: SNMPv3 can provide authentication and privacy protections absent from common community-only SNMPv2c use. The root condition for this case is: Model-driven network APIs encode data according to a schema rather than terminal display formatting. The focused prevention check is: Track YANG module versions and API capability discovery for every platform.

Question 601

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A controller sends NETCONF XML edit-config calls to a device interface that accepts only RESTCONF HTTP methods. What is the best authorized corrective or investigative action for this service-provider network operations situation?

  1. Check assigned privilege and authorization scope for the requested YANG resource rather than changing IP routing.
  2. Keep Terraform state and reviewed configuration aligned with approved provider resources.
  3. Select the transport and encoding contract that the device actually supports.
  4. Construct the documented targeted RESTCONF resource path and appropriate mutation method.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: A controller sends NETCONF XML edit-config calls to a device interface that accepts only RESTCONF HTTP methods. The most directly supported response is: Select the transport and encoding contract that the device actually supports. Technical basis: NETCONF uses RPC over a secure session, while RESTCONF exposes YANG resources through HTTP semantics. Evidence of success: A documented request succeeds through the advertised management protocol and returns a recognized response. Ongoing protection: Include protocol negotiation and negative compatibility tests in SDK integration.

Incorrect Answers

A:

The proposed option addresses this separate mechanism: RESTCONF authorization is distinct from TLS reachability and authentication success. The stated problem instead depends on: NETCONF uses RPC over a secure session, while RESTCONF exposes YANG resources through HTTP semantics. The required response is: Select the transport and encoding contract that the device actually supports.

B:

The proposed option addresses this separate mechanism: Infrastructure-as-code state tracks resources and compares actual configuration to declarative intent. The stated problem instead depends on: NETCONF uses RPC over a secure session, while RESTCONF exposes YANG resources through HTTP semantics. The required response is: Select the transport and encoding contract that the device actually supports.

D:

The option fits a control for: REST resource paths and HTTP methods determine which network datastore element is read or modified. The present failure is caused by a different mechanism: NETCONF uses RPC over a secure session, while RESTCONF exposes YANG resources through HTTP semantics. The targeted implementation is: Select the transport and encoding contract that the device actually supports.

Question 602

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A controller sends NETCONF XML edit-config calls to a device interface that accepts only RESTCONF HTTP methods. Which observable result most directly verifies that this network issue was resolved?

  1. Only the expected device and authorized collector establish the gRPC telemetry session.
  2. The server accepts the supported media type and the intended resource update succeeds.
  3. The rollout proceeds in bounded batches without rate-limit failures or unexpected route outages.
  4. A documented request succeeds through the advertised management protocol and returns a recognized response.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: A controller sends NETCONF XML edit-config calls to a device interface that accepts only RESTCONF HTTP methods. The most directly supported response is: Select the transport and encoding contract that the device actually supports. Technical basis: NETCONF uses RPC over a secure session, while RESTCONF exposes YANG resources through HTTP semantics. Evidence of success: A documented request succeeds through the advertised management protocol and returns a recognized response. Ongoing protection: Include protocol negotiation and negative compatibility tests in SDK integration.

Incorrect Answers

A:

TLS encryption alone does not prove peer identity without certificate validation. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: NETCONF uses RPC over a secure session, while RESTCONF exposes YANG resources through HTTP semantics. A passing check should show: A documented request succeeds through the advertised management protocol and returns a recognized response.

B:

The proposed test would be relevant to: HTTP 415 indicates unsupported representation format, not necessarily a failed credential. The reported problem follows from: NETCONF uses RPC over a secure session, while RESTCONF exposes YANG resources through HTTP semantics. Instead, verify: A documented request succeeds through the advertised management protocol and returns a recognized response.

C:

The proposed test would be relevant to: Automation concurrency must respect management-plane scale and fault domains. The reported problem follows from: NETCONF uses RPC over a secure session, while RESTCONF exposes YANG resources through HTTP semantics. Instead, verify: A documented request succeeds through the advertised management protocol and returns a recognized response.

Question 603

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A controller sends NETCONF XML edit-config calls to a device interface that accepts only RESTCONF HTTP methods. Which underlying network infrastructure principle best explains the situation?

  1. Secure ZTP reduces exposure from unauthenticated initial configuration retrieval.
  2. Remote writes can succeed before a client times out, making unconditional retries unsafe.
  3. TLS encryption alone does not prove peer identity without certificate validation.
  4. NETCONF uses RPC over a secure session, while RESTCONF exposes YANG resources through HTTP semantics.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: A controller sends NETCONF XML edit-config calls to a device interface that accepts only RESTCONF HTTP methods. The most directly supported response is: Select the transport and encoding contract that the device actually supports. Technical basis: NETCONF uses RPC over a secure session, while RESTCONF exposes YANG resources through HTTP semantics. Evidence of success: A documented request succeeds through the advertised management protocol and returns a recognized response. Ongoing protection: Include protocol negotiation and negative compatibility tests in SDK integration.

Incorrect Answers

A:

The option explains a separate issue: Secure ZTP reduces exposure from unauthenticated initial configuration retrieval. The reported condition instead follows from: NETCONF uses RPC over a secure session, while RESTCONF exposes YANG resources through HTTP semantics.

B:

The option explains a separate issue: Remote writes can succeed before a client times out, making unconditional retries unsafe. The reported condition instead follows from: NETCONF uses RPC over a secure session, while RESTCONF exposes YANG resources through HTTP semantics.

C:

The option explains a separate issue: TLS encryption alone does not prove peer identity without certificate validation. The reported condition instead follows from: NETCONF uses RPC over a secure session, while RESTCONF exposes YANG resources through HTTP semantics.

Question 604

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A controller sends NETCONF XML edit-config calls to a device interface that accepts only RESTCONF HTTP methods. Which continuing control best reduces recurrence of this problem?

  1. Review datastore access and module capabilities in management-client design.
  2. Test partial failure paths and commit recovery before launching bulk service changes.
  3. Include protocol negotiation and negative compatibility tests in SDK integration.
  4. Test least-privilege roles with read and write API operations.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: A controller sends NETCONF XML edit-config calls to a device interface that accepts only RESTCONF HTTP methods. The most directly supported response is: Select the transport and encoding contract that the device actually supports. Technical basis: NETCONF uses RPC over a secure session, while RESTCONF exposes YANG resources through HTTP semantics. Evidence of success: A documented request succeeds through the advertised management protocol and returns a recognized response. Ongoing protection: Include protocol negotiation and negative compatibility tests in SDK integration.

Incorrect Answers

A:

The alternative guards against: YANG distinguishes configuration data from operational state through its schema semantics. The root condition for this case is: NETCONF uses RPC over a secure session, while RESTCONF exposes YANG resources through HTTP semantics. The focused prevention check is: Include protocol negotiation and negative compatibility tests in SDK integration.

B:

The alternative guards against: Service orchestration manages cross-device operations with transactional semantics subject to device capabilities. The root condition for this case is: NETCONF uses RPC over a secure session, while RESTCONF exposes YANG resources through HTTP semantics. The focused prevention check is: Include protocol negotiation and negative compatibility tests in SDK integration.

D:

That recurring practice manages a separate exposure: RESTCONF authorization is distinct from TLS reachability and authentication success. The present case instead depends on: NETCONF uses RPC over a secure session, while RESTCONF exposes YANG resources through HTTP semantics. The suitable ongoing safeguard is: Include protocol negotiation and negative compatibility tests in SDK integration.

Question 605

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A telemetry program receives gNMI subscription messages but its parser assumes these are asynchronous REST webhooks. What is the best authorized corrective or investigative action for this service-provider network operations situation?

  1. Model customer service intent in Cisco NSO and map it through supported service packages to device configuration.
  2. Construct the documented targeted RESTCONF resource path and appropriate mutation method.
  3. Keep Terraform state and reviewed configuration aligned with approved provider resources.
  4. Use a compatible gNMI streaming subscription and parse the typed telemetry paths.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: A telemetry program receives gNMI subscription messages but its parser assumes these are asynchronous REST webhooks. The most directly supported response is: Use a compatible gNMI streaming subscription and parse the typed telemetry paths. Technical basis: gNMI telemetry is a structured gRPC-based subscription interaction distinct from generic HTTP webhooks. Evidence of success: The collector receives timestamped updates for the subscribed data paths under a sustained session. Ongoing protection: Check stream reconnection and schema compatibility after device updates.

Incorrect Answers

A:

The option fits a control for: NSO service modeling relates high-level service intent to managed multi-device configuration. The present failure is caused by a different mechanism: gNMI telemetry is a structured gRPC-based subscription interaction distinct from generic HTTP webhooks. The targeted implementation is: Use a compatible gNMI streaming subscription and parse the typed telemetry paths.

B:

The option fits a control for: REST resource paths and HTTP methods determine which network datastore element is read or modified. The present failure is caused by a different mechanism: gNMI telemetry is a structured gRPC-based subscription interaction distinct from generic HTTP webhooks. The targeted implementation is: Use a compatible gNMI streaming subscription and parse the typed telemetry paths.

C:

Infrastructure-as-code state tracks resources and compares actual configuration to declarative intent. That principle governs the alternative intervention. The issue described here is different: gNMI telemetry is a structured gRPC-based subscription interaction distinct from generic HTTP webhooks. The case-matched corrective action is: Use a compatible gNMI streaming subscription and parse the typed telemetry paths.

Question 606

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A telemetry program receives gNMI subscription messages but its parser assumes these are asynchronous REST webhooks. Which observable result most directly verifies that this network issue was resolved?

  1. The second playbook run reports no unintended changes after the first converges.
  2. The collector receives timestamped updates for the subscribed data paths under a sustained session.
  3. A properly authorized role can update the resource while the restricted role remains denied.
  4. The orchestrator traces one service instance to the generated device changes and can evaluate consistency.

Explanation

Correct Answer

B:

For this scenario, the observed situation is: A telemetry program receives gNMI subscription messages but its parser assumes these are asynchronous REST webhooks. The most directly supported response is: Use a compatible gNMI streaming subscription and parse the typed telemetry paths. Technical basis: gNMI telemetry is a structured gRPC-based subscription interaction distinct from generic HTTP webhooks. Evidence of success: The collector receives timestamped updates for the subscribed data paths under a sustained session. Ongoing protection: Check stream reconnection and schema compatibility after device updates.

Incorrect Answers

A:

The proposed test would be relevant to: Infrastructure automation benefits from idempotent desired-state operations rather than blind command repetition. The reported problem follows from: gNMI telemetry is a structured gRPC-based subscription interaction distinct from generic HTTP webhooks. Instead, verify: The collector receives timestamped updates for the subscribed data paths under a sustained session.

C:

That observation tests a different mechanism: RESTCONF authorization is distinct from TLS reachability and authentication success. It cannot establish this case, whose mechanism is: gNMI telemetry is a structured gRPC-based subscription interaction distinct from generic HTTP webhooks. The needed verification is: The collector receives timestamped updates for the subscribed data paths under a sustained session.

D:

That observation tests a different mechanism: NSO service modeling relates high-level service intent to managed multi-device configuration. It cannot establish this case, whose mechanism is: gNMI telemetry is a structured gRPC-based subscription interaction distinct from generic HTTP webhooks. The needed verification is: The collector receives timestamped updates for the subscribed data paths under a sustained session.

Question 607

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A telemetry program receives gNMI subscription messages but its parser assumes these are asynchronous REST webhooks. Which underlying network infrastructure principle best explains the situation?

  1. SNMPv3 USM security depends on authoritative engine identity and synchronization.
  2. YANG type constraints restrict allowable values independently of XML or JSON syntax.
  3. Dial-out and dial-in determine which endpoint originates the telemetry transport session.
  4. gNMI telemetry is a structured gRPC-based subscription interaction distinct from generic HTTP webhooks.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: A telemetry program receives gNMI subscription messages but its parser assumes these are asynchronous REST webhooks. The most directly supported response is: Use a compatible gNMI streaming subscription and parse the typed telemetry paths. Technical basis: gNMI telemetry is a structured gRPC-based subscription interaction distinct from generic HTTP webhooks. Evidence of success: The collector receives timestamped updates for the subscribed data paths under a sustained session. Ongoing protection: Check stream reconnection and schema compatibility after device updates.

Incorrect Answers

A:

The alternative principle describes: SNMPv3 USM security depends on authoritative engine identity and synchronization. In this question, the decisive mechanism is: gNMI telemetry is a structured gRPC-based subscription interaction distinct from generic HTTP webhooks. These are distinct technical causes, even when they share a platform.

B:

The alternative principle describes: YANG type constraints restrict allowable values independently of XML or JSON syntax. In this question, the decisive mechanism is: gNMI telemetry is a structured gRPC-based subscription interaction distinct from generic HTTP webhooks. These are distinct technical causes, even when they share a platform.

C:

The alternative principle describes: Dial-out and dial-in determine which endpoint originates the telemetry transport session. In this question, the decisive mechanism is: gNMI telemetry is a structured gRPC-based subscription interaction distinct from generic HTTP webhooks. These are distinct technical causes, even when they share a platform.

Question 608

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A telemetry program receives gNMI subscription messages but its parser assumes these are asynchronous REST webhooks. Which continuing control best reduces recurrence of this problem?

  1. Rotate bootstrap credentials and audit provisioning logs for every new device.
  2. Check stream reconnection and schema compatibility after device updates.
  3. Record sampling rates and periodically reconcile against interface counters.
  4. Restrict direct changes and review drift alerts with service owners.

Explanation

Correct Answer

B:

For this scenario, the observed situation is: A telemetry program receives gNMI subscription messages but its parser assumes these are asynchronous REST webhooks. The most directly supported response is: Use a compatible gNMI streaming subscription and parse the typed telemetry paths. Technical basis: gNMI telemetry is a structured gRPC-based subscription interaction distinct from generic HTTP webhooks. Evidence of success: The collector receives timestamped updates for the subscribed data paths under a sustained session. Ongoing protection: Check stream reconnection and schema compatibility after device updates.

Incorrect Answers

A:

That recurring practice manages a separate exposure: Secure ZTP reduces exposure from unauthenticated initial configuration retrieval. The present case instead depends on: gNMI telemetry is a structured gRPC-based subscription interaction distinct from generic HTTP webhooks. The suitable ongoing safeguard is: Check stream reconnection and schema compatibility after device updates.

C:

That recurring practice manages a separate exposure: Sampled flow telemetry requires careful scaling and cannot guarantee exact per-packet accounting. The present case instead depends on: gNMI telemetry is a structured gRPC-based subscription interaction distinct from generic HTTP webhooks. The suitable ongoing safeguard is: Check stream reconnection and schema compatibility after device updates.

D:

Orchestration requires an authoritative intent source and detects unmanaged configuration changes. Maintaining that control would not track the failure described here. The relevant risk is: gNMI telemetry is a structured gRPC-based subscription interaction distinct from generic HTTP webhooks. Review this instead: Check stream reconnection and schema compatibility after device updates.

Question 609

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A Python script updates one interface but accidentally builds a URL pointing to the entire router configuration collection. What is the best authorized corrective or investigative action for this service-provider network operations situation?

  1. Constrain provisioning networks and verify trusted bootstrap or certificate-based server identity.
  2. Validate certificate trust and name matching and use mutually authenticated TLS when policy requires it.
  3. Construct the documented targeted RESTCONF resource path and appropriate mutation method.
  4. Select a supported RESTCONF or NETCONF interface with the advertised YANG operational model.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: A Python script updates one interface but accidentally builds a URL pointing to the entire router configuration collection. The most directly supported response is: Construct the documented targeted RESTCONF resource path and appropriate mutation method. Technical basis: REST resource paths and HTTP methods determine which network datastore element is read or modified. Evidence of success: Only the intended interface resource changes and unrelated configuration remains intact. Ongoing protection: Unit-test generated paths and block broad writes without approval.

Incorrect Answers

A:

Initial bootstrap is a trust-establishment step vulnerable to redirection without independent authentication. That principle governs the alternative intervention. The issue described here is different: REST resource paths and HTTP methods determine which network datastore element is read or modified. The case-matched corrective action is: Construct the documented targeted RESTCONF resource path and appropriate mutation method.

B:

TLS encryption alone does not prove peer identity without certificate validation. That principle governs the alternative intervention. The issue described here is different: REST resource paths and HTTP methods determine which network datastore element is read or modified. The case-matched corrective action is: Construct the documented targeted RESTCONF resource path and appropriate mutation method.

D:

The proposed option addresses this separate mechanism: Model-driven network APIs encode data according to a schema rather than terminal display formatting. The stated problem instead depends on: REST resource paths and HTTP methods determine which network datastore element is read or modified. The required response is: Construct the documented targeted RESTCONF resource path and appropriate mutation method.

Question 610

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A Python script updates one interface but accidentally builds a URL pointing to the entire router configuration collection. Which observable result most directly verifies that this network issue was resolved?

  1. A failed multi-device change is recorded consistently and incomplete service intent is not silently accepted.
  2. Only the intended interface resource changes and unrelated configuration remains intact.
  3. The device rejects the untrusted provisioning endpoint and retrieves only approved onboarding instructions.
  4. A fresh plan identifies any manual drift rather than silently treating changed resources as intended.

Explanation

Correct Answer

B:

For this scenario, the observed situation is: A Python script updates one interface but accidentally builds a URL pointing to the entire router configuration collection. The most directly supported response is: Construct the documented targeted RESTCONF resource path and appropriate mutation method. Technical basis: REST resource paths and HTTP methods determine which network datastore element is read or modified. Evidence of success: Only the intended interface resource changes and unrelated configuration remains intact. Ongoing protection: Unit-test generated paths and block broad writes without approval.

Incorrect Answers

A:

That observation tests a different mechanism: Service orchestration manages cross-device operations with transactional semantics subject to device capabilities. It cannot establish this case, whose mechanism is: REST resource paths and HTTP methods determine which network datastore element is read or modified. The needed verification is: Only the intended interface resource changes and unrelated configuration remains intact.

C:

Initial bootstrap is a trust-establishment step vulnerable to redirection without independent authentication. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: REST resource paths and HTTP methods determine which network datastore element is read or modified. A passing check should show: Only the intended interface resource changes and unrelated configuration remains intact.

D:

Infrastructure-as-code state tracks resources and compares actual configuration to declarative intent. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: REST resource paths and HTTP methods determine which network datastore element is read or modified. A passing check should show: Only the intended interface resource changes and unrelated configuration remains intact.