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 26

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.

Question 251

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

  1. Dial-out telemetry originates at the device, whereas dial-in requires the collector to connect to the device endpoint.
  2. TLS authenticates remote endpoint identity using chain and name checks, while mTLS can additionally authenticate the router.
  3. gNMI subscription modes determine whether updates are sampled periodically or emitted on supported state changes.
  4. ZTP automates initial enrollment and therefore needs strong device and bootstrap-source authenticity to avoid fleet-wide compromise.

Explanation

Correct Answer

A:

Dial-out telemetry originates at the device, whereas dial-in requires the collector to connect to the device endpoint. This explains the investigated issue: 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 approved corrective response is: Configure supported device-initiated gNMI dial-out streaming to an approved collector reachable from the device.

Incorrect Answers

B:

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: Dial-out telemetry originates at the device, whereas dial-in requires the collector to connect to the device endpoint.

C:

gNMI subscription modes determine whether updates are sampled periodically or emitted on supported state changes. That explains a DIFFERENT 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 mechanism to prioritize for this question is: Dial-out telemetry originates at the device, whereas dial-in requires the collector to connect to the device endpoint.

D:

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: Dial-out telemetry originates at the device, whereas dial-in requires the collector to connect to the device endpoint.

Question 252

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

  1. Capacity-test subscription modes against real supported model leaves before large-scale activation.
  2. Record firewall direction and streaming mode in each telemetry service definition.
  3. Include hostname, expiry and certificate chain tests in gNMI collector deployment.
  4. Inspect writable-state metadata when generating automation forms from YANG models.

Explanation

Correct Answer

B:

Record firewall direction and streaming mode in each telemetry service definition. This helps prevent recurrence of the issue: 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. Acceptance evidence should be: The router establishes an outbound stream and periodic counter updates arrive without new inbound management openings.

Incorrect Answers

A:

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: Record firewall direction and streaming mode in each telemetry service definition.

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: Record firewall direction and streaming mode in each telemetry service definition.

D:

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: Record firewall direction and streaming mode in each telemetry service definition.

Question 253

A provider backbone escalation identifies: A backbone flow analytics system samples one packet in 100 but its dashboard treats observed packets as complete unsampled volumes. What should the network team implement?

  1. Synchronize exporter and collector clocks and preserve flow start/end timestamps with correct normalization.
  2. Verify exported IPFIX templates and map the collector's decoded fields to the correct information elements.
  3. Poll the documented task status and verify actual configured state before closing the change.
  4. Apply documented sampling-rate compensation and report estimation uncertainty for usage analytics.

Explanation

Correct Answer

D:

Apply documented sampling-rate compensation and report estimation uncertainty for usage analytics. This directly addresses the fictional service-provider network case: A backbone flow analytics system samples one packet in 100 but its dashboard treats observed packets as complete unsampled volumes. The technical mechanism is: Sampled NetFlow/IPFIX requires accounting for sampling to estimate total packet and byte counts. Verify success by: A controlled known-rate test produces a volume estimate consistent with the sample configuration rather than one percent of actual traffic.

Incorrect Answers

A:

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 backbone flow analytics system samples one packet in 100 but its dashboard treats observed packets as complete unsampled volumes.

B:

Verify exported IPFIX templates and map the collector's decoded fields to the correct information elements. This would respond to a DIFFERENT fictional service-provider network issue: A PE exports NetFlow records but a flow collector uses the wrong IPFIX template definition and assigns source ports to destination-address fields. It does not directly address the current situation: A backbone flow analytics system samples one packet in 100 but its dashboard treats observed packets as complete unsampled volumes.

C:

Poll the documented task status and verify actual configured state before closing the change. This would respond to a DIFFERENT fictional service-provider network issue: A controller automation receives HTTP 202 from an IOS XR change job and records completion even though the backend still reports pending work. It does not directly address the current situation: A backbone flow analytics system samples one packet in 100 but its dashboard treats observed packets as complete unsampled volumes.

Question 254

A service-provider operations test targets: A backbone flow analytics system samples one packet in 100 but its dashboard treats observed packets as complete unsampled volumes. Which result is required?

  1. A controlled known-rate test produces a volume estimate consistent with the sample configuration rather than one percent of actual traffic.
  2. Test records align with the expected traffic window across multiple provider edges.
  3. A fixture flow maps the known five-tuple and byte count without swapping fields.
  4. Revoking one test device prevents its reenrollment while unaffected lab routers enroll normally.

Explanation

Correct Answer

A:

A controlled known-rate test produces a volume estimate consistent with the sample configuration rather than one percent of actual traffic. This confirms the approved response: Apply documented sampling-rate compensation and report estimation uncertainty for usage analytics. It is relevant because: Sampled NetFlow/IPFIX requires accounting for sampling to estimate total packet and byte counts.

Incorrect Answers

B:

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: Apply documented sampling-rate compensation and report estimation uncertainty for usage analytics.

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: Apply documented sampling-rate compensation and report estimation uncertainty for usage analytics.

D:

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: Apply documented sampling-rate compensation and report estimation uncertainty for usage analytics.

Question 255

A provider troubleshooting note states: A backbone flow analytics system samples one packet in 100 but its dashboard treats observed packets as complete unsampled volumes. Which mechanism is central?

  1. Flow records are meaningful for correlation only when export and collection time bases are reconciled.
  2. Sampled NetFlow/IPFIX requires accounting for sampling to estimate total packet and byte counts.
  3. IPFIX record interpretation depends on its accompanying template ID and field definitions.
  4. RESTCONF URLs identify modeled data nodes, and reserved characters in keys may need proper path encoding.

Explanation

Correct Answer

B:

Sampled NetFlow/IPFIX requires accounting for sampling to estimate total packet and byte counts. This explains the investigated issue: A backbone flow analytics system samples one packet in 100 but its dashboard treats observed packets as complete unsampled volumes. The approved corrective response is: Apply documented sampling-rate compensation and report estimation uncertainty for usage analytics.

Incorrect Answers

A:

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: Sampled NetFlow/IPFIX requires accounting for sampling to estimate total packet and byte counts.

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: Sampled NetFlow/IPFIX requires accounting for sampling to estimate total packet and byte counts.

D:

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: Sampled NetFlow/IPFIX requires accounting for sampling to estimate total packet and byte counts.

Question 256

To prevent recurrence of this provider network issue: A backbone flow analytics system samples one packet in 100 but its dashboard treats observed packets as complete unsampled volumes. Which control should be retained?

  1. Run exporter-template compatibility tests whenever platform software changes.
  2. Alert on NTP drift and template timestamp interpretation anomalies.
  3. Record sampling configuration in every flow export metadata stream.
  4. Retire insecure communities and scan management access policy regularly.

Explanation

Correct Answer

C:

Record sampling configuration in every flow export metadata stream. This helps prevent recurrence of the issue: A backbone flow analytics system samples one packet in 100 but its dashboard treats observed packets as complete unsampled volumes. Acceptance evidence should be: A controlled known-rate test produces a volume estimate consistent with the sample configuration rather than one percent of actual traffic.

Incorrect Answers

A:

Run exporter-template compatibility tests whenever platform software changes. That is a sensible control for 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. It is less targeted to this issue than: Record sampling configuration in every flow export metadata stream.

B:

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: Record sampling configuration in every flow export metadata stream.

D:

Retire insecure communities and scan management access policy regularly. That is a sensible control for ANOTHER scenario: A provider inventories routers using SNMPv2c with an easily guessed community on a shared management segment and exposes interface inventory to unauthorized clients. It is less targeted to this issue than: Record sampling configuration in every flow export metadata stream.

Question 257

At an optical transport engineering team, an engineering review finds: A RESTCONF configuration client uses a full URI with a raw slash inside a YANG list key and accidentally addresses a different resource path. Which change most directly corrects the service problem?

  1. Encode the key components per the documented RESTCONF path rules and verify exact target identity before PATCH.
  2. Inspect NETCONF capabilities and target an actually supported datastore and commit behavior.
  3. Parse the NETCONF reply envelope and fail the operation when the RPC reports a relevant error.
  4. Include the correct list key in the modeled resource path and validate its encoding.

Explanation

Correct Answer

A:

Encode the key components per the documented RESTCONF path rules and verify exact target identity before PATCH. This directly addresses the fictional service-provider network case: 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 technical mechanism is: RESTCONF URLs identify modeled data nodes, and reserved characters in keys may need proper path encoding. Verify success by: A safe fixture updates the intended keyed service instance and leaves similarly named entries untouched.

Incorrect Answers

B:

Inspect NETCONF capabilities and target an actually supported datastore and commit behavior. This would respond to a DIFFERENT fictional service-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. It does not directly address the current situation: A RESTCONF configuration client uses a full URI with a raw slash inside a YANG list key and accidentally addresses a different resource path.

C:

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 RESTCONF configuration client uses a full URI with a raw slash inside a YANG list key and accidentally addresses a different resource path.

D:

Include the correct list key in the modeled resource path and validate its encoding. This would respond to a DIFFERENT fictional service-provider network issue: A YANG list declares an interface name as its key but a RESTCONF update sends a request to the list root without an instance identifier, modifying the wrong scope. It does not directly address the current situation: A RESTCONF configuration client uses a full URI with a raw slash inside a YANG list key and accidentally addresses a different resource path.

Question 258

For an optical transport engineering team, operators addressed: A RESTCONF configuration client uses a full URI with a raw slash inside a YANG list key and accidentally addresses a different resource path. What is the strongest acceptance evidence?

  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 disposable router accepts the authorized bootstrap and rejects a tampered or unsigned configuration.

Explanation

Correct Answer

B:

A safe fixture updates the intended keyed service instance and leaves similarly named entries untouched. This confirms the approved response: Encode the key components per the documented RESTCONF path rules and verify exact target identity before PATCH. It is relevant because: RESTCONF URLs identify modeled data nodes, and reserved characters in keys may need proper path encoding.

Incorrect Answers

A:

The intended interface change appears in the supported datastore and the controller reports successful RPC completion. This would validate ANOTHER scenario: A network controller sends NETCONF `edit-config` to a device but selects the candidate datastore on a platform that advertises running-only support. The specific correction here is: Encode the key components per the documented RESTCONF path rules and verify exact target identity before PATCH.

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: Encode the key components per the documented RESTCONF path rules and verify exact target identity before PATCH.

D:

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: Encode the key components per the documented RESTCONF path rules and verify exact target identity before PATCH.

Question 259

Which network protocol or forwarding behavior explains the following 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.

  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. IPFIX record interpretation depends on its accompanying template ID and field definitions.

Explanation

Correct Answer

C:

RESTCONF URLs identify modeled data nodes, and reserved characters in keys may need proper path encoding. This explains the investigated 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. The approved corrective response is: Encode the key components per the documented RESTCONF path rules and verify exact target identity before PATCH.

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: RESTCONF URLs identify modeled data nodes, and reserved characters in keys may need proper path encoding.

B:

NETCONF datastore operations depend on capabilities exchanged in the session hello, not a universal candidate workflow. That explains a DIFFERENT scenario: A network controller sends NETCONF `edit-config` to a device but selects the candidate datastore on a platform that advertises running-only support. The mechanism to prioritize for this question is: RESTCONF URLs identify modeled data nodes, and reserved characters in keys may need proper path encoding.

D:

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: RESTCONF URLs identify modeled data nodes, and reserved characters in keys may need proper path encoding.

Question 260

A core network change board wants to avoid: A RESTCONF configuration client uses a full URI with a raw slash inside a YANG list key and accidentally addresses a different resource path. Which ongoing safeguard fits best?

  1. Require RPC reply and postchange readback checks for configuration jobs.
  2. Discover NETCONF capabilities at every new device onboarding.
  3. Capacity-test subscription modes against real supported model leaves before large-scale activation.
  4. Include special-character and compound-key tests for RESTCONF clients.

Explanation

Correct Answer

D:

Include special-character and compound-key tests for RESTCONF clients. This helps prevent recurrence of the 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. Acceptance evidence should be: A safe fixture updates the intended keyed service instance and leaves similarly named entries untouched.

Incorrect Answers

A:

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: Include special-character and compound-key tests for RESTCONF clients.

B:

Discover NETCONF capabilities at every new device onboarding. That is a sensible control for ANOTHER scenario: A network controller sends NETCONF `edit-config` to a device but selects the candidate datastore on a platform that advertises running-only support. It is less targeted to this issue than: Include special-character and compound-key tests for RESTCONF clients.

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 special-character and compound-key tests for RESTCONF clients.