I recently sat the AWS Certified Solutions Architect- Associate( S-AAC0 2) exam announced back in February, 2020 using a virtual( remote) proctor. This is my second exam for the year, the first being HashiCorp’s Certified Terraform Associate exam, with Google’s Associate Cloud Engineer come through here next.
In this upright, I talk about three tips-off I used to help understand, organize, study, structure, and pass the exam. I start with the creation of mind maps based on documentation and FAQs. From there, I discuss organizing gloom assets use Terraform( or the Infrastructure as Code tool of your option) and absorbing online educational materials.
Create Mind Maps from Documentation
This is my first year apply spirit delineates as a most important tool for exam prep. A recollection delineate captivates the mental nodes and perimeters that exist during a deep thought exercise. Starting with a topic, studies expand out in a tree-like fashion. Topics closer to the center are broad and general whereas child topics income granularity and specificity. Nothing is set in stone; topics can be re-arranged and migrated across the map without restriction.
Part of a mind map focused on Amazon S3
The S-AAC0 2 quiz lists numerous study tips on the exam preparation page. Reading the FAQs below is one of the study tips.
Reading FAQs is not super fun. I only wanted to read through them formerly while re-organizing the data into something more aligned to the Well-Architected Framework. Thus, I made a new sentiment map for each of these FAQ topics employing important, relevant, or interesting information.
For example, databases play a huge role in the exam. One of my judgment maps is focused on the Relational Database Service( RDS) as shown below 😛 TAGENDDatabases represent a big role in AWS
XMind 2020 is my mind map tool of hand-picked. I would like to share the mind map documents as PDFs, but they are fairly ” cluttered” as I did not think to do this initially. In the future, I will attempt to write clean memory planneds and share as part of the blog post.
Build and Destroy Assets with Terraform
I need to build things to really learn how they labor. Using Terraform to build gloomed sources is the best possible way to learn how a mas scaffold is constructed. Why?
All parameters for an object are visible. I can see the default configuration, how the service interprets the quality, and how errors are handled.Dependencies. I am often improving out an entire region of components or deploying an lotion across numerous spheres. Such forces true clarity into how to build out infrastructure at scale.Resource objective ties-in. Directing with real asset id evaluates and encountering which id costs are needed by other reserves body-builds a strong mental model.Authentication and approval. It runs route beyond usernames and passwords or even personal access tokens. It’s about busines principles, credentials, characters, and ssh keys- and thickening those entry points!
For example, I am now most comfortable with Transit Gateways. I’ve created complex configurations involving Transit Gateways at least 200 days thanks to Terraform. Each layout was improved upon with almost no penalty for failure.
Online Educational Training
I watched a few different AWS Certified Solutions Architect Associate grooming videos. I like understanding someone else’s look on a particular solution or engineering. Being an affiliate position quiz, much of the focus is knowing a little bit about dozens of service and presents. Thus, online training offerings were a bit drab and mainly considered the services offered FAQs with a sprinkling of real-world guidance.
A Cloud Guru’s AWS Certified Solutions Architect Associate S-AAC0 2 course was my favorite of a small sample size. It felt ended, thorough, and I enjoy Ryan Kroonenburg’s vogue. For all sections, I obligated sure to update my brain maps and build resources in AWS, when applicable.
Please accept a crispy high five for reaching this point in the pole!
If there’s anything I missed, please trying to reach me on Twitter. Cheers!
Read more: feedproxy.google.com