Kubectl for cluster management in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

What is the output of this kubectl command?

You run kubectl get pods --namespace=default in your Azure Kubernetes cluster. What will this command display?

A A list of all nodes in the cluster with their IP addresses.

B A list of all pods running in the default namespace with their status and age.

C The detailed configuration of the default namespace.

D The logs of the most recently created pod in the default namespace.

💡 Hint

Think about what 'get pods' and 'namespace' mean in kubectl commands.

The command 'kubectl get pods --namespace=default' lists all pods in the default namespace, showing their names, statuses, and how long they've been running.

❓ Configuration

intermediate

Which kubectl command correctly scales a deployment?

You want to scale the deployment named webapp to 5 replicas in your Azure Kubernetes cluster. Which command will do this?

A kubectl scale deployment webapp --replicas=5

B kubectl set replicas webapp 5

C kubectl update deployment webapp replicas 5

D kubectl deploy scale webapp 5

💡 Hint

Look for the standard kubectl subcommand to change replicas.

The correct syntax to scale a deployment is 'kubectl scale deployment --replicas='.

❓ security

advanced

What error occurs when running kubectl without proper cluster credentials?

You run kubectl get pods but your kubeconfig file is missing or invalid. What error message will you most likely see?

A error: You must be logged in to the server (Unauthorized)

B error: resource not found

C error: invalid command syntax

D error: pod not ready

💡 Hint

Think about authentication errors when credentials are missing.

Without valid credentials, kubectl cannot authenticate and returns an Unauthorized error.

❓ Architecture

advanced

Which kubectl command shows the node where a pod is running?

You want to find out on which node the pod named backend-xyz is running. Which command will give you this information?

A kubectl get nodes backend-xyz

B kubectl describe node backend-xyz

C kubectl get pod backend-xyz -o wide

D kubectl logs backend-xyz

💡 Hint

Look for a command that shows detailed pod info including node name.

The '-o wide' option with 'kubectl get pod' shows extra details including the node name where the pod runs.

✅ Best Practice

expert

What is the recommended way to update a deployment image without downtime?

You want to update the container image of deployment api-server to api:v2 in your Azure Kubernetes cluster. Which kubectl command follows best practices to avoid downtime?

A kubectl delete deployment api-server && kubectl create deployment api-server --image=api:v2

B kubectl scale deployment api-server --replicas=0; kubectl set image deployment/api-server api=api:v2; kubectl scale deployment api-server --replicas=3

C kubectl edit deployment api-server and manually change the image field

D kubectl set image deployment/api-server api=api:v2

💡 Hint

Consider commands that update images with rolling updates.

Using 'kubectl set image' updates the deployment image and triggers a rolling update, avoiding downtime.

Practice

1. What is the primary purpose of the kubectl tool in Kubernetes?

easy

A. To manage and control Kubernetes clusters

B. To create virtual machines in Azure

C. To monitor network traffic outside the cluster

D. To write application code for Kubernetes

Solution

1. Step 1: Understand kubectl's role

   kubectl is designed to interact with Kubernetes clusters to manage resources like pods, deployments, and services.

2. Step 2: Compare options

   Options A, B, and C describe tasks unrelated to kubectl. Only To manage and control Kubernetes clusters correctly states its purpose.

3. Final Answer:

   To manage and control Kubernetes clusters -> Option A

4. Quick Check:

   kubectl = cluster management [OK]

Hint: kubectl controls Kubernetes clusters directly [OK]

Common Mistakes:

• Confusing kubectl with Azure VM tools
• Thinking kubectl writes application code
• Assuming kubectl monitors external network traffic

2. Which of the following is the correct syntax to list all pods in the current Kubernetes namespace using kubectl?

easy

A. kubectl get pods

B. kubectl list pods

C. kubectl show pods

D. kubectl describe pods

Solution

1. Step 1: Recall kubectl commands for listing resources

   The command to list resources is kubectl get, followed by the resource type.

2. Step 2: Evaluate options

   Only kubectl get pods uses the correct syntax kubectl get pods. Options A and B are invalid commands, and D shows detailed info, not a simple list.

3. Final Answer:

   kubectl get pods -> Option A

4. Quick Check:

   List pods = kubectl get pods [OK]

Hint: Use 'kubectl get' to list Kubernetes resources [OK]

Common Mistakes:

• Using 'list' or 'show' instead of 'get'
• Confusing 'describe' with listing
• Adding extra words after 'pods'

3. Given the command kubectl get pods -o wide, what extra information will you see compared to kubectl get pods?

medium

A. Detailed pod logs

B. Extended pod information including node and IP

C. Only pod names without status

D. List of services instead of pods

Solution

1. Step 1: Understand the '-o wide' option

   The -o wide flag shows additional columns like node name and pod IP address.

2. Step 2: Compare output differences

   Extended pod information including node and IP correctly describes the extra info. Detailed pod logs is about logs, not shown here. Only pod names without status is incorrect as status is shown by default. List of services instead of pods is unrelated.

3. Final Answer:

   Extended pod information including node and IP -> Option B

4. Quick Check:

   -o wide = more pod details [OK]

Hint: Use '-o wide' to see node and IP info for pods [OK]

Common Mistakes:

• Thinking '-o wide' shows logs
• Assuming it hides status info
• Confusing pods with services

4. You run kubectl get pod mypod but get an error saying the pod does not exist. What is the most likely cause?

medium

A. You are in the wrong namespace

B. The pod name is misspelled

C. The pod has already been deleted

D. All of the above

Solution

1. Step 1: Check common reasons for pod not found error

   The error can happen if the pod name is wrong, the pod was deleted, or you are looking in the wrong namespace.

2. Step 2: Evaluate options

   All options B, C, and D are valid causes. Therefore, All of the above which includes all is correct.

3. Final Answer:

   All of the above -> Option D

4. Quick Check:

   Pod not found = wrong namespace, name, or deleted [OK]

Hint: Check namespace, spelling, and pod existence [OK]

Common Mistakes:

• Ignoring namespace context
• Assuming pod always exists
• Not verifying pod name spelling

5. You want to update the image of a deployment named webapp to version v2 using kubectl. Which command correctly performs this update?

hard

A. kubectl update deployment webapp --image=webapp:v2

B. kubectl edit deployment webapp image=webapp:v2

C. kubectl set image deployment/webapp webapp=webapp:v2

D. kubectl change image webapp webapp:v2

Solution

1. Step 1: Identify the correct kubectl command to update deployment image

   The command kubectl set image is used to update container images in deployments.

2. Step 2: Analyze each option

   kubectl set image deployment/webapp webapp=webapp:v2 uses correct syntax: kubectl set image deployment/webapp webapp=webapp:v2. Options A, C, and D use invalid or incorrect commands.

3. Final Answer:

   kubectl set image deployment/webapp webapp=webapp:v2 -> Option C

4. Quick Check:

   Update image = kubectl set image [OK]

Hint: Use 'kubectl set image' to update deployment containers [OK]

Common Mistakes:

• Using 'kubectl update' which is invalid
• Trying 'kubectl edit' without proper syntax
• Using non-existent 'kubectl change' command