Google Cloud / Basic: Resource and Access Boundaries

Google Cloud β€” Basic: Resource and Access Boundaries

Define projects, billing, identities, locations, and network contracts before selecting a service.

6 lessons Β· No account required

What you will learn

  • Explain hierarchy and inherited controls.
  • Separate authentication, authorization, and reachability.
  • Record ownership, location, and cost assumptions.

  1. Projects and the Resource Hierarchy

    Use the hierarchy to assign ownership and policy scope without confusing a project with an application, network, or billing account.

    Start learning

  2. Billing and Cost Ownership

    Separate payment relationships, resource ownership, forecasts, alerts, and enforceable controls before making a cost claim.

    Start learning

  3. IAM and Effective Authorization

    Reason about principal, permission, resource, and context instead of treating one role name as proof of access.

    Start learning

  4. Service Accounts and Credential Boundaries

    Separate deployment identity, runtime identity, credential discovery, and authority to impersonate a service account.

    Start learning

  5. Locations and Failure Domains

    Choose locations from service scope, data requirements, dependencies, and failure assumptions rather than a region name alone.

    Start learning

  6. VPC and Network Reachability

    Trace routes, addresses, firewall policy, name resolution, and application listeners as separate parts of a connection.

    Start learning
Back to course