Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise organization runs hundreds of workloads on Compute Engine virtual machines and Cloud SQL instances across dozens of projects in Google Cloud. The finance and FinOps teams report an unexpected increase in monthly spend and identify two core operational requirements:
Which strategy should the cloud architect recommend to meet these requirements?
Project-level labels are key-value annotations applied to project metadata within Resource Manager. Cloud Billing reports provide high-level cost trends and historical spending charts across projects, services, and SKUs.
Every project mapped strictly to a single discrete cost center with no shared resources, and the organization only needed to monitor macro-level budget trends without performing rightsizing.
This architecture leverages the Recommender API from a centralized project in conjunction with granular resource labeling to achieve cross-project cost visibility, right-sizing, and cost attribution.
--billing-project flag (or x-goog-user-project header) in Google Cloud CLI or REST API requests, administrators can query recommendations and utilization insights across all projects in the entire organization (such as google.compute.instance.MachineTypeRecommender, google.cloudsql.instance.OverprovisionedRecommender, and google.resourcemanager.projectUtilization.Recommender).costcenter=finance or environment=production) directly to individual VMs and storage resources ensures usage metadata is forwarded directly to the Cloud Billing system, allowing finance teams to filter and group costs by label in Cloud Billing reports and BigQuery billing exports.Using a single billing project to query organization-wide recommendations eliminates management sprawl and API configuration overhead. Combining this with standard key-value labels on resources directly enables exact cost tracking across different cost centers in Cloud Billing reports.
Network tags are metadata strings assigned to Compute Engine VM instances primarily used by VPC firewall rules and VPC routes to control network traffic flow.
The goal was to configure VPC firewall rules and route tables dynamically based on instance roles rather than tracking financial cost allocation.
Resource Manager tags provide hierarchical access control and conditional IAM policy evaluation. The Service Limit (quota) Recommender analyzes quota utilization (such as regional CPU limits or API rate quotas) over a 30-day window to prevent quota exhaustion.
google.resourcemanager.serviceLimit.Recommender) detects when projects approach 80% of their service quota limits; it does not analyze individual VM CPU and memory utilization to identify overprovisioned or idle compute resources.userLabels) are the standard mechanism forwarded to Cloud Billing for fine-grained cost reporting and attribution.The organization wanted to enforce security access policies based on organizational hierarchy and ensure that projects did not run out of regional Compute Engine quota during scaling events.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated