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 44

Question 430

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

  1. The lab adjacency reaches Full and the stub router installs the designated default route.
  2. Peering remains healthy and management attempts use a routable endpoint instead of a bare link-local address.
  3. Valid component destinations work and an unassigned prefix does not loop indefinitely.
  4. Customer route queries show approved aggregate service routes but no internal infrastructure prefixes.

Explanation

Correct Answer

A:

The lab adjacency reaches Full and the stub router installs the designated default route. This confirms the approved response: Align stub-area configuration on the ABR and member routers and verify default advertisement. It is relevant because: OSPF area-type agreement is required for adjacency and stub routing behavior.

Incorrect Answers

B:

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: Align stub-area configuration on the ABR and member routers and verify default advertisement.

C:

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: Align stub-area configuration on the ABR and member routers and verify default advertisement.

D:

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: Align stub-area configuration on the ABR and member routers and verify default advertisement.

Question 431

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

  1. OSPF broadcast networks use DR/BDR adjacency optimization rather than full mesh formation.
  2. OSPF area-type agreement is required for adjacency and stub routing behavior.
  3. IPv6 link-local addresses are scoped to their link and need an interface scope when referenced locally.
  4. NSR synchronizes control-plane protocol state to standby processors to minimize adjacency disruptions independently of neighbor GR behavior.

Explanation

Correct Answer

B:

OSPF area-type agreement is required for adjacency and stub routing behavior. This explains the investigated issue: 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. The approved corrective response is: Align stub-area configuration on the ABR and member routers and verify default advertisement.

Incorrect Answers

A:

OSPF broadcast networks use DR/BDR adjacency optimization rather than full mesh formation. That explains a DIFFERENT 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. The mechanism to prioritize for this question is: OSPF area-type agreement is required for adjacency and stub routing behavior.

C:

IPv6 link-local addresses are scoped to their link and need an interface scope when referenced locally. That explains a DIFFERENT scenario: An OSPFv3 deployment uses a link-local neighbor address and the monitoring system mistakenly treats it as globally reachable offlink for management. The mechanism to prioritize for this question is: OSPF area-type agreement is required for adjacency and stub routing behavior.

D:

NSR synchronizes control-plane protocol state to standby processors to minimize adjacency disruptions independently of neighbor GR behavior. That explains a DIFFERENT scenario: An IOS XR chassis uses NSR for one IGP but a critical BGP peer lacks state synchronization to the standby process, losing adjacency on failover. The mechanism to prioritize for this question is: OSPF area-type agreement is required for adjacency and stub routing behavior.

Question 432

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

  1. Check interface MTU and OSPF packet parameters when commissioning peer links.
  2. Test protocol instance, VRF and AF together in route acceptance.
  3. Validate area-type consistency before enabling stub policy.
  4. Trend prefix counts and alert before capacity thresholds are reached.

Explanation

Correct Answer

C:

Validate area-type consistency before enabling stub policy. This helps prevent recurrence of the issue: 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. Acceptance evidence should be: The lab adjacency reaches Full and the stub router installs the designated default route.

Incorrect Answers

A:

Check interface MTU and OSPF packet parameters when commissioning peer links. That is a sensible control for ANOTHER scenario: Two provider OSPFv2 routers share an Ethernet segment but never advance past EXSTART because one end uses an incompatible interface MTU. It is less targeted to this issue than: Validate area-type consistency before enabling stub policy.

B:

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: Validate area-type consistency before enabling stub policy.

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: Validate area-type consistency before enabling stub policy.

Question 433

At a multi-tenant data transport provider, an engineering review finds: 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. Which change most directly corrects the service problem?

  1. Inspect origin and other ordered attributes using the platform's best-path detail before rewriting policy.
  2. Inspect the full deterministic tie-breaking sequence and stabilize the intended export policy if one exit must be preferred.
  3. Set and verify the intended local-preference policy and document that it outranks AS_PATH length in local best-path selection.
  4. Restore the intended IGP reachability to the correct BGP next hop or adjust policy consistently with design.

Explanation

Correct Answer

A:

Inspect origin and other ordered attributes using the platform's best-path detail before rewriting policy. This directly addresses the fictional service-provider network case: 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 technical mechanism is: Origin type can influence BGP selection after higher-priority criteria such as weight, local preference and path length. Verify success by: A fixture shows the expected origin-type comparison only after preceding attributes tie.

Incorrect Answers

B:

Inspect the full deterministic tie-breaking sequence and stabilize the intended export policy if one exit must be preferred. This would respond to a DIFFERENT fictional service-provider network 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. It does not directly address the current situation: 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.

C:

Set and verify the intended local-preference policy and document that it outranks AS_PATH length in local best-path selection. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: 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.

D:

Restore the intended IGP reachability to the correct BGP next hop or adjust policy consistently with design. This would respond to a DIFFERENT fictional service-provider network issue: BGP routes are received but a recursive next hop points to a withdrawn loopback, causing the FIB not to install otherwise valid customer NLRI. It does not directly address the current situation: 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.

Question 434

For a multi-tenant data transport provider, operators addressed: 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. What is the strongest acceptance evidence?

  1. Adjacent peer route views show additional paths only when both sides support and negotiate the feature.
  2. A fixture shows the expected origin-type comparison only after preceding attributes tie.
  3. A lab best-path trace shows the expected externally learned candidate winning when earlier attributes tie.
  4. A link-loss test switches eligible prefixes onto the backup next hop within the documented recovery target.

Explanation

Correct Answer

B:

A fixture shows the expected origin-type comparison only after preceding attributes tie. This confirms the approved response: Inspect origin and other ordered attributes using the platform's best-path detail before rewriting policy. It is relevant because: Origin type can influence BGP selection after higher-priority criteria such as weight, local preference and path length.

Incorrect Answers

A:

Adjacent peer route views show additional paths only when both sides support and negotiate the feature. This would validate ANOTHER scenario: A route reflector learns several equivalent multipath candidates but advertises only its best path and a customer confuses multipath forwarding with multiple advertised path dissemination. The specific correction here is: Inspect origin and other ordered attributes using the platform's best-path detail before rewriting policy.

C:

A lab best-path trace shows the expected externally learned candidate winning when earlier attributes tie. This would validate ANOTHER 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 specific correction here is: Inspect origin and other ordered attributes using the platform's best-path detail before rewriting policy.

D:

A link-loss test switches eligible prefixes onto the backup next hop within the documented recovery target. This would validate ANOTHER scenario: 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. The specific correction here is: Inspect origin and other ordered attributes using the platform's best-path detail before rewriting policy.

Question 435

Which network protocol or forwarding behavior explains the following issue: 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.

  1. BGP best-path selection compares multiple attributes in a defined order rather than relying solely on IGP metrics.
  2. Standard BGP advertises selected best routes unless mechanisms such as Add-Path permit multiple distinct paths for a prefix.
  3. Origin type can influence BGP selection after higher-priority criteria such as weight, local preference and path length.
  4. Equal-cost routes can conceal a common downstream failure when their recursive forwarding dependencies overlap.

Explanation

Correct Answer

C:

Origin type can influence BGP selection after higher-priority criteria such as weight, local preference and path length. This explains the investigated issue: 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 approved corrective response is: Inspect origin and other ordered attributes using the platform's best-path detail before rewriting policy.

Incorrect Answers

A:

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: Origin type can influence BGP selection after higher-priority criteria such as weight, local preference and path length.

B:

Standard BGP advertises selected best routes unless mechanisms such as Add-Path permit multiple distinct paths for a prefix. That explains a DIFFERENT scenario: A route reflector learns several equivalent multipath candidates but advertises only its best path and a customer confuses multipath forwarding with multiple advertised path dissemination. The mechanism to prioritize for this question is: Origin type can influence BGP selection after higher-priority criteria such as weight, local preference and path length.

D:

Equal-cost routes can conceal a common downstream failure when their recursive forwarding dependencies overlap. That explains a DIFFERENT scenario: A network uses two next hops with ECMP but one backup route resolves through the same failed access link and the team reports full path redundancy. The mechanism to prioritize for this question is: Origin type can influence BGP selection after higher-priority criteria such as weight, local preference and path length.

Question 436

A core network change board wants to avoid: 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. Which ongoing safeguard fits best?

  1. Keep best-path attribute snapshots alongside policy change tickets.
  2. Avoid using accidental router IDs as a business traffic-engineering policy.
  3. Verify lower-layer IGP readiness before diagnosing dependent BGP sessions.
  4. Document nondefault origin modifications to avoid opaque path changes.

Explanation

Correct Answer

D:

Document nondefault origin modifications to avoid opaque path changes. This helps prevent recurrence of the issue: 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. Acceptance evidence should be: A fixture shows the expected origin-type comparison only after preceding attributes tie.

Incorrect Answers

A:

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: Document nondefault origin modifications to avoid opaque path changes.

B:

Avoid using accidental router IDs as a business traffic-engineering policy. That is a sensible control for ANOTHER scenario: BGP flips between two equal candidates because a team ignores the router-id and neighbor-address tie-breakers after all higher-ranked attributes match. It is less targeted to this issue than: Document nondefault origin modifications to avoid opaque path changes.

C:

Verify lower-layer IGP readiness before diagnosing dependent BGP sessions. That is a sensible control for 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. It is less targeted to this issue than: Document nondefault origin modifications to avoid opaque path changes.

Question 437

A carrier service activation check discovers: A provider changes MED inbound on one customer edge and expects all distant autonomous systems to prefer that link for inbound traffic. Which action best restores the intended behavior?

  1. Correct remote-as and authenticated neighbor parameters to match the provider-customer agreement.
  2. Use MED within its intended neighboring-AS comparison scope and coordinate inbound policy or communities with upstreams where needed.
  3. Bind the correct IPv6 address-family policy and prefix filters to the matching BGP neighbor family.
  4. Generate a reviewed intended-state diff and test representative prefixes before committing the revised policy.

Explanation

Correct Answer

B:

Use MED within its intended neighboring-AS comparison scope and coordinate inbound policy or communities with upstreams where needed. This directly addresses the fictional service-provider network case: A provider changes MED inbound on one customer edge and expects all distant autonomous systems to prefer that link for inbound traffic. The technical mechanism is: MED is a hint for inbound exit selection and is not a global guarantee of all upstream route choices. Verify success by: A test peer honors the agreed MED when comparing eligible paths from the same neighboring AS.

Incorrect Answers

A:

Correct remote-as and authenticated neighbor parameters to match the provider-customer agreement. This would respond to a DIFFERENT fictional service-provider network issue: A new eBGP handoff establishes TCP transport but remains Idle/Active because the peer configuration uses the wrong autonomous-system number. It does not directly address the current situation: A provider changes MED inbound on one customer edge and expects all distant autonomous systems to prefer that link for inbound traffic.

C:

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 provider changes MED inbound on one customer edge and expects all distant autonomous systems to prefer that link for inbound traffic.

D:

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 provider changes MED inbound on one customer edge and expects all distant autonomous systems to prefer that link for inbound traffic.

Question 438

Following a supported configuration correction, the original issue was: A provider changes MED inbound on one customer edge and expects all distant autonomous systems to prefer that link for inbound traffic. Which observation verifies success?

  1. Route-policy trace shows only approved prefixes accepted while unrelated customer families stay filtered.
  2. The prefix becomes usable with a resolved next hop while the IGP remains stable.
  3. A test peer honors the agreed MED when comparing eligible paths from the same neighboring AS.
  4. Neighbor state advances to Full and the LSDB includes the expected network LSA.

Explanation

Correct Answer

C:

A test peer honors the agreed MED when comparing eligible paths from the same neighboring AS. This confirms the approved response: Use MED within its intended neighboring-AS comparison scope and coordinate inbound policy or communities with upstreams where needed. It is relevant because: MED is a hint for inbound exit selection and is not a global guarantee of all upstream route choices.

Incorrect Answers

A:

Route-policy trace shows only approved prefixes accepted while unrelated customer families stay filtered. This would validate 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. The specific correction here is: Use MED within its intended neighboring-AS comparison scope and coordinate inbound policy or communities with upstreams where needed.

B:

The prefix becomes usable with a resolved next hop while the IGP remains stable. This would validate ANOTHER 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 specific correction here is: Use MED within its intended neighboring-AS comparison scope and coordinate inbound policy or communities with upstreams where needed.

D:

Neighbor state advances to Full and the LSDB includes the expected network LSA. This would validate ANOTHER scenario: Two provider OSPFv2 routers share an Ethernet segment but never advance past EXSTART because one end uses an incompatible interface MTU. The specific correction here is: Use MED within its intended neighboring-AS comparison scope and coordinate inbound policy or communities with upstreams where needed.

Question 439

At an ISP route assurance team, an engineer examines: A provider changes MED inbound on one customer edge and expects all distant autonomous systems to prefer that link for inbound traffic. Which technical principle is most applicable?

  1. BGP session establishment is distinct from activation of a specific MP-BGP address family.
  2. BGP route policy can accept or reject NLRI independently of session health.
  3. Shared-address NAT needs distinct translated transport identifiers to demultiplex flows accurately.
  4. MED is a hint for inbound exit selection and is not a global guarantee of all upstream route choices.

Explanation

Correct Answer

D:

MED is a hint for inbound exit selection and is not a global guarantee of all upstream route choices. This explains the investigated issue: A provider changes MED inbound on one customer edge and expects all distant autonomous systems to prefer that link for inbound traffic. The approved corrective response is: Use MED within its intended neighboring-AS comparison scope and coordinate inbound policy or communities with upstreams where needed.

Incorrect Answers

A:

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: MED is a hint for inbound exit selection and is not a global guarantee of all upstream route choices.

B:

BGP route policy can accept or reject NLRI independently of session health. That explains a DIFFERENT 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. The mechanism to prioritize for this question is: MED is a hint for inbound exit selection and is not a global guarantee of all upstream route choices.

C:

Shared-address NAT needs distinct translated transport identifiers to demultiplex flows accurately. That explains a DIFFERENT 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. The mechanism to prioritize for this question is: MED is a hint for inbound exit selection and is not a global guarantee of all upstream route choices.

Question 440

For an ISP route assurance team, the change record describes: A provider changes MED inbound on one customer edge and expects all distant autonomous systems to prefer that link for inbound traffic. What preventive validation should be standard?

  1. Record upstream acceptance of traffic-engineering communities and MED policy.
  2. Review candidate redistribution tables under a default-deny policy.
  3. Verify v4 and v6 filter family independently during peering certification.
  4. Validate dual-family translation behavior before onboarding IPv6-only customers.

Explanation

Correct Answer

A:

Record upstream acceptance of traffic-engineering communities and MED policy. This helps prevent recurrence of the issue: A provider changes MED inbound on one customer edge and expects all distant autonomous systems to prefer that link for inbound traffic. Acceptance evidence should be: A test peer honors the agreed MED when comparing eligible paths from the same neighboring AS.

Incorrect Answers

B:

Review candidate redistribution tables under a default-deny policy. That is a sensible control for ANOTHER scenario: An edge router injects all OSPF internals into BGP without tagging or policy, exposing infrastructure loopbacks to a customer upstream. It is less targeted to this issue than: Record upstream acceptance of traffic-engineering communities and MED policy.

C:

Verify v4 and v6 filter family independently during peering certification. That is a sensible control for ANOTHER scenario: 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 is less targeted to this issue than: Record upstream acceptance of traffic-engineering communities and MED policy.

D:

Validate dual-family translation behavior before onboarding IPv6-only customers. That is a sensible control for ANOTHER scenario: An IPv6-only enterprise application must reach an IPv4-only legacy service, but the provider installs NAT44 and expects it to translate the address families. It is less targeted to this issue than: Record upstream acceptance of traffic-engineering communities and MED policy.