The SDN architecture separates the control plane from the data plane. In this model, the SDN controller is the central element responsible for:
* Receiving application intent via northbound APIs
* Translating intent into traffic policies
* Communicating with infrastructure devices using southbound APIs
The SDN controller enforces policies such as path selection, QoS, and access control rules across the network fabric, ensuring traffic flows align with administrator-defined logic. Neither northbound nor southbound APIs enforce policy themselves; they serve as communication interfaces.
The packet forwarding engine (Option A) simply performs data-plane functions based on instructions, but does not interpret or apply policies.

* Public cloud offers scalability, flexibility, and consumption-based pricing, which directly reduces capital expenditures (CAPEX) and minimizes operational burden (less IT staff needed for infrastructure maintenance).
* Public cloud eliminates upfront hardware investments and shifts cost to predictable operational expenses.
* Public cloud providers handle hardware maintenance, upgrades, and scalability, making it highly cost- effective for government agencies with fluctuating workloads.
Why other options are incorrect:
* A: On-premises increases CAPEX and requires significant IT staff.
* B: Private cloud reduces some OpEx but still requires infrastructure management and higher CAPEX.
* D: Hybrid cloud increases complexity and operational costs.
-

Explanation:
A picture containing table Description automatically generated
IPv4:
Host Registration - IGMP
Router Registration - PIM-DM, PIM-SM, SSM, BIDIR
Inter-Domain Source Discovery - MSDP
IPv6:
Host Registration - MLD
Router Registration - PIM-SM, SSM, BIDIR

Comprehensive and Detailed Explanation:
* C: Before migrating to the cloud, organizations must conduct a thorough assessment of their current infrastructure. This includes evaluating applications, workloads, network topology, security posture, compliance requirements, and interdependencies. This step is essential for planning migration phases, identifying risks, and aligning architecture to business needs.
Other options:
* A: SASE (Secure Access Service Edge) may be a future consideration but is not foundational to cloud readiness.
* B: WAN optimization is important but comes after understanding infrastructure needs.
* D: RPO/RTO calculations are part of disaster recovery, not initial cloud migration planning.

The hub CE router is receiving IP SLA probes from all spokes, processing and responding to every request.
As more spokes are added, the CPU workload on the hub increases exponentially due to:
* Processing incoming IP SLA packets.
* Generating and transmitting responses.
Monitoring CPU utilization at the hub ensures early detection of processing bottlenecks that could impact SLA accuracy and overall performance - a core CCDE v3.1 business-driven design consideration in centralized measurement architectures.
Why other options are incorrect:
* A & B: Spoke resources are minimally taxed.
* D: Buffer usage isn't the main limiting factor for IP SLA responsiveness.