Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
An operations team is deploying workloads to a Google Kubernetes Engine (GKE) cluster. The container images are stored in a private Artifact Registry repository in the same project.
To adhere to the principle of least privilege, the team configures the GKE cluster nodes to use a dedicated custom IAM service account rather than the Compute Engine default service account. The cluster nodes only need permission to download and run the container images.
Which IAM role should be assigned to the custom service account attached to the GKE nodes?
The Storage Admin (roles/storage.admin) role provides full administrative control over Cloud Storage buckets and objects. This includes creating buckets, deleting buckets, changing bucket permissions, and reading/writing all stored objects.
roles/artifactregistry.*) rather than Cloud Storage IAM roles.gcr.io), images were directly stored in backing Cloud Storage buckets, leading some administrators to use storage roles. Artifact Registry decouples these permissions and requires Artifact Registry-specific roles.gs://) buckets, not Artifact Registry repository APIs.roles/storage.objectViewer for pulling, but Artifact Registry requires roles/artifactregistry.reader.The service account belonged to an infrastructure management automation system designed to create, configure, and delete Cloud Storage buckets across the project.
The Artifact Registry Administrator (roles/artifactregistry.admin) role gives users full control over Artifact Registry repositories and their contents. This includes creating repositories, deleting repositories, modifying IAM policies on repositories, and managing repository configurations.
The task involved provisioning a central identity for a Terraform or Infrastructure-as-Code pipeline responsible for creating, updating, and securing Artifact Registry repositories.
The Artifact Registry Reader (roles/artifactregistry.reader) role is a predefined Identity and Access Management (IAM) role that provides read-only access to Artifact Registry resources. It grants the essential permissions required to view repository metadata and pull container images or language packages without granting permissions to upload, modify, or delete artifacts.
artifactregistry.repositories.downloadArtifacts) needed to authenticate and stream image layers to the node runtime.
Granting the Artifact Registry Reader role directly to the custom node service account provides the minimal necessary permissions for GKE image deployment while eliminating security risks associated with administrative or write-level privileges.
The Artifact Registry Writer (roles/artifactregistry.writer) role is designed for CI/CD pipelines, build systems, and developers who need to read and upload artifacts. It grants permissions to read repositories as well as push new container images and create repository tags.
artifactregistry.repositories.uploadArtifacts and download capabilities.The cluster nodes were specifically running continuous integration (CI) worker workloads or container builder processes that compile code and push newly created container images to the registry.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated