Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
An enterprise organization operates a multi-tenant Google Cloud environment where multiple development teams share a central CI/CD project. Each team builds containerized microservices and deploys them to dedicated Artifact Registry repositories in their respective workload projects.
To meet stringent security compliance standards, the DevOps team must ensure that:
How should the DevOps engineer configure the Cloud Build triggers and IAM permissions?
This option relies on the shared default Cloud Build service account ([PROJECT_NUMBER]@cloudbuild.gserviceaccount.com) to execute all pipeline triggers across all teams, attempting to enforce multi-tenant isolation via project-level IAM conditions.
The organization had only a single monolithic application owned by one team with no tenant isolation requirements.
This option suggests granting the Cloud Build Service Agent role (roles/cloudbuild.serviceAgent) directly to custom user-managed service accounts used by the triggers.
service-[PROJECT_NUMBER]@gcp-sa-cloudbuild.iam.gserviceaccount.com). Google Cloud explicitly warns against assigning service agent roles to any standard user accounts or user-managed service accounts.roles/artifactregistry.writer.roles/artifactregistry.writer or roles/logging.logWriter) or custom roles tailored to pipeline steps.You were configuring the Google-managed Cloud Build system identity itself when enabling platform APIs, rather than configuring trigger execution identities for pipeline tenants.
User-specified custom service accounts allow Cloud Build triggers to execute builds under a defined identity rather than using the default Cloud Build service account. This allows fine-grained access management and complete IAM isolation across different workloads and development teams.
roles/artifactregistry.writer restricted directly to the team's specific Artifact Registry repository and roles/logging.logWriter for build logs.roles/iam.serviceAccountUser to the development team on their dedicated service account allows them to associate that service account with their build triggers without granting excessive project-level permissions or managing long-lived static credentials.Assigning custom service accounts directly to Cloud Build triggers is Google Cloud's recommended architectural pattern for multi-tenant CI/CD pipelines. It provides strong boundary separation, enforces least privilege out of the box, and relies entirely on native IAM governance without operational overhead.
This option involves generating downloadable service account JSON keys, storing them in Secret Manager, and having the build steps fetch the secret and run gcloud auth activate-service-account to impersonate tenant identities at runtime.
A build step needed to authenticate to an external, non-Google Cloud third-party platform that does not support OpenID Connect (OIDC) or workload identity federation.
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 Validated