Cloud Digital Leader Scaling with Google Cloud operations Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Create a shared Google Slides presentation documenting best practices for teams to reference.

  Why it's wrong here

  A shared Google Slides deck is a static reference artifact: it cannot enforce or automate any requirement, and its advice is only as good as the team's willingness to read and follow it. Even if teams do read it, they may interpret the guidance differently, leading to configuration drift across projects. In contrast, a golden path must be enforced programmatically at the moment resources are deployed, which documentation alone can never achieve. To make documentation effective, it would need to be codified into policy-as-code or deployment templates.

• ✓

  Use Terraform blueprints, organization policies, and Cloud Foundation Toolkit to create pre-configured landing zones that enforce standards automatically.

  Why this is correct

  Terraform blueprints from the Cloud Foundation Toolkit are production-ready, opinionated Infrastructure-as-Code modules that bake in Google Cloud best practices for networking, IAM, logging, and monitoring. When combined with organization policies (constraints that enforce guardrails at the organization level) and custom Terraform that provisions landing zones, every new project starts in a fully pre-configured, compliant state. This approach enforces the golden path automatically: teams inherit secure defaults without needing to manually configure resources, and any departure from standards requires an intentional exemption. This is the only option that operationalizes standards at scale, making the path the path of least resistance.

• ✗

  Grant all teams Organization Admin access so they can configure resources however they prefer.

  Why it's wrong here

  Granting Organization Admin to all teams is the antithesis of a golden path: it gives every team unrestricted ability to modify organization-level resources, bypass guardrails, and make inconsistent or insecure choices. It violates least privilege, expands the blast radius of any mistake, and makes auditing nearly impossible. Instead, the golden path should limit privileged access to a small platform team and use tools like Cloud Foundation Toolkit to pre-provision projects with sets of permissions that match teams' actual needs. This ensures teams can innovate within a controlled environment, not on top of the organization itself.

• ✗

  Hire a dedicated cloud architect to review every new project's design before it starts.

  Why it's wrong here

  A dedicated architect reviewing every new project design is a manual control that does not scale: as the number of projects and delivery velocity grow, the review queue becomes a bottleneck and a source of inconsistent judgment. Human reviews are also inherently fallible, and in a fast-moving CI/CD environment they often become a rubber stamp or a blocker. Automated enforcement via organization policies and policy-as-code (e.g., Terraform plan checks, Cloud Asset Inventory, or OPA-style policies) can evaluate every deployment consistently and immediately, catching violations before they reach production. Manual review still has a place for exceptional, high-risk designs, but it should be an exception gate, not the primary mechanism for maintaining the golden path.

Go deeper

Related to this question