Gain in-depth knowledge for passing your exam with Exam-Labs Professional Cloud Developer certification video training course. The most trusted and reliable name for studying and passing with VCE files which include Google Professional Cloud Developer practice test questions and answers, study guide and exam practice test questions. Unlike any other Professional Cloud Developer video training course for your certification exam.

Course Readiness

7. Read the GCP Cloud Developer Deep Dive Notes.

Well, welcome aboard, everyone. Again, one thing I'd highly recommend you take a look at is going over to one of my many blog posts on the Cloud Developer exam. The one with the most detail that will really get you started is called the GCP Professional Cloud Developer Deep Dive Notes. Preparing for the exam now, you'llwant to go through this. I've got lots of pictures, commands, and examples we're going to look at throughout the course. I would recommend you take probably 30 minutes to go through the content here and just try to get yourself, I guess, familiar with what we're going to be talking about. This is an exam worthy of a lot of effort, but you'll be very happy once you're done passing the exam. So with that said, there's a lot of great, detailed content that you'll find pretty useful as well. So with that said, take a quick look, 2030minutes maybe, see how you do as far asyour understanding of what you'll be tested on, thisis, again, the Deep Dive Notes. The link is in the description. Let's go ahead and move on. And for those without the links in your course format that you may be using, it is on my blockchain, experperts.org. Again, myblockchainxperts.org is right there. Go in it and type in "Cloud Developer." I've got more than a couple of posts on the Developer Exam. Let's go ahead and move on. We have much to cover in the next two days of training.

Introduction to Google Cloud Platform

1. Google Cloud Intro (Condensed Version)

Let's go ahead and talk about Google Cloud. This specific module has now been added to this Cert prep course as a refresher. If you've been using Google Cloud data today and you'revery familiar with it, then you might as well justskip over this section and go straight over to theobjectives and just get prepared on taking the exam. Now, this is more like a Google 101, and again, it's a refresher for folks that may not have recent Google Cloud experience. So let's go ahead and get started. Again, I really wanted this part to be focused mainly on folks that may have worked with GCP or may not have and just need a quick refresher. But again, if you're familiar withGCP, go to the objectives. I still recommend that you review the test tips, though. Review the demos, review practise questions, code labs, and of course, use quick labs if you can as well. This specific Google Cloud 101 is really going to talk about the overview of Google Cloud, the hierarchy, networking, and the cost calculator that's available. Now, generally, companies want to use Google Cloud for many solid reasons. First of all, Google does have the most powerful infrastructure, and this is a clearly documented course. They do own most of it. Google has been in the data centre business for just about 20 years. It's quite a long time compared to some other cloud providers. They own their own data centers. They have a wide geography when it comes to their fibre backbones. They have submarine lines aswell, these submarine lines. They, of course, traverse the ocean and go from continent to continent, and they have well-established points of presence. Now, Google Cloud enables developers to build, test, and deploy applications on Google's highly scalable, secure, and reliable infrastructure. Notice that Google Cloud is focused on developers. Now, as far as Google's interoperability, this is really provided at multiple layers of the stack. Now, a lot of this is due to the fact that Google is running on software-defined networking. They fully support Kubernetes because they were the ones who really developed it. And then on top of that, they use open APIs as well. And this, of course, provides many benefits and allows you to essentially use multiple providers as well, especially if you're going to use containers. It just makes it so much easier for interoperability purposes. Another feature of Google Cloud that you should be aware of is that it supports sub-minute billing and full sustained use discounts. Also, they do provide what is essentially a heavy discounting programme as well, which is actually quite nice, especially if you're using a significant number of virtual machines. When it comes to Google Cloud, it'sreally important as well to realise thatnetworking Google is really global. When we deploy a virtual machine, that virtual machine is not limited to that region or that zone. And when we get to the networking part, we'll really find out why and how that works. But, in general, when we think of Google Cloud VMs deployed in Compute Engine, for example, they're global, global resources. Now, as far as some other reasons to use GoogleCloud, again, they have a private global fibre network, and it does support live migration of virtual machines as well. They also have industry-leading security, state-of-the-art security, continued expansion, and redundant backups Network tiering is available as well, and they have competitive pricing. Now, network tiering, for those not familiar with that term, basically means you have the choice to traverse Google's network or not when you're exiting Google Cloud. In other words, if you want to save funds and you want to go outside of Google Cloud, you can go ahead and basically exit Google Cloud and go to point A or point B. Or you could use the network tier, the premium tier, and this will allow you to diversify Google's provisioned, highly available network to that point of presence nearest your location that you're trying to reach outside of Google Cloud. So this is a really big benefit. You also have the choice of unmanaged or managed services. In other words, if you want to usea service like App Engine that will helpmanage your containers, you can do that. Or if you just want to use Kubeengine as well, that's up to you. Also, Google does have some really amazing advantages when it comes to their infrastructure. They support top-tier data analytics. In other words, their services in GoogleCloud are clearly ahead of the game when we're talking about big data with BigQuery. Also, other services that are available as well, such as big data services like Dataproc, for example, can definitely provide value. Their pricing is innovative, they have leadership and services areas, scaled security, and superior machine learning and automated intelligence services. Here's an example of their zones and regions, and when we compare GCP to AWS, especially when I'm talking about zones and regions, it's literally a one for one. There's no differentiator here between the number of zones and regions. It's typically right around one or two zones. It's essentially a race, and it's almost broken even now when we go through, say, the GCP for AWS course, where I go through the number of zones and regions when I write or update the course. But again, currently at the time of writingagain there is well over 20 regions essentiallyand number of zones was well above 60. With that said, a lot of greatopportunities there to learn with Google Cloud. Now the submarine lines or networking, as you can see, are significant. huge investment that they've made as well. Now what is the zone and what is the region? Basically, zones have high-bandwidth, low-latency network connections to other zones in the same region. Now, one thing to highlight here is that Google does recommend deploying applications across multiple zones and multiple regions. I would recommend, you know, that for the exam. Now, here's an example of their different regions and zones. And of course, you go to their website to find out the latest number of regions and zones. Again, at the time of writing, By the time you view it, the number will be very different. For that matter, let's go ahead and proceed onto the next module.

2. GCP Hierarchy

Let's go ahead and talk about the hierarchy in the Google Cloud Platform. And this is going to contain organizations, projects, resources, and folders when it comes to the main facet that is going to really facilitate the organisation of your services that you're using, which will be called a project. A project is really meant to not only segment your resources, but also for billing and accounting purposes. It really gives you a great way to essentially provide for what is called chargeback or showback, for example, in your organisation as well. But it also enables you to also consider having all your projects be part of what's called an organization. I'll talk about how this will play out shortly, but basically, each GCP project is going to have a name, a project ID, and a project number. And when we go through the demo on projects, we'll talk more about that, and you'll see exactly how this all comes together. Now, a project is really meant to facilitate the organisation of your services and objects and also for billing and accounting purposes. Now you can see over here we have a project name, a project ID, and a project number. Now, basically, the project name is really meant for you to identify what this project is for. Is it for production? Is it for a money-making application for your company? Is it a SQL database? Is it going to be for resources only in India or resources that are only in Boston? Whatever that scenario is, it's just a really easy way for you to organise things in a logical manner that makes sense to you. Project ID is actually very important because we're going to be using the project ID for a lot of our G Club commands. Also identify what the project is as well, and especially when we want to tie in, for example, a service account or anything of that nature. So we'll find out how the project plays into our resources with Google Cloud. Now, the project number is really a number that we can't change, and it's just a sign at the time of creation. It's really meant for Google to essentially reference your resources in the back end of Google Cloud. Now, projects are again going to be used for these purposes. We could track resources and quote usage, enable billing, manage permissions and credentials, and enable APIs as well as services. For example, when we deploy Cloud SQL ComputeEngine in a new project, the API for that service has to be enabled. When it comes to the hierarchy of Google Cloud, we have, of course, our projects, which are located here, but then we have the opportunity to tie in what's called an organisational node. Now, when we go to the demo, you'll see this coming to play, of course, but just realise that this is the way we could structure our G Suite resources or cloud identity resources, and it allows us to have basically what's called an ".org node" that is going to do what. It will group all of our enterprise resources under G Suite or cloud identities. This gives you an organization—that is, the ability to maintain centralised control of all your Google Cloud projects. If we just had projects and we were a large organization, then it would be very hard to keep track of all the different resource spending that's going on or what services are being used. But also, how do we manage permissions? And then we have the ability to add what's called a folder. A folder basically creates more granularity for our resources. Here's an example of a project and how we would tie in services as part of that project. Now when we talk about basically an organization, we want to ensure that we understand what a resource in Google Cloud is, and that is what that could be: any of the Google Cloud services that we're reusing, anything under a project, any APIs, et cetera. But basically, if we already are using G Suite, let's say, and we have a top-level domain with Google Cloud, we could simply tie in those resources to our cloud environment as well. It's part of the hierarchy. But the main thing that we want to use an organisation for is that it enables the organization—or the company, I should say—to basically be able to follow a corporate lifecycle. Now if this employee leaves, what do we do with their email account? What do we do now that resources are using Google Cloud? Do we save them? Do we delete them? Do we assign them to a new user? This is very important when it comes to the life cycle of the exam. A couple of things I just want to point out are that a network can only belong to one project. There's a limit of five networks and 100 subnets per project. And then there are some other notes that you'll want to review as well. for the exam. We want to realise that a Google Cloud Platform API is going to interact with project-based resources. Now one thing to point out is that resources are going to be global, regional, and horizontal base.That's really important to realize, to understand the types of resources that are being used. For example, if we have a virtual machine image and that image is not attached to a local SSD, then we could move that image somewhere else. But if it's attached to a local resource, then that's really a local resource. So we can't just move it around. Quotas are part of Google Cloud Platform projects. It allows us to basically set limits on our resources. For example, we may not want to have more than, let's say, 20 projects spun up at any given time. Well, we can set that limit. If we don't want certain APIs to be spun up, we could set limits again. The quota is basically focused on two areas. There are basically two types of services: those that are free and those that are not free.And Google also imposes quotas to protect against runaway usage, for example, in your organization, but also protects them from many different aspects that we could just imagine, right? Performance issues, having too many resources spun up, and not getting compensated for whatever. That situation is also too GCP When it comes to accounts, we're going to assign them or associate them with a G Suite domain or Gmail user account. This allows us to again provide granularity and also be part of the organisational structure. Now with GCP, we want to, for example, allow an outside user. We could simply add their Gmail or G Suite account to a project. Therefore, when we add a user to a project, they're only authorised to use that project. But we could also get even more granular to only allow that user to use certain services or to access certain object shares, whatever that reality is. on the exam. The first tip is to understand what a hierarchy is. In the Google Cloud, that is what the organisation is. At the top, the folders would be part of ClubIAM, and then we have projects and then resources. We really want to understand how we could pursue a project together. We're going to be talking about peering more in the networking part. Let's go ahead and move on to the demo.

3. Whiteboard GCP Hierarchy

Well, let's talk about the structure of Google Cloud.Now, with GCP, there is a different approach thanperhaps you get an AWS or Azure for example.So it's really important to understand some ofthe terms around how things really fit in.Now, one of the things I want to talk about just tomake sure that we can grasp is the power of a project.Now a project is actually part of the structure.Now we can have a GCP environment withone project or ten projects or even more.And if we're using G Suite, for example, wecan tie in what's called an organisation as partof our corporate hierarchy in our basically G Suiteor Cloud identity hierarchy that we deploy.Now basically we want to think ofthe organisation as the top level.So it's generally if you're using G Suite as anenterprise, you're likely going to have a domain and thatdomain is going to be tied to your organization.That organisation we could choose to pull intoGoogle Cloud or actually I should say, pullthe organisation as part of our GCP structureand have it be part of a lifecycle.So what I mean is this if I wantedto have a centralised policy where my company A.commanages the three projects that it has, then itcould manage everything as part of an organisational administratoror Admin as it would be known.And so we would tie our Cloud Identity orG Suite capabilities into an organisational admin role.Now we could also be using G Suite aswell and not actually be managing our projects centrally.If we want, we can have differentproject owners manage these individually, and underthe projects would be different resources.Now, on the exam, when we take the exam,it's really important to distinguish why we may wantto have one project, two project or three projects.Now generally we want to think a bitabout this from a couple of perspectives.But for the purposes of the intro part ofthe course, I just want to cover the basics.And as we proceed through the course, we'llcome back to the hierarchy, especially through thepractice questions, et cetera, that we'll run into.Because one of the areas that you may needto think about when structuring your application is dowe deploy one project, two projects, or three, orwhatever the number is, and do we need tointegrate it with G Suite or do we not? G Suite provides some great value toyour organisation if we do integrate withG Suite, for example, or Cloud Identity.Well, let's say one more thing before wego to the next part of the course.The next module is let's say, for example, we haveour on prem services and our on Prem services.Let's say we're using basicallyLDAP or Ad Active directory.What makes us really nice is if we wantedto, we could have our directory services tied intoG suite, which in turn would help us synchronizeour services as well in GCP.And we would want to use basically what's calledGCDS, which is basically Google Cloud directory services.And we'll have more on that coming out.But I just wanted to point outhow the life cycle could be created.So for example, if let me do a different carl here.If let's say, for example, HR notifies, if HRnotifies your, let's say email administrator, that email administratormight delete your G suite services, but will theyactually delete your account on Google Cloud or migrateyour services to another account owner, for example? And if we do this appropriately,we could create a lifecycle.And that's something we'll talk more aboutin the more advanced part of thecourse when we get into the objectives.So think about a project as part of a hierarchy.The organisation is a top level hierarchy.And now one last thing before we go is around folders.Now folders here, if we wanted to, wecould create basically a much more granular approachto our resource structure if we want.And we'll talk more about folders in the item sectionbecause because to use folders we need to use, ofcourse I am as part of the structure.It's a way to get really granularin our resource distribution, essentially in control.So let's go ahead and move on to the next module.

4. Demo – Projects

In this demo, let's go ahead and create a project. But before we do, let's recap what a project is. Essentially, a project on Google Cloud is where you're going to be able to organise your resources. And resources could be your storage buckets, your cloud, your SQL app engine, or any other services you use. Now a project is going to consist of the users, your APIs, any billing requirements, authentication, and monitoring as well. But with that said, a project is extremely useful for many different reasons. Let's go ahead and create a project. Now, as you see, I'm logged in, and I have one project already created, and it looks like I already have another one. So I have two total. Now I go ahead and create a new project here, and when I create a project, you'll notice that it says I have 23 projects remaining in my quota. Well, that's essentially the quota that is set based on the type of account that you're using at the time. So if you have a free tier versus a paid account, your quota will likely be a little different. And if you do need to exceed that for some reason, you would have to put in a request for support, and they would normally approve it unless there's a reason not to. But basically the first thing we want to do is name our project. Now, generally, you want to name a project something that makes sense to your organization. so I'll call this production. Now if I was using G Suite and I had an organisation essentially set up, I could go over here and basically add the organization, and then under that organization, the projects would be under the organization. So basically, just like it's saying here, the organisation would be the parent, and the projects that I would have under that organisation would be the have under that orgaThat's actually a really nice way to structure lifecycle management. You could also structure the permissioning and add granularity as well. You can have the organisational admin manage all the projects, or you could just delegate it to the individual project owners, whichever you so choose. Now, when we create a project, there are three things to pay attention to. Generally, the first thing is the name; the second thing is the project ID. So I could go ahead and change the project ID at the time of creation. Now I can't change it after I create the project, and then after we create the project, we're going to have a project number. Now the project number will not be something we could change, so basically it's going to go ahead and create a project. And once that project is done, we'll go ahead and take a look at all the information about that project, and it looks like it's already done. So if we go up here, you could see that now we have our third project, which is called "production." So we have our project ID right here, and you see that these are the project ideas. This is a project name and the project number. Now, generally, when we reference a project, if we're using Google Cloud or if we're using our APIs, we're going to want to reference the project ID, essentially. So if I go into production, you can see that I don't have any resources for this project. Well, that's because I just created the project. And what do I have to do? I have to create resources and add them into the project. Now, if I go back to the previous project, you can see that I already had resources for that project. So remember, a project is a way to organise your Google Cloud resources. Generally, as a best practice, you may want to have production resources in one QA and development in another QA. Or you could also think aboutit from a compliance perspective. Maybe you have specific information that can't leave, for example, the US. It has to be based in the US. So you want to create a project with resources thatare essentially located in a region in the US. So creating a project is very straightforward. Now, you create a project in console byGcloud or also the API as well. With that said, let's continue onto the next part of the course.

Pay a fraction of the cost to study with Exam-Labs Professional Cloud Developer certification video training course. Passing the certification exams have never been easier. With the complete self-paced exam prep solution including Professional Cloud Developer certification video training course, practice test questions and answers, exam practice test questions and study guide, you have nothing to worry about for your next certification exam.

Hide