DOP-C02 Security and Compliance 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.

• ✓

  Upload the nested stack template, then create the parent template, then validate the templates, then create the stack, then monitor the stack creation.

  Why this is correct

  This order is correct because the nested stack template must be uploaded first so that the parent template can reference it. After creating the parent template, validation ensures no syntax errors. Creating the stack then uses both templates, and monitoring tracks progress.

• ✗

  Create the parent template, then upload the nested stack template, then validate the templates, then create the stack, then monitor the stack creation.

  Why it's wrong here

  Creating the parent template before uploading the nested stack template breaks the dependency chain: the parent template's AWS::CloudFormation::Stack resource includes a TemplateURL property that must point to a real S3 object. Without the nested template in place, CloudFormation cannot resolve that reference during stack creation, even if a syntactic validation might pass. The nested template must be uploaded first so the parent's reference is resolvable when the templates are validated and the stack is launched.

• ✗

  Validate the templates, then upload the nested stack template, then create the parent template, then create the stack, then monitor the stack creation.

  Why it's wrong here

  Validation cannot occur before the templates exist because ValidateTemplate requires the template body as input; you cannot validate a template that has not yet been written. In this sequence, validation is mistakenly placed ahead of both the nested template upload and the parent template creation. Only after both templates exist and the nested template is accessible in S3 can you meaningfully validate syntax and resource definitions, so this order fails at the first step.

• ✗

  Upload the nested stack template, then create the parent template, then create the stack, then validate the templates, then monitor the stack creation.

  Why it's wrong here

  Creating the stack before validating the templates puts the cart before the horse: CloudFormation will implicitly reject invalid templates at creation time, but by then you may have already begun provisioning resources or incurring costs. Moreover, any validation you perform after creation is useless because the stack is either already created or failed. The explicit validation step must precede stack creation so that errors are caught early, before any resources are touched.

Go deeper

Related to this question