AKS monitoring with Container Insights in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary purpose of Container Insights in AKS?

Container Insights helps you monitor your AKS cluster. What does it mainly track?

A It deploys new container images to the AKS cluster.

B It collects performance and health data of containers and nodes in the AKS cluster.

C It automatically scales the number of nodes based on traffic.

D It manages user access and permissions for the AKS cluster.

💡 Hint

Think about what monitoring tools usually do: they watch performance and health.

Container Insights collects metrics and logs from containers and nodes to help you understand cluster health and performance.

💻 Command Output

intermediate

What is the output of enabling Container Insights via Azure CLI?

You run this command to enable Container Insights on your AKS cluster:

az aks enable-addons --resource-group myResourceGroup --name myAKSCluster --addons monitoring

What output should you expect if the command succeeds?

A Warning: Monitoring already enabled

B Error: Addon monitoring not found

C {"addonProfiles":{"omsagent":{"enabled":true}},"provisioningState":"Succeeded"}

D No output, command runs silently

💡 Hint

Successful Azure CLI commands usually return JSON with provisioning state.

The command returns JSON showing the monitoring addon is enabled and provisioning succeeded.

❓ Configuration

advanced

Which configuration snippet correctly enables Container Insights with a custom Log Analytics workspace?

You want to enable Container Insights on AKS but use an existing Log Analytics workspace. Which snippet is correct?

A az aks enable-addons --resource-group myRG --name myAKS --addons monitoring --workspace-resource-id /subscriptions/xxx/resourceGroups/myRG/providers/Microsoft.OperationalInsights/workspaces/myWorkspace

B az aks enable-addons --resource-group myRG --name myAKS --addons monitoring --log-analytics-workspace /subscriptions/xxx/resourceGroups/myRG/providers/Microsoft.OperationalInsights/workspaces/myWorkspace

C az aks enable-addons --resource-group myRG --name myAKS --addons monitoring --workspace /subscriptions/xxx/resourceGroups/myRG/providers/Microsoft.OperationalInsights/workspaces/myWorkspace

D az aks enable-addons --resource-group myRG --name myAKS --addons monitoring --log-analytics /subscriptions/xxx/resourceGroups/myRG/providers/Microsoft.OperationalInsights/workspaces/myWorkspace

💡 Hint

Check the exact parameter name for specifying a custom workspace in Azure CLI docs.

The correct parameter is --workspace-resource-id to specify an existing Log Analytics workspace.

❓ Troubleshoot

advanced

Why might Container Insights data not appear after enabling monitoring on AKS?

You enabled Container Insights on your AKS cluster, but no data shows up in Azure Monitor. What is a likely cause?

A The AKS cluster is running on an unsupported Kubernetes version below 1.20.

B The container images do not have the monitoring agent installed inside them.

C The Azure CLI command to enable monitoring was run without administrator privileges.

D The AKS cluster nodes do not have network access to the Log Analytics workspace endpoint.

💡 Hint

Think about what is needed for data to flow from AKS to Azure Monitor.

Network restrictions blocking outbound traffic to the Log Analytics workspace prevent data from being sent and displayed.

🔀 Workflow

expert

Order the steps to enable and verify Container Insights on an AKS cluster

Put these steps in the correct order to enable Container Insights and verify it is working on AKS.

A 3,4,1,2

B 1,3,4,2

C 3,1,4,2

D 4,3,1,2

💡 Hint

Think about prerequisites before enabling addons and verifying data flow.

First, you need a workspace (3), then ensure network access (4), then enable monitoring (1), and finally check logs (2).

Practice

1. What is the primary purpose of enabling Container Insights on an AKS cluster?

easy

A. To increase the number of nodes in the cluster automatically

B. To deploy applications faster on AKS

C. To monitor the health and performance of the AKS cluster

D. To secure the AKS cluster with firewall rules

Solution

1. Step 1: Understand Container Insights role

   Container Insights is designed to collect and display health and performance data for AKS clusters.

2. Step 2: Compare options with Container Insights function

   Only monitoring health and performance matches Container Insights' purpose; other options relate to scaling, deployment, or security.

3. Final Answer:

   To monitor the health and performance of the AKS cluster -> Option C

4. Quick Check:

   Container Insights = Monitoring AKS health [OK]

Hint: Container Insights is about monitoring, not scaling or security [OK]

Common Mistakes:

• Confusing monitoring with scaling features
• Thinking it deploys apps faster
• Assuming it manages security rules

2. Which Azure CLI command correctly enables Container Insights monitoring on an existing AKS cluster named myCluster in resource group myGroup?

easy

A. az aks update --enable-monitoring --name myCluster --resource-group myGroup

B. az aks enable-addons --addons monitoring --name myCluster --resource-group myGroup

C. az aks create --addons monitoring --name myCluster --resource-group myGroup

D. az monitor enable --resource-group myGroup --name myCluster

Solution

1. Step 1: Identify the correct command to enable addons

   The command to enable addons on an existing AKS cluster is az aks enable-addons with the --addons monitoring flag.

2. Step 2: Verify command syntax and parameters

   az aks enable-addons --addons monitoring --name myCluster --resource-group myGroup uses the correct command and parameters: cluster name and resource group are specified properly.

3. Final Answer:

   az aks enable-addons --addons monitoring --name myCluster --resource-group myGroup -> Option B

4. Quick Check:

   Enable addons command = az aks enable-addons --addons monitoring --name myCluster --resource-group myGroup [OK]

Hint: Use 'az aks enable-addons' with '--addons monitoring' [OK]

Common Mistakes:

• Using 'az aks create' instead of enable-addons
• Trying 'az aks update' with wrong flags
• Confusing Azure Monitor commands with AKS commands

3. After enabling Container Insights on your AKS cluster, you run this command:

az aks show --name myCluster --resource-group myGroup --query addonProfiles

What output indicates that monitoring is enabled?

medium

A. {"omsagent": {"enabled": true}}

B. {"monitoring": {"status": "active"}}

C. {"containerInsights": {"enabled": false}}

D. {"omsagent": {"enabled": false}}

Solution

1. Step 1: Understand addonProfiles output for monitoring

   The monitoring addon in AKS is called 'omsagent'. When enabled, its 'enabled' property is true.

2. Step 2: Match output with enabled monitoring

   {"omsagent": {"enabled": true}} shows 'omsagent' with 'enabled': true, indicating monitoring is active.

3. Final Answer:

   {"omsagent": {"enabled": true}} -> Option A

4. Quick Check:

   omsagent enabled = true means monitoring active [OK]

Hint: 'omsagent' enabled true means Container Insights is on [OK]

Common Mistakes:

• Looking for 'monitoring' or 'containerInsights' keys instead of 'omsagent'
• Confusing enabled false as active
• Misreading JSON structure

4. You enabled monitoring on your AKS cluster but do not see any logs or metrics in Azure Monitor. Which of the following is the most likely cause?

medium

A. Container Insights only works with Windows nodes, not Linux

B. The AKS cluster nodes are running an unsupported Kubernetes version

C. The Azure CLI command used was missing the --resource-group parameter

D. The Log Analytics workspace was not linked or created during monitoring setup

Solution

1. Step 1: Identify key requirement for Container Insights data

   Container Insights requires a Log Analytics workspace to collect and store logs and metrics.

2. Step 2: Analyze why no data appears

   If the workspace was not linked or created, no data will flow to Azure Monitor, causing empty logs and metrics.

3. Final Answer:

   The Log Analytics workspace was not linked or created during monitoring setup -> Option D

4. Quick Check:

   Missing workspace = no logs in Azure Monitor [OK]

Hint: Check Log Analytics workspace linkage if no monitoring data shows [OK]

Common Mistakes:

• Assuming Kubernetes version blocks monitoring data
• Thinking missing CLI parameters always cause no data
• Believing Container Insights only supports Windows nodes

5. You want to set up alerts in Azure Monitor for your AKS cluster using Container Insights to notify you when CPU usage exceeds 80% for 5 minutes. Which steps should you follow?

hard

A. Create a Log Analytics query for CPU usage, then create an alert rule based on that query with a 5-minute evaluation period

B. Enable monitoring with az aks enable-addons, then configure alerts directly in AKS cluster settings

C. Install a custom agent on each node to send CPU metrics, then configure alerts in Azure Monitor

D. Use Azure CLI to scale the cluster automatically when CPU exceeds 80%

Solution

1. Step 1: Use Log Analytics to query CPU metrics

   Container Insights sends metrics to Log Analytics, where you can write queries to analyze CPU usage.

2. Step 2: Create an alert rule in Azure Monitor

   Set an alert rule using the query with a condition for CPU > 80% sustained over 5 minutes to trigger notifications.

3. Final Answer:

   Create a Log Analytics query for CPU usage, then create an alert rule based on that query with a 5-minute evaluation period -> Option A

4. Quick Check:

   Alerts need queries + rules in Azure Monitor [OK]

Hint: Use Log Analytics queries to create alerts in Azure Monitor [OK]

Common Mistakes:

• Thinking alerts are configured directly in AKS without Azure Monitor
• Assuming custom agents are needed for CPU metrics
• Confusing scaling actions with alert setup