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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

VEEAM VMCA2022 Exam - Topic 2 Question 2 Discussion

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 following is the best option to still satisfy the requirement for offsite, immutable or air gapped backups if that cloud provider is selected for archive storage?
B) Set up Scale-out Backup Repository capacity tier to a different cloud provider than the archive tier.
A) Backup copy to a hardened repository at a different site.
C) Backup copy to a Windows repository in the cloud that is scheduled to turn off outside the backup window.
D) Set up capacity tier to local on-premises object storage that supports immutability.

VEEAM VMCA2022 Exam - Topic 2 Question 2 Discussion

Actual exam question for VEEAM's VMCA2022 exam
Question #: 2
Topic #: 2
[All VMCA2022 Questions]

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 following is the best option to still satisfy the requirement for offsite, immutable or air gapped backups if that cloud provider is selected for archive storage?

Show Suggested Answer Hide Answer
Suggested Answer: B

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 tiers1.The capacity tier can be configured to use Amazon S3 or Microsoft Azure Blob Storage, which support Object Lock feature for immutability2. 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. The other options are either not feasible (option A, as the scenario does not mention another site), not secure (option C, as the backup data can still be accessed or modified when the repository is online), or not offsite (option D, as the scenario requires a copy of backup data in a public cloud).Reference:Scale-out Backup Repository,Object Storage Immutability.


by Luisa at Nov 16, 2024, 03:04 PM

Limited Time Offer

25%

Off

Get Premium VMCA2022 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Annabelle
9 months ago
Wait, can you really trust cloud providers without immutability?
upvoted 0 times
...
Kathrine
9 months ago
D is definitely the way to go for immutability!
upvoted 0 times
...
Chanel
10 months ago
C sounds risky, not sure about that one.
upvoted 0 times
...
Yen
10 months ago
I think B is a better choice, more flexibility!
upvoted 0 times
...
Dell
10 months ago
Option A seems solid for offsite backups.
upvoted 0 times
...
Howard
10 months ago
I vaguely recall that option D might be relevant since it mentions local storage with immutability, but I need to double-check the specifics.
upvoted 0 times
...
Franklyn
10 months ago
I feel like option A could be a safe choice, but I’m not entirely confident about how a hardened repository works in this context.
upvoted 0 times
...
Anika
11 months ago
I think option B sounds familiar from our practice questions, where we talked about using different cloud providers for backup tiers.
upvoted 0 times
...
Katie
11 months ago
I remember we discussed the importance of offsite backups, but I'm not sure which option really provides immutability.
upvoted 0 times
...
Junita
11 months ago
I think the key here is to find a way to create an immutable backup copy, even if the cloud provider doesn't natively support it. Setting up a hardened repository at a different site or using local on-premises object storage that supports immutability seem like the most promising options to me.
upvoted 0 times
...
Sharika
11 months ago
I'm a bit confused by this question. Can the cloud provider's limitations be overcome, or do we need to find a completely separate solution? I'll need to review the options carefully to determine the best approach.
upvoted 0 times
...
Gerri
11 months ago
Okay, let's see. If the cloud provider doesn't support immutability, then I guess the best option would be to set up a separate backup repository on a different cloud platform that does support it. That way, we can still meet the requirement for offsite, immutable backups.
upvoted 0 times
...
Tijuana
11 months ago
Hmm, the fact that the cloud provider doesn't support immutability is a real challenge. I'll need to think through the different backup strategies and how they could work around that limitation.
upvoted 0 times
...
Tora
11 months ago
This seems like a tricky one. I'll need to carefully consider the requirements for offsite, immutable backups and how the cloud provider's limitations might impact the options.
upvoted 0 times
...
Leandro
2 years ago
Option D could work, but relying on on-premises object storage might be a hassle if the cusKasandraer is already looking to move to the cloud. A, option A seems like the most straightforward and reliable solution.
upvoted 0 times
...
Kasandra
2 years ago
Haha, option C reminds me of the old 'unplug the server to stop the backup' trick. Definitely not the way to go here.
upvoted 0 times
...
Elroy
2 years ago
I'm not sure why anyone would choose option C. Turning off a Windows repository in the cloud doesn't sound very reliable or secure to me.
upvoted 0 times
Lamar
2 years ago
I agree, option C does seem risky. Option D sounds like a more secure choice.
upvoted 0 times
...
Alton
2 years ago
D) Set up capacity tier to local on-premises object storage that supports immutability.
upvoted 0 times
...
Freida
2 years ago
B) Set up Scale-out Backup Repository capacity tier to a different cloud provider than the archive tier.
upvoted 0 times
...
Ciara
2 years ago
A) Backup copy to a hardened repository at a different site.
upvoted 0 times
...
...
Reiko
2 years ago
I agree with Judy. Option A is the most straightforward way to meet the immutable backup requirement, especially if the cloud provider doesn't support it natively.
upvoted 0 times
...
Judy
2 years ago
Option A seems like the best choice here. Keeping a backup copy in a hardened repository at a different site ensures that the data is stored off-site and is immutable, satisfying the requirement.
upvoted 0 times
Pete
2 years ago
B) Set up Scale-out Backup Repository capacity tier to a different cloud provider than the archive tier.
upvoted 0 times
...
Chery
2 years ago
That sounds like a secure option for offsite backups.
upvoted 0 times
...
Cecilia
2 years ago
A) Backup copy to a hardened repository at a different site.
upvoted 0 times
...
...
Charlene
2 years ago
I see both points, but I think option B) Set up Scale-out Backup Repository capacity tier to a different cloud provider than the archive tier could also work well.
upvoted 0 times
...
Celeste
2 years ago
I disagree, I believe option D) Set up capacity tier to local on-premises object storage that supports immutability is a better solution.
upvoted 0 times
...
Anglea
2 years ago
I think option A) Backup copy to a hardened repository at a different site is the best choice.
upvoted 0 times
...

Save Cancel