Microsoft Azure Fundamentals Certification Course (AZ-900) - Pass the exam in 3 hours!

Hi, I'm Andrew Brown from Exam Pro. And welcome to my az 900

course

, also known as Azure Fundamentals

certification

for the Azure platform. So if you are new to the cloud and don't know anything and want to get started, this is the

course

for you. Because we'll show you how to set up your account. Review top services and more. And as always, I'd love to hear your comments. So if you're on Twitter or LinkedIn definitely let me know what the course is like. And if you

pass

, be sure to use the Azure Azure Certified hashtag on Twitter and I'll definitely get back to you.

I hope you stop by and see you soon. Hi, I'm Andrew Brown from Exam Pro. And we're looking at what az 900 is. So Azure Fundamentals is the entry level cloud

certification

for Microsoft Azure. This certification is generally known by its course code, which is az 900. Az 900 involves learning the core Azure services, the

fundamentals

of cloud computing, and having some hands-on experience working with the Azure portal. And if you look in the top right corner, this is what the certification badge looks like once you earn it for Azure Fundamentals. And then we will talk about certifications in general for Azure.

If you want to have a roadmap for what you'll do after this certification, as you break down your certifications, the role-based certifications like Foundational Associate Expert and Specialty. So at the core, we have the az 900. For the associate, we have the administrator, the developer, the AI ​​engineer, the data scientists, the data engineer, if you notice, for the data engineer, you see that there are two course codes under dp 200, dp 201, because some, some certifications require you to

pass

two different

exam

s. So if you want to become a data engineer, you have to pass those two

exam

s, the expert level or I'm sorry, we sell the security associated with the expert level, we have the solutions architect expert, where you have two exams, you have to pass.

Then there is the expert DevOps engineer. And then for specialties, we have Azure for SAP workloads and IoT developer. These are all role-based Azure certifications. Azure or Microsoft used to have everything that was very service or technology specific. But things have changed in terms of roles, which makes things a lot easier for people who hire, because people who hire look and say, Oh, you have the data engineer certification, you should know how to do data engineering. That's really simplifying things. You can take any of these in any order you like. So if you want to go to expert level right away, you absolutely can.

But in general it is not recommended. You should start with the basics and go to an expert, but you know, whatever you think is best for you. That's what you have to decide. So here's the az 900, so they commonly get sales and management to help tell VPS or CEOs the reasons why their company is using Microsoft Azure. And among developers, it's to show that they are familiar with cloud concepts. So anyone saying, if you've had program experience, but you just don't have cloud experience, it's just a great way to add cloud skills, in az 900 it focuses on developing concepts focused on security and business, which makes sense. because if it's designed for sales and management, there will be things that will help convince them to adopt it, like using the TCL calculator and informing decisions like that, like knowing the SLAs and things like that to drive business decisions.

So what is the value of the az 900? Well, if you're a developer, it won't be as useful on your resume, people won't try to hire you just because you have it, you'll really have to move up to associate or expert status. But that doesn't mean you shouldn't get this one. If you are a developer and already have cloud skills, and another cloud provider, let's say they have AWS skills, you already have an associate level. And you just want to prove that you can work in the cloud and getting this certification just shows that Oh, yeah, okay, I snooped around the Azure portal.

Then you will have that transferable knowledge. So it would be a good case to get it as a developer. Or if you don't have any cloud certifications and want Azure to be the cloud provider you want to use, then it makes sense to get it. The main reason I tell people to always get a foundational certification is because it helps them build confidence before getting a more difficult certification. It will also familiarize you with the exam experience, whether you take it in person or online, because it can be extremely stressful. Ok, now you are convinced that you want to get the az 900.

Then you are asking me, well, how much time do I have to spend to get certified? Well, if you are a developer, let's say, a junior or mid-level developer, and you have been working in the industry for a few years, but you have no experience in the cloud, I will say that you will have to put in about eight

hours

of study if you are a camp graduate. of training. So you don't really have any real-world industry experience. But you want to try to incorporate the cloud as soon as possible to help your resume and stand out from the crowd.

You'll probably spend 15

hours

studying if you're in sales or management, so you just don't have a technical background, but you're trying to understand why you should adopt Azure or the cloud for your business. looking at 20 hours of study. And what I recommend is to dedicate one to three hours a day for seven days. And I mean, every day, you don't want to spread this stuff. Now, the next question is where is this exam performed? And the way it works with most cloud service providers, as they are associated with a company that is also associated with several testing centers around the world, and the one that is associated with Azure is called Pearson VUE .

But the best thing about Pearson VUE is that you can go in person to a testing center, so I would use your Pearson Pearson VUE website and it will tell you the testing centers near you. Or you can take it from the comfort of your home. So if you have a webcam and you have a very small space so you don't have a ton of stuff going on in the background and they can trust that you're in a safe place, it allows you to shoot it from your home office. And that is what we call a supervised exam.

And the reason we call it a proctored exam is because a proctor is a proctor or a person who supervises students during an exam. So you have both options available, if I had to choose one or the other I would highly recommend going in person because online things can go wrong and you don't want to have that problem. But you know, it just depends on you. Well. And the last thing is what it takes to pass the exam. So there are three components here. The first is to watch the video conferences and memorize key information. The second thing is to carry out laboratory practices and follow them with your own Azure account.

And I'll show you how to set up your own account here. But when we get to the sections, you should definitely do it, but don't look at it, because that will make a big difference and help you pass. And the last thing is to take paid practice exams online that simulate the real exam, you can pass the exam without using paid practice exams at the basic level, which is this certification. It is much more difficult at the associate and expert level. Therefore, you will have to get a paid solution; If you are going to take paid practice exams, do me a favor and use hours because it helps us produce this content.

So don't use one of those other paid providers that don't offer free content. Because for us, if we made enough money, we would do it all for free. And that is the point. There you go. So now let's take a look at the exam guide and discuss what we will have to do to pass the exam and how we will have to study. So the first thing is the content outline. And these are basically the general domains, we are going to have to focus our time on the first cloud concepts, this is worth 15-25% of the exam, then you have the core Azure services, this is worth 30-25% of the exam. 35%. of the exam, then there is security, privacy, compliance and trust, this is 25 to 3% of the exam, and then there is price and support, which is 20 to 25% of the exam, you will notice that there are ranges here.

The thing is, there is no guarantee that exactly 25% of the questions will be of that type. So keep that in mind. Then to the qualification. To pass this exam, you need to score 700 out of 1000. Typically, you're trying to get around 70% to pass. I say that because you could get exactly 700. And you could fail because Azure uses a Scaled Score, which means that the raw score you get doesn't necessarily reflect the final score. So you'll want to score a little over 70%. So you want to aim for 75% or higher. We'll talk about the types of questions you'll see on the exam here in a moment.

But there are between 40 and 60 questions. That means you have the chance to answer 12 to 18 questions wrong. I put an asterisk here, because people who actually took the exam reported that they were only presented with 30 questions. And I even contacted Azure support to clarify what the actual number is and their official answer was 40 to 60. But I know that when people take the exam, they are there, their experience is different. There's not much you can do about it. It's just that that's what it is. It's going to be a little fluid in terms of what your experience will be.

But let's go with this and say there are between 40 and 60 questions. In terms of the format of the questions, you'll see multiple choices, you'll see multiple answers, you'll see maybe drag and drop, and then you might see an active area, active areas which usually just means like a couple of drop-down menus where you have to answer two things at the same time. And the duration of the exam is 60 minutes. That means you get about a minute per question in that time, but the exam time is 60 minutes, but the seat time is 90 minutes. So, see time refers to the amount of time you should allocate for the actual exam to have time that includes reviewing the instructions before starting the exam, reading, accepting the NDA, and completing the actual exam, which is the exam time. 60 minutes.

And then provide feedback at the end of the exam, which is usually optional. And the last thing is, how long will this certification be valid? It will be valid for 24 months. That means you will be able to keep this for two years before having to recertify. There you go. So now I just wanted to quickly show you the exam guide, they don't call it the exam guide, literally the exam guide, it's the Microsoft Azure Fundamental Skills measured. And this pretty much gives you the information for breakdowns in terms of what things you might need to learn.

But that doesn't necessarily mean that everything listed here is actually on the exam. But let's go over it quickly. Then you have an idea. So the first one is mastering cloud concepts. And here, we need to know, cloud terms like availability, scalability, elasticity, fault tolerance, disaster recovery, agility, we have not seen them before in the exam, but they are not listed there, so we have to describe them. the economics of models based on capital expenditure at scale versus OPEX consumption, then you have to describe the different types of cloud models, such as infrastructure as a service, platform as a service, software as a service, then we have to describe the public, private and hybrid cloud models.

There's that, then you need to know a bunch of different core services for Azure. I would call these global infrastructure, they mainly have to do with networking, then you have all your core services here. And then more core services or extended services, I guess then management tools, then there's security, privacy, compliance and trust. So there are more security-related networking components, but they don't really show up much in the exam, but I've covered them anyway, just in case, than Azure Identities. That is creating accounts that give people access. The most important one is Azure Active Directory and other security tools.

This is just learning about things like Security Center, which is a security tool, or just security services. Within Azure, then we have governance. This will be like policies, role-based access, just general access that has to do with Azure identities here. Then the monitoring tools, then we have compliance with data protection standards, this usually only points to websites in the Trust Center, it is just a website that lists the compliance information that we have described, the prices of the SLA and the life cycle. So, understanding subscriptions, you know, free versus student versus enterprise, here are just some prices.

So, you have a pricing calculator and a TCL calculator and you understand the support plans, and then you understand the SLAs and then there's thelife cycle, such as understanding general availability. So yeah, there you have it. That is the outline of the exam guide. I mean, you have stuff down here about changes, that doesn't really matter. But yes, that is the outline of the exam guide. If you want to know more about actual exam policies, like actual exam policies, this page is really good as I got it from Azure support team. That's why it says exam policies and frequently asked questions.

So this would be about retirement and certifications, or how to book your exam or here they would have information on how to retake it. So what if you paid for it? And how did you miss it? or how many retakes did you receive or how long are the exam hours? So there's a lot of information here. So if you just want to scroll through it, but yeah, here, they don't say on the exam that it's 60 minutes, they just say, oh, for the general, core exams, it's 60 minutes. So we just have to assume that's the time you get the az 900.

But yeah, just look at that page. And check this out if you're interested. But it's not really necessary, because in the course we cover everything you need to know. But I just wanted those resources. I wanted to let you know about those resources, just in case. Hi, I'm Andrew Brown from Exam Pro. And we start from the beginning of our journey by asking ourselves the most fundamental question, which is what is cloud computing. So looking at the dictionary, cloud computing is described as the practice of using a network of remote servers hosted on the Internet to store, manage and process data instead of a local server or personal computer.

So when we talk about local, we describe it as local. Thus being your own office or your own data center. And this is where you own the servers, you hire the IT staff, you pay the rent or the real estate, you take on all the risk. Whereas with a cloud provider, if you are using them, it is someone else who owns the servers, another person who hires the IT staff, another person who pays or rents the property, and you are only responsible for setting up your cloud. services and code, and someone else takes care of the rest.

Sounds great, right? So now what I want to do is just give you a quick overview of how servers have evolved and what we describe as cloud computing from a technical perspective, and we'll probably dive into this later in the course. But here we'll just get a good overview to understand it from a business perspective. So in the past what we had were dedicated servers, if you wanted a server to run your web application or your technology, what you had to do was buy a single dedicated physical machine. And that was for a specific business, and dedicated servers are still used today.

But they have some disadvantages. They are very expensive. They require a lot of maintenance, however, you get a great level of client customization and you can potentially have better security, depending on your use case, then virtual private servers came along. So we still had one physical machine, but it was still dedicated to a single business, but we figured out how to take that physical machine and virtualize it into submachines. So now we could fully utilize or better utilize that physical server by running multiple applications, we didn't have to buy four different servers for four different applications, we could easily run web applications on four virtual submachines, then we had shared hosting.

And this made it a lot easier for anyone building websites or WordPress, but the idea here is that you had a physical machine and it was shared by hundreds of companies. So it wasn't just one business, sharing the class, but multiple businesses. However, this depends on the majority of tenants not using the resources. So if you had 100 people on a server and one person used more of the server than the others, then everyone might suffer from that case, but at least, you'll get very, very cheap servers. But there are definitely some limitations. Now that we are talking about cloud hosting, cloud hosting gives us the best of both worlds.

So we have multiple physical machines acting as a single system, which could be described as the cloud. And that system is abstracted into multiple cloud services. So you get flexibility, scalability, it's very secure. It is very profitable. And it is highly configurable. So that's where we are. And that's generally what cloud computing is, cloud hosting. Hi, I'm Andrew Brown from Exam Pro. And we're looking at common cloud services. Therefore, a cloud provider may have hundreds of cloud services grouped into various service types. And the four most common types of cloud services for infrastructure are services. And we'll talk about what that is later, it would be calculus.

This is where you have a virtual computer that can run applications, programs and cold code, then you have storage. This is where we would have virtual hard drives where we could store files, then we would have virtual networks, because we have these computers stored. Then you need to put them on some kind of virtual network. And then you have databases. Let's imagine a database running in the cloud. Or if you're not familiar with databases, imagine it's Excel in the cloud, but it powers your web applications. And one thing I want you to know about the term cloud computing is that even though it says computing in the word, at this point we're just using it as a general term.

So it could refer to all of these categories. So when I say cloud computing, I could be referring to databases and computer network storage. But you can also say cloud storage, Compute Cloud cloud databases, cloud networking, and people will know what you mean. Hi, I'm Andrew Brown from Exam Pro and we're discussing what Microsoft is. You've probably seen this logo before. And Microsoft is an American multinational computer technology company, headquartered in Redmond, Washington. And Microsoft makes software for phones, tablets, game consoles and cloud services, which is what we care about here today. And they even have a search engine.

And we are not limited only to that list. They have tons of stuff. But Microsoft is best known for its operating system called Windows. And they've been around since the 1970s. They've been around for quite a while in the tech sphere. Now that brings us to the question: what is Azure? So Azure is what Microsoft calls its cloud provider service. That's why it's called Microsoft Azure, or we commonly refer to it simply as Azure. And here is the logo. If you are wondering what the name of the service is, it means bright blue color of cloudless sky.

So sure, that's cool. And you'll hear me say that cloud service provider often was throughout this course and it's abbreviated as CSP, but that's what Azure is. It is a cloud service provider. There you go. Hi, I'm Andrew Brown from Exam Pro and we're looking at the benefits of cloud computing. So what are the benefits? Well, we have a great list for you here, starting with profitability. So you pay for what you consume, there are no upfront costs, you pay as you go, also abbreviated as P A YG. And you're sharing the cost with thousands of customers.

That's how you're understanding it. That low, low cost. Another benefit is that you can go global, so launch workloads anywhere in the world, simply choose your region and you are now in the global market. Another benefit is that the cloud is secure since cloud providers take care of physical security. And cloud services can be secured by default or you have the ability to configure access down to the granular level. So you have a lot of safety controls that you normally wouldn't have, or would have to build into a stroller. Now, the cloud is also known for being reliable.

So you can have data backup, disaster recovery and data replication and fault tolerance. The cloud is also scalable, you can increase or decrease your resources and services based on demand. The cloud is also elastic. So you can automate scaling during spikes. And a drop in demand when there is no longer demand for those things. And it's also up-to-date, so the cloud provider updates and replaces the underlying hardware and software without interruption for you. And I mean, the last one, there are cases of outages, but generally, less outages than you would have locally. There you go. Hi, I'm Andrew Brown from Exam Pro.

And we're looking at the different types of cloud computing. And we have this nice pyramid on the left side to help us understand how each type builds on the other. Starting at the top of our pyramid, we have Software as a Service, also known as SAS. And this is a product that is run and managed by the service provider; you don't worry about how the service is maintained. And it just works and stays available. You may not know it, but you're probably already using a SaaS product. So examples of that might be Salesforce, Gmail, or Office 365.

So those are things that would be considered SaaS, and they're actually for customers. So you just want to use software, like general software on your computer, but in the cloud. The next category we have is Platform as a Service, abbreviated as past. That's why here we focus on the development and management of your applications. And therefore you don't worry about provisioning, configuring or understanding the hardware or less. And this is really for people who are building applications, but they don't, but they don't think about the infrastructure underlying services like this, Elastic Beanstalk on AWS Heroku, which is very popular with junior developers, which is a third-party service for start web applications.

And then you have Google App Engine. So those are three examples. And these are really for developers. Therefore, the platform service makes it easy for developers to build cloud applications without worrying about everything underneath. At the bottom, we have IaaS Infrastructure as a Service. And these are the basic components of the cloud. So provide access to network functions, computers and data storage space, don't worry about IT staff, data centers and hardware. And this is the real focus of our course: focusing on this layer. But the thing is, again, in this pyramid I emphasize that your service can have a platform as a service and a software service on top of it.

So examples of infrastructure services would be Microsoft, Azure, AWS, or even Oracle Cloud. And this is really intended for administrators. Those are the three types of cloud computing. And there you have it. Hi, I'm Andrew Brown from Exam Pro. And we're looking at the types of cloud computing responsibilities. So we saw the three categories there. But we don't really understand what we are responsible for. What is the cloud service provider responsible for? So, let's establish our categories. And we're going to include on-premises in this because technically, on-premises could be a private cloud and should be in this category.

So we have on-premise infrastructure as a service platform as a service and software as a service. So when we look at applications, it will be the customer's responsibility to pass the on-premises infrastructure. But when we have Software as a Service, the cloud service provider is responsible for that, when we look at the data level it is going to be the same for software as a service, the cloud service provider is going to be responsible, but for The rest will be the client. And then to the next level for runtime. You will be responsible for cloud service drivers for platform as a service and software as a service.

For middleware, it will be the same for operating systems, like the operating system running on the servers, it will be the same, then we will come to virtualization. Now virtualization is accountable to the cloud service provider and up and then from the storage, your servers, it's the same as for storage, it's the same and for networking, it's the same. So you can see that, in the facility, you are responsible for everything. And the more we advance in the types of cloud computing, the less responsibility you have. Hey, this is Andrew Brown from Exam Pro. And we were looking at Azure as a deployment model.

And the first model we are going to talk about is the public cloud. And that's where everything is built at the cloud service provider, nothing is used on-premises or in their own data centers, everything runs within Azure. And generally this is known as cloud native. But for some reason Azure calls it public clouds. That's what we're going to use here in the terminology. And here I have an architectural diagram, where we have a network in Azure. And within that network, we have a virtual machine running and a database running. So that would be an example of public cloud, then we have private cloud.

And this is where everything is built in the company's data centers, also known as on premise, because it is within the organization's facilities, just like itsphysical location. And it could be that an organization could technically be operating its own cloud, but it would be a private cloud, and it could be running some open source cloud software that mimics what Azure would do, like OpenStack. So it looks very similar. But you just put an OpenStack in there. And it runs a virtual machine or a server, and it also runs a database. And last on our list here is the hybrid.

So with hybrid, both the on-premises and the cloud service provider are used, and they are connected to each other. Therefore, there are many different network services that you can use that will make it easier to connect between the two. In this case, we use Express Route Express rose is a dedicated connection, it's like having a fiber optic line running from your local data center to the Azure network. This is just one of the ways you can connect. And if we want to understand the pros and cons, I have this nice little table here, we'll go over it quickly.

So if you use the public cloud, it is a more cost-effective security. It's great that the controls are stronger by default. But some people may not find the cloud meets all of their security requirements due to government and regulatory reasons, not because the cloud is unsecure. But it's just those policies for the configuration level, you will be limited depending on what the cloud service provider exposes to you. So there's a lot of configuration there. It's just that if you have your own servers, you can obviously do anything with them. To gain technical knowledge, you don't need to have such a deep understanding of the underlying infrastructure, because you're not physically setting up servers, or networks, or anything else.

Now moving on to private cloud, private cloud is the most expensive option on our list. So you're going to pay a lot of money there. As for security, there is no guarantee that it will be 100% secure, because you simply do not have the same type of visibility that you would have with a cloud service provider. With all those panels, it's very difficult to develop all that software, but you might be able to meet your security compliance requirements, depending on your situation. But this is becoming less and less as more governments and larger organizations migrate to the cloud.

You can configure the infrastructure exactly how you want because you've literally bought the hardware and you can do whatever you want with it. And technical knowledge, you will have to have a lot of technical knowledge, you may even have a hard time finding the resources to maintain all that. Then down below we have the hybrid model. So this could be more cost effective depending on what you download to the cloud and also the cost of moving data back and forth. For security, you know, you have more to protect. But technically, some things are easier to protect in the cloud than in private.

So maybe you have a boost and sure, you'll get the best of both worlds in terms of setup. And to get technical savvy, you'll need to know both the cloud and how to set things up on-premises. So that's the most work there. And here there is only one more implementation model. I just wanted to talk about the cross cloud. This is not something that is included in the actual exam, but it is something you should understand and know. And so cross cloud is when multiple cloud providers are used, sometimes we'll refer to this as multi cloud or hybrid cloud.

So I just have one example here. So there is a service called Azure Arc. And what Azure Arc does is expand its control plane. So you can run containers, Kubernetes containers on different platforms. So you could have AWS on the left side with the Eks engine and GCP Kubernetes and you could run virtual machines, and they would all be treated as if they were on the same network. So cross cloud is becoming very popular with extremely large organizations where they have unique requirements, but I definitely want you to know what that is, because it just gets pushed to the side.

And it's definitely something that's part of the industry. There you go. Hi, I'm Andrew Brown from Exam Pro. And we're looking at the concept of total cost of ownership for the CEO. So what's the difference between having your own on-premises data centers and then using Azure? You'll notice above that it says capex and OPEX, we'll talk about that on the next slide. But for now, or for the moment, we will focus on the total cost of ownership. So to really make sense of this, I always use this graph here. And if you're wondering what that is, they're icebergs, people sometimes think they look like teeth.

And to make this drawing a little clearer, I added some penguins and a whale, so there was no room for doubt. And the reason we use this as a proxy is because we have the top of the iceberg, which are the costs that we generally worry about. But then we have those hidden costs, those costs that we don't really think about and that are underwater. And if you know icebergs, they can be very big underneath, you don't know. So on the left side, the cost we usually think about is software licensing fees. And then in the case of the cloud service provider, we look at subscription fees.

And so when you compare these two, sometimes the subscription fees can cost more than the software license fee. So you think, well, we should use it in the stroller because it's more cost effective. But when we take into account the total cost of ownership, all the costs involved, we will see a very different picture. On the left side, if you're on-premises, you have to deal with deployment, configuration, and training, but you also have to deal with the physical security of your building, you have to pay for the hardware, you have to pay the security staff. IT, you have to take care of maintenance.

Now, on the right side of the cloud, there is still deployment, configuration, and training to do. But that's all. So there's a big difference in terms of what you have to do. And you might ask, well, what's the savings amount? Well, in general, people find that when they go from on-premises to the cloud, they save 75%. That's a lot of money, okay, 75% of what you would normally spend. And now all these things on the left side are now Azure's responsibility, you don't take care of that anymore, Azure will take care of everything for you. So that's the total cost of ownership.

Hi, I'm Andrew Brown from Exam Pro and we're looking at capex versus opex. So on the left side, we have capital expenditure, that is, capital expenditures. On the right side, we have OPEX operating expenses. And looking to the left, capital spending is spending money upfront on physical infrastructure, so by deducting the expenses from your tax bill over time, many larger companies are used to dealing with capital expenditures. . And they know how to manage your tax bill. And that's why many people are afraid to move to the cloud, because they are used to this way of operating.

But let's talk about some of the things that would be considered a capital expense. Again, it's anything that's physical and then you buy it with money up front. So computers, that would be your server costs, if you bought hard drives, your storage costs, if you bought routers, cables and switches for your network, if you bought things for backup and archiving costs, if you had disaster recovery . So like an uninterruptible power supply, that would be an example of the cost of your data center. So that's your rent, cooling, physical security, your technical staff, so you're hiring people to do things for you.

And so with capital expenditures, you have to guess ahead of time what you plan to spend. Now let's look at operating expenses. Therefore, operating expenses are the costs associated when a local center has passed that cost on to the service provider. So in this case, it is the cloud service provider, and the customer only has to worry about the non-physical costs. So what are examples of OPEX costs: software leasing and feature customization, training employees on cloud services, paying for cloud support, billing based on cloud metrics, computing usage, and usage storage. And the advantage here is that with operating expenses, you can test a product or service without investing in equipment.

So we have investment flexibility. And also in the previous slide we saw that we have a huge cost reduction. So there are two reasons, very good reasons to use the cloud. Hi, I'm Andrew Brown from Exam Pro. And we're looking at cloud architecture terminologies and these are very important to help you conceptualize the benefits of the cloud. So we'll go over these terms and then go over them again in more detail in subsequent slides. So at the top of our list we have availability and this is your ability to ensure that a service remains available. And this is generally known as high-altitude and high-availability or high-availability abbreviated as h a, that's a term you should know.

Then we have the scalability so that it can grow quickly or without obstacles. Then you have a lastness. This is its ability to shrink and grow to meet demand. You have total tolerance. This is your ability to prevent a failure and then you have disaster recovery. This is your ability to bounce back, bounce back from failure. And this is generally known as high durability or high durability. D are. There you have it. Hi, I'm Andrew Brown from Exam Pro. And we're looking at the concept of high availability. This is your ability to keep your service available by ensuring there is no single point of failure or guaranteeing a certain level of performance.

Here I have a technical architectural diagram that describes high availability. So the idea behind this is that if you have one server running your web application, if you run redundant versions of your server, if something were to happen to a single server, traffic could always be routed to those other servers. And that way, your service would remain available. Now, having multiple servers is great. But even what is better is to have multiple servers in multiple data centers because something could happen to one data center and it could become unavailable due to a network problem. So by being able to route traffic, or in that way, you will still have high availability.

And running a workload across multiple AZs and AZs is what Azure calls its data centers, ensuring that if one or two data centers are unavailable, your service will remain available, which is very , very common to run at least three servers in three data centers. . Now, how would you distribute traffic or manage traffic to all three? And that's where an Azure load balancer comes in, that green triangle with the arrows is the representation of a load balancer. Therefore, the load balancer allows you to evenly distribute traffic to multiple servers in one or more data centers. And if a data center or server becomes unavailable, making it unhealthy, the load balancer will route traffic only to available data centers, with servers.

There you have it, that's high availability. Hi, I'm Andrew Brown from Exam Pro. And we're looking at the concept of high scalability. And this is its ability to increase its capacity based on the increasing demand for traffic memory and computing power. If you are a growing company, you will have to scale, you will have to get bigger and better servers. But there are different types of scale. And the first type is the vertical scale. This is the most obvious one that people will think of and it's called upscaling. And what we do is we just upgrade to bigger servers, we need bigger hard drives, faster computers, that's vertical scaling.

But there is another type of scaling called horizontal scaling and horizontal scaling is described as horizontal scaling. And what you're doing is just adding additional servers, because we saw with high availability, we have a load balancer, we can distribute traffic to multiple servers and three servers can equal the same as one large server. So horizontal scaling is when we add more servers of the same size. Hi, I'm Andrew Brown from Exam Pro. And we're looking at the concept of high elasticity. And this is its ability to automatically increase or decrease its capacity based on current traffic memory demand and computing power.

This sounds a lot like high scalability, but the key difference is that it is automatic. And demand can be decreased, not just increased. So the way we would do it is we would have a virtual server, a virtual machine or a server, and if we needed more servers, we would add more servers. And if we need fewer servers, we would remove fewer servers. And this will be achieved using the horizontal scale. So when we say we are scaling this means we are adding more servers of the same size, when we are scaling this means we areremoving more servers of the same size.

And in general you won't use vertical scaling to get high elasticity, it's just extremely difficult to scale vertically. Because if you have to increase, say, your storage drive and then decrease it, you could lose data. Therefore, it is not a good idea, or even feasible, to perform vertical scaling with high elasticity. Now, how would you go about being elastic in Azure, while using Azure as a VM scale set, so that the scale sets automatically scale up or down in response to demand or based on a defined schedule, and we'll talk about that in more detail. later in this course.

And then we have SQL Server, or extensible server database, this hot and cold transactional data is dynamically extended from Microsoft SQL Server 2016 to Microsoft Azure, it's not something we're going to cover, but it's generally the same concept as data sets. skills. There you have it, that's high elasticity. Hi, I'm Andrew Brown from Exam Pro. And we're looking at the concept of high durability. This is your ability to recover from a disaster and prevent data loss. These could be solutions that recover from a disaster and are known as disaster recovery d r, so I'm just going to ask you a bunch of questions to help you think about how to be highly durable.

So a question would be: do you have a backup? So do you have a backup? How quickly can you restore your backup? Is your backup still working? How do you ensure that current live data is not corrupted? That is the concept of high durability, there are a variety of services to implement it. Therefore, it is not a single service. But there you have it, that's the complete list of cloud terminologies and architecture. Hi, I'm Andrew Brown from exam Pro and we're looking at the evolution of computing. And this will really help you understand the different layers of computing.

So we'll start from the left side to dedicated and work our way up to features. So what I want you to know is that when we talk about dedicated, it is a physical server, used entirely by a single client. So the idea is that this customer has purchased this dedicated piece of hardware. But the problem with this is that you have to guess your capacity. So when you buy it, it's like a capital cost or you're buying outright, you have to plan how you're going to fully utilize it. Then you will pay more and have underutilized servers.

And the reason is that when you first start your app, it may be small and then you're expected to grow into that space, but you're just not using that space until you grow into it. Then it is considered wasted. If you want to upgrade beyond your capacity this will be slow and expensive, you will literally have to buy a new server that is bigger and then move everything, you will be limited by your OS. So whatever operating system is installed, that's what you will have, you will have multiple applications, if you install multiple applications on a dedicated server, you may have conflicts when sharing resources.

But in general, it is recommended to have only one main application on a dedicated server; will have a guarantee of security, privacy and full utility of the underlying resources. Because that is the purpose of having a dedicated server. Dedicated servers where you have full control of everything are sometimes called bare metal. And that basically mimics what it was like to have a local server or in the past, and they still exist. That's dedicated, we'll move on to virtual machines. Now we move on to virtual machines, also known as VMs. So the idea here is that if you had a physical server and you had the ability to run virtual machines, it would be like running a machine within a machine.

And now you can run multiple applications on a single machine. The technology that is used to run virtual machines is known as a hypervisor, sir, there are other types that we need to know about that are hypervisors, so know that that is the software that makes virtual machines work, now you are sharing the physical one. server with multiple clients, that's generally a good thing, because you're paying a fraction of the server costs, you have to buy that server outright, you'll still be overpaying for underutilized. Underutilizing the virtual machine, because it solves the problem of wasted space, because you have to choose a particular size of virtual machine, it will not fit your application perfectly, it will be limited by your guest operating system. .

So whatever OS you've chosen, that's what you'll get. So that's what you have there. If you want to run multiple applications on a single virtual machine, they can still conflict and share resources, but now clients that are isolated from you will not have conflicts with you. So you can run, you can run, if you had three applications, you could run them as three virtual machines. Then you don't have that problem. But if they are on the same virtual machine, you still have that problem. There you have it, they are virtual machines. And we will move on to the containers.

Hi, I'm Andrew Brown from Exam Pro. And we're looking at the concept of containers. And this goes a step further, where we have virtual machines and we run multiple containers. We are even and further subdividing the way we run our applications. And the technology that is used to run containers inside a VM or on a physical server is called Docker, Docker daemon. If you use Docker for cleaner education, that's the most common. But that will allow you to run multiple containers and you will be able to maximize the utility of the available capacity. So this is much more profitable, right?

So the available space is always there so you can start more servers or you can scale up your application to fill that available space, your containers share the same underlying operating system. Therefore, containers are more efficient than multiple virtual machines. But the good thing is that you can have different OSS. So the idea is that technically each container can run a different operating system. And now you have much more flexibility. It doesn't look like you can improve this any further, but we'll get to work. So now let's take a look at the evolution of function computing and I bet you didn't believe it.

But we subdivided even more. So we took our applications running containers and broke them down into small pieces of code called functions. And now we even have a greater or better utility of our computation. So we have a managed VM running management containers. So we don't have to worry about the containers or configure them themselves, the functions usually take care of this. This is known as serverless computing, because you don't configure anything, you just put your code online. And it just works, you can choose the memory and duration you need to use. And that's all you pay for.

You are only responsible for your code and data and nothing else. And it's extremely profitable, right? Because you're only paying for that individual function to run and all those underutilized slots are the cloud service provider's problem, it's not your problem. The only drawback is that there is a concept called cold starts, which means that when you start a function, or serverless, or serverless code, you usually have to provision a server, because the cloud service provider doesn't want be. running servers, when they don't, they don't, they are not used. Therefore, you may experience a cold start where you are waiting for a server to start before your code runs.

There are definitely ways around it. There you have it, that's the evolution of computing. Hi, I'm Andrew Brown from Exam Pro. And we're looking at regions and geographies for Azure. So a region is a grouping of multiple data centers. And for Azure, they call their data centers availability zones, since it has 58 regions available in 140 countries. One thing Azure likes to promote is that it has the most regions of any cloud service provider, then we have something we call geography. Therefore, geography is a discrete market of two or more regions that preserve the data residency and compliance boundaries and geographies that are available for Azure.

We have the United States, then there is the Azure Government, we, this is a geography that is only for the United States government. So ordinary citizens can't use it, then there's Canada, that's where I'm from Brazil, and Mexico. And I just want to emphasize the geographic boundaries of data residency and compliance, and I just want to give you an example. So, imagine you live in Canada and work for a Canadian company, and you want to ensure that the data will remain within Canada, for any regular government regulatory reasons. Then you'd want to use Canada as your geography because that data would never leave Canadian soil.

So that's the case there. And I just want to give you kind of a visual example. So on the left side, we have two regions, we have the US East and we have the Europe, Norway, East region. And in those regions, I won't show it here because I don't want to make it too complicated. But there would be availability zones and we could launch resources. We have some servers, virtual machines, those are the images that you see within the regions. And in general, the way regions work in Azure is that when you go to launch a resource, you choose the region at that time of creation.

So if you are starting a virtual machine, it will give you the option to choose a region and just choose from that list. So yeah, there you have it. So I headed to Azure. So I wrote Azure global infrastructure because I just wanted to show you the big map of all the regions. And where Azure is available worldwide. Because sometimes it's nice to look here. We can see that we have things in Australia, we have regions in Africa, we have a region in South America, we have many in North America, we have many in Western Europe.

And then we have some here in Asia. So we have Japan, China, everywhere. So if you want to dig a little deeper into that, there's a lot of good information here on the global infrastructure pages. But that's all. I just wanted to show you that world map. We are now looking at paired regions. Each region is then paired with another region 300 miles away. And the reason Azure does this is so that if one region is updating, the other is still available, which means that if you are running and plan to make sure you never have downtime, you can put your resources in that region paired, and you will have greater availability.

Therefore, some Azure services rely on paired regions for disaster recovery. So when you activate those services, they will automatically start in that paired region. One service that would help you take advantage of your paired region would be a service called Azure Wall. It's a feature of storage, but it's called Azure georedundant storage, so it replicates your data to a secondary region automatically, making sure the data is durable enough. In the case of the primary region, they are recoverable. And just to give you an example of a paired region, let's say we're talking about Canada, so with Canada, you would have Central Canada, and then your paired region is Canada, east, for North America.

And when we say North America, we're actually talking about the United States. Your US East region is paired with the US West region. And then for Germany, there's Central Germany and Germany, Germany, northeast. So it gives you an idea of ​​how far away they are, 300 miles, which is a considerable distance. But there you have it. Hi, I'm Andrew Brown from Exam Pro. And we're looking at region types and service availability for Azure. And what I want you to know about service availability with respect to regions is that not all cloud services are available in all regions.

And there are infrastructure reasons and compliance reasons. So Azure has two types of regions, they have recommended regions. These are regions that provide the widest range of service capabilities. What that means is that most services will be available in this region. And this recommended region is designed to support availability zones, then you have alternate regions. And these are regions that extend Azure's presence within a data residency boundary, where there is also a recommended region. But they are not designed to support availability zones. That doesn't mean you can't throw resources into them. It simply means that when you go to launch a resource, you will not choose an availability zone.

And these regions are labeled as others when you are in the Azure portal. Now let's talk about general availability. So general availability, abbreviated as ga, is when a service is considered ready to be used publicly by everyone. So if you have a service or product that was in beta andnow you are ready to sell it to people, that means its GA. But it is, but only because that's where you sell it, there's also the conversation about whether it's actually available to us. And that will be determined based on the category that Azure cloud services fall into.

Therefore, Azure classifies three different types of availability for services. And the first is essential. So a fundamental cloud service will be available immediately in recommended and alternative regions, when it goes live or at least in the fifth year from the time it was announced, then it will be in the mainstream. These are cloud services that will be available immediately in a referral region or in 12 months when you move to GA. But for alternative region, it can be available according to customer demand. And then the last one is specialized. Therefore, cloud services found in this category will be available in recommended or alternative regions based on customer demand.

Hopefully that clarifies service availability and region types. Hi, I'm Andrew Brown from Exam Pro. And we're looking for special regions for Azure. Therefore, Azure has specialized regions to meet legal or compliance reasons because they may not want to work with specific governments. And to meet those requirements. They are basically given their own region. So, first on our list is the United States and we have three regions that we know about. So we have the US Central Department of Defense, the US government, the Virginia region, the US government of the Iowa region, and then we have three additional ones that we just don't know about, because they are in secret locations.

So maybe they are for area 51, we don't know. So the reason they have these special regions is that if they just want to do business with the government, they need these types of regulations. Then on the other side we have China, so they have a region in eastern China and northern China. And these regions are available through a unique partnership between Microsoft and 21 via net. Therefore, Microsoft does not directly maintain these data centers, but worked with 21 v net to provide access to these regions. And probably to operate these regions, I would probably be an assistant to these countries.

And you would also be a government employee. Therefore, it will not be for citizens to use. But there you have it. Hi, I'm Andrew Brown from Exam Pro. And we're looking at Availability Zones for Azure. And so availability zones, abbreviated as AZ and you'll hear me use that review a lot in this course. And you must learn to remember that it is also a physical location made up of one or more data centers. So a data center is a secure building that contains hundreds of thousands of computers. If you want to see a little, here's the inside of a data center.

And there's a technician working on a server rack and there's a dog in the data center. You should definitely never have a dog in your data center. You'll probably hear me refer to available availability zones as data center because that's the easiest way to look at it, but it can actually be more than one data center. Now a region will generally contain three availability zones, I say generally here because there are cases where there are less than three. But there are actually very specific reasons that by having exactly three availability zones, data centers within a region will be isolated from each other.

There will be different buildings, but they will be close enough to provide low latency. And that low latency would probably be less than milliseconds. I don't know what it is for Azure. But generally this is how it would be designed. Because you want to feel like you're on the same network. It is common practice to run workloads on at least three azs. And that's why I said before that it's important to ensure that services continue to be available. In this case, one or two data centers fail. And this is called high availability. And we will definitely cover this concept again in this course, just to give you a visual idea, on the left side, what we have is a region called US East and we have multiple availability zones.

Azure simply labeled them one, two, and three. And so, when you go to start a resource, if you look on the right side, you choose your region. So we chose ourselves, east, then we said we're going to use the availability zone and then we choose which one we want to launch it on. So if we decide, it will go into availability zone two, that doesn't mean we will launch two instances, it just means availability zone two. There you go. Hi, I'm Andrew Brown from Exam Pro. And we're looking into AZ supported regions for Azure. So, not all regions support Availability Zones and we address that in the region section, but we'll address it again here.

So we know that there are regions called alternative or other and these do not have any availability zones, so you have recommended regions, and these are supposed to have three azs. The reason they may not have them is because it is a newer region. And Azure promises to add more regions within 12 months or whatever time frame they say. But in general, what you have to do is, when you have resources in the cloud, you should launch them where they have at least three AZ, so you know which regions really have three Z. And that is the center of us, the east from us, the west of us to western Europe, France, central, northern, northern Europe and Southeast Asia.

That's where you generally want to run your workloads. Now, what does it look like when you try to launch a resource and they and you choose a region that doesn't have an availability zone? What will that look like? It will look like this, so the availability zones will be blank. And you will have to choose that infrastructure redundancy is not required. And that would be an example for Brazil, South, where there's just a single az, but it's described as having no AZ, so you just don't choose it in the interface. There you go. Hi, I'm Andrew Brown from Exam Pro.

And we were looking at bug domains and updates. Therefore, an availability zone in an Azure region is a combination of a fault domain and an update domain. So a fault domain is a logical grouping of hardware to prevent a single point of failure within an availability zone. Basically, it is a group of virtual machines that share a common power supply and network switch. The reason it does this is that if part of the data center fails, other servers will go down and, let's say, there is a fire inside the data center and in a particular region, it will not affect the rest of the hardware. that is running, then you have updated domains.

So updating domains is when Azure needs to apply updates to the underlying hardware and software. But the thing is, because Azure is updating them, it takes these machines offline. So the idea is that if you run your workloads on another domain, like another, on the update domain, none of the domains will be updated at exactly the same time. And that way, you won't have any downtime due to updates. So the way fault domains and update domains work is that availability sets are used. Therefore, availability sets are a logical grouping that you can use in Azure to ensure that the virtual machines you place in the availability set are in different fault update domains to avoid downtime.

And to really help with that image here, what I'm going to do is show you this here. Therefore, each virtual machine and availability set is assigned a fault domain and an update domain. And what you're seeing here is you see those gray boxes, they're shelves. In your data center, a rack is like a server closet and all of those servers sit on top of each other. And then each of those servers is where you could deploy your virtual machine. So if you're deployed, if you have a server and it's deployed in full domain zero and fault domain one, it could be any of the servers in that rack, but then down to the domains, you might have very particular servers in that rack that are Those update domains.

Hopefully that makes everything a little clear and a little confusing. But remember the concept behind fault domains and update domains. And just to give you an idea of ​​what it would look like in the Azure portal, if you go ahead and create an availability set, whatever. So here I call it production. And you would choose the failure domains and you would choose the update domains. So I think what you're doing there is choosing the number of domains you want your VMs to be distributed across. And I keep saying virtual machine, that's your server, okay. So if you say two fault domains, that means that when you start two servers and put them into that availability set, they will have cross faults, two different fault domains.

And if you start five servers and your update domains are five, that means it will be on five different servers that are isolated from each other. Hopefully, that makes sense. But that's fault and domain updating. So quickly I just wanted to show you the default and updated domains that are in Azure here. So the idea is that if you're starting a virtual machine and you want to control the availability set, what you can do is go over here, where we have availability options, we'll roll it down. and choose the availability set. And then we don't have an established availability.

So I'm going to go ahead and create one, if I just click there. And so when we create a set, we say, you know, production set. And so we have these two, these two dialogues here. So what it is, when you say there are three failure domains, that means that if you were to launch three VMs and put them all into this availability set, they would be spread across three different racks, so if one rack goes out so that other racks are operational, so your service will continue to be available. And then below, it's the same thing in a rack, there can be multiple machines, and certain machines will be scheduled for updates, but not all of them will be updated at the same time.

So if you say this, you'll say spread it across five machines. And that's all there really is to do. So I just wanted to show you where that was, when you actually start it up for a virtual machine. Hi, I'm Andrew Brown from Exam Pro. And we're thinking about creating our own Azure account so we can get hands-on experience with Azure. So what I did here was I went to Azure dot Microsoft COMM. And that's what I want you to do too. And then when you're here, look for a free account, they have it everywhere. So they have it here and they have it here.

And I bet you could even get it by logging in. Well, what I'm going to do is just click on free account here in the top right corner. And then when it's here, we'll have another free home button. So we'll go ahead and click on that. And now we have to log in with our Microsoft account. Or if you don't have one, we'll create one, I'll create a new one. And I created an email just for this tutorial here. It's called Azure exam pro Co. And I'll have to set a password. So I'll just exit the screen and generate a password.

Excellent. So I generated a very strong password and I'll paste it in there. And I'm going to move on. So the next thing you're going to ask me is send me an email to my email there. And I will have to enter a verification code. So I'll come back here in a moment to show you that code. Well, I went ahead and checked my email and immediately received the verification code. So mine is 6599, yours will be different. So I'm going to go ahead and enter mine here. So it was 6599. And I'm fine, I don't need any advice or offers, and then we'll move on to the next thing.

And now before we continue, we have to complete this challenge here. So let's try it. So we have x and five, w w w Q. Okay. And so, after waiting a bit for this page to load, we have information. Then we have to fill in our information about you. So our country, your first name, last name, email, phone number, identity verification by phone, identity verification by card. Wow, they have a lot of steps here. And so we will continue our way here. So now I'm going to go ahead and fill out this information. And I'll see you here in a moment.

So I just completed the About Us section here. So what I'm going to do is continue with the next thing. And now it will ask me to verify my identity over the phone. So I want a text message. So I'll click the text me button. So I'm going to check my phone to see if there's that verification code. Then I received the text message for the verification code. I'm going to go ahead and enter it. So mine is 351033. Your codes will be different from my code. I'm going to go ahead and verify that code. Very good, it seems that it is going to ask us to identify ourcard verification.

So we're waiting for something to load here. So what we will have to do is enter the credit card information. So we'll continue here and fill that out. So I went ahead and filled out my credit card information, I'll move on to the next thing. Excellent. And now that it's verified, I can go ahead and click on the agreement. So I'm going to say I accept the subscription. And the second, I don't have to check the box. That is if I want to receive tips on offers. But I'll definitely check the first box because it's necessary and we'll go ahead and sign up.

Excellent. And now we are here. And it looks like we're ready. I suppose a live demo could be scheduled, which seems very generous of Azure. But I'm going to go ahead and head to the portal. And here we are, we arrive at Microsoft Azure. And what you're seeing now is the portal, which tells me that I have $250 in credits. If you're wondering why it's higher or lower than yours, note that it's in Canadian dollars. So I think it's 200 USD, when you convert my currency it's a little bit higher. And then it might be different for you.

But there you have it, that's all we had to do to create an account. And now we can start learning other things in Azure. Hi, I'm Andrew Brown from Exam Pro. And I just wanted to quickly show you that you can change your Azure Portal experience, if you just go over here and click on the gear, you can change the default view from home or dashboard, you can change the menu side here. , so it's docked, which is a lot easier when you're browsing things all the time. And if you want, if you want to change your theme, you can go to dark mode here.

Or you can even do high contrast. Very old school, but very pleasing to the eye. I just wanted to inform you of it. Because you may feel like you want to change your experience from the beginning. There you go. Hi, I'm Andrew Brown from Exam Pro. And we're looking at Azure Compute Services starting with Azure Virtual Machines. So the virtual machine will be the most common type of computing every time you start a server; I would simply think of a virtual machine. And your virtual machines could be running Windows or Linux operating system. Now, the best thing about virtual machines is that they offer a lot of configuration.

So you can choose your address, the amount of memory, the amount of CPU, you can attach storage to it. The problem here is that because it is a virtual machine, hardware shared with other clients can be dedicated, but is usually shared. And then you get a virtual computer. So it looks like you have 100% of the resource, okay, so we have Azure Container instances. So this I would describe as Docker as a service, you can run containerized applications, you probably run Docker on both Windows containers, because I think Windows has containers too, but you run containerized applications in Azure without provisioning servers or virtual machines.

That makes it much easier for you. The next one sounds very similar and is called Azure Kubernetes service. Therefore, it is Kubernetes as a service, easy to deploy, manage and scale containerized applications. So the idea here is that Kubernetes is just another way of working with containers. But it is using an open source library. Kubernetes has basically become the de facto container. And we've seen every cloud provider trying to create their own orchestration service or service, but Kubernetes is the only one left out. This is how you will see it on all platforms. Next is Azure Service Fabric.

This one can be a little confusing, because it is described as many things. But I will describe it here as a tier one enterprise container as a service, application or cloud service. It is for distributed system platforms, running in the Azure cloud or on-premises. And the way they described is easy to package, deploy and manage scalable and reliable microservices. And whenever you hear the word microservices, think about containers too. So with Azure Container instances and Azure Kubernetes services, that's where you also run microservices, then we have Azure Functions. So this would be event-driven serverless computing. Whenever we talk about serverless computing, we're used to talking about serverless functions, which are little bytes of code that you can simply upload.

And it just works. You don't have to think about servers or provisioning anything. And you only pay for the time that code runs. Therefore, serverless functions generally run for a very short period. And as soon as they finish, the underlying servers shut down. And the last one on our list here is Azure Batch. So you can plan the schedule and run your batch computing workloads across 100+ jobs in parallel. When I say jobs here, it's just the code you want to run. You can use spot virtual machines. Spot virtual machines may not be available at this time, but will be available in the future.

But they are generally known as low-priority virtual machines. But the idea here is that there are virtual machines that are being underutilized. Therefore, Azure allows you to rent them at a more profitable price. So if you're doing a lot of scientific calculations or other things, and it doesn't matter if these services go down and you want to use those low priority VMs, that's a great way to save. And those are computer services. Hi, I'm Angie Brown from Exam Pro. And we're looking at Azure storage services, starting with Azure Blob Storage. So I would describe this as serverless object storage.

So have you ever heard of object storage or service storage? This will make sense to you. Therefore, it can store very large files and large amounts of unstructured files. And the idea here is that you pay only for what you store. It's basically unlimited storage, no need to resize volumes, no need to worry about file system protocols, just upload files. And that's why it's considered serverless storage, then we'll move on to Azure disk storage, this is the most common type of storage you'll find. So we can describe it as a virtual volume. Then you are simply choosing an SSD or an HDD.

It's basically a hard drive in the cloud. It is encrypted by default and is connected to virtual machines. So whenever you're spinning up a virtual machine, it's probably spinning up as well as the disk storage attached to it. Then you have Azure file storage. This is a shared volume that you can access and manage like a file server. So it will use protocols like SMB, the reason you would want this is let's say you have multiple virtual machines, multiple servers and you want them all to share the same hard drive, that's what you use it for.

Or if you need users to access using those protocols. That's another way to do it. Then you have like queue storage, now I put an asterisk in front of it, because this is just a service with a strange name. Because this is really for a message queue. This is actually for the integration of applications that are listed here, because they put the word storage. So I think it has a bad name. And even the way you describe it makes you think it's storage. But it is a data store for reliably queuing and delivering messages between applications.

So two applications have simply been integrated and messages have been transmitted. Another one that's confusing is Azure table storage; I would put it in the database categories. And it is not a SQL database. And specifically, it is a wide column without SQL database. As they describe it, it is a SQL-less warehouse that hosts unstructured data independently of any schema. So keep in mind those two, they are just very poorly worded. Then you have Azure Data Box, and also its improved version, the Azure Data Box Heavy. This is a rugged briefcase, computer and storage designed to move terabytes or petabytes of data.

So imagine, someone shows up at your door with this, this tower, which is a computer and you plug in your USB or whatever you want. And you transfer all your files locally in your local data center, and then they send them because it's faster to send the data on a physical device than to send it over the Internet. That's what the Azure Data Box is. And then we have Azure file storage. So, this is long-term cold storage for when you need to keep the fake for years, but want the most economical storage options. If you have a lot of data.

And it's not, it doesn't do anything, you definitely want to install the cheapest storage devices possible. Cheap meaning doesn't mean they are unreliable, it just means they are not active, the disk is not active, it is not actively spinning, no one accesses the data on those hard drives. The last one is Azure, Azure Data Lake storage. This is a centralized repository that allows you to store all structured and unstructured data at any scale when working with big data from multiple different sources, and it used to be in one place, that's the service for you. And those are Azure storage services.

Hi, I'm Andrew Brown from Exam Pro. And we're looking into Azure Database Services; First on our list is Azure Cosmos dB. This is a fully managed SQL-less database. It is designed to scale with a 99.999% availability guarantee, as you love to talk about this database. It's their flagship database because it runs at incredible scale and with incredible performance. So whenever you think of super large databases, think Azure Cosmos dB. Next on our list is your SQL database even though it doesn't have its name. This is for the MS SQL engine. So if you're running Microsoft SQL, you'll want to use this.

It is fully managed with auto-scaling integrity, integrity, intelligence and strong security, and many great features built around these four MSL SQL databases. Now, if you're not using MS SQL and you're using something like MySQL, Postgres or MongoDB, they are the Azure database. Therefore, it is fully managed and scalable. With high availability and security. Then you have SQL Server on virtual machines. Again, it doesn't have its name, but it is the Microsoft SQL engine. Well? Whenever it says SQL servers, just assume it's Microsoft's version of SQL. And the idea for this one is that if you already have SQL servers running on-premises, within your data center, and you want to move them to Azure, this is where you use a lift and a shift.

So you take those virtual machines and move them directly to the cloud, you don't get all the functionality that you would get with Azure SQL Database. But it is the easiest way to access the cloud. Then you have Azure Synopsis Analytics, formerly known as SQL Data Warehouse, because they added an analytics component to it. But it is a fully managed data warehouse with comprehensive integrity and security at all low levels at no additional cost. Then you have the Azure database migration service, so migrate your databases to the cloud without changes to the application code. So there's that service, then you have the Azure cache for Redis.

So if you need an in-memory cache, i.e. using open source Redis, you can use it. And last on our list is Azure table storage. We mentioned this in storage services. But to me, this is a database, it's not a storage service, even though it's called that, so why isn't a column a SQL database, a non-SQL store that houses unstructured data, regardless of any scheme? There you have it, those are Azure Database Services. Hi, I'm Andrew Brown from Exam Pro. And we're looking into application integration services in Azure. Now, I didn't have room on the slide for this.

But just to tell you what application integration is, these are services that are designed to help applications or services talk to each other. It is basically the glue of the services. First on our list here is Azure Notification Center. This uses the publisher's subscription technology below. And this is to send push notifications to any platform from any backend. Next, we have the Azure API applications. So this is essentially an API gateway. So you can quickly create cloud consumption APIs. And then those APIs will have API endpoints and you'll be able to route them to Azure services, or maybe to functions or containers.

But it is a way to create an API in the cloud. Then you have Azure Service Bus. And as the name suggests, it is a service bus. Cloud messaging as reliable as a service, simple and massive hybrid integration. I know that's not very clear. That's the language Microsoft uses to describe it. But what you need to know is that it is a service bus and then you have Azure StreamAnalytics. This is real-time, serverless analytics. Remember that world word real-time and think about this service from the cloud to the edge. Then you have Azure Logic Apps. Therefore, it can schedule, automate tasks, business processes and workflows, and integrates with enterprise, SAS and enterprise applications.

Then you have Azure API Management. This can be confusing, because we have another service called Azure API Apps, I don't know what we would generally call the service. They say it's a hybrid multi-cloud management platform for APIs, across all environments, whatever that means. But when I looked at it, what it does is you can put this in front of an existing API to add additional functionality. So if you have an API, you put it in front of it and it's basically a proxy for your API, and you get all this extra stuff. Then last on our list is Azure Queue Storage.

We saw this in our storage service sections. And I said I don't really consider it a storage service, I consider it an application integration service. And this is a message queue. Therefore, it is a data store for reliably queuing and delivering messages between applications. There you go. Those are the application integration services in Azure. Hi, I'm Andrew Brown from Exam Pro. And we were looking at the developer and mobile tools commonly used with Azure. First on the list is Azure Signal, our service and this is a real-time messaging service, not to be confused with the Azure notification service.

This is to easily add real-time web functionality to applications. So if you've ever heard of pusher, it's like pusher. So that's the equivalent there. The next one we have is Azure App Service. Very easy to use service to deploy and scale web applications with dotnet. Without GS, Java, Python and PHP. I'm a little sad, I don't see Ruby there. But what are you going to do? Therefore, it is so that developers want to focus on creating their web applications and not worry about the underlying infrastructure. So if you've ever used Heroku, think of it like this, but for Azure.

Then you have Visual Studio and Visual Studio is a code editor. It is basically an ID development and integrated development environment designed to build powerful and scalable applications for Azure. You may have heard of Visual Studio code, which is similar but different. But I just wanted to mention Visual Studio here. Then you have Xamarin. I think I'm pronouncing it right. And it is a mobile application framework. It is for creating powerful and scalable native mobile applications, dotnet and Azure. And yes, those are Azure mobile and developer tools. Hi, I'm Andrew Brown from Exam Pro. And we're looking at Azure DevOps services.

So Azure DevOps is really just an umbrella service for a set of modern development services. And we'll jump to them right away. First of all, Azure Boards, if you've ever used a combat board, that's what Azure Boards are. And if you've ever used GitHub projects, it's literally because Azure and GitHub are owned by the same company, Microsoft. And then they brought that technology to Azure. So deliver value to your users faster by using proven agile tools to plan, track, and discuss work across your teams. Then you have Azure pipelines. So build, test, and deploy a CD that works with any language, platform, and cloud.

Connect to GitHub or any other provider and deploy continuously. So if you need automated deployments, that's what Azure pipelines are for, then you have Azure repositories. And this is exactly like GitHub repositories. Get unlimited code, private cloud-hosted Git repositories, and collaborate to create better code with pull requests and advanced file management. I really mean, it's like GitHub repositories, because it's just that the technology moved to Azure. And you have as a test plan, so test and ship with confidence using manual and exploratory testing tools. This is just one way to set up tests. Have you ever used something like Cypress or anything similar, or any other testing tool?

It's just built into Azure, it'll open a browser and literally test your app and make sure it works as expected. , then you have Azure artifacts, so create hosts and share packages with your team. So this is just package management, but specifically for ci cd pipelines, so ci cd pipelines, they have to configure the servers and you have to have pre-installed packages, that will make it a lot easier for you. The last one is the Azure Developer Test Labs. This is simply an easy way to create test environments for your developers. And those are Azure DevOps services.

Hey, I'm Andrew Brown from Exam Pro and we're looking into Azure Resource Manager. And just to understand the service, we understand what infrastructure as code is, also abbreviated as IAC. This is the process of managing and provisioning computer data centers through machine-readable definition files rather than physical hardware configurations or interactive configuration tools. If that's complicated, all it means is that we are using scripts, we are using scripts to configure fewer services like virtual machines, databases or storage. So you don't have to manually go through the interface or you can hand that script to another team or company and they can configure the exact same configuration that you have in a matter of seconds.

So the infrastructure code service for Azure is called Azure Resource Manager, or arm for short, and it allows you to programmatically create Azure resources via a JSON template. I'll just show you what that template looks like. So you would create this template and it will allow you to start a virtual machine. Okay, so instead of going to the interface, clicking and doing a bunch of things, you just define all the things you want to do in JSON. This is a very short version, it would definitely take a lot more setup. But here, this would be a very simple way to set up a virtual machine using code.

Hi, I'm Andrew Brown from exam Pro and we're looking into Azure Quick Start Templates. Therefore, Azure Quick Start Templates are a library of pre-built ARM templates provided by community partners to help you quickly launch new projects for a variety of stack scenarios. So on the last slide, we talked about Azure Resource Manager, where it's just a template or a JSON file to quickly configure resources. Well, that's taking that file and sharing it with other people, right, but it's shared through real providers. Okay, so you could go to the Azure quickstart. And let's say you want to deploy a Django application.

And I think it's also the scripts that the vendors and the community contributed. So if you want to deploy Azure or, sorry, a Django application, you can use that quickstart. If you wanted to deploy Ubuntu with a Docker engine, you could use that script. If you want a CI CD containerized application. with Docker Enterprise Jenkins, you could use that script. And if you wanted a web application that ran Linux with Postgres, you could use that script, so it's just a quick way to get started. Hi, I'm Andrew Brown from Exam Pro. And we're looking at Azure Virtual Networks, also known as V net, and the concept of subnets.

So a virtual network, and as we said, it means V net, is a logically isolated section of the Azure network where you start and your Azure resources. And when you create a virtual network, you have to define a certain number of IP addresses that you are going to use, what we call cider range. We'll come back to that in a moment. But here is a graphical representation of your V network. Here we have the Azure network. And then within that, we have a region, for example, US East, and then we would create our virtual network so that we can launch our Azure resources.

And there we have two subnets, one public and one private. And then in the public one, we have a virtual machine and in the private one, we have a database and at the end in the public one, you can actually have access to the Internet, where the private one is, you don't. Therefore, not all services require a V network. But most do because you simply have to put your resources somewhere. And they have to enter a virtual network, to which they are associated with an IP address, whether public or private. And then other network controls are involved.

Now let's take a look at the cider range. So the cider range, I said, is just an assignment of IP addresses that you're going to use in your virtual network. The only thing I want you to know is that C versus 10.0, point 0.0. That's the name of our network. But we have that slash 16. That's the variety of cider. And the lower the number, the greater the number of IP addresses you will get. I'm not going to go into math in this video, it's not necessary. But understand that slash 16 is a very large number. And that is the number of IP addresses we can launch.

Basically, we could launch 65,000 servers within this virtual network. And so we can subdivide our virtual network into subnets. It is a logical partition of an IP network into smaller network segments. So that's what you're doing, you're splitting into smaller IP ranges. And when you create subnets, they have to be smaller. Therefore, you must also define a range of cider for them. But they have to be smaller than the V network. Remember, I said the larger the number, the smaller it is. So when you have a 24 slash, it only says 256 IP addresses. Alright. And one more thing I want to point out is that we have things called public subnets, and private subnets, public subnets, reach the Internet, private subnets don't.

So when you have sensitive things like your database, you don't want it to be on a public subnet, but on a web application, which usually has traffic coming from the Internet. Alright. Alright. And that's all we need to know here. Hi, I'm Andrew Brown from Exam Pro. And we're looking at cloud-native networking services. Now, these networking services are not very, very important for the exam, but I like to review them. Generally I would make an architectural diagram for this, but it's a bit complicated. So I thought I would go through them and list them. So the first one is Azure DNS.

And we describe the service later in the course here. But this provides ultra-fast DNS responses and ultra-high domain availability. So if you have a domain name and you just want Azure to manage it, you can associate it with Azure DNS, then you have the Azure virtual network, we talked about this before, but we'll talk about it again, briefly. for V net, an isolated logical section of your Azure network for clients to launch Azure resources, then you have the Azure load balancer and as the name implies it is a load balancer but this one is at the level four transport.

So it doesn't really understand requests, like what a web application would send, it's a lower level. And that's what it is, then you have Azure Application Gateway. And this is an HTTP load balancer. Therefore, it understands requests coming from a web server. And what you can do with it is route based on HB requests to specific services. But you can also apply a web application firewall because it is an application load balancer. That's why you can use that web application firewall, which is a separate service, and then you have network security groups. This is one way to protect your subnets.

So it's a virtual firewall around your subnets where you can say, allow these ports to be open. And, and whose and and, and such. There you go. Those are cloud-native networking services. And the reason they are cloud-native networks is because you wouldn't use them with enterprise or hybrid models. It's just what you normally use. And most startups would use all these network and cloud services. Next we have business or hybrid network services. So this is when you're using networks. This will work locally in the cloud. So the first one is the Azure gateway. So this is a scalable and secure entry point for fast delivery of your global applications, like making sure you have a secure entry point to Azure from the outside, then you have Azure Express Route, you definitely want to remember this one for the exam. will probably appear as a question.

This is a connection between your on-premises system and the Azure cloud. And it can range from 50 megabytes per second to 10 gigabytes per second. I'm pretty sure it's safe too. But the point is that if you need a super, super fast connection, from your on-premises data center to Azure, I would use this Express Route service. Remember, you will be in your exam and then you will have a virtual LAN. Therefore, a network service that brings together many network security routing functionalities to provide a single operational interface. I know it sounds complicated, but awareness is just one way to facilitate creationof networks by creating a spoke model and then you have the connection to Azure.

Therefore, a VPN connection securely connects to on-premises Azure networks over IPsec. That's just one way to create a secure connection to Azure. Then you have a virtual network gateway, a site-to-site VPN connection between the Azure virtual network and your on-premises network. So it's just a way to connect with Azure. There you have it, those are the networking services. Hi, I'm Andrew Brown from Exam Pro and we're looking into Azure Traffic Manager. Therefore, this service operates at the DNS layer to quickly and efficiently route incoming DNS requests based on the routing method of your choice. So what you need to do is choose a routing method.

So we got performance weighted priority, geog, multi-value geographic subnet, and you will be able to redirect your traffic so you can route traffic to geographically nearby servers to reduce the latency of failover to redundant systems in case the primary systems go down. of being healthy, or routing to random VMs to simulate B testing, I think, like the best failover use cases for ADN at the DNS level, like it's great. And just a visual example here. Imagine if we had pro.co exam. And we had a production server and a beta server. And we only want 20% of our users to see the beta server.

So we could use, I guess we use weighted there and we would say 80%, in prod, 20%. There. And this is how it would work. There you have it, that's Azure Traffic Manager. Hi, I'm Andrew Brown from Exam Pro. And we're looking at Azure DNS. I told you we'd come back to this one because we're on the networking slides, but I didn't describe it in detail. So, since your DNS allows you to host your domain names in Azure, you can create DNS zones and manage your DNS records. So if you want to add a record, like let's say we have an example CO and DNS manages it as your DNS, we can add beta as a subdomain.

And we could use an alias to route it to a load balancer or a virtual machine. And then that would go into our record list. One thing that's interesting is kind of a disappointment, and that is that Azure DNS doesn't allow you to purchase a domain. So it only gives you the ability to manage DNS records; some other cloud providers allow you to purchase and manage, but only because their DNS doesn't right now, maybe in the future. Hi, I'm Andrew Brown from Exam Pro. And we're looking at the Azure load balancer, we just mentioned it briefly on the network services slide.

And then we'll see more of it here. So, as your load bounce is used to evenly distribute incoming network traffic across a group of resources or back-end servers, your load bounce operates at layer four of OSI, that's the transport layer. So it doesn't understand HTP requests, it just sends packets back and forth. So here is a graphical representation. So imagine you have internet and somehow it is reaching the load balancer, the load balancer will distribute it among your virtual machines, the virtual machines being your servers. And the best thing is that you can have virtual machines in different availability zones, and the load balancer can distribute them between them and that is how we get high availability.

Well. And now with Azure Load Balancer you can create a public load balancer i.e. incoming internet traffic to public servers or servers that have an internal public IP address or a simpler way described would be a load balancer private, so incoming internal network traffic to private servers, i.e. private IP addresses, there you have it. Hi, I'm Andrew Brown from Exam Pro and we're looking at scale sets. This allows you to group identical virtual machines and automatically increase or decrease the number of servers based on change in CPU, memory, disk network performance, or on a predefined schedule.

So when we talk about elasticity, we are talking about the use of scale sets with the ability to automatically increase or decrease the number of servers. So here is a visual representation. Imagine you have Internet traffic and it hits that load balancer. And then we determine that the current load on the existing server is greater than 80% CPU utilization, so some additional servers will be needed. And what happens is the skill set decides, okay, we're going to have to add one or two more servers. And when CPU usage drops below 80%, he says, okay, we don't need those servers anymore.

Get rid of them. Well. Those are sets of scales. Hi, I'm Andrew Brown from exam Pro and we're looking into IoT services in Azure. And before getting into the matter, what is IoT? So IoT means Internet of Things. So, a network of Internet-connected objects, usually hardware, capable of connecting and exchanging data. Here is a graphical representation of IoT devices, you may recognize some, let's go over a quick list of things that could be IoT devices. Then you have smart light bulbs, so maybe there are light bulbs in your house that are controlled by the Internet. Smart refrigerators who don't want one of those smart light switches, narrowband hardware or broadband, this is just one way to connect to the Internet, it's like Wi Fi.

Then you have security cameras, then you have voice command speakers. So think about Alexa, then you could have temperature, pressure or humidity sensors, if you are in the agricultural industry you can leverage IoT devices for that. Maybe you have drones, maybe you have phones, which could be an IoT device, and even buttons. So AWS had these things called AWS or dash buttons. They were not popular. But the idea was that you could press a button and like it and buy something. So if you always had to get soap for your washing machine, you could have that button right on your washing machine.

But let's actually talk about IoT services here. So the first one here is IoT Central. This allows you to connect your IoT devices to the cloud and then you have IoT Hub. This enables highly secure and reliable communications between your IoT applications and the devices you manage. Then you have IoT Edge, it is a fully managed service built into Azure IoT Hub and allows data processing analysts to get closer to IoT devices. So this is really edge computing, I really should have highlighted that. But this is where you can offload your computing from the cloud to local computing hardware, such as IoT devices, phones, or home computers.

Therefore, it is just a way to save money or use your local network for calculations. Then you have Windows 10, IoT Core services. So this is a cloud services subscription that provides the essential services needed to bring the device to market on Windows IoT, or 10 IoT Core, so it's basically long-term support and services to manage device updates and evaluate its state. Alright, there you have it. Those are your IoT services. Hi, I'm Andrew Brown from Exam Pro. And we're looking at big data and analytics services in Azure. So before we get into it, let's talk about what big data is.

Therefore, it is a term used to describe massive volumes of structured and unstructured data that are so large that it is difficult to move them in the process using traditional software and database techniques. That's why we need special services just to handle them. First on our list here is Azure Synopsis Analysis, formerly known as SQL Data Warehouse. The same goes for enterprise data warehousing and big data analytics. Therefore, it is intended to run SQL queries against large databases to generate things like reports. Then you have HD Insight HD is short for Hadoop. But anyway, it runs open source analytics software, like Hadoop, Kafka, and Spark.

I figured it would be called HD Insight because it only supported Hadoop and then they added additional services, but that's what it's called. Then you have the Azure Data blocks. Therefore, we have a Spark-based irregular analytics platform optimized for Microsoft Azure cloud services platforms. So, the creators of Spark created third-party data, blocks, cloud service support with Azure, that is, data blocks. And yes, of course, you can run Spark on HD Insight. But Data Bricks is their own cloud service provider and Azure has partnered with them so you can use it within the Azure platform. Then there is data lake analytics, that is, an on-demand analytics job service that simplifies big data.

And we looked at what data lakes were when we looked at storage services, but we'll describe them here in a moment. In another way, a data lake is a storage repository that holds a large amount of raw data in its native format until it is needed. There you have it, those are the big data and analytics services we need to know about. Hi, I'm Andrew Brown from Exam Pro. And we're looking at AI and machine learning services in Azure. So a great way to describe this is to always have this graph here where we have this kind of onion where each one depends on the other.

And we will start with artificial intelligence. So what is artificial intelligence or AI? These are machines that perform jobs that imitate human behavior. Now, that doesn't mean the technology behind it has to be complex. It could be if all statements, but it could be using machine learning, it could be using deep learning. But the point is that if it mimics human behavior, then you have machine learning. And this is where machines come in that get better at a task without explicit programming. Then they are smart enough to learn on their own, then you have deep learning.

And so deep learning is where machines that have an artificial neural network inspired by the human brain can solve complex problems. Literally, it's like the power of the human brain. Maybe not as good as the human brain, but close enough. And AI could take advantage of ml and deep learning. That's why it is like this. So when we want to do machine learning in Azure, they have a service called Azure Machine Learning service. So, this is a service that simplifies the execution of AI and ML related workloads, allowing you to create flexible pipelines to automate workflows.

So you can use Python and R, you can run your deep learning workloads using technologies like TensorFlow. And that's what you would use. Now, there was a service called Azure Machine Learning Studio, I think it still exists if you're still using it. And that is the classic version of the service. And it does basically what the Azure Machine Learning service does. But there are some limitations. So it doesn't have a pipeline or other functionality. And if you're wondering if you could easily migrate from classic to the other, it's not easy to migrate. Basically, you'll definitely always want to start with Azure Machine Learning Services.

There is no reason you would want to use Azure Machine Learning Studio unless you are using it for legacy reasons. Hi, I'm Andrew Brown from Exam Pro. And we're still looking at AI and ml services, specifically just AI services, because Azure has a lot of them, and I'll go through them quickly and they're self-explanatory. So the first one is personalized and offers rich and personalized experiences for each user using AI. Then you have the translator that adds real-time multi-language text translation to your apps, websites, and tools. It has an anomaly detector that detects anomalies and data to quickly identify and fix problems.

Azure Intelligence Service Bot Service, a scale-on-demand bot service, form recognition, Recognizer automates the extraction of tables and text key value pairs from your documents. It has computer vision, easily customized computer vision models for unique use cases, and language understanding, so you can develop natural language understanding in apps, bots, and IoT devices. We have a Q&A builder, so create a Q&A chatbot from your existing content. Text analytics, which extracts information such as sentiment, key phrases, named entities and languages ​​from your text, content moderator, moderates text and images to provide a safer and more positive user experience. face to detect and identify people and emotions in images, ink, recognizer recognizes digital and ink content, such as handwriting forms and document layouts.

There you have it, they have a lot of services and they haven't even had time to create all the icons for them. That's the amount they have. Hi, I'm Andrew Brown from Exam Pro. And we're looking at serverless services in Azure. So what is serverless? This is one of the underlying servers or server infrastructure and the operating system is provided by the service provider inCloud; will generally be highly available, scalable and cost-effective. Therefore, serverless technology relies on events at scale. Therefore, you can activate a service function or trigger other events that allow you to compose a complex application and simply scale it.

So with serverless technology, it's like playing with Lego blocks. Then you have server abstraction, so servers are abstracted and their code is described as functions. These functions can be executed on different computing instances. So if some people like to use Python, or some people like to use JavaScript, you can mix and match there. Then you have microbilling. So when you have traditional servers, you're probably billed at least per second or hourly. But the thing is, if you don't use the server for the entire second or hour, you're paying for the process you're not using. Therefore, serverless functions will bill you in a microsecond.

Therefore, you are saving money because you are not paying for unused calculations. Now, let's quickly go over some of the serverless services. I'm sure there's more to it than this, but this is what I think is worth highlighting. So the first one is Azure Functions to run small amounts of code known as serverless. functions in your favorite languages, you have C Sharp, Java, JavaScript, Python and PowerShell. And if Azure is listening, can you please support Ruby, because I love using Ruby. Then you have blob storage. So this is serverless. object storage, just upload your files, don't think about resizing the underlying filesystems, basically unlimited space, and you can upload quite large files.

Then you have Logic Apps which allows you to create serverless workflows composed of Azure Functions, building, I would say you're building a state machine for serverless computing, then you have an event bridge, which looks a little similar, but I don't. is. pub messaging subsystems to allow you to react to events and trigger other Azure cloud services, such as Azure Functions. There you have it, that's serverless services. Hi, I'm Andrew Brown from Exam Pro. And we're looking at the Azure portal. Therefore, the Azure portal is a unified web-based console that provides an alternative to command-line tools. You can manage your Azure subscription with the Azure portal, creating, managing, and monitoring everything from simple web applications to complex cloud deployments.

So what does that mean? It simply means the browser you use to access Azure. So whenever you sign in to Azure, that's the portal, that's all you need to know. There's another thing about the Azure portal, and it's the Azure preview portal. So the thing is, sometimes there are new features or new products that Azure has created that aren't necessarily generally available, but you can check them out first if you use the Azure preview portal. They could be previews, beta versions, or other early versions. So the way to do it is very similar to how you would access the normal portal.

But if you want to try a preview of the new features, go to the

azure

.com points preview portal. Or if you're looking for a stable, in-production, feature-ready version, just use Portal Dot Azure Calm. That's all you need to know about the Azure portal. So I just wanted to quickly show you what the portal looks like. We will show you in this course how to create your own account and work within the portal. I already have one set up here. And I'm already logged in. And if I go to the top here, now I have this portal link.

And when I come in here, we can see what the portal looks like. This is the portal, you can see it tells me about my expenses, but I'm in the dashboard. Right now, on the left side, we have this hamburger menu where we can explore the services, we can go up here and search for them as well. So whatever you're looking for, if it's a monitor, we can go there. And that's pretty much it. This is the portal. So it's just the browser when you log in, you can interact with any cloud resource. Hi, I'm Andrew Brown from Exam Pro.

And we're looking at PowerShell for Azure. First of all, what is PowerShell? So, PowerShell is a task automation and configuration management tool. But an easier way to look at it is that it is a command line shell and it is also a scripting language. And so when I say command line shell, I mean this thing, this blue thing. So if you have a Windows machine, I think you should have Windows Professional, but you can go ahead and install this. And it allows you to automate things using your scripting language as well as in this program. PowerShell is now also available in Azure.

And we'll get to that for a moment, let's just talk about the benefits of PowerShell over traditional shells. So shell could be something like bash or Zed sh, which would accept and return taxes. But PowerShell is built on top of dotnet Common Language Runtime, so CLR. And accepts and returns dotnet objects. So those objects make it much easier to automate scripts. That's why PowerShell is available in Azure and is known as Azure PowerShell. And then we have a set of commands to manage Azure resources directly from the PowerShell command line. And if you're wondering how you would access PowerShell, you can use Cloud Shell, which we'll talk about here in a moment.

Okay, I just wanted to quickly show you PowerShell. I'm on my Windows computer right now. And this is installed natively on my Windows 10 computer, and I can type commands here. And this is just give me a list of all my directories in this current folder. But I also want to show you that we have PowerShell here in the Azure portal. So I'm using Cloud Shell here and I chose to use PowerShell. And you can see that it's pretty much the same experience with a few extra things that make working in the cloud easier. That's all. Hi, I'm Andrew Brown from Exam Pro.

And we're looking at Visual Studio code. So, Visual Studio Code is a free source code editor, that is, your code created by Microsoft, for Windows, Linux and Mac OS. And you can even run it in the cloud. If you're wondering what it looks like, this is the editor. And this should not be confused with Visual Studio. So Visual Studio is an identification and it is also used for programming. But it has many built-in functions. Is Visual Studio Code open source? Well they say it is but I don't know to what extent I don't know if it is 100% open source.

But this is the most popular text editor or code editor out there right now. And Microsoft has, or I'm sorry, Azure has a service called, like, Visual Studios workspaces, which is in Azure and allows you to spin up these developer environments using this editor directly in the cloud. I don't think it's on your test. But I thought it was cool to mention it. And if you don't have a code editor, I recommend downloading this one for your computer because it's great. So I just wanted to quickly show the Visual Studio code here. So if you want to download it yourself, just type the Visual Studio code into Google.

And you should end up here, you can download a version, it's for Windows, Mac and Linux, so you can download it for anything and run it in the cloud on Azure, or even start your own server on other cloud providers. I happen to have Visual Studio Code open here with an open source project. Just to show you what it looks like. What people really like is that it looks great and has really good accessories. So if I just go to the extensions here, you can add anything you need and enhance this editor here. If you don't have a code editor, I recommend downloading it.

And I just wanted to get you familiar with this editor. Hi, I'm Andrew Brown from Exam Pro. And we're looking into Azure Cloud Shell. Therefore, Azure Cloud Shell is an interactive, authenticated shell that can be accessed through a browser to manage Azure resources. And therefore, it provides the flexibility to choose the Shell experience that best suits the way you work. So you can use bash or PowerShell, we just talked about PowerShell. And this is the place where you can use it in Azure. So just to give you an idea, if you ever want to access the Cloud Shell, it's in the portal header.

And then you click on that button, it opens PowerShell or it depends on what you choose, but it will open it below. And then you'll be able to use PowerShell right away and also CLR right away, which we'll talk about next is Azure Salesforce. Hi, I'm Andrew Brown from Exam Pro. And we're looking at Azure ver ally. So what is CLR? CL Eyes means command line interface. And processes commands to a computer program in the form of lines of text. And the operating system implements a command line interface in a shell or terminal. So we saw a shell before, which was PowerShell.

But we'll see what the CLR commands look like here in a moment. Therefore, Azure COI can be installed on Windows, Mac and Linux. Once installed, you will need to type A z followed by other commands to create, update, delete, view, and manage your Azure resources. And to really show you what that code looks like, below we have a bash script. But this could easily be PowerShell. And you have the AZ commands and then you will have what it is that you want to do. So if you want to create a group, type group C, create an E, and provide the name and location.

Or let's say you want to start a virtual machine, which is a server that creates AZ VM and then provides those other parameters. This is how Azure resources would be created programmatically. And there are tons and tons of ci commands for Azure. So basically anything you're looking at can be created with the CLR programmatically. Hi, I'm Andrew Brown from exam Pro and I'll show you how to create resource groups. And the reason we're going to create one is because without one, we won't be able to launch virtually any resources until we do because you always have to choose a resource group when launching Azure resources.

Even if it appears here in our dashboard, if it doesn't appear, I want you to go up here and type resource group. And we'll go ahead and click on resource group here. And then on the left side, I want you to click Add. And we'll just have to use our free trial, which is our type of subscription. I'm just going to type exam pro as a resource group. We'll stay in the Eastern US, because that's where most Azure services are available and that's what I'll be using at all times. This course always uses US East. So we're going to come down here and press Create more, review, more, create.

Because there really is nothing more to check. And once you pass the validation, this could happen instantly for you, you may have to wait a few seconds, go ahead and hit Create. And now we have created our resource group. And there is no cost resource pool. So no need to worry about happiness, or if you keep it, don't delete it, or if you notice that the group hasn't appeared yet, you'll have to hit refresh. And sometimes Azure takes a while to display resources when you initially create them and when you delete them. So I'm going to wait a little here.

And I'm going to keep refreshing myself. And I'll see you back in a few minutes. Okay, I waited a couple of minutes. And if you continue here and hit refresh, we can now see that we have our resource group. So that's all there really is to do. There's nothing very exciting there. I'm just going to click on Microsoft Azure at the top to go back to my dashboard. And see you in the next follow-up. Hi, I'm Andrew Brown from Exam Pro. And we're going to consider how to create our own virtual network. So we create a resource group, but we also need a virtual network or V net.

So we actually have some network to cast our resources. So what I want you to do is go all the way to the top here, and we're going to go ahead and type V net, which will get virtual networks and go ahead and click on that. If you realize, you don't have any network. So we'll have to go ahead and create our own. So go ahead and hit the Add button. And we're going to have a bunch of options here, I'm just going to name this, or sorry, we're going to choose that resource group. So exam Pro, and we'll just call this exam pro v net.

And there are some additional steps here, we'll just take a look here, we don't really need to change anything, but we'll just take a look. So for the IP address you can set the IP address space, the default value will be 10 points 0.0 416 which is very good for us, you can see it supports ipv6 which is great. It's going to create a default subnet for us that's going to be 10 points 0.04, forward slash 24. It's going to be a subnet with like 256 IP addresses, which is great. Go to the Security tab, we have basic DDoS protection and you'll definitely want to stay there because it's free.

The same goes for the firewall, we don't want it activated because it will cost extra money. I'm going to go back to basics, we'll hit review and create, we'll just wait for the validation to complete. This may be instantaneous for you, or you can wait a few seconds, it's different for everyone. And now that the validation is complete, we'll go ahead and hit Create. ANDthen we will simply wait for it to finish creating. Great, that's how it's created. So it just says that the deployment is underway. So we'll have to wait a bit until the deployment is complete, it's already done super fast.

And we'll go ahead and press go to resource. And now we are in our virtual network. And we have a bunch of settings on the left side. So address space, subnets, etc., etc. We don't need to know anything at this level, we just need that virtual network to be able to launch resources. Now that we have resource groups and virtual networks, we can start launching resources. So there you have it, see you in the next follow-up. Hi, I'm Andrew Brown from Exam Pro. And I'll show you how to start your own server in Azure. Therefore, a server would be considered some type of computing service.

And what we are going to do now is use virtual machines. So go to the top to search, I want you to type a virtual machine. I know it's on our board here. But to get used to always being able to find things, it's great to use search. And then once we're here on the left side, I want you to click Add. And we will be presented with many different options. So the first thing we need to do is choose our resource group, we have another resource group that was created here for us for Azure, I wouldn't worry about it, let's just choose the one we created.

I'm going to name this virtual machine, I'm going to call it my VM, we're going to boot it into USB. If we want to choose an AZ, we could go to the availability zone and choose one. I'm just not going to stick with any infrastructure, so we have Ubuntu here, you're using the latest version, it might be different for you, I would. Don't worry too much about that. Then we have to choose our size. This will really determine our cost here. This is $89. Canadian, I'm going to go ahead and press select here. And we're just going to sort on the right side by cost and choose the cheapest server, which is the b1 Ls.

That's a VPC, eu and half a gigabyte of RAM. Because this is just an example application. We are not going to make a server or we are not going to do anything with it. So we should also make sure not to spend our free credits too much. We have the option to add a public key. This is what you would generally want to do. But that's a lot of work. And for this demonstration, we'll just choose the password. They are very picky about passwords here and they have to have a special upper and lower case character.

Number, and it also has to be 12 characters. So I'm going to write test with a capital T test, 123, exclamation exclamation, and then test with a capital T 123. Exclamation explanation. So here we go. We don't need any input port, I will say none because we are not SSH. Again, I'm going to click here to show you some of the other options. Then we could choose the type of disk we would connect. So by default it is on premium, you may want to use standard or standard HDD. Generally when you launch web applications you want SSD, if we choose standard I would say hey you should really go with premium.

So back to Premium, you'll notice that the drive is encrypted by default, so you can't have an unencrypted drive. That's a very good default option. If we go to networks, it will automatically select our V network that we chose and the default subnet that we created when we created the V network. And then here we can choose whether we want an IP address or not. If you didn't have an IP or a public IP address, you would still have a private IP address. And that would mean that you would like it to actually be destined for a private subnet.

You have a network security group set to two basic here. And that's it, you can also put it behind a load balancer, we're not going to do that. Let's go to administration, administration, we have a couple of options here, like identity, auto close, close backup, this is all good, we will leave it only for advanced, we could put custom data in here, that means we could provide you with a script that you would use to initially configure the server, but we're not going to do that. And that's it. So I'm going to go back to basics, scroll to the bottom and hit review, review, create.

And what we will have to do is wait for this validation step. That was very fast, it may have taken several seconds, or even a minute. But sometimes it's faster than others. So now I'm going to go down and press Create. And we're just going to wait for that deployment to ship, which will say that the deployment is underway. And soon, it will say that the implementation is complete. See you here at a time when the implementation is complete. Great, so we had to wait a few minutes there. And now it says the implementation is complete.

And we can press proceed to go to the resource. And here is our virtual machine, we have some CPUs and networking on the disk. So there's some activity here. If we wanted to access it, there should be a Connect button here, we won't be able to access it, because we just didn't configure it somehow. That was the case, we have some options on the left side, like the disks that are actually connected to it, and maybe the size here. So if we wanted to resize, change it to a larger size, we could go ahead and do that.

But there's nothing really exciting to do here, I just wanted to show you how to start your own virtual machine. And now that we have our own virtual machine launch, I'm going to go back to the overview, we're going to go ahead and remove that because now it's costing us money. It's not costing us much money. But again, we're done here. So we'll just go ahead and delete, we'll say yes to delete. And now it says it is still in the virtual machine. And then we'll wait until this is over. And a lot of times, you can see the progress up here.

And it will say that deleting the virtual machine could take a few seconds, it could take a few minutes, it just depends. So I'll see you here in a moment when I finish deleting it. So after waiting a bit here, it says that this is how you successfully deleted the virtual machine. If we want to make sure it is removed, let's go to virtual machines, the interlocutor in the search. And you'll notice that it still appears there. But it said it was eliminated. And the thing about Azure is that it takes time to propagate. So what we're going to have to do is just hit refresh and it's gone.

So keep in mind that sometimes the consistency in terms of what you see in the UI lags a bit. So if you remember clicking Delete and it says it deleted it, just be a little patient, hit Refresh, and check again to make sure that's the case. There you go. Good, excellent. Now that we've done that, let's learn how to do a different type of computing, which is serverless functions. So if we want to start our own serverless function, by the way, if it's not on the screen, just click on Microsoft Azure here at the top. And we're going to go to our search and we're going to type in functions.

And so, on the left side, I want you to click Add. And then what we're doing is creating a function app. So let's take our free trial. Let's choose our resource group that we created earlier, we'll give it a name. I'm just calling it, these are the names of the function apps. I just saved my app. My app is not available yet. They are all unique nicknames, I just call the app exam pro, you may have to change this a few times before you get what you want. And then for publishing we'll use code, we don't want to use a Docker container, that's too much work.

And we will only use node js, which is just version 12 of JavaScript. I think that's great, let's change this to make sure you're east. To make our lives a little easier, there's nothing wrong with Central, I just want everything to be consistent. So everything is very predictable in these. In this follow-up, we'll go all the way to the top and look at hosting quickly here, we'll see that we have a storage account. Well, there's nothing exciting here, it'll be Linux or Windows, we don't really care about this, we can just let it be Windows, go back to basics, I'll go ahead and hit review plus create.

So we'll wait for this validation step to complete here. Again, it could take a second or a minute, it just depends on the day with Azure. So we'll wait here for a while. Here we go. It has just finished validating, go ahead and press Create. And now we're waiting for that initial deployment. Then we will see that the deployment is on its way and then we will have to wait for the deployment to complete. So it's in progress, it's underway, this shouldn't take long and we should say it will be complete here in a moment. Excellent.

So after waiting a few minutes, our deployment is complete, we'll go ahead and hit go to resources. So now what we have to do is create a function ourselves. So, on the left side, go to the functions. And then here, let's add ourselves a new function. And so we have a lot of presets here for us, it won't matter what we choose, as long as you do it, and I'm going to say, let's choose the HTTP trigger, we'll leave it with a default name, okay. , we'll keep it as a role for the authorization level, we'll go ahead and create that role.

So once that function has been created here and is ready, let's start adding our code. Because again, the whole point of serverless is that you don't have to worry about servers, you just add your code and it works. And here is a code that you already have for us. What I'm going to do is just add myself a console log. console. log is like saying hello world. So let's say hello world. And then I'm going to press save. And now it's just connecting to Application Insights. I don't know if he's actually running it. Yes, it is connected.

Excellent. And now let's go ahead and do the test. So we have a bunch of options here, I'm not going to fill anything in, I'm just going to hit run. And let's see what the result is. Good, excellent. You know, I'm just seeing how this really works. And I think what we need to do is pass a name and to the query string here. So what we're going to do is we're going to go ahead and type a query here, we're going to put in a name and we're going to say, Andrew. Um, and that should be enough.

So just hit the run. Good, excellent. Then he says, Hi, Andrew. There you go. That's all you have to do to create a serverless function. And it costs us nothing to maintain this. So we don't necessarily have to delete it. If you wanted to remove it, I guess we would come back here, we would have to go back to the functions here. And I'll just click Delete. Here, we will type Yes, press Delete. And there you have it. That's all there is to it for serverless computing, go back to Microsoft Azure here, go back to the dashboard.

And see you in the next follow-up. Hi, I'm Andrew Brown. And in this video, I'm going to show you how to set up blob storage. And if you remember from the actual course, Blob Storage is like serverless storage, so you don't have to worry about running out of space or resizing your disk. So let's get to it. At the top, I want it to write blob storage. And you're going to go to storage accounts. And this is where you end up creating all your storage accounts, you can see we have a couple of virtual machine storage devices and when we create the serverless function there, so go ahead and hit Add.

And what we're going to do is choose exam Pro, or what you called yours when we were in the resource groups step. Then we'll have a storage device and I say my blob storage. Oh, that would be all lowercase in my blob storage. And that's already taken. So we'll say blob storage pro exam and it can't have scripts. Here we go. And then we will launch it in the eastern US. We have the difference between standard and premium. I think we'll stick with the standard. We have storage type v2, or v1 or Blob Storage, we want Blob Storage, we have some replication options here, I'll just leave it as is.

We have access here hot or cold, we'll just leave it hot. And we can just look at networking here for a moment, we'll leave this as it is, we'll just look at what's advanced for the moment. So, nothing exciting there, we go back to the basic visit review, other than creating, we will have to wait for validation. We'll go ahead and now press Create. And then I should say implementation in progress, we're waiting to see the implementation complete, you might be getting into the swing of how to qualify services now, it's almost always the same process.

And we will wait here until this is complete. Good, excellent. So I waited a minute there. And now, that's all set up. So let's go ahead and press go to resource. And then we have a lot of things here. So what we want to do is start uploading files. But I think first we have to create a container to get over here, to the left side and go to the containers, let's create a new container, I'll call it Star Trek,It will be a private container. So it's just for me, we'll press Create. And now we should be able to click on that container.

Alright, now that we know we have that container, what we can do is go ahead and upload our first file. I happen to have a file here on my desktop. So I'm going to select it there and upload it. All the default options are great here, we'll just hit load. And there we go. Then we simply upload a file to our blob storage. Yes, that's all there really is to do. Now that we're done, we can go ahead and delete this container. So I think we'll go back to storage accounts. I'm not sure if we need to remove the containers first, I guess we'll find out.

And we'll just go over here to Blob Storage, go ahead and hit Delete. And we will give it to yes, we will go to eliminate. And there you have it. So go back to Microsoft Azure there and go back to your desktop, and I'll see you in the next follow-up. Hi, I'm Andrew Brown from Exam Pro. And I'm going to show you how to use Cloud Shell. So if you want, it doesn't really matter where you are, because Cloud Shell can be accessed from anywhere. When you are in the Azure portal. It's actually this icon up here.

So what I want you to do is go ahead and click on that. And what it will do is ask you if you want bash or PowerShell. I'm going to choose PowerShell, we'll use our free tier and we'll need to create some storage with it. I'm going to drag it up a little bit. So we'll wait for it to create that storage device. Now we see this blue screen, which is very typical of PowerShell. And then you will have to initialize our accounts. So let's wait here a little bit until it's done. Excellent. And now we have our Cloud Shell.

So one of the advantages of having Cloud Shell is that if you want to do CLR and start doing things programmatically, within Azure, you can do that very easily here. So now we have the CLR installed, we can just type AZ, type clearly here, AZ account list. And there we go. We have account information there. That's all I wanted to show you for PowerShell, we can continue here and I think we can just turn it off, or that would restart it, we just press X. And there you have it. That's all. Hi, I'm Andrew Brown from Exam Pro.

And we're looking at the Azure Trust Center. All it is is a public web portal that provides easy access to privacy, security and compliance information. There it is, that's the portal. If you type Azure Trust Center, that's the way to access it. And the idea here is that you know, whatever information your organization needs, it's public, so you don't even have to log in to access it. But it simply helps you make security decisions for your company. Alright, I went ahead and went to Google and typed in Microsoft Trust Center. And this is the page here.

So if we scroll down a little bit, we'll see that we have Microsoft Azure. And here we have a lot of options where we can read about their security, privacy, privacy and compliance. Let's go to Azure compliance. and here we can see a list of various compliance programs that Azure is complying with. So we have a lot here. So if we go into GDPR, it may ask us to log in. So I'll put pressure on Andrew, in Canada. And I agree. Well, now I can read all about the GDPR. This gives me a lot of detailed information about this compliance program and how it applies to Azure.

There are many interesting things here. I'll come back here and we can click on security. And there is only generalized information here. But in general, what you look for when you come here are really these compliance programs. That's what everyone always looks for: reading about that topic in detail. And that's all you have to do to get there. So yeah, there you have it. Hi, I'm Andrew Brown from exam Pro and we're looking at compliance programs for Azure. Therefore, companies will not buy your software solutions unless they are secure. So how would you go about meeting your security compliance requirements?

And that's where compliance programs come into play. Basically, a company will tell you that we will only do business with you if you comply with NIST, or if your P IP gives, or if you comply with HIPAA. Or if it's FIPS compliant, 140, dash, two, you might say, well, that's a lot of things. But you know, after a while, you start to remember them. But it's extremely daunting at first, but I thought it would be fun to go over some of the compliance programs. And in fact, it might help you on your exam, they may ask you about some of these programs.

So we'll just go down the list. The first one here is the Criminal Justice Information Services, the CGI. Therefore, any US state or local agency that wishes to access the fpis cgis database must comply with this security policy. That's your compliance program. Then you have the Cloud Security Alliance star certification. This is an independent, third-party assessment of cloud providers' security posture, then there's general data protection, regulation and GDPR. A European privacy law therefore imposes new rules on companies, government agencies, non-profit organizations and other organizations that offer goods and services to people in the EU or collect and analyze data linked to EU residents.

So if it's data in the EU you need to worry about the GD p r. It has EU model clauses, that is, contractual guarantees around transfers of personal data outside the EU. Then you have HIPAA. This is the one you'll want to remember: the Health Insurance Portability and Accountability Act. So, for the US federal law that regulates patient protected health information, whenever you're dealing with hospital matters, you're dealing with HIPAA, so you have ISO 27018. So, this is an international standard. And it is the code of practice that covers the processing of personal information by cloud service providers.

It's good to remember it. Then we have Ida. This is a multi-tier cloud security, Singapore outside of Singapore, it's the Singapore organization, but this one is called mt CS. Very operational. Singapore Security Management Standard, a standard, a common standard that cloud service providers can apply to address customer concerns about the security and confidentiality of cloud data and the impact on cloud businesses. use of cloud services, it is not something you should remember but it is interesting to know. this one you want to remember sock service organization control One, two and three independent third-party examination reports that demonstrate how the company achieves key compliance controls and objectives.

I know I'm very sorry. Then we have the CSF Cybersecurity Framework from the National Institute of Standards and Technology NIST, you'll definitely want to know this one. It is a voluntary framework consisting of standard guidelines and best practices for managing cybersecurity-related risks. Then there's the UK government's G Cloud. That is the cloud computing certification for services used by government entities in the UK. And the last one is FIPS. And we will be talking about FIPS. Again, in this course here. This is the US and Canadian government standard that specifies security requirements for cryptographic modules that protect sensitive data.information.

There you have it, they are compliance programs. Hi, I'm Andrew Brown from exam Pro and we're looking at Azure Active Directory. So, Azure Active Directory, abbreviated as ad, is Microsoft's cloud-based identity and access management service, which helps your employees sign in and access resources. If you work for a larger company and use Microsoft products. They are probably using Active Directory and you are already familiar with this. But if not, let's learn about it because it is a very important service for the Azure and Microsoft ecosystem. Then the Azure directory would work with external resources. So maybe it would give your Office 365 access to the Azure portal, which is what we're using for two different types of SaaS applications, and it could also give us access to internal resources.

So if you have applications running within your network, or perhaps you are using Azure Active Directory to access real workstations on premises, that is, real workstations with Azure Active Directory, you can implement single sign-on . And Azure Active Directory comes in four editions. So we have free, which provides MFA SSO, basic security and usage reporting, user management, then we have the next level up to Office 365. And by the way, each version has the features above. So with Office 365 apps, you get company-branded SLAs for syncing between on-premises and the cloud, which is really nice. For the premium, you get hybrid architecture, advanced group access, conditional access and then premium to have identity production and identity governance.

But if I didn't make it clear, active directory is what is used to help your employees log in and access resources. That's what it does, it controls access to resources. There you go. Hi, I'm Andrew Brown from Exam Pro. And we're looking at multi-factor authentication. So what is the MFA? So MFA is a security control where after you enter your username, or maybe three emails and password, into a login portal, this login portal could be the Azure portal, this It could be you logging into Facebook, the idea is that you should use a second device, such as a phone, to confirm that it is you logging in.

So why do we use MFA? Well, MFA protects against people who have stolen your password because they may have your password, but they don't have your phone or whatever device you're using for MFA. So, MFA is an option that most cloud providers have. And just like I said before, most social media websites have it. So Facebook, Twitter, everyone has it. So, just to give you a visual example, we have a forum where I enter my email and password, then we have a phone, which is our MFA in this case, and then we get authorization. So the first case is a factor, right, so if we didn't have to use a phone or other device, I would be considered a factor.

And then multi-factor or two-factor authentication would be the addition of another device to confirm that it's you. And what is quite common is to use your phone and install an app on your phone. And then what that phone will do is it will give you a random number that expires, like every, I don't know, 10 seconds, you have to enter it with your username and password or as a second step, and then get access to the Azure Portal. Hi, I'm Andrew Brown from Exam Pro. And we're looking into Azure Security Center. So, Azure Security Center is a unified infrastructure security management system.

Strengthens the security posture of your data centers and provides advanced threat protection for your hybrid cloud workloads. That sounds very elegant. But let's take a look at what that is. So that's what's below. It's a lot of graphics. And it will tell you, if you comply with particular policies, they will tell you about your safety, hygiene and all kinds of security issues, so that you have a good view of your security within Azure. There you go. Hi, I'm Andrew Brown from exam Pro and we're looking into Key Vault. That's why Azure Key Vault helps you protect cryptographic keys and other secrets used by applications and cloud services.

And so within Key Vault, you have a ton of features. So one thing you can do is manage your secret store, strictly storing and controlling access to tokens, passwords, certificates, APIs, keys, and other secrets. It also has key management. Therefore, you can create and control encryption keys used to encrypt your data. Then we have certificate management, which allows you to easily provision, manage, and deploy public and private SSL certificates for use with Azure and connected internal resources. And it is also a hardware security module. So secrets and keys can be protected using software or FIPS, 142 or 140, script up to level two validated HSM.

I told them we'd be talking about hips again, and that's the way it is now. So to understand HSM, the last thing we're talking about, which stands for hardware security module, is a piece of hardware designed to store your encryption keys. And it literally looks like something like this. So Azure would have bought one of these, there are tons of these and that's what stores your cryptographic keys. And this piece of hardware is special because when you store keys on it, they are stored in memory, which means they are not written to disk. If that thing goes off, the keys will be gone and no one will be able to steal your data.

It's just a security measure. And that security measure has to do with FIPS. Okay, so FIPS 147. Two is a US and Canadian government standard that specifies security requirements forthat cryptographic modules protect confidential information. So for HSMs, which are multi-tenant, they will typically have a 140 dash, two compliant, multi-tenant, which means there is more than one client that is using that piece of hardware, but they are virtually isolated from each other. And then if you have a single tenant HSM, you're generally going to be FIPS 140 compliant, dash, three, so a single client on a dedicated HSM, you better be FIPS 140 compliant, dash, three.

But script two of FIPS 140 is pretty good for most people. There you go. Hi, I'm Andrew Brown from Exam Pro. And we were looking into Azure DDoS protection. So before talking about DDoS protection, let's talk about what DDoS is, which stands for distributed denial of service attack, this is a malicious attack, to disrupt normal traffic by flooding a website with large amounts of fake traffic. So to better visualize this, imagine there's someone who doesn't like you, and you have your servers, and they want to attack you and they want to stop your server from working. So what they can do is send remote commands to a group of computers that they control.

And these could also be at a cloud service provider or in your own data center, and from a foreign country. And what they will do is send thousands and thousands of fake requests to your server. So they will have packets that they will send to you with IP addresses, all those IP addresses are made up to be just fake traffic, and then they will flood you with so much traffic that your servers are going to crash, the network is going to crash, you are not going to be able to do anything. But the best thing is that most cloud service providers, including Azure, have built-in DDoS protection.

So, just by using a cloud service provider, you will have a certain level of protection against DDoS attacks. And talk about the different levels. Azure offers two levels of DDoS protection. So basic DDoS protection is free and already activated. It is what protects the entire global Azure network. So if you're using Azure you already get DDoS protection, if you need something more advanced, because the attacks are extremely more complex, you need more visibility and you need professional support. There is the standard DDoS protection plan. So that starts at $2,944. You could say it's high, but trust me, I've experienced the dosage.

And when you're a DDoS, you're willing to pay that amount and it works out of the box, you're going to get metrics alert reports, you're going to get a DDoS expert, so they can talk to you or a team that they can talk to. And they would have an application cost protection guarantee. So SLA, if they couldn't prevent the attack and if you lost the money cost, they will give you credits or help you. Well, that's DDoS protection for Azure. Hi, I'm Andrew Brown from Exam Pro. And we're looking at the Azure Firewall, which is a cloud-based managed network security service that protects your Azure virtual network resources.

So the way it works is you set up a V network, which is a virtual network, and you connect that firewall, you'll use it as the entry point for all your traffic. And then what you're going to do is speak v net. So when I say spoke, I'm just referring to other virtual networks that you've created, which are intermediate with your traffic, so the traffic will go through that V network to those others. And our V-net with the firewall will decide what traffic can flow and what can't, to other V-nets that have specific virtual machines so we can get protection.

But let's talk about some of the features of the Azure firewall. So the first thing you do is create, implement, deploy, and register application network connectivity policies between subscriptions and virtual networks. So subscriptions, i.e. multiple accounts, use a static public IP address for your virtual network resources, allowing external firewalls to identify traffic originating from your virtual network, which is very useful. High availability is built in at no additional cost. Therefore, there is no need to create load balancers and do all the work yourself. You can configure it, you can configure it during deployment to span multiple singles so that you have high availability.

There are no additional costs for a firewall deployed in an availability zone. There is an additional cost for incoming and outgoing data transfers associated with ACS, which is typical. There you have it. Hi, I'm Andrew Brown from Exam Pro. And we're looking at Azure Information Protection, also known as AIP. And what this does is protect sensitive information, like your emails or documents with encryption. And restrict access based on rights. And it's integrated directly into Office applications. So if you're using PowerPoint, Word, Exchange, or any of the Microsoft 360 suite, where you'll have this, this button called protect, you can pull it down and change the access controls and the privacy controls. of your data.

And this is really important if you're a larger corporation. And these kinds of things really matter to you. That's Azure Information Protection, just think about that button you click and then you have those security controls. Hi, I'm Andrew Brown from Exam Pro. And we're looking at Azure Application Gateway. So I think we talked earlier about the application gateway. And it is a load balancer. And specifically, it is an application load balancer. Then operate on layer seven. So these are HTTP requests. And because these are HTTP requests, you can actually understand the nature of a request. And you can create rules to direct traffic to other places.

Another really great feature of Azure Application Gateway is that you can connect a web application firewall. And it will protect at layer seven. So you can configure rules, just like you were configuring routing rules, you can configure security rules about what should be able to flow in and out of this load balancer to give you a picture next, you have internet, you have your application gateway and You can optionally attach it to your wife. And as traffic flows, you can create some rules. So let's say you have a server that serves all your JavaScript assets and a server that serves all your images, you could set a rule that says when the path matches this, just send it to this server and when the path matches that, just send it to that server.

Well, there you have it, that's the Azure Application Gateway. Hi, I'm Andrew Brown from Exam Pro. And we're looking at Azure Advanced Threat Protection, also known as ATP. And before we talk about the service, let's talk about what IDs and IPS are. I know they're throwing a lot of acronyms at you today. So, ID stands for intrusion detection system and IPS stands for intrusion protection system. And what that is, it's a piece of technology that monitors a network or systems for malicious activity, activity or policy violations. So the difference between an IDP IPS is or sorry, ID and an IPS is that an IDS detects an IPS protection, so it actually takes action on the ladder.

And I'm not sure if Advanced Threat Protection is just an IDS or an IPS, but it doesn't hurt to include it in the same category. It is not a big thing. Therefore, Azure Advanced Threat Protection, ATP is a cloud-based security solution that leverages on-premises Active Directory signals to identify, detect, and investigate advanced threats, compromised identities, and malicious information actions targeting your organization. There you have it, that's what it does. Hi, I'm Andrew Brown from Exam Pro. And we were discussing the Microsoft Security Development Lifecycle, also known as STL. Or some people might call it STL. Therefore, STL is an industry-leading security asset assurance process.

And it's a broad Microsoft initiative and a mandatory policy since 2004. That means Microsoft uses it because they created it. The STL has played a critical role in embedding security and privacy into Microsoft software, software, and culture. Therefore, building security into every STL phase of the development lifecycle helps you detect problems earlier. And it helps you reduce your development costs. So it's about these phases. These are the phases for it. Then you have training, design, implementation, verification, and release response requirements. If you want to implement this yourself, I bet they have a great white paper as a PDF that you can read, but it's just a business process.

And it just says that the sooner we implement things in our portfolio in terms of development, the sooner we can reduce security risks, and that's actually called pushing left because the further to the left you start implementing security, the sooner the better. Security will be throughout your pipeline. There you go. Hi, I'm Andrew Brown from Exam Pro. And we're discussing policies. So an Azure policy is a service that you can use to create, assign, and manage policies. A policy allows you to enforce or control the properties of a resource. An Azure policy evaluates resources in Azure by comparing the properties of those resources to business rules.

And these business rules described in JSON format are known as policy definitions. So if it's not clear yet, don't worry, we'll be looking at policy definitions very soon. But just understand what Azure policies do. They are used to create, assign, manage policies, and enforce and control the properties of your resources. Hi, I'm Andrew Brown from Exam Pro. And we're looking at Azure role-based access controls, so this is one particular service, but it's more of a concept of how all the components work to get access to resources. . So its role-based access control helps you manage who has access to resources, what they can do with those resources, and what areas they have access to.

Then you have role assignments. And this is how you control access to resources. So a role assignment consists of three elements: the security principle, the role definition, and the scope. Speaking of the security principle, first, this represents the identity requesting access to the Azure resource. So who wants to have access, they could have a user, which is an individual profile in their Azure Active Directory, they could have a group of users in their Azure Active Directory, they could have a service principal. This is a security identity used by applications or services. To access specific Azure resources.

This is what a service wants to access. And it would have managed the identity, this is the identity in Azure Active Directory that Azure automatically manages, and that's a little bit harder to describe. But that's not so important for the exam. So the last part of the component here is the scope. So this is the resource set that will be granted access to the resource set that will be granted access to the role assignment. So the scope is actually focused on the management subscription or resource group level. So to explain that, the idea I'm trying to convey here is that you have resources down there, right, and that's what you want to have access to.

But you can set the scope at the management group level, you can set the scope at the subscriptions level, you can set the scope at the resource group levels. So, just to talk about the three management groups, when you manage a group of accounts, the subscription is an individual account and the resource groups are a grouping of resources. So wherever you want to apply that scope, you can choose any of those three. Now you are looking at role definitions or the role definition is a collection of permissions. And remember that before we were talking about a policy, this is where that comes in.

Because policies are permissions. A role definition lists the operations that can be performed, such as read, write, and delete; Roles can be high-level, such as owner, or specific, such as a virtual machine reader. And just to give you an example, since you have built-in roles, you can define your own custom roles, but I think you have to pay more to be able to do custom roles, because that's through Azure Active Directory. But the built-in roles you need to know which are owner, contributing reader, and user access manager, these are the four core built-in roles. Now, look at the graph there, we have the green and the red.

So for an owner, you can read, you can grant, you can create, update and delete resources, you can do everything as a collaborator, all you can do is read, create, update and delete, you can't grant access, You can't, you can't Allow other users to access your resources. Then you have a reader. So a reader, as its name implies, can only read resources that it cannot create or delete, and cannot grant access to other users. And then a user acts as administrator only granted. So their job is to give access to other resources, but they can't do anything themselves.

There you have it, they are role-based access controls. Hello,I'm Andrew Brown from Exam Pro. And we're looking at Lock resources. So, as an image, you may need to lock a subscription resource group or resource to prevent other users from accidentally allowing other users to delete or modify critical resources. So in the Azure portal, you can set the following blocking levels that you can configure so that they cannot be removed. And then in the Azure portal, this will simply be called delete. And this authorized This will allow authorized users to still be able to read and modify the resource, but they cannot delete it.

Then it is read-only and in the Azure portal, it will be read-only with script. And this is so that authorized users can read a resource, but cannot delete or update it. Hi, I'm Andrew Brown from Exam Pro. And let's look at the Azure management group. Therefore, Azure management groups are a way to manage multiple subscriptions. And when you hear the word subscriptions in Azure, think of accounts, because it's an easier way to think of a hierarchical structure. Therefore, each directory is assigned a single top-level management group called the root management group. All subscriptions within a management group automatically inherit the conditions applied to the management group.

And this is a graphical representation. So at the top you have your root management group and then you create management groups below it. HR, IT marketing, production developers, you name it. And below you have those individual subscriptions. Again, just things like an account. Those are Azure management groups. Hi, I'm Andrew Brown from Exam Pro and we're looking at the Azure monitor. Therefore, Azure Monitor is a comprehensive solution to collect, analyze and act on elementary dental telemetry from your cloud and on-premises environment. So if you were to go into the Azure monitor on the left side, you would see all these options, activity log alerts, metrics, logs, service, status, etc.

And that's what the Azure monitor is, it's like an umbrella. for plenty of services below. Here's an example of a bunch of information in dashboard form about monitoring and analytics. So with Azure Monitor, you can create a visual dashboard, as we can see here, you can create smart alerts, you can create automated actions, and you can collect logs to have log monitoring. There you go. Hi, I'm Andrew Brown from Exam Pro. And we're looking at the health of the Azure service. Therefore, this is information about current and future problems, such as events that affect the service, planned maintenance and other changes that may affect its availability.

So, going down the list, we have Azure Status, which tells you about service outages in Azure as the status of your service, as well as a custom view of the Azure service status and the regions you are using. And then Azure resource health is information about the health of individual cloud resources, like your virtual machine. So if you're ever wondering what your health status is, you can use Azure Service Health and if you noticed, it was an option in the Azure monitor. So if you're looking for it, that's where you should go to find it. Hi, I'm Andrew Brown from exam Pro and we're looking into Azure Advisor.

Therefore, the average Azure advisor is a personalized cloud consultant who helps you follow best practices to optimize your Azure deployments. The bulletin board, the advisor, displays personalized recommendations for all your subscriptions for the following five categories: high availability, security, performance, cost, and operational excellence. And since we are in the security category, what matters most to us is security. But it would also be important for the pricing section. So the first thing we'll look at is the Azure Advisor cost recommendation. So here you can see that it tells you where the biggest impact may occur, and when you leave, it tells you how much money you can save by following the security recommendations of the new app.

And here are 21 recommendations, if we click on them, he will tell you what kinds of things you could improve on your system to improve its security. There you have it, that's Azure AD. Hi, I'm Andrew Brown from Exam Pro. And we're looking at SLAs for Azure. So SLA means service level agreement. And this describes Asher's commitment to uptime and connectivity. That means if you have a web server, Azure will say, yes, we guarantee that 99.9% of the time it will stay up all year round and it won't stop working. That's the idea behind an SLA for Azure.

SLAs are individualized per Azure service. So they don't have a broad SLA, you'll have to investigate each service to determine what Azure's commitment is for that service. And the way we describe these SLAs is in terms of uptime and connectivity through performance goals. Now, the performance target is just a representation in the form of a percentage. So if someone told you, you know, this service hat has a 99% chance of not failing, that's called two nines. And then you have the three nines, and then you have five nines, and then you have nine nines. And the higher this number, the more reliable and better coverage this SLA will give you, so you want something that has a higher number of nines, and it's not always just nines, it could be 99.9.

Nine 5%. But understand that when someone says nine nines, he is talking about the last value that is there. And it's like one of the tallest. One of the biggest guarantees that SLA can offer, I don't remember, there are like 11 nines, there may be 11 nines. But generally nine nines is the upper limit. And just to mention is that for Azure, if you're using the free tier of shared rips, you don't get SLAs because they just don't support them because you're consuming everything for free. So you have to pay to take advantage of that SLA guarantee. So I said that the SLA is our specific service.

So if you really want to dig in, all you have to do is type Azure SLA into Google. And you should be able to reach this page. And what we can do is click on any of these here. So if I go to the database and we choose Cosmos dB, and we just expand our information here, we get tons of information about their SLAs. And then our performance goals are down here. We have this for availability, this is for read availability. So they have a lot of information. And like I said, it's basically for any service, anything you want, just click on it.

And they have all that SLA information. There you go. Hi, I'm Andrew Brown from exam Pro and we're looking for service credits for Azure. Therefore, a service credit is when a custom customer would get a discount on their Azure bill as competent as compensation for a poorly performing Azure product or service based on the SLA. So those guarantees that Azure offers, if they don't honor them, then they owe you money. And the way they do it is through credits, right? So, credits are like virtual money; I actually don't know how much a service credit is worth.

But just know that if they don't meet those SLAs, they will stand behind you and give you your money back in some sense. Just an example here, if we have an Azure VM, remember, a VM is a server, if it had a monthly uptime percentage of 99.9. So if it was less than that, you'll get a 10% service credit. If it was less than 99, you will get a 25% service credit. And if you were under 95, you get 100% service credit. I guess that means maybe it's the cost of what you spent. But anyway, I'm not exactly sure. But I guess if we say the uptime was less than 95%.

And they will give you 100% service credit. Maybe 100% of your resources will be returned to you. So if you spend $100, you'll get that $100 back. There you go. Hi, I'm Andrew Brown from Exam Pro. And we're looking at a composite SLA. So we said earlier that different services have different SLAs. And the problem with this is that when you have different servers, different SLAs it's a little bit difficult to understand what the actual guarantee is when you use them in combination. Therefore, the composite SLA is just one way to understand what the actual underlying SLA guarantee is for the performance target.

So imagine you have a web application. And that web application uses a SQL database. So the web application has a 99.95% guarantee. Because maybe that's the performance goal for the virtual machine and then for the SQL databases, 99.99%. So what is it? Is 95 99.95%? Or is it four nines? We do not know. So if we were to calculate, calculate that for the SLA with the web application and the SQL database, the result would be 99.94%. Don't ask me about the math, that's the example they give us. But understand that that is what it would become: it would reach 99.94%. And then you would have an overall SLA reduction, while the SQL database would have a 99.9% reduction.

So how could we improve our SLA and consider it in our design, to get the SLA we want? And what you can do is add alternative systems that will improve the overall SLA. And if you think about it logically, it makes sense why that would work. So imagine you have that SQL database and it crashes. But if you had a queue and that queue saved all the transaction attempts that the web application was trying to write to the database and saved the queue, it wouldn't matter if the database crashed. Because once the database is backed up, all those transactions would be there.

And then those transactions would be completed. And then using the signal, which has an uptime of 99.9%, according to the math below, and don't ask me how the math works, but the result would be a 99.95% SLA. And that's an improvement over 99.94%, which is why it's called composite SLA, right? Hi, I'm Andrew Brown from Exam Pro and we're looking at the TCS calculator for Azure. If you remember, earlier in the course we talked about total cost of ownership. That's what TC O means. It's about showing an on-premise business how much money they would save by moving to the cloud and Azure.

That's what the TCL calculator does: it estimates the cost savings you can realize by migrating your workloads to Azure. So what you can do is generate, generate a detailed report and export it as a PDF to send to the decision makers. Now you have to enter all the information, but it will help you convince your boss and the executive level that it's time to move to the cloud, because they will save tons and tons of money. So if you want to use that calculator, you just go to

azure

.

microsoft

.com, slash pricing, Ford slash calculator, and it will give you an idea of ​​how much you'll save.

And now this is just a little bit of what it generates. Because it is a very detailed report. But in this example, the on-premises cost savings would be compared to Azure. And in this case, this person would be saving $130,000 in five years. And it will vary depending on the use case. But yes, that is the TCL calculator. So I just wanted to quickly show you the TCL calculator in action. If you want to find it yourself, just type TCL Azure Calculator into Google. And you should be able to find your way here. So what I did here was define my workload.

So in my workflow, I defined some servers. We have some Linux servers, we have 10 of them, four processes, four cores and eight gigabytes of RAM. And then here I added four servers that are databases running Postgres, then I added some hard drives. So I said three terabytes, two terabytes of backup, etc. And then I defined some network bandwidth. So moving on to the next step, we will adjust our assumptions. This helps us make an even more accurate estimate. So we can choose our currency, some other additional features, we might want to consider where we can save money, like using the Azure hybrid benefit.

And then next we can modify some of our costs that we know for our local environment. So there is a lot to modify here to make it more precise. And then if we move on to the next one, we'll get our savings. Wait a moment. And so, over a five-year period, we should save $666 and 158 cents. And you can roll it out, if you want to do a year, we'll go to a year. So here it says $381. And we have a lot of graphics here, as you can see, and then down below, you should be able to download them.

So you can go ahead and download the results there. And that is the TCL calculator. Hi, I'm Andrew Brown from Exam Pro. And we're looking at the Azure Marketplace. Therefore, Azure Marketplace is a place where there are applications and services made available to you by third-party publishers to quickly get started with Azure. So the available apps of the apps and services that may be available could be free, they could be free trials that could be paid as you go or they could come with their own license. So just an example of what it would look like if you logged into the Azure portal and searched for Marketplace, what you could do here is type in a variety of things.

Just like here, I'm writing in WordPress. ANDhere I have a bunch of WordPress provided by third party publishers that have been vetted by Azure. And again, they could cost money, they could have a free trial, it could be 100% free, but whatever you need, it's usually on the market, it's a great place to check it out. So keep that in mind. So I just wanted to quickly show you Azure Marketplace. So you would have to have an account to see it. But we show you in this course. But anyway, I'm going to go up here to the top and type market.

And this will boost the market. And here you can see that we have a lot of categories of things that we can launch. So whatever we need, and I think I showed it before WordPress, but we'll write it there. So you go into WordPress and there are all these servers. Then you can click there. You might have plans associated with it if there's a price, but just go ahead and hit Create. And then that would start the process of creating a virtual machine and you would go through that and subscribe to whatever the underlying costs were.

But you can see there are tons of things here. So you can sort by price, sort by operating system. There you go. Hi, I'm Andrew Brown from Exam Pro. And we're discussing Azure support plans. And then we have four support plans. We have a basic and direct professional developer standard. Technically, we have five companies, we count, I don't think they are in the exam. And there isn't much information about it because you have to call sales to find out the price and support from that company. So let's go over the difference between these things: It's definitely important for your exam.

We are looking at the basic support plan and everyone gets the basic support plan. When you register. You get email support for billing and accounts only. If you have any questions about your bills or your account, you can get answers from support. Now for standard developers and direct professionals, you get technical support and email support for all levels. And generally speaking just for developers, they will only respond during business hours. But if you had standard or professional direct, they have people answering emails, 24/7, 24 hours a day, I think the general response time for email support, no matter what level you That is, it is approximately 24 hours.

But you know, it's just going to vary. So I would say if you need something more urgent, then you'll want that phone support. So the phone support is standard direct and professional, and that's 24/7. So if it's Saturday, it's 9 p.m. and you need to call support, you can do that. And sometimes you just have to wait 10-15 minutes, I'm not sure if Azure has chat, but it's very common for cloud service providers to provide both chat and phone support, you wait 10-15 minutes and you get access. there. Now for third party support, if you are using technologies like Ruby on Rails, Spring Jango, those things are not really part of Azure, they are third party software that you are using to build your web application.

And Azure will try to do everything they can to support you, even if it's not what they created. And that's not what they have to do. But they will try their best to achieve the standard of developer and direct professional. So that's an advantage to paying for support. Now, in terms of response times, when you open a ticket, you can tell the severity of your ticket, and that will determine how quickly they will respond if you need the answer. So if there's a ticket and you say it has minimal business impact, then maybe they're general questions or something that will be considered severity C, and for developers in standard, they'll respond within eight hours or less. , a professional director can achieve this in four hours or less.

Again, just general questions. Now, if there is something that is going to have a moderate commercial impact, then the time will be much faster, they call that severity. So it will be less than four hours. And then, for the professional live show, it will be less than two hours. And this would be true if your production system was compromised, but it would not affect your business. Now if you have a critical business impact, that means your web application is 100% down and you are losing money, every minute you open a ticket called critical business impact, which is severity c, actually it should be severity a.

There's just a spelling mistake. But they would respond in an hour or less. So what I find is that even if they say an hour or less, that's not always the case. But generally, that's how quickly they will respond. Now for other services, you get like an advisor, health status, community support, Azure documentation, all these support plans. The only reason we're mentioning this here is because they mentioned it on their support page, but they're just trying to say, hey, just keep in mind that you have these additional support tools that you can use at any time and they're self-service, so community support and Azure docs.

Now, if you need general guidance on your architecture, you'll get it from the developer and standards. So you can definitely ask questions there. If you are using a professional direct service, you actually get access to the team, on that team there is a group of people that you can get when you talk to them, where they will give you guidance and call them. Operational support and proactive guidance from professional direct delivery managers. Professional directors are called pro direct. And they have delivery managers, I don't know if that means they are developers. But the point is that they will go the extra mile to help you there.

Plus, you can access webinars led by Azure engineers. So that's great too, if you pay the professional directly. So let's just review all the support plans here for pricing. So the basics are free. And when you sign up, if you don't use the plan, you're using the basic plan. And then for developers, $29 USD per month for standard, that's $100 USD per month. And for direct professional, it is 1000 US dollars per month. There you have it, those are the Azure support plans. So I just wanted to show you how to get to this support plan page in case you want to dig a little deeper, but my chart pretty much sums up everything that's included in the SERP support plans.

So if you want to find this, just go to Azure, just type Google as your support plans and you should be able to get here. You'll notice we have all four plans and then there's enterprise support. And if we go here, there's more information about this. But again, you will have to call technical support to find out the actual price and offers there. But yeah, just take a look here and see if there's anything I missed, but I'm pretty sure I've got everything you need in the main chart on the previous slide. Hi, I'm Andrew Brown from Exam Pro.

And we're looking at the Azure hybrid benefit. Many customers have already invested in Windows server licenses and want to refocus their investment on Azure. This happens because companies had been working with Microsoft servers even before Azure existed, or because they were originally on-premises. And that's why they wanted to use the software. So they bought the licenses, but now they are ready to move to Azure. And since they already have a special agreement with Microsoft, because they buy those licenses, they want to maintain those agreements and take them to the cloud. That's where Azure's hybrid benefit, also abbreviated as hub, comes into play.

It's sometimes called Azure hybrid usage benefit in Microsoft documentation, but for some reason Azure just removed the word usage, but the abbreviation is hub. This gives customers the right to use these licenses for virtual machines in Azure. And then those types of virtual machines would be Windows servers or SQL servers. And I imagine this would probably happen with an upheaval and change, which I think we described somewhere in this course. Therefore, the hub can be turned on and off at any time for existing virtual machines. And the hub can be applied at deployment time for new virtual machines.

And I just wrote, bring your own license here, just because we're talking about licenses, and I just want you to be more exposed to that term, bring your own license, by or L. And that just means that someone bought the license and they want to apply it , they want to incorporate it into Azure. There you have it, that's the hybrid benefit of Azure. So I just wanted to quickly show you this page, which is the Azure hybrid benefits page. If you were to type in Google as your hybrid benefit you would definitely get here, what I wanted to show you is that they actually have this nice little calculator below.

So if you have licenses, you're bringing them in, and you want to run workloads in Azure, you can fill out this material and it will give you an idea of ​​what you could save. So I just wanted you to be aware of that. There you go. Hi, I'm Andrew Brown from Exam Pro. And we're looking into Azure Subscription. So an Azure subscription I would describe as the equivalent of saying my Azure account. I don't know why they use the term subscription, because to me it's just confusing. But I always try to reinforce that it's just your account.

And there are four levels of Azure subscriptions. The first is the free subscription. So when you sign up for the first time, this is the account you will have in your subscription, you must provide a credit card to complete the process, you will get 200 USD of free credit for 30 days, and certain Azure products will be free for 12 months . Now, the goal of this free subscription is to help you avoid charges. And there are some limitations. I remember when I was trying to add another user. I couldn't grant them access. There were definitely some limitations here as well to avoid being charged, but it's not a complete sandbox.

So you may be charged and counted if you start using things outside of the free tier or if you use up your credit. So be careful there. And then once you're ready to switch or upgrade and unlock everything, you can switch to the pay-as-you-go subscription, also abbreviated as PAY g, some people might call it on-demand. And for this, you still need a credit card. But since you already entered the free subscription stage, there is no problem here, you will be charged at the end of the month based on the cloud resources consumed, then you will have an enterprise agreement.

So if you are a business, you can make a deal with Azure and agree to receive a discounted price for the licenses and cloud service. But I bet you are paying a lot of money, compared to a normal person, but the deal is worth it for you. So keep in mind that if you are a company, talk to Azure, they want to work out a deal. And the last one is the student subscription. So for student subscription, it doesn't require a credit card, you get $100 USD credits for 12 months, but it requires a valid student email. So there's a little bit of a vetting process there.

You definitely have to be in school to get it, but it's a very good option. There you have it, those are the Azure subscription models. Hi, I'm Andrew Brown from Exam Pro. And we're looking at the Azure pricing calculator. So set it up to estimate Azure product costs; No login required to use this tool. And what you can do is download an Excel spreadsheet and share those costs with your boss. So to get there, go to azure.

microsoft

.com Price Slash Calculator. And from there you can come in here and complete different things. So there are a bunch of different categories, one of which would probably be a virtual machine.

So you go in there and say what regions it's going to be released in, what operating system and all the configuration types it will give you an estimated cost. So the next one has an initial cost of $0 with a monthly cost of 100 52 point $62. So if you're not sure how to understand all the pricing, go here and give it a try and you'll get a clear idea of ​​what you're going to spend on Azure. I just wanted to show you the pricing calculator. So if you just went to Google and typed in Azure pricing calculator, you should be able to get to this page.

And then we have a lot of products. We also have example scenarios, which is very nice to see here. So let's say we wanted a CI CD pipeline here, and we said add to estimate, we can get that information for all of these components, I'm just going to go to individual products, because it's a little bit easier to see. So let's say we want to determine our storage costs. So let's go to storage here. And we will try with storage accounts. And then down below, we now add storage. And so we can enter some information to try to determine our costs.

So we could do blob file storage, table storage, I'm going to use file storage, I'm not actually going tousing blob, it's simply easier to calculate. And then we will have the performance level two premium redundancy LRS. And we will be east of us. So if we had 1000 gigabytes, I guess that's a terabyte, that's 150 dollars. If we had X number of write operations, X number of listings, container creation operations, read operations. And here we would have $150 as a monthly cost. So here, you just have to modify it according to your consumption. And then they will generally show you similar purchasing options.

But in reality, this just means signing up for an Azure account. But I just wanted to show you what that looks like so you know you can explore any cost and try to calculate something before you use it. Hi, I'm Andrew Brown from Exam Pro. And we're looking at Azure cost management. Therefore, this service allows you to perform cost analysis. So you can visualize the spending of your Azure cloud resources. But you can also create a budget for the service. So when you set a budget, you'll define a threshold and receive an alert when you approach or have passed that threshold.

And just to give you a visual representation that is for cost analysis. So you can see that you get beautiful graphs and you can drill down and filter those things to really understand how you're spending things in Azure. So definitely check it out. And there you have it. Hi, I'm Andrew Brown. From exam Pro, I'm going to show you how to book your exam for the az 900. So what I want you to do is type Pearson VUE Azure, or Pearson, Vue Microsoft into Google, and you'll be directed to this page. And then what you're going to want to do is on the right side, go ahead and click log in, then it's going to ask you what certification you want to write on the az 900.

And there's the certification, then we'll see that this page is going to show some intermediate information about the certification, what we're going to do is go ahead and schedule a Pearson VUE. Now there is a kind of certificate. But if you are a student or an instructor, we are neither. So we're going to choose Pearson VUE mode, there's this dropdown here that literally does nothing. I don't know why they have it here. I thought maybe the price would change. Maybe the availability would change depending on where you are. But we'll go ahead and stick to the schedule with Pearson VUE, what it will do is ask us to sign in to our Microsoft account.

Mine is called Azure exam pro cow, it's the same account I created when I created my Azure account. And then I'll just put my password in there. We will press log in. And then the next step is to ask me to complete my certification profile. So this is all the personal information related to me. And note that you must log in exactly as your government-issued ID, in order to book the exam. So I'm going to complete this and proceed to the next step. And I'll see you there. Alright, now let's move on to the next step.

And so we finish my profile, discount for separate exams, I'm not a Microsoft employee, I didn't attend the event, so I won't get any interesting discounts here. So we'll go ahead and proceed to Pearson VUE to schedule our exam. So wait here a moment. And now that we get here, I'll ask you how you want to take the exam at a local testing center in my home office or in a privately accessible cloud. I'll show you how to do it in a local test. center, we may not have any options here, but we will try. And we will choose our language, English is the case here.

And it will say the price and etc., we will move on to the next thing. So what it will do is show me locations near me. Next, you have a graph and some things there. So we'll just take a look here. So what I can do is click on a location, so I'll choose downtown Mississauga. That's pretty good. So I'm going to go ahead and check the apply box. And we're going to have to select at least three testing centers here. So I'll choose this one and move on to the next one. And now we have some options here for programming.

I want you to stop. You'll have to come back to this one here. And then we will choose our time. And from there, all we have to do is add to the order, pay and that's it. That's all you need to book your exam. So, good luck on your exam.