Prepare and test your skills

Prepare and test your skills

Google Cloud sustainability goals (opens in a new tab) cover measuring cloud emissions and then lowering them through cleaner regions and more efficient workloads. Measurement turns energy use into trackable emissions data, while reduction removes waste from compute and storage. Together they link lower carbon with lower cost.
The Carbon Footprint dashboard shows estimated greenhouse gas emissions from covered Google Cloud services for a selected billing account. Every resource created in Google Cloud has an associated footprint, and the dashboard aggregates that impact at the billing account level. Data is computed automatically with no setup or API to enable, but previous-month data can take up to 21 days to appear.
Access lives in the Tools section of the Google Cloud console and is controlled by Identity and Access Management (IAM) on the billing account. A billing account administrator grants one of three roles: Carbon Footprint Viewer (roles/billing.carbonViewer), Billing Admin (roles/billing.admin), or Billing Viewer (roles/billing.viewer). Viewing carbon data requires billing.accounts.getCarbonInformation, billing.accounts.list, and billing.accounts.get, but it does not require access to billing spending data.
Summary cards and charts help teams see trends and find large sources. Each tab shows an annual footprint for the past 12 complete months and a past-month figure compared with the previous month. Charts break emissions down by month, by region, and, in the location-based tab only, by project and by product. When unattended projects exist, a “Recommendations to reduce emissions” card links to Active Assist to reclaim or shut them down.
Market-based and location-based views are the two Scope 2 accounting methods in the Carbon Footprint dashboard. Both follow the Greenhouse Gas Protocol (GHGP), and Scope 1 and Scope 3 emissions are identical on both tabs. Only the Scope 2 calculation differs between them.
A comparison matrix contrasting the two Carbon Footprint dashboard tabs: both follow the Greenhouse Gas Protocol with identical Scope 1 and Scope 3 emissions, but differ in the Scope 2 method (Google's carbon-free energy purchases versus the local grid), and only the location-based tab adds project and product breakdowns.
| Tab | Scope 2 method | What it shows |
|---|---|---|
| Market-based emissions | Scope 2 market-based after carbon-free energy purchases | Emissions by scope 1, scope 2 market-based, and scope 3 |
| Location-based emissions | Scope 2 location-based from the local grid | Emissions by scope 1, scope 2 location-based, and scope 3, plus breakdowns by project and by product |
The location-based tab reveals physical-grid impact where the workload ran, while the market-based tab reveals the benefit of Google’s carbon-free energy (CFE) purchases. A region can look clean on one view and higher on the other, so teams should check both before choosing a region. Emissions appear in metric tons of CO2 equivalent (tCO2e) in the dashboard and kilograms of CO2 equivalent (kgCO2e) in the export.
Exam tip: Market-based and location-based tabs differ only in how Scope 2 emissions are calculated; Scope 1 and Scope 3 emissions are identical across both tabs.
Exporting Carbon Footprint data to BigQuery enables custom analysis beyond the built-in dashboard. The BigQuery Data Transfer Service creates a monthly partitioned table named carbon_footprint in a chosen dataset. Exports run on the 15th day of the following month, backfill can reach back to January 2021, and BigQuery storage and query use for the export is billed.
Once data flows from Carbon Footprint to BigQuery, teams can build views in Looker Studio, Google Sheets, or Looker. Teams can also join carbon exports with billing data (opens in a new tab) to estimate emissions at the instance level or by tag and label. Those granular estimates are approximations because cost and emissions scale with usage, but they help prioritize high-usage resources for cleanup.
Lowering emissions with regions and efficiency is the customer’s share of sustainability in the cloud. Google handles sustainability of the cloud through efficient data centers and clean energy, while the customer handles efficiency of workloads. Migrating on-premises workloads (opens in a new tab) to the cloud can cut energy use and associated emissions by 1.4 to 2 times, and further savings come from continuous optimization.
Low-carbon region choice places workloads where CFE percentage is higher or grid carbon intensity is lower. Teams compare published CFE scores and carbon-intensity data, then enforce the choice with the resource locations constraint in Organization Policy Service, which blocks new resources in high-carbon regions. For batch work that is not time-critical, carbon-aware scheduling runs jobs when and where carbon intensity is lowest.
Efficiency actions remove energy waste from compute and storage:
Google Cloud’s commitment to sustainability (opens in a new tab) combines efficient infrastructure, carbon-free energy, and transparent tools that let customers measure and reduce their own footprint. Google improves data centers and clean-energy supply, while customers design workloads that waste less energy. Measurement connects both sides through shared, auditable data.
Customer transparency through the Carbon Footprint tool means visibility into gross greenhouse gas emissions from electricity tied to covered Google Cloud services. The tool aggregates project-level impact so organizations can measure their cloud footprint, report it to stakeholders, and track progress toward climate goals. Good organization matters because data flows from individual resources up to projects.
The dashboard breaks emissions down by three dimensions:
How emissions are calculated (opens in a new tab) follows a transparent methodology aligned with the Greenhouse Gas Protocol, including data sources, Scope 3 inclusions, and allocation of shared infrastructure to each customer. Location-based accounting uses the local grid’s emissions factor to show physical impact, while market-based accounting subtracts the benefit of Google’s CFE purchases. Teams need both views because a high-CFE region can show low market-based emissions even when location-based emissions are higher.
Access and analysis follow an ordered setup. First, an administrator grants the Carbon Footprint Viewer role (roles/billing.carbonViewer) on the billing account to teams like FinOps and platform engineering. Then teams confirm folders, projects, tags, and labels reflect business units and configure automated export to BigQuery. Finally, teams define carbon key performance indicators (KPIs) such as kilograms of CO2 equivalent per customer, transaction, or revenue unit, and join carbon data with billing data to review cost and carbon together.
Shared responsibility for sustainable architecture splits work between Google and the customer at the boundary between platform and workload. Google owns sustainability of the cloud, while the customer owns sustainability in the cloud. Beyond this split, Google promotes a shared fate model where both sides act as partners to reduce the footprint of the whole ecosystem.
| Owner | Area | What it includes |
|---|---|---|
| Sustainability of Google Cloud | Renewable energy, climate-conscious cooling, hardware optimization, and efficient data centers with high power usage effectiveness (PUE) | |
| Customer | Sustainability in the cloud | Right-sizing resources, using serverless services that scale to zero, and managing data lifecycles |
Efficient design improves business outcomes because efficient workloads finish faster, run for less time, and consume fewer kilowatt-hours. Migration from on-premises systems can reduce energy use and emissions by 1.4 to 2 times because large cloud data centers use modern cooling and power distribution. Region choice is a customer-owned control in this model: the same workload can have a smaller market-based footprint when it runs where clean energy is more available, and the resource locations constraint in Organization Policy Service can block storage buckets and other resources in high-carbon regions.
Exam tip: Google is responsible for sustainability of the cloud, while the customer is responsible for sustainability in the cloud.
Carbon-free energy goals and efficient operations turn measurement into lower emissions for a billing account. The Carbon Footprint dashboard lives in the Tools section of the console, computes data automatically, and shows tCO2e in the dashboard and kgCO2e in the export. Previous-month data can take up to 21 days to appear, and access requires Carbon Footprint Viewer, Billing Administrator, or Billing Viewer without needing spending-data access.
The two dashboard tabs differ only in Scope 2 method, with Scope 1 and Scope 3 identical on both. The market-based tab reflects purchased clean energy and shows emissions by month and by region. The location-based tab reflects the average grid where usage occurred and adds emissions by project and by product. Both tabs show an annual footprint for the past 12 complete months and a past-month comparison.
Operational efficiency acts on what the dashboard reveals through Google Cloud Active Assist Unattended Project Recommender. Active Assist analyzes usage across all projects and flags unattended projects for reclaiming or shutdown, and a recommendations card appears next to the summary cards when flagged projects exist. Removing that idle capacity directly lowers reported emissions and costs (opens in a new tab). Exported data supports deeper work through BigQuery Data Transfer Service into the carbon_footprint table on the 15th of the following month, with backfill to January 2021. Google’s shift from offsets to carbon removal is reflected in the schema: old offset fields are now NULL, while active fields report scope 1, scope 2 location-based, scope 2 market-based, scope 3, and two totals that sum scope 1 plus the chosen scope 2 plus scope 3.
Sustainable operations at scale (opens in a new tab) means growing workloads while lowering environmental impact through efficient infrastructure, measurement tools, and data products. Google manages efficiency of the platform, while customers run lean workloads and track emissions. This partnership lets organizations meet environmental commitments without giving up performance or scale.
Enabling sustainable operations at scale starts with carbon-neutral infrastructure and efficient data centers. Migrating on-premises workloads to Google Cloud reduces energy use and associated emissions by 1.4 to 2 times compared with typical on-premises rooms. Google Cloud data centers are custom-designed for high power usage effectiveness (PUE), which measures how efficiently a facility uses energy for computing versus cooling and power distribution.
Responsibility divides at the infrastructure-workload boundary. Google owns sustainability of Google Cloud, including energy efficiency, water stewardship, renewable energy, climate-conscious cooling, and hardware optimization. The customer owns sustainability in the cloud, including right-sizing, serverless services that scale to zero, and data lifecycle management. Customer workloads depend on Google data centers for efficient power and clean energy, while Google depends on customers to avoid idle and oversized resources.
Data and AI products extend sustainability beyond infrastructure by turning planetary and location data into lower-emission decisions:
A real-world example is TELUS, which migrated workloads to carbon-neutral infrastructure and used data analytics to optimize operations, supporting smart-city work that uses real-time data to reduce traffic congestion and emissions.
Optimizing compute and storage means using only the resources a workload truly needs so data centers consume less electricity. An efficient foundation helps because modern cloud data centers use less energy than typical on-premises rooms for the same work. Higher efficiency then lowers both emissions and cost.
Intelligent workload management matches capacity to demand so compute does not run idle. Active Assist machine type recommendations for Compute Engine suggest smaller or more efficient types based on utilization. Aggressive autoscaling expands during peaks and shrinks afterward, while serverless scales to zero between events so no energy is spent waiting. Strong security also helps efficiency by preventing spikes from denial of service (DoS) attacks, breaches, and lengthy cleanup work.
Storage optimization (opens in a new tab) lowers the energy cost of keeping, copying, and moving data. Cloud Storage lifecycle rules transition infrequently accessed data to Nearline, Coldline, or Archive, or delete data that is no longer needed. Compressed columnar formats like Parquet or optimized Avro use far less disk and read more efficiently than row-based JSON or CSV, which lowers compute and input/output energy. Teams also audit persistent disks and delete old snapshots, store data in higher-CFE or lower-intensity regions, limit replication to mandatory DR or HA needs, run compute in the same region as its data, and use Storage Transfer Service or data-sharing APIs instead of mass dumps.
Exam tip: Sustainability of Google Cloud means Google’s data centers and core services, while sustainability in the cloud means the customer’s workloads and resource choices.
Turning measurement into improvement makes Carbon Footprint part of the normal operational loop. Carbon Footprint measures gross greenhouse gas emissions from electricity for covered services, aggregated at the project level. Teams break data down by project, region, and service to prioritize the largest emitters and verify that fixes actually lower emissions.
A four-step clockwise loop from establishing a baseline to identifying hotspots to optimizing workloads to GreenOps governance, all connected to a central BigQuery hub.
The calculation follows the Greenhouse Gas Protocol with documented sources, Scope 3 inclusions, and allocation of shared infrastructure to each customer. Location-based accounting shows local-grid impact where the workload ran, while market-based accounting shows impact after Google’s CFE purchases. Correct attribution depends on folders, projects, tags, and labels because data flows from resources to projects to the billing account.
Continuous measurement and improvement (opens in a new tab) follows an ordered path from baseline to governance:
roles/billing.carbonViewer) to FinOps and platform teams, organize hierarchy and labels, automate export to BigQuery, and define carbon intensity per customer, transaction, or revenue unit.Monthly BigQuery exports feed FinOps dashboards so carbon and cost appear together, and event notes like right-sizing or decommissioning link each drop in emissions to a specific action. Cost often trends with carbon but is only an initial indicator, because a high-cost, high-CFE region can have high cost with low market-based emissions.
Both tabs follow the Greenhouse Gas Protocol (GHGP) and are identical for Scope 1 and Scope 3 emissions, differing only in how Scope 2 emissions are calculated. Market-based emissions show Scope 2 after Google's carbon-free energy (CFE) purchases, while location-based emissions show Scope 2 from the local grid where the workload ran, and only the location-based tab adds breakdowns by project and by product.
Access lives in the Tools section of the Google Cloud console and is controlled by Identity and Access Management (IAM) on the billing account with the Carbon Footprint Viewer (roles/billing.carbonViewer), Billing Admin (roles/billing.admin), or Billing Viewer (roles/billing.viewer) role. Viewing requires billing.accounts.getCarbonInformation, billing.accounts.list, and billing.accounts.get but does not require access to billing spending data, and data is computed automatically with previous-month data taking up to 21 days to appear.
The BigQuery Data Transfer Service creates a monthly partitioned table named carbon_footprint in a chosen dataset, with exports running on the 15th day of the following month and backfill available to January 2021. BigQuery storage and query use for the export is billed, and teams can then build views in Looker Studio, Google Sheets, or Looker or join carbon exports with billing data to estimate emissions at the instance level or by tag and label.
Last updated