My Experience with the Free Google Cloud Security Engineer Professional Certification

My Learning Journey & Exam Experience, Plus Some Useful Advice for Passing the Exam

Pak Cyberbot
4 min readJun 4, 2024

🔴 My Journey to Certification
◾️ My Motivation

🔴 Exam Experience

🔴 Resources for Preparation
◾️ Tips for Passing the Exam

🔴 My Other Articles

Credly Badge

My Journey to Certification

I applied for the “Google Cloud Innovators Get Certified Program”. In the first stage, I attended a 4-hour session and completed the required labs to advance to the second stage. Before this program, I had never worked extensively on Google Cloud due to its expense, except for using the YouTube API during my project YouTube Evidence Collector. However, I had experience setting up infrastructure on my local machine using virtualization technologies and a solid understanding of networking concepts.

The second stage was based on a first-come, first-served basis, so I quickly completed the labs to secure my spot. Maciej Zachariasz(LinkedIn) conducted our 1.5-hour sessions every Thursday for 8 weeks, starting on April 8. His lectures were invaluable. Thanks to him, I was provided with a Google Cloud Skill Boosts 10-week subscription, giving me the opportunity for hands-on experience with Google Cloud. I fully utilized this and put other commitments aside for 2 months to focus on my learning.

Here’s my Google Cloud Skill Boosts profile.

I completed the skill badge requirements to earn the Google Cloud Security Engineer voucher and finished the entire learning path, which you can find here. With some weeks left in my subscription, I plan to complete additional labs.

My Motivation

My primary goal wasn’t just to pass the certification. I aimed to deeply understand Google Cloud to apply it in my cybersecurity field. Additionally, if I’m lucky, I might find bugs in it and earn some bounties — a dream of mine.😂

Exam Experience

I scheduled my exam for Monday, June 4, from 8 AM to 10 AM PKT. The online proctoring system was impressive. It locks down your entire computer using their lockdown browser, scans your room, and requires biometric face identification before starting the exam. You’ll need your national ID, and your webcam and microphone will record your surroundings throughout the exam. Therefore, ensure complete silence in your house to avoid issues.

Here are some useful links:

You need to create accounts on these two platforms:

Resources for Preparation

There are numerous materials available online to help you prepare for the exams:

I highly recommend getting a Google Cloud Skill Boosts subscription for hands-on experience. You can complete the learning path here.

You can also check out my GitHub for my notes: https://github.com/PakCyberbot/GCloud-SecurityEngineer-Notes

Tips for Passing the Exam

  1. Hands-on Experience: Exam MCQs are scenario-based, so hands-on experience is crucial. Understanding each service mentioned in the exam guide will significantly help.
  2. No Passing Marks Mentioned: Google doesn’t specify passing marks or show your score. They simply indicate pass or fail so aim for the full marks.
  3. Practical Skills Over Theory: Don’t rely solely on theoretical knowledge. Practical skills are vital, as they prove your ability to perform tasks if hired.
  4. Focus on Skill Enhancement: Money and certification can be motivators, but the main focus should be on enhancing your skills. The certification is a byproduct of your learning journey.

By following these tips and dedicating yourself to learning, you can successfully pass the Google Cloud Security Engineer Professional Certification and enhance your cybersecurity skills.

You can follow me for more informative material on:

My Other articles

You can check out my other article on the topic: My Experience with the Free eJPTv2 Exam

These 2 articles could motivate you:

Sign up to discover human stories that deepen your understanding of the world.

--

--

Pak Cyberbot
Pak Cyberbot

Written by Pak Cyberbot

(T³) Technical Thinking Tinkerer

No responses yet

Write a response