You have an Azure Functions microservice app named App1 that is hosted in the Consumption plan. App1 uses an Azure Queue Storage trigger. You plan to migrate App1 to an Azure Kubernetes Service…

Question

Options

• AConfigure the horizontal pod autoscaler.
• BInstall Virtual Kubelet.
• CConfigure the AKS cluster autoscaler.
• DConfigure the virtual node add-on.
• EInstall Kubernetes-based Event Driven Autoscaling (KEDA).

• A
  74% (28)
• B
  5% (2)
• C
  8% (3)
• D
  13% (5)

Explanation

https://learn.microsoft.com/en-us/azure/aks/concepts-scale#horizontal-pod-autoscaler Kubernetes uses the horizontal pod autoscaler (HPA) to monitor the resource demand and automatically scale the number of replicas. By default, the horizontal pod autoscaler checks the Metrics API every 15 seconds for any required changes in replica count, but the Metrics API retrieves data from the Kubelet every 60 seconds. Effectively, the HPA is updated every 60 seconds. When changes are required, the number of replicas is increased or decreased accordingly. Horizontal pod autoscaler works with AKS clusters that have deployed the Metrics Server for Kubernetes 1.8+. https://learn.microsoft.com/en-us/azure/aks/keda-about Kubernetes Event-driven Autoscaling (KEDA) is a single-purpose and lightweight component that strives to make application autoscaling simple and is a CNCF Incubation project. It applies event-driven autoscaling to scale your application to meet demand in a sustainable and cost-efficient manner with scale-to-zero.

No community discussion yet for this question.