VEEAM VMCE_v12 Exam - Topic 17 Question 18 Discussion

Actual exam question for VEEAM's VMCE_v12 exam

Question #: 18
Topic #: 17

An engineer sets up a backup job with direct backup to the AWS S3. The retention of the job is set to 31 days and the immutable period is set to 31 days. However, one full backup data is not removed automatically after 60 days.

Which option could be the reason for this?

AThe backup job is disabled accidentally.

BThe backup data is encrypted.

CIt is an active full backup, not synthetic full.

DA retention exception is enabled for the restore point.

Show Suggested Answer

Suggested Answer: A

Veeam Backup & Replication allows you to set up failover plans to control the order in which VMs are started during a failover. By creating a failover plan, you can specify that the database servers boot before the application servers. This is achieved by setting up VM dependencies within the failover plan, ensuring that the database servers (which are critical for the application servers to function) are operational before the application servers start. Creating a disaster recovery template (B), creating a replica mapping (C), or initiating a planned failover (D) does not directly address the boot order of the servers during failover.

by Alethea at Jul 06, 2024, 06:50 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Katina

5 months ago

Could it be that the job was disabled? Just a thought.

upvoted 0 times

...

Novella

5 months ago

I agree with C, synthetic backups are usually easier to manage.

upvoted 0 times

...

Mee

5 months ago

Wait, why would encryption affect deletion? That seems off.

upvoted 0 times

...

Elza

5 months ago

I think it's definitely option C. Active backups behave differently.

upvoted 0 times

...

Denae

6 months ago

Sounds like a retention exception issue.

upvoted 0 times

...

Shalon

6 months ago

I wonder if a retention exception could be the issue here. It seems like a plausible reason for the backup not being removed.

upvoted 0 times

...

Shawna

6 months ago

Could it be that the backup is still considered active? I feel like I read that active backups might not be deleted automatically.

upvoted 0 times

...

Vincenza

6 months ago

I think I saw a similar question where the backup job was disabled, but I can't recall if that would affect the retention period.

upvoted 0 times

...

Truman

6 months ago

I remember something about retention settings, but I'm not sure how they interact with immutability in AWS.

upvoted 0 times

...

Roxane

6 months ago

I've got a hunch that the backup being an active full, not a synthetic full, could be the reason it's not being removed. That might be causing the retention policy to not work as expected.

upvoted 0 times

...

Tamesha

6 months ago

I'm a bit confused on this one. The retention and immutable period are both 31 days, so I'm not sure why the full backup wouldn't be removed automatically. Maybe it's an issue with the backup job being disabled?

upvoted 0 times

...

Dylan

6 months ago

Okay, let's see. The key details are the 31-day retention and immutable period, but the full backup isn't being removed after 60 days. Could it be a retention exception?

upvoted 0 times

...

Teri

6 months ago

Hmm, this seems like a tricky one. I'll need to think through the backup process and retention policies carefully to figure this out.

upvoted 0 times

...

Fausto

7 months ago

This question seems straightforward, I think the answer is to add the RSSO Group to the firewall policy.

upvoted 0 times

...

Dacia

7 months ago

Hmm, I'm a bit unsure about this. I'll need to review the concepts of critical chain, crashing, leads, and fast tracking to decide which one is the riskiest.

upvoted 0 times

...

Larae

12 months ago

Haha, I bet the engineer just accidentally hit the 'Disable Backup' button. Classic move, right?

upvoted 0 times

Lorrine

10 months ago

D) A retention exception is enabled for the restore point.

upvoted 0 times

...

Ronna

10 months ago

C) It is an active full backup, not synthetic full.

upvoted 0 times

...

Ricarda

11 months ago

A) The backup job is disabled accidentally.

upvoted 0 times

...

Rozella

12 months ago

I'm going with B. The backup data is encrypted, so the auto-removal might not be working as expected.

upvoted 0 times

Louann

10 months ago

Let's check if the backup job is accidentally disabled. That could be the reason as well.

upvoted 0 times

...

Leontine

11 months ago

I agree with you, B. The encryption could be the reason for the backup data not being removed automatically.

upvoted 0 times

...

Ruby

11 months ago

I'm leaning towards D. A retention exception might be causing the issue.

upvoted 0 times

...

Tawna

12 months ago

I think it could be C. It's an active full backup, not synthetic full.

upvoted 0 times

...

Melodie

1 year ago

C seems like the most likely reason to me. If it's an active full backup and not a synthetic full, it won't be removed automatically after 60 days.

upvoted 0 times

Twanna

11 months ago

Yes, an active full backup won't be removed automatically after 60 days.

upvoted 0 times

...

Peter

11 months ago

I agree, C seems like the most likely reason.

upvoted 0 times

...

Jina

1 year ago

Hmm, I think option D is the answer here. The retention exception must be enabled for the restore point, preventing the full backup from being removed automatically.

upvoted 0 times

...

Belen

1 year ago

But what about option D? Could a retention exception be causing this issue?

upvoted 0 times

...

Pamella

1 year ago

I agree with Ruthann, it makes sense that it's an active full backup.

upvoted 0 times

...

Ruthann

1 year ago

I think the reason could be option C.

upvoted 0 times

...