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 40

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.

Question 391

At an inter-AS service aggregation carrier, an engineer examines: A NETCONF RPC returns an `<rpc-error>` element but a script reports success because the SSH TCP session remained connected. Which technical principle is most applicable?

  1. NETCONF datastore operations depend on capabilities exchanged in the session hello, not a universal candidate workflow.
  2. RESTCONF URLs identify modeled data nodes, and reserved characters in keys may need proper path encoding.
  3. Dial-out telemetry originates at the device, whereas dial-in requires the collector to connect to the device endpoint.
  4. Transport session success is not equivalent to NETCONF RPC completion or valid datastore modification.

Explanation

Correct Answer

D:

Transport session success is not equivalent to NETCONF RPC completion or valid datastore modification. This explains the investigated issue: A NETCONF RPC returns an `<rpc-error>` element but a script reports success because the SSH TCP session remained connected. The approved corrective response is: Parse the NETCONF reply envelope and fail the operation when the RPC reports a relevant error.

Incorrect Answers

A:

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: Transport session success is not equivalent to NETCONF RPC completion or valid datastore modification.

B:

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: Transport session success is not equivalent to NETCONF RPC completion or valid datastore modification.

C:

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: Transport session success is not equivalent to NETCONF RPC completion or valid datastore modification.

Question 392

For an inter-AS service aggregation carrier, the change record describes: A NETCONF RPC returns an `<rpc-error>` element but a script reports success because the SSH TCP session remained connected. What preventive validation should be standard?

  1. Require RPC reply and postchange readback checks for configuration jobs.
  2. Include special-character and compound-key tests for RESTCONF clients.
  3. Discover NETCONF capabilities at every new device onboarding.
  4. Discover supported API transports and model revisions during device enrollment.

Explanation

Correct Answer

A:

Require RPC reply and postchange readback checks for configuration jobs. This helps prevent recurrence of the issue: A NETCONF RPC returns an `<rpc-error>` element but a script reports success because the SSH TCP session remained connected. Acceptance evidence should be: A negative test captures the intended operation failure despite healthy transport and leaves the configuration unchanged.

Incorrect Answers

B:

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: Require RPC reply and postchange readback checks for configuration jobs.

C:

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: Require RPC reply and postchange readback checks for configuration jobs.

D:

Discover supported API transports and model revisions during device enrollment. That is a sensible control for 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. It is less targeted to this issue than: Require RPC reply and postchange readback checks for configuration jobs.

Question 393

For a regional service-provider operations center, the failure is: A trap receiver processes authenticationFailure SNMP notifications but drops interfaceDown events because its trap ACL permits only one source subnet. Which authorized correction best addresses it?

  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. Use the documented idempotent update operation or reconcile existing state before retrying a non-idempotent creation.

Explanation

Correct Answer

C:

Align authorized SNMP notification-source addresses and collector access lists with all intended router loopbacks. This directly addresses the fictional service-provider network case: A trap receiver processes authenticationFailure SNMP notifications but drops interfaceDown events because its trap ACL permits only one source subnet. The technical mechanism is: SNMP traps depend on exporter source addressing and receiver permissions, independent of periodic polling success. Verify success by: A controlled interface-down event generates one accepted trap while unapproved senders remain blocked.

Incorrect Answers

A:

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 trap receiver processes authenticationFailure SNMP notifications but drops interfaceDown events because its trap ACL permits only one source subnet.

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 trap receiver processes authenticationFailure SNMP notifications but drops interfaceDown events because its trap ACL permits only one source subnet.

D:

Use the documented idempotent update operation or reconcile existing state before retrying a non-idempotent creation. This would respond to a DIFFERENT fictional service-provider network issue: A script uses an unscoped POST endpoint and accidentally creates multiple static routes when its retry logic repeats a successful but slow request. It does not directly address the current situation: A trap receiver processes authenticationFailure SNMP notifications but drops interfaceDown events because its trap ACL permits only one source subnet.

Question 394

After fixing the following network problem, what should the team verify: A trap receiver processes authenticationFailure SNMP notifications but drops interfaceDown events because its trap ACL permits only one source subnet.

  1. An authorized monitoring poll succeeds under protected SNMPv3 while an unauthorized v2c request fails.
  2. An SNMP walk finds the expected instance and polling returns a plausible CPU sample from the correct scope.
  3. A fixture containing the two modules resolves both leaf values to their correct models without ambiguity.
  4. A controlled interface-down event generates one accepted trap while unapproved senders remain blocked.

Explanation

Correct Answer

D:

A controlled interface-down event generates one accepted trap while unapproved senders remain blocked. This confirms the approved response: Align authorized SNMP notification-source addresses and collector access lists with all intended router loopbacks. It is relevant because: SNMP traps depend on exporter source addressing and receiver permissions, independent of periodic polling success.

Incorrect Answers

A:

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: Align authorized SNMP notification-source addresses and collector access lists with all intended router loopbacks.

B:

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: Align authorized SNMP notification-source addresses and collector access lists with all intended router loopbacks.

C:

A fixture containing the two modules resolves both leaf values to their correct models without ambiguity. This would validate ANOTHER 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 specific correction here is: Align authorized SNMP notification-source addresses and collector access lists with all intended router loopbacks.

Question 395

A carrier root-cause review considers: A trap receiver processes authenticationFailure SNMP notifications but drops interfaceDown events because its trap ACL permits only one source subnet. What underlying mechanism explains this?

  1. SNMP traps depend on exporter source addressing and receiver permissions, independent of periodic polling success.
  2. SNMP data is organized by object identifiers and may vary across platform-specific MIB modules.
  3. SNMPv2c community strings do not offer the cryptographic protections available in properly configured SNMPv3.
  4. IaC state must be coordinated to prevent concurrent operations from clobbering resource identity and dependencies.

Explanation

Correct Answer

A:

SNMP traps depend on exporter source addressing and receiver permissions, independent of periodic polling success. This explains the investigated issue: A trap receiver processes authenticationFailure SNMP notifications but drops interfaceDown events because its trap ACL permits only one source subnet. The approved corrective response is: Align authorized SNMP notification-source addresses and collector access lists with all intended router loopbacks.

Incorrect Answers

B:

SNMP data is organized by object identifiers and may vary across platform-specific MIB modules. That explains a DIFFERENT scenario: A monitoring backend discovers no device CPU metric because it queries a nonexistent vendor OID and assumes the router is down. The mechanism to prioritize for this question is: SNMP traps depend on exporter source addressing and receiver permissions, independent of periodic polling success.

C:

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 traps depend on exporter source addressing and receiver permissions, independent of periodic polling success.

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: SNMP traps depend on exporter source addressing and receiver permissions, independent of periodic polling success.

Question 396

After addressing: A trap receiver processes authenticationFailure SNMP notifications but drops interfaceDown events because its trap ACL permits only one source subnet. Which recurring service assurance check is most useful?

  1. Retire insecure communities and scan management access policy regularly.
  2. Test alarm-source reachability and permitted OIDs during management network changes.
  3. Validate OID presence after each hardware or software upgrade.
  4. Audit bootstrap credential issuance and retirement per asset.

Explanation

Correct Answer

B:

Test alarm-source reachability and permitted OIDs during management network changes. This helps prevent recurrence of the issue: A trap receiver processes authenticationFailure SNMP notifications but drops interfaceDown events because its trap ACL permits only one source subnet. Acceptance evidence should be: A controlled interface-down event generates one accepted trap while unapproved senders remain blocked.

Incorrect Answers

A:

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: Test alarm-source reachability and permitted OIDs during management network changes.

C:

Validate OID presence after each hardware or software upgrade. That is a sensible control for ANOTHER scenario: A monitoring backend discovers no device CPU metric because it queries a nonexistent vendor OID and assumes the router is down. It is less targeted to this issue than: Test alarm-source reachability and permitted OIDs during management network changes.

D:

Audit bootstrap credential issuance and retirement per asset. That is a sensible control for 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. It is less targeted to this issue than: Test alarm-source reachability and permitted OIDs during management network changes.

Question 397

A provider backbone escalation identifies: A core team routes an SRv6 service through legacy MPLS-only nodes without defining an interworking point, so traffic loses its intended segment behavior. What should the network team implement?

  1. Engineer the xhaul path using the documented latency, synchronization, capacity and isolation targets for the radio architecture.
  2. Define the Carrier Ethernet E-Line service demarcation and use an appropriate provider Ethernet or pseudowire transport between the designated endpoints.
  3. Align the DS-TE class type bandwidth model and router reservations with the intended MAM or RDM admission policy.
  4. Place an explicit supported SRv6-to-MPLS interworking function at the technology boundary or constrain the SRv6 path to capable nodes.

Explanation

Correct Answer

D:

Place an explicit supported SRv6-to-MPLS interworking function at the technology boundary or constrain the SRv6 path to capable nodes. This directly addresses the fictional service-provider network case: 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 technical mechanism is: An SRv6 segment list is encoded in IPv6 forwarding constructs and cannot be processed as an MPLS label stack by a non-SRv6 router. Verify success by: A lab trace shows the correct encapsulation before and after the gateway with the customer prefix still reachable.

Incorrect Answers

A:

Engineer the xhaul path using the documented latency, synchronization, capacity and isolation targets for the radio architecture. This would respond to a DIFFERENT fictional service-provider network issue: A 5G fronthaul transport team treats a RAN radio-to-distributed-unit path as an ordinary best-effort internet uplink and sees timing instability during peak load. It does not directly address the current situation: A core team routes an SRv6 service through legacy MPLS-only nodes without defining an interworking point, so traffic loses its intended segment behavior.

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 core team routes an SRv6 service through legacy MPLS-only nodes without defining an interworking point, so traffic loses its intended segment behavior.

C:

Align the DS-TE class type bandwidth model and router reservations with the intended MAM or RDM admission policy. This would respond to a DIFFERENT fictional service-provider network issue: A transport planner provisions an RSVP bandwidth pool using MAM assumptions but the network is configured for RDM, causing unexpected class bandwidth borrowing. It does not directly address the current situation: A core team routes an SRv6 service through legacy MPLS-only nodes without defining an interworking point, so traffic loses its intended segment behavior.

Question 398

A service-provider operations test targets: A core team routes an SRv6 service through legacy MPLS-only nodes without defining an interworking point, so traffic loses its intended segment behavior. Which result is required?

  1. A lab trace shows the correct encapsulation before and after the gateway with the customer prefix still reachable.
  2. A test subscriber modem or ONU registers on the matching access system using its intended provisioning method.
  3. A test frame sent between the two UNI endpoints retains the required service VLAN attributes and does not reach any unapproved site.
  4. A packet capture shows one flow retains a consistent label and path selection stabilizes.

Explanation

Correct Answer

A:

A lab trace shows the correct encapsulation before and after the gateway with the customer prefix still reachable. This confirms the approved response: Place an explicit supported SRv6-to-MPLS interworking function at the technology boundary or constrain the SRv6 path to capable nodes. It is relevant because: An SRv6 segment list is encoded in IPv6 forwarding constructs and cannot be processed as an MPLS label stack by a non-SRv6 router.

Incorrect Answers

B:

A test subscriber modem or ONU registers on the matching access system using its intended provisioning method. This would validate ANOTHER scenario: A wholesale provider expects DOCSIS cable access equipment to terminate xPON optical network units and finds that provisioning never completes. The specific correction here is: Place an explicit supported SRv6-to-MPLS interworking function at the technology boundary or constrain the SRv6 path to capable nodes.

C:

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: Place an explicit supported SRv6-to-MPLS interworking function at the technology boundary or constrain the SRv6 path to capable nodes.

D:

A packet capture shows one flow retains a consistent label and path selection stabilizes. This would validate ANOTHER scenario: An IPv6 multicast-sensitive telemetry application changes the IPv6 flow label every packet and load-sharing routers distribute a single transport stream across many paths. The specific correction here is: Place an explicit supported SRv6-to-MPLS interworking function at the technology boundary or constrain the SRv6 path to capable nodes.

Question 399

A provider troubleshooting note states: A core team routes an SRv6 service through legacy MPLS-only nodes without defining an interworking point, so traffic loses its intended segment behavior. Which mechanism is central?

  1. Optical and packet layers can both repair failures, and uncoordinated timers may cause oscillation or unnecessarily prolonged reconvergence.
  2. An SRv6 segment list is encoded in IPv6 forwarding constructs and cannot be processed as an MPLS label stack by a non-SRv6 router.
  3. An E-Line is a point-to-point Ethernet service whose service boundary must be explicit even when the underlying provider backbone uses routed transport.
  4. The IPv6 flow label can help identify related packets for consistent treatment when network devices use it in hashing.

Explanation

Correct Answer

B:

An SRv6 segment list is encoded in IPv6 forwarding constructs and cannot be processed as an MPLS label stack by a non-SRv6 router. This explains the investigated issue: 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 approved corrective response is: Place an explicit supported SRv6-to-MPLS interworking function at the technology boundary or constrain the SRv6 path to capable nodes.

Incorrect Answers

A:

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: An SRv6 segment list is encoded in IPv6 forwarding constructs and cannot be processed as an MPLS label stack by a non-SRv6 router.

C:

An E-Line is a point-to-point Ethernet service whose service boundary must be explicit even when the underlying provider backbone uses routed transport. That explains a DIFFERENT 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 mechanism to prioritize for this question is: An SRv6 segment list is encoded in IPv6 forwarding constructs and cannot be processed as an MPLS label stack by a non-SRv6 router.

D:

The IPv6 flow label can help identify related packets for consistent treatment when network devices use it in hashing. That explains a DIFFERENT scenario: An IPv6 multicast-sensitive telemetry application changes the IPv6 flow label every packet and load-sharing routers distribute a single transport stream across many paths. The mechanism to prioritize for this question is: An SRv6 segment list is encoded in IPv6 forwarding constructs and cannot be processed as an MPLS label stack by a non-SRv6 router.

Question 400

To prevent recurrence of this provider network issue: A core team routes an SRv6 service through legacy MPLS-only nodes without defining an interworking point, so traffic loses its intended segment behavior. Which control should be retained?

  1. Check subscriber access-media type before selecting aggregation hardware and automation profiles.
  2. Review optical and routing timer interaction in multilayer failure drills.
  3. Maintain an inventory of per-hop encapsulation support and interworking validation tests.
  4. Require postboot image attestation and rollback readiness in change acceptance.

Explanation

Correct Answer

C:

Maintain an inventory of per-hop encapsulation support and interworking validation tests. This helps prevent recurrence of the issue: A core team routes an SRv6 service through legacy MPLS-only nodes without defining an interworking point, so traffic loses its intended segment behavior. Acceptance evidence should be: A lab trace shows the correct encapsulation before and after the gateway with the customer prefix still reachable.

Incorrect Answers

A:

Check subscriber access-media type before selecting aggregation hardware and automation profiles. That is a sensible control for ANOTHER scenario: A wholesale provider expects DOCSIS cable access equipment to terminate xPON optical network units and finds that provisioning never completes. It is less targeted to this issue than: Maintain an inventory of per-hop encapsulation support and interworking validation tests.

B:

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: Maintain an inventory of per-hop encapsulation support and interworking validation tests.

D:

Require postboot image attestation and rollback readiness in change acceptance. That is a sensible control for 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. It is less targeted to this issue than: Maintain an inventory of per-hop encapsulation support and interworking validation tests.