8 hours 21 minutes 48 seconds
🇬🇧 English
Speaker 1
00:00
Hey, it's Andrew Brown, your favorite cloud instructor over here on free code can't bring you another free cloud certification study course. And this time, it's the Azure fundamentals, also known as the AZ 900. And the way we're going to achieve Microsoft certification is by watching those lecture videos, doing those hands on labs. And as always, I'm going to provide you a free practice exam.
Speaker 1
00:23
So you can go get that certification, putting a resume, put it on your LinkedIn and go get that cloud role you've been looking to get, if you love these kinds of cloud certification study courses, the best way to support more free courses just like this 1 is to purchase the paid optional materials, it's going to help you increase your odds of passing the exam. And it just helps the production of these courses. And if you don't know me, I'm Andrew Brown. And I've taught a lot of different cloud certification study courses here.
Speaker 1
00:54
We've done AWS, Azure GCP, Kubernetes, Terraform, you name it, I've taught it. But that's about it. Let's go ahead and learn some Azure and I'll see you soon. Ciao.
Speaker 1
01:09
Hey, this is Andrew Brown, and welcome to the Microsoft Azure fundamentals. And we're asking the most important question first, which is what is the certification? Well, the Azure fundamentals is the entry level cloud certification for Microsoft, Azure or Azure. And you'll see me alternate between those pronunciations.
Speaker 1
01:28
They're both accepted. So whichever you prefer, There is no prerequisite for this certification. But you should probably have a little bit of it experience. But if you don't, it's totally fine.
Speaker 1
01:40
If you're totally new to cloud, you're still be okay here. The key topics that we are covering is understanding the basics of cloud computing, exploring the benefits of using cloud services, and looking at those core services, those being computing, networking, storage, and databases, understanding identity security governance. So, you know, 1 example for identity would be Entra ID, previously known as Azure AD, something you'll hear again and again, through all the Microsoft certification courses, understanding how pricing works, things like subscriptions, and cost management tools, and learning about the tools available for managing Azure resources, such as Azure portal, or the SDK or the CLI, things like that. Microsoft Azure is the second leading cloud service provider in the world, the first being AWS.
Speaker 1
02:27
But let that not discourage you because Azure is still an extremely great cloud service to use. And it's used quite a lot. So Azure fundamentals is a very common starting point for people breaking the cloud, similar to the AWS cloud practitioner. So both are really great entries into cloud, who's a certification for will consider this fundamental certification.
Speaker 1
02:52
If you're new to cloud, and you want to learn the fundamentals and benefits adopting cloud services in general, you are from a non technical background, such as an executive management or sales level, and you need to acquire strategic information about cloud for adoption or migration, you'll want to understand the capabilities of Azure and how to build basic solutions and deploy cloud services in your organization. Very, very basic, but I mean, the objective of these fundamental certifications is not to really teach you how to build cloud workloads. That is more at the associate level. But we'll talk about that later on.
Speaker 1
03:26
Or you're a senior cloud engineer or solution architect or, or cloud architect who needs a reset or refresh their knowledge after working with Azure for multiple years, but maybe you didn't notice some things change. So it's a great revisit to get an idea of what is going on here. So what is the value of the certification? Well, the fundamentals is provides the most expensive view possible for cloud architecture and Azure.
Speaker 1
03:52
I like to say this is going to provide you a bird's eye view or the 50,000 foot view. So we're going to cover a lot of stuff. But it's not going to be as detailed as you imagine. But the idea here is to promote big picture thinking, zooming out and assessing the cloud and Azure landscape for changes, trends, opportunities, and being strategic about the approach and process for our cloud journey.
Speaker 1
04:17
Okay, The Azure fundamentals is not a difficult exam, it will not validate that you can build cloud workloads. For technical roles, such as developer engineer DevOps, it's not going to be enough to obtain those roles. But it's possible that it could shortlist your resume for interview. The exam covers content not found in other certifications.
Speaker 1
04:37
So strongly recommend that you take this as your foundational certification. A lot of people like to skip fundamentals because they say they think that they're easy. Yes, the certification is easy. But the exam content has a lot of stuff in it, especially mine, because I pack in a ton of stuff that I just I'm not going to put at the next level, because I'm going to assume that you're taking this course and getting all that knowledge there.
Speaker 1
04:58
The AZ 900 lays a good foundation for specialized or specialization for Azure certifications, and is a stepping stone for professional development in cloud services. So definitely there is value in the AZ 900. Let's go take a look at the Azure roadmap. And this is not all of the Azure certifications and Microsoft certifications, they just have too many, I cannot fit them all on screen here.
Speaker 1
05:22
And I think all the course codes are up to date, but they're changing them all the time. So it's possible that they might be incremented by some versions. But the entry we have the Azure fundamentals, there are other fundamental certifications. We have the AI 900, which is for AI, we have the DP 900, which is for data, we have the SC 900, which is for security.
Speaker 1
05:44
But again, I don't have room for all that. So I'm not showing them on here. So I'm showing you the path that is commonly completed after taking the AZ 900. So you have some associate certifications, you have a couple expert certifications, you have specialty certifications, there's definitely more associates, there's definitely more specialties, But there's always the 2 pros or experts, I should say.
Speaker 1
06:04
So getting my handy pen out here, very often, what people go for after the fundamentals is the administrator, the AZ 104. This is the most common path for those that are going to their next step in their Azure journey. And a lot of times people are going for that solutions architect expert, which is over here. But before you do that, you really want to go and grab that developer, the AZ 204.
Speaker 1
06:30
These are the this is the the most common strategy right here is these. But of course, it really depends on what you're doing. If you're doing security, you have the SC 900. And then there's 3 different associate level security certifications.
Speaker 1
06:45
If you are going after data, that's a whole different track. So it's going to really vary based on that. But again, you know, this is the most common track. And even if you go do all of this, and you want to do something else, that's totally fine, because this is going to lay a very, very strong foundation and give you really good skills in Azure.
Speaker 1
07:03
So how long does it take to study for this certification? Well, if you're a beginner, we're looking at about 30 hours. And this is someone that's never written, or used Azure or any cloud provider have never written any code, or held a tech role. Technically, the certification doesn't require you to code.
Speaker 1
07:20
But I really want to make sure that I set you up really well. Because in Azure, coding and scripting, and that kind of stuff is way more important than any other cloud provider, because you come across it a lot more. And so I've stuck in a bunch of coding stuff. And it is very challenging for beginners, but I want to try to get you best prepared as possible.
Speaker 1
07:42
Because when you go to the associate level with like the AZ 104, it is so much more difficult. So I made this much harder than it had to be to prepare you for the next level, despite the exam. Okay. So again, 30 hours on that side of your experience, then you're already working with Azure, or you maybe are you've worked in AWS and GCP, and you are trying to pick up Azure, the it could be as little as 6 hours.
Speaker 1
08:07
So you know, generally, the study time is 24 hours. And I would say it's split between lectures and labs, and then you have your practice exams. So just make sure that you put your time in with the practice exams. Practice exams are very, very, very, very, very important for Azure because Azure has all these different question types.
Speaker 1
08:27
And we'll talk about that in a moment. But yeah, the recommend studies 1 to 2 hours a day for 14 days, take your time, let it absorb, you could finish it in a couple days, but don't do that. You know, make sure that you are acquiring the knowledge for long term. And the best way to do that is to take your time and and not try to pass it in a weekend.
Speaker 1
08:48
What does it take to pass the exam? Well, you got to watch those lecture videos, you got to do those hands on labs and follow along within your own account. Strongly recommend that you do some paid online practice exams, we give you a full free practice exam, like a full set, which is on our platform there, we have a lot of practice exams, you get that at exam pro.co forward slash AZ 900. And really help support the course here.
Speaker 1
09:13
Where do you take the exam? Well, you're going to either take it in person at a test center or the convenience of your home. And so I would just say just a second here. Sorry about that.
Speaker 1
09:25
Bako is knocking on my door. Baker's the other Andrew, who you'll hear me talk about Bako a bit throughout the course, But he's the other person that works with me that's never on camera, you never see him. But he helps do a lot of the work over here with the platform and creating the content. But anyway, so Azure delivers exams via, I got to reclick here.
Speaker 1
09:51
And the clicks not working. There we go. Pearson view is the proctoring system that Microsoft uses. In the past, there used to be a bunch of ones, there's criterion, which Google used to use Google Cloud, there's PSI online, which AWS like to use.
Speaker 1
10:07
But for whatever reason, both AWS and Microsoft exclusively only use Pearson view now. And I think GCP is now using PSI online, and everyone else uses PSI, for whatever reason. But yeah, you have to use Pearson view. And you can do it online or Pearson view has a network of test centers that you can go to in person.
Speaker 1
10:32
Personally, I recommend that you go in person if you can, because if there is a test center near you, the whole environment is controlled, it's going to be a lot less stressful. Whereas if you do it from home, you know, if you have family, or you have the least ideal place to set up, because you have to have a non cluttered room, and they have to inspect your room and things can go wrong. So I'm just saying if you have that opportunity to go to an in person in person test center, leverage that if you can't, that's okay. Do what works for you.
Speaker 1
11:03
But understand that these certifications are proctored. So when you go sit that exam, there's someone who is monitoring you to make sure that you are not cheating. In terms of the content outline, there is 3 domains, I think there used to be more, but they grouped up into 3, I'm not sure why. Each domain has its own weighting.
Speaker 1
11:21
And that determines how many questions in a domain will show up. So we'll take a look there. Something that's really interesting about Azure exams is that they, they don't give you the same amount of questions per person. So they'll give you like you like you might sit the exam and get 35 and your friend might get 40.
Speaker 1
11:41
So I had to give ranges here in terms of the percentage that will appear on your exam. So we have describing cloud concepts, which is 25 to 30%. So you're going to get about 13 to 15 questions, describe Azure architecture and services, that's 35 to 40%. That is the majority of the certification, most fundamentals is about learning all the services that the cloud service provider is providing, then we have described Azure Management and Governance.
Speaker 1
12:09
So that's 30 to 35%. With 14 to 1616 questions, there is a sub domains under each of these. So of course, securities in there and all those other things are in there, but we'll have to open up the exam guide to see that. Okay.
Speaker 1
12:23
So again, you know, just pointing out that that domain 2 is the largest 1 there. So make sure that we we're going to make sure that we know a wide range of Azure services. But we're also going to make sure we know in depth a bit more about those core services. Let's talk about grading, you got to get a 700 points out of 1000.
Speaker 1
12:44
So that's about 70%. We say around because Azure uses skilled scoring, meaning that it doesn't necessarily mean you get 70%. And you pass, you could technically pass with 71%. Or sorry, fail with 71%.
Speaker 1
12:58
But you could also technically pass with 69%. So just understand, it's not based on percentage, it's based on a point system, in terms of what kind of questions you'll be getting. Well, first, let's talk about the range of questions, but you can get between 35 to 50, I usually say 37 to 37 to 50. It's confusing, because I don't know how they determine how many you get.
Speaker 1
13:22
When I sat my exam, I got about 35 questions, some people get more, it's really, really tricky to to nail that down there. So you know, we say about 10 to 14 questions, you have, you can afford to get wrong, there are no penalty for wrong questions. So absolutely, always fill in the answers. In terms of formatting questions, we have multiple choice, multiple answer, drag and drop, yes, And no, I do need to point out that when you go and take associate level and expert level certifications with Microsoft, they have way more question types.
Speaker 1
13:58
And just to help prepare you for that level of difficulty. And it doesn't appear in these exams. But in our practice exams, we try to put in case studies. So case studies is a much more advanced exam type question.
Speaker 1
14:14
And, you know, I really feel that we need to do that. Because if we don't, you're going to feel like you're ready for the AZ 104. And you're going to get totally blindsided because again, the difficulty ramp is super hard. So again, we're increasing the difficulty for your benefit.
Speaker 1
14:29
So if you feel like this course is hard, that's good, because it's going to make the next 1 really, really easy for you. In terms of duration, apparently, it's 45 minutes, I cannot remember how long it was when I sat it. And when you search the internet, it's very difficult to determine that number. Microsoft does not make it easy to find out that number, you think that they would other cloud service providers, their certification exams, they tell you right on the same page, good luck finding it on Azure, but 45 minutes would still leave us with about 1 minute per time.
Speaker 1
15:02
Again, it depends if you get the 35 questions, or 45 questions. So we're gonna have to say about a minute. So we'll say the exam time is 45 minutes. Some people say the seat time is 60 to 65 minutes.
Speaker 1
15:15
When we say see time, we're talking about the time you should allocate for the exam that includes things like time to review instructions, read and accept the NDA, complete the exam, provide the feedback at the end. Now, personally, I think that the seat time should always be 30 minutes on top of whatever that is. So if it's 45 minutes, it really would be 75 minutes, or 70 minutes or something like that. So you know, anyway, if you got a 45 minute exam, show up 30 minutes or 35 minutes earlier, because if you're checking in, especially online, you got to pull out your government ID, you got to make sure the lighting is right, and then it scans it in if things go wrong, you know, it's going to cut in your time.
Speaker 1
15:58
So give yourself ample time and don't get stressed out for that. Okay. So these certifications are for Microsoft are valid forever, this is specific for fundamental certification. So if you take the any 1 that has 900 in the name, so AZ 900, DP 900, AI 900, sc 900, pl 900, ms 900, you get in the pattern here, if it says 900 in the name, it's a fundamentals, those certifications do not expire.
Speaker 1
16:29
And so I just want to make that very, very, very clear. For the other levels like associate expert, I think it's 2 years, it's either 2 or 3 years. But the interesting thing is that if you want to get recertified, you don't have to pay to take the exam. Again, you can take a simpler test to make sure that your knowledge is up to date.
Speaker 1
16:52
And I think it's free. So that's a great advantage that Microsoft has at the associate and expert level specialty level. But yeah, there we go. And I'll see you in the next 1.
Speaker 1
17:08
Alright, so I went on to the internet and I searched for AZ 900. And we've ended up on the learn.microsoft.com. The reason I want to show you this page is to get more familiar with where we actually get the information so that you can read up about about it if we didn't answer everything or if anything has changed. But it's good, good, good to be familiar with these pages.
Speaker 1
17:27
So once you're here on the AZ 900, What they'll have down below here is the study guide. Now the study guide used to be in a PDF format. And for whatever reason, Azure has just made it a website with all the other study guides here, I really don't like this format, I find that it's very hard to find information And to read it, I really prefer the old PDF, but that's never coming back. Or if it is, it's somewhere else.
Speaker 1
17:51
And I don't know where it is. But what we can see over here is the actual breakdown. So we have cloud concepts. And so we think see things like defining cloud computing, share responsibility model, the different deployments of cloud, and a bunch of other stuff here.
Speaker 1
18:11
You can see describing the cloud service types. Now, at 1 point, they actually removed this. And now it's back. So that's really interesting.
Speaker 1
18:17
I don't know why they ever removed it to begin with. But it's good to see that that is returning, we have, I call this global infrastructure or and cloud networking. So they call this core architectural components, which I suppose some of these things are, but this is more like a billing thing. And this is more global infrastructure.
Speaker 1
18:37
Then we have Azure Compute and networking services and recovering virtual machines, functions, skill sets, availability sets, Azure Virtual Desktop. Now, we don't have to do all these things. And we aren't going to do all these things, because some of these things are really hard, like Azure Virtual Desktop is not an easy task. But we need to know what they are, we are going to launch a virtual machine.
Speaker 1
18:57
And play around with that a little bit, we are going to launch an Azure function. Then we have storage services. So we do a lot with Azure storage, because it is cheap and easy to use. Then we need to know how to perform different operations with Azure.
Speaker 1
19:15
As your storage there that we have Azure identity access and security. So again, this is a sub category under here for sub domain. So we need to know a bunch of things about security. I'm just going to tell you that some of the content is going to say Azure ID, some of it's going to say Microsoft Entre ID, Microsoft, for some crazy reason, decided to change the name of Azure AD, even though everybody was fine with it, it confuses myself and Beko and everyone else to this day.
Speaker 1
19:43
So just understand that some of its Azure AD, some of its Microsoft Entry ID, but this is this is really what's going to be going forward. Okay. We have described cost management in Azure. So that's TCO, some more pricing stuff here.
Speaker 1
19:58
Azure purview, Azure policy, we have the Azure portal, which is just the platform which we use everything Azure Arc, which I guess it's okay to know, we actually do a lot of interesting coding here. So I show you how to do ISE with arm templates and Azure bicep and terraform. So that stuff's fun there, we look at monitoring tools. So we look at Azure Service Health, Azure Advisor, all sorts of fun stuff.
Speaker 1
20:28
Now, there could be other stuff that appears exam that's not on here. And so we just do a very thorough job to show you basically everything. And just to kind of round out your knowledge. But again, it's very difficult to to find all the details like the time of the exam and the amount of questions, they really just do not make this easily available here.
Speaker 1
20:52
If anyone finds it, please tell me because I sure can't find it. And the only way I know is by sitting an exam and I have to remember those details afterwards, they do show what kind of changes that they make. So they're always making teeny tiny changes. But try not to worry about that too much, because we do ensure to include a lot of stuff here.
Speaker 1
21:10
And this exam is up to date and and the fresh and as fresh as it can be as of this recording. But you know, I find that even 2 years out, people are passing, like people are passing the current exam with the old the old 1, which is which is really interesting. So it just shows you that not much changes on those exams. Okay.
Speaker 1
21:33
But anyway, that's that. Another thing I want to show you is the exam Sam sandbox. So this emulates the Pearson view kind of experience. And it'll just show you some of the question formats.
Speaker 1
21:43
Now, we are under here for the AZ 900. And it might show us more exam types and what we'll actually see on the exam. So go here, this just has 10 questions, it's going to just show us all the types. So here we have multiple choice, then we have multiple select, I'm not looking at what the correct answers are, or read any of it, I'm just showing you here, I believe that we drag these into these areas here.
Speaker 1
22:06
So that's this 1, then this 1 is your answer area, and you're bringing them over, and then you're trying to determine the order. So you're changing the order here, then this one's an answer area. So we go here, and it's just an image. And this is draggable.
Speaker 1
22:23
We have this 1 here. So we look at this graphic, and we try to match it based on this information. And we read it very clearly. This 1 here.
Speaker 1
22:35
What is this for a hot area. So hot area is you have a graphic very similar to that other 1, but you click it, it's almost like you're kind of interacting with it, but you're not, it's just an image, then we have a case study. So this is something that we absolutely, absolutely give you in our platform. And you will not see this on your exam.
Speaker 1
22:51
But we give you this exam question type anyway, because it's super important to get that kind of experience. And those this one's a little bit more robust in terms of the information. And so there are other things. Yeah, another thing with case studies is when you do a case study, you basically get a series of questions around this case study.
Speaker 1
23:13
Right. And it went to the next part. And it's kind of like a mini exam inside the mini exam. I'll show you case studies in another video.
Speaker 1
23:20
So I know I'm going really quick there. But we'll come back to that. Then sometimes you have these additional tabs. So this is kind of like a mini case study for just a particular question.
Speaker 1
23:30
But they might say, Hey, check out the exhibit. And you have to look at the exhibit, come back and then answer the question. So there's that. And then sometimes there's multiple exhibits.
Speaker 1
23:43
So yeah, but yeah, there you go. So that is the, the sandbox there. So hopefully that gives you a good idea, the price might vary based on where you live. So if we go to Canada, I'm not sure what the prices in Canada.
Speaker 1
23:58
So we go here, and it still shows $199 USD, we go somewhere else, does it ever show a different price? Sometimes it does. Okay, for some reason, Canada gets a bad price, but some other places do a little bit better. So understand that that price is going to fluctuate based on where you live.
Speaker 1
24:16
Yeah, hopefully that gives you an idea of the exam. And we'll see the next 1. Okay, ciao. Hey, this is Andrew Brown from exam pro.
Speaker 1
24:30
And we are at the start of our journey asking the most important question first, which is what is cloud computing. So cloud computing is the practice of using a network of remote servers hosted on the internet to store, manage and process data rather than a local server or personal computer. And so when we're talking about on premise, you own the servers, you hire the IT people, you pay or rent the real estate, you take all the risks. But with a cloud provider, someone else owns the servers, someone else hires the IT people, someone else pays or rents the real estate.
Speaker 1
25:01
And you are responsible for configuring cloud services and code. And someone takes care of the rest of it for you. Okay. So to understand cloud computing, we need to look at the evolution of cloud hosting going all the way back to 1995.
Speaker 1
25:14
Where if you wanted to host your website or web app, you'd have to get a dedicated server. So that would be 1 physical machine dedicated to a single business running a single project, a site or an app. And as you can imagine, these are expensive, because you have to buy out right the hardware, have a place to store it, the network connection, having a person to maintain it. But it did give you a guarantee of high security.
Speaker 1
25:38
And they still do as of today. So this model hasn't gone away. But it's been specialized for a particular use case, then came along the virtual private server. So the idea is we still had 1 physical machine.
Speaker 1
25:49
But now we were able to subdivide our machine into sub machines via virtualization. And so essentially, you're running a machine within a machine. And so you had better utilization of that machine, running multiple web apps, as opposed to having a physical machine per project. So you got better utilization and isolation of resources.
Speaker 1
26:11
And so these 2 options still required you to purchase a machine, a dedicated machine. And so that was still kind of expensive, but then came along shared hosting. And so if you remember, the mid 2000s, like with GoDaddy, or HostGator, or any of those sites, where you had really cheap hosting, the idea is that you had this 1 physical machine shared by hundreds of businesses. And the way this worked, it relied on tenants under utilizing their resources.
Speaker 1
26:37
So you know, you wouldn't have a sub machine in there, but you'd have a folder with permissions that you could use. And so you would really share the cost. And this was very, very cheap. But you were limited to whatever that machine could do.
Speaker 1
26:51
And you're very restricted in terms of the functionality you had. And there was just poor isolation, meaning that, you know, if 1 person decided to utilize the server more, they could hang up all the all the websites on that single server, then came along cloud hosting. And the idea is that you have multiple physical machines that act as 1 system. So this is distributed computing.
Speaker 1
27:11
And so the system is abstracted into multiple cloud services. And The idea is that you basically get the advantages of a lot of the things above. It's flexible, you can just add more servers, it's scalable, it's very secure because you get that virtualized isolation. You get it extremely at a low cost because you're sharing that cost with the users, where in the shared hosting, it might be hundreds of businesses, we're looking at 1000s of businesses.
Speaker 1
27:37
And it was also highly configurable, because it was a full virtual machine. Now, cloud actually still includes all of these types of hosting, they haven't gone away. But it's just the idea that you now have more of a selection for your use case. But hopefully that gives you an idea what cloud hosting looks like.
Speaker 1
27:53
And it really has to come down to distributed computing. Okay. Hey, this is Andrew Brown from exam Pro. And we are looking at common cloud services.
Speaker 1
28:06
So a cloud provider can have hundreds of cloud services are grouped into various types of services. And the 4 most common types of cloud services for infrastructure as a service. And we'll talk about what that is later on would be compute. So this is where you have a virtual computer that can run applications, programs and cold code, then you have storage.
Speaker 1
28:28
So this is where you would have virtual hard drives that you could store files, then you'd have virtual networking because you have these computers and storage, you need to put them in some kind of virtual network. And then you have databases. So just imagine a database that is running in the cloud. Or if you're not familiar databases, just imagine that it's Excel in the cloud, but it powers your web apps.
Speaker 1
28:53
And 1 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 just use it as a catch all term. So it could refer to all of these categories. So when I say cloud computing, I could be referring to compute network storage and databases. But you can also say cloud storage, cloud compute, cloud databases, cloud networking, and people will know what you mean.
Speaker 1
29:20
Hey, this is Andrew Brown from exam Pro. And we are looking at what is Microsoft. So you've probably seen this logo before. And Microsoft is an American multinational computer technology corporation headquartered in Redmond, Washington.
Speaker 1
29:33
And Microsoft makes software phones, tablets, game consoles, cloud services, which is what we care about here today. And they even have a search engine. And we're not just limited to that list. They have tons of stuff.
Speaker 1
29:46
But Microsoft is best known for their operating operating system called Windows. And they've been around since the 1970s. So they've been around for quite a while in the tech sphere. So now that leads us to the question is what is Azure.
Speaker 1
30:00
So Azure is what Microsoft calls their cloud provider service. And so it's called Microsoft Azure, or we commonly refer to it as just Azure. And so here is the logo for it. If you're wondering what is the name behind the service, it means bright blue color of the cloudless sky.
Speaker 1
30:19
So sure, that's great. And so you'll hear me say cloud service provider frequently it was throughout this course, and it is abbreviated to CSP. But that's what Azure is, it is a cloud service provider. So there you go.
Speaker 1
30:38
Hey, this is Andrew Brown from exam Pro. And we are looking at the benefits of cloud computing. So what are the benefits? Well, we have a big list here for you starting with cost effectiveness.
Speaker 1
30:47
So you pay for what you consume, there is no upfront cost, you pay as you go, also abbreviated as PAYG. And you're sharing the cost with 1000s of customers. So that's how you're getting that, that low low cost. Another benefit is that you can go global.
Speaker 1
31:02
So launch workloads anywhere in the world, just choose your region. And you are now in the global market. Another benefit is the cloud is secure as a cloud providers take care of the physical security and cloud services can be secure by default, or you have the ability to configure access down to the granular level. So you have a lot of security controls that you would have that you you would normally not have, or you'd have to build out on prem.
Speaker 1
31:28
Now, the cloud is also known for being reliable. So you can have data backups, disaster recovery and data replication and fault tolerance. The cloud is also scalable, you can increase or decrease your resources and services based on the demand. The cloud is also elastic.
Speaker 1
31:44
So you can automate scaling during spikes and and drop the demand when there is no longer the demand for that stuff. And it's also current. So the underlying hardware and managed software is patch upgraded and replaced by the cloud provider without interruption to you. And I mean, the last 1, there is cases of interruption, but generally fewer interruptions than you would have on prem.
Speaker 1
32:06
So there you go. Hey, this is Andrew Brown from exam Pro. And we are looking at the different types of cloud computing. And we have this nice pyramid on left hand side to help us understand how each type builds off the other starting at the top of our pyramid, we have software as a service, also known as SAS.
Speaker 1
32:27
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 remains available. So you might not be aware of this, but you probably already are using a SaaS product. So examples of that could be Salesforce, or Gmail, or Office 365. So those are the those are things that would be considered SAS.
Speaker 1
32:49
And these are really for customers. So it's just you wanting 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 pass. And so here we focus on development and management of your applications.
Speaker 1
33:07
And so you don't worry about provisioning, configuring or understanding the hardware or OS. And this is really for people that are building apps, but they don't but they don't think about any of the infrastructure underneath services like this would be elastic beanstalk on AWS or Roku, which is very popular amongst junior developers, which is a third party service for launching web apps. And then you have the Google App Engine. So those are 3 examples there.
Speaker 1
33:31
And these are really for developers. So platform of service makes it easy for developers to build apps on the cloud without worrying about all the stuff underneath. At the bottom, we have infrastructure as a service, IAS. And this is the basic building blocks of cloud IT.
Speaker 1
33:48
So provide access to networking features, computers, and data storage space, don't worry about the about it, staff, data centers and hardware. And this is the true focus of our course here is focusing on this layer. But the thing is, again, on this pyramid is that I, the infrastructure service can have platform as a service and software service on top of it. And so examples of infrastructure service would be Microsoft Azure, AWS, or even Oracle Cloud.
Speaker 1
34:15
And so this is really intended for administrators. So that is the 3 types of cloud computing. And there you go. Hey, this is Andrew Brown from exam Pro.
Speaker 1
34:28
And we were looking at the types of cloud computing responsibility. So we saw the 3 categories there. But we don't really understand what it is that we're responsible for. And what is the cloud service provider responsible for?
Speaker 1
34:39
So let's lay out our categories. And we're going to include on premise into this, because technically, on premise could be a private cloud and should be in the category here. So we have on premise infrastructure as a service platform as a service and software as a service. So when we're looking at applications, it's going to be the customer's responsibility for on prem infrastructure pass.
Speaker 1
35:02
But when we have software as a service, the cloud service provider is responsible for that. When looking at the data level, it's going to be the same for software as a service, the cloud service provider is going to be responsible, but for the rest, it's going to be the customer. And then on the next level for the runtime, it's going to be responsible on the cloud service provider for the platform as a service and software as a service. For middleware, it's going to be the same for the OS, like the operating system that is running on the service, it's going to be the same.
Speaker 1
35:32
Then we get to virtualization. Now it's the virtualization is responsible with the cloud service provider and above. And then for storage, it's or sorry, servers, it's the same for storage, it's the same and for networking, it's the same. So you can see that on premise, you're responsible for everything.
Speaker 1
35:53
And the the farther we move up the types of cloud computing, the less responsibility you have. Hey, this is Andrew Brown from exam Pro. And we were looking at Azure's deployment models. And the first model we're going to talk about is public cloud.
Speaker 1
36:09
And that's where everything is built on the cloud service provider, you're not using anything on prem, or in your own data centers, everything is running within Azure. And generally, this is known as cloud native. But for some reason, Azure calls the public cloud. So that's what we're going to use in the terminology here.
Speaker 1
36:26
And so here I have an architectural diagram where we have a network on 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 clouds, this is where everything is built on the company's data centers, also known as on premise, because it's within the premises of the organization, like their physical location. And it could an organization organization could technically be operating their own cloud, but it'd be private cloud.
Speaker 1
36:58
And they could be running some open source cloud software that mimics what Azure would do, such as OpenStack. So it looks very similar. But you just put an OpenStack in there. And it's running a virtual machine or a server, and it's also running a database.
Speaker 1
37:13
And the last on our list here is hybrid. So with hybrid, you're using both on premise and the cloud service provider, and they're connected together. And so there's a lot of different networking services that you can use that will facilitate the connection between the 2. In this case, we're using Express Route Express routes is a dedicated connection.
Speaker 1
37:35
It's like having a fiber optic line running from your on premise data center to the Azure network. So just 1 of the ways you can connect. And if we wanted to understand like the pros and cons, I have this nice little table here, we'll just quickly go through it. So if you're using public cloud, it's more cost effective security, it's, it's screen controls are stronger by default.
Speaker 1
37:56
But some people might not find the cloud will meet all their security requirements because of government and regulatory, regulatory reasons, not because the cloud is not secure, but it's just those, those policies. For level of configuration, it's going to be limited based on what the cloud service provider exposes to you. So there's a lot of configuration there. It's just that if you're if you have your own servers, you obviously can do anything and everything with them.
Speaker 1
38:21
For technical knowledge, you don't need to have as much in depth knowledge of the underlying infrastructure because you're not physically setting up servers, or that networking and everything else. Now coming down to private cloud, private cloud is the most expensive option on our list. So you're going to be paying a lot of money there. For security, there is no guarantee that is 100% secure, because you just don't have the same kind of visibility that you would have with a cloud service provider with all those dashboards, it's just so hard to build out all that software.
Speaker 1
38:48
But you could meet your security compliance requirements, depending on your situation. But this is becoming less and less as more governments and larger organizations move over to the cloud, you can configure infrastructure exactly how you like, because you literally have bought the hardware and do anything you want with it. And the technical knowledge, you'll have to have a serious amount of technical knowledge, you might even have a really hard time finding the resources to, to maintain all that stuff. Then, down below, we have the hybrid model.
Speaker 1
39:19
So this could be more cost effective based on what you offload to the cloud, and also the cost of actually moving data back and forth. For security, you know, you have more to secure, But technically, some things are easier to secure on the cloud than it is in private. So maybe you have a boost in security, you're going to get the best of both worlds in terms of configuration. And for technical knowledge, you're going to need to know both the cloud and and like how to set things up on premise.
Speaker 1
39:47
So that's the most work there. And just 1 more deployment model here, I just want to talk about cross cloud, this isn't something that is listed on the actual exam. But it's something that you should understand and know. And so cross cloud is when you're using multiple cloud providers.
Speaker 1
40:01
Sometimes people refer this as multi cloud or hybrid cloud. And so I just have an example here. So there's a service called Azure arc. And what Azure arc does that extends your control plane, so you can run containers, Kubernetes containers on different platforms.
Speaker 1
40:16
And so you could have AWS on the left hand side with EKS and GCP Kubernetes engine. And so you can be running virtual machines. And they're all treated like they're on the same network. So cross cloud is becoming very popular with extremely large organizations, where they they have very unique requirements.
Speaker 1
40:32
But I definitely want you to know what that is, because it just gets left out. And it's definitely something that is part of the industry. So there you go. Hey, this is Andrew Brown from exam pro.
Speaker 1
40:45
And we're looking at the concept of total cost of ownership TCO. So what is the difference between on premise, so having your own data centers, and then using Azure, you'll notice above it, it says kpex and OPEX, we're going to talk about that in the next slide. But for the time, for the time being, we're going to focus on the total cost of ownership. So to really make sense of this, I always use this graphic here.
Speaker 1
41:07
And if you're wondering what that is, those are icebergs, people sometimes think they look like teeth. And so just to make this drawing a little bit more clear, I've added some penguins and a whale, So there's no mistaking it. And the reason we're using this as a representation is because we have the top of the iceberg, which are the costs that we're generally concerned about. But then we have those hidden costs, those costs that we're not really thinking about that is underneath the water.
Speaker 1
41:27
And if you know icebergs, they can be really big underneath, you don't know. So on the left hand side, the cost that we generally think of is the software license fees. And then for the cloud service provider, we look at the subscription fees. And so when you're comparing these 2, sometimes the subscription fees can cost more than the software license fee.
Speaker 1
41:47
So you'd think, well, we should really just use on prem because it's more cost effective. But when we take in the total cost of ownership, all the costs involved, we're going to see a very different picture. So on the left hand side, if you are on premise, you have to deal with the implementation, the configuration, and the 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 for the IT personnel, you have to deal with maintenance. Now on the right hand side on the cloud, you still have to do implementation and configuration and training.
Speaker 1
42:20
But that's about it. So there's a big difference in terms of what you have to do. And you might ask, Okay, well, what is the amount of savings? Well, generally, people find that when they move from on prem to the cloud, they save 75%.
Speaker 1
42:35
That's a lot of money, okay, 75% of what you generally would spend. And so now all this stuff on the left hand side is now Azure's responsibility, you don't take care of those anymore, Azure is going to take care of it for you. So that's total cost of ownership. Hey, this is Andrew Brown from exam Pro.
Speaker 1
42:54
And we're looking at capital versus operational expenditure. So on the left hand side, we have capex. So capital expenditures on the right hand side, we have operational expenditures, OPEX. And so looking on the left hand side, capital expenditure is spending money up front on physical infrastructure.
Speaker 1
43:10
So deducting the expenses from your tax bill over time, a lot of companies, larger companies are used to dealing with capital expenses, and they know how to work their tax bill. And so that's why a lot of people are afraid to move over to the cloud because they're used to this, this this way of operating. But let's talk about some of the things that would be considered a capital expense. So again, it's anything that's physical, and then you're buying it with money up front.
Speaker 1
43:34
So computers, so that would be your server costs. If you were to buy hard drives, that be your storage costs. If you bought routers, cables and switches for your network, if you're purchasing things for backup and archive costs, if you had disaster recovery, so like an uninterruptible power supply would be an example that you have your data center costs. So that's your rent, cooling, physical security, your technical personnel, so you're hiring people to do things for you.
Speaker 1
43:59
And so with capital expenses, you have to guess upfront what you plan to spend. Now let's look at operational expenditure. So operational expenditure is the cost associated when an on premise data center has put as shifted that cost to the service provider. So here, in this case, it's the cloud service provider, And the customer only has to be concerned with non physical costs.
Speaker 1
44:19
So what's examples of OPEX costs while leasing software and customizing features, training employees in cloud services, paying for cloud support, billing based on the cloud metrics, So compute usage and storage usage. And the advantage here is that with operational expenses, you can try a product or service without investing equipment. So we have flexibility of investment. And we also from the previous slide, we saw that we have a huge reduction cost.
Speaker 1
44:47
So there's 2 reasons, really good reasons to use the cloud. Let's take a look at cloud architecture terminologies. Before we do, let's talk about some of the roles that are around doing cloud architecture. So the first is solutions architect.
Speaker 1
45:04
This is a role in a technical organization that architects a technical solution using multiple systems via researching documentation, and experimentation. And then you have the cloud architect, this is a solutions architect that is focused solely on architecting technical solutions, using cloud services, understand that in the actual marketplace, a lot of times solutions architect is used to describe both a cloud architect and a solutions architect. And you know, these are going to highly vary based on your locality and how companies want to use these terms. But this is just me broadly defining them here.
Speaker 1
45:37
So just don't take them as a perfect word in terms of what they're representing. So a cloud architect needs to understand the following terms and factors and factor them into their designed architecture based on the business requirements. So we have the idea of availability, your ability to ensure a service remains available, scalability, your ability to grow rapidly or unimpeded elasticity, your ability to shrink and grow to meet the demand fault tolerance, your ability to prevent a failure, disaster recovery, your ability to recover from a failure. And there are a couple other things that you that should be considered.
Speaker 1
46:08
They're not terminologies, but they're definitely important to a solutions architect or cloud architect. And these are things you always need to consider as well. And this is just me talking to my solutions architect friends, where they'll always ask me these 2 questions after presentation, they'll say, how secure is the solution? And how much is this going to cost?
Speaker 1
46:27
All right. And so for the terminologies up here, we're going to define these right away. And we're going to figure these out throughout the course, we have 2 giant sections just on cost and security alone. So there we go.
Speaker 1
46:44
Hey, this is Andrew Brown from exam Pro. And we are looking at the concept of high availability. So this is your ability for your service to remain available by ensuring there is no single point of failure, or ensure a certain level of performance. So here I have a technical architectural diagram that is describing high availability.
Speaker 1
47:01
So the idea behind this is that if you have a server, which runs your web application, if you were to run redundant versions of your server, if anything happened 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's better is having multiple servers and multiple data centers, because something could happen to a data center, it could become unavailable because of a networking issue.
Speaker 1
47:27
So by being able to route traffic, or that way, you're going to remain highly available. And and running a workload across multiple availability zones and availability zones is what Azure calls their data centers ensures that if 1 or 2 data center becomes unavailable, your service will remain available, Very, very common to run at least 3 servers across 3 data centers. Now, how would you distribute the traffic or manage the traffic to all 3? And that's where an Azure load bouncer comes into play that green triangle with the arrows that is the representation of a load balancer.
Speaker 1
48:04
So load balancer allows you to evenly distribute traffic to multiple servers in 1 or more data center. And if a data center or server becomes unavailable, so unhealthy, the load balancer will route the traffic to only available data centers with servers. So there you go, that is high availability. Hey, this is Andrew Brown from exam Pro.
Speaker 1
48:27
And we're looking at the concept of high scalability. And this is your ability to increase your capacity based on the increasing demand of traffic, memory and computing power. If you are a growing company, you're gonna have to scale up, you're gonna have to get bigger and better servers. But the there are different types of scaling.
Speaker 1
48:42
And the first type is vertical scaling. This is the most obvious 1 people are going to think of. And it's called scaling up. And what we do is we just upgrade to bigger servers, we need bigger hard drives, faster computers, that's vertical scaling.
Speaker 1
48:54
But there's another kind of scaling called horizontal scaling. And horizontal scaling is is described as scaling out. And what you're doing is you're just adding additional servers, because we saw with the high availability, we have a load balancer, we can distribute traffic to multiple servers, and 3 servers can equal the same thing as 1 big server. So horizontal scaling is when we add more servers of the same size.
Speaker 1
49:22
Hey, this is Andrew Brown from exam Pro. And we're looking at the concept of high elasticity. And this is your ability to automatically increase or decrease your capacity based on this, the current demand of traffic, memory and computing power. So this sounds a lot like high scalability.
Speaker 1
49:39
But the key difference is that it's automatic. And you can decrease the demand, not just increase it. And so the way we would do that is that we would have a virtual virtual machine or server. And if we needed more servers, we would add more servers.
Speaker 1
49:55
And if we need less servers, we would remove less servers. And so this is going to be accomplished using horizontal scaling. So when we say we're scaling out, this means we're adding more servers of the same size. When we're scaling in, this means we're removing more servers of the same size.
Speaker 1
50:10
And generally, you're not going to use vertical scaling for high elasticity, it's just extremely difficult to to vertically scale. Because if you if you have to increase, let's say your storage drive, and then you decrease it, you could lose data. So it's not a good idea or even feasible to do vertical scaling with high elasticity. Now, how would you accomplish being elastic on Azure?
Speaker 1
50:36
While you use Azure VM scale set, so scale sets automatically increase or decrease in the response to demand or based on a defined schedule. And we'll talk about those in greater detail later in this course. And then we have SQL server, or server stretch database, these dynamically stretch warming cold transactional data from Microsoft SQL Server 2016 to Microsoft Azure, not something we're going to cover, but it's generally the same concept that skill sets do. So there you go, that's high elasticity.
Speaker 1
51:10
Hey, this is Andrew Brown from exam Pro. And we're looking at the concept of being highly fault tolerant. And this is your ability for your service to ensure there is no single point of failure, preventing the chance of failure. So when we looked at high availability, we had also said that was no point of failure.
Speaker 1
51:25
But when we really talk about that, we're really talking about being highly fault tolerant, because there is the word failure in the word, and that is what being fault tolerant is. And so how do we prevent failure? Well, we use the concept of fail overs. So fail overs is when you have a plan to shift traffic to redundant system in the case a primary system fails.
Speaker 1
51:47
And so I have a graphic here that represents a primary database failing over to a secondary database. And I have a bit of a description here. So the idea is that we have a copy of our production database, and we're gonna call that a secondary system. And the idea here is that every time something is written to our primary database, it's going to be synced.
Speaker 1
52:09
So it's going to be sent over to our secondary database. So it's up to date, the latest database. And then if the primary database happens to fail for whatever reason, whether it's hardware or otherwise, something's going to detect that there's something wrong with the primary, and it's going to fail over to the secondary and the secondary is going to be promoted to being the primary instance. And the key thing to understand is that that's that secondary is standby, it's not in actual use, it's only in use when the failover occurs.
Speaker 1
52:44
So what would you use an Azure to build out a highly fault tolerant system. That's where Azure Traffic Manager comes into play. So with this, and this works with a DNS level. And so the idea here is that you can fail over from a primary system at the DNS level to a standby.
Speaker 1
53:02
This is really great. If you have regional failures, you could probably also use a load balancer. But this is the case that I'm showing here. But there you go.
Speaker 1
53:15
Hey, this is Andrew Brown from exam Pro. And we're looking at the concept of high durability. So this is your ability to recover from a disaster and to prevent the loss of data. So this could be solutions that recover from a disaster is known as disaster recovery, d, r.
Speaker 1
53:30
And so I'm just going to ask you a bunch of questions to help you think about how to be highly durable. So 1 question would be like, do you have a backup? So do you have a backup in place? How fast can you restore your backup?
Speaker 1
53:41
Does your backup still work? How do you ensure current live data is not corrupt. So that is the concept of high durability. There's a variety of services to implement it.
Speaker 1
53:52
This is not just a single service. But there you go, that is the full list of cloud architecture terminologies. So to understand disaster recovery, we need to know more about things around it like business continuity plans, BCPS, and RTOs and RPOs. So a BCP is a document that outlines how a business will continue operating during unplanned disruption in services.
Speaker 1
54:20
So it's basically the plan that you're going to execute, if that happens. And so here we have a disaster. And you can see that there's a chance of data loss and downtime. And these 2 factors as RPO and RT are going to define the length of these durations.
Speaker 1
54:35
So recovery point objective is the maximum acceptable amount of data loss after unplanned data loss incident expresses amount of time. So how much data are you willing to lose? And then recovery time objective. So the maximum amount of downtime your business can tolerate without incurring a significant financial loss.
Speaker 1
54:52
So how much time you're willing to go down, okay, so those are the 2 there. And now let's go take a look at the disaster recovery options that we can use to define in our our BCP. So let's take a look at our disaster recovery options. And based on what you choose, they're going to be a trade of costs versus time to recover based on the RPOs or RTOs, of course.
Speaker 1
55:18
And so sometimes this is represented vertically, like a thermostat, or you can do it horizontally here. Both are valid ways of displaying this information, but I just have it horizontally here today. And so we have low or high or you could say, even though I don't have it written here, this could be cold, or this could be hot. Okay.
Speaker 1
55:38
So on the left hand side, we got backup and restore pilot light, warm standby, multi active site notice we're using the like the words like pilot light warm things that are relating to temperature. So again, cold and hot. All right. So let's just walk through what each of these things conceptually do in terms of architecture.
Speaker 1
55:58
So when you're doing a backup and restore your back, you basically back up your data. And at the time of disaster recovery, you're just going to restore it to new infrastructure. For a pilot light, the data is replicated to another region with the minimal services running to keep on replicating that data. And so you might have some core services running a warm standby is a scaled down copy of your infrastructure.
Speaker 1
56:18
So you basically have everything that you would absolutely need to run an application. But the idea is it's not at scale. And so at any time when there's an incident, you're going to scale up to the capacity that you need. And then you have multi site active active, where you have a scaled up copy of your infrastructure in other regions.
Speaker 1
56:35
So basically everything you have identically in another region. And so in terms of the RPOs and the RTOs, for backup restore, you're looking at hours, with the pilot light, you're looking at 10 minutes with a warm standby, you're looking at minutes and multi site active active, you're looking at real time. So you know, hopefully that gives you an idea of you know, the difference in terms of scale. But let's just look at more detail.
Speaker 1
56:57
So for a backup and restore, this is for low priority use cases, restore data after event, deploy resources after an event, and it's very cost effective. For pilot light, this is where you have less stringent RTOs and RPOs. So you're going to be just running your core services, you're going to start and scale resources after the event. And this is a little bit more expensive.
Speaker 1
57:18
This is very good for warm standby is good for business critical services. So you scale resources after the event. And it's almost very, it's very, it's costly, but it's not as expensive as a multi site active active. So you get 0 downtime, near 0 loss, you have it's great for mission critical services, and it's just as expensive as your original infrastructure.
Speaker 1
57:41
So you're basically doubling the cost there. Okay. Hey, this is Andrew Brown from exam Pro. And we are looking at the evolution of computing.
Speaker 1
57:51
And this is going to really help you to understand the different layers of compute. And so we're going to start from on the left hand side to dedicated and work our way all the way to functions. So what I want you to know is that when we're talking about dedicated, this is a physical server, wholly utilized by a single customer. And so the idea is that this customer has purchased this dedicated piece of hardware.
Speaker 1
58:15
But the thing with this is that you have to guess your capacity. So when you buy it, it's like a capital cost or you're purchasing for for like the whole, like you have to plan how you're going to fully utilize it. So you're going to overpay, and you're going to have underutilized servers. And the reason why is that when you first launch your app, it might 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.
Speaker 1
58:40
So it's considered wasted. If you want to upgrade beyond your capacity, this is going to be slow and expensive, you literally would have to buy a new server that's larger and then move everything over, you're going to be limited by your operating system. So whatever operating system is installed, that's what you're going to have, you're going to have multiple apps. If you do install multiple apps onto a dedicated server, you might have conflicts in resource sharing.
Speaker 1
59:03
But generally, it's recommended to only have a single primary application on a dedicated server, you are going to have a guarantee of security, privacy and full utility of the underlying resources. Because that is what that's the whole purpose of having a dedicated server is sometimes dedicated servers where you have full control of everything is called bare metal. And that's basically mimics what it was like to have a server on premise or back in the day, and they still exist. So that is dedicated, and we'll move on to VM.
Speaker 1
59:34
So now we're moving on to virtual machines, also known as VMs. And so the idea here is that if you had a physical server, and you had the capability of running virtual machines, that's like running a machine within a machine. And So now you're able to run multiple applications on a single machine. The technology that's used to actually run VMs is known as hypervisor.
Speaker 1
59:52
There are there are some other kinds, but the ones we need to know is hypervisor. So just know that that's the software that makes virtual machines work.
Omnivision Solutions Ltd