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 39

Question 380

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

  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. Validate endpoint scheme, port and trust chain before each API integration rollout.

Explanation

Correct Answer

B:

Audit bootstrap credential issuance and retirement per asset. This helps prevent recurrence of the 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. Acceptance evidence should be: Revoking one test device prevents its reenrollment while unaffected lab routers enroll normally.

Incorrect Answers

A:

Monitor bootstrap certificate expiry and NTP readiness during staging. That is a sensible control for ANOTHER scenario: A ZTP controller provisions a router using an expired certificate chain and the operations team disables validation globally to make the download succeed. It is less targeted to this issue than: Audit bootstrap credential issuance and retirement per asset.

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: Audit bootstrap credential issuance and retirement per asset.

D:

Validate endpoint scheme, port and trust chain before each API integration rollout. That is a sensible control for ANOTHER scenario: An operations client sends an unencrypted HTTP call to a management endpoint that requires TLS and reports a protocol failure as an unreachable routing prefix. It is less targeted to this issue than: Audit bootstrap credential issuance and retirement per asset.

Question 381

A provider backbone escalation identifies: 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. What should the network team implement?

  1. Install a correctly named trusted collector certificate and verify mutual TLS identities where required.
  2. Configure supported device-initiated gNMI dial-out streaming to an approved collector reachable from the device.
  3. Renew and install the correct trust chain and verify system time before repeating secure enrollment.
  4. Select the appropriate supported ON_CHANGE subscription for eligible leaves or adjust SAMPLE cadence for counters that need periodic sampling.

Explanation

Correct Answer

D:

Select the appropriate supported ON_CHANGE subscription for eligible leaves or adjust SAMPLE cadence for counters that need periodic sampling. This directly addresses the fictional service-provider network case: 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 technical mechanism is: gNMI subscription modes determine whether updates are sampled periodically or emitted on supported state changes. Verify success by: A controlled counter sequence generates telemetry at the intended cadence and collector load meets capacity targets.

Incorrect Answers

A:

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 provider subscribes to a gNMI counter in SAMPLE mode but expects only updates when the value changes, saturating the collector with unnecessary periodic messages.

B:

Configure supported device-initiated gNMI dial-out streaming to an approved collector reachable from the device. This would respond to a DIFFERENT fictional service-provider network 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. It does not directly address the current situation: 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.

C:

Renew and install the correct trust chain and verify system time before repeating secure enrollment. This would respond to a DIFFERENT fictional service-provider network issue: A ZTP controller provisions a router using an expired certificate chain and the operations team disables validation globally to make the download succeed. It does not directly address the current situation: 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.

Question 382

A service-provider operations test targets: 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. Which result is required?

  1. A controlled counter sequence generates telemetry at the intended cadence and collector load meets capacity targets.
  2. The router establishes an outbound stream and periodic counter updates arrive without new inbound management openings.
  3. A lab connection establishes with expected certificate validation and rejects an endpoint using a mismatched identity.
  4. Test records align with the expected traffic window across multiple provider edges.

Explanation

Correct Answer

A:

A controlled counter sequence generates telemetry at the intended cadence and collector load meets capacity targets. This confirms the approved response: Select the appropriate supported ON_CHANGE subscription for eligible leaves or adjust SAMPLE cadence for counters that need periodic sampling. It is relevant because: gNMI subscription modes determine whether updates are sampled periodically or emitted on supported state changes.

Incorrect Answers

B:

The router establishes an outbound stream and periodic counter updates arrive without new inbound management openings. This would validate 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. The specific correction here is: Select the appropriate supported ON_CHANGE subscription for eligible leaves or adjust SAMPLE cadence for counters that need periodic sampling.

C:

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: Select the appropriate supported ON_CHANGE subscription for eligible leaves or adjust SAMPLE cadence for counters that need periodic sampling.

D:

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: Select the appropriate supported ON_CHANGE subscription for eligible leaves or adjust SAMPLE cadence for counters that need periodic sampling.

Question 383

A provider troubleshooting note states: 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. Which mechanism is central?

  1. Dial-out telemetry originates at the device, whereas dial-in requires the collector to connect to the device endpoint.
  2. gNMI subscription modes determine whether updates are sampled periodically or emitted on supported state changes.
  3. TLS authenticates remote endpoint identity using chain and name checks, while mTLS can additionally authenticate the router.
  4. Network automation retries can create duplicate side effects unless operation identity and idempotency are managed.

Explanation

Correct Answer

B:

gNMI subscription modes determine whether updates are sampled periodically or emitted on supported state changes. This explains the investigated 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. The approved corrective response is: Select the appropriate supported ON_CHANGE subscription for eligible leaves or adjust SAMPLE cadence for counters that need periodic sampling.

Incorrect Answers

A:

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

C:

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: gNMI subscription modes determine whether updates are sampled periodically or emitted on supported state changes.

D:

Network automation retries can create duplicate side effects unless operation identity and idempotency are managed. That explains a DIFFERENT scenario: A script uses an unscoped POST endpoint and accidentally creates multiple static routes when its retry logic repeats a successful but slow request. The mechanism to prioritize for this question is: gNMI subscription modes determine whether updates are sampled periodically or emitted on supported state changes.

Question 384

To prevent recurrence of this 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. Which control should be retained?

  1. Record firewall direction and streaming mode in each telemetry service definition.
  2. Include hostname, expiry and certificate chain tests in gNMI collector deployment.
  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

C:

Capacity-test subscription modes against real supported model leaves before large-scale activation. This helps prevent recurrence of the 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. Acceptance evidence should be: A controlled counter sequence generates telemetry at the intended cadence and collector load meets capacity targets.

Incorrect Answers

A:

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: Capacity-test subscription modes against real supported model leaves before large-scale activation.

B:

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: Capacity-test subscription modes against real supported model leaves before large-scale activation.

D:

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: Capacity-test subscription modes against real supported model leaves before large-scale activation.

Question 385

At a converged broadband aggregation team, an engineering review finds: A NetFlow collector receives records with event times 15 minutes behind the source because the PE clock is unsynchronized, scrambling incident and capacity correlations. Which change most directly corrects the service problem?

  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. Apply documented sampling-rate compensation and report estimation uncertainty for usage analytics.
  4. Preserve the full module namespace and revision for each data path and parse namespace-qualified fields.

Explanation

Correct Answer

A:

Synchronize exporter and collector clocks and preserve flow start/end timestamps with correct normalization. This directly addresses the fictional service-provider network case: 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 technical mechanism is: Flow records are meaningful for correlation only when export and collection time bases are reconciled. Verify success by: Test records align with the expected traffic window across multiple provider edges.

Incorrect Answers

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 NetFlow collector receives records with event times 15 minutes behind the source because the PE clock is unsynchronized, scrambling incident and capacity correlations.

C:

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 NetFlow collector receives records with event times 15 minutes behind the source because the PE clock is unsynchronized, scrambling incident and capacity correlations.

D:

Preserve the full module namespace and revision for each data path and parse namespace-qualified fields. This would respond to a DIFFERENT fictional service-provider network issue: Two providers exchange YANG model payloads that use identical local leaf names but different module namespaces, so parsing associates traffic counters with the wrong schema. It does not directly address the current situation: A NetFlow collector receives records with event times 15 minutes behind the source because the PE clock is unsynchronized, scrambling incident and capacity correlations.

Question 386

For a converged broadband aggregation team, operators addressed: A NetFlow collector receives records with event times 15 minutes behind the source because the PE clock is unsynchronized, scrambling incident and capacity correlations. What is the strongest acceptance evidence?

  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. A safe fixture updates the intended keyed service instance and leaves similarly named entries untouched.

Explanation

Correct Answer

B:

Test records align with the expected traffic window across multiple provider edges. This confirms the approved response: Synchronize exporter and collector clocks and preserve flow start/end timestamps with correct normalization. It is relevant because: Flow records are meaningful for correlation only when export and collection time bases are reconciled.

Incorrect Answers

A:

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: Synchronize exporter and collector clocks and preserve flow start/end timestamps with correct normalization.

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: Synchronize exporter and collector clocks and preserve flow start/end timestamps with correct normalization.

D:

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: Synchronize exporter and collector clocks and preserve flow start/end timestamps with correct normalization.

Question 387

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

  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. SNMPv2c community strings do not offer the cryptographic protections available in properly configured SNMPv3.

Explanation

Correct Answer

C:

Flow records are meaningful for correlation only when export and collection time bases are reconciled. This explains the investigated 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. The approved corrective response is: Synchronize exporter and collector clocks and preserve flow start/end timestamps with correct normalization.

Incorrect Answers

A:

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: Flow records are meaningful for correlation only when export and collection time bases are reconciled.

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: Flow records are meaningful for correlation only when export and collection time bases are reconciled.

D:

SNMPv2c community strings do not offer the cryptographic protections available in properly configured SNMPv3. That explains a DIFFERENT scenario: A provider inventories routers using SNMPv2c with an easily guessed community on a shared management segment and exposes interface inventory to unauthorized clients. The mechanism to prioritize for this question is: Flow records are meaningful for correlation only when export and collection time bases are reconciled.

Question 388

A core network change board wants to avoid: A NetFlow collector receives records with event times 15 minutes behind the source because the PE clock is unsynchronized, scrambling incident and capacity correlations. Which ongoing safeguard fits best?

  1. Record sampling configuration in every flow export metadata stream.
  2. Run exporter-template compatibility tests whenever platform software changes.
  3. Record firewall direction and streaming mode in each telemetry service definition.
  4. Alert on NTP drift and template timestamp interpretation anomalies.

Explanation

Correct Answer

D:

Alert on NTP drift and template timestamp interpretation anomalies. This helps prevent recurrence of the 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. Acceptance evidence should be: Test records align with the expected traffic window across multiple provider edges.

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: Alert on NTP drift and template timestamp interpretation anomalies.

B:

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: Alert on NTP drift and template timestamp interpretation anomalies.

C:

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: Alert on NTP drift and template timestamp interpretation anomalies.

Question 389

A carrier service activation check discovers: A NETCONF RPC returns an `<rpc-error>` element but a script reports success because the SSH TCP session remained connected. Which action best restores the intended behavior?

  1. Inspect NETCONF capabilities and target an actually supported datastore and commit behavior.
  2. Parse the NETCONF reply envelope and fail the operation when the RPC reports a relevant error.
  3. Encode the key components per the documented RESTCONF path rules and verify exact target identity before PATCH.
  4. Install a correctly named trusted collector certificate and verify mutual TLS identities where required.

Explanation

Correct Answer

B:

Parse the NETCONF reply envelope and fail the operation when the RPC reports a relevant error. This directly addresses the fictional service-provider network case: A NETCONF RPC returns an `<rpc-error>` element but a script reports success because the SSH TCP session remained connected. The technical mechanism is: Transport session success is not equivalent to NETCONF RPC completion or valid datastore modification. Verify success by: A negative test captures the intended operation failure despite healthy transport and leaves the configuration unchanged.

Incorrect Answers

A:

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 NETCONF RPC returns an `<rpc-error>` element but a script reports success because the SSH TCP session remained connected.

C:

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 NETCONF RPC returns an `<rpc-error>` element but a script reports success because the SSH TCP session remained connected.

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: A NETCONF RPC returns an `<rpc-error>` element but a script reports success because the SSH TCP session remained connected.

Question 390

Following a supported configuration correction, the original issue was: A NETCONF RPC returns an `<rpc-error>` element but a script reports success because the SSH TCP session remained connected. Which observation verifies success?

  1. A safe fixture updates the intended keyed service instance and leaves similarly named entries untouched.
  2. The intended interface change appears in the supported datastore and the controller reports successful RPC completion.
  3. A negative test captures the intended operation failure despite healthy transport and leaves the configuration unchanged.
  4. A controlled request succeeds over authenticated TLS while plaintext attempts are rejected.

Explanation

Correct Answer

C:

A negative test captures the intended operation failure despite healthy transport and leaves the configuration unchanged. This confirms the approved response: Parse the NETCONF reply envelope and fail the operation when the RPC reports a relevant error. It is relevant because: Transport session success is not equivalent to NETCONF RPC completion or valid datastore modification.

Incorrect Answers

A:

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: Parse the NETCONF reply envelope and fail the operation when the RPC reports a relevant error.

B:

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: Parse the NETCONF reply envelope and fail the operation when the RPC reports a relevant error.

D:

A controlled request succeeds over authenticated TLS while plaintext attempts are rejected. This would validate ANOTHER scenario: An operations client sends an unencrypted HTTP call to a management endpoint that requires TLS and reports a protocol failure as an unreachable routing prefix. The specific correction here is: Parse the NETCONF reply envelope and fail the operation when the RPC reports a relevant error.