問題文
After a secret rotation, some application instances start failing authentication while others continue to work. What is the mechanism, and what would have prevented it?
選択肢
- The rotation created a secret under a new name, so only the instances whose configuration already pointed at the new name can authenticate
- Instances that still hold the old cached value fail, and an overlap period during which the target accepts both values would have prevented it
- Purge protection removed the old value as soon as the new version was created, so the instances that still reference the old one can no longer authenticate
- The vault throttled the reads that all instances issued at once after the rotation, so the instances whose requests were rejected are the ones that fail