DOP-C02 Monitoring and Logging Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Create launch template, then Auto Scaling group, then configure network, then set capacities, then add scaling policy

  Why this is correct

  This is the correct order because the launch template must exist before creating the Auto Scaling group, network configuration is part of the group creation, capacities are set after group is created, and scaling policy depends on capacities.

• ✗

  Auto Scaling group, then launch template, then configure network, then set capacities, then add scaling policy

  Why it's wrong here

  An Auto Scaling group cannot be created without an existing launch template (or legacy launch configuration) because the group is only a wrapper that references the template to know which AMI, instance type, security groups, and user data to use when launching instances. The CreateAutoScalingGroup API call normally requires a LaunchTemplate or LaunchConfigurationName parameter, so attempting to create the group first will produce a validation error. Additionally, the network configuration, such as VPC and subnets, is selected during the group creation flow after the template is chosen, so reversing the order breaks every subsequent dependency.

• ✗

  Configure network, then launch template, then Auto Scaling group, then set capacities, then add scaling policy

  Why it's wrong here

  Configuring the network is not a discrete pre-step; VPC, subnets, and Availability Zones are selected as part of the Auto Scaling group creation flow, after the launch template is chosen. A launch template itself may contain network interface settings, but the ASG still requires you to specify VPC subnet or AZ placement when you create the group, and that placement can override or complement the template. Doing network configuration before a launch template or ASG exists has no target object to attach to, and the AWS console/API will not let you define a standalone 'network' for a future group. The correct order is template, then group, with network as a step inside that group creation process.

• ✗

  Create launch template, then Auto Scaling group, then configure network, then add scaling policy, then set capacities

  Why it's wrong here

  Adding a scaling policy before setting the group's capacity limits is invalid because every scaling policy, whether target tracking, step, or simple, operates by adjusting the DesiredCapacity within the currently configured MinSize and MaxSize boundaries. If MinSize and MaxSize are not already defined, the policy has no allowed range for its adjustments, and target tracking policies cannot compute the number of instances needed to maintain a metric target without existing capacity values. For example, when you attach a target tracking policy, EC2 Auto Scaling requires the group to have healthy capacity, otherwise scaling activity will fail. Therefore, capacities must be finalized, or at least initialized, before the scaling policy is added, even though these values can be later modified.

Go deeper

Related to this question