Setting Up a Cloud Solution Environment
What this domain tests
Setup questions check whether you know the sequence and the guardrails for getting a project ready: resource hierarchy (organization, folders, projects), billing account linkage, quotas, and the command-line and console tooling used to create and configure resources.
Concepts to master
- Resource hierarchy and inheritance. Policies and IAM bindings set at a folder or organization flow down to projects unless overridden. Understand that a project must belong to exactly one parent and that moving a project changes inherited policy.
- Billing. A project without an active billing account cannot use billable services. Budgets and alerts are notifications, not hard caps - a classic trap.
- Quotas. Per-project and per-region limits exist for APIs, CPUs, and other resources. Know that quota increases are requested, not instant, and that some limits are regional.
- Tooling. The console,
gcloud, and infrastructure-as-code tools each create the same underlying objects. Know how to set a default project and region in a CLI configuration so commands target the right place.
Traps to expect
Questions often blur the line between budget alerts and spending limits (there is no automatic shutdown), or between organization policy constraints and IAM roles. Another common trap: assuming a newly created project already has APIs enabled or a billing link. Also watch for regional versus global resource scope.
Rule of thumb
Set the hierarchy and billing link first, enable only the APIs you need, then apply least-privilege IAM at the highest sensible node. A worked example: to stand up a new environment, create a folder under the organization, attach the billing account to each project, enable required APIs, and set a budget with alerts - remembering the budget will warn, not stop, spending.