Keda uses ScaledObjects to drive scaling. Which statement best describes its relationship to ScaledObjects?

Keda uses ScaledObjects to drive scaling. Which statement best describes its relationship to ScaledObjects?

• A. It runs without any objects
• B. It is a monitoring tool
• C. It uses ScaledObjects to drive scaling
• D. It is a replacement for the Kubernetes API

Answer: (C)

KEDA acts as the controller that reads ScaledObject resources and applies scaling to the specified workload. A ScaledObject defines which deployment (or other scale target) to scale and the triggers that determine when to scale, such as queue depth or metric values. KEDA continuously evaluates those triggers and updates the target’s replica count accordingly, within any min/max limits. That means ScaledObjects are the instructions KEDA uses to drive scaling, making this relationship the defining one. It isn’t just a monitoring tool, it isn’t a replacement for the Kubernetes API, and it requires a ScaledObject to know what to scale.

KEDA acts as the controller that reads ScaledObject resources and applies scaling to the specified workload. A ScaledObject defines which deployment (or other scale target) to scale and the triggers that determine when to scale, such as queue depth or metric values. KEDA continuously evaluates those triggers and updates the target’s replica count accordingly, within any min/max limits. That means ScaledObjects are the instructions KEDA uses to drive scaling, making this relationship the defining one. It isn’t just a monitoring tool, it isn’t a replacement for the Kubernetes API, and it requires a ScaledObject to know what to scale.