Use the exam blueprint to understand exam objectives.
- [Instructor] Okay, I said in a previous movie that there's a bunch of information here on this website and some of it is more important than other parts, so I'm going to be your guide and I'm going to take you to, I think, the most important piece of information on this site that you need so that you can properly prepare and have success in the exam, and that is the Exam Guide. So, you can see right here, this button, Download Exam Guide. If I click this, this gives you a PDF, a three-page PDF.
This is the absolute bible in terms of preparation and this, to me, is really where you're going to start after you have your hands-on experience. And you'll notice, interestingly, if you read through this, the very first thing that Amazon tells you on AWS Knowledge is, hands-on experience using compute, networking, storage, and database AWS services. So, there it is, it's a little bit buried, but super important. What that means is no matter what they list on this exam blueprint, what topics, what aspects of the topics, you might still see item that are not listed here because they come up in the real world and the only way you're going to know that is if you actually build some solutions.
So, an example I gave in a previous movie would be either creating or moving, and that would be lift-and-shift, a professional website from some other provider to AWS. I can tell you just from practical experience, I've done this over the years for many different types of providers, even before the cloud was out there, and it's written one way in the book, but when you go out and you do it, you're going to learn aspects that there's no other way. And again, the ultimate goal is what? It's, yes, to be certified, but the ultimate goal is to actually know how to deliver solutions on the AWS Cloud and there's no substitute for real-world experience.
So, it continues on here. Professional experience architecting large-scale distributed systems. This goes to, is this the right exam for you? Even though the architect, really, in many ways is prestigious, frankly, it pays more, often, than developer or DevOps, there is a training cost associated and what I find is that you want to set a bar that you can reach. So, if you have experience architecting solutions, maybe not even on any cloud, on-premise, great, fantastic, but if you're completely new to both the cloud and architecture, you may want to start with a more tactical exam, such as the developer exam or the DevOps exam because you're going to have both tactical, hands-on setting up services and planning in this exam.
That makes it a little bit more difficult. So, you can see that you have concepts like elasticity and scalability, you have concepts of security features, client interface, and as if you didn't hear it already, the last bullet point on this AWS Knowledge is hands-on experience with deployment and management services. Then it goes on, starting to be a little bit intimidating here. General IT Knowledge, where do I get this? Again, I'm like a broken record, from practical experience because these IT knowledge aspects are not specific to the Amazon Cloud.
What is specific is how they deliver these services. Now, if you scroll down, there's more information here. So, they have the beginning of some resources and then you go into more specifics about the exam. So, what are those specifics? The first thing, very important, the table below lists the domains measured by this exam and the extent to which they are represented, so this is very important. And again, this is something I see people who are preparing not pay enough attention to.
You can see that this is an architecture exam and so, domain one, which is Design, designing highly available, cost-efficient, fault-tolerant, scalable systems is 60% of the exam. This is more of a design exam than a tactical, if you will, exam. So, Implementation and Deployment, Security and Troubleshooting are 40%, so it's key that when you're selecting and preparing, you understand not only what the domains are, but how they are weighted.
Very, very important. So much so that I literally think that in your study grid, or wherever you're writing these down, you should pull this gride out from the exam blueprint and you should remind yourself because it's really easy when you're discovering all these or working with all these cool Amazon services to just say, oh, let me click on this, let me try this, let me look at this, da, da, da, da, da, and an hour or two or three later, you've really been doing implementation or you've been doing data security and you haven't been, for example, reading the white papers or looking at the recommendations for design for those services or understanding how they work together.
You need to prioritize your study time to match the exam topic weighting. And if you find yourself going, I just don't want to read all these design patterns and I don't want to see all these drawings, I want to actually use these services by writing code to see how they work or by doing configuration, then, again, you may want to focus on the developer or the DevOps exams first, assuming you haven't already passed them.