Cloud Digital Leader Fundamental Cloud Concepts Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Google Cloud's Sustainability API

  Why it's wrong here

  Google Cloud does not offer a product called 'Sustainability API.' Carbon emission data for GCP usage is surfaced through the Carbon Footprint dashboard in the console, with an optional BigQuery export for programmatic analysis. Invented APIs are not part of GCP's catalog, so this option cannot be used to measure gross carbon emissions.

• ✓

  Carbon Footprint dashboard in the Google Cloud Console

  Why this is correct

  The Carbon Footprint dashboard in the Google Cloud Console is the correct tool. It provides a per-project and per-service breakdown of gross carbon emissions (in metric tons of CO2e) associated with your GCP resource usage. The dashboard uses Google's region-specific carbon intensity data and includes monthly trends, making it the primary interface for customers to measure their gross operational carbon footprint.

• ✗

  Cloud Monitoring

  Why it's wrong here

  Cloud Monitoring is designed for observability of system and application performance, collecting metrics such as CPU utilization, memory usage, latency, and uptime. While it can ingest custom metrics, it has no native integration that calculates or reports carbon emissions from cloud resource consumption. Its alerting and dashboards are unrelated to environmental impact measurement.

• ✗

  Cloud Audit Logs

  Why it's wrong here

  Cloud Audit Logs records administrative actions and API calls made on Google Cloud resources, such as who created a VM or changed an IAM policy. These logs are essential for security, compliance, and operational forensics but do not contain any carbon emission or energy consumption data. Emission accounting relies on resource metadata and carbon intensity factors, which audit logs do not provide.

Go deeper

Related to this question