A reviewer answers “secure AKS” with a twelve-chart service mesh for the canal scheduler. Which host and cluster security controls should the security engineer prioritize instead?
Select an answer to reveal the explanation.
Short Explanation
Twelve Helm charts aren’t the AZ-500 answer. Patch the node image, keep Kubernetes current, kill public node IPs, and force egress through the hub firewall—that’s cluster security, not an app cookbook.
Full Explanation
Official AKS security monitoring and hardening emphasize host and cluster controls: current node images and Kubernetes versions, no public IPs on nodes where appropriate, and restricted egress (for example through a hub firewall) as a security outcome. Deep service-mesh packaging and Helm cookbooks belong to application-development tracks, not this AZ-500 compute-security item. Forced-tunnel network design details remain Domain 2; this question only requires recognizing egress lockdown as part of securing the cluster.