DVA-C02 · Question #660
A company uses AWS Secrets Manager to store API keys for external REST services. The company uses an AWS Lambda function to rotate the API keys on a regular schedule. Because of an error in the…
The correct answer is C. Roll back to the last working version of the API keys in Secrets Manager. Rolling back the secret’s staging labels so that the last known-good version is labeled AWSCURRENT immediately restores the previously working API key for your clients. This requires no changes to external systems or additional key-generation logic, minimizing operational…
Question
A company uses AWS Secrets Manager to store API keys for external REST services. The company uses an AWS Lambda function to rotate the API keys on a regular schedule. Because of an error in the Lambda function, the API keys are updated in Secrets Manager but not in the external REST services. Before investigating the root cause, the company wants to resume requests bound for the external REST services. Which solution will meet this requirement with the LEAST operational overhead?
Options
- AManually create a new version of the API keys in Secrets Manager. Update the keys in the REST
- BManually read the new version of the API Keys from Secrets Manager. Update the keys in the
- CRoll back to the last working version of the API keys in Secrets Manager.
- DFix and reinvoke the Lambda function to generate a new version of the API keys in Secrets
How the community answered
(29 responses)- A3% (1)
- B10% (3)
- C79% (23)
- D7% (2)
Explanation
Rolling back the secret’s staging labels so that the last known-good version is labeled AWSCURRENT immediately restores the previously working API key for your clients. This requires no changes to external systems or additional key-generation logic, minimizing operational overhead.
Community Discussion
No community discussion yet for this question.