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).