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 13

Question 120

For a wholesale transit provider, the change record describes: A router publishes gNMI dial-out telemetry to a collector whose TLS certificate hostname does not match the configured endpoint and fails the handshake. What preventive validation should be standard?

  1. Include hostname, expiry and certificate chain tests in gNMI collector deployment.
  2. Record firewall direction and streaming mode in each telemetry service definition.
  3. Capacity-test subscription modes against real supported model leaves before large-scale activation.
  4. Require explicit human approval for any plan that destroys active network service components.

Explanation

Correct Answer

A:

Include hostname, expiry and certificate chain tests in gNMI collector deployment. This helps prevent recurrence of the 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. Acceptance evidence should be: A lab connection establishes with expected certificate validation and rejects an endpoint using a mismatched identity.

Incorrect Answers

B:

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: Include hostname, expiry and certificate chain tests in gNMI collector deployment.

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: Include hostname, expiry and certificate chain tests in gNMI collector deployment.

D:

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: Include hostname, expiry and certificate chain tests in gNMI collector deployment.

Question 121

For a multi-region fiber backbone operator, the failure is: A PE exports NetFlow records but a flow collector uses the wrong IPFIX template definition and assigns source ports to destination-address fields. Which authorized correction best addresses it?

  1. Apply documented sampling-rate compensation and report estimation uncertainty for usage analytics.
  2. Synchronize exporter and collector clocks and preserve flow start/end timestamps with correct normalization.
  3. Verify exported IPFIX templates and map the collector's decoded fields to the correct information elements.
  4. Read operational state using the supported data retrieval API instead of treating a read-only leaf as writable configuration.

Explanation

Correct Answer

C:

Verify exported IPFIX templates and map the collector's decoded fields to the correct information elements. This directly addresses the fictional service-provider network case: A PE exports NetFlow records but a flow collector uses the wrong IPFIX template definition and assigns source ports to destination-address fields. The technical mechanism is: IPFIX record interpretation depends on its accompanying template ID and field definitions. Verify success by: A fixture flow maps the known five-tuple and byte count without swapping fields.

Incorrect Answers

A:

Apply documented sampling-rate compensation and report estimation uncertainty for usage analytics. This would respond to a DIFFERENT fictional service-provider network issue: A backbone flow analytics system samples one packet in 100 but its dashboard treats observed packets as complete unsampled volumes. It does not directly address the current situation: A PE exports NetFlow records but a flow collector uses the wrong IPFIX template definition and assigns source ports to destination-address fields.

B:

Synchronize exporter and collector clocks and preserve flow start/end timestamps with correct normalization. This would respond to a DIFFERENT fictional service-provider network issue: A NetFlow collector receives records with event times 15 minutes behind the source because the PE clock is unsynchronized, scrambling incident and capacity correlations. It does not directly address the current situation: A PE exports NetFlow records but a flow collector uses the wrong IPFIX template definition and assigns source ports to destination-address fields.

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 PE exports NetFlow records but a flow collector uses the wrong IPFIX template definition and assigns source ports to destination-address fields.

Question 122

After fixing the following network problem, what should the team verify: A PE exports NetFlow records but a flow collector uses the wrong IPFIX template definition and assigns source ports to destination-address fields.

  1. Test records align with the expected traffic window across multiple provider edges.
  2. A controlled known-rate test produces a volume estimate consistent with the sample configuration rather than one percent of actual traffic.
  3. Dry-run output lists only the intended routers and unrelated devices show no changes.
  4. A fixture flow maps the known five-tuple and byte count without swapping fields.

Explanation

Correct Answer

D:

A fixture flow maps the known five-tuple and byte count without swapping fields. This confirms the approved response: Verify exported IPFIX templates and map the collector's decoded fields to the correct information elements. It is relevant because: IPFIX record interpretation depends on its accompanying template ID and field definitions.

Incorrect Answers

A:

Test records align with the expected traffic window across multiple provider edges. This would validate ANOTHER scenario: A NetFlow collector receives records with event times 15 minutes behind the source because the PE clock is unsynchronized, scrambling incident and capacity correlations. The specific correction here is: Verify exported IPFIX templates and map the collector's decoded fields to the correct information elements.

B:

A controlled known-rate test produces a volume estimate consistent with the sample configuration rather than one percent of actual traffic. This would validate ANOTHER scenario: A backbone flow analytics system samples one packet in 100 but its dashboard treats observed packets as complete unsampled volumes. The specific correction here is: Verify exported IPFIX templates and map the collector's decoded fields to the correct information elements.

C:

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: Verify exported IPFIX templates and map the collector's decoded fields to the correct information elements.

Question 123

A carrier root-cause review considers: A PE exports NetFlow records but a flow collector uses the wrong IPFIX template definition and assigns source ports to destination-address fields. What underlying mechanism explains this?

  1. IPFIX record interpretation depends on its accompanying template ID and field definitions.
  2. Sampled NetFlow/IPFIX requires accounting for sampling to estimate total packet and byte counts.
  3. Flow records are meaningful for correlation only when export and collection time bases are reconciled.
  4. IaC state must be coordinated to prevent concurrent operations from clobbering resource identity and dependencies.

Explanation

Correct Answer

A:

IPFIX record interpretation depends on its accompanying template ID and field definitions. This explains the investigated issue: A PE exports NetFlow records but a flow collector uses the wrong IPFIX template definition and assigns source ports to destination-address fields. The approved corrective response is: Verify exported IPFIX templates and map the collector's decoded fields to the correct information elements.

Incorrect Answers

B:

Sampled NetFlow/IPFIX requires accounting for sampling to estimate total packet and byte counts. That explains a DIFFERENT scenario: A backbone flow analytics system samples one packet in 100 but its dashboard treats observed packets as complete unsampled volumes. The mechanism to prioritize for this question is: IPFIX record interpretation depends on its accompanying template ID and field definitions.

C:

Flow records are meaningful for correlation only when export and collection time bases are reconciled. That explains a DIFFERENT scenario: A NetFlow collector receives records with event times 15 minutes behind the source because the PE clock is unsynchronized, scrambling incident and capacity correlations. The mechanism to prioritize for this question is: IPFIX record interpretation depends on its accompanying template ID and field definitions.

D:

IaC state must be coordinated to prevent concurrent operations from clobbering resource identity and dependencies. That explains a DIFFERENT scenario: Two Terraform jobs edit the same service-provider cloud network workspace in parallel, creating conflicting route-table state and duplicate resources. The mechanism to prioritize for this question is: IPFIX record interpretation depends on its accompanying template ID and field definitions.

Question 124

After addressing: A PE exports NetFlow records but a flow collector uses the wrong IPFIX template definition and assigns source ports to destination-address fields. Which recurring service assurance check is most useful?

  1. Record sampling configuration in every flow export metadata stream.
  2. Run exporter-template compatibility tests whenever platform software changes.
  3. Alert on NTP drift and template timestamp interpretation anomalies.
  4. Require read-before-write or idempotency controls on mutating API workflows.

Explanation

Correct Answer

B:

Run exporter-template compatibility tests whenever platform software changes. This helps prevent recurrence of the issue: A PE exports NetFlow records but a flow collector uses the wrong IPFIX template definition and assigns source ports to destination-address fields. Acceptance evidence should be: A fixture flow maps the known five-tuple and byte count without swapping fields.

Incorrect Answers

A:

Record sampling configuration in every flow export metadata stream. That is a sensible control for ANOTHER scenario: A backbone flow analytics system samples one packet in 100 but its dashboard treats observed packets as complete unsampled volumes. It is less targeted to this issue than: Run exporter-template compatibility tests whenever platform software changes.

C:

Alert on NTP drift and template timestamp interpretation anomalies. That is a sensible control for ANOTHER scenario: A NetFlow collector receives records with event times 15 minutes behind the source because the PE clock is unsynchronized, scrambling incident and capacity correlations. It is less targeted to this issue than: Run exporter-template compatibility tests whenever platform software changes.

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: Run exporter-template compatibility tests whenever platform software changes.

Question 125

A provider backbone escalation identifies: A network controller sends NETCONF `edit-config` to a device but selects the candidate datastore on a platform that advertises running-only support. What should the network team implement?

  1. Parse the NETCONF reply envelope and fail the operation when the RPC reports a relevant error.
  2. Encode the key components per the documented RESTCONF path rules and verify exact target identity before PATCH.
  3. Update the source service instance and template and redeploy through the authorized NSO service workflow.
  4. Inspect NETCONF capabilities and target an actually supported datastore and commit behavior.

Explanation

Correct Answer

D:

Inspect NETCONF capabilities and target an actually supported datastore and commit behavior. This directly addresses the fictional service-provider network case: A network controller sends NETCONF `edit-config` to a device but selects the candidate datastore on a platform that advertises running-only support. The technical mechanism is: NETCONF datastore operations depend on capabilities exchanged in the session hello, not a universal candidate workflow. Verify success by: The intended interface change appears in the supported datastore and the controller reports successful RPC completion.

Incorrect Answers

A:

Parse the NETCONF reply envelope and fail the operation when the RPC reports a relevant error. This would respond to a DIFFERENT fictional service-provider network issue: A NETCONF RPC returns an `<rpc-error>` element but a script reports success because the SSH TCP session remained connected. It does not directly address the current situation: A network controller sends NETCONF `edit-config` to a device but selects the candidate datastore on a platform that advertises running-only support.

B:

Encode the key components per the documented RESTCONF path rules and verify exact target identity before PATCH. This would respond to a DIFFERENT fictional service-provider network issue: A RESTCONF configuration client uses a full URI with a raw slash inside a YANG list key and accidentally addresses a different resource path. It does not directly address the current situation: A network controller sends NETCONF `edit-config` to a device but selects the candidate datastore on a platform that advertises running-only support.

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 network controller sends NETCONF `edit-config` to a device but selects the candidate datastore on a platform that advertises running-only support.

Question 126

A service-provider operations test targets: A network controller sends NETCONF `edit-config` to a device but selects the candidate datastore on a platform that advertises running-only support. Which result is required?

  1. The intended interface change appears in the supported datastore and the controller reports successful RPC completion.
  2. A safe fixture updates the intended keyed service instance and leaves similarly named entries untouched.
  3. A negative test captures the intended operation failure despite healthy transport and leaves the configuration unchanged.
  4. A compatibility test only edits leaves present in each device's advertised schema, with unsupported devices safely excluded.

Explanation

Correct Answer

A:

The intended interface change appears in the supported datastore and the controller reports successful RPC completion. This confirms the approved response: Inspect NETCONF capabilities and target an actually supported datastore and commit behavior. It is relevant because: NETCONF datastore operations depend on capabilities exchanged in the session hello, not a universal candidate workflow.

Incorrect Answers

B:

A safe fixture updates the intended keyed service instance and leaves similarly named entries untouched. This would validate ANOTHER scenario: A RESTCONF configuration client uses a full URI with a raw slash inside a YANG list key and accidentally addresses a different resource path. The specific correction here is: Inspect NETCONF capabilities and target an actually supported datastore and commit behavior.

C:

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: Inspect NETCONF capabilities and target an actually supported datastore and commit behavior.

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: Inspect NETCONF capabilities and target an actually supported datastore and commit behavior.

Question 127

A provider troubleshooting note states: A network controller sends NETCONF `edit-config` to a device but selects the candidate datastore on a platform that advertises running-only support. Which mechanism is central?

  1. Transport session success is not equivalent to NETCONF RPC completion or valid datastore modification.
  2. NETCONF datastore operations depend on capabilities exchanged in the session hello, not a universal candidate workflow.
  3. RESTCONF URLs identify modeled data nodes, and reserved characters in keys may need proper path encoding.
  4. Ansible host selection controls deployment blast radius independently of the syntax of the configured tasks.

Explanation

Correct Answer

B:

NETCONF datastore operations depend on capabilities exchanged in the session hello, not a universal candidate workflow. This explains the investigated issue: A network controller sends NETCONF `edit-config` to a device but selects the candidate datastore on a platform that advertises running-only support. The approved corrective response is: Inspect NETCONF capabilities and target an actually supported datastore and commit behavior.

Incorrect Answers

A:

Transport session success is not equivalent to NETCONF RPC completion or valid datastore modification. That explains a DIFFERENT scenario: A NETCONF RPC returns an `<rpc-error>` element but a script reports success because the SSH TCP session remained connected. The mechanism to prioritize for this question is: NETCONF datastore operations depend on capabilities exchanged in the session hello, not a universal candidate workflow.

C:

RESTCONF URLs identify modeled data nodes, and reserved characters in keys may need proper path encoding. That explains a DIFFERENT scenario: A RESTCONF configuration client uses a full URI with a raw slash inside a YANG list key and accidentally addresses a different resource path. The mechanism to prioritize for this question is: NETCONF datastore operations depend on capabilities exchanged in the session hello, not a universal candidate workflow.

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: NETCONF datastore operations depend on capabilities exchanged in the session hello, not a universal candidate workflow.

Question 128

To prevent recurrence of this provider network issue: A network controller sends NETCONF `edit-config` to a device but selects the candidate datastore on a platform that advertises running-only support. Which control should be retained?

  1. Include special-character and compound-key tests for RESTCONF clients.
  2. Require RPC reply and postchange readback checks for configuration jobs.
  3. Discover NETCONF capabilities at every new device onboarding.
  4. Alert on NTP drift and template timestamp interpretation anomalies.

Explanation

Correct Answer

C:

Discover NETCONF capabilities at every new device onboarding. This helps prevent recurrence of the issue: A network controller sends NETCONF `edit-config` to a device but selects the candidate datastore on a platform that advertises running-only support. Acceptance evidence should be: The intended interface change appears in the supported datastore and the controller reports successful RPC completion.

Incorrect Answers

A:

Include special-character and compound-key tests for RESTCONF clients. That is a sensible control for ANOTHER scenario: A RESTCONF configuration client uses a full URI with a raw slash inside a YANG list key and accidentally addresses a different resource path. It is less targeted to this issue than: Discover NETCONF capabilities at every new device onboarding.

B:

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: Discover NETCONF capabilities at every new device onboarding.

D:

Alert on NTP drift and template timestamp interpretation anomalies. That is a sensible control for ANOTHER scenario: A NetFlow collector receives records with event times 15 minutes behind the source because the PE clock is unsynchronized, scrambling incident and capacity correlations. It is less targeted to this issue than: Discover NETCONF capabilities at every new device onboarding.

Question 129

At a global tier-one IP transit carrier, an engineering review finds: A provider inventories routers using SNMPv2c with an easily guessed community on a shared management segment and exposes interface inventory to unauthorized clients. Which change most directly corrects the service problem?

  1. Migrate supported devices to SNMPv3 with appropriate authentication/privacy and restrict manager addresses.
  2. Verify the device-supported SNMP MIB/OID mapping and appropriate index before collecting the metric.
  3. Align authorized SNMP notification-source addresses and collector access lists with all intended router loopbacks.
  4. Model the service with a supported Cisco NSO package and transactional orchestration across the participating devices.

Explanation

Correct Answer

A:

Migrate supported devices to SNMPv3 with appropriate authentication/privacy and restrict manager addresses. This directly addresses the fictional service-provider network case: A provider inventories routers using SNMPv2c with an easily guessed community on a shared management segment and exposes interface inventory to unauthorized clients. The technical mechanism is: SNMPv2c community strings do not offer the cryptographic protections available in properly configured SNMPv3. Verify success by: An authorized monitoring poll succeeds under protected SNMPv3 while an unauthorized v2c request fails.

Incorrect Answers

B:

Verify the device-supported SNMP MIB/OID mapping and appropriate index before collecting the metric. This would respond to a DIFFERENT fictional service-provider network issue: A monitoring backend discovers no device CPU metric because it queries a nonexistent vendor OID and assumes the router is down. It does not directly address the current situation: A provider inventories routers using SNMPv2c with an easily guessed community on a shared management segment and exposes interface inventory to unauthorized clients.

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 provider inventories routers using SNMPv2c with an easily guessed community on a shared management segment and exposes interface inventory to unauthorized clients.

D:

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 provider inventories routers using SNMPv2c with an easily guessed community on a shared management segment and exposes interface inventory to unauthorized clients.

Question 130

For a global tier-one IP transit carrier, operators addressed: A provider inventories routers using SNMPv2c with an easily guessed community on a shared management segment and exposes interface inventory to unauthorized clients. What is the strongest acceptance evidence?

  1. A controlled interface-down event generates one accepted trap while unapproved senders remain blocked.
  2. An authorized monitoring poll succeeds under protected SNMPv3 while an unauthorized v2c request fails.
  3. An SNMP walk finds the expected instance and polling returns a plausible CPU sample from the correct scope.
  4. The dry-run diff lists only the intended PE and interface while the old PE remains unchanged.

Explanation

Correct Answer

B:

An authorized monitoring poll succeeds under protected SNMPv3 while an unauthorized v2c request fails. This confirms the approved response: Migrate supported devices to SNMPv3 with appropriate authentication/privacy and restrict manager addresses. It is relevant because: SNMPv2c community strings do not offer the cryptographic protections available in properly configured SNMPv3.

Incorrect Answers

A:

A controlled interface-down event generates one accepted trap while unapproved senders remain blocked. This would validate ANOTHER scenario: A trap receiver processes authenticationFailure SNMP notifications but drops interfaceDown events because its trap ACL permits only one source subnet. The specific correction here is: Migrate supported devices to SNMPv3 with appropriate authentication/privacy and restrict manager addresses.

C:

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

D:

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