Helen will come back with more with more AWOS or descaling fun.
So let's see what we have now.
While troubleshooting a problem in your application so you had an application and you were troubleshooting
a problem.
You have stopped and restarted an instance multiple times to try to fix the problem.
There was one instance where the problem was defined.
And then you started restarting stopping and restarting the instance multiple times after the problem
was fixed.
Good news.
You then nontheist that the associated the associated odors killing group has determined the instance
that you you're troubleshooting restarting stopping as unhealthy and marketed to be replaced.
Oops.
So you were trying to troubleshoot the problem.
You did not know that there is something called Stand by state.
You could have taken the instance out into the done by state troubleshoot whatever you like.
Still it is managed by auto scaling but skinning when not check the health of of the instance.
So that's that's the right procedure to troubleshoot a problem to instance and avoid having auto scanning
considered it considers it as an unhealthy one.
Ok now it is Mark like you didn't know that.
Now you figured that out from the auto scaling dashboard that these two instances marked for termination
you do not want Skilling to terminate at these instance he's healthy there's nothing wrong about it.
And you where the the reason why it was considered by easy to status checks and is it the status checks
then told auto scaling that this instance is unhealthy.
What can you do to ensure the instance is back to healthy state and will not get terminated.
A You cannot take it back to the state once it's marked for placement.
As we know from the auto scaling that this is not quite accurate.
What about the instance the other Skilling will then added back to the healthy state instances.
Wrong because of scaling if any easy to instance is reported by easy to status checks as anything the
status the state of that is it for instance is reported to be anything except for running state.
So if it is pending If it is stopped if it is rebooted if they've terminated all that.
That means Skilling will market for me.
See manually add the instance back into the auto skating group if the oldest killing determined an instance
to be more marketed for termination doesn't mean that it has expelled it from the upskilling group for
you to hit that game market means it is scheduled for termination during a very limited time you can
use the command line interface command auto scaling said instance health to mark the instance as healthy.
And this is the correct answer.
So this is wrong.
This is wrong.
And this is wrong so this is the correct answer.
But it is a very short period of time.
And here since the question did not mention that it started to be terminated because if auto scaling
more except for termination it waits for a very limited timeframe before it starts terminating the instance.
If you were able to issue that command within that limited timeframe then the instance would be set
back to healthy and the market for emulation will go away.
If you did the command after it started to terminate you would receive an error back of that.
And since he's already terminating
Cato is incorrect B is incorrect C is incorrect and D is the correct answer.
And if we know why is incorrect because within a very short period of time it is marked for replacement.
You can't you can bring it back to healthy b is incorrect because once it's labeled for replacement
we'll soon start to terminate.
So rebidding does not help.
Incorrect for C because you can do this you can manually add it because it's not expelled to start with
and the is your correct answer and things to remember once marked for placement the oldest getting service
will shortly after that start to terminate the instance and then replace it with another.
So if it is marked for replacement for termination and then remember that if an instance is defined
as unhealthy auto scaling will first terminate and to launch new instances this is for unhealthy instances
but for rebalancing it was the other way around.
So number one is launch in the instance in the it is on that do not have enough instances and then terminate
from the ones that were available.
It's a completely different approach.
During the very short time when do you can use the said instance health command as we mentioned.
And if there are two Skilling groups started it tell me the instance you would get an error back when
you issue the command
and last advice that when troubleshooting an easy to instance if that is it to a status check reported
the instance as anything the state of the instance as anything except the running state or scaling will
process or just getting process were considered as unhealthy.
And one market for replacement.
What's the solution.
Move the instance into a standby state under the auto scaling group do your troubleshooting and then
put it back through.
It will go through pending auto scanning will do a health check.
And if healthy is going to be again in service under the water skinning group Greg next question an
instance in an auto Skilling group has been reported by easy to status checks to the auto scaling process
as unhealthy or just killing the market for replacement.
Which of the below statement is correct and it is two answers in auto scaling will start shortly after
that to terminate they see to instance we just discussed that in the previous question.
This is correct.
I have two answers and here we said which of the below statements is correct.
We did not mention anything.
There is no not.
So those three magical letters of not that can make that white color black and the black color white
are basically invert the question completely is not here and that's why it is correct.
The oldest killing it has to launch a replacement first then terminate the unhealthy instance.
This is wrong.
This happens during that launching a new one first and then terminating happens you rebalancing sea
otter skin has to be to do a rebalancing first then terminate the instance wrong.
We're not talking about rebalancing situation or talking about unhealthy instances.
The auto scanning will terminate the instance first then launch a new one and that is correct because
there is no point in keeping an unhealthy instance it's not going to carry your load.
It's going to be healthy for your production traffic and that's why it makes more sense to terminate
it and then launch a new one.
So is correct.
B and C are wrong and the.
Is correct and and the are correct answers and for our refresher for rebalancing a new instance is launched
first then the ones causing the imbalance get terminated for unhealthy instances.
The other way around.
All this killing has to terminate the unhealthy first because you don't need them and they are not going
to do you any benefit then launch a new one or new ones based on how many were marked as unhealth next
question you are newly hired too.
You can do it too.
Incorporated as the years as I mean you were tasked to review the AWOS environment and recommend enhancements
so you have an environment set up and now you are the expert and you were given a task to review the
environment and come up with any enhancements as applicable.
One of the resulting recommendations that you had was to merge the three different single easy authors
getting groups into one.
So there were three different authors getting groups if one in one everybody's on is G-2 in another
I believe it is on is G-3 in a third I believe it is on how can this be achieved.
Delete two of the groups and the third will automatically be configured to stretch and cover the other
two.
I mean it is wrong.
This is not how it is getting worse.
It's not automated stretching into area it is on you have to manually define the outer skin in groups
of the group and where it is applicable which I mean it is isn't be used and it has command line interface
command to stitch the three groups into one.
There is no such a thing a command that will stitch all those groups together.
See define one of the three other Skilling groups to cover their availability zones of the other two.
I believe it all just getting groups and then delete the other two.
And that's how it works.
The create a Forth group that covers all three of everything and then delete the original three.
This is wrong because when you merge auto scaling groups you basically pick one of them.
Make sure that it is effective.
Now in the other two I believe it is on.
And then you can delete the old ones but the one that you will choose to be the umbrella across the
different everybody's and must be one of the preexisting single everybody's owns or just getting groups
that you wanted to merge.
Right so the correct answer is see Google pressure to merge existing single everybody's own or just
killing groups one of them must be updated to spend the set of I it is zones of all groups.
Then delete the remaining other skinning groups except the one that you have configured to span or storage
to all of the zones manually.
The final one the one that represents the merge must be one of the original authors killing groups and
not a new one.
All right.
So let's take a quick break and then we'll come back for more on descaling fun.
I'll see you shortly.