Why might "ETCD" be deployed as a separate cluster from the Kubernetes control plane nodes in large production environments, and what is the trade-off?
Correct! Well done.
Incorrect.
The correct answer is B) Running etcd on dedicated nodes isolates its resource usage (etcd is sensitive to disk I/O latency) from control plane components, improving reliability and performance, at the cost of additional infrastructure to manage and maintain
Correct Answer
Running etcd on dedicated nodes isolates its resource usage (etcd is sensitive to disk I/O latency) from control plane components, improving reliability and performance, at the cost of additional infrastructure to manage and maintain
etcd performance is highly sensitive to disk write latency; co-locating it with other control plane components under heavy load can cause latency spikes affecting the whole cluster, so dedicated etcd nodes (a "stacked" vs "external" topology trade-off) are common in large deployments.