↓ Skip to main content
Experiment, Fail, Learn, Repeat
  1. Posts/

Preparing for Google Cloud Developer Certification

·333 words·2 mins
Google Cloud Google Cloud
Author
Hairizuan Noorazman
Software engineering experiments, implementation notes, and lessons learned.
Table of Contents

Recently, Google has been launching a couple of certification programs that would help people dictate their knowledge and expertise levels with the Google Cloud Platform. At the moment (January 2019), there are 7 certifications including Professional Cloud Architect, Cloud Developer and Professional Data Engineer.

So with all that happening, I decided to try to go for the Cloud Developer and see how being certified is like. I added all the resources that I used and relied on before going for the exam so you can refer and use them to prepare for the exam. I may have over-prepared in my case as I was kind of aiming for the Google Cloud Developer certification in the future.

Tips on preparing for the exam
#

  1. Here are some of the coursera courses that should help prepare for the exam. The coursera courses give a quick overview of the features available in Google Cloud Platform. They use Qwiklabs in order to allow you to quickly test out one or two of the features on the platform and be familiar with using them (without you having a GCP account and paying for trying out the service)
  2. Qwiklab Quests
  3. Being familiar with the Google Cloud Console. Rather than just just sticking to the coursera courses and qwiklabs only, it really helps to use the platform on the daily basis. Use it and try developing apps that use specific features on the platform. It is relatively quite easy to try out features as there is plenty of sample code within the Google Cloud Platform documentation page.
  4. For the Google Cloud Developer certification, the exam literally would test every aspect of the platform. It’s especially vital to appreciate the different choices of data products in Google Cloud Platform such as Cloud Spanner, Cloud Datastore, Cloud SQL etc. E.g. Like when and what situation you would you one of the products over the rest; why would you migrate over to other data products when your requirements grows etc

Related

Cookiecutter template for Google Cloud Run

··429 words·3 mins
Google Cloud Google Cloud
While working on a couple of projects that would be deployed on Google Cloud Run, I realized that a couple of them tend to have some sort of similar structure. Due to the number of repositories I would typically handle on a personal basis as well as the amount of context switch I would need to move between projects; it would ideal that all of such projects are automated as much as possible.

SSH configurations for going into Google Cloud Instances

··386 words·2 mins
Google Cloud Google Cloud
A classic move to reduce the attack surface of Google Cloud Instances is follow the advice below: If service on instance don’t need Public IPs, don’t attach Public IPs to such instances If instance requires Public IPs, ensure that only specific ports that are required are exposed. Clamp down on the rest of the ports and ensure no ingress on them With these basic principles, it would be simple to think how these would eventually lead to an architecture where users access the instances via a bastion host. A bastion host is a instance that would allow user to ssh in from the “outside” world. The more critical instances would linked together in a private network that is unaccessible from the outside (except for load balancers to receive traffic etc).

Introduction to Google Cloud Run

··731 words·4 mins
Google Cloud Serverless R Google Cloud Serverless R
There are various serverless compute solutions on the Google Cloud Platfrom; initially it used to be only Appengine and Google Cloud Function. Google Appengine is a solution that allow you to focus on writing up apps and allow Google to take of deployment/scaling/operations. Google Cloud Functions take a step further and allow you as a developer to develop just plain old functions and allow Google to handle the rest of it, thereby making it easier to split your app functionality to parts that require to scale and parts that don’t need to.

Private Go Modules in Google Cloud Build

··1037 words·5 mins
Google Cloud Golang Google Cloud Golang
So recently, I’ve been needing to automate my builds for my few Golang projects via Google Cloud Build. However, rather than building docker containers, I needed Golang binaries instead, which kind of meant that I would need to have the CI/CD pipeline have a Go environment/runtime to build them. However, when it comes to these CI/CD solutions, including private Golang packages/modules in siad projects is usually quite troublesome. Private Golang packages usually take the code from private Github/Bitbucket/Gitlab repos and getting the go get command to fetch them successful require a bit of hacks here and there to make it work successfully.