Q34 — AWS SAA-C03 Ch.14

Question 34 of 100 | ← Chapter 14

Q1034. A company is designing a new internal web application in the AWS Cloud. The new application must securely retrieve and store multiple employee usernames and passwords from an AWS managed service.Which solution will meet these requirements with the LEAST operational overhead?

• A. Store the employee credentials in AWS Systems Manager Parameter Store. Use AWS CloudFormation and the BatchGetSecretValue API to retrieve usernames and passwords from Parameter Store.
• B. Store the employee credentials in AWS Secrets Manager. Use AWS CloudFormation and AWS Batch with the BatchGetSecretValue API to retrieve the usernames and passwords from Secrets Manager.
• C. Store the employee credentials in AWS Systems Manager Parameter Store. Use AWS CloudFormation and AWS Batch with the BatchGetSecretValue API to retrieve the usernames and passwords from Parameter Store.
• D. Store the employee credentials in AWS Secrets Manager. Use AWS CloudFormation and the BatchGetSecretValue API to retrieve the usernames and passwords from Secrets Manager. ✓

Correct Answer: D. Store the employee credentials in AWS Secrets Manager. Use AWS CloudFormation and the BatchGetSecretValue API to retrieve the usernames and passwords from Secrets Manager.

Explanation

To securely retrieve and store multiple employee usernames and passwords from an AWS managed service with the least operational overhead, the best solution is:D. Store the employee credentials in AWS Secrets Manager. Use AWS CloudFormation and the BatchGetSecretValue API to retrieve the usernames and passwords from Secrets Manager.Explanation:\1. AWS Secrets Manager: - Secrets Manager is specifically designed for managing sensitive information such as usernames and passwords. It provides built-in functionality for secure storage, automatic rotation of credentials, and easy access management. This makes it ideal for storing employee credentials.\2. Operational Overhead: - Using Secrets Manager reduces operational overhead since it automates key aspects of secret management, such as encryption, access control, and rotation. This allows your team to focus on application development rather than secret management.\3. BatchGetSecretValue API: - This API provides a straightforward method for retrieving multiple secrets in a single call, making it efficient for applications that need to access multiple usernames and passwords.\4. Integration with AWS CloudFormation: - CloudFormation can be used to manage the deployment of your application and its integration with Secrets Manager, ensuring that the infrastructure is easily replicable and manageable.Evaluation of Other Options:A. Store the employee credentials in AWS Systems Manager Parameter Store: - While Parameter Store can store sensitive information, it does not have the same level of features for secret management as Secrets Manager, such as automatic rotation and native integration with IAM policies for secret access.B. Store the employee credentials in AWS Secrets Manager: - This option is valid but includes AWS Batch unnecessarily. AWS Batch is typically used for running batch jobs rather than for retrieving secrets, which adds unnecessary complexity.C. Store the employee credentials in AWS Systems Manager Parameter Store: - Similar to option A, this lacks the advanced features of Secrets Manager, such as automatic rotation and built-in security features specifically designed for managing sensitive data.Conclusion:Option D is the most efficient solution for securely managing employee usernames and passwords, providing a robust, low-maintenance approach to secret management while utilizing AWS managed services effectively.