What steps should the developer take to access the RDS DB instance from the code?
(Choose two.)
Modify the endpoint name using either the AWS Management Console or AWS CLI.
Upload the driver to Amazon S3 and reference it in the code.
Download the appropriate database driver and include it with the application.
Construct a connection string using the Elastic Beanstalk environment variables.
Create a CNAME record referencing database instances ALIAS.
Explanations:
Modifying the endpoint name is not necessary to access the RDS instance. The endpoint provided by RDS remains constant and is used to connect to the database. This step does not directly relate to accessing the database from the application code.
Uploading the driver to Amazon S3 is not a standard practice for accessing a database. The appropriate database driver should be included in the application package or managed via dependency management, not stored in S3.
Downloading the appropriate database driver and including it with the application is essential to establish a connection to the RDS DB instance. The driver facilitates communication between the application and the database.
Constructing a connection string using the Elastic Beanstalk environment variables is a best practice for accessing the RDS DB instance. This allows the application to use environment-specific settings (such as the database endpoint, username, and password) without hardcoding them in the application code.
Creating a CNAME record is not necessary for accessing the RDS DB instance. The application can connect directly using the RDS endpoint provided by AWS, and CNAME records are typically used for routing traffic, not for database connections.