You are in charge of designing a Cloudformation template which deploys a LAMP stack. After deploying a stack , you see that the status of the stack is showing as CREATE_COMPLETE , but the apache server is still not up and running and is experiencing issues while starting up. You want to ensure that the stack creation only shows the status of CREATE_COMPLETE after all resources defined in the stack are up and running. How can you achieve this?

Answer options:

A.Define a stack policy which defines that all underlying resources should be up and running before showing a status of CREATE_COMPLETE.B.Use lifecycle hooks to mark the completion of the creation and configuration of the underlying resource.
C.Use the CreationPolicy to ensure it is associated with the EC2 Instance resource.
D.Use the CFN helper scripts to signal once the resource configuration is complete.

Answer – C and D
The AWS Documentation mentions
When you provision an Amazon EC2 instance in an AWS CloudFormation stack, you might specify additional actions to configure the instance, such as install software packages or bootstrap applications. Normally, CloudFormation proceeds with stack creation after the instance has been successfully created. However, you can use a CreationPolicy so that CloudFormation proceeds with stack creation only after your configuration actions are done. That way you’ll know your applications are ready to go after stack creation succeeds.
For more information on the Creation Policy, please visit the below url
https://aws.amazon.com/blogs/devops/use-a-creationpolicy-to-wait-for-on-instance-configurations/