Correct Answer: B and D

We need to configure autoscaler for the AKS cluster. We do not want to scale Kubernetes pods, so kubectl command is not needed.

A: kubectl command is used for configuring Kubernetes and not AKS cluster.

B: The az aks command is used for the AKS cluster configuration.

C: Set-AzVm cmdlet is used for VMs.

D: Azure portal, under node pools, press scale, then choose auto scale.

E: Set-AzAks, creates or updates an AKS cluster, the correct cmdlet is Set-AzAksCluster.

AKS clusters can scale in one of two ways:

- The cluster autoscaler watches for pods that can't be scheduled on nodes because of resource constraints. The cluster then automatically increases the number of nodes.

- The horizontal pod autoscaler uses the Metrics Server in a Kubernetes cluster to monitor the resource demand of pods. If an application needs more resources, the number of pods is automatically increased to meet the demand.

Reference:

https://docs.microsoft.com/en-us/azure/aks/cluster-autoscaler

C is correct.

You already build an image in your machine.

The command az acr build will enqueue a new build task in acr https://docs.microsoft.com/en-us/cli/azure/acr?view=azure-cli-latest#az-acr-build

Correct Answer: A

Placement Groups is a capability to achieve co-location of your Azure Infrastructure as a Service (IaaS) resources and low network latency among them, for improved application performance.

Azure proximity placement groups represent a new logical grouping capability for your Azure Virtual Machines, which in turn is used as a deployment constraint when selecting where to place your virtual machines. In fact, when you assign your virtual machines to a proximity placement group, the virtual machines are placed in the same data center, resulting in lower and deterministic latency for your applications.

The VMSS should share the same region, even it should be the same zone as proximity groups are located in the same data center. Accordingly, it should be proximity 2 only.

Reference:

https://azure.microsoft.com/en-us/blog/introducing-proximity-placement-groups

Correct Answer: B - No

From the RG1 blade, click Deployments. You see a history of deployment for the resource group.

Reference:

https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/template-tutorial-create-first-template?tabs=azure-powershell