Pass Microsoft Certified: Azure Developer Associate Certification Exams in First Attempt Easily

Microsoft Certified: Azure Developer Associate Certification Practice Test Questions, Microsoft Certified: Azure Developer Associate Exam Practice Test Questions

Want to prepare by using Microsoft Certified: Azure Developer Associate certification exam practice test questions efficiently. 100% actual Microsoft Certified: Azure Developer Associate practice test questions and answers, study guide and training course from Exam-Labs provide a complete solution to pass. Microsoft Certified: Azure Developer Associate exam practice test questions and answers in VCE Format make it convenient to experience the actual test before you take the real exam. Pass with Microsoft Certified: Azure Developer Associate certification practice test questions and answers with Exam-Labs VCE files.

Develop Azure Infrastructure as a Service compute solutions

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 theprocess of being able to publish a web project fromVisual Studio on to an Azure Virtual machine. So over here I have on my virtual machinein place, it's a demo VM virtual machine. This is based on a Windows Server 2019 data center. Now, if I go on to Visual Studio So here is 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 onto 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 onto 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 what those steps are that need to be performed. So, first and foremost, allow me to enter Azure. So over here we have to first go to the DNS name for the virtual machine. Hit 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 Swatch machine. So let me go ahead and click on "Save." Now that this is done, let me go ahead and connect to the virtual machine. So please allow me to remove desktop from 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 now that I've ensured that I have Internet Information Services installed on this particular virtual machine. So if you want to go ahead and install agent information services on the server holds 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 onto the next framework. So, since I have a 4.7 framework application that needs to be deployed, I have to ensure that ASP Net4.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 first, let me just go on to the enhanced security configuration. So let me temporarily do this. Turn this off, click on okay, go onto I, and search for web deploy. So I'll go ahead and download this tool. So I'll click on download. So I'll choose 64 bits. I'll click on "next." I'll say I want to run the tool. Once the installation starts, I'll click on Next, accept the licence agreement, and go on to Next. I'll install all of the features. Click on "Install." Once it's installed, I'll click on Finish. So that's done. Now let me go back to zero. 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, press TCP, 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, now that I've logged into my Azure account, I should be able to see all of my virtual machines. Let me go out and choose the Demo VM virtual machine. So it will 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 you've gone ahead and installed or implemented all of the prerequisites, we can now go ahead and publish a solution onto 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. Click 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 to ESPN by default, I should be able to see my application. So now, very easily, you can actually go ahead and publish your application from Visual Studio onto this watch 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 that has Linux. has the underlying OS, so this is also an objective in the exam, so let's go ahead and add a resource, and now I'll go ahead and choose Ubuntu Server, which has 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 Ubuntu Server so I'll choose mysame resource group I'll name the virtual machine and select the same region as our Windows virtual machine, so I'll leave the image hazardous. I'll leave the size "hazardous" now in the authentication type; if you want secure authentication, you can go ahead and use a public key, or else 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 give a username and password that you can use to log into the Linux instance. Now in the selected ports, we are now allowing inbound traffic on port 22, so when you want to go ahead and connect to the virtual machine, which has a Linux OS, we have to connect on port 22. Let me go on to Next for the disk, so again, I'll leave the discs as they are now in the networking. 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 are 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 will go ahead and create a new virtual network. Now, please note, 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 am also ensuring that the Linux virtual machine will be assigned a public IPaddress I'll leave everything dangerous to continue. Next forthe management again, I'll just turn off poor diagnostics I'll leave the advanced hazardous area and proceed to build 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 actually currently on a Windows client machine, so on a Windows workstation. Now if you want to go ahead and connect to this Linux virtual machine, then you should go ahead and download a tool known as Footy. So, once you have the tool installed, you can go ahead and download the tool over here. This is what it looks like. So over here, you can go ahead and connect to our Linux virtual machine. So first, 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 move ahead with 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 put it in place as the host name or the IP address. I'll leave the port numbers as is. Click on "Open." So I'll enter the username and password, which 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, you 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 issue a "pseudo update" command to update all the packages on this particular system. Once the app get update command is complete, 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 ahead and take the public IP address of this virtual machine, go on to a new tab, and then browse for the web server homepage. But before that, we have to go on to the networking section. We have to ensure that we add a rule for Port 80. So even if Nick's Web server listens on port 80, let's go ahead and add an inbound port rule. So very quickly, I'll mark the destination as Port 80, give the name, and click on add. Now that we have the rule in place, let's go on to the overview blade. Let's take the public IP address, go on to New Tab, and now you can see the homepage web server. So this marks the end of this chapter, wherein we have 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 a bastion host, which can be used to access your virtual machines' RAPAF out 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. Let's say you have a web server in one subnet. 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. When it comes to administration for either of these services, one of the most common ways to begin is to ensure that, say, the database server has a public IP address. And if it's, let's say, a Windows server, you basically allow traffic on port 389 so that from a workstation connected to 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 of that, 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, database servers 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, where the answer is using a jump server or a bastion host? So, normally, you would create another virtual machine that is part of your virtual network and allows remote access. 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'll 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 onto this virtual machine, and from this virtual machine, you will go ahead and administer the other virtual machines that 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 bastion host for a jump server.

7. Using a jump server

Hi and welcome back. Now, in this chapter, let's look at a labon and how we can create a simple jump server. So I have one virtual machine, known as Target VM. so it's a default subnet in one of my virtual networks. Now, what we're going to do is create a new Windows virtual machine—a simple Windows virtual machine. So we'll make sure we can connect an Internet workstation to this virtual machine. And from this virtual machine, we should be able to remote desktop into the virtual machine—that's our Target VM virtual machine. So we just want to ensure that there is no public IP address that is assigned to this virtual machine. So let's go ahead onto Azure. So here we are in Azure. Now, currently I do have a public IP address that's been assigned to the virtual machine. Now, in order to ensure that we don't have a public IP address for this virtual machine, you can actually go ahead and go to the networking section. This is for the virtual machine. You can go on to the network interface. We can go on to IP configurations. We can go on to the IP configuration itself, and we can go ahead and click on Disable for the public iPads. And we can go ahead and click on "Save." Now, while this is being completed, allow me to return to the virtual machines. So my target VM is a virtual machine. So this is running as part of thedefault subnet in one of my virtual network. Now, let's go on to the virtual network. Let's go on to subnets, and let's go ahead and add a new subnet. So I'll just leave it as subnet A. I will leave the address range as it is. Let me go ahead and click on okay, so we have the subnet in place. Now let me go ahead and create a new virtual machine on this particular new subnet. So I'll choose my test environment. I'll choose my resource group. So it's in my test group; I'll give a virtual machine name. I'll pick the West Coast of the United States as my location. since that's the location of my target VM virtual machine. I'll choose Windows Server. I'll just change the size. I'll give the account details. I'm going to leave the permitted selected ports hazardous (4389) I'll go on to Next for the disks. I'll leave the discs in the networking as they are. So I'll choose my virtual network. I'll choose the new subnet that I just created, subnet A. I will definitely ensure that this virtual machine has a public IP address. Remember, this is required. I'll leave the network security groups there. Let me go on to Next for advance, go on to Tax, go on to Review and Create, and I'll go ahead and create this virtual machine. And then we'll come back once you have the water machine in place and once the public IP address has been saved. Now, once you have the jump server in place, So you can see the jump server has a public IP address, and that's fine. Now let me go on to the networking section. now in the inbound port rules for the network security group. So let me go on to the RDP rule. So to make this more secure, I'll input the source as an IP address. I'll give the IPS of my client workstation. I'll put "destination" as the IP address of this particular virtual machine. So, let's take a look at the private IP address of the virtual machine, the jump server. It's over here. Leave the portrait as it is. 3389, the action has been allowed. Let me go ahead and click on "Save." So now that we have the jumpsuit in place, let's go ahead and first connect to this virtual machine. So I'll go out onto the oval. Let me click on "Connect RDP." So let me just go ahead and connect to this virtual machine. Now, while I'm connecting to that virtual machine, let me go on to the target VM virtual machine.So here you can see that there is no public IP address assigned to the virtual machine. So now let me go on to the networking section when we get to the inbound port rule. So now over here, I'll mention the source as an IP address. And now as a source, I'm going to mention what the private IP address of our jump server is. So remember, this is for our target VM virtual machine. So we're saying that we only accept connections from the jump server and from nowhere else in the destination, which we can put as the virtual network. So if you want multiple virtual machines in this particular subnet to accept connections from our jump server, we can place "destination" as the virtual network. Leave all the settings as they are and click on "Save." So now that we have the rule in place, for the target VM virtual machine, this is the private IP address. So let me copy it. I'll go out onto the jump server over here. Let me go ahead and open Remote Desktop. Let me enter the private IP address of our target via a virtual machine. Click on Connect so you can see that we can connect. We enter the credentials Click on "Yes." So now, we have actually gone ahead and connected to our target VM virtual machine from our jump server. So now over here, only our jumpserver is exposed onto the Internet, which accepts connections from our workstation. From there, we can connect to other virtual machines in our virtual network using their private IP addresses. So this is secure because we are not exposing those virtual machines onto the Internet, right? So this marks the end of this chapter.

8. Lab - Using a junp server

Hi and welcome back. Now in this chapter, I want to go through Azure Bastion. So in the earlier chapter, I talked about the concept of a jump slabber, and we saw how to implement that. Now, in that sort of scenario, what you have todo is that the middle machine, which is used tobasically log on to the other virtual machines, you arebasically responsible for maintaining that virtual machine. So it's an extra piece of infrastructure that you need to maintain. Now, in Azure, there is a concept of Azure Bastion, which is a managed service that you can use to securely log into your internal virtual machines. So when you go in and basically use this service automatically, the service will provision a virtual machine or a resource within another subnet. The subnet needs to have the name Azure Bastion Subnet." So this particular resource willbe fully managed by Azure. You don't need to manage this resource from your client workstation. You can actually connect wirelessly via Internet wires as a Bastion host, and then you can go ahead and access the machines securely in your subnets. So here, you don't even need to assign public IP addresses again to your virtual machines. You don't even need to manage the network security groups. Right? So let's go over some notes on Azure Bastion, and then we'll see a lesson on how to implement this particular service.

9. Azure Bastion host

Hi and welcome back. Now in the prior chapter, we saw how to connect to our Target VM virtual machine, which doesn't have a public IP address. So we connect to that Target VM virtual machine on its private IP address via a jump server. Now we can also go ahead and connect to this Target VM virtual machine via the Azure Bastion service, which is a fully managed service that you can use to connect to your Windows and Linux-based virtual machines. So first, on the Target VM virtual machine, let me go on to the networking section. I'm going to go ahead and actually delete this rule for RDP because I won't need it anymore. Let me go and click on "yes." Now that the rule has been deleted, let's go over to the Overview. Now in the Connect button, so you have RDP forWindows based virtual machines, as such for Linux based virtualmachines, and then you have the Bastion option. So let's go ahead and choose that. Now, if I go and click on Use Bastion, it's actually going to go ahead and actually give me an error. So basically the error is that you need to have a subnet that has the name "Azure Bastion subnet." So this is a requirement in order to use the Bastion service because the Bastion service will basically create a virtual machine in that Bastion subnet, and then connections will be created from that Bastion host onto the virtual machines that we have in our virtual network. So let me go ahead and create a subnet known as your Bastion Host. So if I go on to the overview of my Target VM virtual machine, I can go on to the virtual network, I can go onto the subnets, and I can go ahead and add a new subnet. I'll give you a name as your Bastian subnet. It has to be the same name. I'll leave the address range as it is. Click on "Okay," and once we have the subnet in place, let's go over to our target. We have virtual machines. Let's continue to connect. Let's click on Bastion. Let's say we use bastion. Now over here, you can see you're not getting an error. So if you scroll on down, you can see that it is going ahead and creating a new public IP address that will be assigned to the Bastion Host. Remember, this is not a public IP address for the Target VM virtual machine. We can then go ahead and click on "Create." Once the Azure Bastion host has been deployed, you can proceed to provide the Target VM virtual machine's username and password. I'll go ahead and click on Connect. So it'll go ahead and open a new tab and start a session. So I just need to ensure that I allow the pop-up from this site. Let me go and click on Connect again. So now it's opening up in a new tab, I'll say "allow," and now I can see in another tab that we are now connected to our target VM virtual machine. So neither of us had to assign a public IP address to the virtual machine. Neither did we have any network security group rules to allow traffic on port 3389. Everything is done as a managed service via the Bastion host. You can then go ahead and work with the server as you normally would. Right, so this marks the end of this, wherein we looked at the bastion service.

10. Lab - Using an Azure Bastion host

Hi and welcome back. Now, in this chapter, let's have a quick introduction to Azure Resource Manager templates. So this provides the ability to define your infrastructure as code. So, go ahead and make templates with JSON, that JavaScript object notation. This defines the infrastructure and the configuration of the resources that need to be deployed onto Azure. So you have your JSON file, which is basically your Resource Manager template. You can go ahead and submit that to me as your resource manager. That JSON file could be used to create various types of resources. So you could use a file to create, let's say, a virtual machine and a real storage account, or even a virtual network. Now, there are different sections when it comes to the Azure Resource Manager template. So first you have the resource section. So this is used to specify the resources that need to be deployed. The variable section is available to you. So these are values that can be used in the template itself. We have a parameter section. This can be used to provide values during the deployment phase. And then finally, we have the output section. So this returns values from the deployed resources. We no longer need to dwell on Arm templates. So working with Arm templates is more from an administrative perspective, and you dwell more on that when you go ahead and give the AZ 103 or AZ 104 exam or even the Easy 300. For the purpose of this exam, I'm going to go through how you can go ahead and create and deploy Arm templates. Now, if you go on to any resource in yours, let me go on to an existing storage account. Now there is a property known export template" over here itself. So here you will get the JSON template, which can be used to go ahead and deploy the storage account. Now, if you want to go ahead and deploy your own custom template, so you can go ahead and create a new resource, you can search for template. So you can do a template deployment using custom templates. You can go ahead and hit Create. Now you can go ahead and build your own template in the editor. You can also go ahead and use the most commonly used templates. If you're starting out with creating templates, it's good to go ahead and choose an existing template to see how it works. You also have templates, which are available on GitHub as well. So there are a variety of templates available. Now if I just go ahead and choose to create a Windows virtual machine So, using an existing common template, you will now see that you are being directed on to the deployment of a simple Windows VM virtual machine. Now, if you go on to edit the template over here, you can see the entire JSON-based template that is used to go ahead and create the water machine. Now, this is kind of a lengthy template. And that's because, remember, when you create a virtual machine, you need to have a storage account in place for diagnostics. You need to have a public IP address, a network security group, a virtual network, and a network interface. So all of these need to be in place. So either the templates can go ahead and create all of these resources from scratch, or it can go ahead and use existing resources. So if you have an existing virtual network, you can ensure that this template references that existing virtual network. Now, if you go and again click on "Save," So here you just have to give the details for the deployment of this template. So you can go and mention a resource group; you can give the admin username, give the password, and give a very unique DNS label. Here you can choose the Windows OS version. So I leave everything as it is. You can agree to the terms and conditions, and then you can go ahead and click on Purchase. So what this is going to do is go ahead and actually deploy your Windows Virtual Machine. So, when you went ahead and created a Windows Virtual Machine, you had to go through a series of steps in a wizard, specifying the virtual network, the storage account, the disk, the IP address, and the network security group. But everything has now been embedded as JSON code in a template. So you can actually take this template, you can reuse it, and you can actually deploy it using the Azure Portal. You can also deploy it using PowerShell. So, if you need to deploy similar types of virtual machines, it makes much more sense to create a template, submit it to Azure, and Azure will go ahead and create the resources based on that template. Now, once the deployment is complete, you'll actually see a notification. So if you go on to your virtual machines, you'll be able to see your virtual machine, and along with the virtual machine, you'll be able to see even the other artefacts such as your virtual network, your IP address, etc. So all of this has been done with the help of ARM templates, right? So this marks the end of this chapter. You.

11. Azure Resource Manager Templates

Hi and welcome back. Now in this chapter, we are going to understand the concept behind the Azure Backup service. So, before we get into the Azure BadService, consider the following use case scenario. So let's say you have an application. So this application may be responsible for taking videos from users. So users could upload videos. Let's take the example of YouTube. So users are uploading videos using your application. Now let's say that before these videos can actually be stored, they have to be processed. So let's say that your system architecture consists of virtual machines that are used to process these videos. So on each of these virtual machines, you might install a module that could be used to process these videos. So your application takes the videos from the users and then submits the videos to a cluster of virtual machines. Each of these virtual machines has modules to process those videos. Now, why do we have multiple virtual machines? because you may have thousands and thousands of videos being uploaded by your users. And just having one virtual machine to process all the videos is not a very good architectural design. So you would split your videos amongst multiple virtual machines. So in such an architecture, you are basically responsible, or your application is responsible, for the maintenance of these virtual machines. So you are basically responsible for maintaining the cluster of these virtual machines. You are responsible for ensuring that on each virtual machine this module is installed, and you are responsible for ensuring each virtual machine gets the videos. Following that, the videos are likely to be stored in an Asia storage account. So this is a sample architecture for an application. So now we come to the Azure Batch Service. So in the Azure Batch service, what you can do is that you can create something known as an AzureBatch account, and your application can actually interact directly with this as your batch account using the API calls. So let's say that the videos that users are actually uploading as part of your application need to be processed. You could instruct your batch account to take those videos from your application and send them to a pool of virtual machines. So now that we're here, your Azure Batch service is responsible for picking up the videos from your application and then sending them across to the virtual machines for processing. Now, the advantage is that the Azure Batch service is responsible for maintaining the cluster of your virtual machines. So it is not part of your application or the responsibility of your application to maintain the spool of virtual machines. Your Azure Batch service can automatically pick up the videos that are submitted by your application. Your Azure Batch service can then distribute the videos for processing on the virtual machines. Even that module, which needs to be installed on each virtual machine for processing the videos, can actually be automatically installed by the Azure Batch service itself. And whatever the output of the processing is, again, it can be stored in an Azure Storage account using the Azure Blob service. So all of the headaches that we saw earlier on as part of your architecture can actually be taken care of by the Azure Backup service itself. So this is just to give you a quick introduction to the Azure BAT service. Obviously, in subsequent chapters, we are going to look at or dwell more on the Azure Batch service. You're going to see how we can use the Azure Bath service to process jobs on demand. Right, so this marks the end of this chapter.

So when looking for preparing, you need Microsoft Certified: Azure Developer Associate certification practice test questions and answers, study guide and complete training course to study. Open in Avanset VCE Player & study in real exam environment. However, Microsoft Certified: Azure Developer Associate exam practice test questions in VCE format are updated and checked by experts so that you can download Microsoft Certified: Azure Developer Associate certification exam practice test questions and answers files in VCE format.