Question 490
An administrator checks the following condition: An operator creates a Pod but expects it to maintain its replica count after deletion. What is the MOST directly supported cause?
Explanation
Correct Answer
A standalone Pod is not self-replacing through a higher-level controller. This mechanism fits the stated evidence. Validate it by checking that deleting a replica triggers an approved replacement.
Incorrect Answers
Replica count alone does not guarantee distribution across nodes. That can explain why a rolling application has three replicas but one node's failure leaves only one ready, whereas the current evidence supports a Deployment or ReplicaSet provides ongoing replica reconciliation.
The alternative describes gitOps requires a controller that observes desired Git state and applies it, which is relevant when a GitOps deployment repository changes but the cluster is never reconciled. It does not explain this case because a standalone Pod is not self-replacing through a higher-level controller.
It would account for a Kubernetes Deployment pod cannot read a nonsecret configuration key that was never mounted, not the current evidence. For this incident, a standalone Pod is not self-replacing through a higher-level controller; the alternative mechanism leaves that distinction unexplained.





CompTIA Linux+ (XK0-006) Practice Tests