Cost Management Strategies in Migration Plan

PCA By islever Editorial Last updated

Creating a migration plan (i.e., documents and architectural diagrams).

Short answer

BE Configure labels and tags for resources and adopt infrastructure as code to ensure cost visibility and governance.

Question

You are creating a migration plan to move your organization’s infrastructure from on-premises to Google Cloud. You want to understand and manage costs effectively after the migration is complete. Which strategies should you include in the migration plan? (Choose two.)
  1. Enable Backup and DR Service.
  2. Configure labels and tags for the resources provisioned in Google Cloud. Correct Answer
  3. Create a Cloud Scheduler job to export billing data to Cloud SQL.
  4. Create service alerts using Cloud Monitoring.
  5. Adopt infrastructure as code (IaC) for the cloud resources. Correct Answer

Key Takeaways

The core concept tested is effective post-migration cost management; the common trap is confusing general operational tools like monitoring or backups with specific FinOps practices that enable cost tracking and prevention of waste.

This question addresses cost management strategies for a Google Cloud migration plan, emphasizing the importance of resource labeling and Infrastructure as Code (IaC) to ensure financial visibility and control.

Common mistake: Many learners incorrectly choose D (Cloud Monitoring alerts), assuming that setting up alerts is sufficient for cost management without realizing that labels are required first to attribute those costs accurately to specific resources or teams.

Expert Analysis

Why the Answer Is Correct

To effectively manage costs after migration, you need both visibility into where money is being spent and control over resource provisioning. Option B, configuring labels and tags, is essential because it allows you to categorize and allocate costs by project, team, or application, which is fundamental for detailed billing reports and cost analysis. Option E, adopting Infrastructure as Code (IaC), ensures consistency and governance, preventing 'resource sprawl' and orphaned resources that lead to unmanaged costs. Together, these two strategies provide the necessary framework for understanding and controlling cloud spend.

Why the Other Options Are Wrong

Option A (Backup and DR Service) focuses on resilience and data protection, not cost management. Option C is incorrect because billing data is typically exported to BigQuery for analysis, not Cloud SQL, and manual scheduling via Cloud Scheduler is less standard than automated exports for cost insights. Option D (Service alerts) is primarily for uptime and performance monitoring; while budget alerts exist, they rely on the underlying cost data structure provided by labels to be meaningful for granular management.

Community Comment Notes

Community consensus strongly supports B and E. Users like 'respawn' and 'CyberPeter' note that labels are obvious for cost tracking and IaC prevents waste. Some users initially considered C or D but were corrected by comments pointing out that C involves BigQuery rather than Cloud SQL and D is more about performance/uptime unless specifically configured as budget alerts, which still depend on the structure provided by labels.

Exam Strategy

When asked about cost management, always look for options related to tagging/labeling (for visibility) and automation/IaC (for control). Avoid selecting generic operational tools like basic monitoring or backup services unless they explicitly mention cost-related features.

Frequently Asked Questions

Why isn't Cloud Monitoring alerting enough for cost management?

Monitoring alerts track performance and uptime. While budget alerts exist, they lack the granular visibility needed to understand which resources drive costs without proper labeling.

Can I export billing data to Cloud SQL instead of BigQuery?

While technically possible with custom pipelines, GCP's native and recommended workflow for detailed billing analysis is exporting to BigQuery, making option C incorrect in this context.

More PCA FAQ →

Discussion 8 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 8

  1. respawn 👍 4
    B is obvious. C sounds right but not relevant here because billing data is exported to bigquery, not Cloud SQL. And using Cloud Scheduler is unnecessary to do that. D is for performance/uptime. not related to costs. A is for resilience only. so answer is B and E. IaC ensure consistency and avoid orphaned resources.
  2. CyberPeter 👍 3
    B. Configure labels and tags for resources provisioned in Google Cloud Labels/tags allow you to track and allocate costs by project, team, environment, or application. Essential for cost visibility and reporting in Billing Reports and Cost Management tools. E. Adopt infrastructure as code (IaC) for cloud resources Using IaC (Terraform, Deployment Manager) allows you to: Track resource creation and changes Enforce standardization to avoid overprovisioning Optimize and predict costs through repeatable deployments
  3. 41168b9 👍 3
    Recommended Cost Management Workflow Tag Everything: Use Terraform (IaC) to ensure every resource has a cost-center label. Set Budgets: Create a budget for the project in the Billing Console. Configure Alerts: Set threshold rules to email the project leads when spending exceeds the forecast. Analyze: Use the BigQuery export to find "waste" (e.g., idle VMs or unattached disks).
  4. jmo09 👍 3
    The answers are B and E because labels provide the cost visibility needed to understand spending patterns and allocate costs appropriately, while IaC provides the control and governance needed to manage costs effectively by preventing waste, enabling cost estimation, and ensuring consistent, cost-optimized configurations across the infrastructure.
  5. glb2 👍 2
    Answer is B and C. Question is only about costs
Show 3 more comments
  1. cachopo 👍 1
    Adopting Infrastructure as Code (IaC), such as Terraform, is a foundational FinOps practice. It prevents manual resource sprawl by providing a strict, version-controlled source of truth for what is deployed. By defining infrastructure in code, you can consistently track resource lifecycles, reliably tear down temporary environments without leaving orphaned disks or IP addresses behind, and integrate cost-estimation tools into your CI/CD pipelines before resources are even provisioned.
  2. cachopo 👍 1
    B and E Configuring labels and tags directly maps cloud resources to specific cost centers, teams, or environments. When you review your invoices or export your billing data, these labels allow you to filter, group, and analyze your spending granularly, making it possible to identify exactly which application or team is driving costs.
  3. hitmax87 👍 1
    B - to track resources. D - GCP budget alerts natively route through Cloud Monitoring channels.

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Multi-Regional vs Regional Cloud Storage for Global Software Downloads

S-grade

Surviving a Zone Outage With SQL Server on GCP

S-grade

Fixing BigQuery connection errors from a Compute Engine VM

S-grade

Moving 75 TB into Cloud Storage with Google-recommended practices

S-grade

Practice All PCA Questions

Access 81 questions with complete answers and detailed explanations.

View Full PCA Practice Test →

← Back to PCA Study Guide