Keda uses which construct to define scaling rules?

Keda uses which construct to define scaling rules?

• A. Deployments
• B. MetricsServer
• C. ScaledObjects
• D. StatefulSets

Answer: (C)

KEDA expresses its scaling behavior with a ScaledObject. This Custom Resource defines which Kubernetes workload to scale (scaleTargetRef) and the external triggers (such as queues, metrics, or events) that drive the scaling decisions. You can specify min and max replicas and even scale to zero when there’s no work. The actual workload might be a Deployment (or another resource type), but the rules that tell KEDA how to scale live in the ScaledObject. MetricsServer is used by the native HorizontalPodAutoscaler to gather metrics, not for KEDA’s external scaling rules. StatefulSets are just a type of workload and aren’t where KEDA stores its scaling policy. So, the construct used to define scaling rules is ScaledObject.

KEDA expresses its scaling behavior with a ScaledObject. This Custom Resource defines which Kubernetes workload to scale (scaleTargetRef) and the external triggers (such as queues, metrics, or events) that drive the scaling decisions. You can specify min and max replicas and even scale to zero when there’s no work. The actual workload might be a Deployment (or another resource type), but the rules that tell KEDA how to scale live in the ScaledObject. MetricsServer is used by the native HorizontalPodAutoscaler to gather metrics, not for KEDA’s external scaling rules. StatefulSets are just a type of workload and aren’t where KEDA stores its scaling policy. So, the construct used to define scaling rules is ScaledObject.