Azure Full Course | Microsoft Azure Tutorial For Beginners | Azure Cloud Computing | Simplilearn

Key Takeaways

[Music] Welcome to our Azureful course by Simpleon. Ever wondered why Microsoft Azure is taking the lead in the cloud world? Well, here's the scoop. Azure is the go-to cloud platform for businesses around the globe. From building powerful applications to managing vast amount of data and implementing cuttingedge AI solutions, Azure has become the backbone of modern enterprises. Now, as more companies shift to the cloud, the demand for skilled Azure professionals is soaring, creating endless career opportunities in cloud computing, AI, DevOps, and cyber security. In this course, you will get hands-on with everything Azure has to offer. We will start by showing you how to build cloud-based applications and efficiently manage cloud resources. You'll also gain the skills to secure cloud environments and work with databases, ensuring you're equipped to tackle real world challenges. And here's the best part. We have got a special Azure job interview prep section packed with essential interview questions to help you shine in front of the future employers and accelerate your career in the cloud industry. Now before we move on, if you are interested in becoming a cloud expert then simply learns cloud architect master program is the perfect choice for you. This comprehensive program will help you master top platforms like AWS, Microsoft Azure and Google Cloud, equipping you with in- demand skills to design and deploy scalable cloud solutions. You will gain access to official AWS author learning content, hands-on project, and even a Microsoft exam voucher for an Azure certification. And over four months, you will dive into 40 plus industry relevant skills including cloud architecture principles, AI, DevOps, and more with live interactive classes led by experts. Cloud computing is booming with 98% of companies already adopting it, creating a huge demand for skilled professionals. So guys, hurry up and enroll now and you can find the course link below. >> Imagine you're the owner of a small software development firm and you want to scale your business up. However, a small team size, the unpredictability of demand, and limited resources are roadblocks for this expansion. That's when you hear about cloud computing. But before investing money into it, you decide to draw up the differences between onremise and cloud-based computing to make a better decision. When it comes to scalability, you pay more for an on-remise setup and get lesser options, too. Once you've scaled up, it is difficult to scale down and often leads to heavy losses in terms of infrastructure and maintenance costs. Cloud computing, on the other hand, allows you to pay only for how much you use with much easier and faster provisions for scaling up or down. Next, let's talk about server storage. on premise systems need a lot of space for their servers not withstanding the power and maintenance hassles that come with them. On the other hand, cloud computing solutions are offered by cloud service providers who manage and maintain the servers saving you both money and space. Then we have data security. On-remise systems offer less data security thanks to a complicated combination of physical and traditional IT security measures. Whereas cloud computing systems offer much better security and let you avoid having to constantly monitor and manage security protocols. In the event that a data loss does occur, the chance for data recovery with on-remise setups are very small. In contrast, cloud computing systems have robust disaster recovery measures in place to ensure faster and easier data recovery. Finally, we have maintenance. On premises systems also require additional teams for hardware and software maintenance, loading up the costs by a considerable degree. Cloud computing systems, on the other hand, are maintained by the cloud service providers, reducing your costs and resource allocation substantially. So now thinking that cloud computing is a better option, you decide to take a closer look at what exactly cloud computing is. Cloud computing refers to the delivery of ondemand computing services over the internet on a pay as you go basis. In simpler words, rather than managing files and services on a local storage device, you'll be doing the same over the internet in a costefficient manner. Cloud computing has two types of models, deployment model and service model. There are three types of deployment models: public, private, and hybrid cloud. Imagine you're traveling to work. You've got three options to choose from. One, you have buses, which represent public clouds. In this case, the cloud infrastructure is available to the public over the internet. These are owned by cloud service providers. Two, then you have the option of using your own car. This represents the private cloud. With the private cloud, the cloud infrastructure is exclusively operated by a single organization. This can be managed by the organization or a third party. And finally, you have the option to hell a cab. This represents the hybrid cloud. A hybrid cloud is a combination of the functionalities of both public and private clouds. Next, let's have a look at the service models. There are three major service models available. EAS, pass and SAS. Compared to on-remise models where you'll need to manage and maintain every component including applications, data, virtualization, and middleware, cloud computing service models are hassle-free. Refers to infrastructure as a service. It is a cloud service model where users get access to basic computing infrastructure. They are commonly used by IT administrators. If your organization requires resources like storage or virtual machines, is the model for you. You only have to manage the data, runtime, middleware, applications, and the OS while the rest is handled by the cloud providers. Next, we have pass. Pass or platform as a service provides cloud platforms and runtime environments for developing, testing, and managing applications. This service model enables users to deploy applications without the need to acquire, manage, and maintain the related architecture. If your organization is in need of a platform for creating software applications, PASS is the model for you. PASS only requires you to handle the applications and the data. The rest of the components like runtime, middleware, operating systems, servers, storage and others are handled by the cloud service providers. And finally, we have SAS. SAS or software as a service involves cloud services for hosting and managing your software applications. software and hardware requirements are satisfied by the vendors, so you don't have to manage any of those aspects of the solution. If you'd rather not worry about the hassles of owning any IT equipment, the SAS model would be the one to go with. With SAS, the cloud service provider handles all components of the solution required by the organization. Time for a quiz now. In which of the following deployment models are you as the business responsible for the application, data, and operating system? One is two pass three SAS. Four is and pass. Let us know your answer in the comment section below. >> Back in the 2000s, organizations were utterly dependent on purchase servers for their IT infrastructure. These servers not only came with limited functionality, but were also very expensive. The traditional way of storing and managing data was costly and complicated. It required a massive amount of hardware and complex software to run. All these issues were resolved using cloud computing. Rather than owning their computing infrastructures, organizations were able to scale up or scale down resources based on the requirement. Companies providing these computing services are called as cloud providers. According to Corner, the two popular cloud providers in the cloud market are Amazon AWS and Microsoft Azure. Now let's take a step back and talk about a question. What should an individual learn in the year 2021? Amazon Web Services or Microsoft Azure. Though this question is tricky, we need to understand which cloud provider is the best option to choose. Now let's take a brief look at both of these cloud providers. Amazon Web Services is an evolving cloud computing platform that offers various services such as compute power, storage, database, content delivery, and other resources to help business scale and grow. AWS services are provided based on a subscription basis. Similarly, Microsoft Azure provides a set of cloud services to design, create, and monitor applications on a network. Talking about the general features, Amazon Web Services was established in the year 2006. Today it holds a market share of 31.7%. Whereas Microsoft Azure was started in the year 2010 and now has a market share up to 16.8%. Amazon AWS is the world's most broadly adopted cloud platform. It offers up to 165 services globally. These services are used by millions of companies like Spotify, Netflix, Facebook, BBC, etc. Talking about Netflix, the company moved its IT operations to AWS in the year 2009. AWS was able to solve the company's scalability and data management issues. Azure offers several services in various categories including artificial intelligence, analytics, containers, IoT and many more. These services are used by many famous companies like Accenture, LinkedIn, Stack, eBay and Samsung. Accenture chose Microsoft Azure to boost productivity and provide better security to its employees. The AWS pricing model is based on an hourly basis. With AWS, every individual pays only for the services that are required for his work. Every person only pays for the services he consumes. Azure pricing is charged on a per minute basis. The payment system is very simple and doesn't involve any long-term contracts. Microsoft Azure is free of upfront costs and cancellation fees and only users pay for the resources they consume. With Azure and Amazon AWS, there are no additional costs or termination fees. Moving on to the next factor, let's talk about availability zones. Availability zones are isolated data centers with independent power and networking. These zones protect applications and files from data center failures. In total, AWS has nearly 77 availability zones within 24 geographic regions around the world. The company plans to establish nine more AWS availability zones and three more AWS regions in Indonesia, Japan, and Spain. On the other hand, Microsoft Azure has many isolated availability zones. These zones are located within an Azure region and they provide fast network connectivity. Azure has 44 availability zones around the world. The company is planning to launch 12 more zones. Now, after discussing the availability zones, let's talk about the services. The services that I am going to compare here come under the following domains. Compute, storage, database, security and finally networking. AWS and Azure provide a wide variety of services with low migration cost so that every individual can shift his or her current traditional infrastructure to cloud platform very easily. AWS EC2 is a suitable example of compute services. EC2 is a web service that aims to make life easier for developers by providing secure and resizable compute capacity in the cloud. It can be integrated to several other services like S3 AM cloud formation etc. Azure has a small service called Azure virtual machine image. It helps the developers to develop and design identical virtual machines in the matter of minutes. Azure virtual machines are becoming more popular among IT infrastructures. These machines let an individual create and use virtual machines in the cloud as I or infrastructure as a service. Virtual machines can be created using Azure portal, Azure PowerShell and ARM templates. Azure CLI or client software development kits. Next comes Amazon S3. It is the best example for storage service. Simple storage service is an object storage service designed to store and recover any information from anywhere via the internet. Amazon S3 facilitates storage through a web service interface. The service provides 99.9% durability and 99.9% availability of objects. It has the capacity of storing computer files up to 5 terabytes in size. On the other hand, Azure provides a similar service called blob storage service. This service provides a large amount of storage and is highly scalable. It stores an object in the tires depending on how often the data is being accessed. Blob storage supports widely used frameworks like Java,Net, Python and NodeJS. It is the only cloud storage service in Microsoft Azure that offers a premium SSDbased object storage tire for low latency networks. AWS provides a secure cloud platform where every individual can manage and deploy their applications. Compared to the on- premises environment, AWS security offers a high level of data protection at a lower cost. For security purposes, AM is a suitable service. AWS identity and access management is a cloud service that controls and manages AWS resources securely. It has no upfront cost also gives a facility to create and maintain services within a specific set of users on your AWS resources. In Microsoft Azure, Azure Active Directory or in short also called as Azure AD is a web service which provides MFA multiffactor authentication features to users in order to protect their data from cyber attacks. Next is Amazon RDS. It is a web service designed to simplify the setup operation and scaling of a relational database. It is simple to set up, use and scale when required by users. It provides inexpensive and resizable capacity and automates several tasks such as hardware provisioning, database setup, patching, and backups. On the other side, the Azure SQL database automatically updates and backups data in order to focus on the development of applications. Not just that, it also manages database services and response to client requirements. Client requirements such as scalability of a service, data backup and high availability of database. Similarly, these cloud providers have plenty of services that help users build and deploy their applications effectively. Moving on to the next topic, let us focus on integrating AWS and Azure with open source tools. Now we will explain how to build a pipeline using genkins along with one of the services of Amazon web services that is the EC2. In this integration process, we have a sample Python application called as a docker file. This docker file will consist of a Python base image. The docker file builds a pipeline in order to create a docker image. Upon pushing the code to the repository, later the new image is used to start a new AWS service on an ECS cluster. Now let's have a look at how the integration of opensource tools happen in Azure. In your Azure cloud application, DevOps tools like Docker, Maven, and Genkins can be integrated. In case you want to integrate the Genkins pipeline, go to project and create a subscription followed by Genkins. You can specify the required filters based on your requirement. Then choose your endpoint for Azure DevOps to communicate with Genkins. So that was all about Amazon AWS and Microsoft Azure. Both AWS and Azure are honored to be on top of all other cloud providers. Both provide all necessary features like scalability, high availability and security. But the moment I hear about choosing the best one, I have to say that all that depends upon the individual business needs. Both cloud providers are the certified ones that hold immense value in the current cloud service market. Hi there. Let me take the pleasure of welcome you to this Azure tutorial. I'm Sam, an Azure cloud architect working for Simply Learn and I'm more than glad to walk you through this session where we're going to talk about Azure in great length and breadth. And if you're looking for a video that talks and walks you through all the services in Azure, then this could be one of the best video you could find in the internet. And without any further delay, let's get started. Everybody likes stories it. So let's get started with a story. In a city not so far away, a CEO had plans to expand his company globally and called one of his IT personnel for an IT opinion. And this guy has been in the company for a long time and is very seasoned with the company's uh infra and he nicely answered the questions with what he foresaw and he said I have a good news and a bad news for us to go global and he starts with the good news. He said, "Sir, we're well on our way to become one of the world's largest shipping company." And the bad news is, however, our data centers have almost run out of space and setting up new ones around the world would be too expensive and very timeconuming. Now, the IT personnel, let's call him Mike, now he explains the situation from how he saw it. But the CEO had done some homework about how he was going to do it and he answered Mike saying, "Don't worry about that, Mike. I've come up with a solution for a problem and it's called Microsoft Azure." Well, Mike is an hardworking and honest IT professional working for that company, but he did not spend time on learning the latest technologies. And he asked this question very honestly. Oh, how does it solve a problem? And the CEO begins to explain Azure to Mike and he starts with what is cloud computing and then he goes on and talks about Azure and the services offered by Azure and why Azure is better than the other cloud providers and what are the great companies that uses Azure and how they got benefited out of it and then he winds it all up with the use cases of Azure. So he begins his explanation saying Microsoft Azure is known as the cloud service provider and it works on the basis of cloud computing. Now Microsoft Azure is formerly known as Windows Azure and it's uh Microsoft's public cloud computing platform. It also provides a range of cloud services including some of them are compute analytics storage and networking. We can always pick and choose from these services to develop and scale our applications or even plan on running existing applications in the public cloud. Microsoft Azure is both a platform as a service and infrastructure as a service. Let's now fit their conversation out and let's talk about what is cloud computing Azure services offered by Azure. How is Azure leading when compared to other cloud service providers and what are the companies that are using Azure? Let's talk about that. In simple terms, cloud computing is being able to access compute services like servers, storage, database, networking, software analytics, intelligence and lot more over the internet which is the cloud. with the uh flexibility of the resources that we use like anytime I want a resource I can use one and it becomes available immediately and anytime if I want to retire an resource I can simply retire a resource and not pay for it and we also typically pay only for the services that we use and this helps greatly with our operating cost to run our infrastructure more efficiently and scale our environment up or down depending on the business needs and changes. And all the servers and stoages and databases and networking all that are accessed through the network of remote systems or remote computers hosted in the internet typically in the provider's data center which is Azure in this case. Now we don't use any physical server or an onremises server here. Well, we still use physical servers and VMs, you know, hosted on a hardware or a physical server, but they're all in the provider environment and none of them sit on premises or in our data center. We only access them remotely. It looks and feels the same except for the fact that they are in a remote location. We access them remotely, do all the work remotely, and when we're done, we can shut it down and not pay for them. So some of the use cases some of the use cases of cloud computing are creating applications and services. The other use cases are storing or using cloud for storage alone. If there is one thing that ever grows in an organization is the storage. Every new day there is a new storage requirement and it's very dynamic. It's very hard to predict and if we go out and buy a big storage capacity up front until we use the storage capacity fully the empty stoages you know we're wasting money on them so instead I can go for a storage which scales dynamically that's in the cloud put storage or put data in the cloud and pay only for what you are storing and for the next month if you have deleted or flushed out some files or data pay less for it. So it's a very dynamic storage in the cloud and a lot of companies are getting benefited from storing data in the cloud because of its u dynamic in nature and the cost that comes along with it the cheap cost that comes along with it and also they give a lot of the providers like Azure they give data replication for free they promise an SLA along with the data we store in the cloud so there's an SLA attached to it and they also O provide data recoveries as well. If in case something goes wrong with the physical disk where our data is stored, Azure automatically makes our data available from the redundant or other places where it had stored our data because of the SLA they wanted to keep. The other use case for Azure is hosting websites and running blogs using the compute service. Be it storing music and letting your users stream the music, Azure is a good place to store music and stream the music with the benefit of CDN content delivery network which allows us to stream video or audio files with great speed. You know with that with Azure our audio or video application works seamlessly because they are provided to the client with very low latency and that improves the customer experience for our application. Azure comput service is a good place for delivering software on demand. There are a lot of softwares embedded softwares that we can buy using Azure and everything on a pay as you go service model. So anytime we need a software, we can go out and immediately buy the software for the next 1 hour or 2 hour let's say and use them and then return it back. We're not bound to any yearly licensing cost by that. Azure computing services has analytic available for us with which we can analyze get a good visualization of what's going on in a network be logs be the performance be the metrics you know instead of looking at logs and searching logs and trying to do manual things over the heaps and heaps of logs that we have saved Azure Analytics Services helps us to get a good visual of What's going on in the network? Where have we dropped? Where have we increased or what's causing what's the major driver? What is the top 10 errors that we get in the server in the application? Stuff like that. Those can be easily gathered from the Azure analytic services. Now cloud is really a very cool term for the internet. A good uh analogy would be looking back. Anytime we look at a diagram when we do not know how things are transferred, we simply draw a cloud. Right? For example, a mail gets sent from a person in one country to a person in the other country. A lot of things happening in between from the time you hit the send button and the time the other person hits the read button. Right? And we the simple and the easiest way of putting it in a picture is simply draw a cloud and on the one end one person will be sending the email and on the other end the other person will be reading the email. So a cloud is a really cool term for the internet. Now that's some basics about cloud computing. Now that we've understood about cloud computing in general, let's talk about Microsoft Azure as a cloud service. Now, Microsoft Azure is a set of cloud services to build, manage, and deploy applications on a network with the help of Microsoft Azure's frameworks. Now, Microsoft Azure is a computing service created by Microsoft basically for building, testing, deploying, and managing applications and services through a global network of Microsoft managed data centers. Now, Microsoft Azure provides SAS which is software as a service and PAS which is platform as a service and IAS infrastructure as a service and they support many different programming languages tools and framework and those tools and framework include both Microsoft specific and third party software. Now let me pick and talk about a specific service for example management. Azure automation provides a way for us to automate the manual long running and frequently repeated task that are commonly performed task both in cloud and enterprise environment. It saves us a lot of time and increases the reliability and it kind of gives a good administrative control and even schedules the task automatically to be performed on a regular basis. To give you a quick history of Microsoft Azure, it was launched on 1st February 2010 and it was awarded or it was called an industry leader for infrastructure and platform as a service by Gartner. Now Gartner is the world's leading research and advisory company. This Microsoft Azure supports a number of programming languages like C, Java and Python. All these cool services we get to use and pay only for how much we use. For example, if we use for an hour, we only get to pay for an hour. Even the costliest system available. And if we use them for an hour, we only pay for that particular hour. And then we're done. No more billing on the resource that we have used. Microsoft Azure has spread itself more than 50 regions around the world. So it's quite easy for us to pick a region and you know start provisioning and running our applications probably from day one because the infrastructure and the tools and technologies needed to run our application are already available. All that we have to do is commit the code in that particular region or build an application and launch it in that particular region and they become live starting day one. Now because we have 50 regions around the world, we can very carefully design our environment to provide low latency services to our customers. All right? Instead of in traditional data center let's say you know customers will have to or their request will have to travel all the way around the globe to reach a data center which lives in the other side of the planet and this adds more latency to it and it is really not feasible to build a data center uh near each customer location because of the cost involved but with Azure it's possible. Azure already has data centers around the world and all that we have to do is just pick a data center, build an environment there. They're available starting day one. Number one, and also the cost is considerably saved because we are using a public cloud instead of an physical infrastructure to serve those customers from a very local location. And the services that Azure is offering is ever increasing. As of now, as we speak, we have like 200 plus services offered and uh they span through different domain or different platform or different technologies available within the Azure console portal. Now, we're going to talk about that later in this section. So, hold your breath till we talk about it. But for now, just know that we have like 200 plus services offered by Azure. Let's now talk about different services in Azure. Starting with artificial intelligence plus machine learning where we have a lot of tools and technologies. So the wide variety of services available in Azure includes artificial intelligence plus machine learning plus analytic services to get an or to give us a good visual of how the data or how the application is performing or the type of the category of data stored and to read from the logs. and variety of compute services, different VMs with different size and different operating systems, different containers available, different type of databases available, a lot of developer tools that are available for us and identity service to manage our users in the Azure cloud and those users can be integrated or federated with let's say Google, Facebook, you know, LinkedIn. So there are some external federation services they can be used to integrate with our identity system IOT's IoT services IoT tools and technologies available and management tools to manage the users you know creating identity is one and then managing them on top of it is a totally different thing and we have tools technologies to manage the uh users cool services for data migration data migration is now made simple tools and technologies available for mobile application uh development and I can plan my own network in the cloud with the networking services I can implement my own security both Azure provided and third party security services on Azure cloud that's now possible and lot of storage options available in the cloud so these are just a glimpse of the big list of services available in Azure cloud So that was a glimpse of what's available in the cloud. Let's talk about the services in a specific. Let's take compute for example. You know whenever we're building a new application or deploying existing ones. The Azure compute service provides the infrastructure we need to run and maintain our application. We can easily tap in the capacity that Azure cloud service has and we can scale our compute requirement on demand. We can also containerize our application. We have the option of choosing Windows or Linux v machine and take the advantage of the flexible options Azure provides for us to migrate our VMs to Azure and lot more. And these compute services also include a full-fledged identity solution meaning integration with active directory in the cloud or an on premises and lot more. Let's look at some of the services that this compute domain provides. Some of the services the compute domain provides are virtual machines. And this Azure virtual machines gives us the ability to develop and manage a virtual computer environment or a virtualized environment inside Azure's cloud environment that in a virtual private network. Now we will talk about virtual private network at a later point but as of now just uh know that there are a lot of services available in Azure compute service that we can get benefited from. We can always choose from a very wide range of uh compute options. For example, you know we have an option to choose the operating system. We have the option to choose whether the system should be in on premises or in the cloud or do we want to maintain the environment both in on premises and in the cloud. we have the option of choosing the operating system whether we want to use our own operating system with some software attached uh to it or do we want to go and buy the operating system from the cloud from Azure marketplace and these are just a few of the options available for us when we want to buy the compute environment and these compute environments are easily scalable meaning we can easily scale our VM instances from one instance to thousands thousands of virtual machines in a matter of minutes or simply put in a couple of button clicks and all these services are available on a pay for what we use model. Meaning there is no upfront cost. We use the service and then pay for the services that we have used. There's no literal long-term commitment when it comes to using virtual machines in the cloud. And these most of the services are built on a pay-per-minut billing basis. All right. And at no point because of the pay-per- minute billing model, at no point we will be overpaying for any of the services. That's that's attractive, isn't it? Now, let's talk about batch service. Now, batch service is always uh independent. Regardless of whether you choose Windows or Linux, it's going to run fairly well. And with batch servers we can take advantage of the uh environment's unique features and not only that in short the batch service helps us to manage the whole batch environment and also it helps to schedule the jobs. Now this Azure batch service is actually runs on a large scale parallel and high performance computing. Because of that batch jobs are highly efficient in Azure. And when we run batch services, this Azure batch creates a pool of computer nodes and uh installs the needed applications that we want to run and then it schedules jobs to those individual nodes in those pools. As a customer, there is no need for us to install a cluster or there is no need for us to install a software that actually schedules the jobs or even to manage or even to scale those infrastructure or the uh software because everything is managed by Azure. And this batch service is a platform as a service. There is no additional charge for using this batch service except for I mean the only charges that we'll be paying is for the virtual machines that this service uses and uh the storage that we will be using of course and uh the networking services that we will be using for this batch service. Let's summarize this batch service. We have a choice of operating system that we can pick and use and it scales by itself. Now the alternative for the batch would be cues but in cues we'll have to pre-provision and pay for the infrastructure even if we're not using it but with a batch we only pay for what we use and this batch service helps us to manage uh the application manage the scheduleuling as a whole as if they are just one thing as next thing in compute domain let's talk about this fabric service now this fabric service is actually a distributed system platform that helps us to package, deploy and manage a scalable and a very reliable micros service and containers. And what does it help? This Azure fabric service helps us or it helps the developers and administrators so they can avoid the complex infrastructure problems and they can focus only on implementing workloads or taking care of their development taking care of their application instead of spending time on infrastructure. So what's service fabric? service fabric. It provides runtime capabilities and uh life cycle management to applications that are composed of microservices. No infrastructure management at all. And with service fabric we can easily scale the application to tens or hundreds or even to thousands of machines. Here machines represent containers. As next thing in compute domain let's talk about virtual machine scale set. Now this virtual machine scale set it lets us to create a group of identical load balanced VMs. I just want to mention it again. It helps us to manage a group identical and load balanced VMs. The number of instances or the number of VM instances in an in a scale set can increase or decrease in response to uh the demand or in response to a schedule that we define. You know the resources needed on a Monday morning is not the same as that would be required on a Saturday or a Sunday morning. All right. And even within the day the resources that would be needed in the beginning of the business hour is not the resources that would be needed at noon or you know after 8 or 9 in the evening. So the demands could actually vary in the environment and the skill set helps us to take care of the varying demand or take care of the uh different infrastructure requirement at a different schedule throughout the day throughout the week throughout the month or could be throughout the year as well. The scale set also allows us to provide high availability to our applications and it helps us to uh centrally manage configure and update a large number of VMs as if they they are just one thing. Now you might ask well virtual machines are enough. Why would we need a virtual machine scale set? Just like I said this virtual machine skill set helps us uh with uh a greater redundancy and improved performance for our applications and those applications can be accessed through a load balancer that actually distributes uh the requests to the application instances. So in a nutshell this virtual machine scale set it helps us to create a large number of identical virtual machines. number one and with scale set we can increase or decrease the virtual machines with virtual machine scale set we can centrally manage and configure and update a big group of VMs and it's a great use case when it comes to big data or container workloads as next thing in compute domain uh let's talk about cloud services now this Azure cloud service is actually a platform as a service and it's very friendly in fact it is designed for applications that support scalability or an application that requires scalability or reliability and and on top of it you want them to be very inexpensive to operate. So Azure cloud service provides all these. So where would this cloud service run? Well, it runs on a VM but it's a platform as a service. VMs are infrastructure as a service and when we run applications on VM through cloud service, it becomes platform as a service. So here is how you got to be thinking with infrastructure as a service like VMs. We first create and configure the environment and then we run applications on top of it. Let's look at the responsibility. The responsibility for us in VM is that we manage everything end to end like uh you know deploying new patches, picking the versions of the operating system and making sure they are uh intact and all that stuff. It's all managed by us. But on the contrary with platform as a service it's I mean it's as if the environment is already ready. All that you have to do is deploy your application in it and manage the platform. I mean manage the platform not as an administrator because all the administration is taken care by Azure like uh you know deploying new versions of the operating system. It's all handled by the Azure. So we deploy the application and we manage the application. That's it. infrastructure management is handled by Azure. So what does cloud service provide? This cloud service provides a platform uh where we can uh write the uh application code and we don't have to worry about hardware. Simply hand over the code and cloud service takes care of it. So no worry on the hardware at all. So responsibilities like patching, what do we do if something uh crashes, how do I update the infrastructure, how do I uh manage uh the maintenance or the downtime in the underlying infrastructure. All that is handled by Azure. It also provides an testing environment for us. You know, we can simply run the code, test it before it's actually released to the production. I want to expand a bit on these testing applications. So this Azure cloud service it actually gives us an staging environment for testing a new release without it affecting the existing release which actually reduces the customer downtime. So we can run the application, test it, and anytime that's ready for production. All that's needed for us to do to move it to production is simply to swap the staging environment into the production environment and the old production environment will now become the new staging environment where we can uh add more to it and then swap it back at a later point. So it it kind of gives us in swappable environment for testing our applications and not only that it gives us health monitoring alerts. It helps us to monitor the health and availability of our application. There is a dashboard we can benefit from uh when we use Azure cloud services and that shows the key statistics all in one place and we can also set up realtime alerts to warn when a service availability or a certain metrics that we are concerned about degrades as next thing in compute domain let's talk about functions now functions are serverless computing many time if you heard about Azure being serverless a lot of time they are referenced ing or the person who's talking to you is referencing to serverless uh computing or Azure functions which is a serverless computing service hosted on Microsoft Azure. The main motive of uh a function is to accelerate and simplify application development. Functions helps us to run code on demand without we need to pre-provision or manage any Azure infrastructure. So, Azure functions are script or u a piece of code that gets run in response to an event that you want to handle. So, in short, we can just write a code that you need for a problem at hand without actually worrying about the whole application or the infrastructure that will be running uh that code. And the best of all the best is when we use functions, we only pay for the time that our code runs. So what does functions provide or what does Azure functions provide? Azure functions allow users to build applications using serverless uh simple functions with a programming language of our choice. So the current programming languages that are supported is C, F, NodeJS, Java and PHP. So here we really don't have to worry about provisioning or uh maintaining servers. If a code requires more resource, yes, Azure functions handles or it provides the additional resources needed by the code. And the best part is we only pay for the amount of time the functions are running. Not the resources but the amount of time the function is running. As next thing and moving to the new domain, let's talk about the container domain in Azure. Now the container domain or the container service it allows us to quickly deploy a production ready Kubernetes or a docker swarm cluster. Now what's a container? A container is a standard unit of software that packages of code and all its dependencies. So the applications run quickly and reliably from one computing environment to another. It could be testing uh to staging to developing development environment to staging to production or from one production to another production or on premises uh to cloud or one cloud to another cloud vice versa. Now imagine we had an option not to worry about the VM and just focus on the application. Well, that's exactly what containers helps us achieve. So these container instances enable us to focus on applications and not worrying about managing VMs or not worrying about the learning the new tools required to manage the VMs or even the deployment and our applications that we create they run in a container and running in a container is what helps us to achieve all these not being able to manage or not needing to manage the virtual machines. So these containers uh they can be deployed into the cloud using a single command if you're using a command line interface and a couple of button clicks if we are using the Azure portal and these containers are kept uh lightweight but they are equally secure as virtual machines. Let's talk about container services. Next thing uh the container service or sometimes called as Azure Kubernetes service. It helps us to manage the containers. container is one thing and a service that's used to manage the container is another thing. Now this Kubernetes service or ACS it helps us to manage the containers. So let's expand on this a bit. So this Azure container service or ACS it it actually provides a way uh to simplify the creation, configuration and management of a cluster of virtual machines that are preconfigured to run containerized applications on top of them. and deploying them, deploying these containers might take like 15 to 20 minutes or deploying the virtual machines that run containers in it might take 15 to 20 minutes. And once they are provisioned, we can actually manage them by using simple SSH tunnel into them. And this ACS when it runs application, it runs applications from docker images. What does that mean? Docker images makes sure that the applications the container runs are fully portable. Images are portable and ACS also helps us to orchestrate the container environment. Not only that, it also helps us to ensure that these applications that we run in containers can be scaled to thousands or even tens of thousands of containers. So in a nutshell, managing an existing application into a container and running it using AKS or ACS is really easy or that's what it is all about to make the application management or migration easy. Now managing the containerbased architecture and we discussed that containers could be tens or even tens of thousands of containers. So managing them is made simple using this container services and even training of model using a large data set in a complex and resource intensive uh environment. This AKS helps us to simplify that uh environment. All right. As next thing in container domain, let's talk about container registry. We spoke about registry a little bit when we spoke about docker images. So container registry is a single place where we can store our images which are docker images when we use when we use uh containers it's it's docker images that we use for our image purposes. So these container images are a central registry that can be used to ease container development by easing the storage and management of container images. So there we can store all kind of images like u docker swarm or the images used in docker swarm are in kubernetes. Everything can be stored in container registry in Azure. Now anytime we store a container image it provides us an option for geo replication. What that means is that we can efficiently manage a single registry replicated across multiple regions. Now these georrelication it actually enables us to manage global deployments assuming we are having an environment that requires a global deployment. So it helps us to manage global deployments as one entity because we are georrelicating. We would be updating we would be editing one image and that image gets replicated throughout the global uh replication centers we would have set up and so just one editing would have actually edited the global images and those global images would have provisioned the global application. So one edit replication and then provisioning of the applications globalwide. And this replication also helps us to helps us network latency because you know anytime an application needs to deploy it does not have to rely on a single source which which can be reached only through high latency network. Because we have global replications around the world. Anytime the application wants to check back, it would check back uh the application which is in a very nearby location for the application itself. Global replication means that we are managing it as a single entity that's being replicated across the multiple regions in the globe. As next thing in a learning, let's talk about um Azure databases. Now this Azure databases are u rational in fact they have many flavors in them. Uh we're going to look at uh different uh flavors. No SQL NoSQL cache type of database that Azure offers. So we're going to learn one at a time or we're going to learn one by one. So this Azure SQL database is a relational database. In fact, it's a relational database as a service. It's managed by Azure. We don't get to do a lot of management in it. So it's a relational database as a service uh based on Microsoft uh SQL server database engine and this database is a high performance database. It is very reliable and uh it's very secure as well and this high reliability high performance and for this high security we really don't have to do anything. It comes along with it and uh it's managed by Azure. And there are two things that I definitely need to mention about Azure SQL database that is it's an intelligent service. Number one, it's fully managed by Azure. And it also has this one good thing which is it has built-in intelligence that learns app patterns and adapts to maximize performance and reliability and data protection of the application. That's something that's not found in uh many of the other cloud providers that I'm aware of. So I thought I'll mention it. So it uses built-in intelligence to learn about um the user's database patterns and helps improve performance and protection and migration or importing data is very easy when it comes to Azure SQL database. So it can be readily or immediately used for analytic reporting and u intelligent applications in Azure. As next thing let's talk about Azure Cosmod. Now, Azure Cosmodb is a database service that is for NoSQL type and uh it's it's created to provide low latency and uh an application that scales dynamically or that scales rapidly. Now, this Azure Cosmodb is an a globally distributed service and it's a multimodel database. This can be provisioned in a click of a button. That's all we got to do if we need to provision an Azure Cosmod in the Azure. It helps with scaling the database. Now we can elastically and independently scale throughput and storage across this database and in any of the Azure geographic regions. It provides a good throughput. It provides good latency. It provides good availability and um it provides or uh Azure promises a a comprehensive SLA that uh no other database can offer. That's the best part about Cosmod. So this Cosmod was built with global distribution in mind and it's built uh with the horizontal scale in mind and all this we can use by only paying for what we have used. And remember the difference between Azure Cosmodb and SQL database is that Azure Cosmod supports NoSQL whereas SQL doesn't. All right. Few other things about Azure Cosmodb is it allows users to use key value graph column family and document data. It also gives users a number of AP options like SQL, JavaScript, MongoDB and and few others that you might want to check in the document at at the time of reading. And the best part here is that all that we mentioned we get to use only by paying for the amount of storage and throughput that are required and the storage and the throughput can be elastically scaled based on the requirement of that R. All right, let's talk about um Reddis cache. Discussion about Azure database won't be complete without we talking about Reddis cache. Now Reddis cache is a a secure data cache. It's also called it's also sometimes called as messaging broker that provides high throughput and low latency access to data for the applications. Now Reddis cache is based on an a popular open-source caching product which is reddis sometimes called as radius cache. Now what's the use case? It's typically used to cache to improve the performance and scalability of a system that rely heavily on backend data stores. Now performance when we use ZIS cache is improved by temporarily copying the frequently accessed data to a fast storage located very close to the application. Now with Reddis cache, this fast storage is located in memory with Reddis cache instead of being loaded from the actual disk in the database itself. Now this Reddis cache can also be used as an in-memory data structure store. Not only that it can be used as an distributed non- relational database and a message broker. So there are variety of uh use cases for this radius cache. And by using radius cache the application performance is improved by taking advantage of the low latency and the high throughput performance that this reddis cache engine provides. So to summarize this radius cache when we use reddis cache data is stored in the memory instead of the disk to ensure that there is high throughput and low latency when the application needs to read the data. It provides various levels of scaling without any downtime or interference. Now this radius cache is actually backed by radus server and it supports u a string hashes linked list and various other data structures. Now let's talk about security and identity services. Now identity management in specific is a process of authenticating first and then authorizing using security principles. And not only that, identity management involves controlling information about those principal identities. You might ask now what's an principal identity? Now identity or principal identity are services, applications, users, groups and a lot more. The specialtity about uh this identity management is that it not only helps authenticate and authorize principles in cloud, it also helps authenticate and authorize principles or resources on premises especially when you run an hybrid cloud environment. So all these services and features that this identity management helps us to get additional level of validation like identity management can provide multiffactor authentication. It can provide access policies based on condition permit or deny based on condition. It can also monitor suspicious activity and not only that it can also report it. It can also help generate alerts for potential security issues and in a way to mitigate it can send us an alert so we can get involved and prevent and a security accident from happening. So let's talk more about identity management. So some of the services under security and identity management are Azure security center. Now this Azure security center provides security management and threat protection across the workloads in both cloud and in the hybrid environment. It helps control user access and application control to stop any malicious activity if present. It helps us to find and fix vulnerabilities before they can be even exploited. It integrates very well with analytic methods that helps us to identify or it gives us the intelligent to identify or detect attacks and prevent them before it can actually happen. And it also works seamlessly with hybrid environment. So you don't have to have one policy for on premises and one policy for the cloud. It's now a unified service both for on premises and the cloud. The next service in security and identity would be keywalt. Now a key wault is a service or a feature that help safeguard the cryptographic keys and any other secrets used by the cloud applications and the services. In other words, this Azure key wault is a tool for securely storing and accessing the secrets of the environment. I mean the secret keys. Now a secret is anything that you really want to have a very tight control access like the certificates like the passwords stuff like that. Now if I tell you what keywalt actually solves that would actually explain what keywalt is. Now key walt is used in secrets management. It helped in securely storing the tokens, the passwords, the certificates. It helps in key management. You know it really helps in creating and controlling the encryption keys that we would use to encrypt data. It helps in certificate management. Talking about certification management, it helps us to easily provision, manage and deploy public and private SSL TLS certificates in Azure and lot more. So in a nutshell, this key wall, it provides users the ability to provision new walls and keys in just a matter of minutes. All that in a single command or all that in a couple of button clicks. It also helps users to centrally manage their keys, secrets and policies. Next in the list, let's talk about Azure Active Directory. Now, Azure Active Directory, it helps us to create intelligent driven access policies to limit resource usage and manage user identities. What what does that mean? Now, this Azure Active Directory is a cloudbased active directory and identity management service. Now, Azure Active Directory combines, you know, it's actually a combination of the core directory services plus application access management plus identity protection. And one good thing about this Azure, in fact, there are a lot of good things, but especially when you're running hybrid environments, you might wonder well how this Azure Active Directory is going to behave. Now this Azure Active Directory is built to work on on premises and cloud environment as well. Not only that, it also works seamlessly with mobile applications as well. So in a nutshell, this Azure Active Directory, it acts as an central point of identity and access management for our cloud environment. It also provides good security solutions that protect against unauthorized access of our app and the data. Now that we've discussed about security and identity, let's talk about the management tools that Azure has to offer. Azure provides built-in management and account governance tools that helps administrators and developers that helps them to keep their resources secure and very compliant and again it helps both in on premises and in the cloud environment. And these management tools help us to monitor the infrastructure, monitor the applications. It also helps in provisioning and configuring resources. It also helps in updating apps. It helps in analyzing threats, taking backup of the resources, build uh disaster recoveries. It also helps in applying policies and conditions to automate our environment. we use u Azure management tools and it's also used in cost control methods. So this Azure management plays a wide role across the Azure services and in the management tools first comes the Azure advisor. Now this Azure advisor it acts as a guide to educate us about Azure best practices. It throws recommendations that we can select on the basis of the category of service and it also provides the impact it can have or the impact that would happen in our environment if we follow the recommendations given and recommendations are uh first one is the recommendations are kind of templatized and it throws um the templatized recommendations. Not only that, it also provides customized uh recommendations on the basis of the configuration, on the basis of our usage patterns. And these recommendations are not hard. It's not like something that it recommends and then just leaves us hanging there. These recommendations provided are very easy to follow, very easy to implement and see results. You can think of Azure advisor as an a very personalized cloud consultant that helps you to follow best practices to optimize our deployments. It kind of analyzes our resources, our configurations, our usage and then it recommends a solution for us that really helps in improving the cost effectiveness, improving the performance, improving high availability and improving security in our Azure environment. So with this Azure advisor, we can get a proactive, actionable and personalized best practice recommendations. Now you don't have to be an expert. Just follow the Azure advisor and your environment is going to be good. It also helps in improve the performance, security, high availability of our environment. And also it helps in bringing down the overall Azure spend. And the best part is it's a free service that analyzes our Azure usage and provides recommendations. How we can optimize our Azure resource to reduce cost and reduce cost at the same time boost the performance helps in strengthening the security and improve the overall reliability of our environment. And next in the list would be network watcher. Now this network watcher helps users identify and gain insights in the overall network performance and the health of the overall environment. Now these Azure watchers provides enough tools to monitor to diagnose to view the metrics and to enable or disable logs which means you know generate and collect the logs for resources in the Azure virtual network. So with network watcher can monitor and diagnose issues in networking without even logging into the virtual machines with just the logs which are real time we can actually come to a conclusion what could be wrong in a certain resource in a VM or in a database you know by just looking at the logs and not only that it's used for analytic or to gain some intelligence of what's happening in our network we can gain a lot of insight to the current network traffic pattern using the security group flow logs that this network watcher offers. It also helps in investigating VPN connectivity issues using detailed logs. Now you might or might not know that you know VPN troubleshooting requires both parties or it involves two parties. you know the person the network administrator on this side and the network administrator on the other side and they will have to check logs in their end and we'll have to check logs and our end stuff like that but with the network watcher it kind of takes it to the next level the logs itself we could easily identify which side is having the issue and suggest an appropriate fix and the next in the list would be Microsoft Azure portal now this Microsoft Azure portal it provides provides a single unified console to perform various number of activities like building not only building managing and monitoring the web applications that we build. Now this portal can be used to organize our environment or the appearance of the environment or the visual of the environment based on our work style. And using Azure portal, users can control who gets to manage or access the resources all from the Azure portal. And this Azure portal gives a very good visibility on the spends that happen on each resource, right? And if we can customize it, we can also identify spends based on team, spends based on days, spends based on department, stuff like that. So it kind of gives us a good visual of where the money is spending or where is the bill consumed within the Azure environment. Next in the list would be Azure resource manager. Now Azure resource manager enables us to manage the usage of the application resources. Now we use resource manager to deploy, monitor and manage solution resources as a group as if it's one single entity. Now the infrastructure of our application is typically made of various components which includes virtual machine storage virtual network web app database servers some other third party services that we might use in our environment and they are by nature separate services but with Azure resource manager we don't see them as different components or different entities instead we see them as related services in a group that supports an application. Now we kind of get the relation between them instead of you know letting them spread. Azure resource manager identifies the relation between them and helps us to visually see them all as one or single entity. Not only that, Azure resource manager helps or it ensures that the resources that we provision or deploy at a constant rate along with the other application. It also helps users to visually see their resources and how they are connected and that helps in managing the resources a lot better. Resource group also is used to control who can access the resources within the users's organization. Kind of gives you the fine grained control over who gets to access and who does not get access. And the last one in the management tools would be automation. And this automation gives us the ability to automate, configure and install upgrades across hybrid environments. It provides a cloud-based automation and configuration service. Not only that, this can be applied for non-asure environments as well which is on premises. So some of the automation we could do is process automation, update management automation, configuration features automation, stuff like that. And this Azure automation provides complete control during the deployment operation and also during the decommissioning of the workloads and resources. With automation we can actually automate uh time consuming or mundane or any task that's errorprone because of uh human errors those things can be automated. So irrespective of how many times you run it, it's going to run the same way and that really helps in reducing the overall time and also the overhead cost because a lot of the things are automated which means it's human error-free which means the application is not going to break and keep running for a longer time. With automation we can actually build a good inventory of operating system resources and configuration items all in one place with ease. And this really helps in tracking the changes and investigating the issue. Let's say something happened because we have automation because it's logging the configuration changes. It's easy to track, easy to identify, easy to identify what has changed lately that has broken the environment, go back and fix it or kind of roll it back. That solves the problem. And that actually summarizes the Azure management tools or management services. Now let's talk about the networking tools or the networking services available in Azure. There are variety of services especially networking services that Azure offers and I'm sure it's going to be an interesting one. Let's begin our discussion with content delivery network. Now the content delivery network in short CDN it allows us to perform secure and a very reliable content delivery. Not only that, it also helps in accelerating the delivery time or in other words reducing the delivery time also called as load times. It also helps in saving bandwidth and increases in responsiveness to the application. Let's expand on this. The content delivery network is actually a distributed network of servers that can efficiently deliver web content to users. Now, CDN's, we're going to use the word CDN here. CDN's store cacheed content on global edge servers, also called as uh POPS, point of presence locations that are very close to the end users. So, the latency is minimized. It's like taking a copy of the data or taking a multiple copy of the data and storing it in different parts of the world. and whoever is requesting it, the data gets delivered to them from a server which is very locally to them. So this CDN offers developers a global solution for rapidly delivering high bandwidth content to users by caching the content in a strategically placed location which is very near to them. So these content delivery networks it really helps in handling that's one advantage you get for content delivery network that's we can handle spikes and heavy loads very efficiently and we can also run analytic against the logs that gets generated in content delivery network which helps in gaining good insight on the workflow and what would be the future business need for that application and this just like a lot of other services. This is on a pay as you go type. So you use the resource first and then you only pay for what you have used. The next one in networking would be express route. Now express route is actually a circute or a link that provides an a direct private connection to Azure and because it's direct it gives low latency link to Azure. It gives good speed and reliability for the Azure data transfer. It could be on premises to Azure. So it gives very good speed. It gives increased reliability and low latency for that connection. Let's expand on this a bit. And now this express route is an service that actually provides an private connection between Microsoft data center and infrastructure in our premises or in a different collocation facility that we might have. Now these express routes uh do not go over the public internet and because they don't go over the public internet they offer a high security reliability and speed and low latency compared to the connections um which are in the internet because it's fast because it's reliable because it it has low latency it can be used as an extension of our existing data center. You know, users are not going to feel the difference whether they are accessing services from an on-remises or in the cloud environment because latency is minimized as much as possible. Users are really not going to see the difference. And because it's a private line and not an public internet line, it can be used to build hybrid applications without compromising a privacy or the performance. Now these virtual private cloud these express routes can be used for taking backups. If assume a backup going through the internet that would be a nightmare. If you use express route for backups that's going to be fast and imagine recovering a data through the internet from the cloud through the internet to the on- premises in a time of disaster. That would be the worst nightmare. So these express routes can be used not only to backup but also to recover the data because it provides good speed low latency. Recovering the data is going to be lot sooner. The next product or service we're going to discuss in networking is Azure DNS. Now Azure DNS allows us to host domain name in Azure and these domain names come with an exceptional performance and availability. Now, Azure DNS is used to set up and manage DNS zones and records for our domain name in the cloud. Now, this Azure DNS is a service for DNS just like the name says and it provides name resolution by using Azure's infrastructure and uh by using this domain, we can actually manage the DNS ourselves through the Azure portal with the same credential. Imagine having a DNS provider which does not even belong in our IT. Imagine that environment. You know, we would have a separate portal to manage the DNS environment. Now those are gone and now we can actually manage the DNS in the very same Azure portal where we use the rest of the other services. And this Azure DNS very much integrates with other DNS service providers. It uses a global network of name servers to provide fast response to DNS queries. And these domains are having additional availability compared to the other uh domain service providers availability promises. These are going to have more availability than the rest because most of the servers are maintained by Microsoft and it helps resolve sooner. It helps reyncing let's say a server fails. It kind of helps reyncing with the rest of the servers. So all the Microsoft's environment, all the Microsoft's global network of name servers kind of ensures that our domain names are resolved properly. Not only properly but also are available most of the time. Right. Next in the list in networking services is virtual network. I'm sure this is going to be very interesting and I'm sure you're going to like it. So this networking or virtual networking in Azure, it actually allows us to set up our own private cloud in the public cloud. It gives us an isolated and highly secure environment for our application. Let's expand on this. Now this Azure virtual network helps us to provision Azure virtual machines and uh it helps us to securely communicate with other on premises and internet networks. It also helps in controlling the traffic that flows through or flows in and out of this virtual network to other virtual networks and to the internet. Now this Azure virtual network sometimes called as VNET is actually a representation of our own network in the cloud. It's actually a logical isolation of the Azure cloud dedicated to our subscription. All our environments are provisioned in a VNET that is separate from another customer's VNET. That way we have that logical separation there. So this virtual network can also be used to provision VPNs in the cloud. So we can connect the uh cloud and the on premises uh infrastructure and lot more especially in a environment where we have hybrid environment surely we will be using virtual network because that's going to require a VPN for secure data transfer in and out of the cloud and in and out of the on premises environment. All right. So it kind of gives us an boundary for all the resources. So all the traffic between the Azure resources they kind of logically stay in between or logically stay within the Azure virtual network. And here we can design the network. It's given over to us. You know you can pick the IP, you can pick the routing, you can pick the subnet. You know, lot of freedom is given or I would say a lot of control on how the network is designed. It's not like something that's already cooked and we only get to use it. No, we can actually build the network from the scratch. We can pick the IP address that we like. We can pick, you know, which subnet needs to communicate with the other subnet, stuff like that. And like I said, if you are using hybrid environment, you definitely would be requiring a virtual network because it helps connect the on premises and the cloud in a secure fashion using VPN. The last product we're going to discuss in networking is a load balancer. This load balancer actually provides application a good availability and a good network performance. So how does it work? It actually works by load balancing the traffic to and from uh the virtual machine and the cloud resources. Not only that, it also load balances between uh cloud and cross premises virtual networks. With Azure load balancer, we can actually scale our application and create high availability for our services, which means our application will be available most of the time. If any of the server goes dead, the server does not get traffic. What happens if the server gets traffic? User is going to experience downtime. What happens if the server does not get traffic? User won't experience any downtime. The connection is shifted to an healthy service. So the user experiences uptime all the time. So this load balancer supports inbound and outbound scenarios and it provides low latency. It gives high throughput of the data transfer and we can actually scale up the flow of the TCP and UDP connections from hundreds to thousands to even millions because we have a load balancer now in between the user and the application. So how does it operate? This load balancer actually receives the traffic and it uh load balances the traffic to the backend pool of instances connected to it according to the rule and the help probe that we set. That's how it maintains high availability. So what does load balancer help? It helps in creation of high available scalable application in the cloud in minutes. It can be used to automatically scale the environment with the increasing application traffic. And one feature of load balancer is to check the health of the user's application instance and it removes or it stops sending the request to the unhealthy instance and kind of shifts that connection to the healthy instance. That way a user or a connection does not get stuck with an instance that's not healthy. That's all that you need to know about the networking services. Now let's talk about the storage services or the storage domain in Azure. Now Azure storage in general is a a Microsoft manage service providing cloud storage which basically is highly available, secure, durable, scalable and redundant because it's all managed by Azure. We don't get to manage a lot of it. And these Azure stoages are a group of storage services. They cater different needs. And the storage products include Azure blobs which is actually an object storage. It includes um Azure data lake. It includes Azure files as you see it. It includes Azure cures. It includes Azure tables and lot more. But let's start our discussion with Azure store simple. Azure store simple is an hybrid cloud storage solution that actually lowers the cost of storage to nearly 60% of how much you would be actually spending without using it. So, Azure Simple Storage or Store simple is an integrated storage solution that manages the storage task between on premises and the cloud storage. What I really like about Azure is that it's built around a hybrid environment in mind. There are a lot of other cloud providers that are there where running and hybrid environment is a big challenge. You know, it has some compatibility. you won't be able to find an hybrid or a on premises and cloud solution for your need stuff like that. But with Azure especially when it comes to storage a lot of the things that we're going to see it clearly is designed with hybrid environment in mind. All right. So let's come back and talk about store simple. So store simple is an very efficient cost effective and a very easily manageable SAN storage area networking solution in the cloud. I thought I'll throw in this information. And the reason why it got store simple is really because it uses store simple 8000 series devices which are used in Azure data center and this uh store simple or simple storage. It comes along with storage tearing to manage uh the stored data across the various storage media. So the current the very current data is actually stored in on premises on solid state drives and data that is used less frequently is stored in uh HDDs or hard disk drives and the data that requires archived or that needs to be archived very old data let's say less frequently used data candidate for archived they are actually pushed uh to the cloud. So you see how this storage sharing automatically happens in store simple. And one another cool feature of store simple is that it enables us to create an ondemand and scheduled backups of data and and then store the data locally or in the cloud. And these backups are actually taken in the form of incremental snapshot which means that they can be created and restored quickly. It's not a complete backup. It's an incremental backup. And these cloud snapshots they can be critically important when there is a disaster and when there is a disaster recovery scenario because these snapshots can be called in and they can be put on storage systems and then they become the actual data. So recovering is faster if you have proper scheduled backups or if you have frequent backups. And this storage simple it really helps in easing our backup mechanism which means it kind of eases our disaster recovery steps or procedures as well. So the store simple it can be used to automate data management, data migration, data movement, data taring across the enterprise both in cloud and on premises. It actually improves the compliance and accelerates the disaster recovery for our environment. And if there is one thing that's increasing every new day in our environment, that would be storage. And this store simple addresses that need. And we really don't have to pre-plan or or think in deep or having a proper storage because now we have a simple storage available in the cloud. And moreover, it's on a pay as you go type. So not much pre-planning on storage is needed. Yes, there would be a need but not as much as I would without the cloud or without the simple storage. And the next service under storage that we would like to discuss is the data lake store. This data lake store or storage it's a cost effective solution for big data analytics in specific. So let's expand this. So this data lake storage is an enterprisewide repository for big data analytic workload. Now that's the major service that's dependent on this data lake store. And this data lake enables us to capture data of any size of any type and of any injection speed and it kind of collects them in one single space or in one single place for operational efficiency. I mean operational efficiency and for analytic purpose. Hadoop in Azure is very dependent on this data lake storage and this uh data lake store is designed with performance for analytics in mind. So anytime you think of or anytime you're using analytic in the cloud or anytime you're using Hadoop in the cloud in Azure, we are definitely using or we will be to the most part or or the normal procedure or the right storage to pick would be data lake store in Azure. It's designed with security in mind. So anytime we use Azure storage we can be rest assured that we are using storage from within a data center which has or which was built with security in mind. So this data store also uses Azure blob storage behind the scenes for global scale durability and for performance. Let's talk about blob storage. Now blob storage provides large amount of storage and scalability. Now this blob storage is the object storage solution for Azure cloud. Let's expand a bit on blob storage. Azure blob storage is Microsoft offering for object storage. Now this blob storage is optimized for storing massive amount of unstructured data which could be text or binary data. It's designed and it's optimized for rapid reads. If I explain to you on what scenarios we would be using blob storage that might help you get a good understanding of what blob storage is. So it's help or its design as of now it's being used in many IT environments to serve images or documents directly to the browser. It helps in storing files for distributed access. A lot of fetchers can fetch data from Azure blob storage and it currently helping users stream video and audio. It's currently being used for writing log files. It's currently being used to store data as backup and restore at a later point in times of disaster recovery. It also is used as an archiving storage in lot of cloud IT environments. It's widely used in storing analytic data. Not only storing but also running analytic query against the data stored in it. So that's a wide use case for blob storage. Not only that, in addition to all that we mentioned, uh it also supports versioning. So anytime somebody updates an data, a new version gets created, which means at any point I can roll back as and when needed. And it provides a lot of flexibility on optimizing the users's storage need. It also supports uh taring of the data. So based on need when I actually explore I would find a lot of options I can pick from that uh you know suits to my unique storage environment or unique storage need and like I said it stores unstructured data and this unstructured data is available for customers through restbased object storage environment. The next product in storage service would be Q storage. Now Q storage provides durable cues for large volume cloud services. It's a very simple and a cost-effective durable messaging queue for large workloads. Let's expand this Q storage for a moment. Now this Q storage is a service for storing large amount of messages that can be accessed from anywhere in the world through HTTP and HTTPS calls. A single queue or a single cube message can be up to like 24 KB in size. And a single queue can contain millions of such 24 KB in size messages. And how much can it hold? It can hold up to the total capacity of the storage account itself. So that's kind of easy to translate how much would it hold. And this Azure Q storage, it provides an messaging solution between applications and components in the cloud. What does it help? It helps in designing an application for scale. It helps in decoupling the application. So you know it's not very dependent or sometimes it's not at all dependent on the other application because now we have a queue in between which kind of translates or which kind of connects or which kind of decouples both the environment. Now we have a queue in between both the environment can scale up or scale down independently. The next in the storage service would be file storage. Let's talk about file storage. Now these Azure files provide secure, simple and managed cloud file shares. Now with fileshare in the cloud, it actually extends the user servers on premises performance and capacity and lot of familiar tools for the cloud fileshare management can be used along with the file storage that we're talking about. So let's expand a bit on file storage. Now this Azure files or Azure file storage offers a fully managed file shares in the cloud that can be accessed via the uh SMB protocol server message block protocol. Now this Azure file shares can be mounted concurrently by cloud or in on premises deployments. Lot of operating systems are compatible with it. Windows are compatible, Linux is compatible, Mac OS is compatible. In in addition to all this being able to run on on premises and on the cloud or being able to access from on premises and on the cloud, it can also offer cache for caching uh the data and keeping it locally. So it's immediately available when needed. So that's some additional feature I would say that's some advanced feature that it offers compared to the other file shares available in the market. Let's talk about table storage. Let's talk about table storage. Now table storage is a NoSQL key value pair storage for quick deployments with large semistructured data sets. The difference between one important thing to note with table storage is that it has a flexible data schema and also it's highly available. Let's expand a bit on table storage. So anytime you want to pick a schemalless a NoSQL type table storage is the one we'll end up picking. It provides an key pair attribute storage with a schemalless design. This table storage is very fast and very cost effective for many of the applications and for the same amount of uh data. It's a lot cheaper when you compare it with the traditional SQL data or data storage. So some of the things that we can store in the table storage are of course they're going to be flexible data sheets uh such as uh user data for web application address books device information and other types of metadata for our service requirements and it can have any number of tables up to the capacity limit of the storage account. Now this is not possible with SQL. This is only possible with NoSQL especially with table storage in Azure. explanation of storage really concluded the length and breadth of the explanation this CEO was giving his uh IT personal but this IT personal is not done with it yet. He still has a question even after this lengthy discussion and his question was well there are a lot of other cloud providers available. What made you specifically choose Azure? I mean from the kind of question that he asked we can say that he is very curious and uh he definitely had asked an very thoughtful question. So his CEO went on and started to explain about the uh other capabilities of Azure or how it kind of outruns the rest of the cloud providers. So he started or uh he again started his discussion but from a different angle now. So he started to explain what are the capabilities or how Azure is better than uh the competitors. So he started with explaining the platform as a service capabilities and I'm going to tell you what the CEO told his ID person. So this platform as a service or in platform as a service the infrastructure management is completely taken care by uh Microsoft allowing users to focus completely on the innovation. No more infrastructure management responsibilities. Go and focus on innovation. That's that's a fancy way of saying it. When we buy platform as a service, that's what we get. We can contribute our time on innovation and not just maintaining the infrastructure. And u Azure especially is u net friendly. Azure supports net programming language and um it has or it is built or designed or it is optimized to work with old and new applications deployed using net programming framework. So if your application isnet most of the time you would end up picking Azure I mean if you try to compare most of the time you would end up picking Azure as your cloud service provider and the security offerings that Azure offers is it's designed based on the security development uh life cycle which is an industry-leading assurance process. When we buy services from Azure, it assures that uh the environment is designed based on security development life cycle. And like I mentioned many times in the past and I would like to mention it again, Azure has well thought about the hybrid environments which a lot of other cloud providers have failed. So it's very easy to set up an hybrid environment to migrate the data or not to migrate the data and still run a hybrid environment. They work seamlessly with the Azure because Azure provides seamless connection across on premises data centers and the public cloud. It also has a very gentle learning curve. If you look at the uh documentation, it's picture and the documentations are neat and clear. Would really it would encourage you to learn more. or it would encourage you to think and imagine and try easily get a grasp of how services work. So it has a very gentle learning curve. Azure allows the utilization of technologies that several business have used for years. So there is a big history behind it. It has a very gentle learning curve. the the certifications, the documentations, the stage bystage certification levels. It it's all very gentle learning curve which is generally missing in other cloud service providers. Now, this would really impress the CTOs or or people working in finance and budgeting. If an organization is already using Microsoft software, they can definitely go and avail or be bold and ask for a discount that can reduce the overall Azure spending. In other words, overall pricing of the Azure. So that's what helped or they are the information that helped the CEO pick Azure as his cloud service provider. And then this CEO goes on and talks about the different companies that are currently using Azure. And they are definitely using Azure for a reason like Pixar, Boeing, Samsung, EasyJet, Xerox, BMW, 3M. They are major multinational, multi-billion companies. They rely, run, operate their IT in Azure. And this CEO has a thought that his IT person is still not very convinced unless and until he shows him a visual of how easy things are in Azure. So he goes on and explains about a practical application of Azure which is what exactly I'm going to show you as well. All right, a quick project on building an Azure app using or building a net application in Azure web app and making it connect to an SQL database will solidify all the knowledge that we have gained so far. So this is what we're going to do. I have an Azure account open as you see logged in and everything is fresh here. Let me go to resource group. There's nothing in there. It's it's kind of fresh. Right, I'm logged in and this is what we're going to do. So, we're going to create an application like this, which is nothing but an to-do application, a to-do list application, which is going to run from the web app, get information from us, and save it in the database that's connected to it. So, you can already see it's a two-tier application, web and DB. All right, so let me go back to my Azure account. The first thing is to create an resource group. Let's give it an a meaningful name. Let's call it Azure Simply Learn. All right. And it's going to be a free trial. And the location, pick one that's nearest to you or, you know, wherever you want to launch your application. Now, for this use case, I'm going to pick central US and create. It's going to take a while to get created. There you go. It's created. It's called Azure Simply Learn. Now, what do we need? We need an web app and an a separate SQL database. Let's first get our web app running. So, go to app services and then click on add. It's not the web app plus SQL that we want. We want web app alone for this u example. So, let's create an web app. Uh give it a quick name. Let's call it um Azure Simply Learn. The subscription is free trial and I'm going to use my existing resource group. A resource group that we created some time back. It's going to run out of Windows and we're going to publish uh the code. All set. We can create it. All right. While this is running, uh let me create my uh database. Right? SQL database. Create a database. Give it a name. Let's call it Azure SimplyLearn DB. Put it in our existing resource group that we created. It's going to be a blank database. All right. And it's going to require some uh settings like the name of the server and the admin login, the password that goes along and in which location this is going to be created. The server name is going to be Azure SimplyLearn DB. That's the server name. And the admin login can be what can be the admin login name. Let's see. So let's call it simply learn. That's my admin login name. And let me pick a password. Click on create. So what have we done so far? We have created an web app and we have created an uh a database in the resource group that we have created. Right. So if I go to resource group, it's going to take some time before things show up. So if I go to my resource group, I only have one resource group as of now, Azure Simply Learn. And there I have a bunch of resources being created and it's still being created. Right? In the meantime, I have my application right here that's running out of uh or that's in Visual Studio as of now. Right. So once the infrastructure is set and ready in the Azure console, uh we're going to go back to Visual Studio, feed these inputs in the Visual Studio. So the code knows what the database is, the the credentials to log to the database, stuff like that. So we're going to feed those information in Visual Studio. By that we're actually feeding it into the application, and then we're going to run it from there. Deploying this application takes uh quite a while. We really got to be patient. All right. Now we have all the resources that we need for the application to run. Here is my uh database and here is my app service. There's one more thing we need to do that is um create an firewall exception rule. So one more thing needed is to create an firewall exception uh rule. Right? So the application is going to run from my local desktop and it's going to connect to the uh uh database, right? So let's add an exception rule by simply adding the client IP. It's going to pick my IP, the IP of the laptop I'm using as of now, and it's going to create an exception to access the database. So that's done. Now we can go back to our Visual Studio. I already have a couple of um apps running or a couple of uh configurations pushed from uh Visual Studio. I'm going to clean that up. If you're doing it for the first time, you you may not uh need to do this. All right. So, let's start from the scratch. This is very similar to uh how you would be doing in your environment. All right. So we're going to uh select an existing Azure app service. Now before that I have logged in as you can see I have logged in with my credential. So it's going to pull few things automatically from my Azure account. So in this case I'm going to use an existing Azure app. So select existing and then click on publish. All right. If you recall, these are the very same resources that we created a while back. All right, we have clicked on save and it's uh running kind of validating the code and it's going to come up with an URL. Now, initially the URL is uh not going to work because we haven't mapped the application to the database. That would be the next thing. All right. So, the app has been published and it's running from my uh web app. As of now, it's going to throw an error. Like you see, it's throwing an error. That's because we haven't mapped the app and the DB together. So let's do that. All right, let's do that. So let's go to server explorer. Uh this is where uh we're going to see our uh uh databases that we have created. Now let's quickly verify that. Go back to uh the resource group, right? Appropriate resource group which is right here. And uh here I have my uh database Azure SimplyLearn database. All right. It has some issues connecting uh to my uh database. Give me a quick moment. Let's fix it. All right. So we'll have to map the database into this application. All right. So let's go to the solution explorer. Click on publish and a page like this get shown. And from here uh we can go to configure. Here is our web app. All right. With all its uh credentials. Let's validate the connection number one. All right. And then click on next. This is my DB connection string, right? Which the app is going to use to connect to my DB. Now, if you recall, RDB was uh Azure uh simply learn DB and that's not being shown here. So, let's fix that, right? So, let's fix that. Click on configure and here uh let's put our uh DB servers uh URL. Now before that let's change this to SQL server. All right. And then in here uh put the DB's URL. So go back to Azure. Here is my DB or server's name. Put that here. Right. The username to connect to the server. That's right here. Put that in. And the password to connect to the server. Let's put that in. All right. It's trying to connect to our Azure portal or the Azure infrastructure. And here is my database. If you recall, it's Azure SLDB. That's the name of the database. Let's test the connection. Connection is good. Click on okay. So now it's showing up correctly. Azure simply learn DB. That's the name of uh the database that we created. Now it's configured. All right, let's modify the data connections. Right, let's map it to the appropriate database again. All right, so our name of the database is Azure SimplyLearn DB and then uh it's going to be SQL server. That's the data source. The uh username is simply learn and the password is what we have given in the beginning. All right, let's validate the connection. It's good. Click okay. Now we're all set and ready to publish our application again. Now the application knows how to connect uh to the database. We have educated it with the u the correct connection strings the DNS name the username and the password for the application to connect to the database. So, Visual Studio is building this project and once it is up and running, we'll be prompted with an URL uh to connect and anytime we put or we give inputs to the URL that's going to receive the input and save it in the database. All right. So, here is my uh to-do list app and uh I can start uh creating to-do list for myself. All right. So, I have the items already listed. U I can create an entry and these entries get stored in the u in the database. I can create another entry and I'll take the dog for a walk that's going to get stored. I can create another entry uh book tickets for uh scientific uh exhibition and that's going to receive and put that in the database. And that concludes our session. So through this session we saw how I can use Azure services to create web app and connect that to the DB instance and how those two services which are decoupled by default which are separate by default how I can you know use the connection strings to make connection between the app server and the database and be able to create an working app. I strongly believe you enjoyed me walking you through this session. So today's uh topic is Azure virtual network tutorial. Let's look into what's in it for you. So we will be covering why is Azure virtual network important. What is Azure virtual network is benefits of using the Azure virtual network. Components of Azure virtual network that includes the subnet routing network security group. why these components are required to be created in the virtual network and how to launch an instance uh within the Azure VNET or the virtual network and then we will be seeing one demo in which we'll create Azure virtual network subnets and network security groups. So first of all let's look into why is Azure virtual network important. So why Azure virtual network is required? So somewhere far away at an office a company was struggling with few challenges. The company got a bigger projects which lead to the following challenges that includes poor network connectivity. Time-consuming process in building network topologies could not divert network traffic to its destination on time. So these were a couple of challenges the company was facing. So the employees thought that what could be the possible solution to these challenges and then we require the Azure virtual network in that case. So first of all let's understand what is Azure virtual network is an Azure VNET or a virtual network represents your network or environment to run VMS and applications in the cloud. When it is created the services and virtual machines within the network interact securely with each over the internet. So virtual network you can consider it as a virtual cloud which is basically kind of a cloud space virtually assigned to the users or or to the organization which they can dedicatedly use for their purpose. So for example, if you have to create some uh instances or virtual machines onto the Azure cloud and you want to connect it with the on-pre servers for example uh then you might require the virtual network in that case. Let's assume that those instances that are created in the virtual network require the range of IP addresses that you want to allocate to them and that is something you can customize using the Azure virtual network. How do you want that the traffic should be routed to your instances in the virtual network? How the firewall securities should be applied? Everything the end user can control in the virtual network. So it seems like that you are working in your own data center. Ideally you would be working onto the Azure cloud using the virtual network. Now what are the advantages of using the Azure virtual network? So a couple of them are it provides an isolated environment for your application. So as I said that it feels like it seems like that you are working in your on-pre environment that means within your data center but ideally it is a virtual space that is allocated to you which is a kind of an isolated environment uh that is specifically designed for your task and the activities. A generally a subnet in a vinet can access the public internet by default. So we create a subnet inside the virtual network which can access the public internet. So there is a public network connectivity that is enabled in the virtual net so that a subnet which will be created in the vnet can be accessed. Traffic can be easily filtered from different resources. So you can have some uh control lists defined. You can have some security groups created and how do you want to allow the traffic onto the servers or the application that is something which you can control. It is a highly secure network and the security groups and the policies are basically implemented by the end user. So you can design how the security should be implemented. High network connectivity. So you have a higher bandwidth as compared to the normal internet connection you might be having in the data center. Compared to that you use the Azure network only which gives you the higher network connectivity. It builds sophisticated network topologies in a simple manner and which is easily manageable as well as uh there are less troubleshooting issues that we would encounter. Now what are the components of Azure virtual network? One of them is the subnets. Then you have routing. Then you have network security groups. Now what do we mean by subnets? The subnet is one of the major or a prime important component in the virtual network. So what you have to do is first obviously you would be creating a virtual network. Inside that you can create the subnets. Subnets you can consider it a logical partitioning a virtual partitioning inside the virtual network. Subnet lets user segment the virtual network into one or more sub networks. For example, let's assume that you're working in an organization and in the organization there are different departments. For every department, there should be some set of IP addresses that you want to allocate to the machines that the employees are using or all the department should be isolated. That means so they should have their own network ids and the network addresses allocated to their machines. And in that case what you would do is you would create the subnets and the subnet ids that would be allocated to those departments. These sub networks can be separated logically and each subnet consist of a server. So what you do is when you create a subnet you can uh you can create a server or an instance inside that subnet and how do you want to give an access to that instance depends on criteria or the requirement. Hence a subnet can further be divided into two parts. One as the public subnet and the other one as the private subnet. These are the naming conventions of the subnet. Then how do you want to give the internet connectivity depends on how the public subnet should be interacting with the internet. And for the private subnet as the name suggests that the internet is blocked. So that means it is completely isolated in the virtual network. The private instances though if you want that any instance created in the private subnet should have the internet connectivity or an access you can primarily go with the NAD gateways in that case which is a network address translation or kind of a translator which converts the private to public and vice versa and that would actually enable the internet connectivity to your subnets. Then in the public instances they can directly access the instance as the name suggests public instances that public subnets that means they have the direct internet connectivity. Next component is routing and uh the routing is primarily a routing rules you can say that are applied and those are actually applied to the routers only. So since on the cloud we cannot have a direct router access and hence using the routing as a component we can define some routing rules which are directly applied to the router in the infrastructure. It delivers the data by choosing a suitable path from source to destination for each subnet. Azure virtual network automatically routes traffic and creates a route table. When you create a virtual network automatically a route table is created and that basically is required to route the traffic and that can be used by every subnet. That doesn't mean that you only have to create a single route table in the virtual network. You can have multiple route tables also created which can be associated with different subnets as well. Then you have the network security groups. uh it is kind of a firewall that protects the virtual machine by limiting the network traffic. It restricts inbound and outbound network traffic depending upon the destination IP address port and the protocol. So it is basically um the network security group sits on the instances and u or virtual machines and they basically define that how the traffic should be reaching to the ports onto the virtual machines. So how do you want to open up the ports and for which IP addresses you want to open up the ports that is something the end user or the administrator has to specify or a design. So they act as a kind of a firewall rules only that protects the virtual machines. So how to launch an instance using Azure VNET? So first of all you have to create a virtual network. So virtual network act as a container for subnets. So first thing is that you would be creating a virtual network. Then you would be creating subnets which are considered as a subset within the virtual network. So cloud instances included in the subnet. So first vinets are created then the subnets are created and then you configure the properties in the security group. Have a look at this in detail. Now with respect to the virtual network what you need to do is you have to create a virtual network in the Azure cloud. Then you have to create subnets into each virtual network which is kind of a subset of a virtual network. So you can create one as a public subnet, the other one as a private subnet for example. Now you have to assign instances. So when you create an instance you have to specify that what is the virtual network for which virtual network you're creating an instance within that virtual network you have to select that on which particular subnet the instance should be created and then connect instance to a relevant network security group. So attach your network security group to the instances and based on the properties or the rules that are defined in the network security group that will be applied to the instances within the subnets. Finally, configure the properties in the network security and set the policies. As a result, you'll be able to launch your instance on Azure within the virtual network. Now we will be seeing one demo that how we can create Azure virtual network subnets and the network security group. So just be there uh to watch uh our demo on the Azure virtual network. In today's session, I would be showing how you can create the virtual networks onto the Azure and for that you require the credentials on Microsoft Azure. And here you can see on my screen that I have already logged in into the Azure console. Now what you need to do is uh in order to search virtual network you can type and search in the dashboard uh in the search bar uh with respect to the virtual networks and here you can find uh the virtual network and the gateways. So what you need to do is you just have to click on the virtual networks and then it will give you the options to add the components inside the virtual networks. So let me first uh open up uh the virtual network right now in theory we discussed that the virtual network comprises of multiple components and subcomponents. So primarily is that first you have to create a virtual network then you have to assign the IPv4 C block to the virtual network and then you create the subnets inside the network which is a subset of the virtual network. Along with that you define the routing rules and uh likewise you create the instances inside the subnets that will be part of the virtual networks. So that's what we are going to do uh in this demo. So I would be adding up a new virtual network. So you can see here there are already two virtual networks that have been added. One is the demo vinet which is by default. So when you created the Azure credentials the demo virtual network was already created by the Azure. so that it can provide you the default settings and then the test one has been created by me and uh that's the customized one or you can say a non-default virtual network. So I'll I'm going to add another wet and um would define the name to it. So let's wait for the details to appear. So here you have to define the virtual network to create. Uh obviously we will be going with the free trial only and then you have to create a resource group. So what is a resource group? It is primarily a collection of resources that share the same life cycle permissions and the policies. So if you have a resource group uh created, you can use it. Otherwise you can create a new resource group. So I already have one that is the demo one. I would be using that. In the instance details you have to specif the name of uh the virtual network. So these are certain uh parameters that you have to go with uh while defining the name. So let's say I put something like test vnet as uh the virtual network that I want to create and that is you have to select a region where you want to get that uh created. So these are the available regions that you can select. I would go with um US east uh east US only and then we have to define the IP addresses also. See, so in the IP addresses uh the C blocks are allocated to the virtual networks and that becomes a fixed IP address uh for that VNET. So what you can do is you can specify a range of IP addresses. Now whenever we talk about a virtual network and the IP addresses, we primarily focus on the private IPs only. So this is the private IP that we are actually uh talking about. So I can reserve some IP address C for our VNET and that is the range of 40.0.0.0/16 I'm going to reserve. So now we'll create one subnet and uh we'll name that subnet. So as we discussed that subnets are the subcomponents of uh the vnet. So here you can see we have already created one u subnet with the name public subnet. So likewise we can add another subnet also and uh let's name it to something like uh demo subnet right and uh the subnet should have the IP address range and that IP address range should be part of the VNET only in V8. Uh so same subnet address range you would be defining in the subnet as well. So that will be 40.0.1 or we can select 2.0 0/24. The rest of the things uh would be default. We are not attaching any route table as of now. So just click on okay. And here you can see that the subnet is created. Now once the subnet is created now we are going to create a virtual machine inside that subnet. And for that we'll go to the search bar and here we'll type virtual machines. Now we'll create a virtual machine in the same VNET that is the test VNET and inside the demo subnet so that our virtual machine gets the private IP address from uh the subnet that has been created in the VNET itself. So what you need to do is you have to open up the virtual machines. Click on add and here you should add a new virtual machine. So you should uh select the name of the virtual machine and uh the network details where we would be defining the VNET as well as the subnet where the virtual machine should be created. So in the subscription we'll go with the free trail and in the resource group we'll go with the demo that has already been created. We'll put a virtual machine name uh something like uh test uh VM and the rest of the things will be default. So we'll quickly skip the disk check also. Now in the networking we would be selecting the test VNET as a virtual network and in the subnet we would be selecting the demo subnet. So that is the recently one added in the test vet and we want that our virtual machine should be part of that subnet only. Now obviously since we are creating a virtual machine so it should be part of it should have the public IP also assigned since uh from the public network we need to access those virtual machines. So we'll keep it enabled right and the next uh would be the default settings that we are going to proceed with. So let's uh review all the configurations and then create your virtual machine. So here you can see that our virtual machine has been created. Validation has been passed and it takes couple of minutes to get that updated. So let's wait for a few more minutes so that our virtual machine is ready. And primarily what we want to look into is that our virtual machine is created in a correct vinet and it gets uh the private IP address from the subnet that has been part of the uh vinet uh which has been defined in the creation of a virtual machine. So let's wait for a couple of more minutes and uh we'll look into the status of the vet. Now you can see here our test virtual machine has been created. Now what we wanted to look into is that a virtual machine is created in a correct subnet or not and that is something which we can validate by checking the private IP address. So it got the private IP from the range of uh the IP address that we have specified in the subnet. Now in order to access uh this particular virtual machine you have to use the public IP since uh since uh we have to access it from the internet. So from the private IP this virtual machine will not be accessible. So that's the reason that when we created a virtual machine we allocated the public IP address also for this instance. So that is uh with respect to uh the virtual network and the demonstration on it and how we can create a VNET and the subcomponents of the VNET how they are associated or interlin with each other and that actually creates a kind of an isolated environment on the public cloud which gives you the understanding that you can work into u just like an on-prem environment. In this video, I will take you through what is Azure Active Directory followed by what is the difference between Windows AD and Azure AD. Then we will look into the services audience i.e. who uses these services and at last we will have a quick demo of Azure Active Directory. So let's get started with the video. First, what is Azure Active Directory? But before getting into the definition of Azure AD, let's have a real life example of Azure AD to understand it in a better way. There are a lot of pre-created applications that you can offer user access to using Azure AD. So Netflix is one of them. So here's the scenario. You want to share a Netflix account with a dozen people from your organization. Giving your Netflix username and password to everyone isn't safe. So how do you give them access? Here enters Azure AD. The Netflix application is available in the Azure AD gallery and can be added to your Azure AD tenant. This adds the application to your tenency and allows you to save your Netflix credentials in the secured credential store so that users can be assigned to it. The only people who have access are the ones you give it to. Unless they have their own account, you're essentially building a company white password vault. Then assigning people to the systems. They require access to so they can log in without knowing the username and password for those systems. All they need is the Azure AD account or password and Azure AD will handle the rest. So saying in technical terms, Azure Active Directory is a cloud-based identity and access management service from Microsoft that allows your employees to sign in and access resources such as Microsoft 365, the Azure portal, and thousands of other SAS apps and internal resources such as apps on your company's internet and network, as well as any cloud apps built by a company. Azure AD is required for sign in and identity protection in Microsoft online business services such as Microsoft 365 and Azure. If you sign up for any Microsoft online business, you'll be given access to Azure AD which includes all of the free services. But what makes Azure AD so different from Windows AD that it has become more popular among people from technical firm. What is Windows AD? Active Directory saves information about network objects and make it easier for administrator and users to find and use their information. It organizes directory information logically and hierarchically using a structured data store. But its supreme drawback is its layers. So let's have a look at its layers and its functioning. First is adds Windows active directory domain services. Active Directory domain services is an example of a directory service that provides mechanisms for storing directory data and making it available to network users and administrators. Second is ADFS active directory federation services. Federated identity and access management is made possible by active directory federation service with securely shares digital identity and entitlements right across security and corporate boundaries to provide customers, partners and suppliers with a streamlined user experience while accessing an organization's web- based applications. ADFS extends the ability to employ single sign on capability accessible within a single security or enterprise boundary to internet facing apps. Third is ADRMS active directory right management services. Microsoft's active directory rights management services safeguard sensitive documents and emails unlike traditional security methods like firewalls and ACL. ADRMS encryption and protection remain constant regardless of where a file goes or how it is transferred. But Azure Active Directory actually combine these layers and make the whole process more easier and hassle-free. Azure AD combines these layers into two layers. W A Windows Active Azure Directory and Windows Azure Access Control Service. Windows active Azure directory combines all the problems revolving around identification management and Windows Azure access control service takes care of federating all the services of an organization. So let's have an example. When an employee join the promises of an organization, the administrator guides them towards signing to particular services they use and then give access to it and the employees can access these services through the credentials like username and password. Now that we know what is Azure Active Directory and how it functions different from adds, let's have a look at the service audience of Azure Active Directory. Ashure AD is majorly intended to IT admins, app developers, and online subscribers. For IT admins, you can use Azure AD as an IT administrator to limit access to your apps and app resources based on your business needs. When accessing critical organizational resources, for example, you can utilize Azure AD to enforce multiffactor authentication. Finally, Azure Active Directory provides you with strong features to help you protect users identities and credentials while also meeting your access governance requirements. As an app developer, you may utilize Azure AD to add single sign on to your app using a standardbased method allowing it to function with the user's existing credentials. Also, Azure AD has APIs that may be used to create customized app experiences based on existing organizational data. For online subscribers, you're already using Azure AD as a subscriber. Each tenant of Microsoft 365, Office 365, Azure, and Dynamics CRM online is an Azure AD tenant by default. you may begin managing access to your connected clouds apps right away. So now that we know the basic concept of Azure AD, let's have a quick demo of it. So the first thing we need to do is login in our Azure ID account and then go to Azure Active Directory sector. Here you will see add option where you can add a user, group, enterprise application, app registration according to your choice and below that you can search for any tenant like for user or for any group. So right now it doesn't belongs to any group or there is no user with this name. Here you will get basic information like their name, what is their ID, what is the license, which groups they belong and what all devices they use. You can al have an access to their password as well. >> Imagine you are at the forefront of your company's shift to the cloud. They need a cloud expert and you see this as your chance to shine. By earning a Microsoft Azure certification, you can become that expert. With Azure certification, you are not just keeping up with the change, you are leading it. You know how to deploy virtual machines, secure data, and optimize resources. Your team relies on you and your boss notices your pivotal role in a smooth migration. This certification also boosts your career. Companies everywhere need as your certified professionals. Whether it's a promotion, a raise or new job offers, your opportunities expand. The journey itself is rewarding, connecting you with a vibrant community and keeping you ahead of tech trends. In other words, a Microsoft Azure certification does not just boost your skills, it transform you into a cloud hero essential to your company's success and your career growth. So what is a Microsoft Azure certification? Microsoft Azure certification encompasses a series of over a dozen credential designed for professional in cloud computing or those aspiring to enter the field. Azure is an approach that enables you to innovate rapidly by using cloudnative architectures with loosely coupled microservices, managed databases, AI, DevOps support and many others. So there are four levels of Microsoft Azure certification. fundamental level, associate level, expert level and specialy level. So the first one is fundamental level ideal for nontechnical individuals starting in cloud computing and cloud professional at the beginning of their career. The next is associate level certification best suited for candidates with a solid understanding of Azure basics. The third one is expert level certification designed for those with a strong cloud background including associate level certification and hands-on experience. The fourth one is specialty certification focus on specific areas such as Azure IoT developer speciality and Azure for SAP workloads. So now let's discuss why to pursue an Azure certification. So in the dynamic world of cloud computing, obtaining a certification in platform like Microsoft Azure is a strategic career move. So here are several reasons to pursue an Azure certification. The first one is industry recognition and credibility. The second one is alignment with industry trends. The third one is diverse career opportunities. The fourth one is increased employability and job security. The fifth one is career advancement and higher earning potential. So now move forward and discuss top Azure certification path as per the designation. As you can see this chart we have three type of levels in certification. Expert level, fundamental levels and associate level. So now let's discuss one by one. So first one is fundamentals level certification. So in this first we have Microsoft certified Azure fundamental A900. The course fundamentals is designed to teach you the foundational concept of Azure. Crafted by A900 certified expert, this course align perfectly with the Azure fundamental exam syllabus. The exam format is multiple choice questions. Exam duration is 45 minutes and the cost for this exam is $99. Please note that certification which we are discussing in this video might be discontinued in the future or the syllabus can be changed. And the second one in fundamentals is Microsoft certified Azure AI fundamentals AI 900. The AI 900 Microsoft Azure fundamental course is designed to help you learn machine learning and artificial intelligence. This certification is intended for you if you have both technical and nontechnical background. Data science and software engineering experience are not required. Exam format is MCQ and exam duration is 45 minutes. The cost for this exam is $99. Next we have associate level certification. So first one on the list is Microsoft certified Azure administrator associate a 10004. As an Azure administrator you often serve as a part of a larger team dedicated to implementing an organization's cloud infrastructure. You also coordinate with other roles to deliver Azure networking, security, database, application development and devops solution. The skill covered are managing Azure identities and governance, implementing and managing storage, configuring and managing virtual networking, deploying and managing Azure compute resources. Exam format is multiple choice questions and exam duration is 100 minute. The cost for this exam is $165. The second one we have AZ 500 as your security engineer associate. In this you implement, manage and monitor security for resources in Azure multicloud and hybrid environments as a part of an end to end infrastructure. You recommend security components and configuration to protect the following identity and access data application networks. Your responsibilities as an issur security engineer include managing the security posture, identifying and immediating vulnerabilities. Exam format is multiple choice question. Exam duration is 100 minutes and the cost for the exam is $165 US. The next we have a 204 as your developer associate. You are responsible for participating in all the phases of development including requirements gathering design development, deploying, security maintenance, performance tuning and monitoring. You should be proficient in Azure SDK, data storage options, data connection, APIs, app authentication and authorization. As a candidate, you should have at least two years of professional development experience and experience with Azure. Exam format is multiple choice question. Exam duration is 100 minutes and the cost for this exam is $165 US. The third one we have expert level certification. So the first one is we have Microsoft certified DevOps engineer expert A400. As a DevOps engineer you are developer or infrastructure administrator who also has subject matter expertise in working with people, processes and products to enable continuous delivery of value in organization. Your responsibilities for this role include delivering Microsoft DevOps solution that provide continuous security integration, testing, delivering, deployment, monitoring, and feedback. You must have experience both administrating and developing in Azure with a strong skills in at least one of these areas. You should also have experience implementing both GitHub and Azure DevOps solution. The exam format is multiple choice questions. Exam duration is 150 minutes and the cost for the exam is $165. The second one we have Microsoft Azure solution architect expert A305. The responsibility for this role include advising stakeholders and translating business requirement into design for Azure solution that align with the Azure well architected framework and cloud adoption framework for Azure. In this role, you implement solution on the Azure by partnering with various other job roles including developers, administrator, security engineer, data engineer. So as a candidate for this certification, you should have advanced experience and knowledge of IT operation including networking, virtualization, identity, security, business continuity, disaster recovery, data platform and governance. You should manage how decision in each areas affect an overall solution. Exam format is multiple choice question. Exam duration is 160 minutes and the cost for this exam is $165. So as we conclude our Azure certification road map, we have covered the significance of Azure certification and delve into the fundamentals associate and expert level. >> I would like to welcome you to this Azure interview preparation session. Knowing Azure is one thing. Having worked on Azure is another thing. And being able to answer interview questions in Azure is a totally different thing. Although one helps the other, it's still different skills. And our aim through this video is to prepare you with common product and scenario-based interview questions. So why wait? Let's get started. A common cloud interview question is what's the difference between SAS paz and I is we all know that a software as a service is thin client model of software provisioning where client in this case usually is simply a web browser providing the point of access to softwares running on the servers. Now SAS is the most familiar form of cloud service for customers. SAS moves the task of managing software and its deployment to third-party services meaning the vendor actually gets to manage all that. So uh SAS is software as a service involving applications being consumed and used by organization. So it's generally using an application and usually organizations pay for their use of this particular application. Now some examples of SAS would include Office 365. Salesforce is another very good example of SAS and a lot of uh Google apps and storage solutions like box and Dropbox are a very good example of software as a service. Talking about platform as a service or paz, it actually functions at the lower level than SAS. Now typically it provides a platform on which software can be developed and deployed. Now here we develop the software, we deploy the software. Now paz actually provides an abstract of much of the work dealing with servers and giving client and environment in which the operating system and the server software and the hardwares and the network are managed and taken care. In other words, with a platform as a service, all the things that I've mentioned like the servers, the server software, the hardware, everything is managed by the provider and we can focus on business side of the scalability and we can focus on application development of our product or the service. So in short, platform as a service is a service that enables developers to build and work with applications without even having to worry about the infrastructure or management of the underlying hosting environments. And some examples of pass and Azure is SQL and Azure storage. Talking about infrastructure as a service IAS. Now this is moving down the stack even further. Now we get to the fundamental building block of the cloud service which is infrastructure as a service IAS. Now IAS is fully of highly automated scalable computer resources. IAS is full of storage. IAS is full of the network capability. That's what I is. Now is clients have direct access to the servers and storage just as they would to do traditional servers. But in this case it's going to be in the cloud. In this case, it's going to be more scalable. So, IAS is very similar to what you would do in your on premises physical data center. But when we talk about IAS, we get to do everything, but it's stored in the cloud. So, if we need to build a definition around IAS, IAS or infrastructure as a service provides users with components. It provides components. It does not give us an built environment. It simply provides a component such as operating system uh networking capabilities and a lot more. Now this is a paid for based on the usage and can be used to host applications. In other words, this is pay as you go type. The more you use, the more you pay. The less you use, the less you pay. And some of the examples of IAS in Azure is virtual machine. That's a great example for IAS and V-Nets for networking. That's another good example for IAS in Azure. Another common question in Azure interview is what are the instant types offered by Azure. The main intention of this question is how well have you understood the different offerings in Azure and how well are you trained to pick the right offering for the right service. Now one size does not fit all and there of there are a lot of services in Azure that under the carpet it does the same thing but depending on how different your requirement is we'll have to pick the appropriate service. So this actually this question what are the different instant types offered by Azure it's to test how well have you used the product and services available in Azure and how well have you applied them for the given requirement. You shouldn't be provisioning more you shouldn't be provisioning less at the same time. So it's kind of matching the right service to the right requirement. So what are the instant types offered by Azure? As you see in the list, we have general purpose compute optimized, memory optimized, storage optimized, GPU virtual machines, and high performance compute virtual machines. Now answering just the names won't be enough in an interview. You'll have to go further and explain why and in what scenario you would use general purpose and what are the use cases, what type of servers is a good fit for a general purpose and what type is a good fit for computer optimized so on and so forth and that's exactly what we're going to do now. So the general purpose VMs you know they provide a balanced CPU to memory ratio and it's very good for testing very good for a development environment very good for small and medium databases and also for low to medium traffic web servers and some of the use cases are like we said test servers low traffic web servers small to medium databases some enterprisegrade applications it's also good for relational database it's also good for uh servers used for in-memory caching. It's also good for some small analytic uh database, very good for microservices. And if you're trying to build a proof of concept for an idea that you just have or just parked uh this is another good server for doing proof of concepts because you're not going to send actual traffic to it. I just want to show that you know your idea works. So general purpose server is a very good use case for those scenarios. And the largest instance size uh we can get in general purpose is standard D64 V3 uh which comes with 256 GB of memory and u 1600 GB of SSD temporary storage. On the other hand, compute optimized VMs have an a high CPU to memory ratio and are very good for medium traffic web servers, very good for batch processing servers, very good for application servers. Now, because it's computer optimized and compute means CPU, it's an excellent choice for workloads that demand faster CPU but does not need as much memory or temporary storage virtual CPU. Some of the workloads that run very well on computer optimized are analytic workloads. Uh gaming servers require more CPU. They run really well. Uh batch processing are some of the applications that can be placed in computer optimized. And by doing that we get the actual benefit of the computer optimized instance. And the largest instance size or the largest instance size type is standard F72's V2. And here we get uh 144 GB of memory and uh 576 GB of SSD temporary storage in compute optimized VMs. In the same lines, memory optimized to VM. They offer high memory to CPU ratio and that are great for databases. Databases require more memory. So it's a great fit for database and uh it's a great fit for medium to uh large scale caches applications that require in-memory analytics. So this memory optimized memory is more. So it's very good for in-memory analytics applications. And the largest instance size we get here is standard M1 128M. And look at the um gigabit of memory. It's uh 3892 GB of memory. And uh look at the uh temporary storage. It's uh 1,400 uh 3336 a GB of temporary storage on the same lines storage optimized. Now I guess I don't have to explain to you what storage optimized is used for. You might have easily guessed looking at the flow. Yes, storage optimized WM offer high disk throughput and IO and are very ideal for big data uh SQL NoSQL databases, data warehousing servers, large transactional databases and lot more. And some of the examples of the applications that can be launched on storage optimized are Cassandra, MongoDB, Cloudera, Reddius. These are some familiar applications that can get benefited when we run them on storage optimized. And one difference between storage optimized and the other servers are they are generally optimized to use the local disk on the node attached directly to the VM rather than using an durable disk which is actually an remote uh disk space. Now what does this allow? This allows for greater input outputs per second or uh throughput for the workload. So that's what we get a greater throughput a greater input outputs per second is what we get uh when we use storage optimized. And the largest instance size available in storage optimized is uh standard uh L32S and u uh the memory is 256 GB and look at the temporary storage it's 5630 GB of temporary storage GPU type VMs easy to guess uh GPU optimized VMs are specialized virtual machines available with uh multiple GPUs attached to them. Now these sizes are designed for or these WMs are designed for computer inensive graphic intensive visualization workloads that require a lot of um graphical processing unit attached to it. So in short these are virtual machines that specialize in heavy graphic rendering and video editing. It also helps with the model training and interferencing with the uh standard ND24 RS which has 448 GB of memory and 2948 GB of temporary storage. And the last but not the least but the best last but the best is higherformance uh compute or Azure H series virtual machines. Now they are the latest in high performance computing WMs and are aimed to handle workloads like batch processing, analytic, molecular modeling and fluid dynamics lot of complicated applications in this uh WM and this is the fastest and powerful CPU virtual machine with optional high throughput interfaces and the largest instance size that's available is a standard L32S which comes with 224 GB memory and 2000 GB of SSD temporary storage. And a third common question is what are the deployment environments offered by Azure. There are two main deployment environments. One is the staging environment and the other one is the production environment. Now in staging environment, let's talk about staging first. So when you're deploying your web app or web app on Linux, you can deploy them to a separate slot instead of the default production slot when running them in standard premium or isolated app service plan tiers. Now the deployment slots are actually live app with their own host name and at a later point the staging environment can be swapped with the production environment. So why do we need an staging environment? What are the benefit of it? So the benefit of uh deploying our application to a nonproduction or staging environment, it provides a platform to validate changes to our application before it can be made live in the production environment. And in the staging environment, the app can be identified using the Azure's global unique identifier also called as the GUID URL. And it's very very similar to the production URL except that it has an custom name in front of it that identifies it as the staging environment. And for production environment uh this is the live uh production environment that's serving customers request that's serving the customer content. Now it can be slightly different from the staging environment in a way that the URL that's used to identify the production environment that's more of an DNSfriendly name like the name of the actual servicecloudapp.net that way it differs in case of staging environment you have an custom name right before it. So the custom name and then the cloudapp.net net but in this case you get the uh direct service name as the name of the URL. So this is live production environment which receives and handles and serves customer traffic. Another commonly asked question in Azure is what are the advantages of scaling in Azure. The actual thought behind the question is to see how much have you understood scaling? How much have you seen and how much have you applied the scaling effect in the production environment and have received benefits in return. So let's talk about it. Advantages of scaling in Azure. Some of the advantages are we get uh the maximum application performance. Now autoscaling is a built-in feature for the cloud services be it um AWS, Azure, uh Google and couple of other cloud service providers. It's a built-in feature for a cloud service. A cloud service should be autoscalable and that includes mobile services, virtual machines and um when we run our applications uh on mobile services or virtual machines, the website actually gets the best performance uh during the change in the demand. Again, different applications uh might require different uh performance needs. For example, for some apps, the performance measured based on memory. And another good example is the fluctuating demand. For example, you could have a web app that handles millions of requests during the day and literally nothing at the night. And autoscaling this environment, autoscaling uh any of these environment will automatically scale or fatten your environment. So to receive the all the incoming traffic and during lean period, it actually gets slimmer and slimmer uh so to help you with the cost. So it actually maximizes uh the performance. That's what autoscaling does. And like we said, autoscaling scales up and scales down based on demand. It not only scales up but also scales down. So to help you with the cost and if you know the particular pattern in which the application is going to receive uh traffic then we can very well go ahead and schedule scaling to our application or schedule scaling that infrastructure based on time. If we already know that Monday to Friday that's the traffic uh that I would get and it's a constant one. It's not a public facing but you know it's an internal application. So I know all the 500 users or the thousand or the 5,000 users who will be using it. So at any given point it's just 5,000 users. It's not going to go beyond that. And during Saturday and Sunday literally nobody's going to be in office. So no load at all. So uh in that case I pretty much know how the pattern is going to be. I can go for scheduled scaling if I know the pattern. And autoscaling like I said not only helps with keeping the application highly available, it also helps with the cost effectiveness of our infrastructure. So anytime there's a VM or a group of VMs running on less CPU autoscaling is going to actually get the environment slimmer and slimmer. So we're not unnecessarily running any resources and paying for it. If you're being interviewed for the infra site in Azure, this is another common question that gets asked. How are Windows active directory and Azure Active Directory different? Let's talk about the Windows Active Directory first. The non-cloud Windows Active Directory was the service was released along with Windows 2000 server edition. And this active directory is essentially a database that helps organizations to organize the users, organize the computers and lot more. It provides authentication and authorization to the applications. Not only to the applications but also to file servers, to printers and lot of other onremises uh resources. That's what the basic non-cloud active directory does. On the other hand, the Azure Active Directory is not designed to manage web- based services. The Azure Active Directory, on the other hand, was designed to support web-based services that use REST API interfaces for Office 365, Salesforce.com, etc. Unlike the plain active directory, this uses an completely different protocol. So protocol-wise it's different and the services that it support is quite different. Now besides that it also has couple of other differences as well and let's look at them. So the actual active directory or the Windows actual directory is a directory service that facilitates working with interconnected complex and different network resources in a very unified manner. On the other hand, Azure Active Directory is Microsoft's multi-tenant cloud-based directory and identity management service. And the Windows Active Directory has five layers to store data to store user details and to issue the management certifications. On the other hand, Azure Active Directory integrates or compresses the five layers into just two layers. Here, Windows Active Directory works with on premises servers like applications, file servers, and printers, etc. On the other hand, Azure Active Directory, it uh works on web- based services that use restful interfaces. If you're being hired for the development environment or for the cloud DevOps support environment or even for the production support environment, you might find yourself being asked this question. What are the types of cues offered by Azure? Now, Azure supports two types of Q mechanisms. The storage Q and the service bus Q. Let's talk about storage Q first. Now, the storage Q which are part of Azure storage infrastructure. It provides a simple restbased uh interface. Simple restbased get, put and peak interface. It provides reliable persistent messaging within and between the services. It follows the pub sub model or a pub sub messaging infrastructure and it's best suited for users that need to store more than 80 GB of messages in the queue. It can provide a logs for all the transactions executed against the user's queue. So that's what we get with storage Q. And on the other hand, service bus Q. The service bus cues are built on top of broader messaging infrastructure and they are designed to integrate applications and applications component that can span multiple communication protocols. So that way it differs. So this is good for applications and components that may span multiple communication protocols and even different totally different network environments. So in short, these service buses or the service bus cues in Azure are part of Azure's messaging infrastructure and they uh integrate applications or application components that can actually span multiple different protocols and multiple different network environments. It also provides an first in first out style for delivery and the user's Q size has to remain under 80 GB. Another familiar question is what are the advantages of Azure resource manager? Now this resource manager helps us to manage uh the usage of the application resources. This question is actually to test how well have you tested how well have you used resource manager and have gotten the benefit of it. This question actually tests how easy it has become after the introduction of resource manager compared to uh when doing deployments or when provisioning resources without uh the resource manager. So let's get into the answers for the question. What are the advantages of Azure resource manager? The in short resource manager is called ARM. So the ARM helps deploy, manage and monitor all the resources for an application, a solution or a group. So all the interconnected application, all the interconnected services can be monitored as group using resource manager and uh a users can be granted to access to resources that they require within a resource manager. So in an account I can have like 10 different resources created by a resource manager or a resource group created by resource managers and I can allow deny connection to those services or only to those services based on whether the user should be accessing one and not accessing the other. So that way it becomes easy to give access to a group of application. It helps in getting billing details for the group of resources. which group is using more, which group is using less and which group has contributed more to this month's bill, stuff like that. So those details can be obtained using Azure Zos manager and provisioning resources is made much easier uh with the help of this resource manager. Another question is how has integrating hybrid cloud been useful for Azure? Well, with the use of hybrid cloud, we get the best of both the worlds. So what's hybrid cloud? It's nothing but combining the public cloud and the private cloud and allowing data and applications to be shared uh between them. So whenever the compute or the processing demand fluctuates, hybrid cloud computing gives businesses the ability to seamlessly scale their on- premises infrastructure in the public cloud and handle any kind of u uh overflow in the requirement or overflow in handling the application. So it really helps it helps it boost the productivity of our on premises application. So with the hybrid uh cloud we get a greater efficiency with combination of Azure services uh DevOps processes and tools for the application running in on premises and by having an hybrid cloud environment users can take advantage of a constantly updated Azure service and other AWS marketplace um applications for their on premises environment and the other benefit is uh with hybrid cloud environment we can simply deploy applications regardless of its locations. In case of on- premises, we'll have to worry about the location. But when we expand our on- premises environment in the cloud, they can or we can pick any of the locations and simply deploy it in them. And uh this enables the applications to be created at a greater speed. What's federating in Azure SQL? Now, this question is very specific about SQL. How can we scale the SQL database? Now this is a very good question or a valid question or an important question in the interview because many customers or companies have uh not been able to meet the user demand because they could not scale out uh the databases. Uh the theory of scaling out or adding servers to accommodate the increased workloads and traffic is not hard to understand but uh the implications can be very complicated. The implications can be very expensive. We're well aware of scaling the web service that's very common. But how do we scale the database? So Microsoft provides the tools and technologies so we can scale out the database in the cloud and that's what is called SQL or federation in Azure SQL. So the way we scale out the SQL database is by sharding sharding the database. So sharding actually enables users to take advantages of the resources in the cloud. Not only that, it allows users to have their own database or a shad database amongst the each other. Because we're creating an highly available database because we're having shards in a database, it actually reduces the possibility of a single point of failure for our database. And uh more importantly because we're shing uh because we're using federation and Azure SQL it provides an cost effective scaling of our databases by using cloud resources or by using billing only for the cloud resources that we have used. So no pre-provisioning no overprovisioning it provisions the right amount and we pay the right amount. Let's talk about this one. What are the different types of storage offered by Azure? Now the different types of storage offered by Azure are as you already know and as you can see they are Azure blob stoages, table stoages, file storage and Q storage. So let's expand one after the other. Now blob storage are nothing but a massive scalable object storage and that's very good for storing text and binary data. And Azure blob storage is u Microsoft's object storage solution for the cloud. blob storage is optimized for storing massive massive amount of unstructured data that can be in form of text or uh or in form of binary data. So in short blob storage enables users to store unstructured data and those data can be in the format of pictures, music, video files and lot more and it stores them along with their metadata. And another advantage or another feature benefit that we get from blob storage is when object is changed it is verified to ensure it is of the latest version number one and number two it provides maximum flexibility to optimize the users storage needs and this unstructured data is available to customers through an URL or an RESTbased object storage. So they are the benefits that come along with the blob storage. Table storage on the other hand is an a NoSQL store for schemalessless storage of secured data. Now this Azure table storage is a service that stores u structured nosql data in the cloud. And because this table is schemalless, it's very easy to save your data. It's very easy to adapt your uh data as the need for your application grows. And this table storage is very fast and cost effective for many type of applications. So some of the some of the type of data that we can store is u table storage is good for flexible databases like user data for web applications. Address book storage, device information storage and if you want to store metadata, this is a very good use case to store them in Azure table storage. Azure files is another storage. Uh here it's an file share for cloud or on premises uh deployment. So file storage provides a file sharing capabilities accessible by the server messaging block protocol and this can be accessed from the cloud and this can be accessed from on premises as well. Now here in file storage the data is protected by SMB uh 3.0 and HTTPS uh protocols and the more important thing is Azure takes care of managing hardware and the operating system deployments for Azure file storage. So this additional file storage can be used uh when we want to burst the storage capacity in on premises. So on premises the primary and cloud is the secondary or the extended on premises storage. So it actually improves the on-remises performance and capabilities for our on premises data center. And then we have cues Azure cues. It's a messaging store for reliable messaging between the application components. So we spoke a little about this uh in the previous question. So the Azure Q storage is a service for storing a large amount of messages that can be accessed from anywhere in the world via HTTP or HTTPS uh protocol. In here the uh a single message can be up to 64 kilobits in size and in a queue we can have millions of messages and the limit can actually go up if we have not uh reached the limit of the storage account. So it's millions and millions of requests that can be stored in the storage queue or the Q storage. So the Q storage in short uh provides message queuing for large workloads and it enables users to build flexible applications and separate the functions one from another. So one failing doesn't affect the other application which is running healthy and this cure storage it ensures the application is scalable and less prone to individual component uh failures because they are decoupled separate. Now it also helps in monitoring the queue which ensures the customer's demands are met. So Q is a great place to monitor or a great component to monitor so we understand how much peak he can be reached for a particular application service or a container. What is text analysis API in Azure machine learning. Now a text analysis is actually an cloudbased analytics API and it provides an advanced natural language processing over the raw text and it has got uh four main functions like the sentiment analysis or and the keyphrase analysis, language uh deduction and and few other things. Now what do you mean by sentiment analysis? Now sentiment analysis is from the logs from the comments from the text comments that we receive do an analysis and find out whether that's an positive or an negative statement. Now if it is the API the API returns an sentiment score between zero and one and one is positive and zero is negative and then in text analysis we have um a keyphrase extraction which is it will automatically extract the key phrase to uh quickly identify the main points in that uh keyphrase. For example, if you're analyzing an text which says the food was delicious and there were wonderful stuff, then uh the API returns the main talking points of that phrase like food. Food is the main talking point and wonderful stuffs that was a main talking point. So that's another feature that this uh text analysis has. And then we have language deduction in text analysis, right? irrespective of what you paste, it can try to gauge and try to align it to the 120 or up to 120 languages that it supports. So I can simply take text from the internet and I can paste it and text analysis software is going to identify the language and then can run phrase and sentiment analysis on those text. Right? So in short, text analysis is an API, a set of web services that can be used for text analysis. It can be used to analyze unstructured statement, sentiment analysis, keyphrase extraction and lot more. And the results are generally between zero and one and one being positive and zero being the negative sentiment. There is no much training or in other words, this is not as complicated as couple of other text analysis softwares are available in the market. We can simply paste, we can simply upload the text and we can call the service and it runs a sentiment analysis on it all by itself. Let's look at this question. What are the advantages of Azure Q storage? If you're going to work in a development environment, if you're going to work in an environment that embraces DevOps, this could be a question. What are the advantages of Azure Q storage? Now, Azure Q storage is built to flexibly operate the applications and separate the functions between the applications that run large workloads. So when we design applications for scale, these applications can be decoupled so that they can scale independently. you know a thing happening on an application is not dependent on another application and anything happens to an section of the application will not affect the other application because they are now decoupled and connected through the Q storage. So the Q storage gives us asynchronous message queuing for communication between the applications irrespective of whether they are running in the cloud or whether they are running in desktop or whether they are running on premises or on mobile devices. So in short this Q storage enables message queuing for large workloads in a simple and cost effective and a durable manner. Talking about the advantages advantages is it provides rich client libraries for Java, Android, C++, PHP, Ruby and lot other services getting added during every new release from Azure. And the main advantage again is it enables users to build flexible apps and uh separate the functions for bigger or greater durability. Again, introduction of cues into our application. It ensures our users applications are scalable and less prone to individual component failures. Meaning one component failing is not going to take the whole application down. Right? If one component fails, it's just that component that stays fails. the rest are healthy and the rest are going to function. It also helps us to monitor the cues and ensure the servers aren't overhelmed by sudden traffic burst. So how much do I have in the queue uh kind of determines uh the traffic for my application and if the queue is more I can always go and autoscale my environment and the queue is less I can always go and shrink or make my environment thinner so it can save cost and anytime there is more data in the queue I can autoscale monitor the metric and do autoscaling based on that metric. So the environment knows that there are more datas coming in. I need to expand myself to handle that much amount of data. This is a very common question. What are the two kinds of Azure web service roles? Now a service role is a set of managed and load balanced virtual machines that work to perform some task and based on what it's going to run on top of it. Is it going to run a web service or is it going to run a worker service? defines what kind of roles that gets attached or that goes on this virtual machines. So we have two types web role and worker roles. The web role is a cloud service role that's configured to run web applications developed on programming languages technologies and majorly they support internet information service and they support ASP.NET PHP uh Windows communication foundation and so on. So that's web roles and these web roles it automatically deploys and hosts application through the users's IIS internet uh information service. On the other hand, worker roles are roles that u runs applications and service level tasks which generally do not require IAS. So is actually the differentiating factor. So in worker roles is not installed by default. The worker roles are mainly used to perform supporting background process along with web roles and do tasks automatically compressing or uploading the images running scripts and um or doing some changes in the database getting new messages from the queue and processing and lot more you know the work the applications or the work that does not require IAS that's what this worker role does again the main difference between the web role and the worker role is that the web role automatically deploys and hosts your application through I is whereas the worker role does not use IA is and runs our application as standalone. This is another classic question. What is Azure service fabric? So Azure service fabric is actually an distributed system platform that makes it easy to pack, deploy and manage a scalable and reliable microservices and containers. Now, service fabric also addresses some of the significant challenges in developing and managing cloudnative applications. And the problem that it addresses and fixes is now developers and administrators can avoid complex infrastructure problems and focus on implementing mission critical and demanding workloads that can be scaled and that can be managed through the console or from the single place. In short, service fabric provides a platform that makes the process of developing microservices and managing application life cycle lot easier. And the advantages of service fabric is that now we can produce application with faster time to market because all the worry about the infrastructure is taken away from us. We don't have to design an infrastructure. All that we need to worry about is simply the application and the application life cycle. Again the advantage is it supports Windows, it supports Linux. Not only that, it supports servers on premises and in the cloud. With service fabric, we can uh scale up our environment to even thousand machines in just a single command or if there is a immediate need for thousand machines, I can immediately scale them up to thousand machines. That's possible with service fabric. Now let's look at this question. You can expect this question if the customer is running hybrid environment meaning having some of the applications in on premises and running some of the applications from the cloud and for some reason when classifying the application that goes to the cloud and that stays on premises they have decided to keep the database inhouse. So in that environment a lot of customers do that. So in that environment this is a classic and a scenario based question. A client wants the front end of their application to be hosted on Azure in the cloud and wants the database to be hosted in on premises for security reasons or to have full control on that databases. How do we go about suggesting a solution for this customer? The ideal solution in this scenario is to use um the VNET based pointto-sight VPN solution. So all the front-end applications will be in the cloud and they'll be hosted in a VNET and from the VNET they'll be connecting to the database through an pointto-sightVPN. So the traffic and the writings and the reads are not coming through the internet but through a pointto-sightVPN link that's connecting the Azure VNET and the on premises environment. And this uh model or this approach or this solution is best suited for scenarios where there are only a limited number of resource that needs to be connected between on premises and the cloud. This is a very common question. What's Azure traffic manager? Of course, we're no more running applications on a single server. We're no more running applications on or or from a single environment, right? the same application is being run from multiple environments within Azure and it can be running from Azure and on premise as well. So multiple environments between Azure and on premises and a lot of customers have such environment and if you're facing an interview with such customer this could be an ideal question. What is Azure Traffic Manager? Now, the Azure Traffic Manager is a DNS-based traffic load balancer that actually enables us to distribute traffic between services across Azure global regions. And by doing this, it provides a good availability and a good responsiveness to the application. And this traffic manager, it uses DNS to direct client requests to the most appropriate service endpoint based on the traffic routing logic and the health of the endpoints that it maintains. So in short, this traffic manager is a load balancer that enables users to provide high availability and responsiveness by distributing traffic in an optimal manner across the Azure when we run the same application in different regions. So some of the advantages or some of the use cases of using Azure traffic manager is it provides multiple automatic failover options. It also helps with reduced downtime. It also helps with the distribution of user traffic across multiple locations so one location is not overloaded. And then it helps with users knowing from where our customers are getting connected from. That's another big use case with Azure Traffic Manager. Let's look at this question, right? This is an ideal question. Now there are group of servers connected together within an virtual uh network and now we need to move them or create a separation between them. How do you go about achieving it? So the question goes like this. You need to isolate network traffic among VMs in a subnet which is part of a virtual network with little downtime and impact on the users. So that's the given scenario and the best way we can uh do it is create a new virtual network and move all the VMs in that subnet to the new virtual network. Now this feature is not possible with lot of other cloud service providers like AWS and a lot of other providers. Now in those environments we might need to shut down, we might need to stop the VM, create a new VM based on the image and it's an hefty process. But here in Azure, I can simply move the VMs from one subnet to another virtual network without needing for any additional security like the network security group. I can simply isolate them if I need to by creating a simple new virtual network and moving the servers to the new virtual network. Look at this one. This is another common question with respect to Azure. What is public, private and hybrid cloud? So this is really to test how well have you understood the different cloud offerings in the market public, private and hybrid or at least the three basic offerings in the market public, private and hybrid cloud. Now the public cloud is the most common way of deploying cloud uh computing applications and uh it has resources like uh servers, storage and are owned and operated by thirdparty cloud service providers like Microsoft Azure. Microsoft Azure is a very good example of public cloud. So here every component that the user is using is running only on Azure. That's public cloud, right? Let me talk to you about some of the advantages of public cloud. Some of the advantages is low cost because there's no need to purchase hardware or software and we pay only for the services that we use in public cloud and there's literally no maintenance because uh the service provider maintains the environment for us and uh with public cloud we have nearly unlimited scalability meaning we can get resources on demand and can meet our business requirements on demand and the public clouds are very highly uh reliable because uh they have a vast network of servers and they ensure that uh our application does not fail. So there are some advantages of public cloud. Let's talk about private cloud. Now private cloud uh consists of compute resources used extensively by one business or one organization. Now this private cloud can be physically located at our organizations on-site data center or it can be hosted by a third party service provider. Whichever the case, the private cloud services and infrastructure are always maintained on a private network and they're maintained on hardware and software that are dedicated solely for one organization or solely for your organization. So in short, private cloud in Azure is Azure services being run within an onremises data center or on premises data center used by the user to host systems or applications. And some of the advantages, some of the advantages is it gives more security. Resources are not shared with others. So a higher level of control and security over our resource and application is possible. And then we have hybrid cloud. Now hybrid cloud is the best of both worlds. So it combines the features of both public and private cloud. And some of the user components are being run on Azure and others within on premises data center. So they kind of share the resources. In other words, they kind of share the application. Half of the application would be running in on premises and half of them would be uh in the cloud and they would be working in harmony to support the application and the business need. So that's hybrid cloud. This is one another good example question that wants to test how well you pick services or how well have you understood Azure products and services and are picking the right service for the need. So the question would go like this. So what kind of storage is best suited to handle unstructured data? There are a lot of storage options available and the requirement here is what or which one would you choose for unstructured data. The answer for that question is blob storage because blob storage is designed to support unstructured data. It works in this way. It places the data into different tiers based on how often they are accessed. Different tier means different performance. Different performance means different cost associated with it. So a lot of add-on advantages will we get when we use blob storage for unstructured data. In addition to it any type of unstructured data can be stored in blob storage. This is not true with couple of other storage options that we have in Azure. Only with blob storage we can uh store any type of unstructured data and the data integrity is maintained every time an object is changed in the blob storage. And the best part is the blob storage helps increase applications performance and reduces the bandwidth consumption and reduces the bandwidth consumption for that application. So they are the benefits that we get for blob storage and blob storage are the ones that are well suited for unstructured data and that's what your answer should be. It's really an five-step process and if you have worked and if we have done some labs some basic labs with Azure you can easily answer this question. So it's a five-step process. First step is to log into the Azure. The second one is to create an uh resource resource or a resource manager. And within the resource manager, you would be selecting the resource and then pick the u operating system. Do you want Windows or Linux? And within Windows, what's the flavor you want? Or within Linux, what's the flavor you want? So decide on it. And then entering the relevant information. relevant information like the uh name of the uh instance or the VM that we're going to launch and the password uh the URL that goes with it and a couple of other relevant information that goes gets itself attached with the uh VM and then select the size of the virtual machine different size different uh types available for the kind of application and for the intensity of the application that will be running on top of it. I'll select the virtual, select the size of the virtual machine, review everything whether they're good or not. If there are any changes required, go back and edit them and then come back and launch and your VM is there for you to start working within like 3 or 4 minutes, not even 5 minutes, within 3 or 4 minutes, it gets ready and you can start working on it. So, it's a quick and it's a fivestep process and you should be able to answer it easily if you have done a few labs in Azure. Let's now look at some scenario-based question. You've been posed with a scenario. So, we thought through it and we picked some common scenario-based question that are being asked in interview and I thought we'll present it for you with the answers with explanation so you can get benefited through it. So, let's look at this question. You're asked to make sure your virtual machines are able to communicate securely with each other to ensure security or to have good amount of security. What would you do? And the correct and the best answer for this would be using virtual network in Azure which enables us to communicate with the internet securely which enables us to communicate with the on premises data center in a secure fashion. So the advantage of using virtual uh network is users can create their own private network. Users can pick their own private IP ranges. Users can create their own subnet. Users can create their own routing between those two subnets. Lot more goes into that virtual network. So it it's very customizable and the users are provided with an isolated and highly secure environment for applications. It's completely isolated from other customers. It's completely isolated from other applications that are running in other virtual network that we own. So within our account we can have multiple virtual networks and one application running on a virtual machine is completely isolated from other applications running on other virtual machines and uh of course all traffic stays within the Azure network. Azure virtual machine or within the Azure network depending on how you set up the routing. If you have set up routing to go or reach the internet it's going to go otherwise it's going to stay within Azure. If you have set up routing to reach on premises, then it's going to go and reach on premises. Otherwise, it's not going to go and reach on premises. It's going to stay within the Azure. And it also allows users to design their own network like we already discussed picking up IPs, picking routing, you know, picking subnets, you know, how many servers should be present in that uh particular subnet or how many servers should that subnet accommodate the size of the subnet, the IP ranges, the natting, the masking of IPs, creating of VPN, all that's possible with the virtual network. So it really allows users to design their own network and using virtual machine is how we secure applications in the cloud. Let's look at this other scenario. How do you ensure that every time a user logs in they are not asked to re-enter the password as part of authentication. So you really don't want your users to re-enter the password every time they log in to a different application. Well, all the applications have their authentication mechanism in place. All of them wants to authenticate the user before they log in. Ensuring the user does not log in every time does not mean that no wiping away all the authentication and authorization that's present in that application. You still need that in place. But how do you make the user hassle-free so they're not asked to re-enter the password or the same password again and again? Let's look at the options available. The first one is to enable Microsoft account authentication. Well, it's not going to fix because with that the user will still need to re-enter the username and password. Deploy express route. Uh it's not going to fix uh either because express route is a network level service that connects on premises to the cloud. So that has got nothing to do with prompting or not prompting for password. And then we have uh setup VPN between on premises data center and Azure. set up AD domain controller in VM and implement integrated Windows authentication. Well, uh you can use the same username and password for on premises and the cloud, but this setup the the VPN and the AD controller setup, it's not going to stop you asking for repeative passwords. So, this is all about um using the same password in on premises and in the cloud. And this has got nothing to do with u u not prompting the user to uh re-enter the password. All right. So that's same password is different from not prompting the user to reenter the password. They are two different scenarios. So u that is also out of the equation. And the last one is configure ad sync to use single sign on. That's the right one. So when we configure the AD to use uh single sign on then uh it's going it's not going to ask for the username and password every time we access an application because we have logged in and that login is going to stay active for like 24 hours or so depending on how you configure it and within that time you can access a lot of other applications and it's not going to ask for the username and password because you already have a single signed on and you have signed in using the right credentials. Let's look at this one. You need to ensure that virtual machines remain available while migrating to Azure. What would be the appropriate service to use? Right? Let's look at the options. Traffic manager. Traffic manager is um is literally and DNS service. And then let's look at the other one. Update domains. It again has to do with traffic manager. Updating the URL. So the traffic manager gets updated and then starts sending request to that particular uh URL. It's going to take some downtime because when we update the URL they will have to be populated to all different places and it takes time. So within that time any user trying to access it's going to fail. And then we have express route and cloud services. Express route could be the in fact it's the right answer because express route it's an extension of our on premises and cloud environment. And in this question it really comes out from a customer who's having an hybrid environment. So they have applications running in on premises. They have applications running in the cloud and they want to have a way to migrate applications from on premises to the cloud. In other words, kind of do a cut over between on premises and the cloud. And this express route is a service that connects between on premises and the cloud. Uh so when you do the cut over the traffic is now sent to the cloud instead of being handled in on premises. In fact the services and the application is getting down are getting shut down in on premises. So the request will come in the same pattern. Instead of they being handled in on premises, they are now routed to the cloud using express route and the API calls get addressed or the the queries gets answered uh in the cloud through the express route service. Look at this question. You are an administrator for a website called web game and you're required to validate and deploy changes made to your website by your development team with minimum downtime. So the real question is how do you validate the deployment changes that's made by the development team. Let's look at the options. Create a new linked resource. Create a staging environment for the site. Enable remote debugging on the website. And then create a new website. Well, why would you want to create a new website? Just to validate the changes. And doing a remote debugging is not going to help because debugging only captures logs of the changes happening. It does not do anything with validating the changes. Create a staging environment could be or is the right answer because when we have staging environments, anything that we run on production can be run on staging environment and uh any failures that would happen in production if we simply run it in production can be captured when we run the application in the staging environment. So that way staging environment is a very helpful and useful service and that way I can catch any errors. In other words, I can validate the changes that were done by my development team uh before I move it to production and that reduces the downtime in the production environment. Look at this one last question that we have for you. It's um a standard tier application is used across the world and uses Azure website standard tier. It uses large amount of image files. So you can get it. This could be an e-commerce website which has a lot of pictures in it and this is causing the application to load slow. How can we handle this situation? Let's look at the options given. Configure blob storage with custom domain. Well, this application has pictures but the pictures only the pictures is not all that the application has. All right. So, configuring blob storage might not help. This could be an very interactive website and that can't be run from blob storage. Let's look at the other options. Configure Azure website autoscaling to increase instances at high loads. Now, it's the picture that's causing issues for the website. It's not the CPU or it's not the memory unavailable memory not enough that's causing the application to be slow. So, we need to identify what's causing the application to be slow. So, it's not the CPU, it's not the memory. So, configure Azure for autoscaling is not going to help. And then what are the other options? Let's see. Configure Azure CDN to cache all responses from the applications web endpoint. A CDN could be the right answer. But look at that. It says uh CDN to cache all responses from the application's web endpoint. CDN is not designed for that. Though it can do it, that's not the best way to use CDN to capture all responses from the application's web endpoint. The proper design for CDN would be to cache the frequently used ones. In other words, cache the static content which are photos, videos, logos and pictures and lot more static content that never changes. Let's look at the last option. Configure Azure CDN to cache site images and content stored in Azure blob storage. Absolutely correct. So here we will have to redesign the application uh to store the pictures highquality lazy loading or slow loading pictures because of the high quality and the bigger size. So store them in CDN and then the content let it be stored in Azure blob storage. That's the right way of designing the application and if we do it this application is going to run faster or the application is going to respond faster to the users. >> So that's a wrap up on our full course. If you have any doubts or question, ask them in the comment section below. Our team of experts will reply to you as soon as possible. Thank you and keep learning with Simply Learn. Hi there. If you like this video, subscribe to SimplyLearn YouTube channel and click here to watch similar videos. To nerd up and get certified, you can check the description box below.