Associate Cloud Engineer certification video training course by prepaway along with practice test questions and answers, study guide and exam dumps provides the ultimate training package to help you pass.

Gcloud for Associate Cloud Engineer

6. Step 06 - Setting Default Region and Zone for Compute Engine

Whenever we are playing with compute instances, the configuration of the default zone and region is very, very important. Let's see the different options that are present to configure the default region and zone for Compute Engine. Let's look at the three options first.

The first option is centralised integration. This is basically the compute engine configuration for a specific project. The command-line way you can actually do that is by calling Get G Cloud Compute Project Info and adding metadata. The metadata is the option that must be passed in. So you need to say "metadata." You can say Google Compute's default region is equal to a specific region or Google Compute's default zone is equal to a specific region. Now, where can you see this in the UI?

The place you can actually see this in the UI is if I go back to Compute Engine, minimise the virtual machines, and go to Settings, and inside Settings there are settings. So this is the metadata that we are configuring right now. And over here, you can see that the default location is configured here. This is where you can configure the selected region and zone. You can see that this is right now empty, and that is what you can actually configure by using this command. So G Cloud, Compute, Project Info, and Add Metadata would help you set the metadata for the current project to include a default region and a default zone.

The other option is the local G cloud configuration. We have done this multiple times earlier. set compute region region in Gcloud configuration The third option is command-specific. In every command that you would use, you could specify a zone and a region in that specific command. So if you look at the documentation for GcloudCompute instances create, if you look at this command, and if you search for "hyphen zone," you can see that you can specify the zone where a specific instance has to be created. Some commands allow zones, and some commands allow you to configure regions. So in the specific command that you are executing, you can specify your zone and a region.

Now, which of these options has the highest priority whenever you specify a zone or a region as part of your command? That is the one that has the highest priority. So option three has the highest priority, which overrides option two. If you have a local G Cloud configuration where you have already set the region inside the configuration that you are making use of, that has the second-highest priority, and the lowest priority is for the centralised configuration.

However, the important thing to remember is that this is a centralised configuration. You are making this configuration directly in the service. So this configuration is applicable to any user in this specific project. However, that specific user might choose to override the default configuration or centralised configuration by specifying a local G Cloud configuration or a command-specific configuration. I'm sure you're having a wonderful time, and I'll see you in the next step.

7. Step 07 - Exploring Gcloud commands - list and describe

Welcome back. In the last few steps, we were playing with G Cloud commands. There are two specific types of commands that are very, very common: list and describe. Let's look at them in depth in this specific step. Typically, these commands are used to list a set of resources. You want to list the instances, regions, and zones, so gCloud compute resources list g) Cloud compute images, regions, zones, or disc types list g: compute instances, disks, and snapshots in the cloud list If you look at this list of commands, most of them support a few common options. We already looked at the filter earlier and outside the Cloud Compute Regions List, so this would list the list of regions. If I go ahead and authorise it, let's go ahead and authorise it.

Let's set the current project to "Cloud Configuration Set Project" and let's pick up the project information from here. So, whenever you use Cloud Shell for the first time, you must define your project. Let's go and try to run the G Cloud Compute Regents try to ruIt lists a set of regions. You can also list zones. Compute the zones list, for example, in G Cloud. What would happen? It would list the list of zones. Let's say I wanted to list the zones that are present in a specific region. That's where we can use a filter. So I can say the filter is equal to the fact that if I scroll up, I can see the name of the column. So what's the name of the column? "region." As a result, filter equals region colon US two. So I can filter all the zones in a specific region by using a filter. And this is applicable to any list command. As you can see, there are three zones in US West 2: A, B, and C. So you can say "Hyphen filter." You can also sort by hyphenifen.

So I can say that in addition to filter, I can say sortby, and I can specify what you want to sort by. Let's say I want to sort by region name. Then everything is sorted by region name. You can see that you are the one who is coming last, and everything is in alphabetical order. Asia is listed first, and if you want to sort it in the reverse direction, you can say "Till till region," and this would sort in the reverse direction. So you can see that Asia comes last and the US comes first. And you can also get the Uris. So if I actually say Hyphen Uri, for each of the resources in Google Cloud, there is a Uri that is associated with them, and this would bring back the URLs that are associated with each of these zones.

So if you want to see the URLs that are attached to a region, you can say region. list should be called the Regents List, and this would list the URLs for all the regions inside my current project. A little later, we'll see how you can make use of Uris in the commands you run. So you can see an example of images in this section. So G Cloud Compute Images, list, sort by name, filter, and project Windows or open to. So whenever you see a list command, whether you are listing images, regions, zones, these types, instances, this snapshot, or anything else, you'd see that they would support filter, sort by, and Uri. The next set of commands you'd look at are described commands. We already executed the described command earlier. Images from G Cloud Compute. Describe a specific image. Or you can say "G Cloud Compute regions." Describe a specific region.

So let's actually start with that. The list of regions would be displayed in the G Cloud Regions list. And if you want to describe a specific region, you can say "G Cloud Compute Regions." It would provide all the details that are associated with a specific region. As a result, G Cloud compute regions describe us. The last option that you are seeing here lets you print all the details that are associated with that specific region. There are a lot of quotas that are assigned. You can see the description, the kind of region it is in, the name of the region, and the date it was created. The created timeline does not look good. It says "1969." You can see the different quotas that are associated with that specific region. Similar to that, you can describe images, regions, or whatever resources you'd want to describe. We looked at a couple of important types of commands on the list in a previous step and described how you're having a great time, which I'll show you in the next step.

8. Step 08 - Playing with Compute Instances in Gcloud

Welcome back. Let's quickly look at some of the commands we looked at earlier for playing with compute instances. You want to start, stop, delete, reset, or describe compute instances whenever you're playing with them. Let's look at a few examples. CloudCompute Instances begin with a unique instance name. What does it do? It would start those specific instances of cloud computing instances, stop example instance one, and start example instance two. We're using spaces to separate the instance names over here. This would bring both instances (example instance one and example instance 2G cloud compute instances) to a halt; we had already deleted one.

That's exactly the command that we used when we deleted the instance, except that we used the specific instance name. One important fact to remember when you are deleting instances is to delete disks. There are a lot of discs that can be attached to your compute instance. The boot disc is the one where your operating system is running. A variety of other data discs can also be attached to your Compute instance. So if you want to delete all the discs that are attached, then you can say "hyphen delete disc is equal to all." If you want to delete only boot discs, then you can say Hyphenife and delete Hyphen disks, which are equal to boot. Otherwise, you can say "Data" to delete the data disks.

The opposite of delete is Keep disks. So you can say "Keep disks" and specify which ones you want to keep. The other command that is interesting in Gcloud Compute instances is the Move command. If you want to move a specific instance from one zone to another zone, you can use the Move command. Over here, you can see the example for Gcloud Compute Instances for a specific instance you want to move from US Central One B to US Central One F. So this is moving a VM from one zone to another. In this quick step, we look at some of the important commands to play with Compute instances. I'll see you in the following step.

9. Step 09 - Playing with Instance Templates in Gcloud

Back on track. Let's look at a few commands to play with instance templates. Earlier, we used Web Console to create a number of instance templates. You can also create instance templates from the command line. "Create cloud compute instance templates" is the command. You can also delete, list, and describe the instance templates. Let's start by listing the instance templates that we created earlier. So. G Cloud Compute instance templates.

Let's do a quick review here. G Cloud Compute instance templates. I'll go with list. This would show the list of instance templates that we created earlier. So my instance template with custom images and my instance template with startup script are shown in the G Cloud Compute Instances list. If you want, you can create a new one as well. So I can just say "Create a CloudCompute Instance Template" and name it. Let's say I would want to call this instance template from the command line. This would be created with the default configuration. So you'd see that an instance template would be created.

And if I do a Gcloud instance templates list, you'd see that there is one that was just created. So, from the command line, instance template, you can see that the default machine type, which is N one standard one, is associated with that specific instance template. You can also delete it if you want. So you can say "Cloud Compute Instance Templates Delete" and specify the name of it, and this would delete that specific instance template. So the instance template will be deleted. Let's go ahead and say yes if you want.

You can also describe an instance template. So I can say, "Check out Compute instance templates," and I can look at all the details in a specific template. I can specify my instance template with a custom image and examine all of the details surrounding it. So you can see all the details inside that specific template. Here, you can create your instance template by using the Create command; we did the default create. However, even if you don't make one, you can still make an instance template. From a source instance, you can create an instance, and from that specific source instance, you can create your instance template.

When doing this, you also need to specify the source instance zone. Which zone is that instance running in? One important thing to remember about creating an instance template is that it supports almost all the options that are supported by Google Cloud Compute instances. Creating instance templates is very similar to creating instances, except that over there we are creating instances. However, over here with instance templates, we're creating a template that will be used to create the instances.

So you can specify the image, family snapshot, or instance template. You can specify if you want to use a service account or not. You can specify the tags, and you can specify if you want to create preemptible instances. You can specify if you want to restart on failure. You can also specify a maintenance policy. You can also specify the size and type of the boot disk. Do you want to auto-delete the boot disk, or do you not want to auto-delete the boot disk? Specify the hyphen by specifying the "hyphenno boot disc auto delete option." You can specify if you want delete protection or if you don't want delete protection. You can also specify the metadata or the metadata from a file and specify the startup script or the shutdown script.

You can also specify the network to which you'd want to attach the instance that you would create from it. You can also specify the network and the subnet. You can also specify if you want to create GPU instances. So all the things that you can specify with G Cloud Compute instances are created. You can specify this when creating your instance templates. Once you specify this configuration with your instance template, whenever you create an instance using that specific template, the instances will have that configuration by default. Now let's do a Google Cloud Compute instance.

Templates list. Now let's say you have already created an instance template. You have configured it, and it is ready. You want to create an instance from that specific instance template. How do you do that? The command is very simple, right? I'd like to give my instance a name, so call it my test VM. I want to use this instance template to create this specific VM. How can I specify that we looked at it when we talk about creating G Cloud Compute instances create? The way you can do that is by specifying an option called "Source instance template." So you can say instance template, and then specify sequel two and its name. my instance template with a custom image, and you can press Enter.

You can see that it's asking me for a zone. I'll use the zone that is suggested. The other option would have been to pass the zone that I would want to use as part of my command as well. Let's go ahead and say yes. So you can see that the instances are now created, and if I actually take this external IP and go and run this Oops, not yet. After a couple of minutes, I see that I have gotten a response back from that specific instance. So you can see that you can easily use instance templates to create your instances from the command line as well. Except we looked at some of the most important commands for experimenting with instance templates. I'll see you in the next one.

Prepaway's Associate Cloud Engineer video training course for passing certification exams is the only solution which you need.