Exam AWS Certified Solutions Architect - Associate SAA-C03 topic 1 question 157 discussion

I tend to agree D and E... A - Manual task that can be automated, so why make life difficult? B - The maximum retention period is 35 days, so would not help C - The maximum retention period is 35 days, so would not help D - Only option that deals with logs, so makes sense E - Partially manual but only option that achieves the 5 year goal

dude trust me

A. Take a manual snapshot of the DB cluster. E. Use AWS Backup to take the backups and to keep the backups for 5 years. Explanation: To meet retention and deletion requirements (5 years) and permanent audit log storage, here’s what each selected option provides: ✅ A. Take a manual snapshot of the DB cluster Manual snapshots do not expire automatically, unlike automated backups. They can be retained as long as needed (e.g., up to 5 years) and deleted manually or via automation after that period.

Ans D, E

D + E I think. D deals with the logs. AWS Backup for backups.... Why make backups more difficult by not using the built in backup tool?

I'd say "A" over "E" because in the option "E", it says use AWS Backup to take the "backups" not snapshot. "If you use AWS CLI, this is set using the parameter DeleteAfterDays. The retention period for snapshots can range between 1 day and 100 years (or indefinitely if you don't enter one), while the retention period for continuous backups can range from 1 day to 35 days. The creation date of a backup is the date the backup job started, not the date it completed. If your backup job doesn't complete on the same date it started, use the date on which it began to help calculate retention periods." From here: https://docs.aws.amazon.com/aws-backup/latest/devguide/creating-a-backup-plan.html

Agree with the reasoning of JayBee

C - C - https://www.bing.com/ck/a?!&&p=7e852c106834b9bdJmltdHM9MTcxMzM5ODQwMCZpZ3VpZD0xNzJiMThiOS1kM2RiLTZlZGEtMWNhZC0wYjRlZDJiZDZmZDYmaW5zaWQ9NTQ0OQ&ptn=3&ver=2&hsh=3&fclid=172b18b9-d3db-6eda-1cad-0b4ed2bd6fd6&psq=does+Aurora+offer+auto+backup&u=a1aHR0cHM6Ly9kb2NzLmF3cy5hbWF6b24uY29tL0FtYXpvblJEUy9sYXRlc3QvQXVyb3JhVXNlckd1aWRlL0F1cm9yYS5NYW5hZ2luZy5CYWNrdXBzLmh0bWwjOn46dGV4dD1BdXJvcmElMjBiYWNrcyUyMHVwJTIweW91ciUyMGNsdXN0ZXIlMjB2b2x1bWUlMjBhdXRvbWF0aWNhbGx5JTIwYW5kLHRvJTIwYW55JTIwcG9pbnQlMjB3aXRoaW4lMjB0aGUlMjBiYWNrdXAlMjByZXRlbnRpb24lMjBwZXJpb2Qu&ntb=1 D - Only answer for audit logs of activities on database

My thoughts: 1. AWS backups is designed to make back ups 2. "configure backup retention for 5 years" with what? a script? maybe AWS backups???? are the back ups done with DD and stored in S3? i cannot trust this answer 3. "Take a manual snapshot of the DB cluster" this is not an amazon best practice they want us to use their tools AWS backups 4. "create a life cycle policy" assuming the back ups are stored in S3 (which is not a best practice) cannot trust this that leaves D and E

D AND E- makes more sense as we automate backups in Aurora DB - Export data to CloudWatch to capture all log events and configure CloudWatch to retain logs indefinitely.

D and E. A would work as well, but D is the better option as its automated. E is the only option that gets you to the 5 year retention.

D AND E- makes more sense as we automate backups in Aurora DB - Export data to CloudWatch to capture all log events and configure CloudWatch to retain logs indefinitely.

DE makes more sense

The reasons are: Configuring the automated backups for the Aurora PostgreSQL DB cluster to retain backups for 5 years will meet the requirement to store all data for that duration. Exporting the database logs to CloudWatch Logs will capture the audit logs of actions performed in the database. CloudWatch Logs retention can be configured to store logs indefinitely. This meets the need to keep audit logs available beyond the 5 year data retention period. Additional manual snapshots or using AWS Backup for backups is not necessary since automated backups are already enabled. A lifecycle policy is useful for transitioning storage classes but does not apply here for a set 5 year retention.

Automated backup is limited 35 days

Previously, you had to create custom scripts to automate backup scheduling, enforce retention policies, or consolidate backup activity for manual Aurora cluster snapshots, especially when coordinating backups across AWS services. With AWS Backup, you gain a fully managed, policy-based backup solution with snapshot scheduling and snapshot retention management. You can now create, manage, and restore Aurora backups directly from the AWS Backup console for both PostgreSQL-compatible and MySQL-compatible versions of Aurora. To get started, select an Amazon Aurora cluster from the AWS Backup console and take an on-demand backup or simply assign the cluster to a backup plan.

A is not a valid option for meeting the requirements. A manual snapshot of the DB cluster is a point-in-time copy of the data in the cluster. While taking manual snapshots can be useful for creating backups of the data, it is not a reliable or efficient way to meet the requirement of storing all the data for 5 years and deleting it after 5 years. It would be difficult to ensure that manual snapshots are taken regularly and retained for the required period of time. It is recommended to use a fully managed backup service like AWS Backup, which can automate and centralize the process of taking and retaining backups.