C_THR78_2111 - SAP Certified Application Associate - SAP Litmos - PDF document

Learning SAP Certified Application Associate - SAP Litmos Dumps Certification Get your required dump now: https://certsgot.com/product/dumps - c_thr12_67 - sap - certified - application - associate - sap - hcm - with - erp - 6 - 0 - ehp7/ Copy Paste The Above URL To Get The Dump Related Information So now we’ll go to the auto - scaling groups, and I’ll create an auto - scaling group over here. Now, whenever you create an auto - scaling group, you have to select the launch configuration as the first step. So w e’ll select the launch configuration as Kplabs’ identity. This is the one that we created. Now you need to give the name of this autoscaling group, which I’ll call Kplabsg, the group sites. It will start with one instance. It is asking me into which VPC I want to launch subnets. I’ll give three subnets: one for A, one for B, and one for C. So, basically, this will assume that the first instance launched will be part of one A. It will be part of one B when it scales up, when it creates two in the second inst ance. When it creates the third instance, it will be part of one C. Perfect. Now we’ll configure a scaling policy. I’ll select the second option. So it asks me to scale the number of instances to one, and depending on your configuration, you can even put five. So whenever the load increases, it can horizontally scale up to five instances. So I’ll just select three for now and click on the specific option. And now you have two policies over here. One is to increase the group size, and you need to create a n ew alarm. So I’ll deselect send notification to SNS, and in this cloud watch alarm, what I’ll do is you have to create a policy. Let’s assume if the average CPU utilization is greater than or equal to 70% for at least one consecutive period of time — I would say 1 minute over a year — and you have to give the name of the alarm. So I’ll say KP Lab scale. So this is the name of the alarm, you see. So if the CPU utilization is greater than or equal to 70%, then this alarm will be triggered. So I click on “create a larm,” and if this alarm is triggered, what should be done? and that is something that we have to define. So I’ll say you should add two instances. Perfect. Now we’ll have to create a second policy as well, which says decrease the group size, add one more alarm, and deselect the SNS topic. And here it says whenever average CPU utilization this time is less than equal to, say, 20% for at least one consecutive period of, say, 1 minute, the name of the alarm will be KP Labs’ hyphen scale. I’ll set the alarm o ver here and hyphen down. Perfect. So now I have two policies. I’ll go ahead and configure notifications now. So this is where we can add a notification. So if a new instance gets launched, if an instance gets terminated, or due to some activity in the lif e cycle, if we want to get notified via email, you can do that over here. So I’ll leave this up as a default. Let me just cancel it. I’ll then click Review to create an auto - scaling group. So the auto - scaling group is created. Now, if you see over here, si nce our minimum instance is one, what auto scaling will do is it will automatically start one instance. So if you see the first instance, it has already been started.