Develop Azure Infrastructure as a Service compute solutions

3. AZ-203/204 - Lab - Building Windows Virtual Machines

So here we are in Azure. Now we're going to go ahead and create a virtual machine in the Azure Portal. Now, you can go ahead and add a resource from the All Resources section, or you could go on to the Virtual Machine Blade over here, and you can go ahead and add a virtual machine from here itself. So if you go on to All Resources, if you go ahead and create a new resource, so over here, you'll get the two most popular virtual machines which are available. So you have Windows Server 2016VM and Ubuntu Server 18.04. If you go on to Virtual Machines, if you add a virtual machine from here, also if you go on to the image here, you'll be able to see the various underlying images which are available when you want to go ahead and spin up your virtual machine. So let's go ahead and do that right now. So let's create our virtual machine. Now, remember, the virtual machine needs to be part of a resource group. If you don't have a resource group, you can go ahead and create a new resource group. But I already have a resource group in place,so I'll go ahead and choose that resource group. Next, you go ahead and give the water machine a name.

Next, you must select the underlying region in which you want to host your virtual machine. So I'll choose Central America. Now, there is this option of availability. So, in availability, you can go ahead and add your virtual machine as part of an Availability Zone or an Availability Set. So we will leave that for now. We'll go on to other chapters where we'll look at availability sets and Availability Zones.So next is your underlying OS. So I'm going to choose Windows Server 2016 Data Center. Now, next is the size. Now we can go ahead and change the size of the virtual machine. So over here, I'm going to choose a D, two S, and V. three. So this has two virtual CPUs. It has eight gigs of RAM, and it has the capability to hold four data disks. So over here, you can actually go ahead and choose what should be the size of the virtual machine. Now, obviously, depending upon what size you choose, you also have a cost per month over here. So depending upon that, obviously, if you choose a VM size that has a high number of vCPUs, which has a high number of RAM, you'd be paying more. So let me go ahead and choose the D two S underscore V three.

Click on "select." I'll give you the username and password. So this is the username and password that will be used to log into our virtual machine. Now, please note, over here there are some restrictions when it comes to the password. So, please make sure that you create a password based on these constraints. Next we have the inbound port rules. Do you want to include them as part of the network security group? The network security group is used to control the inbound and outbound traffic on your virtual machine. Now, we'll be covering network security groups in a separate chapter. For now, let's go ahead and ensure that we can at least RDP into our virtual machine. So this will go ahead and add a rule for port 3389. Now I'll go on to Next for the disk. Please note that if you have an existing Windows Serverlicense, you can make use of that and also save on the overall cost of the virtual machine.

Next, you get the option of determining the discs for your underlying virtual machine. So, by default, you get an OS disc type. So the options that you have are premium SSD, standard HD, and standard SSD. So we'll go through this in another chapter. If you go and scroll down now, you also have the option of choosing what should be the underlying data disk. So over here, you can go ahead and add a new data disc onto your virtual machine. For now, I'll leave it as it is. Let me go on to Next for Networking. Now in the networking section, it's going to go ahead and create a new virtual network for you by default. It will also create a new subnet for you and also assign a public IP address.

Now, if you want to go ahead and create your own virtual network, you can do so. So you can go ahead and click on the "Create New" button to go ahead and create a new virtual network. But now I'll leave everything as it is and let me go to the next level for the management. So I'll leave the management as is, except for boot diagnostics. So, if you want to ensure that you receive diagnostic information during the boot process of your virtual machine, you can direct all diagnostic information to a storage account. But just for now, I'll just turn off board diagnostics. Allow me to proceed to Next for advanced, sorry, advanced hazardous.

If you want, you can add tags. I'll leave it as it is. Go on to review and create. Now, in the Review and Create, please make a note of what you're going to be charged per hour for the virtual machine. You can then go ahead and review all of these settings, and once you're okay, you can go ahead and create the virtual machine. Now, let's come back once we have the virtual machine in place. Now, once your deployment is complete, so you can go ahead on the resource, please note that you will also get a notification when the deployment is a success. So let's go on to all resources. So now you can see that in addition to the virtual machine which we have, we also have a number of other resources which have been created. So what are the resources that we have?

So we have the Virtual Network.We have the virtual machine itself. We have a public IP address. It is a separate resource that has been assigned to the Virtual Machine.We have the network security group which is used to control the inbound and outbound traffic on the Virtual Machine.We have the network interface and then, finally, we have the disc which is assigned to the Virtual Machine.You can go on to the Virtual Machine resource. So in the overview, you can go ahead and see all the information about the Virtual Machine.So you can see the subnet and the virtual network in which the virtual machine has been launched. You can also see what the public IP is. What is the private IP address, what resource group does the Virtual Machine belong to, and how big is the virtual machine? Right, so this marks the end of this chapter. For Bearing, we have looked at building a virtual machine on the Azure platform.

4. AZ-203/204 - Lab - Publishing an application from Visual Studio to a VM

Hi and welcome back. Now in this lab, I want to go through the process of being able to publish a web project from Visual Studio on to an Azure Virtual Machine. So over here I have one virtual machine in place. It's a demo VM virtual machine. This is based on Windows Server 2019 Data Center. Now if I go on to Visual Studio, I have a sample application in place. Now let's say that I want to go ahead and publish this particular project. So let me go ahead and click on New. And over here you have the option of publishing on an Azure virtual machine.

So you can go ahead and browse for the Azure virtual machine. And then this will automatically go ahead and publish your project on to the virtual machine. But before you can actually go ahead and do this, there are a number of steps that you have to perform. So the whole purpose of this lab is to understand those steps that need to be performed. So first, let me go on to Azure. So over here we have to first go on toDNS name for the watch machine, hit on Configure. So we have to give a DNS name label that needs to be unique so I can see that it is unique. I also need to ensure that I have a static IP address for the Swatching machine. So let me go and click on Save. Now once this is done, let me go ahead and now connect to the virtual machine. So let me go ahead and remote desktop onto this virtual machine. Now that I've logged into the virtual machine,now on the virtual machine, I've already gone ahead and installed Internet Information Services.

But if you want to go ahead and install Internet Information Services, so I basically want to go ahead and publish an ASP.NET 4.7 version application so that I can ensure that I have Internet Information Services installed on this particular virtual machine. So if you want to go ahead and install Internet Information Services on the server Votes page, ensure that you have a web server installed. So over here in the management tools,it's very important to ensure that the management service installed is basically selected. That's important if you go on to the next framework. So, since I have a 4.7 framework application that needs to be deployed, I have to ensure that ASP.Net 4.7 is installed on this particular web server. So I've ensured that both of these are installed on this particular virtual machine. Next, I need to go ahead and install the web deploy tool on this virtual machine. So let me start with the enhanced security configuration.

So let me template this. Turn this off, click on OK,go on to I and search for Web Deploy 3.5. So I'll go out and download this tool. So I'll click on download. So I'll choose a 64 bit. I'll click on Next. I'll say I want to run the tool. Once the installation starts, I'll click on Next except the licence agreement goes on to Next. I'll install all of the features. Click to install. Once installed, I'll click "Finish." So that's done. Now let me go back to Azure. Let me go on to the network security groups. So I have a rule for port 80. Now I also have to go ahead and add another inbound port rule. So this is for port number 8172. So this will allow our local workstation to go ahead and publish a solution onto the virtual machine. I'll select the IP address of my client workstation. I'll leave the source code range as it is. For the destination, I can choose Virtual Network, pressTCP. Just change the name and click on Add. So now I have a security rule in place as well for port 8172.

Now, after a couple of minutes, just to ensure the rule takes effect, So in Video Studio, let me go ahead and create a new profile. So I'll choose Azure Virtual Machines. Let me go ahead and click on Browse. So again, since I've turned on to my Azure account, I should be able to see all my virtual machines. Let me go ahead and choose the Demo VM virtual machine. So it'll actually go ahead and quickly check the configuration of the Azure Virtual Machine. If there are any issues, it will actually notify you. But since we have gone ahead and installed or implemented all of the prerequisites, we can now go ahead and publish a solution on this virtual machine. So let me go ahead and create the profile. And finally, let me go ahead and click on Publish. So it will ask for the credentials of the virtual machine. You can accept the security certificate by clicking on Accept. And now it's going to go ahead and publish your Visual Studio solution on to the virtual machine. Now, once this is done, in another tab, if I go onto default, aspx, I should be able to see my application. So now, very easily, you can go ahead and publish your application from Visual Studio onto this virtual machine. So this marks the end of this chapter.

5. AZ-203/204 - Lab - Building a Linux virtual machine

Hi and welcome back. Now in this chapter we are going to go ahead and create a virtual machine which has Linux as its underlying OS, so this is also an objective in the exam, so let's go ahead and add a resource. Now I'll go ahead and choose Ubuntu Server as the underlying Linux OS, so please note that you can also choose other Linux distributions to be the underlying OS for your virtual machine. For now, I'll choose the Ubuntu server, so I'll choose my same resource group. I'll give a name for the virtual machine. I'm going to choose the same region as we have for our Windows virtual machine, so I'm leaving the image hazardous I'll leave the size hazardous now in the authentication type. If you want secure authentication, go ahead and use a public key.

Otherwise, you can go ahead and specify a password. So just to make this demo a little bit simpler, let's go ahead and choose a password and let's give a username and password which you can use to log into the Linux instance. We are now allowing inbound traffic on port 22 in the selected ports, so if you want to connect to the virtual machine with an a Linux OS, we must connect on port 22. Let me go on to Next for the disks, so again, I’ll leave the discs as they are now in the network. What's going to happen is that it's going to detect that we already have an existing virtual network that's part of the central US region. Please know that if you had to create your virtual machine in a different region, let's say the West US region, then this wizard would automatically try to detect if you have a virtual network in that particular region. If you don't, it doesn't go ahead and create a new virtual network.

Now, please note that you can also go ahead and just create a new virtual network in this region just to host your Linux virtual machine. It's up to you. At the moment, I am leaving this Linux virtual machine on our existing virtual network I'm also ensuring that the Linux virtual machine will be assigned a public IP address I'll leave everything as it is contained for the management again. I'll just turn off poor diagnostics I'll leave the advanced hazards and let me go ahead and create this virtual machine. Again, Please take a note of the cost per hour when it comes to this virtual machine, and then I'll go ahead and create the virtual machine now. While this is being cleared up, I am currently on a Windows client machine, so on a Windows workstation. If you want to go ahead and connect to this Linux virtual machine, then you should go ahead and download a tool known as Putty. So you can go ahead and download the tool over here.

Once you have the tool in place, once you install it. This is what it looks like. So over here, you can go ahead and connect to our Linux virtual machine. So let's go ahead and wait for the deployment of this virtual machine. Now, once the deployment of the virtual machine is complete, we can go ahead and onto the virtual machine. Now remember, we're going to be using the Putty tool to go ahead and connect to the virtual machine. So let's take the public IP address. So I'll go on to the Putty tool. I'll put it as the host name or the IP address. I'll leave the port number as is and click on Open. So I'll enter the username and password that I mentioned when I created the virtual machine. Now, once you're logged in, similar to the chapter on installing a workload on a Windows virtual machine, we can also go ahead and install a workload on this Linux virtual machine.

So I'm going to go ahead and install a tool known as NGINX. So this is a web server that's available for Linux distributions. Now, before that, the first thing that we can do is to issue a pseudo update command to update all the packages on this particular system. Once the app's get update command is completed, I'll issue the following command to install the NGINX web server. Now, once the installation of the web server is complete, we can actually go out and take the public IP address virtual machine, go on to a new tab, and then browse for the web server homepage. But before that, we have to again go on to the networking section. You have to ensure that you add a rule for port 80. So even that NGINX web server listens on port 80. So let's go ahead and add an inbound port rule.

So very quickly I'll mark the destination has port 80, give the name, click on add. Now, once we have the rules in place, let’s go on to the overview blade. Let's take the public IP address, go onto a new tab, and now you can see the homepage for the Internet's web server. So this marks the end of this chapter wherein we looked at how to spin up a Linux virtual machine.

6. Understanding Network Security Groups

Hi and welcome back. Now, in this chapter, I'm going to go ahead and explain the concept of having a jump server or bastion host which can be used to access your virtual machines or part of your virtual network. Now, over here, I'm giving an example of a virtual network. So let's say a virtual network has three subnets. Now, let's say in one subnet you're hosting a web server. So you're basically allowing traffic on port 80. And let's say you have a database server, so the web server communicates with the database server. Now, when it comes to administration for either of these servers, one of the common ways of probably doing this initially is to ensure that, let's say, the database server has a public IP address. And if it's, let's say, a Windows server, and let's say a Windows server, you basically allow traffic on ports three, eight, and nine, so that forms a workstation on the Internet.

You go ahead, connect to the virtual machine and perform whatever administration you want. You could go and install database software and configure database software for all that you have, but you have to ensure that it has a public IP address. Now, this is obviously a security concern, especially when it comes to a database server. So remember, the database server should only be used within the virtual network itself. Your web server should only be able to communicate with the database server. Also, when it comes to allowing traffic on port 3389 onto your web server, that should also be highly restricted. So what's the other way, or the secure way of, let's say, administering these particular virtual machines? Well, the answer is using a jump server or a bastion host.

So what you normally do is that you create another virtual machine that's part of your virtual network that you allow remote access to. Let's say again, this is a Windows machine on port 3389. So that's to this machine, and then from this machine, you go ahead and remote desktop to the other virtual machines via their private IP addresses. So you will no longer assign a public IP address to this virtual machine. No, you will administer this virtual machine via its private IP address. So you will log in first on this virtual machine, and from this virtual machine you will go ahead and administer the other virtual machines which are part of your virtual network. Yes. Obviously, this virtual machine needs to have a public IP address so that you can connect to it from the Internet. This is the entire idea of having a jump server or a bastion host.

Study with ExamSnap to prepare for Microsoft Certified: Azure Developer Associate Practice Test Questions and Answers, Study Guide, and a comprehensive Video Training Course. Powered by the popular VCE format, Microsoft Certified: Azure Developer Associate Certification Exam Dumps compiled by the industry experts to make sure that you get verified answers. Our Product team ensures that our exams provide Microsoft Certified: Azure Developer Associate Practice Test Questions & Exam Dumps that are up-to-date.