You have an Azure Functions microservice named App1 running on the Consumption plan that uses an Azure Queue Storage trigger. You will migrate App1 to an Azure Kubernetes Service (AKS) cluster. The AKS environment must (a) use the same event-driven scaling behavior as the current deployment and (b) support both kubenet and Azure CNI networking. Which two actions should you perform? (Select two.)

To maintain event-driven scaling behavior for an Azure Functions microservice migrated to AKS, you need Kubernetes-based Event Driven Autoscaling (KEDA). KEDA extends Kubernetes to allow event sources like Azure Queue Storage to drive scaling, directly addressing requirement (a). KEDA integrates with the Horizontal Pod Autoscaler (HPA) to scale pods based on metrics from event sources. Therefore, configuring the HPA is also necessary to define the scaling policies once KEDA provides the event-driven metrics. The AKS cluster autoscaler scales the underlying node pools, not individual pods based on event queues, so it doesn't directly address event-driven pod scaling. Virtual Kubelet and the virtual node add-on enable running pods on Azure Container Instances (ACI) to provide burst capacity, which is a different scaling mechanism than event-driven scaling for the microservice itself.