AKS cluster creation in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Architecture

intermediate

Choosing the Right Node Pool Configuration

You want to create an AKS cluster optimized for a mix of CPU-intensive and memory-intensive workloads. Which node pool configuration best supports this scenario?

A Create a single node pool with Standard_B2s VM size to save costs.

B Create a single node pool with Standard_D4s_v3 VM size for all workloads.

C Create two node pools both with Standard_D2s_v3 VM size for simplicity.

D Create two node pools: one with Standard_F8s (CPU optimized) and another with Standard_E8s_v3 (memory optimized).

💡 Hint

Think about separating workloads by resource needs to optimize performance.

Option D creates specialized node pools for CPU and memory intensive tasks, improving efficiency and performance. Other options either mix workloads inefficiently or use underpowered VMs.

❓ Configuration

intermediate

Correct Azure CLI Command for AKS Creation

Which Azure CLI command correctly creates an AKS cluster named 'myAKSCluster' in resource group 'myResourceGroup' with 3 nodes?

A az aks create --resource-group myResourceGroup --cluster-name myAKSCluster --nodes 3

B az aks create --resource-group myResourceGroup --name myAKSCluster --node-count 3 --enable-addons monitoring

C az aks create --resource-group myResourceGroup --name myAKSCluster --node-count three

D az aks create --resource-group myResourceGroup --name myAKSCluster --node-count 0

💡 Hint

Check the correct parameter names and valid values for node count.

Option B uses correct parameter names and a valid node count. Option B uses wrong parameter names, C uses a non-numeric node count, and A sets node count to zero which is invalid.

❓ security

advanced

Securing AKS Cluster API Server Access

You want to restrict access to the AKS API server to only your corporate IP range 203.0.113.0/24. Which configuration achieves this?

A Enable API server authorized IP ranges with 203.0.113.0/24 during cluster creation.

B Use Azure Firewall to block all IPs except 203.0.113.0/24 after cluster creation.

C Configure network policies inside the cluster to restrict API server access.

D Set up a VPN gateway and connect to the cluster through VPN only.

💡 Hint

Consider built-in AKS features for API server access control.

Option A uses the built-in API server authorized IP ranges feature to restrict access. Option A is external and less direct, C controls pod traffic not API server, and D is a workaround but not direct API server restriction.

❓ service_behavior

advanced

Effect of Enabling Cluster Autoscaler

What happens when you enable the cluster autoscaler on an AKS node pool with min nodes 1 and max nodes 5?

A The node pool will automatically scale between 1 and 5 nodes based on pod resource demands.

B The node pool will always maintain 5 nodes regardless of workload.

C The node pool will scale down to zero nodes when no pods are running.

D The node pool will only scale up but never scale down.

💡 Hint

Think about how autoscaler adjusts node count based on workload.

Option A correctly describes autoscaler behavior within min and max limits. A is static, C is invalid because min nodes is 1, and D is incorrect as autoscaler scales both ways.

✅ Best Practice

expert

Best Practice for Managing Secrets in AKS

Which approach is the best practice for securely managing sensitive data like database passwords in an AKS cluster?

A Store secrets in ConfigMaps since they are easier to manage than Secrets.

B Hardcode secrets in container environment variables for easy access.

C Store secrets in Kubernetes Secrets and enable encryption at rest with Azure Key Vault integration.

D Keep secrets in plain text files inside container images for simplicity.

💡 Hint

Consider security and encryption features available in AKS and Azure.

Option C follows best practices by using Kubernetes Secrets with encryption and Azure Key Vault integration. Other options expose secrets insecurely or use inappropriate storage.