Prepare and test your skills

Prepare and test your skills

Evaluating Google's infrastructure and energy commitments means using the Carbon Footprint (opens in a new tab) dashboard to see the estimated greenhouse gas emissions from covered Google Cloud services for a selected billing account. The dashboard turns energy use into trackable emissions data so teams can understand where emissions come from and act to reduce them. Every resource created in Google Cloud has an associated footprint, and the dashboard aggregates that impact at the billing account level.
The Carbon Footprint dashboard lives in the Tools section of the Google Cloud console and requires no setup or API to enable. Data is computed automatically, but it can take up to 21 days for the previous month's data to become available. Emissions appear in metric tons of CO2 equivalent (tCO2e) in the dashboard and in kilograms of CO2 equivalent (kgCO2e) in the data export.
Access to the dashboard is controlled by Identity and Access Management (IAM) permissions on the billing account. A billing account administrator grants access through one of three roles: Carbon Footprint Viewer (roles/billing.carbonViewer), Billing Admin (roles/billing.admin), or Billing Viewer (roles/billing.viewer). The required permissions are billing.accounts.getCarbonInformation, billing.accounts.list, and billing.accounts.get, and viewing carbon data does not require access to billing spending data.
Market-based and location-based emissions are the two Scope 2 accounting views in the Carbon Footprint dashboard. Both views follow the definitions from the Greenhouse Gas Protocol (GHGP) (opens in a new tab), which is the international standard for carbon reporting. Scope 1 and Scope 3 emissions are identical across both tabs, and only the Scope 2 calculation differs.
| Tab | Scope 2 method | What it shows |
|---|---|---|
| Market-based emissions | Scope 2 market-based | Emissions broken down by scope 1, scope 2 market-based, and scope 3 |
| Location-based emissions | Scope 2 location-based | Emissions broken down by scope 1, scope 2 location-based, and scope 3 |
The location-based tab provides additional breakdowns that the market-based tab does not, including emissions by project and by product. Together the two tabs show both the physical-grid impact of a workload and the benefit of Google's carbon-free energy purchases.
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.
Summary cards in the Carbon Footprint dashboard give a quick view of emissions trends over time. Each tab shows an annual carbon footprint for the past 12 complete months and a carbon footprint for the past month compared to the previous month. These cards help teams see whether total emissions are rising or falling without digging into detailed charts.
Carbon Footprint integrates with Google Cloud Active Assist Unattended Project Recommender to turn insight into action. The recommender analyzes usage activity across all projects and flags unattended projects for reclaiming or shutdown. When a billing account has unattended projects, a "Recommendations to reduce emissions" card appears next to the summary cards, linking waste reduction to both lower cost and lower carbon.
Charts in the Carbon Footprint dashboard break down total emissions by time, place, and source for further investigation. The monthly view shows long-term direction, while the region, project, and product views show where the largest emissions occurred in the most recent complete month. The project and product breakdowns appear only in the location-based tab.
Exporting Carbon Footprint data to BigQuery enables custom analysis beyond the built-in dashboard. The BigQuery Data Transfer Service (opens in a new tab) creates a monthly partitioned table called carbon_footprint in a chosen dataset, with exports running on the 15th day of the following month. A backfill can retrieve historical data back to January 2021, and BigQuery storage and query resources used for the export are billed.
System architecture showing Carbon Footprint data flowing from billing account to dashboard, via Data Transfer Service to a partitioned BigQuery table, then to Looker Studio, Sheets, Looker and billing joins.
Once data is in BigQuery, teams can build custom views with Looker Studio (opens in a new tab) (formerly Data Studio), Google Sheets with pivot tables and charts, or Looker for existing Looker customers. Teams can also join carbon export data with Cloud Billing (opens in a new tab) export data to estimate emissions at the instance level or tag and label level. These granular estimates are approximations because both cost and emissions scale with usage, but they help prioritize high-usage resources for optimization.
Google Cloud Carbon Footprint (opens in a new tab) is the reporting tool that measures gross greenhouse gas emissions from electricity associated with covered Google Cloud services. The tool provides a dashboard in the Google Cloud console and exportable data for deeper analysis, so organizations can monitor emissions over time and gather evidence for environmental disclosure. Its methodology is transparent, auditable, and aligned with the Greenhouse Gas Protocol.
What Carbon Footprint reports is gross carbon emissions calculated in a way that stakeholders and regulators recognize. Location-based accounting shows the impact of the local electrical grid where the workload ran, while market-based accounting shows the benefit after considering Google's carbon-free energy (CFE) investments. Using both views together prevents a misleading conclusion about a region.
| Accounting method | What it measures | What it tells an organization |
|---|---|---|
| Location-based | Emissions factor of the local grid where the workload ran | The physical-grid impact of running in that region |
| Market-based | Emissions after considering Google's CFE investments | The carbon benefit of Google's clean energy for that workload |
A region can look different depending on grid mix versus clean-energy purchases, so decisions should always validate both metrics. This dual view keeps reporting honest and helps teams choose regions and architectures with full context.
Establishing a trusted baseline means setting up access, organization, and metrics so Carbon Footprint data is complete and correctly attributed. A trusted baseline depends on a well-defined resource hierarchy of folders and projects plus resource annotations with tags and labels, because Carbon Footprint data is aggregated at the project level. Without that structure, emissions cannot be correctly assigned to business units.
roles/billing.carbonViewer) in Identity and Access Management (IAM) for the appropriate billing account so teams like FinOps, SecOps, and platform engineering can view the dashboard.Once this foundation is in place, carbon data flows from Google Cloud usage to the dashboard for quick review and to BigQuery for detailed investigation. That flow keeps engineering decisions and business reporting connected to the same source of truth.
Exam tip: Cost often trends with carbon, but cost is only an initial indicator; a high-cost region with a high CFE score can have high cost but low market-based emissions.
Identifying carbon hotspots means analyzing granular Carbon Footprint data to find the largest drivers of emissions. The dashboard supports breakdowns by project, region, and service to quickly surface the largest gross carbon emitters. BigQuery exports support deeper joins with billing data and annotations that link changes to specific actions.
Together, these techniques move an organization from a total emissions number to a prioritized list of where to act first. The result is a clear link between a reduction action and its measured carbon and cost benefit.
Carbon data for transparency and disclosure provides verified, auditable emissions data for environmental, social, and governance (ESG) reporting. The BigQuery export creates the auditable record that supports both mandatory and voluntary regulations and meets stakeholder demands for openness. Because the methodology follows the GHG Protocol and documents data sources and allocation, the same dataset used for engineering decisions can support formal reporting.
Governance embeds this data into routine operations through GreenOps. A GreenOps function integrates Carbon Footprint data with Cloud Billing (opens in a new tab) data and loads monthly BigQuery carbon exports into existing FinOps dashboards, such as Looker (opens in a new tab). Presenting carbon and cost in a single interface keeps sustainability in the standard operational review cycle, defines accountability for reduction targets across projects, and tracks carbon efficiency against spending.
Active reduction and resource optimization are the customer's share of sustainability in the cloud. Google is responsible for sustainability of Google Cloud, including efficient data centers, renewable energy, and hardware optimization, while the customer is responsible for making workloads energy efficient. Migrating on-premises workloads to the cloud can reduce energy usage and associated emissions by 1.4 to 2 times, but active reduction goes further by continuously removing waste. These actions also lower cost because cloud data centers consume less energy when they run fewer idle or oversized resources.
Selecting low-carbon regions means deploying workloads and data in Google Cloud regions (opens in a new tab) that use a higher percentage of carbon-free energy (CFE) or have lower grid carbon intensity. Regional CFE scores and carbon-intensity data are published for Google Cloud regions, so a team can compare regions before deployment and choose the lowest-carbon option that still meets compliance and performance needs. The choice balances carbon goals against latency, data residency, and service availability.
To enforce the choice, the team can use the resource locations constraint in the Organization Policy Service to limit where new resources and storage buckets can be created and block high-carbon regions. For batch workloads that are not time-critical, carbon-aware scheduling integrates regional CFE data into scheduling logic so jobs run when and where carbon intensity is lowest. In this model, policy flows from the organization to the project, and workloads flow only to allowed low-carbon regions.
Eliminating idle resources means finding and decommissioning projects, virtual machines, and disks that consume energy without doing useful work. Active Assist (opens in a new tab) provides automated recommenders that analyze actual utilization and identify waste, including the unattended project recommender that is integrated with Carbon Footprint data to flag entire unused projects. Idle virtual machine and idle resource recommendations for Compute Engine serve the same purpose at the resource level.
The workflow depends on the recommender for detection and on the customer's IT service management (ITSM) process for action. Review and removal are tracked through engineering tickets to achieve verified reductions in carbon and cost. Unused instances are stopped or deleted instead of running continuously, so energy flows only to resources that perform useful work.
Right-sizing infrastructure means matching provisioned capacity to actual utilization so resources are neither too large nor running longer than needed. Right-sizing recommenders such as machine type recommendations for Compute Engine (opens in a new tab) virtual machines analyze usage and suggest a smaller or more efficient machine type when an instance is consistently underutilized. For compute-intensive and AI workloads, the efficient choice also includes selecting the most efficient machine types and AI models and fixing code-level inefficiencies that cause excessive computation.
When demand varies, automatic scaling and serverless services that scale to zero reduce waste further. Capacity flows from the scaling system to the workload only while demand exists, then scales back when demand falls. This pattern avoids paying for and powering idle capacity between peaks.
Reducing storage energy means keeping only useful data, storing it in the most efficient form and place, and moving it as little as possible. Data governance policies transition infrequently accessed data to a colder storage class or permanently delete it, which lowers the energy cost of disks and replication. Keeping data longer or copying it more widely than needed directly increases energy use.
Replication across regions is limited to mandatory disaster recovery (DR) or high-availability (HA) requirements because cross-region and multi-region copies significantly increase energy use. Energy for transfer is also reduced by deploying compute-intensive workloads such as AI training and BigQuery processing in the same region as the data source, so data flows from storage to compute without crossing regions.
Exam tip: Cost often trends with carbon, but high-cost regions with high CFE scores can have high cost with low market-based emissions, so always validate savings against both location-based and market-based metrics.
The two tabs differ only in how Scope 2 emissions are calculated, while Scope 1 and Scope 3 emissions are identical across both tabs and both views follow Greenhouse Gas Protocol definitions. Location-based accounting shows the physical-grid impact where the workload ran, while market-based accounting shows emissions after considering Google's carbon-free energy investments. The location-based tab also provides breakdowns by project and by product that the market-based tab does not.
The Carbon Footprint dashboard is in the Tools section of the Google Cloud console and requires no setup or API to enable, with previous-month data available after up to 21 days. Emissions appear in metric tons of CO2 equivalent in the dashboard and in kilograms of CO2 equivalent in the data export. Access is controlled by Identity and Access Management permissions on the billing account through the Carbon Footprint Viewer, Billing Admin, or Billing Viewer roles, and viewing carbon data does not require access to billing spending data.
Export uses the BigQuery Data Transfer Service to create a monthly partitioned table called carbon_footprint, with exports running on the 15th day of the following month and backfill available back to January 2021. BigQuery storage and query resources used for the export are billed. Teams can then build custom views with Looker Studio, Google Sheets, or Looker and join carbon export data with Cloud Billing export data to estimate emissions at the instance level or tag and label level, which are approximations because both cost and emissions scale with usage.
An organization is defining sustainability and operational efficiency guidelines for its cloud infrastructure. The IT operations team wants to actively minimize carbon emissions and reduce wasted energy across its compute and database workloads.
Which strategy aligns with Google Cloud recommendations for active carbon reduction and resource optimization?
Last updated