When talking to someone who works for the customer, they mention they are working on a different project with a major cloud provider that does not currently support immutability. Which of the…

Question

Options

• ABackup copy to a hardened repository at a different site.
• BSet up Scale-out Backup Repository capacity tier to a different cloud provider than the archive tier.
• CBackup copy to a Windows repository in the cloud that is scheduled to turn off outside the backup
• DSet up capacity tier to local on-premises object storage that supports immutability.

• A
  3% (1)
• B
  83% (30)
• C
  6% (2)
• D
  8% (3)

Explanation

The best option to still satisfy the requirement for offsite, immutable or air gapped backups if the cloud provider selected for archive storage does not support immutability is to set up Scale-out Backup Repository capacity tier to a different cloud provider than the archive tier. Scale-out Backup Repository is a logical entity that groups several backup repositories into a single pool of storage, and allows to move backup files between performance and capacity tiers. The capacity tier can be configured to use Amazon S3 or Microsoft Azure Blob Storage, which support Object Lock feature for immutability. By using a different cloud provider for the capacity tier than the archive tier, the backup data can be stored in two separate locations, with one copy being immutable or air gapped.

No community discussion yet for this question.