A developer needs to store configuration variables for an application. The developer needs to set an expiration date and time for the configuration. The developer wants to receive notifications before the configuration expires.
Which solution will meet these requirements with the LEAST operational overhead?
To store configuration variables with an expiration date and receive notifications before expiration with the least operational overhead, the best solution is to create an advanced parameter in AWS Systems Manager Parameter Store and set Expiration and ExpirationNotification policy types. Advanced parameters support the required policies for expiration and notifications, which standard parameters do not. This approach minimizes operational overhead by fully utilizing built-in AWS capabilities without the need for additional components like Lambda functions or EC2 instances.
C is correct. You have to use "advanced parameter in AWS Systems Manager Parameter Store" to be able to Set Expiration and ExpirationNotification policy types.
it leverages the advanced parameter tier and the parameter policies feature of Parameter Store, which meet the requirements with the least operational overhead.
You can't set expiration policy on standard parameter
By creating a standard parameter, you can set an expiration date for the parameter
A is the right Answer
Using Lambda function and SNS will address the requirement with least operational overhead.
Changing my mind option A is correct here.
It is C. standard tier does not have those features
Advanced Parameters: These offer more capabilities, such as adding policies for expiration and triggering notifications
A is sufficient. C is abundant
https://docs.aws.amazon.com/systems-manager/latest/userguide/parameter-store-policies.html
C is the correct answer.
https://docs.aws.amazon.com/systems-manager/latest/userguide/parameter-store-policies.html