Your team currently has an Autoscaling Group defined in AWS used to manage the EC2 Instances for an application dynamically. Now there are some issues with the application. The team needs to debug the problem. What can be done to ensure that this requirement can be fulfilled?

Answer options:

A.Delete the Autoscaling Group so that you can investigate the underlying Instances.
B.Delete the Launch Configuration so that you can investigate the underlying Instances.
C.Suspend the scaling process so that you can investigate the underlying Instances.
D.Use the AWS Config to take a configuration snapshot of the Instances and then investigate the underlying Instances.

Correct Answer: C
The AWS Documentation mentions the following.
You can suspend and then resume one or more of the scaling processes for your Auto Scaling group. This can be useful when you want to investigate a configuration problem or other issue with your web application and then make changes to your application without invoking the scaling processes.
Amazon EC2 Auto Scaling can suspend processes for Auto Scaling groups that repeatedly fail to launch instances. This is known as an administrative suspension, and most commonly applies to Auto Scaling groups trying to launch instances for over 24 hours but have not succeeded in launching any instances. You can resume processes suspended for administrative reasons.
Options A and B are incorrect since you should not delete either the Autoscaling Group or the Launch Configuration. This will disrupt the architecture of the application.
Option D is incorrect since this is not possible with the AWS Config service.
For more information on suspending and resuming autoscaling processes, please visit the following URL-
https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-suspend-resume-processes.html