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 46

Question 450

For a regional service-provider operations center, operators addressed: A provider tries to deliver MAP-T using an IPv4-in-IPv6 encapsulation template and loses packets because the customer expects stateless translation. What is the strongest acceptance evidence?

  1. A known IPv4-only test name yields a reachable synthesized AAAA result and end-to-end connectivity.
  2. A lab flow exhibits the intended address and port-set translation without relying on a MAP-E encapsulated payload.
  3. A lab tuple resolves to the correct subscriber session without conflating two simultaneous clients.
  4. A permitted IPv6 test prefix appears while an unapproved wider prefix remains denied.

Explanation

Correct Answer

B:

A lab flow exhibits the intended address and port-set translation without relying on a MAP-E encapsulated payload. This confirms the approved response: Apply the correct MAP-T algorithmic mapping and translation domain settings rather than a tunnel-only configuration. It is relevant because: MAP-T uses stateless IPv4/IPv6 translation, whereas MAP-E relies on IPv4-in-IPv6 encapsulation.

Incorrect Answers

A:

A known IPv4-only test name yields a reachable synthesized AAAA result and end-to-end connectivity. This would validate ANOTHER scenario: 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. The specific correction here is: Apply the correct MAP-T algorithmic mapping and translation domain settings rather than a tunnel-only configuration.

C:

A lab tuple resolves to the correct subscriber session without conflating two simultaneous clients. This would validate 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. The specific correction here is: Apply the correct MAP-T algorithmic mapping and translation domain settings rather than a tunnel-only configuration.

D:

A permitted IPv6 test prefix appears while an unapproved wider prefix remains denied. This would validate 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. The specific correction here is: Apply the correct MAP-T algorithmic mapping and translation domain settings rather than a tunnel-only configuration.

Question 451

Which network protocol or forwarding behavior explains the following issue: A provider tries to deliver MAP-T using an IPv4-in-IPv6 encapsulation template and loses packets because the customer expects stateless translation.

  1. NAT64 forwarding requires an IPv6 destination representation of the IPv4 server, frequently supplied by DNS64.
  2. Carrier-grade NAT shares a public address across subscribers and often requires port and time context for attribution.
  3. MAP-T uses stateless IPv4/IPv6 translation, whereas MAP-E relies on IPv4-in-IPv6 encapsulation.
  4. Protocol troubleshooting should identify the originating control-plane gap rather than reset an unrelated dependent protocol.

Explanation

Correct Answer

C:

MAP-T uses stateless IPv4/IPv6 translation, whereas MAP-E relies on IPv4-in-IPv6 encapsulation. This explains the investigated issue: A provider tries to deliver MAP-T using an IPv4-in-IPv6 encapsulation template and loses packets because the customer expects stateless translation. The approved corrective response is: Apply the correct MAP-T algorithmic mapping and translation domain settings rather than a tunnel-only configuration.

Incorrect Answers

A:

NAT64 forwarding requires an IPv6 destination representation of the IPv4 server, frequently supplied by DNS64. That explains a DIFFERENT scenario: 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. The mechanism to prioritize for this question is: MAP-T uses stateless IPv4/IPv6 translation, whereas MAP-E relies on IPv4-in-IPv6 encapsulation.

B:

Carrier-grade NAT shares a public address across subscribers and often requires port and time context for attribution. That explains a DIFFERENT 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. The mechanism to prioritize for this question is: MAP-T uses stateless IPv4/IPv6 translation, whereas MAP-E relies on IPv4-in-IPv6 encapsulation.

D:

Protocol troubleshooting should identify the originating control-plane gap rather than reset an unrelated dependent protocol. That explains a DIFFERENT scenario: An OSPF route vanishes from one area after an ABR summary change, yet the operator repeatedly resets BGP neighbors to fix the symptom. The mechanism to prioritize for this question is: MAP-T uses stateless IPv4/IPv6 translation, whereas MAP-E relies on IPv4-in-IPv6 encapsulation.

Question 452

A core network change board wants to avoid: A provider tries to deliver MAP-T using an IPv4-in-IPv6 encapsulation template and loses packets because the customer expects stateless translation. Which ongoing safeguard fits best?

  1. Include DNS synthesis and DNSSEC compatibility cases in NAT64 acceptance.
  2. Validate dual-family translation behavior before onboarding IPv6-only customers.
  3. Review IGP link metrics against current network capacity and service objectives.
  4. Distinguish translation versus encapsulation requirements in IPv4-as-a-service profiles.

Explanation

Correct Answer

D:

Distinguish translation versus encapsulation requirements in IPv4-as-a-service profiles. This helps prevent recurrence of the issue: A provider tries to deliver MAP-T using an IPv4-in-IPv6 encapsulation template and loses packets because the customer expects stateless translation. Acceptance evidence should be: A lab flow exhibits the intended address and port-set translation without relying on a MAP-E encapsulated payload.

Incorrect Answers

A:

Include DNS synthesis and DNSSEC compatibility cases in NAT64 acceptance. That is a sensible control for ANOTHER scenario: 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 is less targeted to this issue than: Distinguish translation versus encapsulation requirements in IPv4-as-a-service profiles.

B:

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: Distinguish translation versus encapsulation requirements in IPv4-as-a-service profiles.

C:

Review IGP link metrics against current network capacity and service objectives. That is a sensible control for ANOTHER scenario: An IS-IS L2 router forms adjacency but traffic chooses a high-latency optical link because the interface metric was left at a low default. It is less targeted to this issue than: Distinguish translation versus encapsulation requirements in IPv4-as-a-service profiles.

Question 453

A carrier service activation check discovers: A provider aggregates two PE uplinks in LACP but one port belongs to a different bundle ID, creating unpredictable blackholes for hashed subscriber flows. Which action best restores the intended behavior?

  1. Trace shared-risk link groups and relocate one service path to independent optical facilities where required.
  2. Align LACP partner/key and port-channel membership on both sides and confirm capacity and hashing.
  3. Verify recursive next-hop and forwarding-plane independence for each ECMP member and correct the backup topology.
  4. Introduce the appropriate L1/L2 boundary or L2 route advertisement and review the required reachability design.

Explanation

Correct Answer

B:

Align LACP partner/key and port-channel membership on both sides and confirm capacity and hashing. This directly addresses the fictional service-provider network case: A provider aggregates two PE uplinks in LACP but one port belongs to a different bundle ID, creating unpredictable blackholes for hashed subscriber flows. The technical mechanism is: Link aggregation requires compatible control negotiation and consistent member roles to share forwarding correctly. Verify success by: Both links join one stable operational bundle and sampled customer flows traverse valid active members.

Incorrect Answers

A:

Trace shared-risk link groups and relocate one service path to independent optical facilities where required. This would respond to a DIFFERENT fictional service-provider network issue: An operator assumes two physically diverse core paths are independent, yet both circuits terminate in the same optical amplifier shelf and fail together during power loss. It does not directly address the current situation: A provider aggregates two PE uplinks in LACP but one port belongs to a different bundle ID, creating unpredictable blackholes for hashed subscriber flows.

C:

Verify recursive next-hop and forwarding-plane independence for each ECMP member and correct the backup topology. This would respond to a DIFFERENT fictional service-provider network issue: 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. It does not directly address the current situation: A provider aggregates two PE uplinks in LACP but one port belongs to a different bundle ID, creating unpredictable blackholes for hashed subscriber flows.

D:

Introduce the appropriate L1/L2 boundary or L2 route advertisement and review the required reachability design. This would respond to a DIFFERENT fictional service-provider network issue: Two provider core routers form an IS-IS L1 adjacency but do not exchange a prefix from another area because the engineer assumes L1 routers have universal interarea visibility. It does not directly address the current situation: A provider aggregates two PE uplinks in LACP but one port belongs to a different bundle ID, creating unpredictable blackholes for hashed subscriber flows.

Question 454

Following a supported configuration correction, the original issue was: A provider aggregates two PE uplinks in LACP but one port belongs to a different bundle ID, creating unpredictable blackholes for hashed subscriber flows. Which observation verifies success?

  1. During switchover, eligible traffic continues while routing sessions safely reestablish within the timer budget.
  2. The laboratory upgrade keeps the intended traffic classes forwarding while both supervisors reach the approved release.
  3. Both links join one stable operational bundle and sampled customer flows traverse valid active members.
  4. A limited allowed route set is advertised and the threshold alerts only on unexpected growth.

Explanation

Correct Answer

C:

Both links join one stable operational bundle and sampled customer flows traverse valid active members. This confirms the approved response: Align LACP partner/key and port-channel membership on both sides and confirm capacity and hashing. It is relevant because: Link aggregation requires compatible control negotiation and consistent member roles to share forwarding correctly.

Incorrect Answers

A:

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: Align LACP partner/key and port-channel membership on both sides and confirm capacity and hashing.

B:

The laboratory upgrade keeps the intended traffic classes forwarding while both supervisors reach the approved release. This would validate ANOTHER scenario: A dual-supervisor router reports standby Hot but an engineer schedules an in-service upgrade without checking platform release interoperability and ISSU prerequisites. The specific correction here is: Align LACP partner/key and port-channel membership on both sides and confirm capacity and hashing.

D:

A limited allowed route set is advertised and the threshold alerts only on unexpected growth. This would validate ANOTHER scenario: An eBGP exchange reports Established but a contracted prefix is missing because the advertiser rejects it under a maximum-prefix protection threshold. The specific correction here is: Align LACP partner/key and port-channel membership on both sides and confirm capacity and hashing.

Question 455

At a wholesale transit provider, an engineer examines: A provider aggregates two PE uplinks in LACP but one port belongs to a different bundle ID, creating unpredictable blackholes for hashed subscriber flows. Which technical principle is most applicable?

  1. Logical ECMP diversity does not ensure physical failure independence when transport infrastructure shares common risk.
  2. NSR synchronizes control-plane protocol state to standby processors to minimize adjacency disruptions independently of neighbor GR behavior.
  3. The IS-IS overload bit can discourage transit forwarding through a router during startup or maintenance.
  4. Link aggregation requires compatible control negotiation and consistent member roles to share forwarding correctly.

Explanation

Correct Answer

D:

Link aggregation requires compatible control negotiation and consistent member roles to share forwarding correctly. This explains the investigated issue: A provider aggregates two PE uplinks in LACP but one port belongs to a different bundle ID, creating unpredictable blackholes for hashed subscriber flows. The approved corrective response is: Align LACP partner/key and port-channel membership on both sides and confirm capacity and hashing.

Incorrect Answers

A:

Logical ECMP diversity does not ensure physical failure independence when transport infrastructure shares common risk. That explains a DIFFERENT scenario: An operator assumes two physically diverse core paths are independent, yet both circuits terminate in the same optical amplifier shelf and fail together during power loss. The mechanism to prioritize for this question is: Link aggregation requires compatible control negotiation and consistent member roles to share forwarding correctly.

B:

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: Link aggregation requires compatible control negotiation and consistent member roles to share forwarding correctly.

C:

The IS-IS overload bit can discourage transit forwarding through a router during startup or maintenance. That explains a DIFFERENT scenario: A provider enables IS-IS overload on a recovering core node then removes the flag before the full route database is synchronized, leading to transient transit blackholes. The mechanism to prioritize for this question is: Link aggregation requires compatible control negotiation and consistent member roles to share forwarding correctly.

Question 456

For a wholesale transit provider, the change record describes: A provider aggregates two PE uplinks in LACP but one port belongs to a different bundle ID, creating unpredictable blackholes for hashed subscriber flows. What preventive validation should be standard?

  1. Verify port-channel membership and individual-link counters after physical changes.
  2. Include N-1 link capacity tests in planned-maintenance readiness checks.
  3. Audit FIB recursive adjacency groups as part of resiliency tests.
  4. Perform IPv6 topology capability verification for every new core node.

Explanation

Correct Answer

A:

Verify port-channel membership and individual-link counters after physical changes. This helps prevent recurrence of the issue: A provider aggregates two PE uplinks in LACP but one port belongs to a different bundle ID, creating unpredictable blackholes for hashed subscriber flows. Acceptance evidence should be: Both links join one stable operational bundle and sampled customer flows traverse valid active members.

Incorrect Answers

B:

Include N-1 link capacity tests in planned-maintenance readiness checks. That is a sensible control for ANOTHER scenario: A core routing node performs maintenance with all traffic temporarily pinned to one uplink, exceeding the designed capacity even though connectivity stays up. It is less targeted to this issue than: Verify port-channel membership and individual-link counters after physical changes.

C:

Audit FIB recursive adjacency groups as part of resiliency tests. That is a sensible control for ANOTHER 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. It is less targeted to this issue than: Verify port-channel membership and individual-link counters after physical changes.

D:

Perform IPv6 topology capability verification for every new core node. That is a sensible control for ANOTHER scenario: A new IPv6-only service is added to an IS-IS core, but routers run a single topology configuration where the IPv6 reachability bits are not negotiated consistently. It is less targeted to this issue than: Verify port-channel membership and individual-link counters after physical changes.

Question 457

For a multi-region fiber backbone operator, the failure is: A service provider exports VPNv4 labels across multiple autonomous regions but assumes LDP sessions must directly span every access network and interregion core. Which authorized correction best addresses it?

  1. Reconcile LDP label mapping with current IGP FEC reachability and refresh only the impacted forwarding state through supported procedures.
  2. Enable LDP on the approved core interface and verify IGP reachability and label binding for the PE FEC.
  3. Design the supported unified MPLS hierarchy with transport label continuity and controlled route exchange at the ABR or AS border.
  4. Review SR policy candidate preference and validation rules before comparing metric objectives.

Explanation

Correct Answer

C:

Design the supported unified MPLS hierarchy with transport label continuity and controlled route exchange at the ABR or AS border. This directly addresses the fictional service-provider network case: A service provider exports VPNv4 labels across multiple autonomous regions but assumes LDP sessions must directly span every access network and interregion core. The technical mechanism is: Unified MPLS connects labeled forwarding domains through compatible hierarchical transport and route policies rather than universal direct LDP peering. Verify success by: A service prefix traverses the core layers with valid outer transport labels and correct VPN label disposition at the egress PE.

Incorrect Answers

A:

Reconcile LDP label mapping with current IGP FEC reachability and refresh only the impacted forwarding state through supported procedures. This would respond to a DIFFERENT fictional service-provider network issue: Label advertisement remains present for a withdrawn IGP FEC due to a stale forwarding cache, producing a short-lived blackhole after a route-policy rollback. It does not directly address the current situation: A service provider exports VPNv4 labels across multiple autonomous regions but assumes LDP sessions must directly span every access network and interregion core.

B:

Enable LDP on the approved core interface and verify IGP reachability and label binding for the PE FEC. This would respond to a DIFFERENT fictional service-provider network issue: Two P routers forward IPv4 internet traffic but no MPLS labels appear for PE loopbacks because one interface has LDP disabled. It does not directly address the current situation: A service provider exports VPNv4 labels across multiple autonomous regions but assumes LDP sessions must directly span every access network and interregion core.

D:

Review SR policy candidate preference and validation rules before comparing metric objectives. This would respond to a DIFFERENT fictional service-provider network issue: A carrier configures multiple SR policy candidate paths and expects the smallest latency metric to always win, but an explicitly higher-preference candidate overrides it. It does not directly address the current situation: A service provider exports VPNv4 labels across multiple autonomous regions but assumes LDP sessions must directly span every access network and interregion core.

Question 458

After fixing the following network problem, what should the team verify: A service provider exports VPNv4 labels across multiple autonomous regions but assumes LDP sessions must directly span every access network and interregion core.

  1. A test at the required maximum service size passes without fragmentation-dependent loss or interface MTU errors.
  2. A P router's LFIB contains approved core transport FECs and no unintended VRF-specific customer forwarding state.
  3. Available TE reservable bandwidth rises in line with released legitimate reservations without changing the physical capacity.
  4. A service prefix traverses the core layers with valid outer transport labels and correct VPN label disposition at the egress PE.

Explanation

Correct Answer

D:

A service prefix traverses the core layers with valid outer transport labels and correct VPN label disposition at the egress PE. This confirms the approved response: Design the supported unified MPLS hierarchy with transport label continuity and controlled route exchange at the ABR or AS border. It is relevant because: Unified MPLS connects labeled forwarding domains through compatible hierarchical transport and route policies rather than universal direct LDP peering.

Incorrect Answers

A:

A test at the required maximum service size passes without fragmentation-dependent loss or interface MTU errors. This would validate ANOTHER scenario: An MPLS pseudowire intermittently drops large customer frames after VLAN tagging increases payload size beyond a transit link's supported frame budget. The specific correction here is: Design the supported unified MPLS hierarchy with transport label continuity and controlled route exchange at the ABR or AS border.

B:

A P router's LFIB contains approved core transport FECs and no unintended VRF-specific customer forwarding state. This would validate ANOTHER scenario: A P router allocates labels for customer routes that should only exist at the VRF-aware PE, and the core sees unexpected VPN forwarding context. The specific correction here is: Design the supported unified MPLS hierarchy with transport label continuity and controlled route exchange at the ABR or AS border.

C:

Available TE reservable bandwidth rises in line with released legitimate reservations without changing the physical capacity. This would validate ANOTHER scenario: One router reports TE bandwidth exhausted even though link counters show the circuit nearly idle, and operators increase interface speed without investigating reservations. The specific correction here is: Design the supported unified MPLS hierarchy with transport label continuity and controlled route exchange at the ABR or AS border.

Question 459

A carrier root-cause review considers: A service provider exports VPNv4 labels across multiple autonomous regions but assumes LDP sessions must directly span every access network and interregion core. What underlying mechanism explains this?

  1. Unified MPLS connects labeled forwarding domains through compatible hierarchical transport and route policies rather than universal direct LDP peering.
  2. A label binding without reachable next-hop context is insufficient to deliver a usable MPLS transport LSP.
  3. LDP discovery and its subsequent transport session are separate stages with independent failure conditions.
  4. An established TE LSP does not attract user traffic unless routing or policy intentionally steers packets into it.

Explanation

Correct Answer

A:

Unified MPLS connects labeled forwarding domains through compatible hierarchical transport and route policies rather than universal direct LDP peering. This explains the investigated issue: A service provider exports VPNv4 labels across multiple autonomous regions but assumes LDP sessions must directly span every access network and interregion core. The approved corrective response is: Design the supported unified MPLS hierarchy with transport label continuity and controlled route exchange at the ABR or AS border.

Incorrect Answers

B:

A label binding without reachable next-hop context is insufficient to deliver a usable MPLS transport LSP. That explains a DIFFERENT scenario: A remote PE receives an LDP label binding but the advertised transport loopback is absent from the IGP, making forwarding unresolved. The mechanism to prioritize for this question is: Unified MPLS connects labeled forwarding domains through compatible hierarchical transport and route policies rather than universal direct LDP peering.

C:

LDP discovery and its subsequent transport session are separate stages with independent failure conditions. That explains a DIFFERENT scenario: Two neighboring MPLS routers use different LDP authentication credentials and fail to form a TCP session even though UDP discovery hellos arrive. The mechanism to prioritize for this question is: Unified MPLS connects labeled forwarding domains through compatible hierarchical transport and route policies rather than universal direct LDP peering.

D:

An established TE LSP does not attract user traffic unless routing or policy intentionally steers packets into it. That explains a DIFFERENT scenario: The route processor shows an RSVP-TE tunnel Up, but a live traffic test still traverses native IGP forwarding because the tunnel is not selected for the destination. The mechanism to prioritize for this question is: Unified MPLS connects labeled forwarding domains through compatible hierarchical transport and route policies rather than universal direct LDP peering.

Question 460

After addressing: A service provider exports VPNv4 labels across multiple autonomous regions but assumes LDP sessions must directly span every access network and interregion core. Which recurring service assurance check is most useful?

  1. Include transport and service-layer OAM in VPN fault playbooks.
  2. Include crossregion label-stack tracing in service acceptance.
  3. Measure end-to-end label-stack MTU at every new pseudowire deployment.
  4. Include TE database completeness checks during IGP maintenance.

Explanation

Correct Answer

B:

Include crossregion label-stack tracing in service acceptance. This helps prevent recurrence of the issue: A service provider exports VPNv4 labels across multiple autonomous regions but assumes LDP sessions must directly span every access network and interregion core. Acceptance evidence should be: A service prefix traverses the core layers with valid outer transport labels and correct VPN label disposition at the egress PE.

Incorrect Answers

A:

Include transport and service-layer OAM in VPN fault playbooks. That is a sensible control for ANOTHER scenario: A provider applies MPLS LSP ping only to the global transport loopback while a customer L3VPN remains broken, then claims VPN reachability is fully proven. It is less targeted to this issue than: Include crossregion label-stack tracing in service acceptance.

C:

Measure end-to-end label-stack MTU at every new pseudowire deployment. That is a sensible control for ANOTHER scenario: An MPLS pseudowire intermittently drops large customer frames after VLAN tagging increases payload size beyond a transit link's supported frame budget. It is less targeted to this issue than: Include crossregion label-stack tracing in service acceptance.

D:

Include TE database completeness checks during IGP maintenance. That is a sensible control for ANOTHER scenario: A backbone planner expects constrained TE to calculate alternate paths while the IGP advertises only basic reachability and no extended TE link attributes. It is less targeted to this issue than: Include crossregion label-stack tracing in service acceptance.