* B (Weighted Random Early Detection - WRED):WRED proactively drops packets before buffers are full to avoid global synchronization in TCP traffic and prevent tail drops, thus improving overall TCP performance under congestion.
Other options explained:
* A: WFQ provides fairness but does not proactively avoid congestion.
* C: LLQ is for delay-sensitive traffic, not congestion avoidance for TCP.
* D: FIFO offers no QoS or congestion control.

End-to-end network visibility is often hindered by:
* Siloed monitoring and logging systems
* Vendor-specific platforms that don't integrate
* Inconsistent telemetry across domains (e.g., WAN, DC, Cloud)
Too many disparate solutions lead to data fragmentation, blind spots, and lack of unified analytics. This makes correlating threats and verifying policy enforcement complex. Overlapping controls (A) and manual processes (C) are operational concerns but don't directly obstruct architectural visibility.
The CCDE blueprint emphasizes cross-domain visibility, consistent policy enforcement, and integration as central to a secure and scalable network design.

InBidirectional PIM, redundancy for Rendezvous Points (RPs) is provided through thePhantom RP mechanism. This setup offers HA by:
* A. Using two phantom RP addresses: You configure two RPs with the same virtual RP address but advertise them with loopback interfaces having different subnet masks. These phantom RPs allow seamless failover between active and standby RPsdatatracker.ietf.org+14arubanetworking.hpe.
com+14examtopics.com+14ciscolive.com+3examtopics.com+3ccie-sp.gitbook.io+3learnwithsalman.
com+4lostintransit.se+4learningnetwork.cisco.com+4.
* F. Controlling routing through a longest match prefix: The active RP is chosen based on unicast routing - the loopback with the longest prefix match to the RP address is preferred. If that RP fails, the IGP converges and the standby with the next-longest prefix becomes activearubanetworking.hpe.com.
This combined mechanism aligns with CCDE v3.1 design principles by ensuring multicast HA with minimal complexity - no MSDP involvement and leveraging existing IGP behaviors.
Why other options are incorrect:
* B&D: Changing administrative distance or protocol advertisement doesn't inherently establish redundancy in Bidir-PIM RP selection.
* C: Static mroutes are static and don't support dynamic redundancy or failover.
* E: Anycast RP with MSDP is not supported or needed in Bidir-PIM environments.
This design ensures robust, seamless RP redundancy using phantom RPs with longest-prefix selection logic, remaining cost-effective and operationally concise.
https://community.cisco.com/t5/networking-knowledge-base/rp-redundancy-with-pim-bidir-phantom-rp/ta-p
/3117191

* Cisco SD-WAN Cloud OnRamp SaaS optimizes cloud application performance by dynamically measuring SaaS application paths from multiple branch edges toward the Microsoft 365 cloud.
* It automatically selects the best-performing path, continuously monitors SLA metrics (latency, loss, jitter), and dynamically reroutes based on real-time performance.
* This directly addresses SaaS resiliency across multiple ISPs with minimal manual intervention and is aligned with CCDE v3.1 SD-WAN design methodologies for SaaS optimization.
Why other options are incorrect:
* A: Cloud OnRamp gateway is for IaaS optimization (AWS, Azure), not SaaS.
* B: Cloud OnRamp SWG (Secure Web Gateway) is for internet-bound security inspection, not SaaS path optimization.
* C: "Cloud OnRamp" alone is too general; SaaS is the specific solution for this SaaS use case.