Topic 1 Question 121
Your managed instance group raised an alert stating that new instance creation has failed to create new instances. You need to maintain the number of running instances specified by the template to be able to process expected application traffic. What should you do?
Create an instance template that contains valid syntax which will be used by the instance group. Delete any persistent disks with the same name as instance names.
Create an instance template that contains valid syntax that will be used by the instance group. Verify that the instance name and persistent disk name values are not the same in the template.
Verify that the instance template being used by the instance group contains valid syntax. Delete any persistent disks with the same name as instance names. Set the disks.autoDelete property to true in the instance template.
Delete the current instance template and replace it with a new instance template. Verify that the instance name and persistent disk name values are not the same in the template. Set the disks.autoDelete property to true in the instance template.
解説
ユーザの投票
コメント(17)
Really tricky question. Ideal scenario would be
- create new template, while creating ensure that in the new template disks.autoDelete=true, 3. delete existing persistent disks, 4. make rolling update ... In order to switch to new template we need "Rolling update". Unfortunately, it is not mentioned.
With current options C - not correct, we cannot update existing template D - not correct, we cannot delete existing template when it is in use (just checked in GCP) (We need rolling update) B - will not solve our problem without Rolling update A - This is the only option (I know that it can be temporary) that will work without Rolling update according to https://cloud.google.com/compute/docs/troubleshooting/troubleshooting-migs
👍 48TAvenger2021/02/21Correct Answer is (C): Your instance template has set the disks.autoDelete option to false for boot persistent disks so that when a VM has been deleted (for example, because of autohealing), the persistent disk was not deleted. When the managed instance group attempted to recreate the VM with the same name, it ran into the same issue where a persistent disk already exists with the same name. Delete the existing persistent disk to resolve the immediate problem and update the instance template to set the disks.autoDelete to true if you would like boot persistent disks to be deleted alongside the instance
👍 41ESP_SAP2020/08/20- 正解だと思う選択肢: A
Answer : A As many have mentioned here C and D is straight NO, C talks about updating the instance template and D talks about deleting an instance template BUT as per google documentation you cannot delete an instance template nor update it if it is in use. So A is the only one the makes sense here.
https://cloud.google.com/compute/docs/instance-templates#how_to_update_instance_templates
👍 5bobthebuilder551102022/08/03
シャッフルモード