AWS Certified Security - Specialty free question 2 / 10 · Domain 1: Detection
You want to keep GuardDuty findings for one year. Which combination of how long GuardDuty stores findings and how to keep them longer is correct?
- Stored for 30 days; send them to a destination of your choice through EventBridge or export them to S3 to keep them longer
- Stored for 30 days; collecting them in the delegated administrator account extends that to 90 days
- Stored for 90 days; once you archive a finding, it is then kept with no expiration
- Stored for 90 days; send them to a destination of your choice through EventBridge or export them to S3 to keep them longer
Show the answer and explanation
Answer: D
Why this is correct
GuardDuty stores findings for 90 days. With EventBridge, besides automated monitoring and processing, you can send finding data to a destination of your choice and keep it as long as you like. To keep findings longer, GuardDuty also supports exporting the findings it generates to Amazon S3.
Why the other options are wrong
"Stored for 30 days; send them to a destination of your choice through EventBridge or export them to S3 to keep them longer" … The page says GuardDuty stores findings for 90 days, not 30. The second half is right: EventBridge delivery and an export to S3 are the ways it gives to keep findings longer.
"Stored for 30 days; collecting them in the delegated administrator account extends that to 90 days" … The page says GuardDuty stores findings for 90 days, not 30. To retain findings longer, it gives sending them to your preferred storage platform through EventBridge and exporting them to Amazon S3.
"Stored for 90 days; once you archive a finding, it is then kept with no expiration" … The 90 days is right, but the ways the page gives to keep findings longer are sending them to your preferred storage platform through EventBridge and exporting them to Amazon S3.
Key point
If an audit requires retention beyond 90 days, set up the S3 export or the EventBridge delivery from the start. Each finding has its own unique finding ID.