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 a data store. The main web application best runs on m2 x large instances since it is highly memory-bound. Each new deployment requires the 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 into the architecture. The first tests show that the new component is CPU bound. Since the company has some experience with using Chef, they decided to streamline the deployment process and use AWS OpsWorks as an application lifecycle tool to simplify the application`s management and reduce the deployment cycles. What configuration in AWS OpsWorks is required to manage the application integrated with the new chat module in the most cost-efficient and flexible way?

Answer options:

A.Create one AWS OpsWorks stack, create one AWS OpsWorks layer, and create one custom recipe.
B.Create one AWS OpsWorks stack, create two AWS OpsWorks layers, and create one custom recipe.
C.Create two AWS OpsWorks stacks, create two AWS OpsWorks layers, and create one custom recipe.
D.Create two AWS OpsWorks stacks, create two AWS OpsWorks layers, and create two custom recipes.

Answer - B
The scenario here requires that you need to manage the application that is created with java, node.js, and DynamoDB using AWS OpsWorks. The deployment process should be streamlined, and the deployment cycles should be reduced.
As the java and node.js have different resource requirements, it makes sense to deploy them on different layers. It would make maintenance easier as well.
Option A is incorrect because it would be a better solution to create two separate layers: one for Java and one for node.js.
Option B is CORRECT because only one stack would be sufficient, and two layers (one for Java and one for node.js) would be required for handling separate requirements. One custom recipe for DynamoDB would be required.
Option C is incorrect because two OpsWork stacks are unnecessary.
Option D is incorrect because two OpsWork stacks are unnecessary.
More information on AWS OpsWork Stack
An AWS OpsWorks Stack defines your entire application`s configuration: the load balancers, server software, database, etc. You control every part of the stack by building layers that define the software packages deployed to your instances and other configuration details such as Elastic IPs and security groups. You can also deploy your software onto layers by identifying the repository and optionally using Chef Recipes to automate everything Chef can do, such as creating directories and users, configuring databases, etc. You can use OpsWorks Stacks’ built-in automation to scale your application and automatically recover from instance failures. You can control who can view and manage the resources used by your application, including ssh access to the instances that your application uses.
For more information on Ops work, please visit the below URL-
https://aws.amazon.com/opsworks/stacks/faqs/