An agile team just starts using AWS, and the team leader wants them to move the legacy Java-based software to the AWS platform in 2 weeks. The requirement is that the new environment must be highly available, and the infrastructure is managed as code and version controlled. Besides, the team has good experiences of Chef, so they want to use that knowledge during the migration. Which actions should the team perform to meet the needs? Select 2.

Answer options:

A.Use several CloudFormation templates to build up infrastructure such as VPC, NAT Gateway, Bastion, and Route53. Version control it using CodeCommit.
B.As CloudFormation does not support the OpsWorks service, use Chef in EC2 to build up the web services. Existing cookbooks can be used. Add an auto-scaling group with a proper auto-scaling configuration to ensure high availability.
C.AWS infrastructure such as VPC, NAT Gateway, Bastion host, Security Groups, and EC2 instances are created using CloudFormation templates. Version control it using GitHub.
D.Use a nested CloudFormation template to create an OpsWorks stack. The resource type is “AWS::OpsWorks::Stack”. Add a Java layer in the stack. Make sure that the Scaling configuration is turned on.
E.Use OpsWorks to build up the Java web services. Existing cookbooks can be used. However, OpsWorks cannot be put into the CloudFormation template as CloudFormation does not support it.

Correct Answer – A, D
 
Options A, D are Correct:
Firstly, OpsWorks is a supported service in CloudFormation according to https://aws.amazon.com/about-aws/whats-new/2014/03/03/aws-cloudformation-supports-aws-opsworks/. The AWS OpsWorks Resource Types in CloudFormation includes:
AWS::OpsWorks::App
AWS::OpsWorks::ElasticLoadBalancerAttachment
AWS::OpsWorks::Instance
AWS::OpsWorks::Layer
AWS::OpsWorks::Stack
AWS::OpsWorks::UserProfile
AWS::OpsWorks::Volume
Secondly, EC2 application instances should be managed inside OpsWorks, and they do not belong to infrastructure preparations.
Option A is more accurate than Option
C.Option A is CORRECT: Because infrastructure should be done via CloudFormation, and it can be easily version controlled. Either CodeCommit or GitHub is ok.
Option B is incorrect: Because CloudFormation supports OpsWorks service. A nested template could be utilized to maintain OpsWorks related resources.
Option C is incorrect: Because infrastructure refers to the resources which do not change frequently, such as VPC subnets and Bastion hosts. EC2 instances are application related and should be maintained within OpsWorks stacks.
Option D is CORRECT: Because the team can use the Chef experiences in OpsWorks to build up the application. Together with
Option A, a highly available environment can be built.
Option E is incorrect: Because the OpsWorks service is supported in CloudFormation. It makes more sense to create an OpsWorks stack as a CloudFormation resource.