Question 670
At the Highbridge education technology team, during a compliance readiness review, teams alter production Kubernetes manifests manually and cannot reproduce an earlier service version. What underlying weakness best explains these results?
Explanation
Correct Answer
The situation indicates that untracked cluster edits create drift between approved configuration and deployed workloads. The recommended response is to use reviewed Helm charts or controlled Kubernetes manifests with versioned release values, with a follow-up check that a prior version can be redeployed from a saved chart and environment configuration. This directly addresses the reported issue at the Highbridge education technology team.
Incorrect Answers
Urgency changes the approval timetable but not the need for traceability or code-line reconciliation. This can occur in other projects, but it is not the primary explanation at the Highbridge education technology team.
This explanation belongs to infrastructure drift response. The immediate weakness in the question is that untracked cluster edits create drift between approved configuration and deployed workloads. For the Highbridge education technology team, the priority is to use reviewed Helm charts or controlled Kubernetes manifests with versioned release values.
Although premature cleanup destroys traceability and recovery materials for supported versions, the situation does not describe that specific cause; it instead indicates that untracked cluster edits create drift between approved configuration and deployed workloads. For the Highbridge education technology team, the priority is to use reviewed Helm charts or controlled Kubernetes manifests with versioned release values.