Your mission is to create a lights-out datacenter environment, and you plan to use AWS OpsWorks to
accomplish this. First you created a stack and added an App Server layer with an instance running in it. Next
you added an application to the instance, and now you need to deploy a MySQL RDS database instance.
Which of the following answers accurately describe how to add a backend database server to an OpsWorks
stack? (Choose three.)
Add a new database layer and then add recipes to the deploy actions of the database and App Server
Use OpsWorks’ “Clone Stack” feature to create a second RDS stack in another Availability Zone for
redundancy in the event of a failure in the Primary AZ. To switch to the secondary RDS instance, set the
[:database] attributes to values that are appropriate for your server which you can do by using custom
The variables that characterize the RDS database connection—host, user, and so on—are set using the
corresponding values from the deploy JSON’s [:depioy][:app_name][:database] attributes.
Cookbook attributes are stored in a repository, so OpsWorks requires that the “password”:
“your_password” attribute for the RDS instance must be encrypted using at least a 256-bit key.
Set up the connection between the app server and the RDS layer by using a custom recipe. The recipe
configures the app server as required, typically by creating a configuration file. The recipe gets the
connection data such as the host and database name from a set of attributes in the stack configuration and
deployment JSON that AWS OpsWorks installs on every instance.