Pass Microsoft Azure AZ-204 Exam in First Attempt Guaranteed!

All Microsoft Azure AZ-204 certification exam dumps, study guide, training courses are Prepared by industry experts. PrepAway's ETE files povide the AZ-204 Developing Solutions for Microsoft Azure practice test questions and answers & exam dumps, study guide and training courses help you study and pass hassle-free!

Develop Azure Infrastructure as a Service compute solutions

12. AZ-203 - Introduction to the Azure Batch Service

Hi, and welcome back. Now, before we move forward, it's important to understand the architecture of the Azure Bath service. Basically, what are the important parts of the Azure Bath service? Now let's say you have your application, so your application can make EPA calls to the Azure Bat service. Now, along with your application and the Azure Backup service, you can also provision an Azure Storage account. So remember, your Azure Storage account can be used to store the input and output files for Azure Batch. So now let's say that your application is responsible for processing videos, so it could submit the videos to the Azure Bath service for processing. Now, when the request is made on the Azure Bath service, you basically make a request to create a job. The job would then have tasks. So let's say one of the tasks is basically to process the videos.

Now, what the Azure Batch service will do is ensure that it creates a pool of virtual machines. These virtual machines will go ahead, pick up the tasks, and basically execute those tasks. Now, what is the underlying application or what's the underlying process that's going to run on this virtual machine? So remember that your application, your main application, wants to ensure that the AzureBatch service will process the videos. So the application or module that is required to process the video needs to be installed on each virtual machine so that particular module can be downloaded from the Azure Storage account. So the Azure Batch service will take that module, which is required to process the videos, from the Azure Storage account and then install it on the virtual machine. The virtual machine in that pool would then start converting or processing those videos. Now, the video itself is basically an input. So what your application can do is take the videos from the users. It can store the videos as input files in the Azure Storage account.

Your Azure Batch service will then take the videos and the input videos and give them to the virtual machines. The virtual machines will then start processing those videos and whatever the output is. So remember that your batch service is executing something on these virtual machines. Whatever the output is, it can then be stored in the same place as your storage account. So these are all the important parts that you need to understand when it comes to the architecture of the Azure Batch service. So first, you have the service itself. It's basically something known as an account. So you create something known as an Azure Batch account. In your Azure Batch account, you basically have jobs. The job consists of tasks. You don't have the pool. So the pool is basically the virtual machines that are used to execute those tasks that are pertinent to the jobs. You then have your Azure Storage account, which can be used to basically store the applications that run on the virtual machines. It can also be used to store your input files and your output files as well. Right, so this is just a quick take on the architecture of the Azure web service.

13. AZ-203 - Batch Service Architecture

Hi, and welcome back. Now let's go through some of the important points for the Azure Batch service. So, use a service when you want to run large-scale and high-performance batch jobs. Now, in the batch service, remember that it will automatically manage the pool of nodes. So these are the virtual machines that will actually carry out those batch jobs.

The batch service itself will also automatically install the required applications on the virtual machines. So whatever is required to actually process your jobs can be automatically installed by the Azure Batch service. It will also automatically schedule the jobs to run on the virtual machines. Now, some of the examples given in the Microsoft documentation on the types of workloads you can run using the Bath services are as follows: if you want to perform any 3D image rendering, then consider using the Bath service.

If you want to calculate or do financial risk modelling using the Monte Carlos simulations, then consider the Azure Bath service. If you want to carry out any image analysis or any media transcoding, So all of these are really high-powered computers and resource-intensive operations. So if you have any of these requirements, then consider using the Azure Backup service. You can use the virtual machine. The high-performance virtual machines used to run inPanel have jobs using the Azure Batch service. Now, I have a quick review of the basic service workflow in the Azure Bath service.

Now, the data files and the application files will reside in the Azure Storage account. So the application that needs to be installed on the virtual machines that will actually do the underlying processing will actually be stored in the Azure Storage account. And those files, which are basically input files for your Azure Batch service, are what you need to process. So, for example, if you want to process video files, these video files also need to reside in an Azure Storage account. The Bat service will automatically create a pool of compute nodes. You then create a job in the BAT service. The job is nothing but a collection of tasks.

The tasks of the job will run in a specific pool. Each task that is run will upload its output as well onto the Azure Storage account. And we're going to see all of this in subsequent demos. Now, in your pool of nodes, you can decide to either have dedicated compute nodes or low-priority compute nodes. So what's the core difference? Now that low-priority nodes are less expensive, they take advantage of the surplus capacity that is available in Azure. But what's the caveat? So, if there is insufficient capacity in Azure, then the low-priced nodes that are assigned to your batch job can be taken back. So if you decide to use the low-priced nodes as part of your batch service, then you have to keep this in mind. So any time the capacity decreases to zero, these low-priority nodes can be taken back from you.

Now, if this is done, the task that is running will be stopped and will only run again once a node is back online. So only consider low-level nodes when you have jobs that can be distributed across multiple nodes. So let's say that you have about five to ten nodes, and the jobs are being distributed across these nodes. So when there is less capacity in Azure, maybe not all of the nodes will be taken back from you, just a partial set of the nodes. So in such a case, use low-priority nodes when your jobs can run on multiple virtual machines. Also, if the jobs can be resumed easily and a lot of work is not lost due to a cancelled task, then consider using low-priority nodes. If you want to ensure that jobs are never terminated, then consider the use of dedicated compute nodes. Now you can work with the Azure Bath service either via the portal, via the SDK, via API calls, or via the Azure command line interface. There is also a tool known as the Azure Batch Explorer that can be used to work with the Azure Batch service. Right, let's mark the end of this chapter, in which we have looked at some of the important points of the Azure Batch service.

14. AZ-203 - Azure Batch Service - Important Points

Hi, and welcome back. Now, before we go on to the Azure Portal and see how we're going to work with the AzureBatch service, let's have a quick understanding of what exactly we are going to do in our lab. Well, the first thing we're going to do is create the Azure Batch account. Along with that, we're also going to create an Azure Storage account.

Now, in the Azure Storage account, we're going to be storing a video file known as Sample MP4. We're going to be using a tool. We're going to be downloading a tool known as FFMPG. So this is a freely downloadable tool. This is a tool that can be used to basically record Or you could convert videos from one format to another, or you could even extract the audio from the video file. This is a multipurpose tool that's available on the Internet. We're going to associate this application with the Azure Batch account.

And we're also going to associate the AzureBatch account with our Azure Storage account. In the Azure Batch account, we're going to create a pool of just one virtual machine that's going to be a dedicated virtual machine. In that batch account, we're going to create something known as a job and a task. Now, what this job and task are going to do is that they're going to take this file, our application. So this is going to be our application. It's going to download and install the application. But in this case, it's just an executable. It will just download and place the executable on this virtual machine, and then it's going to execute a command as part of this task that's actually going to pick up this video file from my Azure Storage account.

It's going to use Ffmpg executable on this virtual machine, and it's going to extract the audio and create a new audio file. So this is going to be a simple example of how we're going to be using the Azure Batch service. Remember, you can use the Azure Batch account to run multiple jobs, perform multiple tasks, take multiple video files in this example, and create multiple audio files. So depending upon what you want to process as part of the Azure Backup service, you can do so. But from an exam perspective, it's important to understand this entire workflow. So we're going to do this step by step and understand why the execution of a simple example is necessary. So let's move ahead with our lab.

15. AZ-203 - What are we going to do in our labs for Azure Batch

Hi, and welcome back. So now we're going to go ahead and see how we can use the Azure Batch service from the Azure Portal. So now for this particular lab, we're going to be using a tool known as FFMPG. So this is a cross-platform solution that can be used to record, convert, and stream audio and video. Now, just to give you an example, here we are at the command prompt. Now, in one of my folders, what I have is a sample.mp4 file. So this is just a sample video file. I've also gone ahead and downloaded the Ffmpg executable. So on the site itself, you can go ahead and download the tool itself for the platform. So currently, since I'm on Windows, what I've done is that I've gone ahead and downloaded the zipfile, which is available for the Windows platform.

I extracted the zip codes, and I have just taken the executable from that zip file. Now we can use this executable to actually extract the audio file from the sample.mp4 file. So I would go ahead and execute this command with your input. It will take the video file and then go ahead and copy the extracted audio file. Now, once you execute this command, if I now look at my directory, I can see that I have the extracted audio file. So what I've just done is make sure that I understand the complete process that I want to execute using the Azure Batch service. So here we are, Azure. Now let's go ahead and create a storage account.

So remember, the storage account will be used to store the application that is going to run on the underlying virtual machines in the Azure Bath service. It will also be used to store the input files and the output files from the Azure Batch service. So let's go ahead and do that. So we can go ahead and create a storage account. I'll choose the resource group. I'll give you a storage account name. I'll choose a region. I'll just keep the replication servers locally running and in storage. I don't need high availability for the solution since this is just a demo in advance. I'll keep everything as it is. I won't add any tags. I'll go on to review and create. And let me go ahead and create this storage account. Now, once the storage account is in place, you can go ahead and access the resource. Now you can go on to the blobs. We can also go ahead and create a container known as input. So this can be used to store all the input files that are going to go into the batch service. You can also create another container known as "output." Now, once this is done, let's go ahead and move on to blobs. Let's go on to the Input container and let's upload our sample MP4 file. So remember, this is going to be our input file for the Azure Batch service. I'll click on "Upload" once a file is in place. Now let's go ahead and create an Azure Batch account.

So you can go ahead and choose the batch service. Click on Create, select a resource group, and give an account a name. I'll leave the location as "central US." You can select a storage account. Remember, we created a storage account. So I'm going to choose that. Go on to Next for more information. So now, in the pool allocation mode, you have two choices. You have either the BatService or the user subscription. Now, if you choose the Bad service, then those virtual machines that are going to do the processing as part of the Azure Batch account will actually be managed by the account or the service itself. If you want to manage the virtual machines yourself, you can actually make it part of the user subscription. So I'm going to leave the default as the batch service. I won't add any tags. I'll go on to review and create, and then I'll go ahead and create the batch account. Now, once your batch account is in place, you can go ahead and access the resource. Now, the first thing we'll do is go on to the applications. So now we're going to go ahead and associate our video processing application so that's FMPGAs part of your batch account.

Now, please note that you just have to go ahead and create a zip file out of the executable. When the application is being used by the AzureBatch service, it only accepts zip-based files. So all you have to do is go ahead. I already have an archive-based tool installed on my machine. You can just make sure it's in Zip format. So let's go ahead and click on "Add." So over here, it's asking for an application ID. So let's enter the name. We can also enter the version number for our application. So the current version number of this application is actually 4.2. So I'll enter that. Now we have to go ahead and select our application package. So I'm going to select the zip file that I have on my local machine. I'll click on "submit." So now it's going ahead and uploading a zip package onto our storage account. Now that this is in place, you can now see your application. Now we can go on to Pools. And now we can add a pool for our virtual machines. So let's click on "Add." Let's give the pool an ID. So this is basically a name for the pool. Now what is the underlying image type that you want for the underlying virtual machines?

So I'm going to choose "Windows only." I'll choose the OS family as Windows Server 2016 and leave the OS version as it is. Now, if you scroll down, you can choose what the underlying size of the virtual machine should be. So I'll choose the recommended size for one computer and 3.5 GB of memory. Now, here, you can specify the number of dedicated nodes and the number of low-priority nodes. So remember that the low-priority nodes are the least expensive. But remember, if there is a shortage of resources on the SEO platform overall, then these nodes will be taken away from you. So, just for the purpose of this demo, I'm going to ensure that I have one dedicated node as part of my pool. If you want, you can also decide to auto-scale your entire scale settings. So if you go on to autoscale, you actually have to give a formula based on how you want to autoscale the number of virtual machines in the pool. For now, I just leave it as fixed. If you want, you can decide whether you want to have one task that is a start task that will run each node when it is created as part of the pool.

For now, I'll leave it disabled. You can see that there are many other options that you can specify as part of the pool. I can also specify what application packages need to be installed on this pool of virtual machines. So I can choose my FFMPEG application and the version of 4-2 and click on "Select." Now let me go ahead and click on OK. If I click on Refresh, you can now see that the demo pool has been created. You can see that now the allocation state is resizing. That means what it is doing is going ahead and creating one dedicated note; it's basically now spinning up a virtual machine with part of the spool. Our job, our VOC, will then run on this virtual machine in the spool. Please note that you can have a number of dedicated nodes, and if you have multiple jobs, they can run across these nodes. Just to make this lab simple for you to understand how this all works, we just have one node as part of the pool as part of our patch account, right? So now we can see our allocation state is steady.

That means we now have one virtual machine as part of our pool. Now, the next thing is to go ahead and create a job. So the job has to run as part of a batch account. So let's go ahead and click on "Add." Now, here we can give the name of the job or the job ID. We can select the pool. So this is the pool on which the job will run. So I'll select this pool, and let's go ahead and create our job, right? So now the job is in place. Let's click on the job. Now we can add tasks to this job. So, what exactly do we want to run? Well, we want to run a task that's going to convert our sample MP file into a file in our container in our storage account. So let's go ahead and click on "add over here." Let's add the task ID or just give the task a name for the task. Now here we have to give the command line. So what exactly is our task going to be? So let me go ahead and add the commandline. So let's go ahead and look at the command line. So how do we reference our package in the batch account? So that's why the command of the Easyunderscore Batch Underscore app underscore "package" and then underscore "what is the package ID?" So remember we had given an application versionID of Ffmpg and then we have hashand, then what is the version number? So this is how we can actually reference the application through the command line.

And then obviously, this is just a reference to the application version. And then obviously we have to reference our exe as well. And the rest of the command is the same. So it's taking the input of the sample MP4 file, and we're saying to copy the output as audio AAC, right? So this is our command line, which is going to run as part of the task on the pool of one virtual machine. So how does the Azure Batch account actually get a sample MP4 file? So remember, that's in our storage account, so we have to mention it as part of the resource file. So these are the two important things to understand from the Azure Backup Service when it comes to the exam. So we are going to choose the resource files. Now that we're over here, we can go ahead and pick our storage container. Now, when the Azure Batch service makes reference to the storage container, you have to make sure to use the shared access signature. This is a good practice. Now in a subsequent chapter in another objective for the exam, as part of this course, we have details on what exactly is the shared access signature and what it basically is: storage accounts.

So if you don't have any knowledge about storage accounts and shared access signatures, you can always refer to those videos in the subsequent chapters. For now, what I'm going to do is click on Include SAS, the shared access signature, which expires in seven days, and let's click on OK. Now we'll go ahead and choose the container, which basically has a sample empower file, and that's our input container. Now we can go ahead and click on "Submit," right? So now our task is complete. We can go ahead and click on "Submit" for the task itself. Now, if you go ahead, you can click on Refresh to actually see what the state of the task is. So the task will automatically start running. Now, after about five to 10 seconds, you can see that the task is complete. You can go on to the task itself. Now here, you can see the files that are on that virtual machine. So remember, the virtual machine has now run a task. It has gone ahead and downloaded that sample MP4 file. It's done the processing.

And also, it has created a standard error and standard output dot TXT file. Now, if you go on to the files on node, you can now see your audio dot AAC file. You can actually go ahead and download the file itself. So that means our task has been completed. So remember over here, we have just made our Azure Batch service run a single job with a single task to basically convert a video file. You can actually expand this to create multiple jobs with multiple tasks and multiple input files. But for the purpose of the exam, it's very important to understand this workflow. How does the Azure Backup service actually work? And that's why we just took a simple example of how to convert a single video file, right? So this marks the end of this chapter, in which we have seen how to use the Azure Batch account from the Azure Portal.

16. AZ-203 - Lab - Azure Batch Service - Azure Portal

Hi, and welcome back. Now we are going to understand how to basically work with the BAT service from a simple program. Now we've already seen how to work with the bad service from the Azure Portal. Now we're going to see how we can work with it from a simple console-based dot-com application. Now, if I go to Tools, I'm in Visual Studio. If I go on to the Nougat package manager, let me manage the nugget packages for the solution, and let me just show you what I've installed. So when looking at the install packages, if I go to Microsoft Azure Patch, what I will point out is the version number. So over here, I have Version nine one.

Now in the current version of Azure Batch, the package is basically twelve zero. Now there are key differences in the package for Microsoft Azure Batch after version 100. Now, as part of the Microsoft documentation and the exam, I want to go through both of the changes or both of the versions of Microsoft Azure Batch. So in this lab, we're going to reference the version number that's prior to 10.0.

And then I have another lab in which we will look at the most recent version of Microsoft Azure Batch. And then, apart from that, I also have Microsoft Azure storage. So this is the version number that I have. So these are the two NuGet packages that are part of my project. The other packages were automatically installed when I installed the prior two packages. Now let's go over to our program. Now I just have one simple class, a programme CS class. So this is basically a console-based application. So let's go through the entire aspects of this code.

So the first thing I have are basically constants, which have details of our batch account name, a batch key, and a batch account URL. Now you can get all of these details from the Azure Portal. So if you go on to your batch account, if you go on to keys over here, you can get your batch account name and your batch account URL, and you can use any one of the access keys. So I've gone ahead and added those to my program. Now next we'll go ahead andadd our storage account details. Again, we have to add the storage account name and the account key. Again, you can get this from the Azure Portal. So if you go on to Azure, if you go on to your storage account, Now, if you go on to access keys here, you have your storage account name and you can take either key one or key two. In this example, I've gone ahead and copied key one. So you can just go and click on Copy, then go back to your programme and add it over here. Now, next are some other generalvalues required for the batch service.

So I'm just giving a pool ID a name for the job. What is the package ID? So our application ID and our application version Now, this particular programme is actually going to create a pool of virtual machines, create a job, and create a task. The Azure Batch account is going to already exist, and we're only going to ensure that the application has been uploaded onto our Azure Batch account. So these are the only prerequisites that we're going to do, or we will ensure they're done via the portal. The other aspects are going to be covered by the programme itself. Now in the main function, I just have one method calling another method itself. Next, I'm going ahead and using the batch line to start working with our Azure Batch account. In order to authenticate my programme with the AzureBatch account, I'm using all of the account details to basically create batch shared key credentials. So I'm using that along with the Batch client to go ahead and now work with an Azure Batch account. So I have three other methods.

So we're going to go ahead and create a pool of virtual machines, create a job, and then create a task. So let's go ahead and see what's in all of these methods. So if I go on to the pool creation method, I'm basically passing in the batch client and a pool ID. So what's the name of our pool? So the first thing I'm doing is making a reference to the underlying image I want to use for the virtual machine. So I'm going to be using Windows Server and the SKU of the 2016 data center. I'm going to go ahead and make sure that I'm using an AMD 64-bit computer. If I scroll down, I am then going to initialise a demo pool that's of the type cloud pool. I'm going to ensure now that I'm using the batch client pool operations and the Create pool method to go ahead and create the pool. So over here, I'm making sure that I have one dedicated node, no priority nodes, and I'm giving a size for the virtual machine. I'm also making sure that if I scroll a little bit down, the pool is going to reference our application. So remember, our application is only going to be part of the Azure Batch account. And I'm just going to go ahead and do a commit async, and this is going to ensure that it creates the pool of virtual machines.

So this is from the method of creating the virtual machine pool in the Azure Batch account. Let's go ahead and see how to create a job. So if I go down, let's go on to the job creation method. It's pretty simple. So over here, I'm using the cloud job type. I'm using the batch command job operations to create jobs. Now, from an exam perspective, it is important to understand these methods and types, not only for the AzureBatch service but for other services as well. Now for the job, I'm making sure that I associate with the pool, and then finally, I'm going to commit async to go ahead and create the job. So again, this is pretty simple. Now we come to the method of task creation. So over here I have my task ID, the name of the task, and what's my container? So remember the input and what the blob name is. So what exactly is the file I want to convert as part of the task? Now over here, I have basically the connection string. So first, I'm going to go ahead and basically connect to my Azure Store account. I'm going to go ahead and create a cloud block client. So this is going to ensure that I can actually connect to the container and get a reference to the blob. Now I also have the resource files. So remember that the resource file is basically a reference from the Azure Batch account onto the storage account.

It's based on the resource files that Azure Batch knows where to pick up those input files. Now in version 90, remember that we are using the package of version 90 for Azure Batch. This is how you can actually reference the resource files. When you go on to version ten and above, there is a key difference in how you basically reference the resource file. So currently over here, by using it, it has a list of resource files if I go a little bit down. So now I'm getting the container reference, and then I'm getting the reference to the blob itself, to the sample MP file. Remember that in order for the Azure Blob service to make use of Azure storage accounts like we saw in the Azure Portal, it is very easy to go and do a check and make sure that Azure Batch uses a shared access signature to reference the blob in our storage account.

Over here in the code, I'm first going ahead and creating a constraint, and then after that, I'm going ahead and creating a SAS token and then a SAS Blob URL. Remember that we have another chapter in which we will go ahead and understand the concept of a shared access signature. In case you're not aware, you can go to the chapter, understand the shared access signature, and then come back to this code. Now that we have the SAS URL for the blob, we can go ahead and add it to our resource file list. So if you have multiple video files that need to be processed, you can get the URL for each file and add it to the list of resource files. We then have our application. So the format is still the same. We have easy underscore batch, underscore app, underscore package, underscore the applicationID, and hash the application version.

And then we are constructing our command line. So this is the same as what you saw in the Azure portal. And then finally, we create a new cloud task with our command line and the ID. We mention the resource files, and then finally, we add the task to the job. That's it. Now let's go ahead and execute each of these methods and see how it works. So now that we're here, we're going to go ahead and run the program. So, just to recap, as part of our Azure Batch account, we're going to use the same account that we created in the early chapter of the previous lap. We still have our application, FFMPEG. But if you go on to the pool, you don't have a pool as of yet. And if you go on to the jobs, we don't have a job. So I've gone ahead and deleted the existing pool and the jobs. We're going to basically create this from our DotNet program. So in.NET, please ensure that you've changed all the relevant storage account names, the storage account key, the batch account name, the batch account key, and the batch account URL.

Now what we're going to do is that we're going to go ahead and execute each method one by one just to see how it works. So first is basically the creation of the pool. So let me go ahead and run this path, right? So it's creating a pool of virtual machines. Now it's saying the programme is complete if you go on to our batch account. Let's go on to the pools. So now you can see that our demo pool is in place. So now it's going ahead and creating that virtual machine, which is part of the pool. Now let's go ahead and run the other parts of our program. So I'll just come in here and go ahead and create a job. So I go out and run the program. So the programme is complete, and if you go to Jobs, you can also see our job is in place. Now let's go ahead and run the programme with our task creation. So it's gone ahead and created the task. Let's go back to zero. So in Azure, if you go on to a job, we can now see a task in the active state. And after some time, you can see that the task is now complete. So, similar to what we saw in the lab in the Azure Portal, we also were able to ensure that a Dotnetprogram was able to run a task within a job based on a pool in the Azure Batch account. So this marks the end of this lab.

Microsoft Azure AZ-204 practice test questions and answers, training course, study guide are uploaded in ETE Files format by real users. Study and Pass AZ-204 Developing Solutions for Microsoft Azure certification exam dumps & practice test questions and answers are to help students.