Free Professional Data Engineer Exam Braindumps
Google Cloud Data Engineer Professional Questions 161–165 (page: 34)

Updated On: 10-Feb-2026

You are a head of BI at a large enterprise company with multiple business units that each have different priorities and budgets. You use on-demand pricing for BigQuery with a quota of 2K concurrent on-demand slots per project. Users at your organization sometimes don't get slots to execute their query and you need to correct this. You'd like to avoid introducing new projects to your account.

What should you do?

  1. Convert your batch BQ queries into interactive BQ queries.
  2. Create an additional project to overcome the 2K on-demand per-project quota.
  3. Switch to flat-rate pricing and establish a hierarchical priority model for your projects.
  4. Increase the amount of concurrent slots per project at the Quotas page at the Cloud Console.

Answer(s): C


Reference:

https://cloud.google.com/blog/products/gcp/busting-12-myths-about-bigquery



You have an Apache Kafka Cluster on-prem with topics containing web application logs. You need to replicate the data to Google Cloud for analysis in BigQuery and Cloud Storage. The preferred replication method is mirroring to avoid deployment of Kafka Connect plugins.

What should you do?

  1. Deploy a Kafka cluster on GCE VM Instances. Configure your on-prem cluster to mirror your topics to the cluster running in GCE. Use a Dataproc cluster or Dataflow job to read from Kafka and write to GCS.
  2. Deploy a Kafka cluster on GCE VM Instances with the PubSub Kafka connector configured as a Sink connector. Use a Dataproc cluster or Dataflow job to read from Kafka and write to GCS.
  3. Deploy the PubSub Kafka connector to your on-prem Kafka cluster and configure PubSub as a Source connector. Use a Dataflow job to read fron PubSub and write to GCS.
  4. Deploy the PubSub Kafka connector to your on-prem Kafka cluster and configure PubSub as a Sink connector. Use a Dataflow job to read fron PubSub and write to GCS.

Answer(s): A



You've migrated a Hadoop job from an on-prem cluster to dataproc and GCS. Your Spark job is a complicated analytical workload that consists of many shuffing operations and initial data are parquet files (on average 200-400 MB size each). You see some degradation in performance after the migration to Dataproc, so you'd like to optimize for it. You need to keep in mind that your organization is very cost-sensitive, so you'd like to continue using Dataproc on preemptibles (with 2 non-preemptible workers only) for this workload.

What should you do?

  1. Increase the size of your parquet files to ensure them to be 1 GB minimum.
  2. Switch to TFRecords formats (appr. 200MB per file) instead of parquet files.
  3. Switch from HDDs to SSDs, copy initial data from GCS to HDFS, run the Spark job and copy results back to GCS.
  4. Switch from HDDs to SSDs, override the preemptible VMs configuration to increase the boot disk size.

Answer(s): C

Explanation:

To optimize the performance of a complex Spark job on Dataproc that heavily relies on shuffling operations, and given the cost constraints of using preemptible VMs, switching from HDDs to SSDs and using HDFS as an intermediate storage layer can significantly improve performance. Here's why option C is the best choice:


Performance of SSDs:

SSDs provide much faster read and write speeds compared to HDDs, which is crucial for performance-intensive operations like shuffling in Spark jobs.

Using SSDs can reduce I/O bottlenecks during the shuffle phase of your Spark job, improving overall job performance.

Intermediate Storage with HDFS:

Copying data from Google Cloud Storage (GCS) to HDFS for intermediate storage can reduce latency compared to reading directly from GCS.

HDFS provides better locality and faster data access within the Dataproc cluster, which can significantly improve the efficiency of shuffling and other I/O operations.

Cost Considerations:

Although SSDs are more expensive than HDDs, the performance improvement for shuffle-heavy workloads can justify the cost, especially if the improved performance reduces the overall runtime and thereby the cost of using preemptible VMs.

Using preemptible VMs with SSDs for this workload balances the cost and performance trade-offs effectively.



Your team is responsible for developing and maintaining ETLs in your company. One of your Dataflow jobs is failing because of some errors in the input data, and you need to improve reliability of the pipeline (incl. being able to reprocess all failing data).

What should you do?

  1. Add a filtering step to skip these types of errors in the future, extract erroneous rows from logs.
  2. Add a try... catch block to your DoFn that transforms the data, extract erroneous rows from logs.
  3. Add a try... catch block to your DoFn that transforms the data, write erroneous rows to PubSub directly from the DoFn.
  4. Add a try... catch block to your DoFn that transforms the data, use a sideOutput to create a PCollection that can be stored to PubSub later.

Answer(s): C



You're training a model to predict housing prices based on an available dataset with real estate properties. Your plan is to train a fully connected neural net, and you've discovered that the dataset contains latitude and longtitude of the property. Real estate professionals have told you that the location of the property is highly influential on price, so you'd like to engineer a feature that incorporates this physical dependency.

What should you do?

  1. Provide latitude and longtitude as input vectors to your neural net.
  2. Create a numeric column from a feature cross of latitude and longtitude.
  3. Create a feature cross of latitude and longtitude, bucketize at the minute level and use L1 regularization during optimization.
  4. Create a feature cross of latitude and longtitude, bucketize it at the minute level and use L2 regularization during optimization.

Answer(s): B

Explanation:

Feature Crosses:

Feature crosses combine multiple features into a single feature that captures the interaction between them. For location data, a feature cross of latitude and longitude can capture spatial dependencies that affect housing prices.

This approach allows the neural network to learn complex patterns related to geographic location more effectively than using raw latitude and longitude values.

Numerical Representation:

Converting the feature cross into a numeric column simplifies the input for the neural network and can improve the model's ability to learn from the data.

This method ensures that the model can leverage the combined information from both latitude and longitude in a meaningful way.

Model Training:

Using a numeric column for the feature cross helps in regularizing the model and prevents overfitting, which is crucial for achieving good generalization on unseen data.


Reference:

https://cloud.google.com/bigquery/docs/gis-dataa

To engineer a feature that incorporates the physical dependency of location on housing prices for a neural network, creating a numeric column from a feature cross of latitude and longitude is the most effective approach. Here's why option B is the best choice:



Viewing page 34 of 78
Viewing questions 166 - 170 out of 401 questions


Post your Comments and Discuss Google Professional Data Engineer exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!