Which of the following can be useful for protecting cloud customers from a denial-of-service (DoS) attack against another customer hosted in the same cloud?
Which of the following can be useful for protecting cloud customers from a denial-of-service (DoS) attack against another customer hosted in the same cloud?
Limits are useful for protecting cloud customers from a denial-of-service (DoS) attack against another customer hosted in the same cloud because they can cap the maximum amount of resources any single customer can consume. By enforcing these limits, the cloud provider ensures that other customers will still have access to their necessary resources, preventing a DoS scenario from impacting their services.
Correct Answer: A A reservation will typically guarantee to a cloud customer that they will have the minimum required resources necessary to power on and operate their services within the environment. Reservations also offer insurance against denial-of-service (DoS) attacks or other customers using such large amounts of resources that the cloud customer cannot operate their services.
how would the cloud platform guarantee the "reservation" when DoS attack running wild in that environment ? instead, if you "limit" each tenant to upper threshold level, it will make sure, cloud platform will have enough available resources to allocate to other tenants.
Limit is the appropriate answer, if the DoS here is referring to the over usage resources by one customer, and there by denying resource to another. If this referring to real DoS then again Reservation cannot stop it. So either way Reservation is incorrect.
I dont think so because, a Limit would will be the total amount of resources to be exhausted by the DoS, but, what guarantees that another customer will have the resources needed to run?, the reservation, so the reservation is what protects the other customers.
Nope, Reservations will protect against DDOS.
You and I are reading the question the same... if the attack is coming from one source (current cloud customer or not), a limit will eventually block that DOS attack. The question is poorly worded and should say: Which of the following can be useful for protecting cloud customers from a denial-of-service (DoS) attack WHEN another customer IS hosted in the same cloud? - Answer: Reservations
You and I are reading the question the same... if the attack is coming from one source (current cloud customer or not), a limit will eventually block that DOS attack. The question is poorly worded and should say: Which of the following can be useful for protecting cloud customers WHEN another customer faces a denial-of-service (DoS) attack hosted in the same cloud? - Answer: Reservations
Limits seem to be better...
Limits should be on the attacked customer. This question asks for the way to protect another customer. In general, you cannot limit other customers to protect a certain customer.
If a costumer has "limits" beyond the available "shares", they can consume resources intended to other costumers which can cause resource exhaustion. "Reservations" should prevent such exhaustion for other costumers though their resource requirements can no longer expand until this issue is fixed.
C: Limits
The concept of shares is used to arbitrate the issues associated with compute resource contention situations. Resource contention implies the existence of too many requests for resources based on the actual available resources currently in the system. If resource contention takes place, share values are used to prioritize compute resource access for all guests assigned a certain number of shares.
C Limits is the correct answer, Limits are put in order to throttle the services , hence preventing DOS attacks.
Limits all the way
Correct Answer : C In Cloud computing limits pertain to the constraints on resource usage for individual customers. By setting limits on the amount of resources (such as CPU, memory, bandwidth, etc.) each customer can consume, cloud providers can prevent any single customer from dominating resources and potentially affecting the performance of other customers.
Setting limits on resource usage can help prevent one cloud customer from monopolizing resources, which might inadvertently lead to a denial-of-service situation for other tenants sharing the same infrastructure. Limits cap the maximum amount of CPU, memory, or bandwidth any single customer can use, providing a safeguard against runaway resource consumption—whether from a misbehaving application or a targeted DoS attack.