Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

VEEAM VMCE_v12 Exam - Topic 16 Question 40 Discussion

An engineer is using Veeam Backup and Replication v12.The only backup repository is a Microsoft Windows server with direct attached Fibre Channel storage array.The engineer realizes that none of their backups are immutable. A second copy of the backup on a different site and a different media is required.Which option should be used to provide immutable backups on a secondary site with a different media?
B) Create a Scale Out Backup Repository with the existing Microsoft Windows Server as the performance tier and AWS S3 bucket with immutability enabled as the capacity tier.
A) Create a Scale Out Backup Repository with the existing Microsoft Windows Server as the performance tier and an HPe StoreOnce Catalyst share with immutability enabled as the capacity tier.
C) Create a new hardened repository on a new Microsoft Windows Server, mark it as immutable and create a backup copy job on it.
D) Create a Scale Out Backup Repository with the existing Microsoft Windows Server as the performance tier and Google Cloud Object Storage with immutability enabled as the capacity tier.

VEEAM VMCE_v12 Exam - Topic 16 Question 40 Discussion

Actual exam question for VEEAM's VMCE_v12 exam
Question #: 40
Topic #: 16
[All VMCE_v12 Questions]

An engineer is using Veeam Backup and Replication v12.

The only backup repository is a Microsoft Windows server with direct attached Fibre Channel storage array.

The engineer realizes that none of their backups are immutable. A second copy of the backup on a different site and a different media is required.

Which option should be used to provide immutable backups on a secondary site with a different media?

Show Suggested Answer Hide Answer
Suggested Answer: B

To provide immutable backups on a secondary site with a different media, the best option given the context is B: Create a Scale Out Backup Repository (SOBR) with the existing Microsoft Windows Server as the performance tier and an AWS S3 bucket with immutability enabled as the capacity tier.

This approach involves leveraging the existing backup infrastructure (Microsoft Windows Server with direct-attached storage) as the performance tier of the SOBR, where the most recent backups are stored for fast access. For long-term storage and immutability, backups can be offloaded to an AWS S3 bucket configured with Object Lock. The Object Lock feature in AWS S3 provides an additional layer of data protection by making the backup data immutable, meaning it cannot be deleted or modified for a specified duration. This setup ensures that backup data is protected against accidental deletion, ransomware, and other malicious activities.

By implementing this configuration, the engineer can achieve the desired level of data protection and immutability, utilizing cloud storage as a secure and scalable secondary backup location, distinct from the primary on-premises storage media.


Contribute your Thoughts:

0/2000 characters
Jolene
5 months ago
Wait, can you really make AWS S3 immutable? That’s new to me!
upvoted 0 times
...
Jani
6 months ago
I think D is a great choice too, Google Cloud is reliable.
upvoted 0 times
...
Vanna
6 months ago
C seems a bit outdated, why not use cloud storage?
upvoted 0 times
...
Sharee
6 months ago
A is interesting, but HPe StoreOnce might be overkill for some setups.
upvoted 0 times
...
Sage
6 months ago
Option B sounds solid with AWS S3!
upvoted 0 times
...
Moira
7 months ago
Option D with Google Cloud Object Storage seems like a solid choice too, but I can't recall if it was specifically mentioned in our study materials about immutability features.
upvoted 0 times
...
Wilburn
7 months ago
I'm leaning towards option C because creating a new hardened repository seems like a straightforward way to ensure immutability, but I’m not confident if it meets the secondary site requirement.
upvoted 0 times
...
Madonna
7 months ago
I remember practicing a similar question where we discussed Scale Out Backup Repositories. I feel like option A might be the right choice since it mentions HPe StoreOnce, which is known for immutability.
upvoted 0 times
...
Shawna
7 months ago
I think option B with the AWS S3 bucket sounds familiar, but I'm not entirely sure if it guarantees immutability like the question asks.
upvoted 0 times
...
Catherin
7 months ago
I'm not too familiar with Veeam, but based on the question, it seems like option B with AWS S3 might be a good choice to provide the required immutable backups.
upvoted 0 times
...
Denise
8 months ago
Okay, I think I've got this. The key is to set up a secondary backup repository with immutable storage, so option C looks like the way to go.
upvoted 0 times
...
Rebbecca
8 months ago
Hmm, I'm a bit confused by the different storage options mentioned. I'll need to review the Veeam documentation to make sure I understand the differences between them.
upvoted 0 times
...
Dominga
8 months ago
This looks like a tricky one. I'll need to carefully consider the options and think through the implications of each.
upvoted 0 times
...
Felicidad
10 months ago
I prefer option D, Google Cloud Object Storage is cost-effective.
upvoted 0 times
...
Noe
10 months ago
I'm leaning towards option B, AWS S3 is reliable.
upvoted 0 times
...
Vashti
10 months ago
Ah, the age-old backup dilemma. Gotta love those immutable backups!
upvoted 0 times
...
Carol
10 months ago
Hmm, Option D with Google Cloud Object Storage could work too, but I'd be more comfortable with a known provider like AWS.
upvoted 0 times
Estrella
10 months ago
Yeah, AWS S3 bucket with immutability enabled would be a reliable choice for the backup repository.
upvoted 0 times
...
Pauline
10 months ago
I agree, having a secondary site with a different media for immutable backups is crucial.
upvoted 0 times
...
Janessa
10 months ago
Option A sounds like a good solution, using HPe StoreOnce Catalyst share with immutability enabled.
upvoted 0 times
...
...
Theron
10 months ago
I'd go with Option C. Creating a new hardened repository and marking it as immutable is a straightforward approach.
upvoted 0 times
...
Wilson
10 months ago
Option B looks like the way to go. Using AWS S3 with immutability seems like a solid secondary site solution.
upvoted 0 times
Elfrieda
10 months ago
I agree, AWS S3 is a reliable option for immutable backups on a secondary site.
upvoted 0 times
...
Owen
10 months ago
Option B looks like the way to go. Using AWS S3 with immutability seems like a solid secondary site solution.
upvoted 0 times
...
...
Julieta
11 months ago
I disagree, I believe option C is more secure.
upvoted 0 times
...
Annabelle
11 months ago
I think option A is the best choice.
upvoted 0 times
...

Save Cancel