AKS cluster creation in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create an AKS cluster with the Azure CLI.

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'

A1

B0

C5

D3

Attempts:

3 left

💡 Hint

Common Mistakes

Setting node count to 0 causes an error because the cluster needs nodes.

Using a very high number unnecessarily increases cost.

The --node-count parameter sets the number of nodes in the AKS cluster. The minimum valid value is 1.

2fill in blank

medium

Complete the code to specify the Kubernetes version when creating the AKS cluster.

Azure

az aks create --resource-group myResourceGroup --name myAKSCluster --kubernetes-version [1] --node-count 2 --generate-ssh-keys

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

A1.25.6

Blatest

C1.18.14

Dstable

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'latest' or 'stable' causes the command to fail.

Using an unsupported version number.

The --kubernetes-version parameter requires a valid version string like '1.25.6'. 'latest' or 'stable' are not accepted values.

3fill in blank

hard

Fix the error in the command to enable the HTTP application routing addon.

Azure

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

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

Ahttp-routing

Bhttp_application_routing

Chttp-app-routing

Dhttpapplicationrouting

Attempts:

3 left

💡 Hint

Common Mistakes

Using dashes or no separators in addon names causes errors.

Misspelling the addon name.

The correct addon name for HTTP application routing is http_application_routing with underscores.

4fill in blank

hard

Fill both blanks to create an AKS cluster with a specific VM size and enable monitoring addon.

Azure

az aks create --resource-group myResourceGroup --name myAKSCluster --node-vm-size [1] --enable-addons [2] --generate-ssh-keys

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

AStandard_DS2_v2

Bmonitoring

Chttpapplicationrouting

DStandard_B1s

Attempts:

3 left

💡 Hint

Common Mistakes

Using unsupported VM sizes causes deployment failure.

Confusing addon names.

The --node-vm-size sets the VM size for nodes, and monitoring enables the monitoring addon.

5fill in blank

hard

Fill all three blanks to create an AKS cluster with 3 nodes, Kubernetes version 1.24.9, and enable HTTP application routing addon.

Azure

az aks create --resource-group myResourceGroup --name myAKSCluster --node-count [1] --kubernetes-version [2] --enable-addons [3] --generate-ssh-keys

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

A2

B3

C1.24.9

Dhttp_application_routing

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong addon names.

Using unsupported Kubernetes versions.

Setting node count to less than 1.

Set node count to 3, Kubernetes version to 1.24.9, and enable the HTTP application routing addon with 'http_application_routing'.

Practice

1. What is the main purpose of creating an AKS cluster in Azure?

easy

A. To host traditional web applications without containers

B. To create virtual machines for general computing

C. To store large amounts of unstructured data

D. To run and manage containerized applications using Kubernetes

Solution

1. Step 1: Understand AKS functionality

   AKS (Azure Kubernetes Service) is designed to run and manage containerized applications using Kubernetes orchestration.

2. Step 2: Differentiate from other Azure services

   Virtual machines, storage, and web hosting are handled by other Azure services, not AKS.

3. Final Answer:

   To run and manage containerized applications using Kubernetes -> Option D

4. Quick Check:

   AKS = Kubernetes container management [OK]

Hint: AKS is for Kubernetes container orchestration [OK]

Common Mistakes:

• Confusing AKS with VM creation
• Thinking AKS is for storage
• Assuming AKS hosts non-container apps

2. Which Azure CLI command correctly creates an AKS cluster named myCluster in resource group myGroup with 3 nodes?

easy

A. az create aks --rg myGroup --cluster-name myCluster --count 3

B. az aks create --resource-group myGroup --name myCluster --node-count 3

C. az aks new --group myGroup --cluster myCluster --nodes 3

D. az aks deploy --resource-group myGroup --name myCluster --nodes 3

Solution

1. Step 1: Identify correct Azure CLI syntax

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

2. Step 2: Compare options

   Only az aks create --resource-group myGroup --name myCluster --node-count 3 uses the correct command and parameter names as per Azure CLI documentation.

3. Final Answer:

   az aks create --resource-group myGroup --name myCluster --node-count 3 -> Option B

4. Quick Check:

   Correct CLI syntax = az aks create --resource-group myGroup --name myCluster --node-count 3 [OK]

Hint: Use 'az aks create' with --resource-group, --name, --node-count [OK]

Common Mistakes:

• Using wrong command verbs like 'new' or 'deploy'
• Incorrect parameter names like --group or --nodes
• Mixing command order or missing required flags

3. What will be the result of this command?

az aks create --resource-group myGroup --name myCluster --node-count 2 --enable-managed-identity --ssh-key-value ~/.ssh/id_rsa.pub

medium

A. Creates an AKS cluster with 2 nodes, managed identity, and SSH access enabled

B. Creates an AKS cluster with 2 nodes but disables SSH access

C. Fails because --enable-managed-identity is not a valid flag

D. Creates an AKS cluster with 2 nodes but without managed identity

Solution

1. Step 1: Analyze command flags

   The command uses --enable-managed-identity to enable managed identity and --ssh-key-value to set SSH public key for node access.

2. Step 2: Understand expected behavior

   This command creates a cluster with 2 nodes, managed identity enabled, and SSH access configured using the provided key.

3. Final Answer:

   Creates an AKS cluster with 2 nodes, managed identity, and SSH access enabled -> Option A

4. Quick Check:

   Managed identity + SSH key = Creates an AKS cluster with 2 nodes, managed identity, and SSH access enabled [OK]

Hint: Managed identity and SSH flags enable secure access [OK]

Common Mistakes:

• Assuming --enable-managed-identity is invalid
• Thinking SSH is disabled without extra flags
• Confusing managed identity with service principal

4. You run this command but get an error:

az aks create --resource-group myGroup --name myCluster --node-count two

What is the likely cause?

medium

A. The cluster name cannot be 'myCluster'

B. The resource group name is invalid

C. The node count must be a number, not a word

D. The command is missing the --enable-managed-identity flag

Solution

1. Step 1: Check parameter types

   The --node-count parameter expects a numeric value, but 'two' is a word, causing a syntax error.

2. Step 2: Validate other parameters

   Resource group and cluster name are valid strings; managed identity flag is optional.

3. Final Answer:

   The node count must be a number, not a word -> Option C

4. Quick Check:

   Numeric node count required = The node count must be a number, not a word [OK]

Hint: Node count must be numeric, not text [OK]

Common Mistakes:

• Using words instead of numbers for counts
• Assuming resource group or name causes error
• Thinking managed identity flag is mandatory

5. You want to create an AKS cluster with 4 nodes, enable managed identity, and use a custom SSH key located at /keys/mykey.pub. Which command is correct?

hard

A. az aks create --resource-group myGroup --name myCluster --node-count 4 --enable-managed-identity --ssh-key-value /keys/mykey.pub

B. az aks create --resource-group myGroup --name myCluster --nodes 4 --enable-msi --ssh-key /keys/mykey.pub

C. az aks create --resource-group myGroup --name myCluster --node-count 4 --enable-managed-identity

D. az aks create --resource-group myGroup --name myCluster --node-count 4 --ssh-key-value /keys/mykey.pub

Solution

1. Step 1: Verify required parameters

   The command must specify --node-count 4, --enable-managed-identity, and --ssh-key-value with the correct path.

2. Step 2: Check option correctness

   az aks create --resource-group myGroup --name myCluster --node-count 4 --enable-managed-identity --ssh-key-value /keys/mykey.pub uses correct parameter names and includes all required flags. Other options have incorrect flags or missing parameters.

3. Final Answer:

   az aks create --resource-group myGroup --name myCluster --node-count 4 --enable-managed-identity --ssh-key-value /keys/mykey.pub -> Option A

4. Quick Check:

   Correct flags and values = az aks create --resource-group myGroup --name myCluster --node-count 4 --enable-managed-identity --ssh-key-value /keys/mykey.pub [OK]

Hint: Use full flag names and correct SSH key path [OK]

Common Mistakes:

• Using shorthand or incorrect flags like --nodes or --ssh-key
• Omitting managed identity flag
• Forgetting to specify SSH key path