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 processes terabytes of analytics data daily using batch Apache Beam pipelines on Dataflow. The primary input dataset currently resides in a Cloud Storage multi-region bucket located in the us multi-region, while the pipeline's temporary and staging files (gcpTempLocation) are written to a bucket in us-east1. The Dataflow worker compute instances are provisioned to execute in us-central1.
The cloud operations team reports substantial inter-region network egress charges and increased execution wall time during pipeline shuffle and staging phases. Additionally, the batch workloads are non-time-sensitive.
Which architectural strategy should the data engineering team implement to minimize network egress costs, improve I/O performance, and optimize economic efficiency?
us-central1 across all availability zones.The Archive storage class in Cloud Storage is an ultra-low-cost storage tier engineered specifically for cold data, compliance archiving, and disaster recovery data that is accessed less than once a year.
gcpTempLocation) with worker compute.You needed to store long-term backup datasets or regulatory audit logs that are rarely or never read during daily production analytics.
us-central1 and staging in us-east1, but increase the worker VM thread count and maximum workers to mask network transfer latency.Adjusting thread parameters (numberOfWorkerHarnessThreads) and increasing worker instance scaling limits in Dataflow enables a pipeline to process more element bundles in parallel by leveraging multi-core compute concurrency on each worker VM.
us-central1 and us-east1.gcpTempLocation.The workload were compute-bound (CPU-intensive) rather than I/O-bound, and both compute and storage were already perfectly co-located within the same region.
us-central1, execute Dataflow workers in us-central1, and enable Flexible Resource Scheduling (FlexRS).Data locality refers to the architectural design of placing compute processing resources in the exact same geographic region and zone as the storage services they interact with. Flexible Resource Scheduling (FlexRS) is a Dataflow execution option designed for non-time-sensitive batch workloads that reduces compute costs by utilizing a mix of Spot/preemptible virtual machines (VMs) and standard VMs with delayed scheduling.
gcpTempLocation), and the Dataflow worker VMs within us-central1, all data transfers remain strictly intra-regional. This completely eliminates expensive inter-region cross-network egress charges incurred during stage shuffling and temporary state writes.Co-locating all storage locations (gcpTempLocation and raw data) with the compute region while activating FlexRS provides the highest reduction in cloud billing and network overhead without violating batch execution requirements.
A cross-region internal Application Load Balancer is a networking service designed to distribute client HTTP/HTTPS requests to backend virtual machines or containers across multiple Google Cloud regions to provide high availability, failover, and global reach for interactive serving applications.
You were building a global, highly available interactive web application that required automated multi-region failover and traffic steering for end-user web requests.
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