Your company is running a stateless application on a Compute Engine instance. The application is used heavily during regular business hours and lightly outside of business hours. Users are reporting that the application is slow during peak hours. You need to optimize the application's performance. What should you do?
To optimize the performance of a stateless application running on a Compute Engine instance, you should create a custom image from the existing disk. This custom image ensures that the application environment remains consistent across different instances. Next, you create an instance template from the custom image, which specifies the machine type, disk configuration, and other instance settings. Finally, you create an autoscaled managed instance group from the instance template, allowing you to automatically scale the number of instances based on the demand. This approach ensures high availability and performance during peak hours while maintaining cost efficiency during off-peak hours.
The easiest way would be to create template from --source-instance, and then create MIG, but it is not listed here, also you cannot create a MIG from image directly, you need a template, so answer is C (image -> template -> mig).
C is correct. To sdsdfasd4's point - Not recommended to create template from --source-instance as If the existing instance contains a static external IP address, that address is copied into the instance template and might limit the use of the template. Templates are best created from images or other templates. Creating the template from a running instance may require work to clean it up before it can be used for a MIG
C is the right answer
C is definitely the right answer
06/30/2022 Exam
Option C is the correct choice because creating a custom image from the existing disk ensures that the application environment is consistent and does not change between instances, which can reduce variability in performance. Creating an instance template from the custom image allows you to easily create new instances that are based on the same image, which can save time and effort. Finally, creating an autoscaled managed instance group allows you to automatically scale the number of instances based on demand, which can ensure that there are enough instances to handle peak traffic while minimizing costs during periods of low traffic
C – create a custom image from the existing disk. Create an instance template from the custom image. Create an autoscaled MIG from instance template. A could work if a snapshot was transformed to a custom image. Instance Template can be created only from image.
C is the right answer. https://cloud.google.com/compute/docs/instance-templates/create-instance-templates#using_custom_or_public_images_in_your_instance_templates
Go for C. Instance template can not be created from snapshot. Only from an image.
I think Snapshot option are not correct in this scenario as to take snapshot you need to stop the VM so C looks best option
it's possible to create a snapshot of running VM by reducing I/O disks
C is ok
C We can create an instance from an image or a custom image or a snapshot but an instance template can be created using either image or custom image only. Also refer: https://cloud.google.com/compute/docs/instance-templates/create-instance-templates
C. The key here is stateless, so we don't need snapshot the actual instance, we can start from zero.
vote C
C is the answer
C is the answer
C is correct
C is right. Create a custom image from the existing disk. Create an instance template from the custom image. Create an autoscaled managed instance group from the instance template.
I prefer B, is better because I don't need to stop the instance to create the disk image.