A company runs thousands of AWS Lambda functions and needs a secure way to store sensitive information that all functions use, with automatic rotation and minimal operational overhead. Which combination of steps meets these requirements with the LEAST operational overhead? (Choose two.)

Storing sensitive information in AWS Secrets Manager is the most secure and operationally efficient way to handle secrets. Secrets Manager offers automatic rotation, fine-grained access control, and integration with other AWS services. A Lambda layer that retrieves this information from Secrets Manager allows multiple Lambda functions to share the same code for secret retrieval without duplicating it in each function, reducing operational overhead and promoting code reuse. Storing sensitive information in AWS Systems Manager Parameter Store is a viable option for non-sensitive data or configuration, but Secrets Manager is specifically designed for sensitive information with features like automatic rotation. Creating HTTP security headers with Lambda@Edge is not suitable for storing sensitive information. A Lambda consumer with dedicated throughput is not a standard or efficient pattern for secret management.