Professional Data Engineer - BETA exam

2 months ago
27 September 2023
12 replies
331 views

Userlevel 7

+65

ilias
C2C Team Member

On Monday, September 25, I took the PDE - BETA exam.

It was my first BETA exam. And I can reassure you that it's for the brave!

I admire all my friends from my LinkedIn network who are sitting regularly and taking the BETA exams.

The duration is the main difference between a regular Google Cloud Certification exam and the BETA one. A typical exam takes two hours. In contrast, the BETA is a 4-hour exam.

During the exam, you can't:

drink water or coffee, ☕️
go to the toilet 🚾
… and some other things

But the two above bullet points are the most crucial for me. 😉

In case you want to take the PDE exams:

💥 Get to know the PDE, a great and insightful article from @alex.maksymec 💥
This is the page for the Professional Data Engineer Exam.
If you want to start preparing for the PDE (NOT the BETA), you need the Data Engineer Learning Path. 🚁
If you are brave, here is the Exam Guide for the PDE - BETA. 💪🏻

Click here to find which Google Cloud Certification is suitable for you.

Either way, enjoy the journey to becoming a Google Cloud Certified Person! 🏆

12 replies

Userlevel 7

+17

Thank you for your informative post, @ilias !

Userlevel 7

+65

ilias
Author
C2C Team Member
2 months ago
27 September 2023

Let me know if you have any questions but not related to the Exam questions @KateVysh

Userlevel 7

+28

Wow! 4 hours straight! Congratulations, @ilias!

@malamin have you taken the Beta exam? 😉

Userlevel 7

+35

Dear @Dimitris Petrakis ,

I have not yet taken the beta exam, but I plan to do so soon or next time. I have just received my certification, but I am already interested in learning more about the beta exam technique and guidelines.

Congratulations,@ilias! on taking the beta exam! I know it is a challenging four hours that required deep concentration for pass the exam.

Userlevel 7

+65

ilias
Author
C2C Team Member
2 months ago
27 September 2023

LOL

@malamin I don't know if I have passed it. First, the BETA period must close, and then wait for about 6-8 weeks 😉

But for me, it was definitely a great experience!

Userlevel 7

+17

I'd be tired of waiting for results

Userlevel 7

+35

@ilias thanks for the update! I'm glad to hear that you had a great experience taking the beta exam but I'm confident that you did well. You're a hard worker and you're always prepared, so I know you put your best foot forward.

Good luck!

Userlevel 7

+28

@bdelv Hi Brice, have you also attempted the BETA exams?

Userlevel 2

@Dimitris Petrakis I did not have the occasion yet.

There are currently 2 certifications in BETA:

Machine learning engineer
Data engineer

The machine learning engineer is the only certification I didn’t try to pass yet.
And the Data engineer was not in BETA when I passed it in June 2023 (still the previous version)

Userlevel 7

+65

ilias
Author
C2C Team Member
2 months ago
28 September 2023

@bdelv Are you planning to take the BETA ML Google Cloud Certification?

Userlevel 2

@ilias

It was in my plan to pass them all.

I began studying for it a few days the ML one. But at this time (a few months ago), the “ML engineer” courses, to my mind, had quite an issue of calibration and consistency compared to the other courses (data engineer courses were also sometimes a bit weird and quite some labs were broken. Qwiklabs support was probably sick of me submitting issues every day :) ).

ML path was mixing light concepts with suddenly a crazy deep one. It was testing the knowledge in detail of a tool, which was not like the other certs (deep understanding over detailed memory).

It was already by far the longest to study of all certs (well more than the 2nd one: data engineer). I didn’t really understand the target of the course. ML experts shouldn’t need to invest all this time. And beginners would badly need external courses.

So I decided to postpone it, waiting for the course to be refined. I broke my Pokemon move at 10 out of 11 certs.
Now thinking about it, ML and Data engineer are today the two in BETA. So that probably explains it. They were probably in the middle of a rewriting, hence the issues I bumped on.

I’ll probably give it a try again in the near future. It’s probably a smoother experience now.
And I need to catch them all! :)