What should a solutions architect recommend to meet these requirements?
Use AWS Systems Manager to replicate and provision the prototype infrastructure in two Availability Zones.
Define the infrastructure as a template by using the prototype infrastructure as a guide. Deploy the infrastructure with AWS CloudFormation.
Use AWS Config to record the inventory of resources that are used in the prototype infrastructure. Use AWS Config to deploy the prototype infrastructure into two Availability Zones.
Use AWS Elastic Beanstalk and configure it to use an automated reference to the prototype infrastructure to automatically deploy new environments in two Availability Zones.
Explanations:
AWS Systems Manager is primarily used for operational tasks and management of resources rather than for provisioning infrastructure. It does not provide a direct way to replicate infrastructure configurations like Auto Scaling groups or load balancers across Availability Zones.
AWS CloudFormation allows users to define infrastructure as code. By creating a template based on the prototype infrastructure, it enables automated and repeatable deployments in multiple Availability Zones, which meets the company’s requirements for development and production use.
AWS Config is used for tracking configuration changes and compliance of AWS resources but is not a provisioning tool. It cannot deploy infrastructure; rather, it helps in monitoring and managing existing resources.
AWS Elastic Beanstalk is a platform-as-a-service that automates the deployment of applications but is not designed for provisioning the underlying infrastructure components (like Auto Scaling groups and Application Load Balancers) in a specific manner as needed by the company.