問題文
A platform team deploys the Kubernetes connector into its clusters. What does the connector bring that onboarding the underlying cloud account does not?
選択肢
- It is the only way to scan container images, so a cluster without the connector leaves every image it runs unexamined by any scanner.
- Visibility into cluster-internal objects and, when enabled, the ability to admit or reject workloads at the cluster boundary.
- It provides the audit records for the cloud account, so audit log collection does not have to be enabled during onboarding, whatever provider hosts the cluster.
- The connector replaces the cloud account onboarding for any account that hosts a cluster, so the provider-side template no longer has to be deployed once every cluster in that account has the connector installed and reporting.