Q7 — AWS SAA-C03 Ch.14

Question 7 of 100 | ← Chapter 14

Q1007. A company runs thousands of AWS Lambda functions. The company needs a solution to securely store sensitive information that all the Lambda functions use. The solution must also manage the automatic rotation of the sensitive information.Which combination of steps will meet these requirements with the LEAST operational overhead? (Choose two.)

• A. Create HTTP security headers by using Lambda@Edge to retrieve and create sensitive information
• B. Create a Lambda layer that retrieves sensitive information
• C. Store sensitive information in AWS Secrets Manager ✓
• D. Store sensitive information in AWS Systems Manager Parameter Store ✓
• E. Create a Lambda consumer with dedicated throughput to retrieve sensitive information and create environmental variables

Correct Answer: C. Store sensitive information in AWS Secrets Manager, D. Store sensitive information in AWS Systems Manager Parameter Store

Explanation

BC OR CD.To securely store sensitive information used by AWS Lambda functions and manage the automatic rotation of that information with the least operational overhead, the best combination of steps is:C. Store sensitive information in AWS Secrets Manager.D. Store sensitive information in AWS Systems Manager Parameter Store.Explanation of Each Step:C. Store sensitive information in AWS Secrets Manager: This service is specifically designed for securely storing and managing sensitive information, such as API keys and passwords. It also includes features for automatic rotation of secrets, which reduces operational overhead and enhances security.D. Store sensitive information in AWS Systems Manager Parameter Store: This is another option for storing configuration data and secrets. It can also manage parameter values securely and supports encryption. Although it does not have the same built-in rotation features as Secrets Manager, it is still a viable option for storing sensitive information.Evaluation of Other Options:A. Create HTTP security headers using Lambda@Edge: This is unrelated to securely storing sensitive information and does not address the requirements.B. Create a Lambda layer that retrieves sensitive information: While this could be part of a solution, it does not inherently provide secure storage or automatic rotation. It adds complexity and operational overhead without directly addressing the core requirements.E. Create a Lambda consumer with dedicated throughput...: This approach is unnecessary and does not provide a straightforward way to securely store or rotate sensitive information.In summary, Options C and D effectively meet the requirements for securely storing and managing sensitive information with minimal operational overhead. However, using AWS Secrets Manager (Option C) is the preferred choice due to its built-in rotation capabilities.