Skip to main content

The road to AZ-400 Azure Certified DevOps Engineer

I've decided to switch gears in my training to focus on something that I haven't before, certifications. I currently hold a Microsoft cert, VMWare cert, and Cisco cert, but I never really set out to say "I want this certification in X amount of take for this purpose.

The reason why I haven't is because I've always been more of a "jack of all trades" technology professional. Recently I've been focusing on one portion, Development Operations (DevOps). It's something that I'm very passionate about and I enjoy extensively. So what does this mean for my blog? Well, it means it won't really be changing. A lot of my content is already focused on this.

So, what's the plan? The plan is to first pass the AZ-203. Why? Because there is a pre-requisite for the AZ-400. It's either the AZ-102 (Azure Certified Administrator) which is focused more on the IT side and the AZ-203 (Azure Certified Developer) which is more focused on the development side. The AZ-203 aligns more with my overall career goals and interests (although the AZ-103 looks to have some amazing content).

What study material will I be using? Let's have a look.

The first thing I did was sign up with Pluralsight. I've used Pluralsight in the past and it's a great platform that only gets better as it goes. Pluralsight has a Path for AZ-203.

https://app.pluralsight.com/paths/certificate/developing-solutions-for-microsoft-azure-az-203

The above link is to the AZ-203 path.

The second piece of study material will be Isaac Levin's blog. Issac is a Senior Product Marketing Manager at Microsoft. He holds a ton of certifications (including the AZ-400), so what better way to study?

https://www.isaaclevin.com/post/az-203-study-guide/

Above is Issac's study guide where he goes over each portion and links to Microsoft documents.

As for study material, those are the pieces I will be focusing on. What I will be using to lab;

1. My Azure account
2. VSCode
3. Visual Studio
4. PowerShell
5. AZ CLI
6. Azure Portal

I've heard that there is some C# on the exam, so as I go over the material I'll be diving into that as well. From what I hear, it's primarily focused on PowerShell and AZ CLI though.

After I pass the AZ-203, I will be jumping into the AZ-400. I'll plan to write a blog post similar to this one on the AZ-400. Wish me luck!

Comments

Popular posts from this blog

DevOps tooling in the Microsoft realm

When I really started to dive into automation and practicing DevOps with specific tooling, there were a few key players. At the time Microsoft was not one of them. They were just starting to embrace the open source world, including the art and practice of DevOps. Since then Microsoft has went all in and the tech giant has made some incredible tooling. Recently I switched to a Microsoft-heavy environment and I love it. I went from AWS/Python/Ansible/Jenkins to Azure/PowerShell/ARM/Azure DevOps. My first programming language was PowerShell so being back in the saddle allowed me to do a full circle between all of the different types of tooling in both worlds. Today I want to share some of that tooling with you.

The first thing I want to talk about is ARM. What is ARM? ARM is a configuration management tool that allows you to perform software-defined-infrastructure. Much like Ansible and Terraform, ARM allows you to define what you want your environment to look like at scale. With ARM, yo…

Monitoring your containers in an AKS cluster with Prometheus

Monitoring and alerting is arguably one of the most important thing in Cloud Engineering and DevOps. It's the difference between your clients stack being up and a client being down. Most of us have SLA's to abide by (for good reason). Today we're going to learn how to spin up Prometheus in an AKS cluster to monitor our applications.

Pre-reqs;
1. Intermediate knowledge of Kubernetes
2. An AKS cluster spun up in Azure

Recently AKS supports Prometheus via Helm, so we'll use that for an automated solution to spin this up. This installs kube-prometheus, which is a containerized version of the application. With raw Prometheus, there are a few things that are needed for the operator;

1. Prometheus: Defines a desired deployment.
2. ServiceMonitor: Specifies how groups of services should be monitored
3. Alertmanager: Defines the operator to ensure services and deployments are running by matching the resource

With kube-prometheus, it is all packaged for you. This means configuri…

Run PowerShell code with Ansible on a Windows Host

Ansible is one of the Configuration Manager kings in the game. With it's easy-to-understand syntax and even easier to use modules, Ansible is certainly a go-to when you're picking what Configuration Management you want to use for your organization. Your question may be "but Ansible is typically on Linux and what happens when I'm in a Windows environment?". Luckily I'm here to tell you that Ansible will still work! I was pleasantly surprised with how easy it is to use Ansible on Windows with a little WinRM magic. Let's get started.

Pre-requisites for this post:
1) WinRM set up to connect to your Windows host from Ansible
2) Ansible set up for Windows Remote Management
3) SSH access to the Ansible host
4) Proper firewall rules to allow WinRM (port 5985) access from your Ansible host to your Windows host
5) Hosts file set up in Ansible that has your IP or hostname of your Windows Server.
6) At least one Linux host running Ansible and one Windows Server host …