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 58

Question 570

After fixing the following network problem, what should the team verify: BGP flips between two equal candidates because a team ignores the router-id and neighbor-address tie-breakers after all higher-ranked attributes match.

  1. A test route exits through the desired high-local-preference border where both paths are otherwise eligible.
  2. A fixture shows the expected origin-type comparison only after preceding attributes tie.
  3. Peering remains healthy and management attempts use a routable endpoint instead of a bare link-local address.
  4. Candidate traces identify the final tie-breaker and forwarding remains consistent across repeated resets.

Explanation

Correct Answer

D:

Candidate traces identify the final tie-breaker and forwarding remains consistent across repeated resets. This confirms the approved response: Inspect the full deterministic tie-breaking sequence and stabilize the intended export policy if one exit must be preferred. It is relevant because: BGP best-path selection includes deterministic final tie-breakers when major attributes are equal.

Incorrect Answers

A:

A test route exits through the desired high-local-preference border where both paths are otherwise eligible. This would validate ANOTHER 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 specific correction here is: Inspect the full deterministic tie-breaking sequence and stabilize the intended export policy if one exit must be preferred.

B:

A fixture shows the expected origin-type comparison only after preceding attributes tie. This would validate ANOTHER scenario: A BGP router holds multiple valid paths yet chooses an unanticipated route because one path has a smaller origin code, not because of a mistaken community. The specific correction here is: Inspect the full deterministic tie-breaking sequence and stabilize the intended export policy if one exit must be preferred.

C:

Peering remains healthy and management attempts use a routable endpoint instead of a bare link-local address. This would validate ANOTHER scenario: An OSPFv3 deployment uses a link-local neighbor address and the monitoring system mistakenly treats it as globally reachable offlink for management. The specific correction here is: Inspect the full deterministic tie-breaking sequence and stabilize the intended export policy if one exit must be preferred.

Question 571

A carrier root-cause review considers: BGP flips between two equal candidates because a team ignores the router-id and neighbor-address tie-breakers after all higher-ranked attributes match. What underlying mechanism explains this?

  1. BGP best-path selection includes deterministic final tie-breakers when major attributes are equal.
  2. BGP best-path selection compares multiple attributes in a defined order rather than relying solely on IGP metrics.
  3. Local preference is an AS-wide policy attribute typically considered before AS_PATH length.
  4. A physical adjacency can exist without all configured address families exchanging usable reachability.

Explanation

Correct Answer

A:

BGP best-path selection includes deterministic final tie-breakers when major attributes are equal. This explains the investigated issue: BGP flips between two equal candidates because a team ignores the router-id and neighbor-address tie-breakers after all higher-ranked attributes match. The approved corrective response is: Inspect the full deterministic tie-breaking sequence and stabilize the intended export policy if one exit must be preferred.

Incorrect Answers

B:

BGP best-path selection compares multiple attributes in a defined order rather than relying solely on IGP metrics. That explains a DIFFERENT scenario: Two eBGP routes reach the same prefix with equal local preference, but operations assumes a shorter AS_PATH cannot affect selection and blames a metric change. The mechanism to prioritize for this question is: BGP best-path selection includes deterministic final tie-breakers when major attributes are equal.

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: BGP best-path selection includes deterministic final tie-breakers when major attributes are equal.

D:

A physical adjacency can exist without all configured address families exchanging usable reachability. That explains a DIFFERENT scenario: An IS-IS neighbor is Up but the remote IPv6 prefix is missing because the address-family topology was disabled on one transit segment. The mechanism to prioritize for this question is: BGP best-path selection includes deterministic final tie-breakers when major attributes are equal.

Question 572

After addressing: BGP flips between two equal candidates because a team ignores the router-id and neighbor-address tie-breakers after all higher-ranked attributes match. Which recurring service assurance check is most useful?

  1. Compare inbound customer import policy with intended exit preferences.
  2. Avoid using accidental router IDs as a business traffic-engineering policy.
  3. Keep best-path attribute snapshots alongside policy change tickets.
  4. Test deterministic mapping and log lookup as part of CGNAT capacity exercises.

Explanation

Correct Answer

B:

Avoid using accidental router IDs as a business traffic-engineering policy. This helps prevent recurrence of the issue: BGP flips between two equal candidates because a team ignores the router-id and neighbor-address tie-breakers after all higher-ranked attributes match. Acceptance evidence should be: Candidate traces identify the final tie-breaker and forwarding remains consistent across repeated resets.

Incorrect Answers

A:

Compare inbound customer import policy with intended exit preferences. That is a sensible control for ANOTHER 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. It is less targeted to this issue than: Avoid using accidental router IDs as a business traffic-engineering policy.

C:

Keep best-path attribute snapshots alongside policy change tickets. That is a sensible control for ANOTHER scenario: Two eBGP routes reach the same prefix with equal local preference, but operations assumes a shorter AS_PATH cannot affect selection and blames a metric change. It is less targeted to this issue than: Avoid using accidental router IDs as a business traffic-engineering policy.

D:

Test deterministic mapping and log lookup as part of CGNAT capacity exercises. That is a sensible control for ANOTHER scenario: A CGNAT operator has millions of sessions but translation logs record only subscriber private addresses, making legal attribution impossible for shared public IPv4 connections. It is less targeted to this issue than: Avoid using accidental router IDs as a business traffic-engineering policy.

Question 573

A provider backbone escalation identifies: A multihomed service-provider customer advertises a /24 prefix with multiple AS prepends yet expects the prepend to influence its own outbound preferred exit. What should the network team implement?

  1. Bind the correct IPv6 address-family policy and prefix filters to the matching BGP neighbor family.
  2. Activate the IPv6 unicast address family and required export policies on both intended peers.
  3. Generate a reviewed intended-state diff and test representative prefixes before committing the revised policy.
  4. Separate inbound inter-AS path influence via prepending from locally controlled outbound local-preference decisions.

Explanation

Correct Answer

D:

Separate inbound inter-AS path influence via prepending from locally controlled outbound local-preference decisions. This directly addresses the fictional service-provider network case: 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 technical mechanism is: AS-path prepending primarily affects external systems' route preference and not necessarily an AS's own egress selection. Verify success by: Lab inbound path attributes show the prepend toward an upstream while the local routing policy sets the expected outbound exit.

Incorrect Answers

A:

Bind the correct IPv6 address-family policy and prefix filters to the matching BGP neighbor family. This would respond to a DIFFERENT fictional service-provider network 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. It does not directly address the current situation: A multihomed service-provider customer advertises a /24 prefix with multiple AS prepends yet expects the prepend to influence its own outbound preferred exit.

B:

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: A multihomed service-provider customer advertises a /24 prefix with multiple AS prepends yet expects the prepend to influence its own outbound preferred exit.

C:

Generate a reviewed intended-state diff and test representative prefixes before committing the revised policy. This would respond to a DIFFERENT fictional service-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. It does not directly address the current situation: A multihomed service-provider customer advertises a /24 prefix with multiple AS prepends yet expects the prepend to influence its own outbound preferred exit.

Question 574

A service-provider operations test targets: A multihomed service-provider customer advertises a /24 prefix with multiple AS prepends yet expects the prepend to influence its own outbound preferred exit. Which result is required?

  1. Lab inbound path attributes show the prepend toward an upstream while the local routing policy sets the expected outbound exit.
  2. Customer route queries show approved aggregate service routes but no internal infrastructure prefixes.
  3. A lab route count shows approved IPv6 NLRI exchanged without unintended IPv4 injection.
  4. Test prefixes show the tagged route rejected and only approved routes advertised.

Explanation

Correct Answer

A:

Lab inbound path attributes show the prepend toward an upstream while the local routing policy sets the expected outbound exit. This confirms the approved response: Separate inbound inter-AS path influence via prepending from locally controlled outbound local-preference decisions. It is relevant because: AS-path prepending primarily affects external systems' route preference and not necessarily an AS's own egress selection.

Incorrect Answers

B:

Customer route queries show approved aggregate service routes but no internal infrastructure prefixes. This would validate ANOTHER scenario: An edge router injects all OSPF internals into BGP without tagging or policy, exposing infrastructure loopbacks to a customer upstream. The specific correction here is: Separate inbound inter-AS path influence via prepending from locally controlled outbound local-preference decisions.

C:

A lab route count shows approved IPv6 NLRI exchanged without unintended IPv4 injection. This would validate ANOTHER 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 specific correction here is: Separate inbound inter-AS path influence via prepending from locally controlled outbound local-preference decisions.

D:

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: Separate inbound inter-AS path influence via prepending from locally controlled outbound local-preference decisions.

Question 575

A provider troubleshooting note states: A multihomed service-provider customer advertises a /24 prefix with multiple AS prepends yet expects the prepend to influence its own outbound preferred exit. Which mechanism is central?

  1. BGP NLRI can be learned without being installed if the next-hop attribute is unreachable.
  2. AS-path prepending primarily affects external systems' route preference and not necessarily an AS's own egress selection.
  3. BGP Add-Path requires capability agreement and path identifiers to advertise more than one route per NLRI to a peer.
  4. Common BGP best-path algorithms prefer eBGP over iBGP before later tie-breakers such as internal next-hop cost.

Explanation

Correct Answer

B:

AS-path prepending primarily affects external systems' route preference and not necessarily an AS's own egress selection. This explains the investigated issue: 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 approved corrective response is: Separate inbound inter-AS path influence via prepending from locally controlled outbound local-preference decisions.

Incorrect Answers

A:

BGP NLRI can be learned without being installed if the next-hop attribute is unreachable. That explains a DIFFERENT scenario: An iBGP core advertises a prefix with a next hop that access routers cannot resolve, causing BGP routes to be present but inactive. The mechanism to prioritize for this question is: AS-path prepending primarily affects external systems' route preference and not necessarily an AS's own egress selection.

C:

BGP Add-Path requires capability agreement and path identifiers to advertise more than one route per NLRI to a peer. That explains a DIFFERENT scenario: Two route reflectors advertise paths from the same client without Add-Path negotiation, and access PEs see one path even though each reflector knows multiple candidates. The mechanism to prioritize for this question is: AS-path prepending primarily affects external systems' route preference and not necessarily an AS's own egress selection.

D:

Common BGP best-path algorithms prefer eBGP over iBGP before later tie-breakers such as internal next-hop cost. That explains a DIFFERENT scenario: A provider expects an iBGP-learned path to beat an otherwise equal eBGP path simply because the iBGP router has a lower IGP cost to the next hop. The mechanism to prioritize for this question is: AS-path prepending primarily affects external systems' route preference and not necessarily an AS's own egress selection.

Question 576

To prevent recurrence of this provider network issue: A multihomed service-provider customer advertises a /24 prefix with multiple AS prepends yet expects the prepend to influence its own outbound preferred exit. Which control should be retained?

  1. Contract-test BGP import/export with representative community fixtures.
  2. Track Add-Path capabilities and route scale in peering acceptance tests.
  3. Identify traffic direction for each BGP tuning ticket.
  4. Trend prefix counts and alert before capacity thresholds are reached.

Explanation

Correct Answer

C:

Identify traffic direction for each BGP tuning ticket. This helps prevent recurrence of the issue: A multihomed service-provider customer advertises a /24 prefix with multiple AS prepends yet expects the prepend to influence its own outbound preferred exit. Acceptance evidence should be: Lab inbound path attributes show the prepend toward an upstream while the local routing policy sets the expected outbound exit.

Incorrect Answers

A:

Contract-test BGP import/export with representative community fixtures. That is a sensible control for ANOTHER scenario: A core route reflector exports only a subset of service prefixes after a route-policy edit because the import policy unintentionally rejects an entire community group. It is less targeted to this issue than: Identify traffic direction for each BGP tuning ticket.

B:

Track Add-Path capabilities and route scale in peering acceptance tests. That is a sensible control for ANOTHER scenario: Two route reflectors advertise paths from the same client without Add-Path negotiation, and access PEs see one path even though each reflector knows multiple candidates. It is less targeted to this issue than: Identify traffic direction for each BGP tuning ticket.

D:

Trend prefix counts and alert before capacity thresholds are reached. That is a sensible control for ANOTHER scenario: An eBGP exchange reports Established but a contracted prefix is missing because the advertiser rejects it under a maximum-prefix protection threshold. It is less targeted to this issue than: Identify traffic direction for each BGP tuning ticket.

Question 577

At a global tier-one IP transit carrier, an engineering review finds: A route reflector exports every VRF route to a public transit peer after route targets are reused carelessly in an import policy. Which change most directly corrects the service problem?

  1. Separate service VRF import/export route targets from public internet BGP policy and validate permitted NLRI.
  2. Rewrite the route-policy decisions with explicit conditional drops or controlled acceptance according to IOS XR RPL semantics.
  3. Preserve and transmit the negotiated community using the supported neighbor settings and route policy.
  4. Provide supported DNS64 synthesis or an equivalent discovery mechanism consistent with NAT64 deployment.

Explanation

Correct Answer

A:

Separate service VRF import/export route targets from public internet BGP policy and validate permitted NLRI. This directly addresses the fictional service-provider network case: A route reflector exports every VRF route to a public transit peer after route targets are reused carelessly in an import policy. The technical mechanism is: Route targets control VPN route distribution and should not be treated as ordinary public BGP communities. Verify success by: A transit peer receives only global internet prefixes while VPN routes remain in authorized VRFs.

Incorrect Answers

B:

Rewrite the route-policy decisions with explicit conditional drops or controlled acceptance according to IOS XR RPL semantics. This would respond to a DIFFERENT fictional service-provider network issue: An IOS XR route policy applies `pass` before a prefix filter and an engineer expects later reject logic to stop evaluation automatically. It does not directly address the current situation: A route reflector exports every VRF route to a public transit peer after route targets are reused carelessly in an import policy.

C:

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: A route reflector exports every VRF route to a public transit peer after route targets are reused carelessly in an import policy.

D:

Provide supported DNS64 synthesis or an equivalent discovery mechanism consistent with NAT64 deployment. This would respond to a DIFFERENT fictional service-provider network issue: An IPv6-only access service installs NAT64 but does not provide a method to obtain suitable IPv6 destinations for IPv4-only DNS names, so subscribers fail by hostname. It does not directly address the current situation: A route reflector exports every VRF route to a public transit peer after route targets are reused carelessly in an import policy.

Question 578

For a global tier-one IP transit carrier, operators addressed: A route reflector exports every VRF route to a public transit peer after route targets are reused carelessly in an import policy. What is the strongest acceptance evidence?

  1. A sandbox change shows the aggregate retained and the desired new filter applied before production approval.
  2. A transit peer receives only global internet prefixes while VPN routes remain in authorized VRFs.
  3. The upstream sandbox peer receives the intended community and applies only the agreed action.
  4. The selected path follows the expected OSPF cost and remains consistent across neighbors.

Explanation

Correct Answer

B:

A transit peer receives only global internet prefixes while VPN routes remain in authorized VRFs. This confirms the approved response: Separate service VRF import/export route targets from public internet BGP policy and validate permitted NLRI. It is relevant because: Route targets control VPN route distribution and should not be treated as ordinary public BGP communities.

Incorrect Answers

A:

A sandbox change shows the aggregate retained and the desired new filter applied before production approval. This would validate ANOTHER scenario: A policy deployer overwrites an existing RPL route policy in production without a prechange candidate diff, causing accidental withdrawal of one customer aggregate. The specific correction here is: Separate service VRF import/export route targets from public internet BGP policy and validate permitted NLRI.

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: Separate service VRF import/export route targets from public internet BGP policy and validate permitted NLRI.

D:

The selected path follows the expected OSPF cost and remains consistent across neighbors. This would validate ANOTHER 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 specific correction here is: Separate service VRF import/export route targets from public internet BGP policy and validate permitted NLRI.

Question 579

Which network protocol or forwarding behavior explains the following issue: A route reflector exports every VRF route to a public transit peer after route targets are reused carelessly in an import policy.

  1. BGP communities are optional policy metadata and must be explicitly propagated when the design depends on them.
  2. MED usually influences a neighboring AS's choice, whereas local preference influences internal best-path selection.
  3. Route targets control VPN route distribution and should not be treated as ordinary public BGP communities.
  4. Improper OSPF area summarization can advertise reachability where no specific destination exists.

Explanation

Correct Answer

C:

Route targets control VPN route distribution and should not be treated as ordinary public BGP communities. This explains the investigated issue: A route reflector exports every VRF route to a public transit peer after route targets are reused carelessly in an import policy. The approved corrective response is: Separate service VRF import/export route targets from public internet BGP policy and validate permitted NLRI.

Incorrect Answers

A:

BGP communities are optional policy metadata and must be explicitly propagated when the design depends on them. That explains a DIFFERENT 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 mechanism to prioritize for this question is: Route targets control VPN route distribution and should not be treated as ordinary public BGP communities.

B:

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: Route targets control VPN route distribution and should not be treated as ordinary public BGP communities.

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: Route targets control VPN route distribution and should not be treated as ordinary public BGP communities.

Question 580

A core network change board wants to avoid: A route reflector exports every VRF route to a public transit peer after route targets are reused carelessly in an import policy. Which ongoing safeguard fits best?

  1. Archive policy diffs and route-acceptance fixtures with change approvals.
  2. Maintain positive and negative RPL policy unit tests for each provider peer.
  3. Teach neighbor-state expectations per OSPF network type in runbooks.
  4. Enforce explicit domain boundaries in route-target and global export policy checks.

Explanation

Correct Answer

D:

Enforce explicit domain boundaries in route-target and global export policy checks. This helps prevent recurrence of the issue: A route reflector exports every VRF route to a public transit peer after route targets are reused carelessly in an import policy. Acceptance evidence should be: A transit peer receives only global internet prefixes while VPN routes remain in authorized VRFs.

Incorrect Answers

A:

Archive policy diffs and route-acceptance fixtures with change approvals. That is a sensible control for ANOTHER scenario: A policy deployer overwrites an existing RPL route policy in production without a prechange candidate diff, causing accidental withdrawal of one customer aggregate. It is less targeted to this issue than: Enforce explicit domain boundaries in route-target and global export policy checks.

B:

Maintain positive and negative RPL policy unit tests for each provider peer. That is a sensible control for ANOTHER scenario: An IOS XR route policy applies `pass` before a prefix filter and an engineer expects later reject logic to stop evaluation automatically. It is less targeted to this issue than: Enforce explicit domain boundaries in route-target and global export policy checks.

C:

Teach neighbor-state expectations per OSPF network type in runbooks. That is a sensible control for ANOTHER scenario: A multiaccess OSPF network forms neighbor relationships but routes stay stuck at 2-Way between two DROTHER peers, and the operator repeatedly resets them. It is less targeted to this issue than: Enforce explicit domain boundaries in route-target and global export policy checks.