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.
Your enterprise data platform processes large daily batch and streaming workloads across Dataproc, Dataflow, and BigQuery. In preparation for a planned fivefold surge in data volume during a seasonal retail event, you need to proactively evaluate and manage resource limits to prevent operational bottlenecks and pipeline failures during cluster and worker scale-ups.
Which monitoring and capacity planning strategy should you implement to identify resource and quota constraints before they cause pipeline failures?
This option disables Spark dynamic allocation to fix executor counts at static levels and relies on Cloud SQL Query Insights to identify long-running database transactions.
The primary workload was hosted on a Cloud SQL database experiencing lock contention and connection pool exhaustion from monolithic transactional queries.
This strategy establishes comprehensive, proactive observability across cluster compute demand and Google Cloud resource quotas by monitoring Hadoop YARN metrics and Cloud Quota allocation metrics in Cloud Monitoring.
Pending resource and Allocated resource metrics exposes when pending container requests cannot be fulfilled by available cluster capacity. Setting an appropriate scaleUpFactor (e.g., higher for Spark dynamic allocation, moderate for MapReduce) ensures that autoscaling adds worker nodes responsively.scaleUpFactor with workload characteristics prevents autoscaler thrashing and ensures smooth scaling during traffic spikes.Monitoring quota utilization alongside orchestrator-level resource demand (such as YARN pending containers) directly addresses the root causes of scale-up failures in distributed data pipelines.
This option attempts to manage capacity by repeatedly altering the vCPU and memory instance sizes of a Cloud SQL database throughout the day.
The goal was vertically resizing a standalone transactional Cloud SQL database with careful adherence to maintenance and downtime maintenance windows.
This option configures monitoring on Apache Cassandra latency percentiles and Kubernetes pod volume utilization metrics commonly used for distributed NoSQL database layers in hybrid API management platforms.
The scenario specifically required diagnosing performance degradation, disk saturation, and write latency spikes within an Apigee hybrid Cassandra datastore cluster.
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