Prepare and test your skills

Prepare and test your skills

Free sample question, answered and explained below. The Professional Data Engineer practice bank has 1,353 more like it. Try 10 free: instant score, no account.
An enterprise runs a mission-critical nightly batch pipeline that processes analytical data and writes updates into a Cloud SQL for PostgreSQL database, followed by downstream machine learning model retraining using specialized GPU-accelerated compute instances.
During recent runs, the pipeline suffered delays and failures caused by:
You need to proactively guarantee deterministic resource availability for the GPU batch workloads and optimize database capacity and resource contention.
Which strategy should you implement?
This strategy relies on Gemini Cloud Assist runtime recommendations, restricts Cloud Monitoring to disk space metrics, and distributes compute across unconstrained multi-region groups.
The primary goal was ad-hoc troubleshooting and exploratory database disk capacity monitoring rather than automated capacity reservation and workload optimization.
Proactive infrastructure architecture relies on native monitoring metrics and reserved hardware rather than dynamic run-time troubleshooting assistants.
This approach relies on Committed Use Discounts (CUDs) for financial savings, configures log-based alerts in Cloud Logging to capture runtime failures, and elevates the PostgreSQL max_connections database flag directly.
max_connections without connection pooling leads to high memory overhead, context switching, and worsened lock contention on the database.The primary goal was purely financial cost optimization across predictable long-term usage, and failure notifications after job termination were acceptable.
To guarantee capacity, CUDs must be paired explicitly with Compute Engine resource reservations.
This option attempts to run batch jobs on Spot VMs, relies on assumed automated quota increases, and introduces Cloud SQL read replicas to absorb pipeline traffic.
SELECT queries; they cannot receive or offload concurrent write transactions, which must still execute on the primary Cloud SQL instance.The batch jobs were fault-tolerant, non-critical background jobs performing read-only analytics where compute cost reduction was the sole objective.
High-demand accelerators like GPUs have constrained availability on spot pools during peak periods, making reservations essential for SLA-driven pipelines.
This solution combines Compute Engine zonal reservations, proactive quota utilization monitoring in Cloud Monitoring, and Managed Connection Pooling in Cloud SQL to ensure deterministic resource capacity and mitigate database contention.
ZONE_RESOURCE_POOL_EXHAUSTED errors during high-demand batch windows.serviceruntime.googleapis.com/quota/allocation/usage) alerts engineers before workloads hit hard project limits, allowing proactive quota adjustment.Compared to reactive autoscaling or unreserved discounting, zonal reservations guarantee actual physical capacity for specialized accelerators, while proactive quota tracking and connection pooling directly resolve the twin bottlenecks of compute limits and database lock contention.
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