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 21

Question 200

For a regional peering-exchange operator, the change record describes: A provider changes an RSVP-TE tunnel to use an explicit path containing a router that lacks TE extensions, leaving the tunnel down despite IP reachability. What preventive validation should be standard?

  1. Validate explicit-route hops against TE capability data before committing.
  2. Maintain optical SRLG metadata with core IGP-TE inventory.
  3. Include TE database completeness checks during IGP maintenance.
  4. Check IGP and LDP FEC consistency at every interregion boundary.

Explanation

Correct Answer

A:

Validate explicit-route hops against TE capability data before committing. This helps prevent recurrence of the issue: A provider changes an RSVP-TE tunnel to use an explicit path containing a router that lacks TE extensions, leaving the tunnel down despite IP reachability. Acceptance evidence should be: RSVP PATH and RESV state establish across the intended nodes and the LSP forwards test traffic.

Incorrect Answers

B:

Maintain optical SRLG metadata with core IGP-TE inventory. That is a sensible control for ANOTHER scenario: A traffic engineering policy considers only link bandwidth when selecting primary and backup paths, but both use one optical shared-risk group. It is less targeted to this issue than: Validate explicit-route hops against TE capability data before committing.

C:

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: Validate explicit-route hops against TE capability data before committing.

D:

Check IGP and LDP FEC consistency at every interregion boundary. That is a sensible control for ANOTHER scenario: A remote PE receives an LDP label binding but the advertised transport loopback is absent from the IGP, making forwarding unresolved. It is less targeted to this issue than: Validate explicit-route hops against TE capability data before committing.

Question 201

For an optical transport engineering team, the failure is: A headend constructs an SR policy from adjacency SIDs but one adjacency SID identifies the wrong outbound interface after topology maintenance. Which authorized correction best addresses it?

  1. Enable the agreed algorithm definition and participation on all required forwarding nodes or avoid steering through unsupported paths.
  2. Identify segment types from the advertised IGP/BGP SID attributes and construct the policy with the correct Prefix-SID and adjacency-SID semantics.
  3. Recalculate the segment list using the current topology and correct adjacency SID advertisements before enabling the policy.
  4. Restore loopback reachability and confirm the label's mapped FEC belongs to an installed valid route.

Explanation

Correct Answer

C:

Recalculate the segment list using the current topology and correct adjacency SID advertisements before enabling the policy. This directly addresses the fictional service-provider network case: A headend constructs an SR policy from adjacency SIDs but one adjacency SID identifies the wrong outbound interface after topology maintenance. The technical mechanism is: Adjacency segments steer traffic over specific local links, unlike more abstract prefix segments. Verify success by: A test packet traverses the intended interface sequence and no longer visits the retired link.

Incorrect Answers

A:

Enable the agreed algorithm definition and participation on all required forwarding nodes or avoid steering through unsupported paths. This would respond to a DIFFERENT fictional service-provider network issue: A Flexible Algorithm is activated only on a subset of routers and a service prefix uses a Flex-Algo SID that transit nodes cannot resolve. It does not directly address the current situation: A headend constructs an SR policy from adjacency SIDs but one adjacency SID identifies the wrong outbound interface after topology maintenance.

B:

Identify segment types from the advertised IGP/BGP SID attributes and construct the policy with the correct Prefix-SID and adjacency-SID semantics. This would respond to a DIFFERENT fictional service-provider network issue: A router advertises a Prefix-SID for a loopback but another node's policy interprets the index as an adjacency segment and sends traffic out an unrelated interface. It does not directly address the current situation: A headend constructs an SR policy from adjacency SIDs but one adjacency SID identifies the wrong outbound interface after topology maintenance.

D:

Restore loopback reachability and confirm the label's mapped FEC belongs to an installed valid route. This would respond to a DIFFERENT fictional service-provider network issue: A remote PE receives an LDP label binding but the advertised transport loopback is absent from the IGP, making forwarding unresolved. It does not directly address the current situation: A headend constructs an SR policy from adjacency SIDs but one adjacency SID identifies the wrong outbound interface after topology maintenance.

Question 202

After fixing the following network problem, what should the team verify: A headend constructs an SR policy from adjacency SIDs but one adjacency SID identifies the wrong outbound interface after topology maintenance.

  1. The PCC installs only approved delegated candidates and reports their active state back to the PCE.
  2. A worst-case policy passes a documented Maximum SID Depth check and forwards test packets end-to-end.
  3. An MPLS capture shows the egress PE still receives the necessary inner VPN service label for correct VRF lookup.
  4. A test packet traverses the intended interface sequence and no longer visits the retired link.

Explanation

Correct Answer

D:

A test packet traverses the intended interface sequence and no longer visits the retired link. This confirms the approved response: Recalculate the segment list using the current topology and correct adjacency SID advertisements before enabling the policy. It is relevant because: Adjacency segments steer traffic over specific local links, unlike more abstract prefix segments.

Incorrect Answers

A:

The PCC installs only approved delegated candidates and reports their active state back to the PCE. This would validate ANOTHER scenario: A PCE computes a low-latency SR-TE candidate, but the PCC ignores it because the PCEP session lacks authorization for delegated policy control. The specific correction here is: Recalculate the segment list using the current topology and correct adjacency SID advertisements before enabling the policy.

B:

A worst-case policy passes a documented Maximum SID Depth check and forwards test packets end-to-end. This would validate ANOTHER scenario: The headend imposes an SR-MPLS list of eight SIDs on a platform supporting only six, causing only complex engineered paths to fail. The specific correction here is: Recalculate the segment list using the current topology and correct adjacency SID advertisements before enabling the policy.

C:

An MPLS capture shows the egress PE still receives the necessary inner VPN service label for correct VRF lookup. This would validate ANOTHER scenario: A transit router keeps unexpectedly popping a provider's VPN label one hop before the target PE, sending customer traffic toward the global routing table. The specific correction here is: Recalculate the segment list using the current topology and correct adjacency SID advertisements before enabling the policy.

Question 203

A carrier root-cause review considers: A headend constructs an SR policy from adjacency SIDs but one adjacency SID identifies the wrong outbound interface after topology maintenance. What underlying mechanism explains this?

  1. Adjacency segments steer traffic over specific local links, unlike more abstract prefix segments.
  2. SRv6 End.DT4 behavior couples decapsulation to an IPv4 table lookup and must be associated with the right service routing context.
  3. Prefix-SID indexes are interpreted through each node's advertised Segment Routing Global Block, not as universally identical label values.
  4. Unified MPLS connects labeled forwarding domains through compatible hierarchical transport and route policies rather than universal direct LDP peering.

Explanation

Correct Answer

A:

Adjacency segments steer traffic over specific local links, unlike more abstract prefix segments. This explains the investigated issue: A headend constructs an SR policy from adjacency SIDs but one adjacency SID identifies the wrong outbound interface after topology maintenance. The approved corrective response is: Recalculate the segment list using the current topology and correct adjacency SID advertisements before enabling the policy.

Incorrect Answers

B:

SRv6 End.DT4 behavior couples decapsulation to an IPv4 table lookup and must be associated with the right service routing context. That explains a DIFFERENT scenario: An SRv6 egress router discards traffic because a local End.DT4 service SID is placed in the wrong VRF context, even though the locator is reachable. The mechanism to prioritize for this question is: Adjacency segments steer traffic over specific local links, unlike more abstract prefix segments.

C:

Prefix-SID indexes are interpreted through each node's advertised Segment Routing Global Block, not as universally identical label values. That explains a DIFFERENT scenario: An operator configures an SR-MPLS Prefix-SID for a PE loopback, but different routers assign inconsistent SID indexes relative to their SRGB ranges, causing label misinterpretation. The mechanism to prioritize for this question is: Adjacency segments steer traffic over specific local links, unlike more abstract prefix segments.

D:

Unified MPLS connects labeled forwarding domains through compatible hierarchical transport and route policies rather than universal direct LDP peering. That explains a DIFFERENT scenario: A service provider exports VPNv4 labels across multiple autonomous regions but assumes LDP sessions must directly span every access network and interregion core. The mechanism to prioritize for this question is: Adjacency segments steer traffic over specific local links, unlike more abstract prefix segments.

Question 204

After addressing: A headend constructs an SR policy from adjacency SIDs but one adjacency SID identifies the wrong outbound interface after topology maintenance. Which recurring service assurance check is most useful?

  1. Verify local SID behaviors and VRF bindings during VPN service provisioning.
  2. Monitor adjacency SID changes and invalidate stale policy segment lists.
  3. Include MSD capability checks in every SR policy computation.
  4. Train operators to differentiate implicit-null, explicit-null and real transport labels.

Explanation

Correct Answer

B:

Monitor adjacency SID changes and invalidate stale policy segment lists. This helps prevent recurrence of the issue: A headend constructs an SR policy from adjacency SIDs but one adjacency SID identifies the wrong outbound interface after topology maintenance. Acceptance evidence should be: A test packet traverses the intended interface sequence and no longer visits the retired link.

Incorrect Answers

A:

Verify local SID behaviors and VRF bindings during VPN service provisioning. That is a sensible control for ANOTHER scenario: An SRv6 egress router discards traffic because a local End.DT4 service SID is placed in the wrong VRF context, even though the locator is reachable. It is less targeted to this issue than: Monitor adjacency SID changes and invalidate stale policy segment lists.

C:

Include MSD capability checks in every SR policy computation. That is a sensible control for ANOTHER scenario: The headend imposes an SR-MPLS list of eight SIDs on a platform supporting only six, causing only complex engineered paths to fail. It is less targeted to this issue than: Monitor adjacency SID changes and invalidate stale policy segment lists.

D:

Train operators to differentiate implicit-null, explicit-null and real transport labels. That is a sensible control for ANOTHER scenario: The forwarding plane sees an implicit-null label for a PE loopback and a troubleshooter treats it as an invalid unassigned label rather than checking the upstream label disposition. It is less targeted to this issue than: Monitor adjacency SID changes and invalidate stale policy segment lists.

Question 205

A provider backbone escalation identifies: Two PEs establish BGP EVPN but remote MAC mobility updates are ignored because a device keeps an older sequence number as authoritative. What should the network team implement?

  1. Use the supported Carrier Supporting Carrier VPN transport design and preserve customer route isolation across the wholesale boundary.
  2. Align the configured Inter-AS VPN option and VPN route-label signaling at the authorized provider border nodes.
  3. Leak only necessary shared-service prefixes with scoped RTs and controlled return-path routing policies.
  4. Validate EVPN MAC mobility extended communities and accept the newer sequence state under supported mobility procedures.

Explanation

Correct Answer

D:

Validate EVPN MAC mobility extended communities and accept the newer sequence state under supported mobility procedures. This directly addresses the fictional service-provider network case: Two PEs establish BGP EVPN but remote MAC mobility updates are ignored because a device keeps an older sequence number as authoritative. The technical mechanism is: EVPN MAC mobility uses sequence information to resolve competing advertisements for a moving endpoint. Verify success by: A host migration test updates the remote PE forwarding location without persistent duplicate MAC forwarding.

Incorrect Answers

A:

Use the supported Carrier Supporting Carrier VPN transport design and preserve customer route isolation across the wholesale boundary. This would respond to a DIFFERENT fictional service-provider network issue: A wholesale carrier provides carrier-supporting-carrier transport, but a subcontractor PE advertises customer routes into the infrastructure global table rather than using labeled backbone service separation. It does not directly address the current situation: Two PEs establish BGP EVPN but remote MAC mobility updates are ignored because a device keeps an older sequence number as authoritative.

B:

Align the configured Inter-AS VPN option and VPN route-label signaling at the authorized provider border nodes. This would respond to a DIFFERENT fictional service-provider network issue: An inter-AS L3VPN reaches the first provider but customer prefixes vanish at the AS boundary because VPNv4 routes and label context are not exchanged under the chosen inter-AS model. It does not directly address the current situation: Two PEs establish BGP EVPN but remote MAC mobility updates are ignored because a device keeps an older sequence number as authoritative.

C:

Leak only necessary shared-service prefixes with scoped RTs and controlled return-path routing policies. This would respond to a DIFFERENT fictional service-provider network issue: A shared-services DNS VRF must serve three customer VRFs, but engineers import full customer route tables into the DNS VRF and unintentionally create broad extranet connectivity. It does not directly address the current situation: Two PEs establish BGP EVPN but remote MAC mobility updates are ignored because a device keeps an older sequence number as authoritative.

Question 206

A service-provider operations test targets: Two PEs establish BGP EVPN but remote MAC mobility updates are ignored because a device keeps an older sequence number as authoritative. Which result is required?

  1. A host migration test updates the remote PE forwarding location without persistent duplicate MAC forwarding.
  2. Route readback shows the prefix only in the intended tenant VRF and the correct L3 VNI or service context.
  3. Customer-specific VPN routes remain in the authorized routing context and other carrier customers cannot import them.
  4. Peak-load packet captures retain the expected markings and voice delay and loss remain inside the service objective.

Explanation

Correct Answer

A:

A host migration test updates the remote PE forwarding location without persistent duplicate MAC forwarding. This confirms the approved response: Validate EVPN MAC mobility extended communities and accept the newer sequence state under supported mobility procedures. It is relevant because: EVPN MAC mobility uses sequence information to resolve competing advertisements for a moving endpoint.

Incorrect Answers

B:

Route readback shows the prefix only in the intended tenant VRF and the correct L3 VNI or service context. This would validate ANOTHER scenario: A provider imports an EVPN Type-5 IP prefix into the wrong VRF because a route-target policy matches a customer label instead of the service's approved tenant RT. The specific correction here is: Validate EVPN MAC mobility extended communities and accept the newer sequence state under supported mobility procedures.

C:

Customer-specific VPN routes remain in the authorized routing context and other carrier customers cannot import them. This would validate ANOTHER scenario: A wholesale carrier provides carrier-supporting-carrier transport, but a subcontractor PE advertises customer routes into the infrastructure global table rather than using labeled backbone service separation. The specific correction here is: Validate EVPN MAC mobility extended communities and accept the newer sequence state under supported mobility procedures.

D:

Peak-load packet captures retain the expected markings and voice delay and loss remain inside the service objective. This would validate ANOTHER scenario: A provider classifies customer voice using DSCP EF at ingress but a later output policy remarks it to best effort, causing jitter under congestion. The specific correction here is: Validate EVPN MAC mobility extended communities and accept the newer sequence state under supported mobility procedures.

Question 207

A provider troubleshooting note states: Two PEs establish BGP EVPN but remote MAC mobility updates are ignored because a device keeps an older sequence number as authoritative. Which mechanism is central?

  1. CSC designs carry another provider's traffic through a backbone without exposing all downstream customer routes into the carrier core.
  2. EVPN MAC mobility uses sequence information to resolve competing advertisements for a moving endpoint.
  3. Inter-AS VPN models differ in whether VRFs, labeled IPv4 or VPNv4 NLRI are exchanged at the border.
  4. Dual-stack VPN services require address-family-specific interfaces and MP-BGP signaling.

Explanation

Correct Answer

B:

EVPN MAC mobility uses sequence information to resolve competing advertisements for a moving endpoint. This explains the investigated issue: Two PEs establish BGP EVPN but remote MAC mobility updates are ignored because a device keeps an older sequence number as authoritative. The approved corrective response is: Validate EVPN MAC mobility extended communities and accept the newer sequence state under supported mobility procedures.

Incorrect Answers

A:

CSC designs carry another provider's traffic through a backbone without exposing all downstream customer routes into the carrier core. That explains a DIFFERENT scenario: A wholesale carrier provides carrier-supporting-carrier transport, but a subcontractor PE advertises customer routes into the infrastructure global table rather than using labeled backbone service separation. The mechanism to prioritize for this question is: EVPN MAC mobility uses sequence information to resolve competing advertisements for a moving endpoint.

C:

Inter-AS VPN models differ in whether VRFs, labeled IPv4 or VPNv4 NLRI are exchanged at the border. That explains a DIFFERENT scenario: An inter-AS L3VPN reaches the first provider but customer prefixes vanish at the AS boundary because VPNv4 routes and label context are not exchanged under the chosen inter-AS model. The mechanism to prioritize for this question is: EVPN MAC mobility uses sequence information to resolve competing advertisements for a moving endpoint.

D:

Dual-stack VPN services require address-family-specific interfaces and MP-BGP signaling. That explains a DIFFERENT scenario: An enterprise customer is promised IPv6 VPN reachability but the PE provisions only VPNv4 MP-BGP and v4 VRF interfaces. The mechanism to prioritize for this question is: EVPN MAC mobility uses sequence information to resolve competing advertisements for a moving endpoint.

Question 208

To prevent recurrence of this provider network issue: Two PEs establish BGP EVPN but remote MAC mobility updates are ignored because a device keeps an older sequence number as authoritative. Which control should be retained?

  1. Document the selected inter-AS option and verify service labels at each boundary.
  2. Audit tenant RT policies for EVPN IP prefix advertisements.
  3. Run controlled host-movement tests after EVPN control-plane upgrades.
  4. Audit per-hop QoS markings and queue drops during service activation.

Explanation

Correct Answer

C:

Run controlled host-movement tests after EVPN control-plane upgrades. This helps prevent recurrence of the issue: Two PEs establish BGP EVPN but remote MAC mobility updates are ignored because a device keeps an older sequence number as authoritative. Acceptance evidence should be: A host migration test updates the remote PE forwarding location without persistent duplicate MAC forwarding.

Incorrect Answers

A:

Document the selected inter-AS option and verify service labels at each boundary. That is a sensible control for ANOTHER scenario: An inter-AS L3VPN reaches the first provider but customer prefixes vanish at the AS boundary because VPNv4 routes and label context are not exchanged under the chosen inter-AS model. It is less targeted to this issue than: Run controlled host-movement tests after EVPN control-plane upgrades.

B:

Audit tenant RT policies for EVPN IP prefix advertisements. That is a sensible control for ANOTHER scenario: A provider imports an EVPN Type-5 IP prefix into the wrong VRF because a route-target policy matches a customer label instead of the service's approved tenant RT. It is less targeted to this issue than: Run controlled host-movement tests after EVPN control-plane upgrades.

D:

Audit per-hop QoS markings and queue drops during service activation. That is a sensible control for ANOTHER scenario: A provider classifies customer voice using DSCP EF at ingress but a later output policy remarks it to best effort, causing jitter under congestion. It is less targeted to this issue than: Run controlled host-movement tests after EVPN control-plane upgrades.

Question 209

At a multi-tenant data transport provider, an engineering review finds: A carrier sells an E-Tree service with root and leaf sites but accidentally permits leaf-to-leaf bridging, exposing isolated branch traffic. Which change most directly corrects the service problem?

  1. Apply the service's root-leaf forwarding restrictions at the correct bridge-domain and UNI attachment points.
  2. Terminate the provider backbone encapsulation at the correct I-component/B-component service edge.
  3. Correct the CFM maintenance domain, association and MEP identifiers for the intended service.
  4. Use IGMPv3 source-specific membership where required and align PIM-SSM source/group forwarding.

Explanation

Correct Answer

A:

Apply the service's root-leaf forwarding restrictions at the correct bridge-domain and UNI attachment points. This directly addresses the fictional service-provider network case: A carrier sells an E-Tree service with root and leaf sites but accidentally permits leaf-to-leaf bridging, exposing isolated branch traffic. The technical mechanism is: E-Tree Ethernet service enforces a rooted multipoint relationship rather than unrestricted multipoint reachability. Verify success by: Root-to-leaf tests pass and direct leaf-to-leaf attempts are blocked.

Incorrect Answers

B:

Terminate the provider backbone encapsulation at the correct I-component/B-component service edge. This would respond to a DIFFERENT fictional service-provider network issue: A carrier backbone applies provider bridging with 802.1ah MAC-in-MAC but its edge fails to strip the outer backbone header, so customer switches receive unknown backbone addresses. It does not directly address the current situation: A carrier sells an E-Tree service with root and leaf sites but accidentally permits leaf-to-leaf bridging, exposing isolated branch traffic.

C:

Correct the CFM maintenance domain, association and MEP identifiers for the intended service. This would respond to a DIFFERENT fictional service-provider network issue: An Ethernet OAM continuity check reports an unexpected remote maintenance endpoint and operators trust the wrong circuit when troubleshooting an outage. It does not directly address the current situation: A carrier sells an E-Tree service with root and leaf sites but accidentally permits leaf-to-leaf bridging, exposing isolated branch traffic.

D:

Use IGMPv3 source-specific membership where required and align PIM-SSM source/group forwarding. This would respond to a DIFFERENT fictional service-provider network issue: A multicast source sends video to an SSM group, but an access router uses IGMPv2 joins without source specification and receivers see no stream. It does not directly address the current situation: A carrier sells an E-Tree service with root and leaf sites but accidentally permits leaf-to-leaf bridging, exposing isolated branch traffic.

Question 210

For a multi-tenant data transport provider, operators addressed: A carrier sells an E-Tree service with root and leaf sites but accidentally permits leaf-to-leaf bridging, exposing isolated branch traffic. What is the strongest acceptance evidence?

  1. A captured customer UNI frame contains only the expected customer Ethernet header while provider core frames carry backbone identifiers.
  2. Root-to-leaf tests pass and direct leaf-to-leaf attempts are blocked.
  3. A double-tagged test from each customer arrives at the correct logical service with its contracted inner VLAN intact.
  4. An IPTV test stream reaches all authorized receivers while transit replication follows the intended efficient tree.

Explanation

Correct Answer

B:

Root-to-leaf tests pass and direct leaf-to-leaf attempts are blocked. This confirms the approved response: Apply the service's root-leaf forwarding restrictions at the correct bridge-domain and UNI attachment points. It is relevant because: E-Tree Ethernet service enforces a rooted multipoint relationship rather than unrestricted multipoint reachability.

Incorrect Answers

A:

A captured customer UNI frame contains only the expected customer Ethernet header while provider core frames carry backbone identifiers. This would validate ANOTHER scenario: A carrier backbone applies provider bridging with 802.1ah MAC-in-MAC but its edge fails to strip the outer backbone header, so customer switches receive unknown backbone addresses. The specific correction here is: Apply the service's root-leaf forwarding restrictions at the correct bridge-domain and UNI attachment points.

C:

A double-tagged test from each customer arrives at the correct logical service with its contracted inner VLAN intact. This would validate ANOTHER scenario: A wholesale Ethernet access provider uses an 802.1ad QinQ handoff but pops both tags before the customer PE, collapsing two independent service instances. The specific correction here is: Apply the service's root-leaf forwarding restrictions at the correct bridge-domain and UNI attachment points.

D:

An IPTV test stream reaches all authorized receivers while transit replication follows the intended efficient tree. This would validate ANOTHER scenario: A provider deploys mVPN for an IPTV customer but replicates each source stream individually to every access PE even when a shared provider multicast tree is available. The specific correction here is: Apply the service's root-leaf forwarding restrictions at the correct bridge-domain and UNI attachment points.