
Ultimate access to all questions.
You receive a Cloud Monitoring alert about potential malicious activity on a node in your Google Kubernetes Engine (GKE) cluster, suggesting a compromised container. You need to isolate the node to prevent further compromise while minimizing disruption to other applications in the cluster. What is the recommended course of action?
A
Taint the suspicious node to prevent Pods that have interacted with it from being scheduled on other nodes in the cluster
B
Scale down the deployment associated with the compromised container to zero other nodes
C
Restart the node to disrupt the malicious activity, and force all Pods to be restructured on other nodes.
D
Cordon the node to prevent new Pods from being scheduled, the drain the node to safely remove existing Pods and reschedule them to other nodes.