- Good luck to everyone taking this exam!
- Skimmed through documents mentioned in https://medium.com/@earlg3/google-cloud-architect-exam-study-materials-5ab327b62bc8
- It is a good idea to take the practice exam https://cloud.google.com/certification/practice-exam/cloud-architect. It will give a taste of what the real exam feel like in a lighter fashion. There are right answers given after the exam. I found it is worth the time.
- If you have more time, might be a good idea to watch the Google Cloud Next 2017: https://www.youtube.com/playlist?list=PLIivdWyY5sqI8RuUibiH8sMb1ExIw0lAR
- IMHO Comparing to the AWS certification exams, it feels like harder than the associate exams but easier than the professional level exams. AWS exams have been designed to have more matching answers, it is a matter to choose what matches most.
- Case studies: All the case studies except JencoMart are on my exam. Dress4win got 6 or 7. Please note I have found some question is very generic, not entirely related to the case study.
- Highlights on the exam:
- Know resources that are global vs regional vs zonal
- Storage: https://cloud.google.com/storage-options/. A number of questions on how to pick one given the workload described in the scenario. The decision tree is used by numerous talks in Google Cloud Next 2017.
- Test environment and test strategy in the cloud vs on premise: A number of questions, a bit of common sense, chose the most logical one.
- Deployment:
- deploy and rollback strategy used in AppEngine, GKE as well managed instances group in compute engine.
- Canary, BlueGreen, A/B test.
- Networking: how HTTPS load balancing works, VPN use cases
- Security Scanner: 1 question
- Storage Transfer service vs gsutil, when to use each.
- Migration: such as how to migrate MySQL server from on premise into the cloud
- Containers: use them whenever "cloud native" is needed
- Troubleshooting:
- how to trouble shoot slow service
- how to investigate when something went wrong on an instance https://cloud.google.com/compute/docs/troubleshooting/troubleshooting-instances
- Troubleshoot an app engine issue with python code
- StackDriver: A number of questions. Should what each one can do.
- Logging
- https://cloud.google.com/logging/docs/audit/
- Know what logging agent does.
- Monitoring
- https://cloud.google.com/monitoring/uptime-checks/
- Know what monitoring agent does.
- Tracing
- Debug
- Error Reporting
- Logging
Last active
July 14, 2023 14:12
-
-
Save pydevops/574871320e3a63e66ab6e0c6ac19f368 to your computer and use it in GitHub Desktop.
google cloud architect cert prepare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think that this is a good way to create a scalable and reliable web application. However, I also think that there are other factors to consider when deploying a Django app, such as the choice between on premise vs cloud based solutions. On premise solutions might offer more control and customization, but cloud based solutions might offer more flexibility and cost-effectiveness. If you want to learn more about the pros and cons of on premise vs cloud based solutions, you can read this article: https://www.cleveroad.com/blog/cloud-vs-on-premise/. It gives a detailed comparison of the two options, as well as some recommendations on how to choose the best one for your project.