What happens, by default, when one of the resources in a CloudFormation stack cannot be created?
A.
Previously-created resources are kept but the stack creation terminates.
B.
Previously-created resources are deleted and the stack creation terminates.
C.
The stack creation continues, and the final results indicate which steps failed.
D.
CloudFormation templates are parsed in advance so stack creation is guaranteed to succeed.
B
https://aws.amazon.com/cloudformation/faqs/
…
Q: What happens when one of the resources in a stack cannot be created successfully?
By default, the “automatic rollback on error” feature is enabled. This will cause all AWS resources that AWS CloudFormation created successfully for a stack up to the point where an error occurred to be deleted. This is useful when, for example, you accidentally exceed your default limit of Elastic IP addresses, or you don’t have access to an EC2 AMI you’re trying to run. This feature enables you to rely on the fact that stacks are either fully created, or not at all, which simplifies system administration and layered solutions built on top of AWS CloudFormation.
B