The correct option is Resource Reservation. This SLA clause requires the cloud provider to set aside a defined amount of CPU and memory so that those resources remain available to your production workloads when needed.

Reservations are implemented as dedicated or zonal capacity at the provider level and they prevent overcommitment and noisy neighbor interference. In the SLA you should require explicit metrics such as vCPU count, RAM size, zones or regions covered, time windows for the reservation, and measurable remedies such as service credits or failover commitments so the guarantee is actionable.

Resource Throttling is incorrect because throttling reduces or limits resource consumption under load and does not provide a guaranteed baseline of CPU or memory for your workloads.

Resource Sharing is incorrect because sharing refers to multi tenant pooling of resources and it does not provide exclusive reserved capacity unless a separate reservation mechanism is also specified.

Committed Use Contract is incorrect because it is primarily a billing or discount commitment for sustained usage and it does not by itself reserve physical or virtual capacity for your workloads.

Full AWS Practitioner Certification Question