You must manage AWS infrastructure as code and be able to deploy multiple identical copies, stage changes, and roll back to previous versions. Which approach fulfills these requirements?

AWS CloudFormation is the correct choice because it allows you to define your AWS infrastructure as code (IaC) using templates. This enables the creation of multiple identical copies of environments, facilitates staging changes, and supports rolling back to previous versions by updating or deleting stacks. AWS CodeCommit is a managed source control service that integrates well with CloudFormation, providing version control for your CloudFormation templates, which is essential for tracking changes and enabling rollbacks. Cost allocation reports and AWS OpsWorks are not primarily designed for infrastructure as code or version control of infrastructure definitions. Amazon CloudWatch metrics and alerts, along with resource tagging, are for monitoring and organization, not for defining and deploying infrastructure as code. AWS Elastic Beanstalk automates deployment and scaling of web applications, but CloudFormation offers more granular control over a wider range of AWS resources for comprehensive infrastructure as code.