<strong>OpsWorks is being used by a developer to setup a short term project. Basically, this project is about an independent component that needs to talk with other domains that are owned by other teams. One of them is a RDS MySQL database that records some important information such as user states. This database is owned and maintained by the operation team. </strong>

Answer options:

A.Associate the Amazon RDS database server when the developer create the app or later by editing the app. When the app is deployed, AWS OpsWorks Stacks creates a file on each of the built-in application server instances containing the connection data.
Then a custom recipe can be used to extract the connection information from the deploy attributes and put it in a file that can be read by the application.
B.The developer can only associate the Amazon RDS database server with an app when the app is created otherwise he has to rebuild the whole stack.
When the app is deployed, AWS OpsWorks Stacks creates a file on each of the built-in application server instances containing the connection data. The application can read the deploy attributes and use them to connect to the database server.
C.The developer can edit the app if he does not associate the database when creating the app. Under the lifecycle of Configure, AWS OpsWorks Stacks creates a file on each of the built-in application server instances containing the connection data.
Then a recipe can be used to extract the connection information from the configure attributes and put it in a file that can be read by the application.
D.The developer can only associate the Amazon RDS database server with an app when the app is created otherwise he has to rebuild the whole stack.
After the RDS is associated, EC2 instances are able to connect with MySQL database automatically as long as proper roles have been attached to the application stack.

Correct Answer-A
First, You can associate an Amazon RDS database server with an app when you create the app or later by editing the app.
Secondly, When you deploy an app, for Linux stacks, AWS OpsWorks Stacks creates a file on each of the built-in application server instances containing the connection data.
An application can use the connection information from the instance`s deploy attributes to connect to a database. However, applications cannot access that information directly—only recipes can access the deploy attributes. You can address this issue by implementing a custom recipe that extracts the connection information from the deploy attributes and puts it in a file that can be read by the application. Details please refer to
https://docs.aws.amazon.com/opsworks/latest/userguide/workingapps-connectdb.html.
Option? ?B ?is? ?incorrect:? Because you can associate the database by editing the app after the app is created.
Option? C is? ?incorrect:? ?Because it is not the lifecycle of Configure. When the app is deployed, the connection data is recorded under the file with deploy attributes.
Option? D is? ?incorrect:? ?Because application still needs to get the credentials to connect to the MySQL database. It won’t connect without knowing the login details.