DOP-C02 Configuration Management and IaC 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.

• ✗

  The LaunchTemplate was recently modified and the new version is not yet available

  Why it's wrong here

  Modifying a launch template in the EC2 console automatically creates a new version that is immediately available for use. AWS CloudFormation does not need to wait for any propagation or caching when referencing a specific version number by ID, so a recent modification would not cause a 'version not found' error. If anything, you would simply need to update your template to point to the new version if you wanted to use it, but the old version would still exist and be valid.

• ✓

  The LaunchTemplate version specified in the template was deleted

  Why this is correct

  The most direct cause of a 'LaunchTemplate version not found' error during stack update or creation is that the exact version number specified in the CloudFormation template has been deleted. Launch template versions are immutable but can be manually deleted (except the default version) when no longer needed, and CloudFormation validates that the referenced version exists before provisioning resources. Once deleted, any stack operation referencing that version fails because the template is effectively trying to instantiate a non-existent configuration.

• ✗

  The target group attachment is incorrect

  Why it's wrong here

  A misconfigured target group attachment would manifest as load balancing or health check failures, not as an error referencing a missing launch template version. The target group and its attachments are independent AWS resources that are created and associated with the Auto Scaling group separately from the launch template definition. Therefore, an incorrect target group would not produce the 'LaunchTemplate version not found' error message that the stack is reporting.

• ✗

  The Auto Scaling group is using a different launch template

  Why it's wrong here

  If the Auto Scaling group were using a different launch template, the stack would still be able to deploy, but the running instances would not match the intended configuration. The error described is specifically about the version identifier in the LaunchTemplate property, meaning CloudFormation cannot resolve the exact version you requested. A different template would be a configuration mismatch, not a missing-invalid reference, so the error would be about the reference itself rather than a comparison between templates.

Go deeper

Related to this question