AKS cluster creation in Azure - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is AKS in Azure?

AKS stands for Azure Kubernetes Service. It is a managed container orchestration service that simplifies deploying, managing, and scaling containerized applications using Kubernetes.

beginner

Name the main components needed to create an AKS cluster.

You need a resource group, a virtual network (optional but recommended), and the AKS cluster itself which includes nodes (virtual machines) to run your containers.

intermediate

What is the purpose of node pools in AKS?

Node pools allow you to group nodes with the same configuration. You can have multiple node pools with different VM sizes or OS types to run different workloads efficiently.

beginner

Which Azure CLI command is used to create an AKS cluster?

The command is az aks create. It lets you specify the cluster name, resource group, node count, VM size, and other settings.

intermediate

Why is it important to enable RBAC when creating an AKS cluster?

RBAC (Role-Based Access Control) controls who can access and manage the cluster resources. Enabling it improves security by limiting permissions to only authorized users.

Which command creates a new AKS cluster in Azure?

A az network vnet create

B az vm create

C az container create

D az aks create

The az aks create command is used to create an AKS cluster.

What does a node pool in AKS represent?

A A group of nodes with the same configuration

B A single container instance

C A virtual network

D A storage account

Node pools group nodes with the same VM size and OS type for workload management.

Which of these is NOT required to create an AKS cluster?

A Storage account

B Virtual network (optional)

C Cluster name

D Resource group

A storage account is not required to create an AKS cluster, but resource group and cluster name are mandatory.

Why enable RBAC in AKS?

A To speed up container deployment

B To increase cluster size

C To control user access and permissions

D To reduce VM costs

RBAC controls who can access and manage cluster resources, improving security.

What is the default orchestrator used by AKS?

A Mesos

B Kubernetes

C Docker Swarm

D Nomad

AKS uses Kubernetes as its container orchestrator.

Explain the steps and components involved in creating an AKS cluster.

Think about what you need before and during cluster creation.

Describe the role and benefits of node pools in AKS cluster management.

Consider how node pools help organize and optimize resources.

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