Free AWS MLA-C01 Actual Exam Questions - Question 5 Discussion
company needs to implement a solution to automatically rotate the API tokens every 3 months.
Which solution will meet this requirement?
A, because Secrets Manager handles rotation natively, unlike KMS options here.
A imo, because Secrets Manager is built for secret rotation with built-in Lambda support, making it easier to automate token updates safely every 3 months. Parameter Store isn’t as specialized for rotation.
Secrets Manager (A) is designed for automatic rotation, unlike Parameter Store.
Maybe B makes sense too since Parameter Store can handle secure strings and you can trigger Lambda for rotation. Secrets Manager is more specialized, but Parameter Store might still work if you script the rotation logic.
Option A feels right since Secrets Manager is designed for managing and rotating credentials automatically. The Lambda just handles the token update process during rotation, which fits the requirement well.
A vs B? Secrets Manager has built-in rotation, Parameter Store doesn’t.
Secrets Manager is built for this exact use case with native rotation support, so A makes sense. Parameter Store (B) doesn't have automatic rotation features as far as I know.
B imo, Parameter Store can store tokens but lacks built-in rotation like Secrets Manager.
A, because Secrets Manager is designed specifically for secret storage and rotation, unlike the others.
It’s A because Secrets Manager supports built-in rotation, unlike Parameter Store or KMS.
Option A looks best. Secrets Manager is built for storing and rotating secrets like API tokens automatically using Lambda. Parameter Store doesn’t natively support rotation, and KMS is more for encryption keys, not API tokens.