Why advanced patterns matter in Kubernetes - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use advanced Kubernetes deployment patterns?

Which reason best explains why advanced deployment patterns like Blue-Green or Canary are important in Kubernetes?

A They allow updating applications without downtime and reduce risk by gradual rollout.

B They make the cluster use less memory by deleting old pods immediately.

C They automatically fix all bugs in the application code during deployment.

D They increase the number of replicas to maximum for faster scaling.

💡 Hint

Think about how users experience updates and how errors can be caught early.

Advanced deployment patterns help update apps smoothly without stopping service and allow testing new versions with a small user group before full rollout.

💻 Command Output

intermediate

Output of a rolling update command

What is the expected output when running this command in Kubernetes?

kubectl rollout status deployment/myapp

A No resources found in default namespace

B deployment "myapp" successfully rolled out

C error: deployment "myapp" not found

D deployment "myapp" paused

💡 Hint

This command checks if the deployment finished updating.

The command shows the rollout status and confirms success when the deployment completes updating all pods.

🔀 Workflow

advanced

Order of steps in a Canary deployment

Arrange these steps in the correct order for performing a Canary deployment in Kubernetes.

A 1,2,3,4

B 2,1,3,4

C 1,3,2,4

D 3,1,2,4

💡 Hint

Think about deploying first, then watching, then increasing traffic.

Canary deployment starts with a small rollout, monitors for problems, then increases traffic before full switch.

❓ Troubleshoot

advanced

Troubleshooting failed rolling update

You ran kubectl rollout restart deployment/myapp but the new pods keep crashing. What is the most likely cause?

A The cluster ran out of CPU resources.

B The service selector labels do not match pods.

C The deployment was paused before restart.

D The new container image has a bug causing crashes.

💡 Hint

New pods crashing usually means something wrong inside the container.

If new pods crash after restart, the container image likely has errors or misconfiguration causing failure.

✅ Best Practice

expert

Best practice for managing secrets in Kubernetes

Which option is the best practice for securely managing sensitive data like passwords in Kubernetes?

A Use ConfigMaps to store all sensitive data for simplicity.

B Include passwords directly in container environment variables in the Deployment YAML.

C Store secrets in Kubernetes Secrets objects and enable encryption at rest.

D Commit secrets in plain text to the Git repository for easy access.

💡 Hint

Think about security and encryption when storing secrets.

Kubernetes Secrets are designed for sensitive data and can be encrypted at rest to protect information.