Practice Free VMCE_v12 Exam Online Questions
The administrator of a VMware environment backed up by Veeam Backup & Replication has a critical server with corruption on one of its three data drives.
What is the fastest way to bring this drive back online with the least disruption to business?
- A . Instant Disk Recovery
- B . Staged restore
- C . Instant VM Recovery
- D . Entire VM restore
A
Explanation:
The fastest way to bring a corrupted data drive back online with the least disruption in a VMware environment is through Instant Disk Recovery. This feature allows the administrator to quickly restore the specific affected disk from a backup, minimizing downtime and impact on business operations.
Reference: Veeam Backup & Replication User Guide, Veeam Instant Disk Recovery Guide
In the war against ransomware, a company decided to implement tape backup. The infrastructure contains Hyper-V VMs.
What is the correct approach to getting all servers onto tape?
- A . Create media pools, then create file to tape jobs.
- B . Create media sets, then create backup to tape jobs.
- C . Create media sets, then create file to tape jobs.
- D . Create media pools, then create backup to tape jobs.
D
Explanation:
The correct approach for backing up Hyper-V VMs to tape in a ransomware protection strategy is to create media pools first and then configure backup to tape jobs. This method ensures organized and efficient tape management while securing VM backups on tape media.
Reference: Veeam Backup & Replication User Guide, Veeam Tape Backup Configuration Guide
A customer wants to set up a Scale-Out Backup Repository. Due to malware concerns, immutability is recommended. An on-premises server can be used to hold primary backups, but it can only hold about 21 days of backups. A copy of the backups should be stored in AWS. The retention for all backups is 60 days.
Which configuration of a Scale-out Backup repository meets these requirements?
- A . Copy mode
Performance Tier: Windows REFS, immutability set for 11 days
Capacity Tier: Amazon S3, immutability set for 60 days - B . Copy and move mode
Performance Tier: Windows REFS, immutability set for 11 days
Capacity Tier: Amazon S3, immutability set for 60 days - C . Copy mode
Performance Tier: Linux Hardened Repository, XFS, immutability set for 11 days
Capacity Tier: Amazon S3, immutability set for 60 days - D . Copy and move mode
Performance Tier: Linux Hardened Repository, XFS, immutability set for 11 days
Capacity Tier: Amazon S3, immutability set for 60 days
D
Explanation:
To meet the requirements of setting up a Scale-Out Backup Repository (SOBR) with immutability for malware protection and specific retention policies, the most fitting configuration is D: Copy and move mode with a Performance Tier configured on a Linux Hardened Repository using the XFS file system and immutability set for 21 days, and a Capacity Tier on Amazon S3 with immutability set for 60 days. This setup utilizes the copy and move mode to ensure that backups are first stored on the on-premises Linux Hardened Repository with an immutability setting that prevents modifications to backups, providing protection against malware for the most recent 21 days of backups. As this on-premises server has limited capacity, older backups beyond 21 days are moved to the Capacity Tier in Amazon S3, where they are also protected with immutability for the entire 60-day retention period. This configuration leverages the strengths of both on-premises and cloud storage while ensuring that all backups are protected from modification or deletion by immutability, aligning with the customer’s malware protection concerns and retention requirements.
A daily backup job for seven Hyper-V VMs has been configured at the main site, keeping 14 days’ worth of backup files. They want to get a copy of the VM backups to a repository at the disaster recovery site. They want to keep six months’ worth of backup files at the disaster recovery site. They also need to be able to restore the VMs to any given day within two months and any given week within the six months.
How should a backup copy job be configured to meet these requirements?
- A . Use periodic copy (pruning) mode, keeping 62 days of retention and six monthly GFS restore points.
- B . Use immediate copy (mirroring) mode, keeping 180 days of retention.
- C . Use periodic copy (pruning) mode, keeping 180 days of retention.
- D . Use immediate copy (mirroring) mode, keeping 62 days of retention and 26 weekly GFS restore points.
A
Explanation:
To meet the specified requirements, configuring a backup copy job in periodic copy (pruning) mode with 62 days of retention and six monthly Grandfather-Father-Son (GFS) restore points is the best approach. This setup allows for daily backups for up to two months and weekly backups for up to six months, aligning with the desired restore capabilities.
Reference: Veeam Backup & Replication User Guide, Veeam GFS Retention Policy Explanation
A Veeam administrator has been tasked to create a backup that will automatically make a copy of data on a different media type, while also being off site, without creating additional backup or backup copy jobs. The administrator has determined that a Scale-out Backup Repository can be used as part of the solution.
How can this be accomplished?
- A . Add an archive tier to the Scale-out Backup Repository and enable "GFS Tierinq".
- B . Add a capacity tier to the Scale-out Backup Repository and enable the "Copy" option.
- C . Add an archive tier to the Scale-out Backup Repository and enable the "Copy" option.
- D . Add a capacity tier to the Scale-out Backup Repository and enable the "Move" option.
B
Explanation:
By adding a capacity tier to the Scale-out Backup Repository and enabling the "Copy" option, the administrator can create a backup that automatically copies data to a different media type (object storage) and also ensures that the data is offsite. This is accomplished without creating additional backup or backup copy jobs. The "Copy" option allows for immediate copying of backups to the capacity tier, meeting the criteria specified.
Reference: Veeam Backup & Replication User Guide: Scale-Out Backup Repository
Veeam Help Center: Capacity Tier and Archive Tier Configuration
An engineer has used a Linux Hardened Repository as the backup repository. The immutability period is set to 60 days.
The backup settings are:
Retention Policy: 14 days
GFS Weekly full backup: 1 week
GFS Monthly full backup: 6 months
If a full backup is created on 27th May 2023 with a monthly GFS flag, when will this restore point be automatically deleted?
- A . 2V June 2023
- B . 28th July 2023
- C . 28th November 2023
- D . 5th August 2023
C
Explanation:
The immutability period set on a Linux Hardened Repository prevents deletion of backup files for the duration of the immutability period. In this case, it is set to 60 days. However, the GFS (Grandfather-Father-Son) retention policy specifies that a monthly full backup is to be kept for 6 months. Since the full backup was created on 27th May 2023 and flagged as a monthly GFS backup, it will be retained for 6 months irrespective of the retention policy or the immutability setting. Hence, the restore point will be automatically deleted after 6 months, which would be on the 28th of November 2023.
Reference: Veeam Backup & Replication User Guide: GFS Retention Policy
Veeam Help Center: Linux Hardened Repository Immutability