Google Cloud ACE Setting Up a Cloud Environment

0.0(0)
studied byStudied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/127

encourage image

There's no tags or description

Looks like no tags are added yet.

Last updated 5:25 AM on 2/3/26
Name
Mastery
Learn
Test
Matching
Spaced
Call with Kai

No analytics yet

Send a link to your students to track their progress

128 Terms

1
New cards

GCP Resource Hierarchy

A structured way to manage resources across an organization, enabling inheritance of policies, billing, and access control.

2
New cards

Resource

The fundamental building block of Google Cloud, such as a VM instance, a storage bucket, or a BigQuery dataset.

3
New cards

Organization

The root node of the Google Cloud resource hierarchy, representing a company or entity.

4
New cards

Folder

A grouping mechanism between the Organization and Projects used to organize resources by department or environment.

5
New cards

Project

The base-level container for resources; all Google Cloud resources must belong to exactly one project.

6
New cards

Organization Node Requirement

Requires a Google Workspace or Cloud Identity account to be created.

7
New cards

Resource Manager

The tool/API used to programmatically manage the resource hierarchy (Organizations, Folders, and Projects).

8
New cards

Inheritance

The principle where policies (IAM and Org Policies) applied at a parent level automatically apply to all child resources.

9
New cards

Organization Admin

The IAM role that provides full administrative access to all resources in the organization.

10
New cards

Folder Admin

The IAM role that allows a user to create, edit, and delete folders within an organization or parent folder.

11
New cards

Project Creator

The role required to create new projects within an organization or folder.

12
New cards

Project ID

A unique, permanent string used to identify a project; it cannot be changed after creation.

13
New cards

Project Name

A user-defined, non-unique string used to label a project; it can be changed at any time.

14
New cards

Project Number

A unique, system-generated numerical identifier for a project assigned by Google Cloud.

15
New cards

Project Deletion

When a project is deleted, it is "soft-deleted" for 30 days before all resources and data are permanently removed.

16
New cards

IAM (Identity and Access Management)

The framework that defines "who" (identity) can do "what" (role) on "which" resource.

17
New cards

Principle of Least Privilege

The security practice of granting users only the minimum permissions necessary to perform their job functions.

18
New cards

IAM Policy

A collection of statements that define access control for a resource; consists of a list of bindings.

19
New cards

IAM Binding

A mapping of a single role to one or more members (identities).

20
New cards

Primitive Roles

Basic legacy roles (Owner, Editor, Viewer) that offer broad, non-granular permissions.

21
New cards

Predefined Roles

Google-managed roles that provide granular access to specific services (e.g., Compute Instance Admin).

22
New cards

Custom Roles

User-defined roles that combine specific permissions; used when predefined roles are too broad.

23
New cards

Member: Google Account

An individual email address associated with a person (e.g., gmail.com or workspace domain).

24
New cards

Member: Service Account

An identity used by applications or VMs to authenticate and access GCP resources programmatically.

25
New cards

Member: Google Group

A collection of Google Accounts; the best practice for managing permissions at scale.

26
New cards

Member: Cloud Identity Domain

Represents all Google Accounts created within a specific organization's domain.

27
New cards

IAM Policy Inheritance Flow

Organization -> Folder -> Project -> Resource.

28
New cards

Additive Policy

IAM policies are additive; if a user has Viewer at the Folder level and Editor at the Project level, they are an Editor.

29
New cards

Billing Account

A resource that defines who pays for a specific set of Google Cloud projects.

30
New cards

Billing Account Linkage

A project must be linked to a valid billing account to use paid services or exit the Free Trial.

31
New cards

Billing Account Creator

The role required to create new billing accounts for the organization.

32
New cards

Billing Account User

The role that allows a user to link projects to a billing account.

33
New cards

Billing Account Administrator

The role providing full control over billing accounts, including managing users and payment methods.

34
New cards

Cloud Billing Export

A feature that sends detailed billing data to a BigQuery dataset or Cloud Storage bucket for analysis.

35
New cards

Budget Alerts

Notifications triggered when spending reaches a defined percentage of a budget (e.g., 50%, 90%, 100%).

36
New cards

Disabling Billing

The action of unlinking a project from its billing account, which stops all services in that project.

37
New cards

Quota

A limit on the amount of a particular GCP resource that a project can use (e.g., CPU cores in a region).

38
New cards

Rate Quota

A limit on the number of API requests allowed over a specific period.

39
New cards

Allocation Quota

A limit on the total number of resources that can exist (e.g., total number of static IPs).

40
New cards

Organization Policy Service

A service that provides centralized, programmatic control over the organization's resources.

41
New cards

Org Policy Constraint

A specific restriction applied via an Organization Policy (e.g., "Restrict Resource Usage" to specific regions).

42
New cards

IAM vs. Org Policy

IAM defines WHO has access; Org Policy defines WHAT can be done with a resource regardless of the user.

43
New cards

Trust Boundary

The project level serves as the primary trust and isolation boundary for resources.

44
New cards

Flat Hierarchy

A structure where all projects are directly under the Organization node without folders.

45
New cards

Departmental Hierarchy

A structure where folders are used to separate different departments (e.g., Engineering, Marketing).

46
New cards

Environment Hierarchy

A structure where folders separate development stages (e.g., Dev, Staging, Prod).

47
New cards

Project Move Requirement

To move a project, you need 'resourcemanager.projects.update' on the project and 'resourcemanager.projects.create' on the destination.

48
New cards

Global Resource

A resource accessible across all regions (e.g., Cloud DNS, VPC Networks, IAM).

49
New cards

Regional Resource

A resource tied to a specific geographic region (e.g., Static IP, Subnets, App Engine).

50
New cards

Zonal Resource

A resource tied to a specific data center zone (e.g., Compute Engine VM, Local SSD).

51
New cards

Resource ID

The specific identifier for a child resource (e.g., the name of a VM instance).

52
New cards

Best Practice: Groups over Individuals

Assign IAM roles to Google Groups rather than individual email addresses to simplify management.

53
New cards

Service Account User Role

Allows a user to "act as" a service account, often required to deploy VMs that use that service account.

54
New cards

Default Service Account

Automatically created service accounts (e.g., Compute Engine default service account) with broad permissions.

55
New cards

Service Account Key

A JSON file used to authenticate as a service account outside of Google Cloud; should be managed carefully.

56
New cards

Google Cloud Console

The web-based graphical user interface for managing GCP resources.

57
New cards

Cloud Shell

An ephemeral, browser-based terminal with the gcloud CLI pre-installed.

58
New cards

gcloud CLI

The command-line interface for interacting with Google Cloud services.

59
New cards

gsutil

The CLI tool specifically for managing Cloud Storage buckets and objects.

60
New cards

bq

The CLI tool specifically for interacting with BigQuery.

61
New cards

Cloud SDK

The package containing gcloud, gsutil, and bq tools.

62
New cards

Compute Instance Admin (v1)

A predefined role that allows full control over VMs but not the networks they sit on.

63
New cards

Storage Object Admin

Allows full control over objects in a Cloud Storage bucket, but not the bucket itself.

64
New cards

Storage Admin

Allows full control over Cloud Storage buckets and the objects within them.

65
New cards

View-only access for billing

The Billing Account Viewer role.

66
New cards

Best Practice for Multiple Teams

Assign each team their own Project to isolate billing and administrative control.

67
New cards

Labels

Key-value pairs used to categorize and filter resources (e.g., env:prod, dept:finance); used for billing granularity.

68
New cards

Tags

Special labels used primarily for networking and firewall rules to identify groups of VMs.

69
New cards

Quotas: Increasing Limits

Most quotas can be increased by submitting a request via the Google Cloud Console.

70
New cards

Self-Service Quota Increase

A feature for certain resources where small quota increases are granted automatically.

71
New cards

Billing: Sub-accounts

Used by resellers to manage multiple customers under a single master billing account.

72
New cards

Project Suffix

A random string sometimes added to a Project ID to ensure global uniqueness.

73
New cards

Moving Projects between Orgs

A complex process that usually requires support or specific migration tools.

74
New cards

Resource Manager API

Must be enabled to programmatically manage folders and projects.

75
New cards

Organization Policy: skipDefaultNetwork

A constraint that prevents the automatic creation of a "default" VPC in new projects.

76
New cards

Organization Policy: allowedLocations

A constraint that restricts which regions resources can be deployed in.

77
New cards

Cloud Identity

The Identity-as-a-Service (IDaaS) that stores user accounts for Google Cloud.

78
New cards

Super Admin

The highest level of access in Google Workspace/Cloud Identity, distinct from the GCP Org Admin.

79
New cards

Cloud KMS

Key Management Service used to manage encryption keys for resources.

80
New cards

Encryption at Rest

Google Cloud encrypts all customer data at rest by default.

81
New cards

Encryption in Transit

Data is encrypted automatically when moving between Google's controlled facilities.

82
New cards

VPC (Virtual Private Cloud)

A global virtual network that belongs to a Project.

83
New cards

Subnet

A regional resource that defines IP address ranges within a VPC.

84
New cards

Project-level IAM

Assigning a role at the project level gives that user access to all resources inside that project.

85
New cards

Folder-level IAM

Assigning a role at the folder level gives that user access to all projects inside that folder.

86
New cards

Org-level IAM

Assigning a role at the organization level gives that user access to every project in the company.

87
New cards

Service Account Creator

The role required to create service accounts within a project.

88
New cards

Service Account Key Creator

The role required to generate JSON keys for service accounts.

89
New cards

Best Practice: Naming Projects

Use a consistent naming convention that includes the environment and application name.

90
New cards

Billing: Credit Cards vs. Invoicing

Standard accounts use credit cards; large organizations can apply for monthly invoicing.

91
New cards

Budget Alert: Pub/Sub

Budgets can send notifications to Pub/Sub to trigger automated cost-control scripts.

92
New cards

Cloud Console Mobile App

Used to monitor resources and receive alerts on a smartphone.

93
New cards

Shared VPC

Allows an organization to connect resources from multiple projects to a common VPC network.

94
New cards

Host Project

In Shared VPC, the project that contains the shared network resources.

95
New cards

Service Project

In Shared VPC, projects that use the network resources of the Host Project.

96
New cards

IAM Role: Browser

Allows a user to see the project's metadata but not its resources.

97
New cards

IAM Role: Project IAM Admin

Allows a user to manage access control policies for a project.

98
New cards

IAM Policy Troubleshooting

Use the IAM Policy Troubleshooter to see why a user has or doesn't have a permission.

99
New cards

Audit Logs

Records of administrative actions and data access within your GCP hierarchy.

100
New cards

Admin Activity Logs

Logs for API calls that modify resources; always enabled and free.