Pass Microsoft Azure Architect AZ-303 Exam in First Attempt Easily

Introduction

1. What tools & software do you need?

Throughout this course, we'll be using a number of different tools and services. You don't necessarily need all of them. However, if you want to followall the walkthroughs you will do. The main tools we'll be using are in an Asia subscription, so of course you're going to need an Azure subscription to be able to walk through anything in here. We'll talk you through how to sign up and get a free $150 credit, which will last for 30 days. Next, we'll be using Azure DevOps. So understanding the principles of DevOps is part of the three or four exams, and we'll cover this on how to use the Azure Resource Manager templates to create automated pipelines. In order to follow along with these tutorials, you'll need to set up an Azure DevOps organization. But don't worry, it is completely free. Next, we'll be using PowerShell, and specifically the Azure PowerShell module. However, through the course, we'll generally use a built-in PowerShell console within the Azure Portal. So although it's not strictly required, it is advisable to go ahead and install the tools on your laptop. Anyway, we'll also be using the Azure CLI. Azure CLI is an alternative command-line tool to PowerShell. Again, generally speaking, you can either use the CLI or PowerShell, but we will actually show you examples of both during this course. Next, we'll be using Visual Studio code. This is a minimal development tool often used by developers and specifically DevOps engineers due to its simplicity, flexibility, and cross-platform use. It's perfect for working with Arm templates, and that's exactly what we'll be doing in this course. And finally, we'll be using the full-blown Visual Studio IDE. Primarily, this is a developer tool for building Net applications. We do use this tool when looking at implementing certain solutions for apps, but if you're happy simply to follow along, feel free to skip this. However, if you are interested in the coding side, then you will need to download and install it. The next few lectures will work through getting these various tools and services. However, if you've already got all these, please feel free to skip ahead and get started.

2. Sign up to Azure (And get free services)

In order to follow along with this course, one of the things we're going to need is an account with Microsoft Azure. Luckily, Azure lets you sign up for freeand even gives you a certain amount ofcredit to use for the first 30 days. To get signed up, go to Azure.Microsoft.com, and then if need be, just click the sign in button to sign in with your Live account. Once signed in, click the "Free Account" button in the top right-hand corner, start for free, and fill in your details. You will have to enter some credit card details, but that's just so that if you go over your limit, And as you can see, you get credit for the first 30 days to keep going. But if you do start to incur charges, it will build your credit card, so you do need to keep an eye on it. Once we're all done, click the sign-up button. Once that's activated, we can either click the button to go to the Portal or go directly in. The address will be Portal.Azure.com, and once we're in, we're ready to go.

3. Controlling Azure Costs

You. When using Azure, it is important to keep an eye on costs. When you sign up for the free version of Azure for the free trial, you get $150 to start with, and you also get a number of services that are free for the first year. When you click the Start for Free link from the Azure website, before you actually go and click the "Sign up" button, you can see the list of items that are free. So for example, for the first year, you get a small virtual machine or a small Windows machine. You get a number of managed disks, an amount of storage, and file storage. You get a number of SQL databases, a small amount of Cosmo DB, and a small amount of bandwidth. You also get a number of products that are always free. So, for example, if you were to create Azure Functions, you would get a million requests per month. Once you have signed up for Azure and you've got your account, a handy way to keep an eye on what your current costs are is to visit the Cost Management and Billing section here. Clicking this will show you any subscriptions you have, along with your current cost for the month. And if you click into it, you get to see even more detail along with a forecast of what it's expecting to cost you by the end of the current billing period, which is a month at a time. You can also click into each area to see what areas are costing you the most money. And further down here, you can also see in more granular detail each of the services that you are consuming. So when using Azure, it's really important that you keep an eye on your costs. It's a good idea to try and build services using either free services that are free for the first month, free for the first year, or even free ongoing services. And whenever you do build services that are costing a lot of money, then sometimes it's an idea to investigate which part of it is costing the most money by drilling down and maybe looking at alternatives that you could use instead. If you do find a resource that's consuming a lot, the simplest way to stop paying for that money is to simply go into the resource itself and delete it. You.

4. Signup for Azure DevOps

In this course, we're going to be using a product called Azure DevOps. Now, this name is fairly new. It used to be called VSTs (or Visual Studio Team Services). Sometimes it's also referred to Team Foundation Services," although technically that's the on-premise version. So the first thing we need to do is sign up. To get a DevOps account, go to Azure Microsoft.com.From the Products menu, go to DevOps and Azure DevOps. Alternatively, you could go to DevOps.azure.com, and this will take you to the Azure DevOps sign-up page. If you're not already logged in, you'll need to sign in using your Microsoft account, and then simply click Start for free. By default, it will create you an organisational profile, and then you're ready to start creating projects.

5. Get the Development Tools

You. Throughout this course, we're going to be using a number of tools provided by Microsoft. Most of these tools can be accessed by going to VisualStudioMicrosoft.com.The first tool you're going to use is the Visual Studio IDE. The Visual Studio IDE is the development platform for building and writing code. Visual Studio comes in a number of different versions, from Community to Enterprise. The Community Edition is completely free and gives you everything that you will need to get started. Visual Studio also runs now on two platforms, both on Windows and on OS X for the Apple Mac. This course is done using the Windows version, and this is important because it does have more functionality. Therefore, if you are using a Mac, my recommendation would be to build a Windows virtual machine using some virtualization software such as VirtualBox or Parallels, and install it. Within that. We also have a new version of Visual Studio called Visual Studio Code. This is a much more streamlined and much more cut-down version of Visual Studio. We'll use this in some of the later lectures, and this will run on Windows or OSX.

6. Azure Powershell

Throughout this course, we'll occasionally need to use Azure PowerShell. We'll actually be using PowerShell within the Azure Portal itself, but it's often useful to have the actual PowerShell installed on your own laptop. Now PowerShell comes installed by default on Windows laptops, and you just need to install the Juice PowerShell module. Doing this is quite straightforward. Go to your Start menu and run PowerShell. We run the command install module nameazallow clobber, and you also need this hyphenated scope current user. If you don't do that, you'll sometimes get errors when trying to install it. So we type that command and press Enter when prompted. If that's okay, hit yes. And again, if you're prompted about the installation policy, again, click yes. Okay. Once that's installed, the first thing we need to do is actually log into our Azure subscription, and we do that by running Connect HIF. You'll then be prompted to log in using the username that you've connected to your Azure subscription. And if you've authenticated correctly, it will show you your default subscription. We can test it out by running a simple command such Get Resource Group," which will then show us all the resource groups that we've got in that subscription. We can do the same on an Apple Mac or even Linux. The only difference is that we first need to install PowerShell. To install PowerShell, we first need to download the binaries. We can get these from GitHub.com PowerShell. Powershellreleases. The main page shows the releases and prereleases. I wouldn't advise buying the prereleases. So just scroll down the page until you find the latest release, and then scroll down a little bit further until we find the one that we want, which for a Mac is OS X 64. If you are doing this on Linux, then obviously choose the correct Linux version that you are running, and simply download the binary and then install it. Once installed, you'll then get a "PowerShell" icon in your applications. So simply run that, and then we can start running PowerShell commands. As with the Windows installation, the first thing we need to do is install the module with the exact same syntax as we used before. So install module name AZ and allow clobbering again. Once that's installed, we can issue a login account that's slightly different on the web and on a Mac. What we need to do is copy that or open that URL and then copy in this code, and then that will lock you in.

7. Azure CLI

you in this lecture. We're going to install the Azure CLI again. We're going to install it on Windows and on an Apple Mac. So for Windows, we want to install the installation installer. The easiest way to go there is to do this in a browser. Go to https aka m s install Azure c l Windows. This will then prompt me to save the installer. Once that's downloaded, run it, and then just step through the standard install process. Once that's installed, we can use CLIin a number of different ways. The first is we can use it from the command prompt, and basically we just type AZ. And the way we can test to make sure it's installed okay is by running the command AZ hyphen version, and that will tell us that it's been installed correctly. Alternatively, we can also run it through PowerShell. And again, that just shows us that it's installed okay. And just like we did with PowerShell, we can do an Azure PowerShell command and just test to make sure. We can log into our account by issuing the command AZ login. And again, as before, it will prompt you with a website to log into your account. Installing the Azure CLI on an Apple Mac is slightly different. We're going to use something called Homebrew to install it. So if you don't have it already, the first thing you need to do is install Homebrew. Go to BrewSh, and on the home page, at the very top, is a command for you to run. So simply copy that into a Terminal window and run it. Once Brew has finished installing, we can then use theBrew command to actually install the Azure CLI type. Install Azure again, as before. Once that's finished, if we want to check that it's installed okay, we can use the AZ High Version command to ensure that it's installed and showing the latest version. And again, we can issue logins to Go ahead and login.

Hide

Implement Azure Infrastructure

1. Networking Introduction

You. In the next few lectures, we're going to start looking at Azure Virtual Networks. Azure Virtual Networks are a representation of your own network within the cloud. It's a logical isolation of the Azure Cloud dedicated to your subscription. You can use VNETs to provision and manage virtual private networks or VPNs in Azure and optionally link those VNETs with other VNETs in Azure or even your own on-premises IT infrastructure to create a hybrid or cross-premises solution. Each virtual network can contain one or more subnets, and each of those subnets can contain one or more resources. In a traditional IAS or infrastructure world, they might be file servers. When you're creating VNETs and creating cyber blocks within those VNETs, they can then be used to link to other VNETs on the on-premises networks. And so because of that, you need to make sure that those side blocks or Internet address spaces do not overlap. You also have control over DNS service settings for Venet and the segmentation of them. Via the use of subnets, we can use the virtual networks to create a dedicated private-only VNet. So for example, sometimes you don't require cross-print configuration for your solution. So, when you create a VNet in this case, the services and VMs within that VNet can communicate directly and securely with one another and with other Cloud services. You can still configure endpoint connections for the VMs and other services in them that require an Internet connection. as part of your solution. You can also securely extend your existing on-premise data centre with VNet. So you can build additional site VPNs, or you could create point-to-site VPNs that can be installed on the individual PCs. By doing this, we can create hybrid cloud scenarios. So that means we can connect our on-premises infrastructure seamlessly to the cloud, again via the use of a VPN or an express route. Virtual networks, or VNETs, can get subdivided into subnets. Subnets provide logical divisions within the network. Subnets can help improve security, increase performance, and make it easier to manage the network. So each subnet contains a range of IP addresses that fall within the virtual network address space. And each subnet must have a unique address range specified as a side-format CIDR. The address range cannot overlap with other subnets in the Virtual Network within the same subscription. So for example, in this case, we could create a VNet with an address space of 10 with this side notation of forward slash 16, and then each of the subnets must fall within that range but be separated by the number of addresses within the range. So again, in this example, subnet one has a 17 and subnet two also has a 17. However, it starts at 1128, whereas Subnet won't start at 10. A forward slash number represents the number of IPS that are available within that subnet. If we start at the very top, 32 would only give you one IP address. Ford 31 gives you two, then 4816, 32, and so on. So as you can see, as the forward slash notation decreases by a digit, the number of IPS available within that range doubles up. So if we look again at what that means within our virtual network, it means that with a ten and a 10 forwardslash 16, that would actually give us 65,536 addresses. So, within that address range, we divide it into two distinct subnets, in this case, in half. So on the first subnet, we have 32 768 IPS, which take us from ten one up to ten 1127, which means our second subnet has to start at ten 1128. There are a few caveats you need to be aware of. The first is that there are five reserved IP addresses per subnet. The first address, whatever zero is, is the network address. Next, Jew reserves one to be the default gateway, and then we reserve two and three to map to Azure DNS IPS and to the VNet space. Finally, Azure reserves network addresses two and five for broadcast. So that means, in an example where we have this 2006 J IPS, the actual addressable number of IPS is that number minus five. So $52,763. The next thing to be aware of is that the minimum subnet size is 29. So if we look at 29, that would give us eight IPS, of which five are reserved. Therefore, we actually only have three available IPS, and the largest subnet we can have is eight. It's important to carefully plan your subnets, and as well as what we've already mentioned, there are a few other things that you need to think about. The first are service requirements. Each service directly deployed into a virtual network has specific requirements for routing and the types of traffic that must be allowed into and out of that subnet. For example, a service may require or create its own subnet, so there must be enough unallocated space for it to do so. For example, if you connect a virtual network to an on-premises network using the Azure VPN gateway, the virtual network must have a dedicated subnet for that gateway. Next, virtual appliances. Azure routes network traffic between all subnets in a virtual network. By default, you can override Azure's default routing to prevent Azure from routing between subnets or to force traffic between subnets through a specific Virtual Network Appliance. So if you require that traffic between the resource and the same virtual network flow through a network virtual appliance, deploy the resources to different subnets. Next, a service endpoint. You can limit access to Azure resources such as Azure SQL Storage or SQL databases to specific subnets within a Virtual Network Service endpoint. And then you can deny access to all of the resources of the Internet. In this way, we create dedicated internal links between internal services on a subnet and the Azure Pass services, such as SQL and Storage. Finally, we can create network SKU groups, and we can associate zero or one network SKU with each group per subnet. However, you can assign the same or different networkSkuta group to different subnets, and each networkSkuta group contains rules that allow or deny traffic to and from sources and destinations. We'll cover each of those terms in more detail as we go further on in the course, but for now, we'll walk through a couple of examples of how we can actually create a virtual network and subnets. We'll do it once through the portal, and then we'll create another one in code using PowerShell. You.

2. Creating Networks with the Portal Walkthrough

You. Hi there. In this lecture, we're going to walk through creating some virtual networks. The first one we will do via the portal, and then we'll do another one via PowerShell. We'll reuse these Vnets later on when we're creating virtual machines, so we'll use the first one and call it Windows Virtual Machines, and then the other one we'll name Linux Virtual Machines. From the main page in your portal, we want to Create Resource" and create a virtual network. Click the Create button. First, we need to give it a name, so this one will be a Windows Virtual Network, and then we need to set the address space, so let's go for ten, 100:16. As we tap out, that tells us that it's giving us 65,000 addresses It also shows us that the address ranges between 10 zero and 125 5255. We're going to click "Create New" on the Resource Group, and I'm going to call this Windows Vnets, so I will call it Wind Vnets because we can't use a reserved word for that. I'm going to set the location to UK South, and then we're also going to create our first subnet, so I will call this one Subnet Windows One, and we'll set the address range to zero, so that's starting at the beginning of the range we set up here rather than filling in the address. The full six and a half addresses using 16 are what I'm going to go for as we tab out. As you can see, that gives us half the amount of addresses in there. I'm going to leave the DDoS protection as standard, and I'm going to leave these as disabled. We'll come back to service endpoints and firewalls later on, once we have all the information filled in just click Create.Once completed, click Go to Resource, and we can see the details here. As you can see at the moment, there are no connected devices; that's as we would expect. We can see our address space up here, and we can see that it's using the Azure-provided DNS service. If we click on Subnets, we can see the subnet that we created here, and again, we can see various other options that we've got. For example, the DDoS protection is set to basic firewalls. We have none. We have no security set up as of yet, and for the DNS service, it's using the default DNS servers. For now, let's just go ahead and create another subnet. So what we do is we click this add-on, and let's call this one Snap Windows Two. So we'll use the suggested side block namespace for this one, so this one will start at 128 because we're halfway through the arrangement, but we'll do a smaller one here; we'll do a slash 24. Now we get some options to add network security groups and root tables. Again, we'll leave these as known for now; we'll come back and add those later, along with service endpoints and subnet delegations. For now, just go ahead and click okay. And if we click away to some other option and then back to subnets, we can see our additional subnet there. So you can see that it's very easy to create it using the portal. Now let's go ahead and create another subnet. But this time we will do it using a PowerShell shell.

3. Creating Networks with Powershell Walkthrough

So we're not going to create another virtual network this time using PowerShell. Now, the easiest way to use PowerShell is actually through the Azure Portal itself, and we can get to the PowerShell show on the Azure Portal up here, so go ahead and click that. If it's the first time you've used this, it's going to want to set it up for you, and to do that, it's going to want to create some storage, so let's just go ahead and click create storage. Once that's done, we can go ahead and create the actual virtual network. As with the Windows Virtual Network, it needs to go into a new resource group the first thing we're going to does create that resource group type new AZ Resource Group we shall call this RSG Linux Phoenix and tell it to location and then press Enter we can confirm that's been created by typing Get Acre source group and passing in the name or we could even browse through the portal go to resource groups wean see if we hit refresh our resource group has appeared once that's created we can now go ahead and create our virtual network we're also going to store the result of that virtual network in a command line into a variable sorry soot define a variable we type dollar and then the name of the variable so Linux Vet we're going to say that is going to be equal to and our new AZ Virtual Network command we need to give it the name of the resource group we've just created we'll give it a location. We'll name the Vet itself and then finally we tell tithe address space we want to use with address prefix and this time we're going to ten knot 16 again. We can confirm that it was created correctly by using Get Virtual Network name Linux, and there we can see all the details, and as you can see, there are currently no subnets, so the next task is to go and create that subnet again. We're going to create the subnet in a virtual network into a variable first, and you'll see why, so we'll say dollar, then the next subnet equals dollar. Add virtual network subnet configuration; the name will be "Subnet Linux One," and again we set an address prefix that will be "100 00:17," so again we're going to go for half the size, we're going to tell it to use the virtual network, and then pass in the dollar Linux virtual network handle up there again. Just to confirm that's been done, get AZ Configname for Virtual Network Dollar Linux Phoenix, and again, that's just to make sure that we've configured it and, as we would expect, we've got a name. We have our address prefix and everything else is null because we haven't configured anything, so the final task is to associate that subnet to the virtual network, so now we will type dollar Linux subnet, then use the pipe and pass.

Hide