Why managed Kubernetes matters in Azure - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a managed Kubernetes cluster in Azure.

Azure

az aks create --resource-group myResourceGroup --name myAKSCluster --node-count [1] --enable-addons monitoring --generate-ssh-keys

Drag options to blanks, or click blank then click option'

A3

B0

Cone

D-1

Attempts:

3 left

💡 Hint

Common Mistakes

Using zero or negative numbers for node count

Using words instead of numbers

The --node-count option sets the number of nodes in the cluster. It must be a positive integer like 3.

2fill in blank

medium

Complete the command to get credentials for your AKS cluster.

Azure

az aks get-credentials --resource-group myResourceGroup --name [1]

Drag options to blanks, or click blank then click option'

AmyAKSCluster

BmyResourceGroup

Cdefault

Dcluster1

Attempts:

3 left

💡 Hint

Common Mistakes

Using the resource group name instead of cluster name

Using default or unrelated names

The --name option requires the AKS cluster name, such as myAKSCluster.

3fill in blank

hard

Fix the error in the command to scale the AKS cluster nodes.

Azure

az aks scale --resource-group myResourceGroup --name myAKSCluster --node-count [1]

Drag options to blanks, or click blank then click option'

A-3

Bzero

C5

Dten

Attempts:

3 left

💡 Hint

Common Mistakes

Using zero or negative numbers

Using words instead of numbers

The --node-count must be a positive integer. Using 5 scales the cluster to 5 nodes.

4fill in blank

hard

Fill both blanks to enable the HTTP application routing addon.

Azure

az aks enable-addons --resource-group myResourceGroup --name myAKSCluster --addons [1] --app-routing-dns-name [2]

Drag options to blanks, or click blank then click option'

Ahttp_application_routing

Bmonitoring

Cmyapp.example.com

Ddefaultdns

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong addon names

Using generic DNS names

The addon name for HTTP routing is http_application_routing. The DNS name is a custom domain like myapp.example.com.

5fill in blank

hard

Fill all three blanks to create a node pool with spot instances.

Azure

az aks nodepool add --resource-group myResourceGroup --cluster-name myAKSCluster --name [1] --priority [2] --spot-max-price [3]

Drag options to blanks, or click blank then click option'

Aspotpool

BSpot

C-1

DRegular

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong priority values

Using positive numbers for max price

The node pool name can be spotpool. The priority for spot instances is Spot. The max price of -1 means the max price is the current on-demand price.

Practice

1. What is the main benefit of using managed Kubernetes services like Azure Kubernetes Service (AKS)?

easy

A. It handles infrastructure tasks like updates and scaling automatically.

B. It requires you to manually configure all cluster components.

C. It only supports Windows containers.

D. It eliminates the need for containerization.

Solution

1. Step 1: Understand managed Kubernetes purpose

   Managed Kubernetes services automate infrastructure tasks such as updates, scaling, and security.

2. Step 2: Compare options

   Options B, C, and D are incorrect because they either require manual setup, limit container types, or misunderstand containerization benefits.

3. Final Answer:

   It handles infrastructure tasks like updates and scaling automatically. -> Option A

4. Quick Check:

   Managed Kubernetes automates infrastructure tasks = A [OK]

Hint: Managed means cloud handles setup and scaling for you [OK]

Common Mistakes:

• Thinking you must manage all cluster setup manually
• Believing managed Kubernetes only supports certain container types
• Confusing containerization with Kubernetes management

2. Which of the following is the correct Azure CLI command to create a managed Kubernetes cluster named myCluster in resource group myGroup?

easy

A. az aks create --resource-group myGroup --name myCluster --node-count 3 --enable-addons monitoring

B. az k8s create --group myGroup --cluster myCluster --nodes 3

C. az aks deploy --resource-group myGroup --cluster-name myCluster --count 3

D. az container create --resource-group myGroup --name myCluster --count 3

Solution

1. Step 1: Identify correct Azure CLI syntax for AKS creation

   The correct command uses az aks create with parameters --resource-group, --name, and --node-count.

2. Step 2: Evaluate options

   az aks create --resource-group myGroup --name myCluster --node-count 3 --enable-addons monitoring matches the correct syntax. Options B, C, and D use incorrect commands or parameters.

3. Final Answer:

   az aks create --resource-group myGroup --name myCluster --node-count 3 --enable-addons monitoring -> Option A

4. Quick Check:

   Correct Azure CLI command for AKS creation = A [OK]

Hint: Use 'az aks create' with resource group and name [OK]

Common Mistakes:

• Using 'az k8s' instead of 'az aks'
• Mixing parameters like --cluster-name instead of --name
• Confusing container creation with cluster creation

3. Given the following Azure CLI command output snippet after creating an AKS cluster, what does the nodeResourceGroup field represent?

{
  "name": "myCluster",
  "nodeResourceGroup": "MC_myGroup_myCluster",
  "kubernetesVersion": "1.24.6",
  "provisioningState": "Succeeded"
}

medium

A. The resource group for Azure Active Directory.

B. The resource group where the AKS cluster nodes are deployed.

C. The resource group for Azure Container Registry.

D. The resource group where user applications are stored.

Solution

1. Step 1: Understand nodeResourceGroup meaning

   The nodeResourceGroup is a system-generated resource group that contains the infrastructure resources for the AKS nodes.

2. Step 2: Eliminate incorrect options

   Options A, B, and C refer to unrelated resource groups for identity services, user applications, or container registry.

3. Final Answer:

   The resource group where the AKS cluster nodes are deployed. -> Option B

4. Quick Check:

   nodeResourceGroup = AKS nodes resource group [OK]

Hint: nodeResourceGroup holds cluster node resources [OK]

Common Mistakes:

• Confusing nodeResourceGroup with app resource group
• Assuming it relates to container registry
• Mixing it up with identity or directory groups

4. You tried to scale your AKS cluster using the command az aks scale --resource-group myGroup --name myCluster --node-count 5 but got an error. What is the most likely cause?

medium

A. The az aks scale command does not exist; you should use az aks update instead.

B. You must delete the cluster before changing node count.

C. Scaling is not supported on managed Kubernetes clusters.

D. You need to specify the node pool name with --nodepool-name when scaling.

Solution

1. Step 1: Check correct command usage for scaling AKS

   Scaling requires specifying the node pool name using --nodepool-name with az aks scale.

2. Step 2: Analyze options

   The az aks scale command does not exist; you should use az aks update instead. is wrong because az aks scale exists. Scaling is not supported on managed Kubernetes clusters. is false; scaling is supported. You must delete the cluster before changing node count. is incorrect; no need to delete cluster.

3. Final Answer:

   You need to specify the node pool name with --nodepool-name when scaling. -> Option D

4. Quick Check:

   Scaling AKS requires node pool name = B [OK]

Hint: Always include --nodepool-name when scaling nodes [OK]

Common Mistakes:

• Omitting --nodepool-name parameter
• Thinking scaling is unsupported
• Trying to delete cluster to scale nodes

5. You want to ensure your AKS cluster automatically updates to the latest patch version for security without downtime. Which managed Kubernetes feature should you enable?

hard

A. Disable node auto-scaling

B. Manual upgrade triggered by user only

C. Cluster auto-upgrade with surge upgrades enabled

D. Use a single-node cluster to avoid complexity

Solution

1. Step 1: Identify feature for automatic, zero-downtime upgrades

   Cluster auto-upgrade with surge upgrades allows patch updates with minimal downtime by upgrading nodes in batches.

2. Step 2: Evaluate other options

   Manual upgrade requires user action, disabling auto-scaling doesn't affect upgrades, and single-node clusters increase downtime risk.

3. Final Answer:

   Cluster auto-upgrade with surge upgrades enabled -> Option C

4. Quick Check:

   Auto-upgrade with surge = zero downtime updates [OK]

Hint: Enable auto-upgrade with surge for smooth updates [OK]

Common Mistakes:

• Relying on manual upgrades only
• Disabling auto-scaling thinking it helps upgrades
• Using single-node clusters for production