Bird
Raised Fist0
Kubernetesdevops~10 mins

Why container orchestration matters in Kubernetes - Test Your Understanding

Choose your learning style10 modes available
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the code to create a Kubernetes Pod manifest with one container.

Kubernetes
apiVersion: v1
kind: Pod
metadata:
  name: my-pod
spec:
  containers:
  - name: my-container
    image: [1]
Drag options to blanks, or click blank then click option'
Adocker run nginx
Bnginx:latest
Ckubectl apply
Dpodman run
Attempts:
3 left
💡 Hint
Common Mistakes
Using commands instead of image names
Leaving the image field empty
2fill in blank
medium

Complete the command to deploy a Kubernetes manifest file named app.yaml.

Kubernetes
kubectl [1] -f app.yaml
Drag options to blanks, or click blank then click option'
Aapply
Bdelete
Crun
Dbuild
Attempts:
3 left
💡 Hint
Common Mistakes
Using kubectl run which creates a pod directly
Using kubectl delete which removes resources
3fill in blank
hard

Fix the error in the command to list all pods in all namespaces.

Kubernetes
kubectl get pods [1]
Drag options to blanks, or click blank then click option'
A-a
B--namespace=all
C--all-namespaces
D--all
Attempts:
3 left
💡 Hint
Common Mistakes
Using -a which is not valid for namespaces
Using --namespace=all which is invalid
4fill in blank
hard

Fill both blanks to create a Deployment manifest with 3 replicas of an nginx container.

Kubernetes
apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx-deployment
spec:
  replicas: [1]
  selector:
    matchLabels:
      app: nginx
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: [2]
Drag options to blanks, or click blank then click option'
A3
Bnginx:1.21
Cnginx:latest
D1
Attempts:
3 left
💡 Hint
Common Mistakes
Using 1 replica instead of 3
Using invalid image tags
5fill in blank
hard

Fill all three blanks to create a Service manifest exposing port 80 for the nginx Deployment.

Kubernetes
apiVersion: v1
kind: Service
metadata:
  name: nginx-service
spec:
  selector:
    app: [1]
  ports:
  - protocol: TCP
    port: [2]
    targetPort: [3]
Drag options to blanks, or click blank then click option'
Anginx
B80
Dhttp
Attempts:
3 left
💡 Hint
Common Mistakes
Using wrong selector label
Using string 'http' instead of port number

Practice

(1/5)
1. Why is container orchestration important in managing applications?
easy
A. It helps keep many containers organized and running smoothly.
B. It replaces the need for containers entirely.
C. It slows down application deployment.
D. It only works with virtual machines, not containers.

Solution

  1. Step 1: Understand container orchestration role

    Container orchestration manages multiple containers to keep them organized and running well.
  2. Step 2: Compare options to orchestration purpose

    Only It helps keep many containers organized and running smoothly. correctly states orchestration helps keep containers organized and running smoothly.
  3. Final Answer:

    It helps keep many containers organized and running smoothly. -> Option A
  4. Quick Check:

    Container orchestration = Organize and run containers well [OK]
Hint: Orchestration means managing many containers easily [OK]
Common Mistakes:
  • Thinking orchestration replaces containers
  • Believing orchestration slows deployment
  • Confusing orchestration with virtual machines
2. Which of the following is the correct way to describe Kubernetes in YAML files?
easy
A. Kubernetes uses YAML files to define container orchestration settings.
B. Kubernetes uses YAML files to write application code.
C. Kubernetes YAML files are only for styling web pages.
D. Kubernetes does not use YAML files at all.

Solution

  1. Step 1: Identify Kubernetes YAML file purpose

    Kubernetes uses YAML files to describe how containers should be run and managed.
  2. Step 2: Eliminate incorrect options

    Options A, B, and C are wrong because YAML is not for code writing, styling, or unused by Kubernetes.
  3. Final Answer:

    Kubernetes uses YAML files to define container orchestration settings. -> Option A
  4. Quick Check:

    Kubernetes YAML = Container orchestration config [OK]
Hint: YAML files describe container setup in Kubernetes [OK]
Common Mistakes:
  • Thinking YAML is for coding apps
  • Confusing YAML with web styling files
  • Believing Kubernetes ignores YAML
3. What happens when Kubernetes detects a container has crashed?
medium
A. It ignores the crash and does nothing.
B. It sends an email but does not restart the container.
C. It deletes all containers in the cluster.
D. It automatically restarts the crashed container.

Solution

  1. Step 1: Understand Kubernetes self-healing feature

    Kubernetes monitors containers and restarts any that crash to keep apps running.
  2. Step 2: Match behavior to options

    Only It automatically restarts the crashed container. correctly describes automatic restart after a crash.
  3. Final Answer:

    It automatically restarts the crashed container. -> Option D
  4. Quick Check:

    Kubernetes self-healing = Auto restart crashed containers [OK]
Hint: Kubernetes restarts crashed containers automatically [OK]
Common Mistakes:
  • Thinking Kubernetes ignores crashes
  • Believing it deletes all containers on one crash
  • Assuming manual restart is always needed
4. You wrote a Kubernetes YAML file but your containers are not scaling as expected. What is a likely cause?
medium
A. The YAML file has too many comments.
B. The YAML file is missing the HorizontalPodAutoscaler configuration.
C. Kubernetes does not support scaling containers.
D. You need to restart your computer to scale containers.

Solution

  1. Step 1: Identify scaling configuration in Kubernetes

    Scaling containers requires a HorizontalPodAutoscaler resource in the YAML file.
  2. Step 2: Evaluate other options

    Comments do not affect scaling, Kubernetes supports scaling, and restarting computer is unrelated.
  3. Final Answer:

    The YAML file is missing the HorizontalPodAutoscaler configuration. -> Option B
  4. Quick Check:

    Scaling needs autoscaler config in YAML [OK]
Hint: Missing autoscaler config stops scaling [OK]
Common Mistakes:
  • Blaming comments for scaling issues
  • Thinking Kubernetes can't scale containers
  • Restarting computer to fix scaling
5. You want your app to handle more users during busy times without downtime. How does Kubernetes help achieve this?
hard
A. By requiring manual container restarts for scaling.
B. By stopping all containers during busy times to save resources.
C. By automatically scaling containers up and down based on demand.
D. By running only one container regardless of load.

Solution

  1. Step 1: Understand Kubernetes scaling capability

    Kubernetes can automatically increase or decrease container count to match user demand.
  2. Step 2: Compare options to scaling goal

    Only By automatically scaling containers up and down based on demand. describes automatic scaling to handle more users without downtime.
  3. Final Answer:

    By automatically scaling containers up and down based on demand. -> Option C
  4. Quick Check:

    Kubernetes auto-scales containers for demand [OK]
Hint: Auto scale containers to match user demand [OK]
Common Mistakes:
  • Thinking containers stop during busy times
  • Believing manual restarts are needed for scaling
  • Assuming only one container runs always
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard