The correct options are kube-apiserver and extension-apiserver.

The kube-apiserver implements the aggregation layer and acts as the aggregator that accepts requests for aggregated API groups and proxies them to registered backend servers using APIService objects. It also handles cluster wide concerns such as authentication and authorization so that aggregated servers can focus on serving their API groups.

The extension-apiserver is an example of an aggregated API server that implements additional API groups or custom resources and registers with the aggregator via APIService records. It typically runs as a separate process or pod and the aggregator routes matching API calls to it.

cloud-controller-manager is responsible for cloud provider specific controllers and it does not act as an API server so it is not part of the aggregation layer.

kube-controller-manager runs built in controllers that reconcile cluster state and it does not host or register API endpoints for aggregation.

kube-scheduler is responsible for placing pods onto nodes and it does not provide or register API endpoints so it does not participate in API aggregation.

Full AWS Practitioner Certification Question