Exam AWS Certified Solutions Architect - Associate SAA-C03 topic 1 question 594 discussion

Using EC2 hibernation and Auto Scaling warm pools will help address this: Hibernation saves the in-memory state of the EC2 instance to persistent storage and shuts the instance down. When the instance is started again, the in-memory state is restored, which launches much faster than launching a new instance. Warm pools pre-initialize EC2 instances and keep them ready to fulfill requests, reducing launch time. The hibernated instances can be added to a warm pool. When auto scaling scales out during the next testing phase, it will be able to launch instances from the warm pool rapidly since they are already initialized

https://docs.aws.amazon.com/autoscaling/ec2/userguide/ec2-auto-scaling-warm-pools.html

Amazon EC2 hibernation and warm pool

If an instance or application takes a long time to bootstrap and build a memory footprint in order to become fully productive, you can use hibernation to pre-warm the instance. To pre-warm the instance, you: Launch it with hibernation enabled. Bring it to a desired state. Hibernate it so that it's ready to be resumed to the desired state whenever needed. https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Hibernate.html#:~:text=you%20can%20use-,hibernation,-to%20pre%2Dwarm

With Amazon EC2 hibernation enabled, you can maintain your EC2 instances in a "pre-warmed" state so these can get to a productive state faster.

C: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Hibernate.html

just use hibernation option so you won't load the full EC2 Instance