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 5 Question 1 Discussion

Going through the discovery data, you examine the requirement for one-hour backups of gold tier virtual machines. Some of these servers have been identified as having large VMDKs with large bursts of I/O. Whichrequirement would you be breaking if you separated these virtual machines into their own backup jobs?
A) Backups must be dynamically scoped to reduce administrative overhead.
B) Gold tier machines have a recovery time objective of 30 minutes and a recovery point objective of one hour. C Mission-critical applications must not be affected by backup processes.
D) Alternative backup methods for virtual machines that are mission critical and susceptible to stuns must be used.

VEEAM VMCA2022 Exam - Topic 5 Question 1 Discussion

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

Going through the discovery data, you examine the requirement for one-hour backups of gold tier virtual machines. Some of these servers have been identified as having large VMDKs with large bursts of I/O. Which

requirement would you be breaking if you separated these virtual machines into their own backup jobs?

Show Suggested Answer Hide Answer
Suggested Answer: A

If you separated the large VMDKs into their own backup jobs, you would be creating more manual work for the backup administrator, who would have to configure and maintain multiple jobs for the same group of VMs. This would go against the requirement of reducing administrative overhead by using dynamic scoping.

Dynamic scoping is a feature of Veeam Backup & Replication that allows you to automatically include or exclude VMs from backup jobs based on tags, attributes, or policies1. For example, you can use VMware tags to assign a backup policy to a VM, and then use the tag as a filter in the backup job. This way, any VM with that tag will be automatically added to the backup job, and any VM without that tag will be automatically excluded. This simplifies the backup management and ensures that all VMs are protected according to their assigned policy.

For large VMDKs with high I/O, you can use alternative backup methods to avoid performance impact and stuns, such as storage snapshots, direct SAN access, or hot-add2.You can also use different storage optimization options to balance the deduplication ratio and the backup file size3. These options can be configured within the same backup job, without the need to separate the large VMDKs.

You can find more information about dynamic scoping and backup methods for large VMDKs in the following resources:

How to Use Dynamic Scoping in Veeam Backup & Replication

Backing up large vmdks (~12 TB)

Backup strategies for a large VM


by Eliseo at Nov 16, 2024, 07:29 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
Jenelle
8 months ago
I thought separating them would help, not hurt!
upvoted 0 times
...
Vivan
8 months ago
C seems relevant too, but B is definitely the main concern.
upvoted 0 times
...
Tonja
8 months ago
Wait, are we sure about that? What if the backups are optimized?
upvoted 0 times
...
Reynalda
8 months ago
Totally agree, RTO and RPO are crucial!
upvoted 0 times
...
Ilene
9 months ago
Sounds like B is the one you'd be breaking.
upvoted 0 times
...
Elza
9 months ago
I'm leaning towards D since it talks about alternative methods for mission-critical VMs, but I need to double-check my notes on that.
upvoted 0 times
...
Anjelica
9 months ago
I feel like the answer could be B, but I also recall something about administrative overhead being important too.
upvoted 0 times
...
Sharen
9 months ago
I remember a practice question that mentioned something about mission-critical applications and their backup processes. Could that be relevant here?
upvoted 0 times
...
Carma
9 months ago
I think separating the VMs might break the requirement about recovery time objectives, but I'm not entirely sure.
upvoted 0 times
...
Jeffrey
9 months ago
I've got a strategy here. Since the question is asking which requirement we'd be breaking, I'm going to carefully read through the answer choices and see which one best matches the information provided in the question. That should help me narrow it down.
upvoted 0 times
...
Jerry
9 months ago
Okay, let's see. The key things I'm looking at are the one-hour backup requirement for gold tier VMs, and the fact that some of these VMs have large VMDKs and I/O bursts. If we separate them into their own backup jobs, I think we might be breaking the recovery time objective (RTO) or recovery point objective (RPO) requirement. But I'll double-check the options to be sure.
upvoted 0 times
...
Roselle
9 months ago
Hmm, I'm a bit confused here. The question is asking about which requirement we'd be breaking, but it's not totally clear to me what the different requirements are. I'll need to re-read the question carefully.
upvoted 0 times
...
Rosina
9 months ago
This seems like a tricky one. I'll need to think carefully about the requirements and how separating the VMs into their own backup jobs might impact them.
upvoted 0 times
...
Caitlin
2 years ago
D looks good to me. These VMs need special treatment since they're prone to backup-related stuns.
upvoted 0 times
...
Glory
2 years ago
Haha, I bet the person who wrote this question is a real backup ninja. Sneaky stuff, trying to trip us up!
upvoted 0 times
Elbert
2 years ago
C) Mission-critical applications must not be affected by backup processes.
upvoted 0 times
...
Denny
2 years ago
A) Backups must be dynamically scoped to reduce administrative overhead.
upvoted 0 times
...
...
Lonny
2 years ago
I'd say C is the right answer. The backup process mustn't impact mission-critical apps, and separating these VMs could do just that.
upvoted 0 times
Glory
2 years ago
D) Alternative backup methods for virtual machines that are mission critical and susceptible to stuns must be used.
upvoted 0 times
...
Glendora
2 years ago
C) Mission-critical applications must not be affected by backup processes.
upvoted 0 times
...
Gertude
2 years ago
B) Gold tier machines have a recovery time objective of 30 minutes and a recovery point objective of one hour.
upvoted 0 times
...
Fabiola
2 years ago
A) Backups must be dynamically scoped to reduce administrative overhead.
upvoted 0 times
...
...
Francesco
2 years ago
Going for option B. The one-hour RPO for gold tier VMs is critical, so separating them into their own jobs could violate that requirement.
upvoted 0 times
Alaine
2 years ago
Let's stick with option B to ensure we meet the recovery objectives for the gold tier virtual machines.
upvoted 0 times
...
Avery
2 years ago
We can't risk violating that requirement. Option B is the way to go.
upvoted 0 times
...
Mari
2 years ago
Agreed, separating them into their own backup jobs could impact the recovery time objective.
upvoted 0 times
...
Benton
2 years ago
Option B is the best choice. We need to maintain the one-hour RPO for gold tier VMs.
upvoted 0 times
...
...
Vicki
2 years ago
That's true. We need to find a way to balance the requirements without compromising the mission-critical applications.
upvoted 0 times
...
Camellia
2 years ago
But wouldn't it also affect the recovery time objective of 30 minutes for gold tier machines?
upvoted 0 times
...
Vicki
2 years ago
I think separating the virtual machines into their own backup jobs would break the requirement for one-hour backups.
upvoted 0 times
...

Save Cancel