The correct answer isBbecause the company wants to view bothAmazon EKS clustersandon-premises Kubernetes clustersfrom acentral locationwith theleast operational overhead.Amazon EKS Connectoris designed for this purpose. It allows externally managed Kubernetes clusters, including on-premises clusters, to be registered to AWS so they can be viewed in theAmazon EKS consolealongside native EKS clusters. This creates a centralized management experience without requiring the company to migrate or rebuild the existing on-premises clusters.

EKS Connector is a low-overhead solution because it extends visibility into Kubernetes environments that are not running directly on Amazon EKS. It provides centralized cluster registration and observability at the AWS management layer while preserving the existing cluster deployments. This is especially useful for hybrid Kubernetes environments where organizations want a single control point for inventory and visibility.

Option A is incorrect becauseAmazon CloudWatch Container Insightsis primarily for metrics, logs, and performance monitoring. Although it provides observability, it is not the primary service for centrally registering and viewing clusters themselves in a unified cluster-management context. Option C is incorrect becauseAWS Systems Manageris not the main service for centralized Kubernetes cluster management. Option D is incorrect becauseAmazon EKS Anywhereis used to run Kubernetes on-premises, but it is not the simplest way to centrally view existing clusters with the least operational effort.

AWS guidance for hybrid Kubernetes visibility recommendsAmazon EKS Connectorfor connecting external Kubernetes clusters to AWS. Therefore, it is the most appropriate solution.