Google Exam Professional Cloud Developer Topic 16 Question 101 Discussion

Actual exam question for Google's Professional Cloud Developer exam

Question #: 101
Topic #: 16

[All Professional Cloud Developer Questions]

Your company is planning to migrate their on-premises Hadoop environment to the cloud. Increasing storage cost and maintenance of data stored in HDFS is a major concern for your company. You also want to make minimal changes to existing data analytics jobs and existing architecture. How should you proceed with the migration?

AMigrate your data stored in Hadoop to BigQuery. Change your jobs to source their information from BigQuery instead of the on-premises Hadoop environment.

BCreate Compute Engine instances with HDD instead of SSD to save costs. Then perform a full migration of your existing environment into the new one in Compute Engine instances.

CCreate a Cloud Dataproc cluster on Google Cloud Platform, and then migrate your Hadoop environment to the new Cloud Dataproc cluster. Move your HDFS data into larger HDD disks to save on storage costs.

DCreate a Cloud Dataproc cluster on Google Cloud Platform, and then migrate your Hadoop code objects to the new cluster. Move your data to Cloud Storage and leverage the Cloud Dataproc connector to run jobs on that data.

Show Suggested Answer

Suggested Answer: D

by Jaime at Jan 26, 2025, 04:24 PM

Limited Time Offer

25%

Off

Get Premium Professional Cloud Developer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Kristofer

2 months ago

Option A looks tempting, but I'm not sure BigQuery is the best fit for our existing Hadoop-based analytics jobs. Rewriting all those jobs seems like a lot of unnecessary work. Option D seems like the perfect balance of cost savings and minimal changes to our architecture.

upvoted 0 times

Rodolfo

6 days ago

Let's proceed with creating a Cloud Dataproc cluster and migrating our Hadoop code objects to the new cluster.

upvoted 0 times

...

Amie

10 days ago

We should definitely consider moving our data to Cloud Storage and leveraging the Cloud Dataproc connector.

upvoted 0 times

...

Rima

17 days ago

Option D does seem like a good balance of cost savings and minimal changes to our architecture.

upvoted 0 times

...

Jacob

18 days ago

I agree, rewriting all those jobs for BigQuery does seem like a lot of unnecessary work.

upvoted 0 times

...

Selene

2 months ago

Haha, Option B is a classic 'let's just throw more hardware at the problem' approach. I doubt our management would be too impressed with that strategy. We need a more strategic, cloud-focused solution like what's described in Option D.

upvoted 0 times

...

Vonda

2 months ago

I'm a bit skeptical about Option C. Migrating HDFS data to larger HDD disks doesn't seem like it will address the core issue of high storage costs. We should look for a solution that truly optimizes our storage costs, like Option D.

upvoted 0 times

Mitzie

1 months ago

Yeah, moving our data to Cloud Storage and using the Cloud Dataproc connector sounds like a more efficient solution.

upvoted 0 times

...

Daryl

2 months ago

I agree, Option D seems like a better choice for optimizing storage costs.

upvoted 0 times

...

Corinne

2 months ago

I prefer option D. Moving our data to Cloud Storage and using the Cloud Dataproc connector for running jobs seems like a more scalable solution for our company's needs.

upvoted 0 times

...

Cassie

2 months ago

Option D seems like the most straightforward approach. It allows us to keep our existing Hadoop code while migrating the data to the more cost-effective Cloud Storage. The Cloud Dataproc connector will make it easy to run our jobs on the new data location.

upvoted 0 times

Tyisha

1 months ago

Yes, it's important to find a solution that minimizes changes to our existing data analytics jobs and architecture.

upvoted 0 times

...

Kaycee

1 months ago

We should definitely consider moving our data to Cloud Storage to save on storage costs.

upvoted 0 times

...

Darrel

2 months ago

I agree, leveraging the Cloud Dataproc connector will definitely make it easier to run our jobs on the new data location.

upvoted 0 times

...

Dallas

2 months ago

Option D seems like the most straightforward approach. It allows us to keep our existing Hadoop code while migrating the data to the more cost-effective Cloud Storage.

upvoted 0 times

...

Solange

2 months ago

I agree with Nathalie. Option C seems like the most efficient way to proceed with the migration while minimizing changes to our existing architecture.

upvoted 0 times

...

Nathalie

2 months ago

I think option C sounds like a good plan. It allows us to migrate our Hadoop environment to Cloud Dataproc and save on storage costs by moving data to larger HDD disks.

upvoted 0 times

...