- Courses
- Tutorials
- Practice
- Jobs
Kubernetes-4
Question 1
How does a ReplicaSet identify which Pods it should manage?
- A
By Pod name prefix
- B
By namespace matching
- C
By label selectors and ownerReferences
- D
By container image version
Question 2
Why is a ReplicaSet considered a lower-level abstraction compared to a Deployment?
- A
It cannot create Pods
- B
It lacks rollback and rollout logic
- C
It does not support YAML configuration
- D
It cannot scale replicas
Question 3
What triggers the creation of a new ReplicaSet when using a Deployment?
- A
Scaling the number of replicas
- B
Restarting a Pod
- C
Updating the PodTemplateSpec
- D
Changing Service selectors
Question 4
During a RollingUpdate strategy, how does a Deployment achieve zero downtime?
- A
By restarting all Pods simultaneously
- B
By pausing traffic using Services
- C
By gradually scaling up the new ReplicaSet while scaling down the old one
- D
By deleting old ReplicaSets immediately
Question 5
Why are Deployments considered ideal for stateless applications?
- A
They automatically persist application data
- B
They manage Pod identity and ordering
- C
They allow easy scaling, rollbacks, and replacement of Pods
- D
They prevent Pods from being recreated
Question 6
What is the purpose of the status section in a Deployment object?
- A
Defines the desired number of replicas
- B
Stores container image configuration
- C
Tracks actual vs desired state for self-healing
- D
Controls Pod scheduling rules
Question 7
Which action increments a Deployment revision number?
- A
Restarting Pods
- B
Scaling replicas up or down
- C
Pausing a rollout
- D
Updating the Pod template configuration
Question 8
A Deployment remains in Progressing state for a long time. Which situation could cause this?
- A
New Pods are failing readiness probes
- B
Old ReplicaSet has zero replicas
- C
Pods are running successfully
- D
Deployment has no labels
Question 9
Why does Kubernetes recommend using Deployments instead of directly managing ReplicaSets?
- A
ReplicaSets are deprecated
- B
Deployments add orchestration, rollback, and rollout safety
- C
ReplicaSets cannot run containers
- D
Deployments reduce cluster resource usage
Question 10
In a canary deployment approach, what is the primary goal of keeping old and new replicas running simultaneously?
- A
Reduce CPU usage
- B
Improve Pod startup speed
- C
Prevent ReplicaSet deletion
- D
Validate new versions with limited user exposure
There are 10 questions to complete.