nerdexam
Amazon

SAA-C03 · Question #595

A company has a custom application with embedded credentials that retrieves information from a database in an Amazon RDS for MySQL DB cluster. The company needs to make the application more secure…

The correct answer is C. Store the credentials in AWS Secrets Manager. Configure the application to load the database. To secure an application's embedded database credentials with minimal programming effort, AWS Secrets Manager is the ideal service because it specializes in storing, rotating, and managing database credentials.

Submitted by dimitri_ru· Mar 4, 2026Design Secure Architectures

Question

A company has a custom application with embedded credentials that retrieves information from a database in an Amazon RDS for MySQL DB cluster. The company needs to make the application more secure with minimal programming effort. The company has created credentials on the RDS for MySQL database for the application user. Which solution will meet these requirements?

Options

  • AStore the credentials in AWS Key Management Service (AWS KMS). Create keys in AWS KMS.
  • BStore the credentials in encrypted local storage. Configure the application to load the database
  • CStore the credentials in AWS Secrets Manager. Configure the application to load the database
  • DStore the credentials in AWS Systems Manager Parameter Store. Configure the application to

How the community answered

(27 responses)
  • A
    7% (2)
  • B
    4% (1)
  • C
    89% (24)

Why each option

To secure an application's embedded database credentials with minimal programming effort, AWS Secrets Manager is the ideal service because it specializes in storing, rotating, and managing database credentials.

AStore the credentials in AWS Key Management Service (AWS KMS). Create keys in AWS KMS.

AWS Key Management Service (KMS) is used for creating and managing cryptographic keys to encrypt data. While Secrets Manager uses KMS for encryption, KMS itself is not the service for storing and managing the credentials directly.

BStore the credentials in encrypted local storage. Configure the application to load the database

Storing credentials in encrypted local storage, while an improvement over plaintext, still requires the company to manage encryption, decryption, and rotation manually, which contradicts the 'minimal programming effort' and 'more secure' requirements compared to a fully managed service.

CStore the credentials in AWS Secrets Manager. Configure the application to load the databaseCorrect

AWS Secrets Manager is specifically designed for storing and retrieving sensitive information like database credentials. It can automatically rotate credentials for Amazon RDS for MySQL databases, significantly enhancing security with minimal changes to the application logic, which simply needs to retrieve the secret from Secrets Manager instead of having it embedded.

DStore the credentials in AWS Systems Manager Parameter Store. Configure the application to

AWS Systems Manager Parameter Store can store secrets, but AWS Secrets Manager offers more advanced features specifically for database credentials, such as automatic rotation for RDS databases, which aligns better with the requirement for 'minimal programming effort' to achieve a 'more secure' solution.

Concept tested: Secure credential management and rotation for RDS

Source: https://docs.aws.amazon.com/secretsmanager/latest/userguide/reference_rds_supported_dbs.html

Community Discussion

No community discussion yet for this question.

Full SAA-C03 Practice