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 36

Question 350

A service-provider operations test targets: A bidirectional multicast service accidentally enables ordinary PIM-SM source register processing for a BIDIR group, creating duplicate replication. Which result is required?

  1. Controlled traffic from multiple sources reaches receivers without duplicated registration-path forwarding.
  2. PIM neighbor and multicast route views show RP reachability and correct shared-tree traffic delivery.
  3. One intended DR is elected and the shared LAN emits the expected controlled PIM behavior.
  4. Tagged frame tests map each subscriber VLAN to the intended service and restore the expected egress tag.

Explanation

Correct Answer

A:

Controlled traffic from multiple sources reaches receivers without duplicated registration-path forwarding. This confirms the approved response: Align PIM-BIDIR group range and designated-forwarder/RP behavior for the supported multicast domain. It is relevant because: Bidirectional PIM uses a shared bidirectional tree and forwarding responsibilities different from ordinary PIM-SM source registration.

Incorrect Answers

B:

PIM neighbor and multicast route views show RP reachability and correct shared-tree traffic delivery. This would validate ANOTHER scenario: A PIM-SM receiver router has no route to the configured rendezvous point, and (*,G) state never forms for ASM traffic. The specific correction here is: Align PIM-BIDIR group range and designated-forwarder/RP behavior for the supported multicast domain.

C:

One intended DR is elected and the shared LAN emits the expected controlled PIM behavior. This would validate ANOTHER scenario: Two multicast access routers each act as designated router for the same LAN after a timer mismatch and receivers see repeated source register behavior. The specific correction here is: Align PIM-BIDIR group range and designated-forwarder/RP behavior for the supported multicast domain.

D:

Tagged frame tests map each subscriber VLAN to the intended service and restore the expected egress tag. This would validate ANOTHER scenario: A provider bridges a customer pseudowire into a service where the incoming access VLAN must be rewritten, but the PE maps the customer tag to an unrelated EVC. The specific correction here is: Align PIM-BIDIR group range and designated-forwarder/RP behavior for the supported multicast domain.

Question 351

A provider troubleshooting note states: A bidirectional multicast service accidentally enables ordinary PIM-SM source register processing for a BIDIR group, creating duplicate replication. Which mechanism is central?

  1. Source-Specific Multicast relies on explicit source/group membership signaling rather than any-source group joins.
  2. Bidirectional PIM uses a shared bidirectional tree and forwarding responsibilities different from ordinary PIM-SM source registration.
  3. PIM sparse mode normally uses an RP during rendezvous for Any-Source Multicast groups.
  4. Traffic shaping delays excess traffic to conform to a rate, with behavior shaped by token and queue parameters.

Explanation

Correct Answer

B:

Bidirectional PIM uses a shared bidirectional tree and forwarding responsibilities different from ordinary PIM-SM source registration. This explains the investigated issue: A bidirectional multicast service accidentally enables ordinary PIM-SM source register processing for a BIDIR group, creating duplicate replication. The approved corrective response is: Align PIM-BIDIR group range and designated-forwarder/RP behavior for the supported multicast domain.

Incorrect Answers

A:

Source-Specific Multicast relies on explicit source/group membership signaling rather than any-source group joins. That explains a DIFFERENT scenario: A multicast source sends video to an SSM group, but an access router uses IGMPv2 joins without source specification and receivers see no stream. The mechanism to prioritize for this question is: Bidirectional PIM uses a shared bidirectional tree and forwarding responsibilities different from ordinary PIM-SM source registration.

C:

PIM sparse mode normally uses an RP during rendezvous for Any-Source Multicast groups. That explains a DIFFERENT scenario: A PIM-SM receiver router has no route to the configured rendezvous point, and (*,G) state never forms for ASM traffic. The mechanism to prioritize for this question is: Bidirectional PIM uses a shared bidirectional tree and forwarding responsibilities different from ordinary PIM-SM source registration.

D:

Traffic shaping delays excess traffic to conform to a rate, with behavior shaped by token and queue parameters. That explains a DIFFERENT scenario: A traffic shaper is configured with a committed rate lower than the contracted customer rate and drops bursts even though physical uplink capacity is idle. The mechanism to prioritize for this question is: Bidirectional PIM uses a shared bidirectional tree and forwarding responsibilities different from ordinary PIM-SM source registration.

Question 352

To prevent recurrence of this provider network issue: A bidirectional multicast service accidentally enables ordinary PIM-SM source register processing for a BIDIR group, creating duplicate replication. Which control should be retained?

  1. Test DR state when changing multicast LAN interfaces.
  2. Validate host and router IGMPv3 compatibility before deploying SSM services.
  3. Maintain separate PIM-SM and PIM-BIDIR group-range policies.
  4. Track provider tree membership and packet replication under subscriber growth.

Explanation

Correct Answer

C:

Maintain separate PIM-SM and PIM-BIDIR group-range policies. This helps prevent recurrence of the issue: A bidirectional multicast service accidentally enables ordinary PIM-SM source register processing for a BIDIR group, creating duplicate replication. Acceptance evidence should be: Controlled traffic from multiple sources reaches receivers without duplicated registration-path forwarding.

Incorrect Answers

A:

Test DR state when changing multicast LAN interfaces. That is a sensible control for ANOTHER scenario: Two multicast access routers each act as designated router for the same LAN after a timer mismatch and receivers see repeated source register behavior. It is less targeted to this issue than: Maintain separate PIM-SM and PIM-BIDIR group-range policies.

B:

Validate host and router IGMPv3 compatibility before deploying SSM services. That is a sensible control for ANOTHER scenario: A multicast source sends video to an SSM group, but an access router uses IGMPv2 joins without source specification and receivers see no stream. It is less targeted to this issue than: Maintain separate PIM-SM and PIM-BIDIR group-range policies.

D:

Track provider tree membership and packet replication under subscriber growth. That is a sensible control for ANOTHER scenario: A provider deploys mVPN for an IPTV customer but replicates each source stream individually to every access PE even when a shared provider multicast tree is available. It is less targeted to this issue than: Maintain separate PIM-SM and PIM-BIDIR group-range policies.

Question 353

At a global tier-one IP transit carrier, an engineering review finds: An access policy applies a strict policer to interactive traffic and expects it to smooth bursts like a shaper, resulting in avoidable packet discards. Which change most directly corrects the service problem?

  1. Use shaping where buffering is appropriate or retune policing burst allowances to the intended contract.
  2. Recalculate shaping rate and burst parameters from the service contract and platform queue behavior.
  3. Attach the required egress scheduler and queue policy at each congestible link while retaining correct ingress classification.
  4. Align the configured Inter-AS VPN option and VPN route-label signaling at the authorized provider border nodes.

Explanation

Correct Answer

A:

Use shaping where buffering is appropriate or retune policing burst allowances to the intended contract. This directly addresses the fictional service-provider network case: An access policy applies a strict policer to interactive traffic and expects it to smooth bursts like a shaper, resulting in avoidable packet discards. The technical mechanism is: Policing typically drops or remarks traffic above a threshold, whereas shaping queues traffic to smooth transmission. Verify success by: A test burst within authorized limits traverses with predictable delay and without unnecessary drops.

Incorrect Answers

B:

Recalculate shaping rate and burst parameters from the service contract and platform queue behavior. This would respond to a DIFFERENT fictional service-provider network issue: A traffic shaper is configured with a committed rate lower than the contracted customer rate and drops bursts even though physical uplink capacity is idle. It does not directly address the current situation: An access policy applies a strict policer to interactive traffic and expects it to smooth bursts like a shaper, resulting in avoidable packet discards.

C:

Attach the required egress scheduler and queue policy at each congestible link while retaining correct ingress classification. This would respond to a DIFFERENT fictional service-provider network issue: Two sites use identical DSCP values but only one interface applies a queue scheduler, and the team assumes packet marking alone guarantees bandwidth on both links. It does not directly address the current situation: An access policy applies a strict policer to interactive traffic and expects it to smooth bursts like a shaper, resulting in avoidable packet discards.

D:

Align the configured Inter-AS VPN option and VPN route-label signaling at the authorized provider border nodes. This would respond to a DIFFERENT fictional service-provider network issue: An inter-AS L3VPN reaches the first provider but customer prefixes vanish at the AS boundary because VPNv4 routes and label context are not exchanged under the chosen inter-AS model. It does not directly address the current situation: An access policy applies a strict policer to interactive traffic and expects it to smooth bursts like a shaper, resulting in avoidable packet discards.

Question 354

For a global tier-one IP transit carrier, operators addressed: An access policy applies a strict policer to interactive traffic and expects it to smooth bursts like a shaper, resulting in avoidable packet discards. What is the strongest acceptance evidence?

  1. Peak-load packet captures retain the expected markings and voice delay and loss remain inside the service objective.
  2. A test burst within authorized limits traverses with predictable delay and without unnecessary drops.
  3. During deliberate congestion, both sites show the intended class distribution and measurable queuing behavior.
  4. Customers reach the approved DNS endpoint but cross-customer reachability tests fail.

Explanation

Correct Answer

B:

A test burst within authorized limits traverses with predictable delay and without unnecessary drops. This confirms the approved response: Use shaping where buffering is appropriate or retune policing burst allowances to the intended contract. It is relevant because: Policing typically drops or remarks traffic above a threshold, whereas shaping queues traffic to smooth transmission.

Incorrect Answers

A:

Peak-load packet captures retain the expected markings and voice delay and loss remain inside the service objective. This would validate ANOTHER scenario: A provider classifies customer voice using DSCP EF at ingress but a later output policy remarks it to best effort, causing jitter under congestion. The specific correction here is: Use shaping where buffering is appropriate or retune policing burst allowances to the intended contract.

C:

During deliberate congestion, both sites show the intended class distribution and measurable queuing behavior. This would validate ANOTHER scenario: Two sites use identical DSCP values but only one interface applies a queue scheduler, and the team assumes packet marking alone guarantees bandwidth on both links. The specific correction here is: Use shaping where buffering is appropriate or retune policing burst allowances to the intended contract.

D:

Customers reach the approved DNS endpoint but cross-customer reachability tests fail. This would validate ANOTHER scenario: A shared-services DNS VRF must serve three customer VRFs, but engineers import full customer route tables into the DNS VRF and unintentionally create broad extranet connectivity. The specific correction here is: Use shaping where buffering is appropriate or retune policing burst allowances to the intended contract.

Question 355

Which network protocol or forwarding behavior explains the following issue: An access policy applies a strict policer to interactive traffic and expects it to smooth bursts like a shaper, resulting in avoidable packet discards.

  1. Unbounded strict priority can starve nonpriority classes during persistent overload.
  2. QoS benefits depend on consistent classification, marking and queue treatment across the full path.
  3. Policing typically drops or remarks traffic above a threshold, whereas shaping queues traffic to smooth transmission.
  4. EVPN MAC mobility uses sequence information to resolve competing advertisements for a moving endpoint.

Explanation

Correct Answer

C:

Policing typically drops or remarks traffic above a threshold, whereas shaping queues traffic to smooth transmission. This explains the investigated issue: An access policy applies a strict policer to interactive traffic and expects it to smooth bursts like a shaper, resulting in avoidable packet discards. The approved corrective response is: Use shaping where buffering is appropriate or retune policing burst allowances to the intended contract.

Incorrect Answers

A:

Unbounded strict priority can starve nonpriority classes during persistent overload. That explains a DIFFERENT scenario: A high-volume backup class is placed in the same strict-priority queue as voice, starving the provider's control and ordinary traffic. The mechanism to prioritize for this question is: Policing typically drops or remarks traffic above a threshold, whereas shaping queues traffic to smooth transmission.

B:

QoS benefits depend on consistent classification, marking and queue treatment across the full path. That explains a DIFFERENT scenario: A provider classifies customer voice using DSCP EF at ingress but a later output policy remarks it to best effort, causing jitter under congestion. The mechanism to prioritize for this question is: Policing typically drops or remarks traffic above a threshold, whereas shaping queues traffic to smooth transmission.

D:

EVPN MAC mobility uses sequence information to resolve competing advertisements for a moving endpoint. That explains a DIFFERENT scenario: Two PEs establish BGP EVPN but remote MAC mobility updates are ignored because a device keeps an older sequence number as authoritative. The mechanism to prioritize for this question is: Policing typically drops or remarks traffic above a threshold, whereas shaping queues traffic to smooth transmission.

Question 356

A core network change board wants to avoid: An access policy applies a strict policer to interactive traffic and expects it to smooth bursts like a shaper, resulting in avoidable packet discards. Which ongoing safeguard fits best?

  1. Include untrusted DSCP abuse tests at provider access interfaces.
  2. Record shaper configuration and measured burst response for each access product.
  3. Validate CE route reception, VPN export and remote import as three separate checks.
  4. Compare policer drops and shaper delay under peak burst profiles.

Explanation

Correct Answer

D:

Compare policer drops and shaper delay under peak burst profiles. This helps prevent recurrence of the issue: An access policy applies a strict policer to interactive traffic and expects it to smooth bursts like a shaper, resulting in avoidable packet discards. Acceptance evidence should be: A test burst within authorized limits traverses with predictable delay and without unnecessary drops.

Incorrect Answers

A:

Include untrusted DSCP abuse tests at provider access interfaces. That is a sensible control for ANOTHER scenario: A customer sends traffic marked CS6 from its access port and expects unlimited priority throughout the provider despite not purchasing a network-control service class. It is less targeted to this issue than: Compare policer drops and shaper delay under peak burst profiles.

B:

Record shaper configuration and measured burst response for each access product. That is a sensible control for ANOTHER scenario: A traffic shaper is configured with a committed rate lower than the contracted customer rate and drops bursts even though physical uplink capacity is idle. It is less targeted to this issue than: Compare policer drops and shaper delay under peak burst profiles.

C:

Validate CE route reception, VPN export and remote import as three separate checks. That is a sensible control for ANOTHER scenario: A CE-PE BGP session successfully exchanges routes but a newly provisioned customer VRF has no route targets and none of its routes propagate to distant PEs. It is less targeted to this issue than: Compare policer drops and shaper delay under peak burst profiles.

Question 357

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

  1. Select the documented IOS XR model-driven API and matching YANG operational path with authenticated transport.
  2. Use the supported secured REST API scheme, certificate validation and documented authentication for the management service.
  3. Negotiate or discover the supported YANG model revision per router before composing the RESTCONF edit.
  4. Select the appropriate supported ON_CHANGE subscription for eligible leaves or adjust SAMPLE cadence for counters that need periodic sampling.

Explanation

Correct Answer

B:

Use the supported secured REST API scheme, certificate validation and documented authentication for the management service. This directly addresses the fictional service-provider network case: 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 technical mechanism is: API endpoint transport and authorization constraints are independent of ordinary IP routing reachability. Verify success by: A controlled request succeeds over authenticated TLS while plaintext attempts are rejected.

Incorrect Answers

A:

Select the documented IOS XR model-driven API and matching YANG operational path with authenticated transport. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: 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.

C:

Negotiate or discover the supported YANG model revision per router before composing the RESTCONF edit. This would respond to a DIFFERENT fictional service-provider network issue: A controller deploys a single RESTCONF configuration template to devices running different firmware but fails when one model revision lacks the targeted leaf. It does not directly address the current situation: 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.

D:

Select the appropriate supported ON_CHANGE subscription for eligible leaves or adjust SAMPLE cadence for counters that need periodic sampling. This would respond to a DIFFERENT fictional service-provider network issue: A provider subscribes to a gNMI counter in SAMPLE mode but expects only updates when the value changes, saturating the collector with unnecessary periodic messages. It does not directly address the current situation: 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.

Question 358

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

  1. A read-only fixture returns the correct interface counters without changing running configuration.
  2. A compatibility test only edits leaves present in each device's advertised schema, with unsupported devices safely excluded.
  3. A controlled request succeeds over authenticated TLS while plaintext attempts are rejected.
  4. The targeted interface changes while other interfaces remain byte-for-byte unchanged.

Explanation

Correct Answer

C:

A controlled request succeeds over authenticated TLS while plaintext attempts are rejected. This confirms the approved response: Use the supported secured REST API scheme, certificate validation and documented authentication for the management service. It is relevant because: API endpoint transport and authorization constraints are independent of ordinary IP routing reachability.

Incorrect Answers

A:

A read-only fixture returns the correct interface counters without changing running configuration. This would validate ANOTHER scenario: A provider telemetry collector expects every IOS XR interface state query to use a generic SNMP community string while the device exposes a supported model-driven operational endpoint. The specific correction here is: Use the supported secured REST API scheme, certificate validation and documented authentication for the management service.

B:

A compatibility test only edits leaves present in each device's advertised schema, with unsupported devices safely excluded. This would validate ANOTHER scenario: A controller deploys a single RESTCONF configuration template to devices running different firmware but fails when one model revision lacks the targeted leaf. The specific correction here is: Use the supported secured REST API scheme, certificate validation and documented authentication for the management service.

D:

The targeted interface changes while other interfaces remain byte-for-byte unchanged. This would validate ANOTHER scenario: A YANG list declares an interface name as its key but a RESTCONF update sends a request to the list root without an instance identifier, modifying the wrong scope. The specific correction here is: Use the supported secured REST API scheme, certificate validation and documented authentication for the management service.

Question 359

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

  1. Cisco programmability can expose structured state through NETCONF, RESTCONF or streaming telemetry rather than one universal device protocol.
  2. Model-driven APIs are constrained by actual module and revision support, not just by having an HTTPS listener.
  3. Dial-out telemetry originates at the device, whereas dial-in requires the collector to connect to the device endpoint.
  4. API endpoint transport and authorization constraints are independent of ordinary IP routing reachability.

Explanation

Correct Answer

D:

API endpoint transport and authorization constraints are independent of ordinary IP routing reachability. This explains the investigated issue: 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 approved corrective response is: Use the supported secured REST API scheme, certificate validation and documented authentication for the management service.

Incorrect Answers

A:

Cisco programmability can expose structured state through NETCONF, RESTCONF or streaming telemetry rather than one universal device protocol. That explains a DIFFERENT scenario: A provider telemetry collector expects every IOS XR interface state query to use a generic SNMP community string while the device exposes a supported model-driven operational endpoint. The mechanism to prioritize for this question is: API endpoint transport and authorization constraints are independent of ordinary IP routing reachability.

B:

Model-driven APIs are constrained by actual module and revision support, not just by having an HTTPS listener. That explains a DIFFERENT scenario: A controller deploys a single RESTCONF configuration template to devices running different firmware but fails when one model revision lacks the targeted leaf. The mechanism to prioritize for this question is: API endpoint transport and authorization constraints are independent of ordinary IP routing reachability.

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: API endpoint transport and authorization constraints are independent of ordinary IP routing reachability.

Question 360

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

  1. Validate endpoint scheme, port and trust chain before each API integration rollout.
  2. Discover supported API transports and model revisions during device enrollment.
  3. Track model-capability inventory and regression-test software upgrades.
  4. Require RPC reply and postchange readback checks for configuration jobs.

Explanation

Correct Answer

A:

Validate endpoint scheme, port and trust chain before each API integration rollout. This helps prevent recurrence of the issue: 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. Acceptance evidence should be: A controlled request succeeds over authenticated TLS while plaintext attempts are rejected.

Incorrect Answers

B:

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

C:

Track model-capability inventory and regression-test software upgrades. That is a sensible control for ANOTHER scenario: A controller deploys a single RESTCONF configuration template to devices running different firmware but fails when one model revision lacks the targeted leaf. It is less targeted to this issue than: Validate endpoint scheme, port and trust chain before each API integration rollout.

D:

Require RPC reply and postchange readback checks for configuration jobs. That is a sensible control for ANOTHER scenario: A NETCONF RPC returns an `<rpc-error>` element but a script reports success because the SSH TCP session remained connected. It is less targeted to this issue than: Validate endpoint scheme, port and trust chain before each API integration rollout.