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 64

Question 630

Following a supported configuration correction, the original issue was: An OSPFv3 deployment uses a link-local neighbor address and the monitoring system mistakenly treats it as globally reachable offlink for management. Which observation verifies success?

  1. Valid component destinations work and an unassigned prefix does not loop indefinitely.
  2. OSPF neighbors reach Full with consistent hellos and the BGP session subsequently obtains IGP reachability.
  3. Peering remains healthy and management attempts use a routable endpoint instead of a bare link-local address.
  4. The eBGP FSM reaches Established and the peer's AS is recorded correctly.

Explanation

Correct Answer

C:

Peering remains healthy and management attempts use a routable endpoint instead of a bare link-local address. This confirms the approved response: Separate OSPFv3 neighbor link-local scope from globally routed management addresses and preserve interface context. It is relevant because: IPv6 link-local addresses are scoped to their link and need an interface scope when referenced locally.

Incorrect Answers

A:

Valid component destinations work and an unassigned prefix does not loop indefinitely. This would validate ANOTHER scenario: An ABR summarizes branch routes into one large prefix that points into an area missing part of the address space, leading to a forwarding loop for unallocated addresses. The specific correction here is: Separate OSPFv3 neighbor link-local scope from globally routed management addresses and preserve interface context.

B:

OSPF neighbors reach Full with consistent hellos and the BGP session subsequently obtains IGP reachability. This would validate ANOTHER scenario: Two OSPF routers connected through an L2VPN are configured with incompatible hello/dead timers and a monitoring dashboard calls the missing adjacency a BGP failure. The specific correction here is: Separate OSPFv3 neighbor link-local scope from globally routed management addresses and preserve interface context.

D:

The eBGP FSM reaches Established and the peer's AS is recorded correctly. This would validate ANOTHER scenario: A new eBGP handoff establishes TCP transport but remains Idle/Active because the peer configuration uses the wrong autonomous-system number. The specific correction here is: Separate OSPFv3 neighbor link-local scope from globally routed management addresses and preserve interface context.

Question 631

At a metro Ethernet service provider, an engineer examines: An OSPFv3 deployment uses a link-local neighbor address and the monitoring system mistakenly treats it as globally reachable offlink for management. Which technical principle is most applicable?

  1. OSPF auto-cost derives from a configurable reference bandwidth and can underdifferentiate fast interfaces.
  2. OSPFv3 control adjacency does not guarantee a route is installed in every VRF or address family.
  3. Local preference is an AS-wide policy attribute typically considered before AS_PATH length.
  4. IPv6 link-local addresses are scoped to their link and need an interface scope when referenced locally.

Explanation

Correct Answer

D:

IPv6 link-local addresses are scoped to their link and need an interface scope when referenced locally. This explains the investigated issue: An OSPFv3 deployment uses a link-local neighbor address and the monitoring system mistakenly treats it as globally reachable offlink for management. The approved corrective response is: Separate OSPFv3 neighbor link-local scope from globally routed management addresses and preserve interface context.

Incorrect Answers

A:

OSPF auto-cost derives from a configurable reference bandwidth and can underdifferentiate fast interfaces. That explains a DIFFERENT scenario: A customer circuit has high latency but OSPF chooses it over the primary because reference bandwidth was never updated for modern high-speed links. The mechanism to prioritize for this question is: IPv6 link-local addresses are scoped to their link and need an interface scope when referenced locally.

B:

OSPFv3 control adjacency does not guarantee a route is installed in every VRF or address family. That explains a DIFFERENT scenario: An OSPFv3 adjacency is up but IPv6 routes are absent because the required address-family instance is missing from the receiving VRF. The mechanism to prioritize for this question is: IPv6 link-local addresses are scoped to their link and need an interface scope when referenced locally.

C:

Local preference is an AS-wide policy attribute typically considered before AS_PATH length. That explains a DIFFERENT scenario: A carrier's inbound customer route has local preference 200 but another exit's route has a shorter AS_PATH, and the team incorrectly expects the short path to win. The mechanism to prioritize for this question is: IPv6 link-local addresses are scoped to their link and need an interface scope when referenced locally.

Question 632

For a metro Ethernet service provider, the change record describes: An OSPFv3 deployment uses a link-local neighbor address and the monitoring system mistakenly treats it as globally reachable offlink for management. What preventive validation should be standard?

  1. Record the correct address scope for OSPF and management telemetry.
  2. Validate area-type consistency before enabling stub policy.
  3. Revalidate summaries against the address plan after branch network changes.
  4. Audit port-block assignments and exhausted mapping pools.

Explanation

Correct Answer

A:

Record the correct address scope for OSPF and management telemetry. This helps prevent recurrence of the issue: An OSPFv3 deployment uses a link-local neighbor address and the monitoring system mistakenly treats it as globally reachable offlink for management. Acceptance evidence should be: Peering remains healthy and management attempts use a routable endpoint instead of a bare link-local address.

Incorrect Answers

B:

Validate area-type consistency before enabling stub policy. That is a sensible control for ANOTHER scenario: An OSPF stub area loses its expected default route when an engineer configures stub mode on the access router but not consistently on the area border router. It is less targeted to this issue than: Record the correct address scope for OSPF and management telemetry.

C:

Revalidate summaries against the address plan after branch network changes. That is a sensible control for ANOTHER scenario: An ABR summarizes branch routes into one large prefix that points into an area missing part of the address space, leading to a forwarding loop for unallocated addresses. It is less targeted to this issue than: Record the correct address scope for OSPF and management telemetry.

D:

Audit port-block assignments and exhausted mapping pools. That is a sensible control for ANOTHER scenario: An ISP assigns customer IPv4 address blocks through CGNAT but configures identical port-set mappings on two subscribers behind the same public address, causing connection collisions. It is less targeted to this issue than: Record the correct address scope for OSPF and management telemetry.

Question 633

For a global tier-one IP transit carrier, the failure is: An IPv6 border router accepts an IPv6 customer route under an IPv4 route-policy address-family clause and quietly blocks legitimate IPv6 service NLRI. Which authorized correction best addresses it?

  1. Activate the IPv6 unicast address family and required export policies on both intended peers.
  2. Validate PIC support, alternate paths and recursion so the forwarding plane can preinstall backup resolution where supported.
  3. Bind the correct IPv6 address-family policy and prefix filters to the matching BGP neighbor family.
  4. Preserve and transmit the negotiated community using the supported neighbor settings and route policy.

Explanation

Correct Answer

C:

Bind the correct IPv6 address-family policy and prefix filters to the matching BGP neighbor family. This directly addresses the fictional service-provider network case: An IPv6 border router accepts an IPv6 customer route under an IPv4 route-policy address-family clause and quietly blocks legitimate IPv6 service NLRI. The technical mechanism is: MP-BGP address families have separate route policies and prefix syntax even when sessions share a neighbor. Verify success by: A permitted IPv6 test prefix appears while an unapproved wider prefix remains denied.

Incorrect Answers

A:

Activate the IPv6 unicast address family and required export policies on both intended peers. This would respond to a DIFFERENT fictional service-provider network issue: A carrier activates an IPv6-only peering exchange but leaves only IPv4 unicast activated, so the BGP session is Established yet receives no IPv6 prefixes. It does not directly address the current situation: An IPv6 border router accepts an IPv6 customer route under an IPv4 route-policy address-family clause and quietly blocks legitimate IPv6 service NLRI.

B:

Validate PIC support, alternate paths and recursion so the forwarding plane can preinstall backup resolution where supported. This would respond to a DIFFERENT fictional service-provider network issue: A provider enables BGP PIC in its core but expects instant convergence even though recursive alternate next hops were not installed for the affected VPN prefixes. It does not directly address the current situation: An IPv6 border router accepts an IPv6 customer route under an IPv4 route-policy address-family clause and quietly blocks legitimate IPv6 service NLRI.

D:

Preserve and transmit the negotiated community using the supported neighbor settings and route policy. This would respond to a DIFFERENT fictional service-provider network issue: A provider uses BGP community 65000:123 as a traffic-engineering signal but one edge strips communities on eBGP export, so the upstream never applies the requested policy. It does not directly address the current situation: An IPv6 border router accepts an IPv6 customer route under an IPv4 route-policy address-family clause and quietly blocks legitimate IPv6 service NLRI.

Question 634

After fixing the following network problem, what should the team verify: An IPv6 border router accepts an IPv6 customer route under an IPv4 route-policy address-family clause and quietly blocks legitimate IPv6 service NLRI.

  1. Lab inbound path attributes show the prepend toward an upstream while the local routing policy sets the expected outbound exit.
  2. The eBGP FSM reaches Established and the peer's AS is recorded correctly.
  3. IPv6 prefixes appear in the target VRF while unrelated global tables remain unchanged.
  4. A permitted IPv6 test prefix appears while an unapproved wider prefix remains denied.

Explanation

Correct Answer

D:

A permitted IPv6 test prefix appears while an unapproved wider prefix remains denied. This confirms the approved response: Bind the correct IPv6 address-family policy and prefix filters to the matching BGP neighbor family. It is relevant because: MP-BGP address families have separate route policies and prefix syntax even when sessions share a neighbor.

Incorrect Answers

A:

Lab inbound path attributes show the prepend toward an upstream while the local routing policy sets the expected outbound exit. This would validate ANOTHER scenario: A multihomed service-provider customer advertises a /24 prefix with multiple AS prepends yet expects the prepend to influence its own outbound preferred exit. The specific correction here is: Bind the correct IPv6 address-family policy and prefix filters to the matching BGP neighbor family.

B:

The eBGP FSM reaches Established and the peer's AS is recorded correctly. This would validate ANOTHER scenario: A new eBGP handoff establishes TCP transport but remains Idle/Active because the peer configuration uses the wrong autonomous-system number. The specific correction here is: Bind the correct IPv6 address-family policy and prefix filters to the matching BGP neighbor family.

C:

IPv6 prefixes appear in the target VRF while unrelated global tables remain unchanged. This would validate ANOTHER scenario: An OSPFv3 adjacency is up but IPv6 routes are absent because the required address-family instance is missing from the receiving VRF. The specific correction here is: Bind the correct IPv6 address-family policy and prefix filters to the matching BGP neighbor family.

Question 635

A carrier root-cause review considers: An IPv6 border router accepts an IPv6 customer route under an IPv4 route-policy address-family clause and quietly blocks legitimate IPv6 service NLRI. What underlying mechanism explains this?

  1. MP-BGP address families have separate route policies and prefix syntax even when sessions share a neighbor.
  2. AS-path prepending primarily affects external systems' route preference and not necessarily an AS's own egress selection.
  3. BGP session establishment is distinct from activation of a specific MP-BGP address family.
  4. Dual-Stack Lite transports IPv4 traffic over IPv6 access to a carrier AFTR performing shared IPv4 translation.

Explanation

Correct Answer

A:

MP-BGP address families have separate route policies and prefix syntax even when sessions share a neighbor. This explains the investigated issue: An IPv6 border router accepts an IPv6 customer route under an IPv4 route-policy address-family clause and quietly blocks legitimate IPv6 service NLRI. The approved corrective response is: Bind the correct IPv6 address-family policy and prefix filters to the matching BGP neighbor family.

Incorrect Answers

B:

AS-path prepending primarily affects external systems' route preference and not necessarily an AS's own egress selection. That explains a DIFFERENT scenario: A multihomed service-provider customer advertises a /24 prefix with multiple AS prepends yet expects the prepend to influence its own outbound preferred exit. The mechanism to prioritize for this question is: MP-BGP address families have separate route policies and prefix syntax even when sessions share a neighbor.

C:

BGP session establishment is distinct from activation of a specific MP-BGP address family. That explains a DIFFERENT scenario: A carrier activates an IPv6-only peering exchange but leaves only IPv4 unicast activated, so the BGP session is Established yet receives no IPv6 prefixes. The mechanism to prioritize for this question is: MP-BGP address families have separate route policies and prefix syntax even when sessions share a neighbor.

D:

Dual-Stack Lite transports IPv4 traffic over IPv6 access to a carrier AFTR performing shared IPv4 translation. That explains a DIFFERENT scenario: A customer uses DS-Lite but expects its home CPE to perform normal IPv4 public-NAT termination locally, and the B4 tunnel is never provisioned. The mechanism to prioritize for this question is: MP-BGP address families have separate route policies and prefix syntax even when sessions share a neighbor.

Question 636

After addressing: An IPv6 border router accepts an IPv6 customer route under an IPv4 route-policy address-family clause and quietly blocks legitimate IPv6 service NLRI. Which recurring service assurance check is most useful?

  1. Record upstream acceptance of traffic-engineering communities and MED policy.
  2. Verify v4 and v6 filter family independently during peering certification.
  3. Identify traffic direction for each BGP tuning ticket.
  4. Test protocol instance, VRF and AF together in route acceptance.

Explanation

Correct Answer

B:

Verify v4 and v6 filter family independently during peering certification. This helps prevent recurrence of the issue: An IPv6 border router accepts an IPv6 customer route under an IPv4 route-policy address-family clause and quietly blocks legitimate IPv6 service NLRI. Acceptance evidence should be: A permitted IPv6 test prefix appears while an unapproved wider prefix remains denied.

Incorrect Answers

A:

Record upstream acceptance of traffic-engineering communities and MED policy. That is a sensible control for ANOTHER scenario: A provider changes MED inbound on one customer edge and expects all distant autonomous systems to prefer that link for inbound traffic. It is less targeted to this issue than: Verify v4 and v6 filter family independently during peering certification.

C:

Identify traffic direction for each BGP tuning ticket. That is a sensible control for ANOTHER scenario: A multihomed service-provider customer advertises a /24 prefix with multiple AS prepends yet expects the prepend to influence its own outbound preferred exit. It is less targeted to this issue than: Verify v4 and v6 filter family independently during peering certification.

D:

Test protocol instance, VRF and AF together in route acceptance. That is a sensible control for ANOTHER scenario: An OSPFv3 adjacency is up but IPv6 routes are absent because the required address-family instance is missing from the receiving VRF. It is less targeted to this issue than: Verify v4 and v6 filter family independently during peering certification.

Question 637

A provider backbone escalation identifies: A policy deployer overwrites an existing RPL route policy in production without a prechange candidate diff, causing accidental withdrawal of one customer aggregate. What should the network team implement?

  1. Separate service VRF import/export route targets from public internet BGP policy and validate permitted NLRI.
  2. Express the correct prefix-set length condition for the desired more-specific NLRI and bound it to the intended neighbor.
  3. Verify IS-IS IPv6 address family and multitopology participation on all transit adjacencies along the route.
  4. Generate a reviewed intended-state diff and test representative prefixes before committing the revised policy.

Explanation

Correct Answer

D:

Generate a reviewed intended-state diff and test representative prefixes before committing the revised policy. This directly addresses the fictional service-provider network case: A policy deployer overwrites an existing RPL route policy in production without a prechange candidate diff, causing accidental withdrawal of one customer aggregate. The technical mechanism is: Safe provider routing policy needs deterministic predeployment validation because small clause changes alter large-scale reachability. Verify success by: A sandbox change shows the aggregate retained and the desired new filter applied before production approval.

Incorrect Answers

A:

Separate service VRF import/export route targets from public internet BGP policy and validate permitted NLRI. This would respond to a DIFFERENT fictional service-provider network issue: A route reflector exports every VRF route to a public transit peer after route targets are reused carelessly in an import policy. It does not directly address the current situation: A policy deployer overwrites an existing RPL route policy in production without a prechange candidate diff, causing accidental withdrawal of one customer aggregate.

B:

Express the correct prefix-set length condition for the desired more-specific NLRI and bound it to the intended neighbor. This would respond to a DIFFERENT fictional service-provider network issue: A route-policy template attempts to match a more-specific /25 by using an exact /24 prefix without a length range, mistakenly accepting only the aggregate. It does not directly address the current situation: A policy deployer overwrites an existing RPL route policy in production without a prechange candidate diff, causing accidental withdrawal of one customer aggregate.

C:

Verify IS-IS IPv6 address family and multitopology participation on all transit adjacencies along the route. This would respond to a DIFFERENT fictional service-provider network issue: An IPv6 service prefix disappears after enabling IS-IS multitopology, and operations only checks the IPv4 SPF database. It does not directly address the current situation: A policy deployer overwrites an existing RPL route policy in production without a prechange candidate diff, causing accidental withdrawal of one customer aggregate.

Question 638

A service-provider operations test targets: A policy deployer overwrites an existing RPL route policy in production without a prechange candidate diff, causing accidental withdrawal of one customer aggregate. Which result is required?

  1. A sandbox change shows the aggregate retained and the desired new filter applied before production approval.
  2. Test prefixes show the tagged route rejected and only approved routes advertised.
  3. The upstream sandbox peer receives the intended community and applies only the agreed action.
  4. During switchover, eligible traffic continues while routing sessions safely reestablish within the timer budget.

Explanation

Correct Answer

A:

A sandbox change shows the aggregate retained and the desired new filter applied before production approval. This confirms the approved response: Generate a reviewed intended-state diff and test representative prefixes before committing the revised policy. It is relevant because: Safe provider routing policy needs deterministic predeployment validation because small clause changes alter large-scale reachability.

Incorrect Answers

B:

Test prefixes show the tagged route rejected and only approved routes advertised. This would validate ANOTHER scenario: A route map denies a tagged customer route but includes a later permit clause matching all prefixes, and operations misinterprets the first match behavior. The specific correction here is: Generate a reviewed intended-state diff and test representative prefixes before committing the revised policy.

C:

The upstream sandbox peer receives the intended community and applies only the agreed action. This would validate ANOTHER scenario: A provider uses BGP community 65000:123 as a traffic-engineering signal but one edge strips communities on eBGP export, so the upstream never applies the requested policy. The specific correction here is: Generate a reviewed intended-state diff and test representative prefixes before committing the revised policy.

D:

During switchover, eligible traffic continues while routing sessions safely reestablish within the timer budget. This would validate ANOTHER scenario: A provider enables graceful restart for BGP but withdraws all forwarding entries immediately after a planned route-processor switchover, ignoring forwarding preservation requirements. The specific correction here is: Generate a reviewed intended-state diff and test representative prefixes before committing the revised policy.

Question 639

A provider troubleshooting note states: A policy deployer overwrites an existing RPL route policy in production without a prechange candidate diff, causing accidental withdrawal of one customer aggregate. Which mechanism is central?

  1. MED usually influences a neighboring AS's choice, whereas local preference influences internal best-path selection.
  2. Safe provider routing policy needs deterministic predeployment validation because small clause changes alter large-scale reachability.
  3. Routing Policy Language statements have defined evaluation semantics and must not be treated as arbitrary ordered ACL entries.
  4. Improper OSPF area summarization can advertise reachability where no specific destination exists.

Explanation

Correct Answer

B:

Safe provider routing policy needs deterministic predeployment validation because small clause changes alter large-scale reachability. This explains the investigated issue: A policy deployer overwrites an existing RPL route policy in production without a prechange candidate diff, causing accidental withdrawal of one customer aggregate. The approved corrective response is: Generate a reviewed intended-state diff and test representative prefixes before committing the revised policy.

Incorrect Answers

A:

MED usually influences a neighboring AS's choice, whereas local preference influences internal best-path selection. That explains a DIFFERENT scenario: An ISP announces the same customer prefix from two sites but a locally configured outbound route map modifies MED instead of local preference, so egress remains unchanged. The mechanism to prioritize for this question is: Safe provider routing policy needs deterministic predeployment validation because small clause changes alter large-scale reachability.

C:

Routing Policy Language statements have defined evaluation semantics and must not be treated as arbitrary ordered ACL entries. That explains a DIFFERENT scenario: An IOS XR route policy applies `pass` before a prefix filter and an engineer expects later reject logic to stop evaluation automatically. The mechanism to prioritize for this question is: Safe provider routing policy needs deterministic predeployment validation because small clause changes alter large-scale reachability.

D:

Improper OSPF area summarization can advertise reachability where no specific destination exists. That explains a DIFFERENT scenario: An ABR summarizes branch routes into one large prefix that points into an area missing part of the address space, leading to a forwarding loop for unallocated addresses. The mechanism to prioritize for this question is: Safe provider routing policy needs deterministic predeployment validation because small clause changes alter large-scale reachability.

Question 640

To prevent recurrence of this provider network issue: A policy deployer overwrites an existing RPL route policy in production without a prechange candidate diff, causing accidental withdrawal of one customer aggregate. Which control should be retained?

  1. Require boundary-prefix tests whenever prefix sets are edited.
  2. Include tagged and untagged candidate routes in route-map test suites.
  3. Archive policy diffs and route-acceptance fixtures with change approvals.
  4. Baseline BFD jitter and loss before setting aggressive detection timers.

Explanation

Correct Answer

C:

Archive policy diffs and route-acceptance fixtures with change approvals. This helps prevent recurrence of the issue: A policy deployer overwrites an existing RPL route policy in production without a prechange candidate diff, causing accidental withdrawal of one customer aggregate. Acceptance evidence should be: A sandbox change shows the aggregate retained and the desired new filter applied before production approval.

Incorrect Answers

A:

Require boundary-prefix tests whenever prefix sets are edited. That is a sensible control for ANOTHER scenario: A route-policy template attempts to match a more-specific /25 by using an exact /24 prefix without a length range, mistakenly accepting only the aggregate. It is less targeted to this issue than: Archive policy diffs and route-acceptance fixtures with change approvals.

B:

Include tagged and untagged candidate routes in route-map test suites. That is a sensible control for ANOTHER scenario: A route map denies a tagged customer route but includes a later permit clause matching all prefixes, and operations misinterprets the first match behavior. It is less targeted to this issue than: Archive policy diffs and route-acceptance fixtures with change approvals.

D:

Baseline BFD jitter and loss before setting aggressive detection timers. That is a sensible control for ANOTHER scenario: A BFD session on a long-haul link uses submillisecond detection and repeatedly declares faults during normal microbursts despite healthy optics. It is less targeted to this issue than: Archive policy diffs and route-acceptance fixtures with change approvals.