You have a launch template where a subnet is specified in its network interface. Now you need to use AWS CLI (aws autoscaling create-auto-scaling-group) to create an Auto Scaling group with the launch template. However, the ASG should be launched in another subnet that is different from the one specified in the launch template. How would you create the ASG with the AWS CLI command?

Answer options:

A.Modify the subnet in the launch template and create the ASG using the latest version of the launch template.
B.Change the subnet in the launch template. In AWS CLI (aws autoscaling create-auto-scaling-group), specify the subnet through the --launch-template option.
C.Specify the subnet through the --vpc-zone-identifier option in AWS CLI (aws autoscaling create-auto-scaling-group). The subnet in the launch template is ignored.
D.Create another launch template with the new subnet in its network interface. In AWS CLI (aws autoscaling create-auto-scaling-group), specify the same subnet through the --vpc-zone-identifier option.

Correct Answer – C
Option A is incorrect: Because the subnet in the launch template is ignored when creating an Auto Scaling group. The subnet needs to be specified in AWS CLI (AWS autoscaling create-auto-scaling-group).
Option B is incorrect: Because the subnet should be specified in the --vpc-zone-identifier option of AWS CLI.
Option C is CORRECT: When creating the ASG using AWS CLI command, the subnets should be specified in the --vpc-zone-identifier option.
Option D is incorrect: Because there is no need to create a new launch template. You just need to specify the subnet in the --vpc-zone-identifier option.
Reference:
https://docs.aws.amazon.com/autoscaling/ec2/userguide/create-launch-template.html
https://docs.aws.amazon.com/autoscaling/ec2/userguide/create-asg-launch-template.html
https://docs.aws.amazon.com/cli/latest/reference/autoscaling/create-auto-scaling-group.html