Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

VEEAM Exam VMCE_v12 Topic 17 Question 18 Discussion

Actual exam question for VEEAM's VMCE_v12 exam
Question #: 18
Topic #: 17
[All VMCE_v12 Questions]

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?

Show Suggested Answer Hide 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.


Contribute your Thoughts:

Larae
2 months ago
Haha, I bet the engineer just accidentally hit the 'Disable Backup' button. Classic move, right?
upvoted 0 times
Lorrine
8 days ago
D) A retention exception is enabled for the restore point.
upvoted 0 times
...
Ronna
13 days ago
C) It is an active full backup, not synthetic full.
upvoted 0 times
...
Ricarda
15 days ago
A) The backup job is disabled accidentally.
upvoted 0 times
...
...
Rozella
2 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
11 days ago
Let's check if the backup job is accidentally disabled. That could be the reason as well.
upvoted 0 times
...
Leontine
28 days ago
I agree with you, B. The encryption could be the reason for the backup data not being removed automatically.
upvoted 0 times
...
Ruby
1 months ago
I'm leaning towards D. A retention exception might be causing the issue.
upvoted 0 times
...
Tawna
1 months ago
I think it could be C. It's an active full backup, not synthetic full.
upvoted 0 times
...
...
Melodie
2 months 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
1 months ago
Yes, an active full backup won't be removed automatically after 60 days.
upvoted 0 times
...
Peter
1 months ago
I agree, C seems like the most likely reason.
upvoted 0 times
...
...
Jina
2 months 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
2 months ago
But what about option D? Could a retention exception be causing this issue?
upvoted 0 times
...
Pamella
2 months ago
I agree with Ruthann, it makes sense that it's an active full backup.
upvoted 0 times
...
Ruthann
3 months ago
I think the reason could be option C.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77