AWS Certified Solutions Architect - Associate
Get started today
Ultimate access to all questions.
Deep dive into the quiz with AI chat providers.
We prepare a focused prompt with your quiz and certificate details so each AI can offer a more tailored, in-depth explanation.
A company is making a prototype of the infrastructure for its new website by manually provisioning the necessary infrastructure. This infrastructure includes an Auto Scaling group, an Application Load Balancer and an Amazon RDS database. After the configuration has been thoroughly validated, the company wants the capability to immediately deploy the infrastructure for development and production use in two Availability Zones in an automated fashion.
What should a solutions architect recommend to meet these requirements?
Other
Community
UAnonymous
A
Use AWS Systems Manager to replicate and provision the prototype infrastructure in two Availability Zones
B
Define the infrastructure as a template by using the prototype infrastructure as a guide. Deploy the infrastructure with AWS CloudFormation.
C
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.
D
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.
Explanation:
Explanation
Correct Answer: B - Define the infrastructure as a template by using the prototype infrastructure as a guide. Deploy the infrastructure with AWS CloudFormation.
Why this is correct:
-
Infrastructure as Code (IaC): AWS CloudFormation is AWS's native Infrastructure as Code service that allows you to define your infrastructure in JSON or YAML templates.
-
Automated Deployment: Once the infrastructure is defined as a CloudFormation template, it can be deployed repeatedly, consistently, and automatically to any AWS region or Availability Zone.
-
Multi-AZ Deployment: CloudFormation templates can be configured to deploy resources across multiple Availability Zones, which meets the requirement for deploying in two Availability Zones.
-
Environment Consistency: The same template can be used for both development and production environments, ensuring consistency between them.
-
Prototype to Production: The manually provisioned prototype infrastructure can serve as a guide to create the CloudFormation template, capturing all the necessary components (Auto Scaling group, ALB, RDS database).
Why other options are incorrect:
A. AWS Systems Manager: While Systems Manager has automation capabilities, it's primarily for managing and automating operational tasks on existing resources, not for infrastructure provisioning across multiple AZs. It's not designed for full infrastructure deployment like CloudFormation.
C. AWS Config: AWS Config is a service for assessing, auditing, and evaluating configurations of AWS resources. It's for compliance and governance, not for infrastructure deployment. It can record inventory but cannot deploy infrastructure.
D. AWS Elastic Beanstalk: Elastic Beanstalk is a Platform as a Service (PaaS) that simplifies application deployment but has limitations for complex infrastructure. While it can deploy across multiple AZs, it's not ideal for capturing and replicating a specific prototype infrastructure that includes Auto Scaling groups, ALB, and RDS in an automated, template-based way.
Key Benefits of CloudFormation for this scenario:
- Repeatability: Deploy the same infrastructure multiple times
- Consistency: Ensure development and production environments are identical
- Version Control: Templates can be stored in version control systems
- Rollback Capability: If deployment fails, CloudFormation can roll back changes
- Parameterization: Use parameters to customize deployments for different environments
This approach aligns with AWS best practices for infrastructure deployment and management.
Comments
Loading comments...