Stateless Compute Engine app is busy during business hours and slow at peak. To scale and improve performance with autoscaling, what sequence should you perform?

To properly scale a stateless Compute Engine application, you first need a deployable artifact. Creating a custom image from the existing disk captures the application's configuration and binaries. This custom image then serves as the base for an instance template. An instance template defines the machine type, image, and other properties for instances in a managed instance group (MIG). Finally, an autoscaled MIG uses this template to automatically create and delete instances based on demand, ensuring performance during peak loads. The other options are incorrect because: Snapshotting the disk directly to create an instance template or custom image isn't the standard or most efficient workflow for creating deployable images for MIGs. Snapshots are primarily for backup and recovery. Creating an instance template directly from an existing disk or creating a custom image from an instance template are not the correct sequence or standard practices. Instance templates are built from images, not the other way around.