Which kubelet flag is used to set the maximum number of pods that can run on a node?

Correct answer: --max-pods=X

Option C is correct because the kubelet configuration flag `--max-pods` is the official and documented flag used to set the maximum number of pods that can be scheduled on a given node, with a default of 110. This flag is recognized in the Kubernetes documentation and is used by cloud providers to limit pod density per node. Option A is wrong because `--pod-limit` is not a valid kubelet flag and does not exist in the Kubernetes kubelet API. Option B is incorrect because `--pod-max-count` is also not a real kubelet flag and would result in an unrecognized argument error at startup. Option D is wrong because `--max-pod-count` is similarly not a valid kubelet flag, making it a distractor that sounds plausible but does not correspond to any actual Kubernetes configuration option.