DVA-C02 Troubleshooting and Optimization 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 IAM user does not have permission to create the resource.

  Why it's wrong here

  If the IAM principal (user or role) executing the CloudFormation stack lacks the necessary permissions to create a specific AWS resource, the operation would fail with an explicit "Access Denied" error. This error typically occurs when CloudFormation attempts to make an API call to the underlying AWS service on behalf of the principal and is rejected due to policy restrictions. The "Resource creation cancelled" status does not indicate a direct permissions failure but rather a termination due to a broader stack event.

• ✓

  Another resource in the stack failed, causing a rollback.

  Why this is correct

  When a CloudFormation stack creates multiple resources, these operations often occur in parallel or a defined sequence. If one resource fails to create or update successfully, CloudFormation's default behavior is to initiate a rollback of the entire stack to its previous stable state. During this rollback, any resources that were in the process of being created or updated, but had not yet failed themselves, will have their operations terminated, resulting in a "Resource creation cancelled" status. This indicates an orchestrated termination rather than an individual resource failure.

• ✗

  The template has a syntax error.

  Why it's wrong here

  CloudFormation performs a thorough validation of the template's syntax and structure before attempting to provision any resources. If the template contains a syntax error (e.g., malformed JSON/YAML, incorrect intrinsic function usage), the stack creation process would fail immediately during this validation phase. The error message would clearly state a "Template validation error" or similar, preventing any resource creation attempts, thus not leading to a "Resource creation cancelled" status.

• ✗

  The resource type is not supported by CloudFormation.

  Why it's wrong here

  If CloudFormation encounters a resource type it does not recognize or support (e.g., a typo in the type, or a service not integrated), the stack creation would fail during the initial validation or very early in the provisioning process. The error message would explicitly indicate an "Unsupported resource type" or "Invalid resource type," not "Resource creation cancelled," which implies an operation was initiated but then terminated due to an external factor.

Go deeper

Related to this question