> For the complete documentation index, see [llms.txt](https://blog.r00t-hunter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://blog.r00t-hunter.com/exam-notes-and-prep-guides.md). # Exam Notes & Prep Guides ### Overview This section documents prep notes for the security certifications I've taken. Each article breaks down what the exam actually tests, which skills are worth building beforehand, the mistakes that commonly cost people time, and how to prepare using legitimate resources - practice labs, official material, and hands-on repetition. These are not walkthroughs and they do not contain exam flags, specific answers, or environment-specific details. Exam content changes per attempt, and sharing that kind of material defeats the purpose of a proctored certification. The value here is in the skill map, not a shortcut. Each guide follows a consistent structure: * **Exam Format & Details** - structure, delivery method, what the deliverable actually is * **What the Exam Is Actually Testing** - the exam broken into individual skill categories, studied independently rather than as one monolithic "exam" * **Core Concepts to Understand** - the underlying theory behind each technique, not just command syntax to memorize * **Common Mistakes That Cost People Time** - the recurring pitfalls that show up regardless of how technically capable someone is * **How to Actually Prepare** - specific, legitimate resources and practice approaches (HTB, TryHackMe, personal lab work, official documentation) * **Is It Worth Doing** - an honest take on the exam's practical value, not marketing copy The goal of this collection is to give people a real study map for exams I've been through, built from what actually mattered on exam day - not a leaked answer set. If a guide here helps someone pass without understanding the underlying attack chain or concept, it hasn't actually helped them. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://blog.r00t-hunter.com/exam-notes-and-prep-guides.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.