A web-startup runs its very successful social news application on Amazon EC2 with an Elastic
Load Balancer, an Auto-Scaling group of Java/Tomcat application-servers, and DynamoDB as
data store. The main web-application best runs on m2.xlarge instances since it is highly memorybound. Each new deployment requires semi-automated creation and testing of a new AMI for the
application servers, which takes quite a while and is therefore only done once per week.
Recently, a new chat feature has been implemented in node.js and waits to be integrated in the
architecture. First tests show that the new component is CPU bound.
Because the company has some experience with using Chef, they decided to streamline the
deployment process and use AWS OpsWorks as an application life cycle tool to simplify
management of the application and reduce the deployment cycles.
What configuration in AWS OpsWorks is necessary to integrate the new chat module in the most
cost-efficient and flexible way?

A.
Create one AWS OpsWorks stack, create one AWS OpsWorks layer, create one custom recipe

B.
Create two AWS OpsWorks stacks, create two AWS OpsWorks layers, create one custom recipe

C.
Create one AWS OpsWorks stack, create two AWS OpsWorks layers, create one custom recipe

D.
Create two AWS OpsWorks stacks, create two AWS OpsWorks layers, create two custom recipes