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.
Your organization uses Google Cloud Infrastructure Manager (Infra Manager) to automate the provisioning of Terraform configurations across dozens of microservices. During a major scheduled release, multiple continuous integration/continuous delivery (CI/CD) pipelines execute concurrently in the same project, triggering multiple deployments at once.
Several deployments fail unexpectedly with API rate limit errors associated with the underlying Cloud Build orchestration polling deployment statuses.
What should you do to mitigate and resolve these deployment failures?
This approach restructures how automated deployment workloads interact with Google Cloud APIs by staggering execution queues or partitioning deployments across project-level boundary limits.
Because Cloud Build API rate limits are enforced at the project/organization level per unit of time, reducing concurrency through serialization or horizontally scaling quota across separate projects directly remedies API throttling during high-volume deployment windows.
lifecycle { prevent_destroy = true } block to all stateful resources defined in the Terraform configuration files.The prevent_destroy meta-argument is a Terraform lifecycle configuration that prevents accidental destruction of critical stateful resources (such as Cloud SQL instances or persistent disks) during terraform apply or terraform destroy operations.
The team needed to safeguard production databases from unintended deletion during automated pipeline updates when resource parameters were modified.
--quota-validation=ENFORCED on all automated deployment commands.The --quota-validation=ENFORCED flag in Infrastructure Manager instructs the service to evaluate whether proposed resource allocations will exceed standard Google Cloud resource quotas before applying changes.
google_compute_network, google_compute_disk, and google_compute_instance resources.ENABLED (logging only) or ENFORCED (hard blocking) mode.The deployment pipeline was failing because Terraform manifests attempted to provision more Compute Engine virtual machine instances or persistent disks than allowed by the project's compute quota.
roles/iam.serviceAccountTokenCreator role to the default Cloud Build service account.The roles/iam.serviceAccountTokenCreator role allows an identity or service account to impersonate other service accounts and generate short-lived OAuth2 access tokens or OpenID Connect (OIDC) identity tokens.
403 Forbidden) when configuring service account impersonation across actuation pipelines, but does not address API rate limit exceptions (429 Resource Exhausted).The CI/CD pipeline failed during initialization because Cloud Build lacked permission to generate delegated credentials or impersonate the Terraform actuation service account.
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