Why container orchestration matters in Kubernetes - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use container orchestration in production?

Imagine you have many containers running your app. What is the main reason to use container orchestration?

A To automatically manage container deployment, scaling, and health

B To manually start and stop each container on every server

C To write code inside containers faster

D To replace containers with virtual machines

💡 Hint

Think about what happens when you have many containers and want them to run smoothly without manual work.

Container orchestration automates deployment, scaling, and health checks of containers, making management easier and reliable.

💻 Command Output

intermediate

Kubernetes pod scaling output

You run the command kubectl scale deployment myapp --replicas=3. What will be the state of pods after this command?

Kubernetes

kubectl scale deployment myapp --replicas=3

A Exactly 3 pods of 'myapp' will be running

B Pods will be deleted automatically

C Pods will run but only 1 will be active

D No pods will run until manually started

💡 Hint

Scaling sets the desired number of pod copies to run.

The scale command tells Kubernetes to maintain 3 running pods for the deployment 'myapp'.

🔀 Workflow

advanced

Order the steps for rolling update in Kubernetes

Put these steps in the correct order for a rolling update of a deployment in Kubernetes.

A 1,3,2,4

B 2,1,3,4

C 1,2,3,4

D 3,1,2,4

💡 Hint

Think about editing the config first, then applying it, then Kubernetes handles pod replacement.

First update the manifest, then apply it. Kubernetes then creates new pods and removes old ones gradually.

❓ Troubleshoot

advanced

Troubleshoot failing pod restart in Kubernetes

A pod keeps restarting repeatedly. Which reason is the most likely cause?

A The pod has no readiness or liveness probes defined

B The pod has enough CPU and memory resources

C The pod is running a simple hello-world container

D The pod image is missing or cannot be pulled

💡 Hint

Check if the pod can start properly or if it fails immediately.

If the image is missing or cannot be pulled, the pod will fail to start and restart repeatedly.

✅ Best Practice

expert

Best practice for high availability in Kubernetes clusters

Which practice best ensures high availability of your application in a Kubernetes cluster?

A Use only one replica of each pod to save resources

B Distribute pods across multiple nodes and use readiness probes

C Disable automatic pod restarts to avoid resource waste

D Run all pods on a single node to simplify management

💡 Hint

Think about avoiding single points of failure and ensuring pods are healthy before traffic.

Distributing pods across nodes prevents downtime if one node fails. Readiness probes ensure only healthy pods receive traffic.