Skip to content

Passing AZ-104 as a software developer

Az-104

The AZ-104 Microsoft Certified: Azure Administrator certification is a Role-based Infrastructure certification with no prerequisites and it introduces you in the complex world of managing your personal or your employer's Azure infrastructure. It is a prerequisite to the Expert certification AZ-305 Azure Solutions Architect Expert and it covers 5 major topics:

  • Manage Azure identities and governance (20-25%)
  • Implement and manage storage (15-20%)
  • Deploy and manage Azure compute resources (20-25%)
  • Implement and manage virtual networking (15-20%)
  • Monitor and maintain Azure resources (10-15%)

The exam itself is challenging, you have to answer 52 questions in 100 minutes. The last 4 questions are part of a case study that mimics a real case scenario of what you would have to handle as an Azure administrator.

I've used the following resources to get ready for the exam and they all are worth going through:

Getting ready for this certification was quite a shift from learning about software development in general. Reading about things like managing Azure subscriptions, administer of infrastructure, configuring virtual networking and managing network traffic brought a fresh perspective of how the software we write as developers needs a solid infrastructure in the background that focuses not only on scalability, flexibility, robust security and so on, but also takes into account cost reduction, monitoring, maintenance and visibility.

For me, the biggest challenge was to get hands-on practice of all the topics covered by the exam and it was the main focus of my studies. Having an Azure account and hosting my own app service in it helped me gain valuable insights of how cloud resources should be used. It helped me transition from a costly app service plan to a static web site that reduced costs dramatically, so if there's one piece of advice I would give to anyone trying to get certified is to get hands-on experience in Azure. Go through the screens, get accustomed to the steps of creating resources, remember as much of it as you can.

The second piece of advice that comes to mind is to go through as many practice questions as you can. Understand how they are structured, pay attention to the wording and try to understand the answers. If the answers do not make sense, consult the documentation (the Summary and resources section of each topic in the Microsoft Azure Administrator course contains valuable information that finds itself way in the actual exam questions).

There are this things called "exam dumps" that contain the actual questions from previous versions of the exam. If you want to go through those (you have to pay for them), do so, but make sure you understand the answers and get something valuable out of them and do not transform the experience of certification into a memory test.

I was able to pass the exam today and it was as challenging as I expected. It's important to know the basics of each Azure service and task mentioned in the Study Guide for Exam AZ-104, the basic structure of az cli commands, powershell cmdlets and ARM templates, and also how and when resources can move from one region to another. Communication between resources in Azure, reducing costs and optimal implementation of infrastructure was also emphasized in the test.

If you want to get in touch and hear more about this topic, feel free to contact me on or via .

© 2026 Andrei Bodea

Privacy policy

Privacy Policy

Last Updated: 2026-08-11

Thank you for visiting Compiled Thoughts (the “Blog”). We value your privacy and want to clarify how we handle any information you may provide or that may be collected when you visit this Blog. By accessing or using the Blog, you agree to the terms of this Privacy Policy.

1. Information We Do Not Collect

  • No Analytics or Tracking — We do not run analytics software, tracking pixels, session recording, or any other tool intended to profile visitors or follow them across sites.

  • No Advertisements — Our Blog does not display third-party advertisements and, therefore, does not collect data for advertising or marketing purposes.

  • No Reader Accounts or Subscriptions — Readers cannot create an account or subscribe, so we do not collect or store reader account data. Sign-in exists only for the Blog’s own author, in order to publish content.

  • No Cookies Set By Us — We do not set cookies of our own for any purpose. Please see Section 2 for the third-party services your browser contacts when you visit.

2. Third-Party Services and Automatic Data Collection

The Blog is a static site with no database of readers. However, displaying a page does require your browser to make requests to the services listed below. Those services necessarily receive your IP address, your browser’s user agent, and the address of the page you requested. This happens automatically when you visit, and we ask that you take it into account when reading Section 1.

  • Web Hosting, Netlify — The Blog is hosted by Netlify, which serves every page and may retain standard server logs, including IP addresses, for operational and security purposes.

  • Typefaces, Google Fonts — Every page loads fonts from fonts.googleapis.com and fonts.gstatic.com. As a result, Google receives your IP address and user agent when you visit. We do not use Google Analytics or any other Google advertising or measurement product.

  • Netlify Identity — The home page loads a login widget from identity.netlify.com. It exists solely so the author can sign in to publish, it offers nothing to ordinary readers, and it is not used to identify you. Your browser requests it regardless, and the widget may use your browser’s local storage to hold a sign-in session.

We do not control what these providers log or how long they retain it. Please consult their own privacy policies if that matters to you.

3. Voluntary Information

If you choose to contact us directly (for example, through an email link or contact form, if provided), we may receive personal information such as your name or email address. In such cases:

  • We will use this information solely to respond to your inquiry.

4. No Third-Party Data Sharing

Beyond the automatic requests described in Section 2, we do not share, sell, rent, or otherwise disclose personal information to third parties, because we do not collect or store any personal information about readers. In the event you voluntarily submit personal data (e.g., via direct email), we do not disclose that to any external entity.

5. Children’s Privacy

Our Blog does not target or direct content specifically to children under the age of 13. We do not knowingly collect or maintain personal information from children under 13. If you believe we may have inadvertently received personal information from a child under 13, please contact us immediately so we can delete such information.

6. External Links

Our Blog may contain links to external websites about programming, interviewing, music, books, psychology, or other related content. We are not responsible for the content, privacy policies, or practices of any third-party sites. We encourage you to review the privacy policies of those websites before interacting with them or providing any personal information.

7. Security

Although we do not collect or store personal data on our servers, we still endeavor to use reasonable security measures to protect the Blog’s integrity. However, no data transmission or storage system can be guaranteed to be 100% secure. Your use of the Blog indicates you understand and accept any inherent risks.

8. Changes to This Privacy Policy

We may update or modify this Privacy Policy from time to time to reflect changes in our practices or for other operational, legal, or regulatory reasons. If we make any material changes, we will update the “Last Updated” date at the top of this document. Your continued use of the Blog after any changes signifies your acceptance of the revised Privacy Policy.

9. Contact Us

If you have any questions or concerns about this Privacy Policy, please reach out using the email address in the header of the page.

By using Compiled Thoughts, you acknowledge that you have read, understood, and agree to this Privacy Policy.