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 42

Question 410

After fixing the following network problem, what should the team verify: 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.

  1. Captures before and after the provider domain show expected outer traffic-class values and preserved customer DSCP when specified.
  2. A dual-stream test shows only the approved interactive flows receiving reserved priority and bulk transfers using the contracted lower class.
  3. A controlled traffic simulation identifies the correct ingress interface and mapped subscriber session without exposing unrelated customers.
  4. A packet capture shows one flow retains a consistent label and path selection stabilizes.

Explanation

Correct Answer

D:

A packet capture shows one flow retains a consistent label and path selection stabilizes. This confirms the approved response: Apply stable, standards-consistent IPv6 flow-label generation for each flow where used by network load sharing. It is relevant because: The IPv6 flow label can help identify related packets for consistent treatment when network devices use it in hashing.

Incorrect Answers

A:

Captures before and after the provider domain show expected outer traffic-class values and preserved customer DSCP when specified. This would validate ANOTHER 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 specific correction here is: Apply stable, standards-consistent IPv6 flow-label generation for each flow where used by network load sharing.

B:

A dual-stream test shows only the approved interactive flows receiving reserved priority and bulk transfers using the contracted lower class. This would validate 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. The specific correction here is: Apply stable, standards-consistent IPv6 flow-label generation for each flow where used by network load sharing.

C:

A controlled traffic simulation identifies the correct ingress interface and mapped subscriber session without exposing unrelated customers. This would validate ANOTHER 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 specific correction here is: Apply stable, standards-consistent IPv6 flow-label generation for each flow where used by network load sharing.

Question 411

A carrier root-cause review considers: 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. What underlying mechanism explains this?

  1. The IPv6 flow label can help identify related packets for consistent treatment when network devices use it in hashing.
  2. DiffServ groups traffic into forwarding classes whereas IntServ-style reservation can entail per-flow state.
  3. QoS trust boundaries prevent arbitrary customer markings from obtaining unlimited provider scheduling priority.
  4. Modular network operating systems may isolate process failures from overall forwarding and supervisor availability.

Explanation

Correct Answer

A:

The IPv6 flow label can help identify related packets for consistent treatment when network devices use it in hashing. This explains the investigated 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. The approved corrective response is: Apply stable, standards-consistent IPv6 flow-label generation for each flow where used by network load sharing.

Incorrect Answers

B:

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: The IPv6 flow label can help identify related packets for consistent treatment when network devices use it in hashing.

C:

QoS trust boundaries prevent arbitrary customer markings from obtaining unlimited provider scheduling priority. That explains a DIFFERENT scenario: A customer sends traffic already marked high priority and an access PE trusts every DSCP value, letting uncontracted backups crowd out voice queues. The mechanism to prioritize for this question is: The IPv6 flow label can help identify related packets for consistent treatment when network devices use it in hashing.

D:

Modular network operating systems may isolate process failures from overall forwarding and supervisor availability. That explains a DIFFERENT scenario: An engineer assumes a process restart on an IOS XR control-plane node always reloads the entire router, causing an unnecessary maintenance outage. The mechanism to prioritize for this question is: The IPv6 flow label can help identify related packets for consistent treatment when network devices use it in hashing.

Question 412

After addressing: 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. Which recurring service assurance check is most useful?

  1. Capacity-test classifier, policer and scheduler state before service rollout.
  2. Verify flow-label behavior during software and hashing-policy upgrades.
  3. Include negative marking tests at each new customer UNI.
  4. Keep flow retention and time synchronization aligned with incident investigation requirements.

Explanation

Correct Answer

B:

Verify flow-label behavior during software and hashing-policy upgrades. This helps prevent recurrence of the 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. Acceptance evidence should be: A packet capture shows one flow retains a consistent label and path selection stabilizes.

Incorrect Answers

A:

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: Verify flow-label behavior during software and hashing-policy upgrades.

C:

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: Verify flow-label behavior during software and hashing-policy upgrades.

D:

Keep flow retention and time synchronization aligned with incident investigation requirements. That is a sensible control for ANOTHER 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. It is less targeted to this issue than: Verify flow-label behavior during software and hashing-policy upgrades.

Question 413

A provider backbone escalation identifies: 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. What should the network team implement?

  1. Configure supported LPTS or CoPP classifications and policers to protect necessary control traffic without suppressing routing adjacencies.
  2. Enable supported BGP Generalized TTL Security Mechanism with an appropriate neighbor distance on the intended peer.
  3. Use the provider's documented RTBH community and next-hop policy with tightly constrained victim prefix scope.
  4. Validate FlowSpec origin and permitted match components, then install the narrowly approved mitigation action.

Explanation

Correct Answer

D:

Validate FlowSpec origin and permitted match components, then install the narrowly approved mitigation action. This directly addresses the fictional service-provider network case: 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 technical mechanism is: BGP FlowSpec can distribute fine-grained traffic-filtering actions that are dangerous if accepted without authorization and specificity. Verify success by: In a benign test, only the intended attack tuple is filtered and legitimate same-prefix traffic continues.

Incorrect Answers

A:

Configure supported LPTS or CoPP classifications and policers to protect necessary control traffic without suppressing routing adjacencies. This would respond to a DIFFERENT fictional service-provider network issue: 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. It does not directly address the current situation: 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.

B:

Enable supported BGP Generalized TTL Security Mechanism with an appropriate neighbor distance on the intended peer. This would respond to a DIFFERENT fictional service-provider network issue: A BGP session from an adjacent PE can be spoofed by packets arriving many router hops away because the provider leaves TTL-security disabled. It does not directly address the current situation: 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.

C:

Use the provider's documented RTBH community and next-hop policy with tightly constrained victim prefix scope. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: 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.

Question 414

A service-provider operations test targets: 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. Which result is required?

  1. In a benign test, only the intended attack tuple is filtered and legitimate same-prefix traffic continues.
  2. The legitimate adjacent session remains established while a distant test source with unsuitable TTL is rejected.
  3. Authorized neighbors exchange the intended FEC labels while an unapproved router cannot create a usable session.
  4. Reload verification shows the expected version and package status with the previous image available for controlled rollback.

Explanation

Correct Answer

A:

In a benign test, only the intended attack tuple is filtered and legitimate same-prefix traffic continues. This confirms the approved response: Validate FlowSpec origin and permitted match components, then install the narrowly approved mitigation action. It is relevant because: BGP FlowSpec can distribute fine-grained traffic-filtering actions that are dangerous if accepted without authorization and specificity.

Incorrect Answers

B:

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: Validate FlowSpec origin and permitted match components, then install the narrowly approved mitigation action.

C:

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: Validate FlowSpec origin and permitted match components, then install the narrowly approved mitigation action.

D:

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: Validate FlowSpec origin and permitted match components, then install the narrowly approved mitigation action.

Question 415

A provider troubleshooting note states: 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. Which mechanism is central?

  1. GTSM uses an expected near-hop TTL to constrain spoofed BGP control traffic.
  2. BGP FlowSpec can distribute fine-grained traffic-filtering actions that are dangerous if accepted without authorization and specificity.
  3. LDP peer trust and label distribution are separate controls that should both be scoped in an MPLS core.
  4. DOCSIS and xPON are different access technologies with different physical and control-plane termination systems.

Explanation

Correct Answer

B:

BGP FlowSpec can distribute fine-grained traffic-filtering actions that are dangerous if accepted without authorization and specificity. This explains the investigated 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. The approved corrective response is: Validate FlowSpec origin and permitted match components, then install the narrowly approved mitigation action.

Incorrect Answers

A:

GTSM uses an expected near-hop TTL to constrain spoofed BGP control traffic. That explains a DIFFERENT 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 mechanism to prioritize for this question is: BGP FlowSpec can distribute fine-grained traffic-filtering actions that are dangerous if accepted without authorization and specificity.

C:

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: BGP FlowSpec can distribute fine-grained traffic-filtering actions that are dangerous if accepted without authorization and specificity.

D:

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: BGP FlowSpec can distribute fine-grained traffic-filtering actions that are dangerous if accepted without authorization and specificity.

Question 416

To prevent recurrence of this 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. Which control should be retained?

  1. Monitor class-specific drops and legitimate protocol health after policy updates.
  2. Audit LDP adjacencies and label allocation policy against topology inventory.
  3. Require peer and prefix authorization and monitor FlowSpec rule impacts.
  4. Verify flow-label behavior during software and hashing-policy upgrades.

Explanation

Correct Answer

C:

Require peer and prefix authorization and monitor FlowSpec rule impacts. This helps prevent recurrence of the 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. Acceptance evidence should be: In a benign test, only the intended attack tuple is filtered and legitimate same-prefix traffic continues.

Incorrect Answers

A:

Monitor class-specific drops and legitimate protocol health after policy updates. That is a sensible control for ANOTHER scenario: 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. It is less targeted to this issue than: Require peer and prefix authorization and monitor FlowSpec rule impacts.

B:

Audit LDP adjacencies and label allocation policy against topology inventory. That is a sensible control for ANOTHER scenario: A provider accepts unbounded remote LDP label mappings from an unexpected neighbor in a shared transport environment. It is less targeted to this issue than: Require peer and prefix authorization and monitor FlowSpec rule impacts.

D:

Verify flow-label behavior during software and hashing-policy upgrades. That is a sensible control for 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. It is less targeted to this issue than: Require peer and prefix authorization and monitor FlowSpec rule impacts.

Question 417

At a managed VPN service carrier, an engineering review finds: A configuration pipeline invokes router REST APIs with bearer tokens embedded in URL parameters, which are copied into proxy logs. Which change most directly corrects the service problem?

  1. Transmit the documented token through protected authorization headers over TLS and revoke any logged credentials.
  2. Bind management endpoints to the restricted VRF or access policy and enforce scoped authenticated HTTPS with credential rotation.
  3. Correlate flow records, interface counters and CGNAT translation logs with synchronized timestamps to locate the ingress.
  4. Configure supported LPTS or CoPP classifications and policers to protect necessary control traffic without suppressing routing adjacencies.

Explanation

Correct Answer

A:

Transmit the documented token through protected authorization headers over TLS and revoke any logged credentials. This directly addresses the fictional service-provider network case: A configuration pipeline invokes router REST APIs with bearer tokens embedded in URL parameters, which are copied into proxy logs. The technical mechanism is: URL query strings can leak reusable secrets through access logs and monitoring systems. Verify success by: A controlled request succeeds with credentials absent from URLs and audit logs.

Incorrect Answers

B:

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: A configuration pipeline invokes router REST APIs with bearer tokens embedded in URL parameters, which are copied into proxy logs.

C:

Correlate flow records, interface counters and CGNAT translation logs with synchronized timestamps to locate the ingress. This would respond to a DIFFERENT fictional service-provider network issue: A broadband DDoS traceback requires identifying the real ingress edge but the SOC correlates only NAT-translated destination addresses, losing the source transit path. It does not directly address the current situation: A configuration pipeline invokes router REST APIs with bearer tokens embedded in URL parameters, which are copied into proxy logs.

D:

Configure supported LPTS or CoPP classifications and policers to protect necessary control traffic without suppressing routing adjacencies. This would respond to a DIFFERENT fictional service-provider network issue: 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. It does not directly address the current situation: A configuration pipeline invokes router REST APIs with bearer tokens embedded in URL parameters, which are copied into proxy logs.

Question 418

For a managed VPN service carrier, operators addressed: A configuration pipeline invokes router REST APIs with bearer tokens embedded in URL parameters, which are copied into proxy logs. What is the strongest acceptance evidence?

  1. External negative tests fail while approved management hosts can read operational data with their assigned roles.
  2. A controlled request succeeds with credentials absent from URLs and audit logs.
  3. A controlled traffic simulation identifies the correct ingress interface and mapped subscriber session without exposing unrelated customers.
  4. Reload verification shows the expected version and package status with the previous image available for controlled rollback.

Explanation

Correct Answer

B:

A controlled request succeeds with credentials absent from URLs and audit logs. This confirms the approved response: Transmit the documented token through protected authorization headers over TLS and revoke any logged credentials. It is relevant because: URL query strings can leak reusable secrets through access logs and monitoring systems.

Incorrect Answers

A:

External negative tests fail while approved management hosts can read operational data with their assigned roles. This would validate ANOTHER scenario: 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. The specific correction here is: Transmit the documented token through protected authorization headers over TLS and revoke any logged credentials.

C:

A controlled traffic simulation identifies the correct ingress interface and mapped subscriber session without exposing unrelated customers. This would validate ANOTHER 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 specific correction here is: Transmit the documented token through protected authorization headers over TLS and revoke any logged credentials.

D:

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: Transmit the documented token through protected authorization headers over TLS and revoke any logged credentials.

Question 419

Which network protocol or forwarding behavior explains the following issue: A configuration pipeline invokes router REST APIs with bearer tokens embedded in URL parameters, which are copied into proxy logs.

  1. Source traceback across NAT and provider cores requires cross-device path and translation context.
  2. Management-plane access must be isolated from subscriber-facing forwarding paths and protected by authorization.
  3. URL query strings can leak reusable secrets through access logs and monitoring systems.
  4. DiffServ groups traffic into forwarding classes whereas IntServ-style reservation can entail per-flow state.

Explanation

Correct Answer

C:

URL query strings can leak reusable secrets through access logs and monitoring systems. This explains the investigated issue: A configuration pipeline invokes router REST APIs with bearer tokens embedded in URL parameters, which are copied into proxy logs. The approved corrective response is: Transmit the documented token through protected authorization headers over TLS and revoke any logged credentials.

Incorrect Answers

A:

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: URL query strings can leak reusable secrets through access logs and monitoring systems.

B:

Management-plane access must be isolated from subscriber-facing forwarding paths and protected by authorization. That explains a DIFFERENT scenario: 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. The mechanism to prioritize for this question is: URL query strings can leak reusable secrets through access logs and monitoring systems.

D:

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: URL query strings can leak reusable secrets through access logs and monitoring systems.

Question 420

A core network change board wants to avoid: A configuration pipeline invokes router REST APIs with bearer tokens embedded in URL parameters, which are copied into proxy logs. Which ongoing safeguard fits best?

  1. Test AAA failure behavior and accounting completeness at scheduled intervals.
  2. Inventory exposed management listeners after each platform upgrade.
  3. Require postboot image attestation and rollback readiness in change acceptance.
  4. Run secret-scanning checks against network automation and management proxy logs.

Explanation

Correct Answer

D:

Run secret-scanning checks against network automation and management proxy logs. This helps prevent recurrence of the issue: A configuration pipeline invokes router REST APIs with bearer tokens embedded in URL parameters, which are copied into proxy logs. Acceptance evidence should be: A controlled request succeeds with credentials absent from URLs and audit logs.

Incorrect Answers

A:

Test AAA failure behavior and accounting completeness at scheduled intervals. That is a sensible control for ANOTHER scenario: TACACS+ accounting records disappear after a redundant server failover and the team continues privileged changes with no traceable command logs. It is less targeted to this issue than: Run secret-scanning checks against network automation and management proxy logs.

B:

Inventory exposed management listeners after each platform upgrade. That is a sensible control for ANOTHER scenario: 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 is less targeted to this issue than: Run secret-scanning checks against network automation and management proxy logs.

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: Run secret-scanning checks against network automation and management proxy logs.