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 Exam VMCE2021 Topic 3 Question 43 Discussion

Actual exam question for VEEAM's VMCE2021 exam
Question #: 43
Topic #: 3
[All VMCE2021 Questions]

A Veeam administrator has been tasked to create a backup that will automatically make a copy of data on a different media type, while also being off site, without creating additional backup or backup copy jobs. The administrator has determined that a Scale-out Backup Repository can be used as part of the solution. How can this be accomplished?

Show Suggested Answer Hide Answer
Suggested Answer: D

https://helpcenter.veeam.com/docs/backup/vsphere/capacity_tier_copy.html?ver=120


Contribute your Thoughts:

Angelyn
1 months ago
Wait, is this a Veeam exam? I heard their tests are harder than a Rubik's Cube dipped in superglue!
upvoted 0 times
Romana
14 days ago
C: Wait, I think it's option B. That sounds like it would meet the requirements.
upvoted 0 times
...
Chaya
15 days ago
B: B) Add an archive tier to the Scale-out Backup Repository and enable 'GFS Tiering'.
upvoted 0 times
...
Joaquin
1 months ago
A: A) Add a capacity tier to the Scale-out Backup Repository and enable the 'Move' option.
upvoted 0 times
...
...
Sherell
2 months ago
I think D) Add a capacity tier to the Scale-out Backup Repository and enable the 'Copy' option would also work, as it creates a copy of data on a different media type.
upvoted 0 times
...
German
2 months ago
Option A is tempting, but 'Move' might not be what we want - we need a true copy, not just moving the data around.
upvoted 0 times
...
Vernell
2 months ago
Hmm, Option D sounds good too. 'Copy' to a capacity tier could work, but I wonder if it's as robust as the archive tier approach.
upvoted 0 times
Gianna
23 days ago
Yeah, the archive tier with 'GFS Tiering' enabled could be a better choice for off-site backups.
upvoted 0 times
...
Ryan
1 months ago
I agree, but the archive tier approach might be more robust.
upvoted 0 times
...
Olene
1 months ago
Option D sounds good, 'Copy' to a capacity tier could work.
upvoted 0 times
...
...
Natalya
2 months ago
I'd go with Option C. The 'Copy' option looks like the easiest way to create that secondary copy on a different media type.
upvoted 0 times
Matt
19 days ago
I think we're all on the same page with choosing Option C for this task.
upvoted 0 times
...
Phung
21 days ago
It's definitely a convenient feature to have for off-site backups without creating additional jobs.
upvoted 0 times
...
Kristin
24 days ago
I agree, the 'Copy' option on the Scale-out Backup Repository would make it easy to achieve that.
upvoted 0 times
...
Francesco
1 months ago
Option C seems like the best choice for creating a secondary copy on a different media type.
upvoted 0 times
...
...
Remedios
2 months ago
But wouldn't enabling the 'Move' option be more efficient in this scenario?
upvoted 0 times
...
Brett
2 months ago
Option B seems to be the way to go. GFS Tiering should handle the off-site storage requirement without any extra work.
upvoted 0 times
Kristel
1 months ago
Exactly, it's a convenient way to ensure our data is stored off-site.
upvoted 0 times
...
Shawana
1 months ago
That's great, it will save us from having to create additional backup jobs.
upvoted 0 times
...
Delbert
2 months ago
I agree, using the archive tier with GFS Tiering will make sure the data is stored off-site without any extra effort.
upvoted 0 times
...
Lindsey
2 months ago
I think so too, it will automatically handle the off-site storage for us.
upvoted 0 times
...
Lynelle
2 months ago
I agree, option B with GFS Tiering sounds like the best solution.
upvoted 0 times
...
Keena
2 months ago
Option B is a good choice. GFS Tiering will handle the off-site storage automatically.
upvoted 0 times
...
...
Lilli
2 months ago
I disagree, I believe the correct answer is B) Add an archive tier to the Scale-out Backup Repository and enable 'GFS Tiering'.
upvoted 0 times
...
Remedios
2 months ago
I think the answer is A) Add a capacity tier to the Scale-out Backup Repository and enable the 'Move' option.
upvoted 0 times
...

Save Cancel