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 14

Question 130

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

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

Explanation

Correct Answer

B:

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

Incorrect Answers

A:

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

C:

An SNMP walk finds the expected instance and polling returns a plausible CPU sample from the correct scope. This would validate ANOTHER scenario: A monitoring backend discovers no device CPU metric because it queries a nonexistent vendor OID and assumes the router is down. The specific correction here is: Migrate supported devices to SNMPv3 with appropriate authentication/privacy and restrict manager addresses.

D:

The dry-run diff lists only the intended PE and interface while the old PE remains unchanged. This would validate ANOTHER scenario: An NSO service template reuses a stale network element device ID, so new customer interface configuration is pushed to the wrong PE. The specific correction here is: Migrate supported devices to SNMPv3 with appropriate authentication/privacy and restrict manager addresses.

Question 131

Which network protocol or forwarding behavior explains the following issue: A provider inventories routers using SNMPv2c with an easily guessed community on a shared management segment and exposes interface inventory to unauthorized clients.

  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. HTTP API methods require supported representations, and mismatched media types can block configuration before authorization of the actual change.

Explanation

Correct Answer

C:

SNMPv2c community strings do not offer the cryptographic protections available in properly configured SNMPv3. This explains the investigated issue: A provider inventories routers using SNMPv2c with an easily guessed community on a shared management segment and exposes interface inventory to unauthorized clients. The approved corrective response is: Migrate supported devices to SNMPv3 with appropriate authentication/privacy and restrict manager addresses.

Incorrect Answers

A:

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

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

D:

HTTP API methods require supported representations, and mismatched media types can block configuration before authorization of the actual change. That explains a DIFFERENT scenario: An external Python script posts interface descriptions to a router API but uses an incorrect content type and receives 415 Unsupported Media Type. The mechanism to prioritize for this question is: SNMPv2c community strings do not offer the cryptographic protections available in properly configured SNMPv3.

Question 132

A core network change board wants to avoid: A provider inventories routers using SNMPv2c with an easily guessed community on a shared management segment and exposes interface inventory to unauthorized clients. Which ongoing safeguard fits best?

  1. Validate OID presence after each hardware or software upgrade.
  2. Test alarm-source reachability and permitted OIDs during management network changes.
  3. Capacity-test subscription modes against real supported model leaves before large-scale activation.
  4. Retire insecure communities and scan management access policy regularly.

Explanation

Correct Answer

D:

Retire insecure communities and scan management access policy regularly. This helps prevent recurrence of the issue: A provider inventories routers using SNMPv2c with an easily guessed community on a shared management segment and exposes interface inventory to unauthorized clients. Acceptance evidence should be: An authorized monitoring poll succeeds under protected SNMPv3 while an unauthorized v2c request fails.

Incorrect Answers

A:

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: Retire insecure communities and scan management access policy regularly.

B:

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: Retire insecure communities and scan management access policy regularly.

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: Retire insecure communities and scan management access policy regularly.

Question 133

A carrier service activation check discovers: 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. Which action best restores the intended behavior?

  1. Define the Carrier Ethernet E-Line service demarcation and use an appropriate provider Ethernet or pseudowire transport between the designated endpoints.
  2. Engineer the xhaul path using the documented latency, synchronization, capacity and isolation targets for the radio architecture.
  3. Coordinate optical restoration and IP-layer convergence objectives using a documented routed-optical failure strategy.
  4. Persist required configuration in a supported durable data service or mounted volume and redeploy from versioned desired state.

Explanation

Correct Answer

B:

Engineer the xhaul path using the documented latency, synchronization, capacity and isolation targets for the radio architecture. This directly addresses the fictional service-provider network case: 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. The technical mechanism is: Fronthaul and midhaul segments have stringent timing and delay requirements that differ from generic broadband service transport. Verify success by: Synthetic timing and delay tests remain within the RAN interface limits at full traffic load.

Incorrect Answers

A:

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 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.

C:

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 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.

D:

Persist required configuration in a supported durable data service or mounted volume and redeploy from versioned desired state. This would respond to a DIFFERENT fictional service-provider network issue: A provider stores a VNF configuration exclusively on the ephemeral container filesystem and loses subscriber policy after an orchestrator restarts the instance. It does not directly address the current situation: 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.

Question 134

Following a supported configuration correction, the original issue was: 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. Which observation verifies success?

  1. A test subscriber modem or ONU registers on the matching access system using its intended provisioning method.
  2. A test frame sent between the two UNI endpoints retains the required service VLAN attributes and does not reach any unapproved site.
  3. Synthetic timing and delay tests remain within the RAN interface limits at full traffic load.
  4. Authorized neighbors exchange the intended FEC labels while an unapproved router cannot create a usable session.

Explanation

Correct Answer

C:

Synthetic timing and delay tests remain within the RAN interface limits at full traffic load. This confirms the approved response: Engineer the xhaul path using the documented latency, synchronization, capacity and isolation targets for the radio architecture. It is relevant because: Fronthaul and midhaul segments have stringent timing and delay requirements that differ from generic broadband service transport.

Incorrect Answers

A:

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: Engineer the xhaul path using the documented latency, synchronization, capacity and isolation targets for the radio architecture.

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: Engineer the xhaul path using the documented latency, synchronization, capacity and isolation targets for the radio architecture.

D:

Authorized neighbors exchange the intended FEC labels while an unapproved router cannot create a usable session. This would validate ANOTHER scenario: A provider accepts unbounded remote LDP label mappings from an unexpected neighbor in a shared transport environment. The specific correction here is: Engineer the xhaul path using the documented latency, synchronization, capacity and isolation targets for the radio architecture.

Question 135

At a mobile packet-core transport operator, an engineer examines: 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. Which technical principle is most applicable?

  1. DOCSIS and xPON are different access technologies with different physical and control-plane termination systems.
  2. 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.
  3. URL query strings can leak reusable secrets through access logs and monitoring systems.
  4. Fronthaul and midhaul segments have stringent timing and delay requirements that differ from generic broadband service transport.

Explanation

Correct Answer

D:

Fronthaul and midhaul segments have stringent timing and delay requirements that differ from generic broadband service transport. This explains the investigated 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. The approved corrective response is: Engineer the xhaul path using the documented latency, synchronization, capacity and isolation targets for the radio architecture.

Incorrect Answers

A:

DOCSIS and xPON are different access technologies with different physical and control-plane termination systems. That explains a DIFFERENT scenario: A wholesale provider expects DOCSIS cable access equipment to terminate xPON optical network units and finds that provisioning never completes. The mechanism to prioritize for this question is: Fronthaul and midhaul segments have stringent timing and delay requirements that differ from generic broadband service transport.

B:

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: Fronthaul and midhaul segments have stringent timing and delay requirements that differ from generic broadband service transport.

C:

URL query strings can leak reusable secrets through access logs and monitoring systems. That explains a DIFFERENT scenario: A configuration pipeline invokes router REST APIs with bearer tokens embedded in URL parameters, which are copied into proxy logs. The mechanism to prioritize for this question is: Fronthaul and midhaul segments have stringent timing and delay requirements that differ from generic broadband service transport.

Question 136

For a mobile packet-core transport operator, the change record describes: 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. What preventive validation should be standard?

  1. Revalidate transport budgets whenever a radio site or functional split is changed.
  2. Maintain an inventory of per-hop encapsulation support and interworking validation tests.
  3. Check subscriber access-media type before selecting aggregation hardware and automation profiles.
  4. Require peer and prefix authorization and monitor FlowSpec rule impacts.

Explanation

Correct Answer

A:

Revalidate transport budgets whenever a radio site or functional split is changed. This helps prevent recurrence of the 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. Acceptance evidence should be: Synthetic timing and delay tests remain within the RAN interface limits at full traffic load.

Incorrect Answers

B:

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: Revalidate transport budgets whenever a radio site or functional split is changed.

C:

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: Revalidate transport budgets whenever a radio site or functional split is changed.

D:

Require peer and prefix authorization and monitor FlowSpec rule impacts. That is a sensible control for ANOTHER scenario: A route server receives a new FlowSpec route and applies a blanket drop to an entire customer prefix without checking the match and validation policy. It is less targeted to this issue than: Revalidate transport budgets whenever a radio site or functional split is changed.

Question 137

For a managed VPN service carrier, the failure is: An engineer assumes a process restart on an IOS XR control-plane node always reloads the entire router, causing an unnecessary maintenance outage. Which authorized correction best addresses it?

  1. Identify the running IOS XR platform and follow its supported installation and operational command workflow.
  2. Use the supported IOS XE software installation workflow for the platform and validate active package and boot state.
  3. Use supported IOS XR process or application recovery procedures and verify expected route-processing behavior without a blanket chassis reload.
  4. Transmit the documented token through protected authorization headers over TLS and revoke any logged credentials.

Explanation

Correct Answer

C:

Use supported IOS XR process or application recovery procedures and verify expected route-processing behavior without a blanket chassis reload. This directly addresses the fictional service-provider network case: An engineer assumes a process restart on an IOS XR control-plane node always reloads the entire router, causing an unnecessary maintenance outage. The technical mechanism is: Modular network operating systems may isolate process failures from overall forwarding and supervisor availability. Verify success by: A controlled process test restores the affected service while unrelated line-card forwarding remains stable where supported.

Incorrect Answers

A:

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: An engineer assumes a process restart on an IOS XR control-plane node always reloads the entire router, causing an unnecessary maintenance outage.

B:

Use the supported IOS XE software installation workflow for the platform and validate active package and boot state. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: An engineer assumes a process restart on an IOS XR control-plane node always reloads the entire router, causing an unnecessary maintenance outage.

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: An engineer assumes a process restart on an IOS XR control-plane node always reloads the entire router, causing an unnecessary maintenance outage.

Question 138

After fixing the following network problem, what should the team verify: An engineer assumes a process restart on an IOS XR control-plane node always reloads the entire router, causing an unnecessary maintenance outage.

  1. Reload verification shows the expected version and package status with the previous image available for controlled rollback.
  2. Software inventory and install-state readback confirm the intended package activation on the correct operating system.
  3. The legitimate adjacent session remains established while a distant test source with unsuitable TTL is rejected.
  4. A controlled process test restores the affected service while unrelated line-card forwarding remains stable where supported.

Explanation

Correct Answer

D:

A controlled process test restores the affected service while unrelated line-card forwarding remains stable where supported. This confirms the approved response: Use supported IOS XR process or application recovery procedures and verify expected route-processing behavior without a blanket chassis reload. It is relevant because: Modular network operating systems may isolate process failures from overall forwarding and supervisor availability.

Incorrect Answers

A:

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: Use supported IOS XR process or application recovery procedures and verify expected route-processing behavior without a blanket chassis reload.

B:

Software inventory and install-state readback confirm the intended package activation on the correct operating system. This would validate ANOTHER scenario: A technician deploys IOS XE package commands to an IOS XR route processor, then misinterprets the command rejection as a missing license. The specific correction here is: Use supported IOS XR process or application recovery procedures and verify expected route-processing behavior without a blanket chassis reload.

C:

The legitimate adjacent session remains established while a distant test source with unsuitable TTL is rejected. This would validate ANOTHER scenario: A BGP session from an adjacent PE can be spoofed by packets arriving many router hops away because the provider leaves TTL-security disabled. The specific correction here is: Use supported IOS XR process or application recovery procedures and verify expected route-processing behavior without a blanket chassis reload.

Question 139

A carrier root-cause review considers: An engineer assumes a process restart on an IOS XR control-plane node always reloads the entire router, causing an unnecessary maintenance outage. What underlying mechanism explains this?

  1. Modular network operating systems may isolate process failures from overall forwarding and supervisor availability.
  2. Cisco IOS software families have different feature and programmability interfaces despite overlapping CLI conventions.
  3. Boot configuration and package activation must match the software installation mode for the given IOS XE platform.
  4. MPLS QoS models determine how label traffic class and customer IP markings interact across provider boundaries.

Explanation

Correct Answer

A:

Modular network operating systems may isolate process failures from overall forwarding and supervisor availability. This explains the investigated issue: An engineer assumes a process restart on an IOS XR control-plane node always reloads the entire router, causing an unnecessary maintenance outage. The approved corrective response is: Use supported IOS XR process or application recovery procedures and verify expected route-processing behavior without a blanket chassis reload.

Incorrect Answers

B:

Cisco IOS software families have different feature and programmability interfaces despite overlapping CLI conventions. That explains a DIFFERENT scenario: A mixed fleet automation job expects an IOS XE NETCONF configuration schema to map identically to all classic IOS software releases. The mechanism to prioritize for this question is: Modular network operating systems may isolate process failures from overall forwarding and supervisor availability.

C:

Boot configuration and package activation must match the software installation mode for the given IOS XE platform. That explains a DIFFERENT 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 mechanism to prioritize for this question is: Modular network operating systems may isolate process failures from overall forwarding and supervisor availability.

D:

MPLS QoS models determine how label traffic class and customer IP markings interact across provider boundaries. That explains a DIFFERENT scenario: A provider carries a customer's EF-marked voice traffic across an MPLS core but rewrites both customer DSCP and MPLS EXP indiscriminately, breaking the promised QoS trust boundary. The mechanism to prioritize for this question is: Modular network operating systems may isolate process failures from overall forwarding and supervisor availability.

Question 140

After addressing: An engineer assumes a process restart on an IOS XR control-plane node always reloads the entire router, causing an unnecessary maintenance outage. Which recurring service assurance check is most useful?

  1. Include platform and release detection before network software maintenance automation.
  2. Document process-level recovery and escalation criteria separately from full reload procedures.
  3. Require postboot image attestation and rollback readiness in change acceptance.
  4. Include negative marking tests at each new customer UNI.

Explanation

Correct Answer

B:

Document process-level recovery and escalation criteria separately from full reload procedures. This helps prevent recurrence of the issue: An engineer assumes a process restart on an IOS XR control-plane node always reloads the entire router, causing an unnecessary maintenance outage. Acceptance evidence should be: A controlled process test restores the affected service while unrelated line-card forwarding remains stable where supported.

Incorrect Answers

A:

Include platform and release detection before network software maintenance automation. That is a sensible control for ANOTHER scenario: A technician deploys IOS XE package commands to an IOS XR route processor, then misinterprets the command rejection as a missing license. It is less targeted to this issue than: Document process-level recovery and escalation criteria separately from full reload procedures.

C:

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: Document process-level recovery and escalation criteria separately from full reload procedures.

D:

Include negative marking tests at each new customer UNI. That is a sensible control for ANOTHER scenario: A customer sends traffic already marked high priority and an access PE trusts every DSCP value, letting uncontracted backups crowd out voice queues. It is less targeted to this issue than: Document process-level recovery and escalation criteria separately from full reload procedures.