Question 20
A Microsoft Azure administrator receives this requirement: A Kubernetes service crashes repeatedly but the security team collects only VM infrastructure metrics and lacks container and audit diagnostics. Which operating control most directly reduces this recurring risk?
Explanation
Correct Answer
This guardrail addresses aks control plane and container logging: AKS workload and Kubernetes audit telemetry require explicit monitoring and log collection beyond resource health. The prevention measure is: Test AKS diagnostic collection coverage after cluster upgrades and namespace changes. A control in another subsystem would not prevent this specific recurrence.
Incorrect Answers
The container group relies on a long-lived shared credential rather than supported managed identity authorization. “Review environment variables and container logging for unintended credential exposure” would address that alternative cause, not the condition in this question: aKS workload and Kubernetes audit telemetry require explicit monitoring and log collection beyond resource health.
“Track identity integration feature lifecycle before Kubernetes version upgrades” responds to this separate finding: the workload identity integration uses an older unsupported pattern rather than the supported federated workload identity model. This question instead needs “Test AKS diagnostic collection coverage after cluster upgrades and namespace changes”, so the alternative does not meet the stated condition.
Sensitive values are placed in plain configuration rather than secure parameters or supported protected secret references. “Scan container deployment manifests and logs for accidentally exposed credentials” applies to that separate problem. The observed case is a Kubernetes service crashes repeatedly but the security team collects only VM infrastructure metrics and lacks container and audit diagnostics; choosing this alternative would address the wrong failure mode.