An enterprise organization is automating infrastructure provisioning on Google Cloud using Infrastructure as Code. During a major deployment using Cloud Deployment Manager templates, several resource creation calls fail mid-execution because regional API allocation limits are exceeded. Additionally, resource updates fail or execute out of order because implicit creation order is relied upon. Which TWO actions should the Cloud Architect recommend to address these operational and architectural failures? (Select TWO.)
- Explicitly define resource dependencies within Deployment Manager templates using the dependsOn directive.Cevap
- Audit project resource limits and request required regional quota increases prior to launching large-scale automated deployments.Cevap
- CConfigure the deployment pipeline to maintain state files in unversioned local storage on the execution runner to avoid remote state synchronization latency.
- DGrant the primitive Owner IAM role to the Deployment Manager execution service account to bypass regional resource quota enforcement.
Cevap
The correct actions are to explicitly define resource dependencies within Deployment Manager templates using the dependsOn directive, and to audit project resource limits and request required regional quota increases prior to launching large-scale automated deployments.
Declaring resource dependencies explicitly with dependsOn ensures Deployment Manager builds resources in the required topological sequence. Proactively verifying and requesting regional quota increases prevents deployment pipelines from failing when provisioning large infrastructure footprints.
Adım Adım Çözüm
Anahtar Kavram
Deployment Manager dependency management and proactive quota planning for Infrastructure as Code automation