A customer wants to set up a Scale-Out Backup Repository. Due to malware concerns, immutability is recommended. An on-premises server can be used to hold primary backups, but it can only hold about 21 days of backups. A copy of the backups should be stored in AWS. The retention for all backups is 60 days.
Which configuration of a Scale-out Backup repository meets these requirements?
The Scale-Out Backup Repository configuration must accommodate both the primary on-premises retention period of 21 days and the overall retention period of 60 days, along with immutability due to malware concerns. The 'Copy and move mode' allows for backups to initially be copied to the performance tier and, after a certain period, moved to the capacity tier to free up space on the performance tier. Using a Linux Hardened Repository with XFS for the performance tier provides better security against malware, while setting the immutability for 11 days ensures the backups on the on-premises server cannot be tampered with in that period. The capacity tier using Amazon S3 with immutability set to 60 days ensures the backups are kept securely for the required retention period. This configuration will meet the requirements of holding primary backups on-premises for about 21 days and storing a copy in AWS for a total retention of 60 days.
move needed
Its c, move option is not necessary
Are you sure? As C doesn't say anything about the data to be aged out. And the retention is 60 days as per the question but the primary repo (Linux Hardened Rep) can only hold 21 days of backup.
As the scenario requires copy of the backup to be in AWS