# Explanation:
* A: Layer 2 ACLs can block or allow specific MAC or IP traffic right at the switchport.
* C: Containing lateral attacks-Layer 2 ACLs help block unauthorized east-west traffic between hosts within the same VLAN.
Incorrect options:
* B: Contextual filtering is associated with next-gen firewalls or Layer 7 inspection.
* D: ACLs add processing load, not reduce it.
* E: VLAN intercept is not a valid Cisco term for ACL application.

Mutual redistribution between different routing protocols can cause routing loops and suboptimal routing due to:
* Route feedback loops (routes being re-imported back into the originating protocol).
* Inconsistent administrative distances (AD) leading to selection of suboptimal paths.
Two key mechanisms avoid these issues:
* A. Administrative Distance (AD) manipulation: Ensures that one protocol is consistently preferred over the other when duplicate routes exist.
* C. Route tagging: Assigns tags to redistributed routes to identify the source of the route and prevent re- importation (looping) into the originating protocol.
These methods align with CCDE v3.1 principles for multi-protocol control plane design and stability.
Why other options are incorrect:
* B & F: Matching routes or process IDs do not directly prevent loops or suboptimal routing.
* D is a duplicate of C.
* E: Filtering helps but is reactive, not a comprehensive prevention mechanism.
-

Explanation:
1 - target 4
2 - target 5
3 - target 1
4 - target 6
5 - target 2
6 - target 3

* D (Queue thresholding on the host subinterface):Protects CPU resources by limiting the amount of control plane traffic destined to the router itself.
* E (Port filtering on the host subinterface):Allows fine-grained filtering of control plane traffic based on specific protocols or ports, protecting sensitive processes like routing protocols or management access.
Other options explained:
* A, B, C: Transit subinterfaces protect forwarding plane transit traffic, not traffic destined to the control plane.

* PBR overrides the normal routing table behavior, potentially leading to microloops during reconvergence because forwarding decisions are based on policies rather than updated routing tables.
* During fast topology changes, PBR decisions may not adapt as quickly as dynamic routing protocols, causing brief routing inconsistencies.
Why other options are incorrect:
* A: PBR can add complexity but does not inherently limit scalability.
* C/D: PBR does not directly affect convergence speed but can introduce inconsistency.