Comprehensive and Detailed Explanation:
* D: The most effective solution is to have Site-X advertise a more specific (longer) prefix (e.g.,
100.75.10.0/24), which allows external BGP routers to prefer Site-X over Site-Y. This ensures traffic destined for Site-X flows directly to it, preserving symmetry. Additionally, control plane coordination between R1 and R2 ensures proper routing consistency and minimizes the risk of loops or misdirection.
Other options:
* A: Using BGP MED works within the same AS; it is often ignored by external ISPs.
* B: Replicating firewall behavior does not address the routing issue.
* C: DNS manipulation is a workaround-not a scalable or robust design solution.
This solution is consistent with BGP best practices and CCDE v3.1 guidance on traffic engineering and policy- based routing.

Comprehensive and Detailed Explanation:
* C: Moving workloads or backup/recovery functions to cloud platforms reduces capital expenditure by avoiding the cost of physical infrastructure, data centers, and maintenance. Cloud-based DRaaS (Disaster Recovery as a Service) offers scalability, resilience, and cost efficiency aligned with an OPEX model.
Other options:
* A and B are security and software lifecycle tasks, not cost-effective DR strategies.
* D increases CAPEX by building and maintaining additional infrastructure.

Comprehensive and Detailed Explanation:
* A: QoS (Quality of Service) helps preserve performance for critical applications when only one link is available by prioritizing high-value traffic. This solution works within existing infrastructure-meeting the "no additional CAPEX" requirement.
Other options:
* B and C introduce new hardware or services-thus increase CAPEX.
* D: Dynamic routing helps with failover but doesn't solve the bandwidth issue under failure conditions; QoS does.

To achieve subsecond convergence in IS-IS or OSPF networks and quickly detect both:
* Link-layer failures (e.g., interface flaps)
* Control-plane adjacency loss
The best solution is:
* C. BFD (Bidirectional Forwarding Detection): A lightweight protocol that enables subsecond failure detection, independent of the IGP timers, by establishing fast detection sessions over forwarding paths.
This is widely deployed in high-performance networks to accelerate convergence without compromising routing stability.
Why other options fall short:
* A. Debounce timers delay interface-down events (not suitable when fast detection is required).
* B. Fast hellos affect hello interval but are still slower and CPU-intensive.
* D. LSP fast flood improves LSP propagation but doesn't address failure detection speed.
This solution is central to CCDE "Protocol Design Implications" where rapid failure detection and recovery drive the convergence architecture.

* CPPr (Control Plane Protection) allows classification and policing of traffic destined for the control plane at a more granular level than CoPP.
* It protects the router from control plane attacks such as reconnaissance scans and DoS targeting interfaces and sub-interfaces.
Why other options are incorrect:
* A: MPP protects management plane access, not data/control plane protection.
* C: CoPP offers global control plane policing but lacks CPPr's granularity.
* D: DPP is not a standard Cisco security mechanism.