Question 940
During an operational security assessment at a public-sector technology agency, the team documents this issue: Investigators can see aggregate cluster CPU but not which namespace caused the capacity spike. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. Select TWO: one corrective action and one test that confirms its effectiveness. (Select TWO.)
Explanation
Correct Answers
Correct corrective action. Enable supported Container Insights collection and scope container, pod and node metrics and logs for the AKS environment. The action targets the recorded failure (Investigators can see aggregate cluster CPU but not which namespace caused the capacity spike), and is intended to reduce the corresponding risk: Node health can mask crash-looping pods, scheduling failure and container resource exhaustion.
Correct verification. A test pod failure appears with its namespace, workload and container logs in the intended monitoring workspace. The measurement or controlled test provides evidence for the issue (Investigators can see aggregate cluster CPU but not which namespace caused the capacity spike) and complements the selected corrective action rather than simply repeating a recommendation.
Incorrect Answers
Configure actionable alerts for failed or delayed GitHub Actions and Azure Pipelines workflows with owner routing and deduplicated notifications. The azure monitor container insights for aks implementation and safeguard are still missing.
A controlled storage denial or networking failure produces attributable diagnostics with resource and timestamp context. It is not the complementary risk control for azure monitor container insights for aks.
Enable Azure Monitor VM Insights or an appropriate data collection configuration to observe supported machine performance and dependency health. This does not supply the required azure monitor container insights for aks action-and-control pair.