New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

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

Contribute your Thoughts:

0/2000 characters
Annabelle
3 months ago
Wait, can you really trust cloud providers without immutability?
upvoted 0 times
...
Kathrine
3 months ago
D is definitely the way to go for immutability!
upvoted 0 times
...
Chanel
4 months ago
C sounds risky, not sure about that one.
upvoted 0 times
...
Yen
4 months ago
I think B is a better choice, more flexibility!
upvoted 0 times
...
Dell
4 months ago
Option A seems solid for offsite backups.
upvoted 0 times
...
Howard
4 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
4 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
5 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
5 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
5 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
5 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
5 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
5 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
5 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
1 year 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
1 year 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
1 year 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
1 year ago
I agree, option C does seem risky. Option D sounds like a more secure choice.
upvoted 0 times
...
Alton
1 year ago
D) Set up capacity tier to local on-premises object storage that supports immutability.
upvoted 0 times
...
Freida
1 year ago
B) Set up Scale-out Backup Repository capacity tier to a different cloud provider than the archive tier.
upvoted 0 times
...
Ciara
1 year ago
A) Backup copy to a hardened repository at a different site.
upvoted 0 times
...
...
Reiko
1 year 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
1 year 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
1 year ago
B) Set up Scale-out Backup Repository capacity tier to a different cloud provider than the archive tier.
upvoted 0 times
...
Chery
1 year ago
That sounds like a secure option for offsite backups.
upvoted 0 times
...
Cecilia
1 year ago
A) Backup copy to a hardened repository at a different site.
upvoted 0 times
...
...
Charlene
1 year 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
1 year 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
1 year ago
I think option A) Backup copy to a hardened repository at a different site is the best choice.
upvoted 0 times
...

Save Cancel