Cloud Digital Leader Scaling with Google Cloud operations 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.

• ✓

  Set up budget alerts to monitor costs

  Why this is correct

  Budget alerts in Google Cloud are configured at the billing account or project level to send notifications when actual or forecasted spend exceeds defined thresholds. This proactive monitoring prevents unexpected charges and enables timely cost governance, ensuring that teams can adjust resource usage before overspending occurs. Alerts are not resource limits but essential visibility tools for financial accountability.

• ✓

  Implement infrastructure as code using Deployment Manager or Terraform

  Why this is correct

  Implementing infrastructure as code (IaC) with Deployment Manager or Terraform involves defining cloud resources in declarative configuration files, which are version-controlled and reviewable. This approach ensures reproducible environment provisioning, eliminates manual configuration errors, and enables GitOps-style automated deployment pipelines. IaC also facilitates consistent environments across development, staging, and production, reducing drift and improving change management.

• ✓

  Enable Cloud Audit Logs for security and compliance

  Why this is correct

  Cloud Audit Logs capture admin activity, data access, and system events, creating an immutable record useful for security investigations and compliance audits. Enabling these logs ensures that unauthorized changes are traceable, policy violations can be detected, and forensic analysis is possible. Audit logs can be exported to Cloud Storage or BigQuery for long-term retention, satisfying regulatory requirements.

• ✗

  Use Cloud Logging to store all logs indefinitely to ensure compliance

  Why it's wrong here

  While Cloud Logging captures operational logs, storing every log indefinitely escalates storage costs and may inadvertently retain data beyond regulatory retention windows, creating compliance risk. Best practice is to define log retention policies aligned with organizational requirements and export logs to lower-cost object storage for archival. Indefinite storage also complicates data lifecycle management and violates the principle of data minimization.

• ✗

  Use a single project for all workloads to simplify management

  Why it's wrong here

  Consolidating all workloads into a single project creates a flat management structure where IAM policies, quotas, and billing are shared, making it difficult to isolate failures or enforce least privilege. Multiple projects provide logical separation between environments or business units, allowing granular access control, independent quotas, and per-project cost tracking. This reduces the blast radius of security incidents and simplifies compliance.

Go deeper

Related to this question