Prepare and test your skills

Prepare and test your skills

Customer transparency and the Carbon Footprint (opens in a new tab) tool give organizations visibility into the gross greenhouse gas emissions from electricity tied to their use of Google Cloud. The tool aggregates the impact of covered Google Cloud services so an organization can measure its cloud footprint, report it to stakeholders, and track progress toward climate goals. Every resource created in the cloud has an associated footprint, and Carbon Footprint brings that data together in one place for action.
What the tool measures is the gross emissions tied to each customer's use of Google Cloud at the project level. The dashboard breaks total emissions down by project, region, and service so teams can quickly find the largest sources. A well-organized hierarchy of folders and projects with consistent tags and labels is essential because attribution depends on that structure:
Because data flows from individual resources up to projects, poor organization makes it hard to assign emissions to the correct business unit.
How emissions are calculated is defined by a transparent, auditable methodology aligned with the Greenhouse Gas (GHG) Protocol. The methodology explains data sources, Scope 3 inclusions, and how emissions from shared infrastructure are allocated to each customer. Results are reported in kilograms of CO2 equivalent using two complementary accounting methods that show both physical impact and Google's clean-energy benefit:
| Accounting method | What it measures | What it reflects |
|---|---|---|
| Location-based | Emissions using the local grid's emissions factor | The physical-grid impact in the region where the workload ran |
| Market-based | Emissions after Google's purchases of carbon-free energy (CFE) | The carbon benefit of running workloads on Google Cloud |
Both views are needed for a complete picture. A region with a high CFE score can show low market-based emissions even when its location-based emissions are higher, so optimization decisions should be validated against both metrics.
Exam tip: Location-based emissions show the local grid impact, while market-based emissions show the impact after Google's CFE purchases — check both before concluding a region is low-carbon.
How teams access and analyze data is controlled by Identity and Access Management (IAM) and supported by export to BigQuery. Access to the dashboard in the Google Cloud console requires the Carbon Footprint Viewer role (roles/billing.carbonViewer) on the billing account, so teams such as FinOps and platform engineering must be granted that role. Data flows from the Carbon Footprint system to the dashboard for visual review and to BigQuery or Sheets for custom analysis. Getting started follows an ordered setup:
Exported data lets organizations build custom dashboards, such as monthly carbon exports in Looker alongside Cloud Billing (opens in a new tab) data. Annotating the data with events like right-sizing or decommissioning a service makes it possible to link a drop in emissions to a specific action.
How transparency supports reporting and climate goals is by turning verifiable metrics into disclosures and operational fixes. The exported, auditable data can be used for environmental, social, and governance (ESG) disclosures and for mandatory and voluntary compliance. Teams can establish a baseline, identify hotspots, apply fixes, and then verify the outcome in the operational feedback loop. This practice also aligns cost optimization with carbon reduction through GreenOps, where carbon and cost are reviewed together to set accountability, track carbon efficiency against spending, and confirm that efficiency work lowers both bills and emissions. Cost alone is only an initial indicator because a high-cost region with high CFE scores may still have low market-based emissions.
Shared responsibility and sustainable architecture describe how Google and the customer work together to lower energy, water use, and carbon emissions. Google Cloud (opens in a new tab) provides energy-efficient infrastructure, while the customer designs workloads that use that infrastructure efficiently. Choices that lower environmental impact also improve performance and cost, which creates sustainable architecture.
How sustainability responsibility is shared is split into sustainability of the cloud and sustainability in the cloud. Google owns sustainability of the cloud, which covers efficient data centers, infrastructure, and core services. The customer owns sustainability in the cloud, which covers how efficiently their own workloads consume compute, storage, and networking:
A layered stack showing that Google owns sustainability of the cloud (efficient data centers, renewable energy and cooling, efficient core services) while the customer owns sustainability in the cloud (right-sizing, serverless scale-to-zero, data lifecycles). Both sides feed a shared-fate partnership that yields lower cost and lower emissions.
| Owner | Area of responsibility | What it includes |
|---|---|---|
| Sustainability of Google Cloud | Renewable energy, climate-conscious cooling, hardware optimization, and efficient data centers | |
| Customer | Sustainability in Google Cloud | Right-sizing resources, using serverless services that scale to zero, and managing data lifecycles |
Google invests in efficient facilities designed for high power usage effectiveness (PUE), a measure of how efficiently a data center uses energy. Beyond this division, Google promotes a shared fate model where Google and the customer act as partners to reduce the footprint of the entire ecosystem.
Exam tip: Google is responsible for sustainability of the cloud, while the customer is responsible for sustainability in the cloud.
Why sustainable design improves business outcomes is that efficient workloads finish work faster, run for less time, and consume fewer kilowatt-hours of energy. This creates a positive feedback loop where higher efficiency leads to lower cost and lower environmental impact. Migrating from on-premises systems to the cloud can reduce energy use and associated emissions by 1.4 to 2 times because cloud data centers operate at large scale with modern cooling and power distribution. Sustainable choices support four business outcomes:
In this model, the application depends on efficient infrastructure, and the infrastructure depends on efficient application design to realize full savings.
Why selecting a low-carbon region reduces emissions is that not all electrical grids produce the same emissions. Selecting a low-carbon region means placing workloads and data in Google Cloud regions that use a higher percentage of carbon-free energy or have lower grid carbon intensity. Customers can compare regions using CFE scores and carbon-intensity data for Google Cloud regions. Region choice is an architectural control the customer owns, and the same workload can have a smaller footprint when it runs where clean energy is more available. For batch work that is not time-critical, customers can schedule jobs in low-carbon regions and keep compute-intensive work in the same region as its data to avoid extra network transfer. Customers can also use the resource locations constraint in Organization Policy Service to block storage buckets and other resources from being created in high-carbon regions, which enforces the choice across the organization.
Carbon-free energy goals and operational efficiency describe how measurement of cloud emissions is turned into lower emissions through efficient operations. The Carbon Footprint (opens in a new tab) dashboard reports estimated emissions for covered Google Cloud services on a selected billing account, and its export and recommendation features turn that measurement into action. Together, these tools support the broader goal of reducing the environmental impact of running workloads in Google Cloud.
The Carbon Footprint dashboard displays estimated greenhouse gas emissions for a selected billing account and is located in the Tools section of the Google Cloud console. Emissions data is computed automatically for the billing account, so no API needs to be enabled, though it can take up to 21 days for the previous month's data to become available. Values appear in metric tons of CO2 equivalent (tCO2e) in the dashboard and in kilograms of CO2 equivalent (kgCO2e) in the data export. Access is controlled by Identity and Access Management (IAM), where a billing account administrator grants one of three roles — Carbon Footprint Viewer (roles/billing.carbonViewer), Billing Administrator (roles/billing.admin), or Billing Viewer (roles/billing.viewer). A user does not need access to billing spending data to view Carbon Footprint data.
Market-based and location-based emissions are the two tabs in the Carbon Footprint dashboard that use different Scope 2 accounting definitions from the Greenhouse Gas Protocol (GHGP). Scope 1 and Scope 3 emissions are identical across both tabs, and only the Scope 2 method differs. Each tab shows an annual footprint for the past 12 complete months and a past-month figure compared with the previous month:
| Tab | Scope 2 method | Extra breakdowns available |
|---|---|---|
| Market-based emissions | Reflects emissions from the energy the organization actually purchases | Emissions by month and by region |
| Location-based emissions | Reflects the average emissions of the grid where the usage occurs | Emissions by month, region, project, and product |
The location-based tab adds two charts the market-based tab does not: carbon emissions by project and carbon emissions by product. Both tabs depend on the same underlying usage, so the difference comes only from how purchased clean energy is counted.
Exam tip: The two dashboard tabs differ only in their Scope 2 method — market-based reflects purchased energy, while location-based reflects the local grid. Scope 1 and Scope 3 values are the same on both tabs.
Reducing emissions through operational efficiency uses Google Cloud Active Assist Unattended Project Recommender together with Carbon Footprint data. Active Assist analyzes usage activity across all projects and recommends reclaiming or shutting down unattended projects. Acting on these recommendations reduces both cost and carbon emissions because idle resources consume energy without delivering value. When a billing account has projects flagged as unattended, a "Recommendations to reduce emissions" card appears next to the annual and monthly summary cards. This card is the dashboard's main operational lever because removing unused capacity directly lowers the emissions the account reports.
Exporting and analyzing carbon data allows deeper study through BigQuery and custom dashboards. The export runs through the BigQuery Data Transfer Service, which creates a monthly partitioned table named carbon_footprint in a chosen dataset. Each month's data is exported on the 15th day of the following month, and a backfill can retrieve historical data back to January 2021. After configuring an export, the organization is charged for the BigQuery resources used to store and query the data. Exporting requires Project Owner or Project Editor on the destination project and Carbon Footprint Viewer or Billing Account Viewer on the billing account, plus an ingress rule for VPC Service Controls when applicable. Once exported, the data can be shared with the BigQuery User role or BigQuery Data Viewer role and fed into Sheets, Looker Studio, or Looker. To reach finer granularity, teams can join Carbon Footprint data with detailed usage cost data (opens in a new tab) to approximate resource-level emissions or with standard usage cost data to approximate emissions by tag or label, though both are approximations because cost and emissions scale together only loosely.
Google's move from carbon offsets to carbon removal is reflected in the Carbon Footprint export schema. Two deprecated fields — carbon_footprint_total_kgCO2e.after_offsets and carbon_offsets_kgCO2e — are now set to NULL because Google shifted away from conventional offsets toward direct carbon removal technologies. The active schema instead reports emissions by scope: carbon_footprint_kgCO2e.scope1, carbon_footprint_kgCO2e.scope2.location_based, carbon_footprint_kgCO2e.scope2.market_based, and carbon_footprint_kgCO2e.scope3. It also provides two totals that combine the scopes in order: carbon_footprint_total_kgCO2e.market_based equals scope 1 plus scope 2 market-based plus scope 3, and carbon_footprint_total_kgCO2e.location_based equals scope 1 plus scope 2 location-based plus scope 3.
Location-based emissions measure the physical-grid impact using the local grid emissions factor where the workload ran, while market-based emissions measure the impact after Google purchases of carbon-free energy (CFE). Both views are needed for a complete picture because a region with a high carbon-free energy score can show low market-based emissions even when its location-based emissions are higher.
Google is responsible for sustainability of the cloud, which covers efficient data centers, infrastructure and core services, while the customer is responsible for sustainability in the cloud, which covers efficient use of compute, storage and networking such as right-sizing resources and managing data lifecycles. Efficient application design combined with efficient infrastructure lowers energy use, cost and carbon emissions.
Access to the dashboard requires the Carbon Footprint Viewer role on the billing account, and data can be exported to BigQuery for custom analysis such as joining carbon data with billing data and building carbon key performance indicators (KPIs). Organizing folders, projects, tags and labels by business unit is essential because emissions are attributed by project, region and service.
Last updated