Question 460
A Linux administrator evaluates: A deployment change should maintain the desired pod replica count during a rolling release. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
The observed Linux condition is: A deployment change should maintain the desired pod replica count during a rolling release. The recommended direct administrative response is: Use Kubernetes Deployments to manage replicated application pods and ConfigMaps for nonsensitive configuration, keeping credentials in approved secret management. The relevant failure or security risk is: Placing passwords inside publicly readable ConfigMaps or editing disposable pods directly can leak data and lose changes at reconciliation. Validate success with: The Deployment reconciles the specified replicas and the app receives configuration without exposing secrets in a ConfigMap.
For the specific observation (A deployment change should maintain the desired pod replica count during a rolling release), the acceptance evidence is: The Deployment reconciles the specified replicas and the app receives configuration without exposing secrets in a ConfigMap. This verifies the action (Use Kubernetes Deployments to manage replicated application pods and ConfigMaps for nonsensitive configuration, keeping credentials in approved secret management.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Placing passwords inside publicly readable ConfigMaps or editing disposable pods directly can leak data and lose changes at reconciliation.
Incorrect Answers
Safe Bash parameter expansion and quoting (4.2) addresses another technical failure: Unquoted paths with whitespace or empty variables can split arguments, select unintended files or target a dangerous default. The case states: A deployment change should maintain the desired pod replica count during a rolling release. The most direct paired action and test is: Use Kubernetes Deployments to manage replicated application pods and ConfigMaps for nonsensitive configuration, keeping credentials in approved secret management.
Git branch workflow and reviewed merging (4.4) would demonstrate or implement: Editing the main branch directly or merging without a review can deploy untested configuration to production. The required paired action and test concerns Kubernetes Deployment and ConfigMap boundaries; a passing result for this alternative could leave that requirement unresolved.
Python JSON data extraction and structured error handling (4.3) would demonstrate or implement: The script returns correct values for normal, missing-key and invalid-JSON fixtures while logging actionable errors. The paired-answer requirement concerns Kubernetes Deployment and ConfigMap boundaries; this alternative does not provide the matching intervention and separate acceptance evidence.