Answer-first summary for fast verification
Answer: Store public and private charts in OCI format by using Artifact Registry.
Artifact Registry is the optimal solution because it is a fully managed Google Cloud service that natively supports Helm charts in OCI format. It provides built-in IAM access control, integrates seamlessly with VPC Service Controls for security perimeters, and allows uniform management of both public and private charts in a single, serverless environment. Options B, C, and D fail to fully meet the requirements: B uses external services without native VPC support, C requires manual Helm index management and is less efficient, and D adds operational complexity with a self-hosted server.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
How can you uniformly manage Helm charts for containerized applications, including both public and private dependencies, while implementing native access control and VPC Service Controls to address security concerns about public Helm repository usage?
A
Store public and private charts in OCI format by using Artifact Registry.
B
Store public and private charts by using GitHub Enterprise with Google Workspace as the identity provider.
C
Store public and private charts by using Git repository. Configure Cloud Build to synchronize contents of the repository into a Cloud Storage bucket. Connect Helm to the bucket by using https://[bucket].storage-googleapis.com/[helmchart] as the Helm repository.
D
Configure a Helm chart repository server to run in Google Kubernetes Engine (GKE) with Cloud Storage bucket as the storage backend.