How Google Cloud Resources Are Managed practice questions

Organization node

Why wrong: The organization node is the root, used for organization-wide policies, not for grouping projects.

Project

Why wrong: A project is a single unit of resources; it does not group other projects.

Resource

Why wrong: Resources are individual services like VMs or buckets, not grouping constructs.

Configure a service perimeter in VPC Service Controls

Why wrong: Service perimeters control data exfiltration, not resource creation.

Use a deny IAM policy at the folder level

Why wrong: Deny policies prevent access, not resource creation.

Set a VPC firewall rule in each project

Why wrong: Firewall rules control traffic but do not prevent resource creation.

The billing export has not been enabled in the Cloud Console

Why wrong: Export is enabled when the dataset is linked; tables should populate after a few hours.

The engineer does not have the Billing Administrator IAM role

Why wrong: Billing Account Administrator is needed to set up export, but the engineer already linked the dataset, so permissions are likely sufficient.

The billing account is not linked to the project containing the BigQuery dataset

Why wrong: Linking is required, but the issue is dataset location.

Committed use discounts

Why wrong: Committed use discounts require a 1 or 3 year commitment for specific resources.

Spot VM discounts

Why wrong: Spot VMs are similar to preemptible but with a shorter maximum lifetime.

Preemptible VM discounts

Why wrong: Preemptible VMs have lower cost but can be terminated at any time, not automatic.

Cost Management dashboard

Why wrong: The dashboard displays costs but does not suggest labels.

Cloud Asset Inventory

Why wrong: Asset Inventory tracks resources and metadata but does not suggest labels.

Organization Policy Service

Why wrong: Organization policies enforce constraints, not recommendations.

Billing export to BigQuery

Why wrong: Billing export provides historical cost data, not pre-deployment estimates.

Active Assist Recommendations

Why wrong: Recommendations help optimize existing resources, not estimate new ones.

Cost Management dashboard

Why wrong: The dashboard shows actual costs, not estimates.

Create a budget alert in Cloud Monitoring with a metric threshold of 80%

Why wrong: Cloud Monitoring is for system metrics, not budget alerts.

Use the Google Cloud Pricing Calculator to set a spending limit

Why wrong: The Pricing Calculator does not create alerts.

Configure a Cloud Scheduler job to check billing data in BigQuery and send a notification

Why wrong: While possible, it is not the standard or recommended approach; budgets and alerts are simpler.

Create a project for each business unit

Why wrong: Projects are children of folders or the organization node.

Create a folder for each business unit

Why wrong: Folders come after the organization node exists.

Enable the Cloud Resource Manager API

Why wrong: The API is enabled by default for projects, but the organization node is created through Workspace/Identity.

The billing account has not been linked to the project

Why wrong: Linking is required but the export would still show an empty table; the dataset location is the common issue.

The IAM permissions for the BigQuery dataset are incorrect

Why wrong: Permissions affect who can query, not whether data is written.

The billing export tables are only updated monthly

Why wrong: Billing export tables are updated daily.

Organization policy constraints

Why wrong: Organization policies enforce restrictions, not metadata.

IAM custom roles

Why wrong: Custom roles define permissions, not metadata.

Tags (network tags)

Why wrong: Network tags are used for firewall rules, not cost allocation.

Shut down idle VMs to free up quota

Why wrong: That would free existing quota but does not increase the limit.

Create a new support ticket with the Billing team

Why wrong: Quota increases are requested via the Cloud Console, not through a support ticket.

Use the gcloud compute quotas update command

Why wrong: There is no gcloud command to update quotas; it must be done via the Console.

Sustained use discounts

Why wrong: Sustained use discounts are automatic but do not require commitment and offer lower discounts.

Preemptible VM instances

Why wrong: Preemptible VMs are cheaper but can be terminated, not suitable for consistent usage.

Reserved instances (like AWS)

Why wrong: GCP uses committed use discounts; 'reserved instances' is not a GCP term.

Create separate billing accounts for each environment

Why wrong: Not necessary for organizing projects; billing accounts can be shared.

Use organization policies at the project level

Why wrong: Organization policies can be applied at any level, but folders are more efficient for grouping.

Use labels to group projects by environment

Why wrong: Labels are for metadata and billing, not for policy inheritance.

Set up budget alerts to monitor spending

Why wrong: Budget alerts help track costs but do not directly optimize them.

Rely solely on sustained use discounts for all instances

Why wrong: Sustained use discounts are automatic but provide less savings than CUDs for always-on workloads.

Create a separate billing account for each project

Why wrong: Not necessary and would complicate management.

Use IAM deny policies at the organization node to block resource creation outside us-central1

Why wrong: Deny policies are for access, not resource creation; organization policy constraints are the correct tool.

Create a folder and apply an organization policy constraint to restrict locations at the folder level

Why wrong: Applying at the organization level is simpler and covers all projects; folder would miss projects at other levels.

Organization node

Why wrong: The organization node is the root of the hierarchy and typically represents the entire company, not per-environment grouping.

Tags

Why wrong: Tags are used for conditional policy enforcement and network firewall rules, not for grouping projects in the hierarchy.

Labels

Why wrong: Labels are metadata key-value pairs attached to resources for cost tracking and filtering, but they do not provide IAM inheritance.

Active Assist recommendations

Why wrong: Active Assist provides cost optimization recommendations for existing resources, not pre-deployment estimates.

Budget alerts

Why wrong: Budget alerts notify when spending exceeds thresholds, but they do not estimate costs upfront.

Cost Management dashboard

Why wrong: The Cost Management dashboard shows actual incurred costs, not pre-deployment estimates.

Set up a budget alert to receive cost reports daily

Why wrong: Budget alerts send notifications, not historical data suitable for analysis.

Use the Cloud Billing API to programmatically fetch cost data

Why wrong: The Billing API provides access to billing data but is limited for complex SQL queries compared to BigQuery.

Download the monthly invoice CSV and import it into Sheets

Why wrong: Invoices provide summary-level data, not granular per-region or per-label breakdowns, and are not suitable for complex queries.

At the project level for each project

Why wrong: Project-level policies are not inherited from higher levels and must be applied manually to each project, which is inefficient.

Using tags on individual resources

Why wrong: Tags are used for conditional policies and network rules, not for global IAM inheritance across projects.

At the folder level for each environment

Why wrong: Setting at folder level would require applying to each folder separately and may not cover all projects if new folders are created.

Preemptible VMs

Why wrong: Preemptible VMs are short-lived and can be terminated at any time, not suitable for stable, predictable workloads.

Sole-tenant nodes

Why wrong: Sole-tenant nodes are used for isolation, not cost savings, and have a higher cost than standard VMs.

Sustained use discounts

Why wrong: Sustained use discounts are automatic for instances that run more than 25% of a month, but they do not require a commitment and offer lower discounts than CUDs.