Bird
0
0

Given a Deployment with 4 replicas and a rolling update strategy, what happens when you update the container image version?

medium📝 Analysis Q4 of 15
Microservices - Orchestration with Kubernetes
Given a Deployment with 4 replicas and a rolling update strategy, what happens when you update the container image version?
APods are updated one by one without downtime
BOnly half of the Pods are updated automatically
CNo Pods are updated until manual restart
DAll Pods are deleted and recreated at once
Step-by-Step Solution
Solution:

  1. Step 1: Understand rolling update behavior

    Rolling update updates Pods gradually to avoid downtime.

  2. Step 2: Eliminate other options

    Deleting all Pods at once causes downtime, manual restart is not needed, and partial updates are not default.

  3. Final Answer:

    Pods are updated one by one without downtime -> Option A

  4. Quick Check:

    Rolling update = gradual Pod replacement [OK]
Quick Trick: Rolling update replaces Pods gradually [OK]
Common Mistakes:
MISTAKES
  • Thinking all Pods restart simultaneously
  • Believing manual restart is required
  • Assuming partial updates only

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Microservices Quizzes
Authentication and Authorization - Why security spans all services - Quiz 3easy Authentication and Authorization - Service-to-service authentication - Quiz 6medium Authentication and Authorization - Why security spans all services - Quiz 15hard Authentication and Authorization - JWT token propagation - Quiz 14medium Event-Driven Architecture - Event replay - Quiz 10hard Monitoring and Observability - Distributed tracing (Jaeger, Zipkin) - Quiz 10hard Monitoring and Observability - Dashboards (Grafana) - Quiz 4medium Orchestration with Kubernetes - Services and networking - Quiz 9hard Resilience Patterns - Bulkhead pattern - Quiz 10hard Service Mesh - Istio overview - Quiz 12easy