* IaaS (Infrastructure as a Service) provides virtualized compute, storage, and networking resources.
* The enterprise manages the OS, applications, and middleware, while the cloud provider manages the underlying hardware and virtualization.
* This directly addresses hardware issues while allowing control over proprietary applications and OS management.
Why other options are incorrect:
* A: SaaS delivers fully managed applications, no control over OS.
* B: PaaS abstracts even the OS layer; limited control for proprietary needs.
* D: Hybrid is a deployment model, not a cloud service type.

* C (Synchronous replication across data centers):Synchronous replication ensures zero or near-zero data loss (very low RPO), as data is written simultaneously to both sites. For an RPO of under 10 seconds, synchronous replication is mandatory.
Other options explained:
* A: Asynchronous replication may result in higher RPO.
* B/D: Single site designs introduce single points of failure for business continuity.

When data center fabrics are extended across multiple private and public clouds, as in hybrid or multi-cloud designs, enterprises benefit from:
* C. Ability to place workloads across clouds: Application and workload mobility is a key outcome of interconnected data center fabrics. It supports disaster recovery, scaling, and cost optimization strategies.
* D. Centralized visibility: Modern SDN/cloud-integrated platforms offer centralized control and monitoring across domains, giving IT teams end-to-end insight regardless of workload location.
These principles support the CCDE v3.1 goals for cloud-aligned architecture, which promotes flexibility, operational simplicity, and global-scale services.
Why other options are incorrect:
* A: Enhanced security is a benefit but not guaranteed simply by interconnecting clouds; it depends on the actual security controls in place.
* B: Cloud deployments may compromise data and network ownership, especially in public models.
* E: Cloud mobility is typically bidirectional when fully designed; unidirectional behavior is limiting and not an intended design goal.

* Traffic shaping buffers excess traffic and smooths traffic bursts, which is essential for DaaS traffic sensitive to periodic link congestion across WAN circuits.
* It helps ensure consistent, predictable performance under fluctuating WAN conditions.
Why other options are incorrect:
* A: Tail drop leads to congestion and packet loss.
* C: WRED is used for congestion avoidance, but not ideal for real-time DaaS traffic shaping.
* D: Policing drops excess traffic instead of buffering, worsening DaaS disconnections.

Cisco FabricPath is a Layer 2 multipath technology that blends traditional Layer 2 Ethernet with routing technologies to enable loop-free forwarding and scalability. Two critical mechanisms used to mitigate loops:
* C. RPF (Reverse Path Forwarding) Check: FabricPath applies a reverse path forwarding check, similar to multicast, to verify the source of a frame and discard duplicates arriving on unexpected paths.
* D. TTL Header: FabricPath adds a Time-To-Live (TTL) field to Layer 2 frames, which is not present in traditional Ethernet. This prevents indefinite circulation of frames by limiting their lifetime in the network-much like in IP.
These elements allow FabricPath to prevent broadcast storms and loops in multipath Layer 2 topologies, addressing legacy STP limitations with efficient loop-avoidance methods.