Prepare and test your skills

Prepare and test your skills

Setting up cloud projects and accounts means creating the containers, identities, policies, and basic services that all other Google Cloud work depends on. The work flows from the organization to folders to projects (opens in a new tab) to resources, with billing, APIs, and access checked along the way. A project is the base container where virtual machines, buckets, and databases live, so most setup tasks are scoped to one project at a time.
The resource hierarchy is the parent-child tree that organizes Google Cloud use for billing and administration. The hierarchy flows in fixed order from organization to folders to projects to service resources, and settings attached at a parent flow downward to everything below it. A separate Google Cloud project is typically created for each administrative domain, such as a department, country, or use case, so management and costs stay aligned to the owner.
The three container levels have different positions and roles. The Organization container is the top-level root tied to a Cloud Identity or Google Workspace domain, and policies set there apply to every folder and project beneath it. A Folder is an optional middle layer that groups related projects by team, environment, or application for delegated management.
| Level | Position | Central role |
|---|---|---|
| Organization | Top node above all folders and projects | Company-wide authority and central policy |
| Folder | Between organization and projects | Groups projects for team or environment management |
| Project | Base container under folder or organization | Holds resources and scopes billing and access |
How centralized management works is that an administrator attaches Identity and Access Management (IAM) roles, tags, or Organization Policy rules at the Organization or Folder, then each child inherits them automatically. IAM controls who can act, while Organization Policy controls what configuration is allowed, such as blocking public IP addresses or restricting resource locations. Labels and display_name provide granular tracking within and across projects and stay editable after creation, so costs can be grouped by environment or owner without recreating resources.
Applying organizational policies to the resource hierarchy means enforcing centralized rules that flow from a parent to all of its descendants. The Organization Policy Service provides this control through organization policies made of constraints, which are individual restrictions on operations or field values. When a user tries to create or update a resource that violates an enforced constraint, Google Cloud blocks the operation.
Boolean constraints and list constraints work in different ways. Boolean constraints are on-or-off rules with an enforced state of true or false and no list of values to manage. List constraints permit a request only when its value matches allowedValues and is not denied. Three common list constraints are gcp.resourceLocations for allowed regions, gcp.restrictServiceUsage for allowed API services, and gcp.restrictNonCmekServices for services that require customer-managed encryption keys (CMEK).
Policy inheritance means a policy enforced on an organization covers all folders and projects under it, and a policy enforced on a folder covers all projects in that folder, including projects added later. A policy override is a different policy set directly on a child folder or project, so only that branch operates under the exception while production keeps the strict baseline. First the strict rule is enforced at the top, then the exception is set on the development or testing folder or project where it is justified.
Exam tip: IAM controls who can act on resources, while Organization Policy controls what configuration is allowed on resources.
Granting members Identity and Access Management (IAM) roles within a project is the process of binding a principal to a role on a specific resource. Identity and Access Management (IAM) enforces access through an allow policy that connects a principal, a role, and a resource. A role granted on a project, folder, or organization inherits downward to all contained resources.
A principal is any identity that can receive access, including Google Accounts for individuals, Google Groups for teams, service accounts for workloads, and workforce identity pool identities for external users. In gcloud, a binding uses the form user:my-user@example.com, while the console accepts the plain email address in the New principals field. Roles differ in breadth and maintenance, so the choice affects both security and upkeep.
| Role type | Who defines it | Scope of access |
|---|---|---|
| Primitive, such as Owner and Editor | Very broad access across all services in a project | |
Predefined, such as roles/SERVICE.IDENTIFIER | Narrow access for a specific service or job | |
Custom, such as projects/PROJECT_ID/roles/IDENTIFIER | Customer organization | Exact permission set for a specific task |
Primitive roles Owner, Editor, and Viewer grant far more access than most tasks need and should not be used in production. Predefined roles support least privilege better because they match a service or job function, and custom roles match a task most closely but must be maintained over time. The Google Cloud console and gcloud CLI update the same allow policy, so either tool grants the same access. In the console, the workflow is to open IAM for the selected project, folder, or organization, enter the principal identifier exactly, select a least-privilege role with an optional condition, and click Save. In the CLI, the pattern names the resource type, resource, member, and role, such as gcloud projects add-iam-policy-binding my-project --member=user:my-user@example.com --role=roles/cloudbuild.builds.viewer.
Managing users and groups in Cloud Identity means creating organization-controlled identities that IAM can then use for Google Cloud access. Cloud Identity is an Identity as a Service (IDaaS) solution that centrally manages users and groups in a domain and can federate with providers such as Active Directory. Each Google Workspace or Cloud Identity account links to exactly one organization resource, and IAM roles granted at that organization flow down to all child projects.
A Google group is a collection of users where each member inherits the IAM roles granted to the group, so access is managed by changing membership instead of editing many bindings. To create a group, open the Groups page for the organization, click Create, enter name and email, add members, and submit. Group creation privileges come from Workspace admin roles, while viewing groups from the Google Cloud console also needs IAM roles such as Organization Viewer. Before deleting a group, revoke all IAM roles from it and wait at least 7 days, because deletion is irreversible.
Google Cloud Directory Sync (GCDS) copies users and groups from Active Directory or LDAP into Cloud Identity using LDAP on the on-premises side and HTTPS with the Directory API on the cloud side. Data flows from Active Directory to GCDS through LDAP, then from GCDS to Cloud Identity, keeping cloud accounts aligned without manual entry. Federation with sync requires two accounts per user, an external account plus a Cloud Identity account, while Workforce Identity Federation needs only the external account.
Enabling APIs within projects means turning on a service interface for one specific project before that project can use it. Enabling an API accepts its Terms of Service and billing responsibility for that project, and the same API can stay disabled in another project. Cloud APIs give code a standard JSON REST way to reach services, with client libraries handling connection and authentication.
The API Library is the catalog where APIs are browsed by category or search, showing service name, status, and client library instructions. To enable from the console, select the target project, open the API page, and click Enable. To enable from the CLI, point gcloud at the correct project with billing verified, then run gcloud services enable with service names such as pubsub.googleapis.com. Enabling one API automatically enables the APIs it depends on, but gcloud services list --project $PROJECT_ID should still be used to verify every required name is present.
API activation requires the serviceusage.services.enable permission, supplied by Owner or Service Usage Admin, while Project Creator alone only permits creating a project. Billing must be linked first because usage is charged to the billing account associated with the project where the API is enabled. When a call touches multiple projects, the client project owns the credentials and the resource project owns the target, and client-based APIs charge the client project while resource-based APIs charge the resource project.
Provisioning products in Google Cloud Observability means setting up logging, monitoring, and alerting so project health can be seen and investigated. Google Cloud Observability collects telemetry from resources and applications into Cloud Monitoring for metrics and Cloud Logging for log storage and search. The Observability API must be enabled in a billed project before managing buckets, views, and links.
The Ops Agent is a single agent on Compute Engine virtual machine (VM) instances that sends metrics to Cloud Monitoring and logs to Cloud Logging. Telemetry flows from the Ops Agent on each VM to those services, where it appears in charts, dashboards, and Logs Explorer. Each VM needs the cloud-platform access scope and a service account with Monitoring Metric Writer and Logs Writer, and a VM Extension Manager policy installs and maintains the agent across a fleet selected by labels and OS type with version set to current-major and autoupgrade enabled.
A log bucket is the storage container that controls retention for all logs it holds, with custom retention from 1 to 3650 days and default encryption at rest. A log sink is a routing rule that forwards matching logs to BigQuery for SQL analysis, Cloud Storage for low-cost archival, or Pub/Sub for real-time delivery. A custom dashboard visualizes internal metrics such as CPU, memory, network, disk I/O, and response times, while an uptime check probes a public HTTP, HTTPS, or TCP endpoint from Google Cloud checkers and triggers an alerting policy through email, PagerDuty, or Slack when it fails.
Assessing quotas and requesting increases means comparing current use against the allowed maximum and formally asking to raise an adjustable ceiling. Quotas generally apply per Google Cloud project and restrict consumption to ensure fairness and prevent overload, while system limits are fixed attributes such as identifier length that cannot be changed. Rate limits control how often an action can happen over time, such as API calls per minute, while allocation limits control how many resources can exist at once, such as load balancers or projects.
The Quotas page shows current use against each quota and links to the adjustment form for that service, metric, and region. Checking quotas requires Project Owner, Project Editor, or Quota Viewer, while modifying quotas requires Owner, Editor, Quota Administrator, or a custom role with serviceusage.quotas.update. The request workflow selects the quotas, clicks Edit quotas, enters contact details and justification with the new value, submits for review, and waits 24 to 48 hours before scaling.
Quota scope defines the boundary a limit applies to, and both regional and project-wide quotas must have room before creation succeeds. For example, Cloud Run allows 1,000 services and 1,000 jobs per project and region, and an increase in one region does not raise another region. Available quota does not guarantee physical capacity, because a zone can run out of a resource such as IP addresses even when quota remains, in which case the path is to use another project or region.
Setting up standalone organizations means creating the root Organization resource that gives a company central ownership of all folders, projects, and billing accounts. The Organization resource is automatically provisioned after domain verification through Google Workspace or Cloud Identity, with no separate create command. Each identity account links to exactly one organization tied to exactly one domain, and projects created before the organization stay under No organization until moved in.
The Super administrator is the domain-level administrator who verifies the domain, creates the organization, and assigns the Organization Administrator role, then stays available for recovery. The Organization Administrator (roles/resourcemanager.organizationAdmin) has full control over one organization and its IAM policies but cannot access other organizations and by default cannot create folders or projects without extra roles. Cloud Billing administration is kept separate, with Billing Account Creator bringing accounts into the organization, Billing Account Administrator managing payment and links, and Billing Account User linking projects to pay for them.
The hierarchy places the Organization at the root, optional Folders in the middle, and Projects at the base to hold service resources, with every child having exactly one parent. Folders can nest up to 10 levels deep to model departments or environments such as production and non-production. The effective policy at any node equals its directly attached policies plus all policies inherited from its ancestors, so one grant at the top applies consistently below.
Setting up cloud networking means creating private networks, address space, firewall rules, and name resolution for Google Cloud workloads. A Virtual Private Cloud (VPC) network is the top-level private container that holds resources and controls how they connect, while each subnet inside it belongs to one region and supplies IP addresses in that region. Every workload needing private connectivity depends on a VPC network and a subnet for its address.
Traffic flows from regional resources to endpoint IPs allocated from subnets in the same region as the service attachment, with IPv4 addresses allocated automatically unless a static reservation is used and IPv6 requiring a static /96 reservation. A static internal address stays reserved after its VM is deleted, while an ephemeral address is released back to the subnet pool. Shared VPC keeps the VPC network and subnets in a host project while workloads live in service projects, requiring Compute Network Admin on the service project and Compute Network User on the host project.
VPC firewall rules are defined at the VPC level but enforced on each VM, and they can target all instances, instances with specific network tags, or instances with specific service accounts. A custom network denies all ingress by default and needs a higher-priority allow rule for VM-to-VM traffic, while the default network allows internal traffic through default-allow-internal. Cloud DNS translates names to IPs, with private zones visible only to authorized VPC networks and public zones publishing authoritative records for the internet.
Confirming availability in geographical locations means verifying that a service, feature, or capacity exists in a target region or zone before deployment. The three primary verification tools are the Google Cloud Console for visual checks, the gcloud CLI for terminal queries, and the official Cloud Locations page for product-by-location lists. Verification must account for resource scope, because global, regional, and zonal resources follow different reachability rules.
Regions and zones define where resources can be used and what failures they survive. A global resource is reachable from any region or zone, a regional resource is usable in any zone of the same region, and a zonal resource is usable only in the same zone. For example, VPC networks and images are global, subnets and regional disks are regional, and Compute Engine VM instances and zonal disks are zonal, so a disk can only attach to a VM in the same zone.
Wider scope generally brings higher availability: single-zone deployments target 99.9%, multi-zone regional deployments target 99.99%, and multi-region deployments target 99.999%. Traffic flows from clients to a global load balancer, then to regional backends in multiple zones, then to replicated data with backups in another location for region failover. Colocating dependent resources such as Compute Engine and Cloud Storage in the same region reduces latency and avoids cross-region egress, while VPC Service Controls perimeters keep data and API calls inside approved networks.
Configuring Cloud Asset Inventory and using Gemini Cloud Assist to analyze resources means keeping a searchable metadata record and asking plain-language questions about it. Cloud Asset Inventory is a global metadata service that collects resource, policy, and relationship data for compliance tracking, audits, and analytics. Gemini Cloud Assist is a generative AI assistant in the Cloud Assist panel that reads telemetry, logs, and inventory metadata to answer questions, suggest code, and recommend fixes.
An asset export is a point-in-time snapshot that flows from Cloud Asset Inventory to Cloud Storage for audit files or to BigQuery for SQL analytics, preserving history beyond the 35-day change window. Search flows from the caller with a project, folder, or organization scope, using searchAllResources for metadata and searchAllIamPolicies for allow and deny policies, with snapshot time within the last 35 days and up to 500 results per page. Effective-permission analysis with analyze-iam-policy combines inherited bindings and custom roles, requiring permissions to read both resources and policies plus iam.roles.get.
Gemini Cloud Assist investigations combine logs and metrics into Issue, Relevant Observations, and Hypotheses with recommended fixes that can be attached to a support case. Cloud Asset Inventory uses periodic sync with eventual consistency, so it fits scheduled audits, drift reporting, and delay-tolerant Pub/Sub notifications. The service API directly fits immediate validation, such as verifying a firewall rule before cutover or revoking access right now, where stale inventory data could break availability or security.
Continue with this study guide: 1.1 Setting up cloud projects and accounts
Managing billing configuration means connecting projects to the accounts that pay for them and then tracking that spend with budgets and exports. A Cloud Billing account (opens in a new tab) is the Google Cloud resource that pays for usage and tracks costs for linked projects. Usage costs flow from resources in a project to the linked Cloud Billing account, and payment for those costs flows through a connected Google payments profile.
How Cloud Billing accounts connect usage to payment depends on the link between projects, the billing account, and the payments profile. The Google payments profile holds payment instruments, billing contacts, and payment history, while the Cloud Billing account tracks which projects used what resources. A project must be linked to an active billing account in good standing, or the project cannot use Google Cloud services, even services that are otherwise free. Every Cloud Billing account is connected to one Google payments profile, and each account operates in a single currency.
An organization resource plus the correct Identity and Access Management (IAM) roles are required before a billing account can be created. A company domain establishes identity with Google through Google Workspace or Cloud Identity, which automatically creates an organization resource tied to exactly one domain. Projects and billing accounts created under that domain become child resources of the organization, so IAM policies and organization policies inherit downward. Once the organization exists, a new billing account can be created from the Google Cloud console billing page and linked to one or more projects.
The creator must hold specific roles on the organization before creating billing:
Creation and management are divided by scope because creation happens at the organization level while daily control happens at the billing account level. Billing Account Creator is granted on the organization and allows creation of new accounts inside that organization. Billing Account Administrator is normally granted on a specific billing account and allows management of settings, budgets, billing export, associations, and closing or reopening the account. Billing Account Viewer gives read-only visibility such as account name, currency, and open or closed state.
Linking a project to a billing account shows why permissions are checked on both sides. Data and control flow from the project to the billing account only after both checks pass: the caller needs billing.resourceAssociations.create on the billing account and resourcemanager.projects.createBillingAssignment on the project. Inheritance flows downward, so a role granted on the organization can affect billing accounts within that organization. A billing account type defines who the account fits and how payment is collected, and all billing accounts within an organization use a single price sheet.
| Account type | Who it fits | How payment works |
|---|---|---|
| Self-serve account | Individual teams and smaller organizations | Pays automatically with an online payment method, such as a credit card or verified bank account |
| Invoiced billing account | Larger organizations with monthly billing | Receives a monthly invoice and pays by invoice |
| Cloud Billing subaccount | Resellers managing charges for customers | Behaves like a billing account with its own linked projects, exports, and IAM roles, but all charges are paid by the reseller's parent billing account and grouped on the invoice |
A subaccount allows access control to be fully separated per customer while keeping payment centralized with the parent account. One central Cloud Billing account is recommended because extra accounts add tracking overhead and reports show one billing account at a time. Multiple accounts are needed only for legal or accounting separation, for paying in multiple currencies, or for allocating support costs differently.
Linking a project to a billing account connects two separate resources, so IAM checks permissions on both sides of the link. A Google Cloud project is the container that holds resources such as virtual machines and storage buckets, while a Cloud Billing account defines who pays for usage in one or more projects. A user who has permission on only one side will see the Change billing or Disable billing option as unavailable in the Google Cloud console, and the user may need to reauthenticate before the change is allowed.
Establishing or changing the link requires create permissions on both resources at the same time. On the billing account, the permission is billing.resourceAssociations.create, held by Billing Account User and Billing Account Administrator. On the project, the permission is resourcemanager.projects.createBillingAssignment, held by Project Billing Manager and Project Owner. In practice, one person needs a billing role plus a project role together, most commonly Billing Account User plus Project Owner or Project Billing Manager.
| Task | Billing account side | Project side |
|---|---|---|
| Link or change billing for a project | Billing Account User or Billing Account Administrator with billing.resourceAssociations.create | Project Billing Manager or Project Owner with resourcemanager.projects.createBillingAssignment |
| Unlock link or unlink to disable billing | Billing Account Administrator with billing.resourceAssociations.delete | Project Billing Manager or Project Owner with resourcemanager.projects.deleteBillingAssignment |
| View associations | Billing Account Viewer, Costs Manager, or Administrator with billing.resourceAssociations.list | Project Browser, Viewer, Editor, or Owner with resourcemanager.projects.get |
The relationship between billing accounts and projects is one-to-many because one billing account can pay for many projects. Each project is linked to at most one Cloud Billing account at a time, but that link can be changed to move the project to a different account. Payment linkage is flexible across organizations, so a billing account can pay for projects that belong to a different organization than the organization that owns the billing account.
Billing is enabled on a project only when two conditions are true at the same time. First, the project must be linked to a Cloud Billing account. Second, that linked account must be active and in good standing, meaning it is not closed or suspended. The console shows Billing is disabled for a project with no linked billing account, and resources in a project linked to a closed or suspended account cannot be used, even for services that are otherwise free. Unlinking a billing account disables billing and stops the project from using its enabled products and services.
Procedures for linking and modifying billing control which Cloud Billing account pays for a project and whether paid services can be used. Billing status can be checked on the My Projects page in Billing, which shows each project with its billing account name and ID, or for a single project with gcloud beta billing projects describe PROJECT_ID. Billing is enabled when the output contains a billingAccountName and billingEnabled: true, and billing is not enabled when the name is blank or billingEnabled: false. How a new project gets linked depends on where the project is created, because different consoles handle billing differently. The Google Cloud console prompts for a billing account or links the only available account automatically. The Firebase console starts the project unlinked on the no-cost Spark plan, and the Google AI Studio console starts the project unlinked on the Free tier for eligible models.
Changing the linked account moves usage to a destination account without expected downtime:
A padlock icon means the link is locked and must be unlocked before it can be changed, and a locked link uses the same create permissions as linking. Disabling billing unlinks the project by selecting Disable billing from the same Actions menu and confirming, but a locked link must be unlocked first. After disabling billing, prior usage is still billed to the previously linked account, so a move on May 15 bills May 1 to May 15 to the old account and later usage to the new account.
A Cloud Billing budget is attached to a Cloud Billing account and filtered to include only selected projects, services, and other resource attributes. Costs flow from resources in linked projects to the Cloud Billing account, and the budget monitors the portion of that flow selected by its filters. Narrow scope gives granular tracking for one team or workload, while broad scope gives an organization-wide view. A realistic budget covers infrastructure costs, software licenses, and anticipated growth for each project, workload, and deployment environment.
Filtering lets one budget track a single project, one service such as Compute Engine or BigQuery, or a combination that matches a workload or environment. Labels provide resource-level filtering because a label is a key-value pair attached to a resource, and costs from labeled resources can be grouped by label key and value for a service, environment, or cost center. Exporting billing data to BigQuery supports custom, team-specific reports with fine-grained access control. Granular control can be extended with quotas and limits, which work alongside budgets as project-level quotas for overall boundaries, service-specific quotas for instances or capacity, and resource type-specific quotas for VMs, buckets, Cloud Run instances, or GKE nodes.
A spend cap budget is different from an alerts-only budget because it enforces a cap instead of only sending notifications. The spend cap budget applies to a single Google Cloud project and a single eligible service, its time range is automatically set to Monthly and cannot be edited, and savings settings also cannot be edited. When the cap is reached for Cloud Run, for example, services fail to serve traffic, new job executions fail to start, and worker pools stop processing tasks until the cap is lifted. An existing alerts-only budget cannot be converted, so it must be deleted and replaced with a new spend cap budget.
Alert thresholds decide when a budget sends a notification based on a percentage of the planned spend amount. A budget first sets a planned spend amount, and then one or more threshold rules define a percentage of that amount. When actual spend or forecasted spend crosses a threshold percentage, the budget triggers an alert to the configured recipients. For example, a 50% rule on a $1,000 budget fires at $500 and a 100% rule fires at $1,000.
| Spend basis | What it measures | Key limitation |
|---|---|---|
| Actual spend | Costs already incurred in the current budget period | Subject to billing reporting delay |
| Forecasted spend | Projected total cost by end of the calendar period | Cannot be used with a custom time range |
Because of reporting delay, actual costs appear in Cloud Billing after resources are used, so it is recommended to set the budget amount below available funds. Default threshold rules notify at three percentages of the budget amount: 50% as an early warning, 90% as spend approaches the limit, and 100% as spend reaches the planned total. An alerts-only budget only informs about spending trends and never automatically caps usage or stops spending when a threshold is met.
Budget alerts are delivered by email for manual review or by Pub/Sub (opens in a new tab) for programmatic automation. Email notifications support manual oversight by sending a message to people when a spend threshold is met. Pub/Sub notifications support automated responses by sending budget status to code and integrations that can act on it. Role-based email alerts send notifications based on IAM roles and require at least one threshold rule. Email alerts to billing admins and users is the default option and sends to everyone with billing admin or billing user roles on the target account. Email alerts to project owners is available only when the budget is scoped to a single project and sends to every Project Owner on that project.
Custom email recipients use Cloud Monitoring notification channels for people who do not hold billing roles, such as project managers or developers. Only Email type channels are supported, and up to five email channels can be linked to one budget. The channel must be created in Cloud Monitoring first, then linked to the budget by creating the channel, opening the budget, enabling linking under Manage notifications, selecting the project that contains the channels, choosing up to five channels, and saving the budget. Automated responses use a Pub/Sub topic connected to the budget, with data flowing from the budget to the topic multiple times per day with current status. A subscriber can forward the message to Slack or run a cost-control task such as disabling billing on a project that exceeds its budget.
Cloud Billing export to BigQuery automatically transfers billing data throughout the day from a Cloud Billing account to a BigQuery dataset that you specify. The exported data can then be queried in BigQuery for detailed analysis or exported to a JSON file. The three exports differ in granularity, so the level of detail in the cost question is the decision rule for which export to enable.
| Export type | Granularity and contents | Choose when |
|---|---|---|
| Standard usage cost | Aggregated usage and cost estimates for invoices, cost types, and projects | You need invoice totals, trends, or project-level costs and credits |
| Detailed usage cost | All standard fields plus resource-level fields, labels, and tags | You need to attribute cost to a specific resource, label, or GKE cluster |
| Pricing data | SKU list prices with service description and product and geo taxonomy | You need unit prices or want to join prices with usage costs for optimization |
Destination configuration defines who can turn on billing export and where the exported data can live. Data flows from the Cloud Billing account to tables inside a BigQuery dataset you specify, where it can be queried for analysis or exported to a JSON file. The export depends on both sides being ready: an identity with administrative access to the billing account and destination, and a prepared destination project and dataset to house the financial data. IAM ownership is required on both the source and the destination, shown as the IAM Owner role on the project holding the data and on the linked Cloud Billing account.
Preparing the destination creates the secure container that will receive billing data before export is enabled. The destination dataset lives inside a Google Cloud project you choose, often a FinOps or billing administration project, and that project must have billing enabled and be linked to the same Cloud Billing account that holds the data to be exported. BigQuery requires the dataset to exist before Cloud Billing can write to it. The destination dataset cannot use customer-managed key encryption and cannot use an unsupported region location, so an existing dataset must be checked against those limits before use.
Turning on export creates a continuous transfer of usage, cost estimates, and pricing data for detailed analysis. The export is configured from the Billing export page in the Google Cloud console for each Cloud Billing account, and the same dataset can hold standard usage cost data, detailed usage cost data, and pricing data. Data flows from the Cloud Billing account to the BigQuery dataset automatically throughout the day, then from BigQuery to analysis, reporting, and visualization tools. Timing is critical because export only sends data forward from the time it is enabled and does not backfill history.
Validating delivery in BigQuery proves that rows from the Cloud Billing account have landed in the destination table and are ready for tools. Validation opens the exported table, runs a query that sums costs, and checks that expected projects, labels, and time ranges appear. Successful results mean the automated transfer is working and the data can feed reports and dashboards. A typical validation query selects labels.value and SUM(cost) grouped by tenant, project, or service, with filters such as labels.key and usage_start_time for a monthly check.
Exam tip: Billing export to BigQuery does not backfill history, so data from before export was enabled never appears in BigQuery.
Continue with this study guide: 1.2 Managing billing configuration
serviceusage.services.enable, and enabling one API automatically enables the APIs it depends on.Identity and Access Management (IAM) controls who can act on resources through allow policies that bind a principal to a role, while Organization Policy controls what configuration is allowed on resources through constraints. A role granted on a project, folder, or organization inherits downward to contained resources, while an enforced organization policy blocks creation or update operations that violate its boolean or list constraints.
Predefined Identity and Access Management (IAM) roles should be used in production because they support least privilege better by matching a specific service or job function. Primitive Owner, Editor, and Viewer roles grant far more access than most tasks need and should not be used in production, while custom roles match a task most closely but must be maintained over time.
Each Google Cloud project links to at most one Cloud Billing account at a time, while one Cloud Billing account can pay for many projects. Billing is enabled only when the project is linked to an active account in good standing, and linking or changing the link requires permission on both sides, most commonly Billing Account User plus Project Owner or Project Billing Manager.
No, Cloud Billing export to BigQuery sends data forward only from the time export is enabled and never backfills history. Data flows automatically throughout the day from the Cloud Billing account to the specified BigQuery dataset, where it can be queried for analysis or exported to a JSON file.
Last updated