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 27

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.

Question 261

A carrier service activation check discovers: A monitoring backend discovers no device CPU metric because it queries a nonexistent vendor OID and assumes the router is down. Which action best restores the intended behavior?

  1. Align authorized SNMP notification-source addresses and collector access lists with all intended router loopbacks.
  2. Verify the device-supported SNMP MIB/OID mapping and appropriate index before collecting the metric.
  3. Migrate supported devices to SNMPv3 with appropriate authentication/privacy and restrict manager addresses.
  4. Serialize the payload using the documented JSON or XML format and matching Content-Type header.

Explanation

Correct Answer

B:

Verify the device-supported SNMP MIB/OID mapping and appropriate index before collecting the metric. This directly addresses the fictional service-provider network case: A monitoring backend discovers no device CPU metric because it queries a nonexistent vendor OID and assumes the router is down. The technical mechanism is: SNMP data is organized by object identifiers and may vary across platform-specific MIB modules. Verify success by: An SNMP walk finds the expected instance and polling returns a plausible CPU sample from the correct scope.

Incorrect Answers

A:

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 monitoring backend discovers no device CPU metric because it queries a nonexistent vendor OID and assumes the router is down.

C:

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

D:

Serialize the payload using the documented JSON or XML format and matching Content-Type header. This would respond to a DIFFERENT fictional service-provider network issue: An external Python script posts interface descriptions to a router API but uses an incorrect content type and receives 415 Unsupported Media Type. It does not directly address the current situation: A monitoring backend discovers no device CPU metric because it queries a nonexistent vendor OID and assumes the router is down.

Question 262

Following a supported configuration correction, the original issue was: A monitoring backend discovers no device CPU metric because it queries a nonexistent vendor OID and assumes the router is down. Which observation verifies success?

  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. A read-only fixture returns the correct interface counters without changing running configuration.

Explanation

Correct Answer

C:

An SNMP walk finds the expected instance and polling returns a plausible CPU sample from the correct scope. This confirms the approved response: Verify the device-supported SNMP MIB/OID mapping and appropriate index before collecting the metric. It is relevant because: SNMP data is organized by object identifiers and may vary across platform-specific MIB modules.

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: Verify the device-supported SNMP MIB/OID mapping and appropriate index before collecting the metric.

B:

An authorized monitoring poll succeeds under protected SNMPv3 while an unauthorized v2c request fails. This would validate 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. The specific correction here is: Verify the device-supported SNMP MIB/OID mapping and appropriate index before collecting the metric.

D:

A read-only fixture returns the correct interface counters without changing running configuration. This would validate ANOTHER scenario: A provider telemetry collector expects every IOS XR interface state query to use a generic SNMP community string while the device exposes a supported model-driven operational endpoint. The specific correction here is: Verify the device-supported SNMP MIB/OID mapping and appropriate index before collecting the metric.

Question 263

At a carrier automation platform team, an engineer examines: A monitoring backend discovers no device CPU metric because it queries a nonexistent vendor OID and assumes the router is down. Which technical principle is most applicable?

  1. SNMPv2c community strings do not offer the cryptographic protections available in properly configured SNMPv3.
  2. SNMP traps depend on exporter source addressing and receiver permissions, independent of periodic polling success.
  3. YANG namespaces and revisions give modeled nodes meaning beyond their unqualified display names.
  4. SNMP data is organized by object identifiers and may vary across platform-specific MIB modules.

Explanation

Correct Answer

D:

SNMP data is organized by object identifiers and may vary across platform-specific MIB modules. This explains the investigated issue: A monitoring backend discovers no device CPU metric because it queries a nonexistent vendor OID and assumes the router is down. The approved corrective response is: Verify the device-supported SNMP MIB/OID mapping and appropriate index before collecting the metric.

Incorrect Answers

A:

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: SNMP data is organized by object identifiers and may vary across platform-specific MIB modules.

B:

SNMP traps depend on exporter source addressing and receiver permissions, independent of periodic polling success. That explains a DIFFERENT scenario: A trap receiver processes authenticationFailure SNMP notifications but drops interfaceDown events because its trap ACL permits only one source subnet. The mechanism to prioritize for this question is: SNMP data is organized by object identifiers and may vary across platform-specific MIB modules.

C:

YANG namespaces and revisions give modeled nodes meaning beyond their unqualified display names. That explains a DIFFERENT scenario: Two providers exchange YANG model payloads that use identical local leaf names but different module namespaces, so parsing associates traffic counters with the wrong schema. The mechanism to prioritize for this question is: SNMP data is organized by object identifiers and may vary across platform-specific MIB modules.

Question 264

For a carrier automation platform team, the change record describes: A monitoring backend discovers no device CPU metric because it queries a nonexistent vendor OID and assumes the router is down. What preventive validation should be standard?

  1. Validate OID presence after each hardware or software upgrade.
  2. Retire insecure communities and scan management access policy regularly.
  3. Test alarm-source reachability and permitted OIDs during management network changes.
  4. Alert on NTP drift and template timestamp interpretation anomalies.

Explanation

Correct Answer

A:

Validate OID presence after each hardware or software upgrade. This helps prevent recurrence of the issue: A monitoring backend discovers no device CPU metric because it queries a nonexistent vendor OID and assumes the router is down. Acceptance evidence should be: An SNMP walk finds the expected instance and polling returns a plausible CPU sample from the correct scope.

Incorrect Answers

B:

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: Validate OID presence after each hardware or software upgrade.

C:

Test alarm-source reachability and permitted OIDs during management network changes. That is a sensible control for ANOTHER scenario: A trap receiver processes authenticationFailure SNMP notifications but drops interfaceDown events because its trap ACL permits only one source subnet. It is less targeted to this issue than: Validate OID presence after each hardware or software upgrade.

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: Validate OID presence after each hardware or software upgrade.

Question 265

For a multi-tenant data transport provider, the failure is: A wholesale provider expects DOCSIS cable access equipment to terminate xPON optical network units and finds that provisioning never completes. Which authorized correction best addresses it?

  1. Coordinate optical restoration and IP-layer convergence objectives using a documented routed-optical failure strategy.
  2. Define the Carrier Ethernet E-Line service demarcation and use an appropriate provider Ethernet or pseudowire transport between the designated endpoints.
  3. Select the appropriate cable modem termination or passive optical line termination architecture for the actual last-mile medium.
  4. Transmit the documented token through protected authorization headers over TLS and revoke any logged credentials.

Explanation

Correct Answer

C:

Select the appropriate cable modem termination or passive optical line termination architecture for the actual last-mile medium. This directly addresses the fictional service-provider network case: A wholesale provider expects DOCSIS cable access equipment to terminate xPON optical network units and finds that provisioning never completes. The technical mechanism is: DOCSIS and xPON are different access technologies with different physical and control-plane termination systems. Verify success by: A test subscriber modem or ONU registers on the matching access system using its intended provisioning method.

Incorrect Answers

A:

Coordinate optical restoration and IP-layer convergence objectives using a documented routed-optical failure strategy. This would respond to a DIFFERENT fictional service-provider network issue: A provider builds an optical routed backbone but still treats every DWDM wavelength change as independent from IP restoration, creating contradictory failover policies. It does not directly address the current situation: A wholesale provider expects DOCSIS cable access equipment to terminate xPON optical network units and finds that provisioning never completes.

B:

Define the Carrier Ethernet E-Line service demarcation and use an appropriate provider Ethernet or pseudowire transport between the designated endpoints. This would respond to a DIFFERENT fictional service-provider network issue: A metro aggregation design places a latency-sensitive enterprise E-Line directly across an IP core with no documented Ethernet service handoff, leading to mismatched expectations for transparent VLAN carriage. It does not directly address the current situation: A wholesale provider expects DOCSIS cable access equipment to terminate xPON optical network units and finds that provisioning never completes.

D:

Transmit the documented token through protected authorization headers over TLS and revoke any logged credentials. This would respond to a DIFFERENT fictional service-provider network issue: A configuration pipeline invokes router REST APIs with bearer tokens embedded in URL parameters, which are copied into proxy logs. It does not directly address the current situation: A wholesale provider expects DOCSIS cable access equipment to terminate xPON optical network units and finds that provisioning never completes.

Question 266

After fixing the following network problem, what should the team verify: A wholesale provider expects DOCSIS cable access equipment to terminate xPON optical network units and finds that provisioning never completes.

  1. A lab trace shows the correct encapsulation before and after the gateway with the customer prefix still reachable.
  2. A test frame sent between the two UNI endpoints retains the required service VLAN attributes and does not reach any unapproved site.
  3. A capability check selects a valid interface for each device and rejects models not advertised by the platform.
  4. A test subscriber modem or ONU registers on the matching access system using its intended provisioning method.

Explanation

Correct Answer

D:

A test subscriber modem or ONU registers on the matching access system using its intended provisioning method. This confirms the approved response: Select the appropriate cable modem termination or passive optical line termination architecture for the actual last-mile medium. It is relevant because: DOCSIS and xPON are different access technologies with different physical and control-plane termination systems.

Incorrect Answers

A:

A lab trace shows the correct encapsulation before and after the gateway with the customer prefix still reachable. This would validate ANOTHER scenario: A core team routes an SRv6 service through legacy MPLS-only nodes without defining an interworking point, so traffic loses its intended segment behavior. The specific correction here is: Select the appropriate cable modem termination or passive optical line termination architecture for the actual last-mile medium.

B:

A test frame sent between the two UNI endpoints retains the required service VLAN attributes and does not reach any unapproved site. This would validate ANOTHER scenario: A metro aggregation design places a latency-sensitive enterprise E-Line directly across an IP core with no documented Ethernet service handoff, leading to mismatched expectations for transparent VLAN carriage. The specific correction here is: Select the appropriate cable modem termination or passive optical line termination architecture for the actual last-mile medium.

C:

A capability check selects a valid interface for each device and rejects models not advertised by the platform. This would validate ANOTHER scenario: A mixed fleet automation job expects an IOS XE NETCONF configuration schema to map identically to all classic IOS software releases. The specific correction here is: Select the appropriate cable modem termination or passive optical line termination architecture for the actual last-mile medium.

Question 267

A carrier root-cause review considers: A wholesale provider expects DOCSIS cable access equipment to terminate xPON optical network units and finds that provisioning never completes. What underlying mechanism explains this?

  1. DOCSIS and xPON are different access technologies with different physical and control-plane termination systems.
  2. Optical and packet layers can both repair failures, and uncoordinated timers may cause oscillation or unnecessarily prolonged reconvergence.
  3. An SRv6 segment list is encoded in IPv6 forwarding constructs and cannot be processed as an MPLS label stack by a non-SRv6 router.
  4. Application hosting support is platform-specific and competing workloads can impact critical control processes.

Explanation

Correct Answer

A:

DOCSIS and xPON are different access technologies with different physical and control-plane termination systems. This explains the investigated issue: A wholesale provider expects DOCSIS cable access equipment to terminate xPON optical network units and finds that provisioning never completes. The approved corrective response is: Select the appropriate cable modem termination or passive optical line termination architecture for the actual last-mile medium.

Incorrect Answers

B:

Optical and packet layers can both repair failures, and uncoordinated timers may cause oscillation or unnecessarily prolonged reconvergence. That explains a DIFFERENT scenario: A provider builds an optical routed backbone but still treats every DWDM wavelength change as independent from IP restoration, creating contradictory failover policies. The mechanism to prioritize for this question is: DOCSIS and xPON are different access technologies with different physical and control-plane termination systems.

C:

An SRv6 segment list is encoded in IPv6 forwarding constructs and cannot be processed as an MPLS label stack by a non-SRv6 router. That explains a DIFFERENT scenario: A core team routes an SRv6 service through legacy MPLS-only nodes without defining an interworking point, so traffic loses its intended segment behavior. The mechanism to prioritize for this question is: DOCSIS and xPON are different access technologies with different physical and control-plane termination systems.

D:

Application hosting support is platform-specific and competing workloads can impact critical control processes. That explains a DIFFERENT scenario: An operations team deploys an application container directly onto a router control processor without checking vendor-supported hosting resources or isolation limits. The mechanism to prioritize for this question is: DOCSIS and xPON are different access technologies with different physical and control-plane termination systems.

Question 268

After addressing: A wholesale provider expects DOCSIS cable access equipment to terminate xPON optical network units and finds that provisioning never completes. Which recurring service assurance check is most useful?

  1. Review optical and routing timer interaction in multilayer failure drills.
  2. Check subscriber access-media type before selecting aggregation hardware and automation profiles.
  3. Maintain an inventory of per-hop encapsulation support and interworking validation tests.
  4. Run restart and rescheduling persistence drills before production upgrade windows.

Explanation

Correct Answer

B:

Check subscriber access-media type before selecting aggregation hardware and automation profiles. This helps prevent recurrence of the issue: A wholesale provider expects DOCSIS cable access equipment to terminate xPON optical network units and finds that provisioning never completes. Acceptance evidence should be: A test subscriber modem or ONU registers on the matching access system using its intended provisioning method.

Incorrect Answers

A:

Review optical and routing timer interaction in multilayer failure drills. That is a sensible control for ANOTHER scenario: A provider builds an optical routed backbone but still treats every DWDM wavelength change as independent from IP restoration, creating contradictory failover policies. It is less targeted to this issue than: Check subscriber access-media type before selecting aggregation hardware and automation profiles.

C:

Maintain an inventory of per-hop encapsulation support and interworking validation tests. That is a sensible control for ANOTHER scenario: A core team routes an SRv6 service through legacy MPLS-only nodes without defining an interworking point, so traffic loses its intended segment behavior. It is less targeted to this issue than: Check subscriber access-media type before selecting aggregation hardware and automation profiles.

D:

Run restart and rescheduling persistence drills before production upgrade windows. That is a sensible control for ANOTHER scenario: A provider stores a VNF configuration exclusively on the ephemeral container filesystem and loses subscriber policy after an orchestrator restarts the instance. It is less targeted to this issue than: Check subscriber access-media type before selecting aggregation hardware and automation profiles.

Question 269

A provider backbone escalation identifies: A mixed fleet automation job expects an IOS XE NETCONF configuration schema to map identically to all classic IOS software releases. What should the network team implement?

  1. Use supported IOS XR process or application recovery procedures and verify expected route-processing behavior without a blanket chassis reload.
  2. Identify the running IOS XR platform and follow its supported installation and operational command workflow.
  3. Use only the supported application-hosting environment with explicit CPU, memory, interface and lifecycle controls.
  4. Classify the actual software platform and supported model-driven capabilities before using a shared configuration adapter.

Explanation

Correct Answer

D:

Classify the actual software platform and supported model-driven capabilities before using a shared configuration adapter. This directly addresses the fictional service-provider network case: A mixed fleet automation job expects an IOS XE NETCONF configuration schema to map identically to all classic IOS software releases. The technical mechanism is: Cisco IOS software families have different feature and programmability interfaces despite overlapping CLI conventions. Verify success by: A capability check selects a valid interface for each device and rejects models not advertised by the platform.

Incorrect Answers

A:

Use supported IOS XR process or application recovery procedures and verify expected route-processing behavior without a blanket chassis reload. This would respond to a DIFFERENT fictional service-provider network issue: An engineer assumes a process restart on an IOS XR control-plane node always reloads the entire router, causing an unnecessary maintenance outage. It does not directly address the current situation: A mixed fleet automation job expects an IOS XE NETCONF configuration schema to map identically to all classic IOS software releases.

B:

Identify the running IOS XR platform and follow its supported installation and operational command workflow. This would respond to a DIFFERENT fictional service-provider network issue: A technician deploys IOS XE package commands to an IOS XR route processor, then misinterprets the command rejection as a missing license. It does not directly address the current situation: A mixed fleet automation job expects an IOS XE NETCONF configuration schema to map identically to all classic IOS software releases.

C:

Use only the supported application-hosting environment with explicit CPU, memory, interface and lifecycle controls. This would respond to a DIFFERENT fictional service-provider network issue: An operations team deploys an application container directly onto a router control processor without checking vendor-supported hosting resources or isolation limits. It does not directly address the current situation: A mixed fleet automation job expects an IOS XE NETCONF configuration schema to map identically to all classic IOS software releases.

Question 270

A service-provider operations test targets: A mixed fleet automation job expects an IOS XE NETCONF configuration schema to map identically to all classic IOS software releases. Which result is required?

  1. A capability check selects a valid interface for each device and rejects models not advertised by the platform.
  2. Reload verification shows the expected version and package status with the previous image available for controlled rollback.
  3. A controlled process test restores the affected service while unrelated line-card forwarding remains stable where supported.
  4. A lab app runs inside its permitted resource envelope while routing processes remain healthy under load.

Explanation

Correct Answer

A:

A capability check selects a valid interface for each device and rejects models not advertised by the platform. This confirms the approved response: Classify the actual software platform and supported model-driven capabilities before using a shared configuration adapter. It is relevant because: Cisco IOS software families have different feature and programmability interfaces despite overlapping CLI conventions.

Incorrect Answers

B:

Reload verification shows the expected version and package status with the previous image available for controlled rollback. This would validate ANOTHER scenario: After an IOS XE image update, the route processor boots but a router retains an old package set because the team updated the boot variable without verifying install mode. The specific correction here is: Classify the actual software platform and supported model-driven capabilities before using a shared configuration adapter.

C:

A controlled process test restores the affected service while unrelated line-card forwarding remains stable where supported. This would validate ANOTHER scenario: An engineer assumes a process restart on an IOS XR control-plane node always reloads the entire router, causing an unnecessary maintenance outage. The specific correction here is: Classify the actual software platform and supported model-driven capabilities before using a shared configuration adapter.

D:

A lab app runs inside its permitted resource envelope while routing processes remain healthy under load. This would validate ANOTHER scenario: An operations team deploys an application container directly onto a router control processor without checking vendor-supported hosting resources or isolation limits. The specific correction here is: Classify the actual software platform and supported model-driven capabilities before using a shared configuration adapter.