Why managed Kubernetes matters in Azure - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why choose managed Kubernetes over self-managed?

Which of the following is the main advantage of using a managed Kubernetes service like Azure Kubernetes Service (AKS) instead of setting up Kubernetes manually?

A You get full control over every node without any restrictions.

B You must manually install and configure all Kubernetes components.

C The cloud provider handles cluster maintenance and upgrades automatically.

D Managed Kubernetes does not support scaling applications automatically.

💡 Hint

Think about who takes care of updates and maintenance in managed services.

Managed Kubernetes services like AKS automate cluster maintenance, upgrades, and patching, reducing manual work and errors.

💻 Command Output

intermediate

Output of AKS cluster creation command

What is the expected output after successfully running this Azure CLI command to create an AKS cluster?

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

A Provisioning succeeded with cluster details including node count and monitoring addon status.

B Error: SSH keys are missing and must be provided manually.

C Command runs but no cluster is created or shown in Azure portal.

D Syntax error: missing required parameters for node count.

💡 Hint

Check what the command does with the --generate-ssh-keys flag and monitoring addon.

The command creates a 3-node AKS cluster with monitoring enabled and generates SSH keys automatically, resulting in a success message with cluster details.

🔀 Workflow

advanced

Correct order to deploy an app on AKS

Arrange the steps in the correct order to deploy a containerized app on Azure Kubernetes Service (AKS).

A 1,2,3,4

B 3,2,1,4

C 1,3,2,4

D 2,1,3,4

💡 Hint

Think about what must exist before deploying the app and applying configs.

You first create the cluster, then build and push the image, prepare deployment files, and finally apply them to the cluster.

❓ Troubleshoot

advanced

Diagnosing AKS node scaling failure

You tried to scale your AKS cluster nodes using az aks scale but the node count did not change. What is the most likely cause?

A You forgot to update the Kubernetes deployment replicas count.

B The cluster autoscaler is disabled or not configured properly.

C The Azure CLI command syntax is incorrect and did not run.

D The container image is missing from the registry.

💡 Hint

Scaling nodes depends on autoscaler settings in AKS.

If autoscaler is disabled or misconfigured, scaling commands won't change node count even if the command runs.

✅ Best Practice

expert

Best practice for securing AKS cluster access

Which option is the best practice to securely control access to your AKS cluster?

A Store cluster admin credentials in plain text files on developer machines.

B Allow anonymous access to the Kubernetes API server for ease of use.

C Disable network policies to avoid connectivity issues.

D Use Azure Active Directory integration with role-based access control (RBAC).

💡 Hint

Think about how to control who can do what in the cluster securely.

Integrating AKS with Azure AD and using RBAC ensures only authorized users can access and perform actions on the cluster.