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 15

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.

Question 141

A provider backbone escalation identifies: An NFV cluster oversubscribes CPU cores for a carrier-grade packet gateway, leading to jitter despite abundant average utilization headroom. What should the network team implement?

  1. Use only the supported application-hosting environment with explicit CPU, memory, interface and lifecycle controls.
  2. Reapply the documented VNF connectivity, virtual switching and service-chain attachments on the new NFV infrastructure.
  3. Bind management endpoints to the restricted VRF or access policy and enforce scoped authenticated HTTPS with credential rotation.
  4. Reserve suitable CPU, NUMA and accelerated interface resources for the packet-processing workload based on capacity testing.

Explanation

Correct Answer

D:

Reserve suitable CPU, NUMA and accelerated interface resources for the packet-processing workload based on capacity testing. This directly addresses the fictional service-provider network case: An NFV cluster oversubscribes CPU cores for a carrier-grade packet gateway, leading to jitter despite abundant average utilization headroom. The technical mechanism is: Virtual packet processing can be constrained by scheduling, locality and data-plane I/O well before overall host averages show saturation. Verify success by: Peak-load tests meet packet loss and jitter objectives without unexpected host scheduling contention.

Incorrect Answers

A:

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: An NFV cluster oversubscribes CPU cores for a carrier-grade packet gateway, leading to jitter despite abundant average utilization headroom.

B:

Reapply the documented VNF connectivity, virtual switching and service-chain attachments on the new NFV infrastructure. This would respond to a DIFFERENT fictional service-provider network issue: A service provider moves a virtualized firewall to a new NFV host but neglects to recreate the virtual interfaces and cannot forward subscriber traffic. It does not directly address the current situation: An NFV cluster oversubscribes CPU cores for a carrier-grade packet gateway, leading to jitter despite abundant average utilization headroom.

C:

Bind management endpoints to the restricted VRF or access policy and enforce scoped authenticated HTTPS with credential rotation. This would respond to a DIFFERENT fictional service-provider network issue: A provider's router management API is reachable from the public internet using a broad admin token, even though the operations team uses a dedicated management VRF. It does not directly address the current situation: An NFV cluster oversubscribes CPU cores for a carrier-grade packet gateway, leading to jitter despite abundant average utilization headroom.

Question 142

A service-provider operations test targets: An NFV cluster oversubscribes CPU cores for a carrier-grade packet gateway, leading to jitter despite abundant average utilization headroom. Which result is required?

  1. Peak-load tests meet packet loss and jitter objectives without unexpected host scheduling contention.
  2. A simulated restart restores service with the approved subscriber policy intact.
  3. Test packets traverse each intended virtual function and no alternate path bypasses the security service.
  4. A controlled request succeeds with credentials absent from URLs and audit logs.

Explanation

Correct Answer

A:

Peak-load tests meet packet loss and jitter objectives without unexpected host scheduling contention. This confirms the approved response: Reserve suitable CPU, NUMA and accelerated interface resources for the packet-processing workload based on capacity testing. It is relevant because: Virtual packet processing can be constrained by scheduling, locality and data-plane I/O well before overall host averages show saturation.

Incorrect Answers

B:

A simulated restart restores service with the approved subscriber policy intact. This would validate ANOTHER scenario: A provider stores a VNF configuration exclusively on the ephemeral container filesystem and loses subscriber policy after an orchestrator restarts the instance. The specific correction here is: Reserve suitable CPU, NUMA and accelerated interface resources for the packet-processing workload based on capacity testing.

C:

Test packets traverse each intended virtual function and no alternate path bypasses the security service. This would validate ANOTHER scenario: A service provider moves a virtualized firewall to a new NFV host but neglects to recreate the virtual interfaces and cannot forward subscriber traffic. The specific correction here is: Reserve suitable CPU, NUMA and accelerated interface resources for the packet-processing workload based on capacity testing.

D:

A controlled request succeeds with credentials absent from URLs and audit logs. This would validate ANOTHER scenario: A configuration pipeline invokes router REST APIs with bearer tokens embedded in URL parameters, which are copied into proxy logs. The specific correction here is: Reserve suitable CPU, NUMA and accelerated interface resources for the packet-processing workload based on capacity testing.

Question 143

A provider troubleshooting note states: An NFV cluster oversubscribes CPU cores for a carrier-grade packet gateway, leading to jitter despite abundant average utilization headroom. Which mechanism is central?

  1. A VNF requires both compute execution and correctly bound virtual networking to participate in a forwarding chain.
  2. Virtual packet processing can be constrained by scheduling, locality and data-plane I/O well before overall host averages show saturation.
  3. Application hosting support is platform-specific and competing workloads can impact critical control processes.
  4. LDP peer trust and label distribution are separate controls that should both be scoped in an MPLS core.

Explanation

Correct Answer

B:

Virtual packet processing can be constrained by scheduling, locality and data-plane I/O well before overall host averages show saturation. This explains the investigated issue: An NFV cluster oversubscribes CPU cores for a carrier-grade packet gateway, leading to jitter despite abundant average utilization headroom. The approved corrective response is: Reserve suitable CPU, NUMA and accelerated interface resources for the packet-processing workload based on capacity testing.

Incorrect Answers

A:

A VNF requires both compute execution and correctly bound virtual networking to participate in a forwarding chain. That explains a DIFFERENT scenario: A service provider moves a virtualized firewall to a new NFV host but neglects to recreate the virtual interfaces and cannot forward subscriber traffic. The mechanism to prioritize for this question is: Virtual packet processing can be constrained by scheduling, locality and data-plane I/O well before overall host averages show saturation.

C:

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: Virtual packet processing can be constrained by scheduling, locality and data-plane I/O well before overall host averages show saturation.

D:

LDP peer trust and label distribution are separate controls that should both be scoped in an MPLS core. That explains a DIFFERENT scenario: A provider accepts unbounded remote LDP label mappings from an unexpected neighbor in a shared transport environment. The mechanism to prioritize for this question is: Virtual packet processing can be constrained by scheduling, locality and data-plane I/O well before overall host averages show saturation.

Question 144

To prevent recurrence of this provider network issue: An NFV cluster oversubscribes CPU cores for a carrier-grade packet gateway, leading to jitter despite abundant average utilization headroom. Which control should be retained?

  1. Run restart and rescheduling persistence drills before production upgrade windows.
  2. Include port binding and chain-path readback in migration automation.
  3. Retest compute placement and performance after NFVI scheduler changes.
  4. Exercise RTBH announcements with disposable prefixes and post-event withdrawal checks.

Explanation

Correct Answer

C:

Retest compute placement and performance after NFVI scheduler changes. This helps prevent recurrence of the issue: An NFV cluster oversubscribes CPU cores for a carrier-grade packet gateway, leading to jitter despite abundant average utilization headroom. Acceptance evidence should be: Peak-load tests meet packet loss and jitter objectives without unexpected host scheduling contention.

Incorrect Answers

A:

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: Retest compute placement and performance after NFVI scheduler changes.

B:

Include port binding and chain-path readback in migration automation. That is a sensible control for ANOTHER scenario: A service provider moves a virtualized firewall to a new NFV host but neglects to recreate the virtual interfaces and cannot forward subscriber traffic. It is less targeted to this issue than: Retest compute placement and performance after NFVI scheduler changes.

D:

Exercise RTBH announcements with disposable prefixes and post-event withdrawal checks. That is a sensible control for ANOTHER scenario: A provider triggers RTBH by announcing a route with an incorrect blackhole community, and legitimate subscriber traffic to the target continues to traverse the core. It is less targeted to this issue than: Retest compute placement and performance after NFVI scheduler changes.

Question 145

At an optical transport engineering team, an engineering review finds: A customer sends traffic already marked high priority and an access PE trusts every DSCP value, letting uncontracted backups crowd out voice queues. Which change most directly corrects the service problem?

  1. Classify or remark traffic at the customer-provider handoff according to the contracted class-of-service policy.
  2. Align the DS-TE class type bandwidth model and router reservations with the intended MAM or RDM admission policy.
  3. Apply stable, standards-consistent IPv6 flow-label generation for each flow where used by network load sharing.
  4. Define the Carrier Ethernet E-Line service demarcation and use an appropriate provider Ethernet or pseudowire transport between the designated endpoints.

Explanation

Correct Answer

A:

Classify or remark traffic at the customer-provider handoff according to the contracted class-of-service policy. This directly addresses the fictional service-provider network case: A customer sends traffic already marked high priority and an access PE trusts every DSCP value, letting uncontracted backups crowd out voice queues. The technical mechanism is: QoS trust boundaries prevent arbitrary customer markings from obtaining unlimited provider scheduling priority. Verify success by: A dual-stream test shows only the approved interactive flows receiving reserved priority and bulk transfers using the contracted lower class.

Incorrect Answers

B:

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 customer sends traffic already marked high priority and an access PE trusts every DSCP value, letting uncontracted backups crowd out voice queues.

C:

Apply stable, standards-consistent IPv6 flow-label generation for each flow where used by network load sharing. This would respond to a DIFFERENT fictional service-provider network issue: 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. It does not directly address the current situation: A customer sends traffic already marked high priority and an access PE trusts every DSCP value, letting uncontracted backups crowd out voice queues.

D:

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 customer sends traffic already marked high priority and an access PE trusts every DSCP value, letting uncontracted backups crowd out voice queues.

Question 146

For an optical transport engineering team, operators addressed: A customer sends traffic already marked high priority and an access PE trusts every DSCP value, letting uncontracted backups crowd out voice queues. What is the strongest acceptance evidence?

  1. A packet capture shows one flow retains a consistent label and path selection stabilizes.
  2. A dual-stream test shows only the approved interactive flows receiving reserved priority and bulk transfers using the contracted lower class.
  3. At scale, traffic classes meet their service objectives without requiring one signaling state entry for every subscriber flow.
  4. A lab administrator change creates an attributable record on the healthy collector during primary-server failure.

Explanation

Correct Answer

B:

A dual-stream test shows only the approved interactive flows receiving reserved priority and bulk transfers using the contracted lower class. This confirms the approved response: Classify or remark traffic at the customer-provider handoff according to the contracted class-of-service policy. It is relevant because: QoS trust boundaries prevent arbitrary customer markings from obtaining unlimited provider scheduling priority.

Incorrect Answers

A:

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: Classify or remark traffic at the customer-provider handoff according to the contracted class-of-service policy.

C:

At scale, traffic classes meet their service objectives without requiring one signaling state entry for every subscriber flow. This would validate ANOTHER scenario: A designer replaces all DiffServ core queues with per-flow IntServ reservations for millions of broadband sessions, exhausting router control resources. The specific correction here is: Classify or remark traffic at the customer-provider handoff according to the contracted class-of-service policy.

D:

A lab administrator change creates an attributable record on the healthy collector during primary-server failure. This would validate ANOTHER scenario: TACACS+ accounting records disappear after a redundant server failover and the team continues privileged changes with no traceable command logs. The specific correction here is: Classify or remark traffic at the customer-provider handoff according to the contracted class-of-service policy.

Question 147

Which network protocol or forwarding behavior explains the following issue: A customer sends traffic already marked high priority and an access PE trusts every DSCP value, letting uncontracted backups crowd out voice queues.

  1. DiffServ groups traffic into forwarding classes whereas IntServ-style reservation can entail per-flow state.
  2. The IPv6 flow label can help identify related packets for consistent treatment when network devices use it in hashing.
  3. QoS trust boundaries prevent arbitrary customer markings from obtaining unlimited provider scheduling priority.
  4. Source traceback across NAT and provider cores requires cross-device path and translation context.

Explanation

Correct Answer

C:

QoS trust boundaries prevent arbitrary customer markings from obtaining unlimited provider scheduling priority. This explains the investigated issue: A customer sends traffic already marked high priority and an access PE trusts every DSCP value, letting uncontracted backups crowd out voice queues. The approved corrective response is: Classify or remark traffic at the customer-provider handoff according to the contracted class-of-service policy.

Incorrect Answers

A:

DiffServ groups traffic into forwarding classes whereas IntServ-style reservation can entail per-flow state. That explains a DIFFERENT scenario: A designer replaces all DiffServ core queues with per-flow IntServ reservations for millions of broadband sessions, exhausting router control resources. The mechanism to prioritize for this question is: QoS trust boundaries prevent arbitrary customer markings from obtaining unlimited provider scheduling priority.

B:

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: QoS trust boundaries prevent arbitrary customer markings from obtaining unlimited provider scheduling priority.

D:

Source traceback across NAT and provider cores requires cross-device path and translation context. That explains a DIFFERENT scenario: A broadband DDoS traceback requires identifying the real ingress edge but the SOC correlates only NAT-translated destination addresses, losing the source transit path. The mechanism to prioritize for this question is: QoS trust boundaries prevent arbitrary customer markings from obtaining unlimited provider scheduling priority.

Question 148

A core network change board wants to avoid: A customer sends traffic already marked high priority and an access PE trusts every DSCP value, letting uncontracted backups crowd out voice queues. Which ongoing safeguard fits best?

  1. Document DS-TE bandwidth constraints and test admission cases before enabling policy.
  2. Capacity-test classifier, policer and scheduler state before service rollout.
  3. Include platform and release detection before network software maintenance automation.
  4. Include negative marking tests at each new customer UNI.

Explanation

Correct Answer

D:

Include negative marking tests at each new customer UNI. This helps prevent recurrence of the issue: A customer sends traffic already marked high priority and an access PE trusts every DSCP value, letting uncontracted backups crowd out voice queues. Acceptance evidence should be: A dual-stream test shows only the approved interactive flows receiving reserved priority and bulk transfers using the contracted lower class.

Incorrect Answers

A:

Document DS-TE bandwidth constraints and test admission cases before enabling policy. That is a sensible control for ANOTHER scenario: A transport planner provisions an RSVP bandwidth pool using MAM assumptions but the network is configured for RDM, causing unexpected class bandwidth borrowing. It is less targeted to this issue than: Include negative marking tests at each new customer UNI.

B:

Capacity-test classifier, policer and scheduler state before service rollout. That is a sensible control for ANOTHER scenario: A designer replaces all DiffServ core queues with per-flow IntServ reservations for millions of broadband sessions, exhausting router control resources. It is less targeted to this issue than: Include negative marking tests at each new customer UNI.

C:

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: Include negative marking tests at each new customer UNI.

Question 149

A carrier service activation check discovers: A network's IOS XR control processor is overwhelmed by bursts of ICMP and BGP packets after access ACLs are changed, even though the data-plane uplinks are uncongested. Which action best restores the intended behavior?

  1. Validate FlowSpec origin and permitted match components, then install the narrowly approved mitigation action.
  2. Configure supported LPTS or CoPP classifications and policers to protect necessary control traffic without suppressing routing adjacencies.
  3. Restrict LDP discovery, sessions and label allocation using peer authentication and supported label filters.
  4. Coordinate optical restoration and IP-layer convergence objectives using a documented routed-optical failure strategy.

Explanation

Correct Answer

B:

Configure supported LPTS or CoPP classifications and policers to protect necessary control traffic without suppressing routing adjacencies. This directly addresses the fictional service-provider network case: A network's IOS XR control processor is overwhelmed by bursts of ICMP and BGP packets after access ACLs are changed, even though the data-plane uplinks are uncongested. The technical mechanism is: Control-plane policing acts on packets punted to route-processing functions rather than ordinary transit forwarding. Verify success by: Control-plane counters show bounded unwanted traffic while BGP and IGP keepalives continue under a test burst.

Incorrect Answers

A:

Validate FlowSpec origin and permitted match components, then install the narrowly approved mitigation action. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: A network's IOS XR control processor is overwhelmed by bursts of ICMP and BGP packets after access ACLs are changed, even though the data-plane uplinks are uncongested.

C:

Restrict LDP discovery, sessions and label allocation using peer authentication and supported label filters. This would respond to a DIFFERENT fictional service-provider network issue: A provider accepts unbounded remote LDP label mappings from an unexpected neighbor in a shared transport environment. It does not directly address the current situation: A network's IOS XR control processor is overwhelmed by bursts of ICMP and BGP packets after access ACLs are changed, even though the data-plane uplinks are uncongested.

D:

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 network's IOS XR control processor is overwhelmed by bursts of ICMP and BGP packets after access ACLs are changed, even though the data-plane uplinks are uncongested.

Question 150

Following a supported configuration correction, the original issue was: A network's IOS XR control processor is overwhelmed by bursts of ICMP and BGP packets after access ACLs are changed, even though the data-plane uplinks are uncongested. Which observation verifies success?

  1. In a benign test, only the intended attack tuple is filtered and legitimate same-prefix traffic continues.
  2. Authorized neighbors exchange the intended FEC labels while an unapproved router cannot create a usable session.
  3. Control-plane counters show bounded unwanted traffic while BGP and IGP keepalives continue under a test burst.
  4. A simulated restart restores service with the approved subscriber policy intact.

Explanation

Correct Answer

C:

Control-plane counters show bounded unwanted traffic while BGP and IGP keepalives continue under a test burst. This confirms the approved response: Configure supported LPTS or CoPP classifications and policers to protect necessary control traffic without suppressing routing adjacencies. It is relevant because: Control-plane policing acts on packets punted to route-processing functions rather than ordinary transit forwarding.

Incorrect Answers

A:

In a benign test, only the intended attack tuple is filtered and legitimate same-prefix traffic continues. This would validate 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. The specific correction here is: Configure supported LPTS or CoPP classifications and policers to protect necessary control traffic without suppressing routing adjacencies.

B:

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: Configure supported LPTS or CoPP classifications and policers to protect necessary control traffic without suppressing routing adjacencies.

D:

A simulated restart restores service with the approved subscriber policy intact. This would validate ANOTHER scenario: A provider stores a VNF configuration exclusively on the ephemeral container filesystem and loses subscriber policy after an orchestrator restarts the instance. The specific correction here is: Configure supported LPTS or CoPP classifications and policers to protect necessary control traffic without suppressing routing adjacencies.