Foundations for Google Clouds
Google Cloud foundations are the setup concepts every other service depends on: projects that group resources, billing accounts that pay for them, the gcloud CLI and console, and IAM, which controls who can do what. This unit sits at the start of the roadmap because every later deployment needs a project and a safe set of permissions.
Stage: Setup · Part of the Google Cloud roadmap · Last reviewed 19 November 2026
What to learn in Foundations
- Create a project, link a billing account and set a budget alert
- Install gcloud and authenticate with an account or a service account
- Grant a role to a user at project level using IAM
- Explain why least privilege matters and pick a narrow predefined role
- Enable an API for a project before using its service
Foundations interview questions
What is the difference between a project and a billing account in Google Cloud?
A project is the container for resources, APIs and IAM policies. A billing account is the payment profile that pays for usage. One billing account can be linked to many projects, and a project must be linked to an active billing account before paid services work.
Why should you use a service account instead of a personal login for an application?
A service account is an identity for software, not a person. You can give it only the roles the app needs, rotate or avoid long-lived keys, and revoke it without affecting any user. Personal credentials tie access to an individual and are harder to audit.
Where Foundations fits in the Google Cloud roadmap
Foundations belongs to the Setup stage (beginner level). Environment and access.
Back to the full Google Cloud roadmap