VMCE_V12 · Question #170
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 21…
The correct answer is D. Copy mode. The optimal design is to leave your on-prem repo immutable (to guard against local malware) and simply copy every backup to AWS where it's locked for 60 days. That way your performance tier keeps just the 21 days you need, and your capacity tier holds the full 60-day chain…
Question
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 21 days of backups. A copy of all backups should be stored in Amazon Web Services. The retention for all backups is 60 days. Which configuration of a Scale-out Backup Repository meets these requirements?
Options
- ACopy mode
- BCopy and move mode
- CCopy and move mode
- DCopy mode
How the community answered
(21 responses)- A5% (1)
- B5% (1)
- C19% (4)
- D71% (15)
Explanation
The optimal design is to leave your on-prem repo immutable (to guard against local malware) and simply copy every backup to AWS where it's locked for 60 days. That way your performance tier keeps just the 21 days you need, and your capacity tier holds the full 60-day chain immutably. Performance Tier: hardened repository on Linux (XFS) with immutability enabled (to protect the first 21 days of backups). Capacity Tier: Amazon S3 with object-lock immutability set for 60 days (to archive the entire 60-
Topics
Community Discussion
No community discussion yet for this question.