Which of the following is TRUE statements when describing the differences between Elastic Beanstalk and CloudFormation?
AWS Elastic Beanstalk introduces two concepts: The template, a JSON or YAML-format, text- based file
Elastic Beanstalk supports AWS CloudFormation application environments as one of the AWS resource types.
Elastic Beanstalk automates and simplifies the task of repeatedly and predictably creating groups of related resources that power your applications. CloudFormation does not.
You can design and script custom resources in CloudFormation
Explanations:
Elastic Beanstalk does not introduce a template concept; instead, it uses application versions and environments. CloudFormation, on the other hand, uses templates in JSON or YAML format to define AWS infrastructure.
Elastic Beanstalk is a service that deploys applications and manages the underlying infrastructure, while AWS CloudFormation is used for defining and provisioning AWS resources in a predictable manner. Elastic Beanstalk does not directly support CloudFormation environments as resource types.
Elastic Beanstalk simplifies application deployment but relies on CloudFormation under the hood to manage the resources. CloudFormation itself is capable of automating and simplifying the task of creating groups of related resources, so this statement is misleading.
CloudFormation allows you to define and script custom resources using AWS Lambda functions or other services to extend its capabilities, enabling more complex infrastructure setups beyond the default AWS resource types.
I chart that the answer is:
You can design and script custom resources in CloudFormation