kubeadm init hangs after printing that it created the API client and is waiting for the control plane. Which two causes are named? Choose two.

Answer: A. A network connectivity problem on the machine
C. Control plane containers crash-looping or hanging

Those are the two most common causes; the container states are inspected with crictl. A missing network add-on shows up later as a Pending CoreDNS, and an unsupported kernel fails preflight.

Source: Troubleshooting kubeadm (Kubernetes) — kubeadm blocks waiting for control plane during installation