Manifest files declare the desired end state for Kubernetes objects and the control plane reconciles the live state to reach that declared state is correct.

Manifest files are declarative YAML or JSON documents that describe the desired configuration of Kubernetes objects such as Pods, Deployments, and Services. The control plane stores those object definitions and controllers continuously compare the actual cluster state with the declared state and then take actions to reconcile any differences until the desired state is reached.

GKE Config Connector is incorrect because it is a Google Cloud add on that lets you manage GCP resources through Kubernetes custom resources and it does not describe the fundamental Kubernetes declarative model used by manifests.

Manifests list explicit procedural steps that the cluster must execute to set up resources is incorrect because manifests are not procedural runbooks. They declare what the end state should be and the control plane figures out the steps to get there.

Manifests run imperative commands directly on individual nodes so that administrators can control each action is incorrect because manifests are applied to the API server and acted on by controllers and kubelets. Manifests do not contain commands that are executed directly on nodes.

Full AWS Practitioner Certification Question