Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Developer practice bank has an additional 608 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your team manages a high-traffic web API on Cloud Run in us-east1 that experiences steady baseline traffic. Reviewing Cloud Billing reveals rising expenses across three areas:
us-central1You need to programmatically identify cost-saving opportunities and re-architect the deployment to minimize egress and operational costs without causing service downtime.
Which approach should you take?
us-central1, and increase the minimum instances on the Serverless VPC Access connector.Exporting Cloud Billing data to BigQuery enables detailed SQL-based cost reporting, chargebacks, and custom dashboarding. Proactive quota alerts notify administrators when project resource consumption approaches configured service limits, and Tier 1 regions offer lower per-vCPU and memory pricing on Cloud Run than Tier 2 regions.
us-central1 fails to eliminate inter-region network traffic charges when reading from the Cloud Storage bucket. Bandwidth charges across regions can easily outweigh modest compute rate savings.us-central1, which is also a Tier 1 region) eliminates intra-GCP transfer fees.The primary goal was building custom multi-project chargeback dashboards in Looker Studio and enforcing capacity governance boundaries, rather than programmatically optimizing active service configurations and network egress.
us-central1 with the Cloud Storage bucket, switch to Direct VPC egress, and place Cloud CDN in front of Cloud Run.This approach combines automated Google Cloud cost intelligence (Recommender API and FinOps hub) with serverless networking and caching best practices (co-location, Direct VPC egress, and Cloud CDN). Together, these tools identify billing inefficiencies programmatically while eliminating avoidable data transfer and idle infrastructure expenses.
google.run.service.CostRecommender) analyzes traffic patterns over the past month and recommends switching from request-based billing to instance-based billing when steady traffic makes lower per-second compute rates and zero per-request fees cheaper. FinOps hub aggregates these insights alongside idle and rightsizing recommendations.us-central1 co-locates it with the Cloud Storage bucket. Intra-region data transfer between Google Cloud services is free, removing inter-region bandwidth fees.Rather than applying blunt spending limits or abandoning serverless operations, this strategy systematically targets every root cost driver—compute billing model, cross-region data movement, internet egress, and VPC connector idle costs—while preserving high availability.
Cloud Billing budget spend caps enforce hard spending limits by automatically pausing Cloud Run workloads when a project crosses a configured budget threshold. Multi-region Cloud Storage buckets replicate data across multiple regions for higher availability, while Cloud Armor provides web application firewall (WAF) and Distributed Denial-of-Service (DDoS) protection.
5xx errors until the next billing cycle or manual intervention. This violates the requirement to avoid downtime.The workload was a non-production sandbox environment where hard cost containment outweighs uptime, multi-region disaster recovery was mandatory, and security filtering against malicious traffic was the primary concern.
us-east1, and route outbound traffic through an external Application Load Balancer without caching.Cost Explorer helps visualize resource-level spending and understand how vCPU, GPU, and networking contribute to monthly bills. Compute Engine managed instance groups (MIGs) run autoscaling clusters of virtual machines, and Committed Use Discounts (CUDs) provide discounted compute pricing in exchange for one- or three-year usage commitments.
us-east1 while reading from a Cloud Storage bucket in us-central1 means every read still incurs cross-region network egress fees.The application required custom OS kernel modifications, specialized VM-level licensing, or persistent local state that serverless containers cannot support, and the compute was co-located with its storage.
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