VMCE_V12 Practice Questions

The restore point is governed by two separate time-based policies: the GFS retention policy and the immutability period.

1. GFS Retention: The backup is flagged for monthly GFS retention, which is set for 6 months. Therefore, the retention policy will protect this restore point until November 27th, 2023 (May 27th + 6 months).

2. Immutability: The Linux Hardened Repository is configured with a 60-day immutability period. This lock prevents deletion until July 26th, 2023 (May 27th + 60 days).

Veeam will only delete a restore point after both its retention period and its immutability period have expired. Since the GFS retention period (November 27th, 2023) is longer than the immutability period (July 26th, 2023), the restore point will be deleted by the next job run after its retention expires.

A. 2V June 2023: This date (likely a typo for 27th June) is too early and does not align with either the 60-day immutability or the 6-month GFS retention.

B. 28th July 2023: This is when the 60-day immutability period expires, but the 6-month GFS retention policy still actively protects the restore point from deletion.

D. 5th August 2023: This date is arbitrary and does not correspond to the expiration of either the configured immutability or the GFS retention policy.

1. Veeam Backup & Replication V12 User Guide for VMware vSphere

"Retention for GFS Backups" section: "If a GFS restore point is stored on a hardened repository with immutability

Veeam Backup & Replication will remove it only after both retention and immutability periods are over." This confirms that the later of the two dates dictates the deletion.

2. Veeam Backup & Replication V12 User Guide for VMware vSphere

"Hardened Repository" section: "For each backup file

Veeam Backup & Replication sets an immutability flag with a time stamp when the file must become immutable until. The time stamp is calculated as follows: current time + number of days specified in the Make recent backups immutable for setting." This explains how the immutability period is applied.

3. Veeam Backup & Replication V12 User Guide for VMware vSphere

"GFS Retention Policy" section: This section details how GFS flags preserve specific full backup files for longer periods (weekly

monthly

etc.)

independent of the short-term retention policy. In this scenario

the 6-month policy is the active retention rule for this specific restore point.

The job statistics Load: Source 0% > Proxy 68% > Network 0% > Target 0% clearly identify the backup proxy as the performance bottleneck. In an all-in-one deployment, the Veeam Backup Server itself performs the proxy role, and its resources (CPU/RAM) are overwhelmed by the data processing tasks for the grown environment. Adding a new, dedicated backup proxy server will offload this processing task. Veeam can then distribute the workload between the original proxy and the new one, allowing for more concurrent processing and significantly reducing the overall backup time to meet the RPOs.

A. Edit the Backup Job settings and enable parallel processing from Advanced options: Enabling more parallel tasks would increase the load on the already overwhelmed proxy, worsening the bottleneck rather than resolving it.

B. Split the VMs in several jobs with the same schedule to process the VMs in parallel: This would create more jobs competing for the same limited resources on the single, bottlenecked proxy, leading to resource contention and likely no improvement.

D. Install another Veeam Backup & Replication server and move half of the VMs to be processed in a separate job: This is an unnecessarily complex and costly solution that creates management overhead. The standard method to scale a Veeam deployment is by adding components like proxies, not entire VBR servers.

1. Veeam Backup & Replication V12 Help Center for VMware vSphere

Real-Time Statistics: This document explains how to interpret the bottleneck statistics. It states

"The bottleneck is the component with the highest load percentage... Proxy — the backup proxy is the bottleneck. The data processing on the proxy is slow." This confirms the analysis of the provided job statistics.

Source: https://helpcenter.veeam.com/docs/backup/vsphere/realtimestatistics.html?ver=120

Section: "Bottleneck Analysis".

2. Veeam Backup & Replication V12 Help Center for VMware vSphere

Backup Proxy: This guide details the role of the backup proxy and the benefits of deploying additional ones. It explicitly states

"To take the load off the backup server

you can deploy backup proxies... For better performance

it is recommended to deploy backup proxies on dedicated machines." This directly supports adding a new proxy to solve the performance issue.

Source: https://helpcenter.veeam.com/docs/backup/vsphere/backupproxy.html?ver=120

Section: "Backup Proxy".

3. Veeam Best Practices V12

VMware Proxies: This official best practices guide recommends scaling out by adding proxies for performance. It notes

"Deploying multiple proxies allows for proxy load balancing

which increases backup performance and reliability." This validates option C as the correct architectural approach to scaling.

Source: https://bp.veeam.com/vbr/2Design/DVeeamComponents/Dbackupproxies/vmwareproxies.html

Section: "Proxy Sizing".

Veeam Backup & Replication integrates directly with VMware vSphere infrastructure, including its tagging system. To dynamically add VMs based on an installed application, an administrator can create a specific vSphere tag (e.g., "App: CustomApp") and assign it to all relevant VMs. A Veeam backup job can then be configured to use this tag as its source object. When the job runs, it queries vCenter Server for all VMs with that specific tag and includes them in the backup. This method ensures that as new VMs are provisioned and tagged, or as tags are removed, the backup job's scope is automatically and dynamically updated without requiring manual edits to the job itself.

A. Using the RESTful API is a complex, programmatic approach for automation, not the standard, built-in method for creating a dynamically populated job within the console.

B. This is overly specific to Veeam Enterprise Manager and incorrectly assumes the use of "both tags," which is not a requirement stated in the question.

D. This method requires external scripting and manual or scripted updates to a CSV file, making it less integrated and less "dynamic" than using native vSphere tags.

1. Veeam Backup & Replication User Guide for VMware vSphere v12: In the section "Creating VM and vApp Backup Jobs

" the "Virtual Machines" step details how to add objects to a job. It states: "When you add a container to the job... The job will process all VMs that are children of the added container at the time the job is started." The "Tags" view is listed as one such container

confirming its use for dynamic job population.

2. Veeam Backup & Replication v12 Best Practices: The "Job Configuration" section

under the subsection "VM Grouping

" recommends using vSphere tags to group virtual machines based on criteria such as application type or service level agreement (SLA). This aligns perfectly with the scenario of grouping VMs by a "custom application" for backup.

3. VMCE v12 Student Guide: Module 2

"Building Backup Capabilities

" explicitly covers the creation of backup jobs. It details the use of vSphere containers

including hosts

clusters

folders

resource pools

and tags

as a primary method for dynamically selecting VMs for protection.

The Virtual appliance (Hot-Add) transport mode is the recommended method for protecting VMware environments using vSAN. In this mode, the backup proxy, which is a virtual machine, directly attaches the snapshots of the target VM's virtual disks. Data is then read directly from the vSAN datastore through the proxy's storage controller, bypassing the VMkernel network stack for data transfer. This architecture effectively isolates the backup data traffic from the production VMkernel network, fulfilling the specified requirement while providing efficient, LAN-free backup performance.

A. Direct NFS access: This transport mode is specifically designed for VMs residing on NFS datastores and is not applicable to vSAN storage.

B. Direct SAN access: This mode is used for Fibre Channel or iSCSI LUNs. vSAN does not present storage as traditional LUNs that an external proxy can access.

C. Network mode: This mode transfers data from the ESXi host to the proxy over the network via the VMkernel interface, which directly contradicts the requirement for isolation.

1. Veeam Backup & Replication V12 User Guide for VMware vSphere

"Transport Modes

" Page 1. Retrieved from helpcenter.veeam.com.

Quote/Paraphrase: The guide explicitly states

"For VMs that are hosted on a vSAN datastore

it is recommended that you use the Virtual appliance transport mode." It further explains that in Virtual Appliance mode

"Data is retrieved directly from the datastore

" which confirms it bypasses the network stack.

2. Veeam Backup & Replication V12 User Guide for VMware vSphere

"Virtual Appliance Transport

" Page 1. Retrieved from helpcenter.veeam.com.

Quote/Paraphrase: "In the Virtual appliance transport mode

Veeam Backup & Replication uses the VMware vSphere API to mount and unmount VM snapshots to a backup proxy... This transport mode is recommended if the backup proxy is a VM." This describes the mechanism that avoids the VMkernel network for data transfer.

3. Veeam Backup & Replication V12 User Guide for VMware vSphere

"Network Transport

" Page 1. Retrieved from helpcenter.veeam.com.

Quote/Paraphrase: "In the Network transport mode

data is retrieved over the local network (LAN). The ESXi host reads data from the storage and sends it to the backup proxy over the LAN." This confirms that Network mode uses the VMkernel

making it incorrect for this scenario.

Veeam Service Provider Console v7 introduced the capability for service providers to remotely deploy and manage Veeam Backup for Microsoft 365 servers. This feature allows providers to install the Veeam Backup for Microsoft 365 software and its components on a target server directly from the VSPC web UI. This streamlines the onboarding process for offering Backup as a Service (BaaS) for Microsoft 365, centralizing both deployment and subsequent management tasks like license installation, job monitoring, and reporting within a single console.

A. Enterprise plugins: These are components of Veeam Backup & Replication and are managed through the VBR console, not deployed directly by the Service Provider Console.

C. Veeam Backup & Replication: The Service Provider Console connects to and manages existing Veeam Backup & Replication servers; it does not have a feature to deploy the VBR server itself.

D. Veeam One: The Service Provider Console integrates with and collects data from existing Veeam ONE servers for monitoring and reporting but does not deploy the Veeam ONE server.

1. Veeam Service Provider Console 7.0 User Guide for Service Providers

"Deployment and Management of Veeam Backup for Microsoft 365

" Page 213. This section explicitly states

"You can deploy the Veeam Backup for Microsoft 365 server on a machine in the client infrastructure or in the service provider infrastructure." It then details the deployment wizard steps.

2. Veeam Help Center (Veeam Service Provider Console 7.0)

"About Veeam Backup for Microsoft 365 Management." This page details the functionality

stating

"Veeam Service Provider Console allows you to automate deployment and configuration of Veeam Backup for Microsoft 365 on client computers."

3. Veeam Service Provider Console 7.0 Release Notes

"What's New

" Section: "Veeam Backup for Microsoft 365 management and monitoring." This document highlights the new capability: "Deployment and management for Veeam Backup for Microsoft 365 v7 allows you to remotely install the product..."

Veeam Backup & Replication V12 includes a security mechanism to protect against brute-force attacks during Multi-Factor Authentication (MFA) login. If a user fails to enter the correct confirmation code five consecutive times, the system will temporarily lock the user account. This lockout is a protective measure that lasts for one minute, after which the user can attempt to log in again. This short duration prevents automated attacks while minimizing disruption for legitimate users who may have made a mistake.

A. The user is not permanently locked out; the lockout is a temporary security measure designed to thwart brute-force attempts.

B. A 24-hour lockout is excessively long for this type of protection; the actual duration is much shorter to balance security and usability.

D. The lockout period is specifically defined as one minute in the product documentation, not one hour.

1. Veeam Backup & Replication User Guide for VMware vSphere v12

"Security and Roles

" section: "Multi-Factor Authentication (MFA)

" Page 1.

Quote: "To prevent brute-force attacks

Veeam Backup & Replication will block the user account for 1 minute after 5 unsuccessful attempts to enter the confirmation code."

A Failover Plan is the specific feature within Veeam Backup & Replication designed for disaster recovery orchestration. It allows an administrator to pre-configure the sequence in which virtual machine replicas are started. This is critical for multi-tiered applications where dependencies exist, such as ensuring a database server is running before the application server that relies on it. The plan can include specific time delays between starting each VM and can be executed with a single click during a disaster, automating and simplifying the recovery process.

A. Attaching an XML file is not a native Veeam feature for orchestrating VM start order within a disaster recovery plan.

B. An Application Group is primarily used for recoverability testing with SureBackup and SureReplica jobs, not for orchestrating a live disaster recovery event.

D. Veeam ONE is a tool for monitoring, reporting, and capacity planning; it does not have capabilities to create or execute disaster recovery migration scripts.

1. Veeam Backup & Replication V12 User Guide for VMware vSphere:

Section: Failover Plans

Content: "A failover plan is a list of recovery instructions that automates the disaster recovery process for a group of critical VMs... For each VM in the list

you can specify a time delay. Veeam Backup & Replication will wait for the specified period of time before starting the next VM in the list." This directly confirms that Failover Plans are used to define a specific start order.

2. Veeam Backup & Replication V12 User Guide for VMware vSphere:

Section: Application Groups

Content: "An application group is a set of VMs that you want to test together... Veeam Backup & Replication will start VMs from the application group in the virtual lab one by one

in the order in which they are added to the group." This clarifies that Application Groups are for testing in an isolated lab

not for live failover orchestration.

The Recovery Point Objective (RPO) is the maximum acceptable age of files that must be recovered from backup for normal operations to resume. The disaster occurred at 10:00 AM, and the company's RPO is 4 hours. The goal is to minimize data loss. The restore point at 9:30 AM is the most recent valid point before the disaster, representing only 30 minutes of data loss. This is the "best" RPO achievable among the given options because it results in the least amount of lost data while being well within the 4-hour tolerance.

B. June 12, 2023, 5:00 AM

This restore point would result in 5 hours of data loss, which exceeds the required 4-hour RPO.

C. June 12, 2023, 1:00 PM

This restore point is dated after the disaster occurred, making it a logically impossible and invalid option for recovery.

D. June 12, 2023, 8:00 AM

While this restore point meets the 4-hour RPO, it represents 2 hours of data loss, which is inferior to the 30-minute data loss of option A.

---

1. Veeam VMCE v12 Student Guide

Module 1: Introduction

page 1-11. This guide defines RPO as "the maximum targeted period in which data might be lost from an IT service due to a major incident." This supports the principle of minimizing data loss up to the defined threshold.

2. Veeam Backup & Replication v12 User Guide for VMware vSphere

section "Key Concepts

" subsection "RPO and RTO." The documentation states

"Recovery Point Objective (RPO) is a maximum amount of data that you can afford to lose. RPO is measured in time." This confirms that the objective is to select the restore point that minimizes this loss.

3. Veeam Backup & Replication v12 User Guide for VMware vSphere

section "Backup Job

" subsection "Job Schedule." This section explains the direct relationship between the frequency of restore point creation and meeting the RPO: "The schedule determines the RPO — the maximum amount of data that you may lose." The 9:30 AM restore point represents a more frequent schedule and thus a better (lower) actual RPO.

The "File share copy job" is the specific feature in Veeam Backup & Replication designed to create a secondary copy of unstructured data backups. This job type allows you to copy file share backups from a source repository to a target repository, which can be at an alternate site. Crucially, it enables the configuration of a separate retention policy for the copied data, fulfilling the requirement for 10 additional days of retention. This functionality directly mirrors the backup copy strategy used for VMs and agents.

A. File to tape job: This job is for archiving file share backups to tape media for long-term retention, not for creating a secondary disk-based copy.

B. File share backup job: This job creates the primary backup of the unstructured data from the source file share; it does not copy an existing backup.

D. Periodic backup copy: This is a scheduling mode within a standard Backup Copy job, which is used for VM and agent backups, not for unstructured data backups.

1. Veeam Backup & Replication V12 User Guide for VMware vSphere

"File Share Backup Copy

" Page 1

Section: "File Share Backup Copy". The guide states

"To create a copy of your file share backups

you can use file share copy jobs. A file share copy job allows you to copy a file share backup from one backup repository to another."

2. Veeam Backup & Replication V12 User Guide for VMware vSphere

"Retention Policy for File Share Copy

" Page 1

Section: "Retention Policy for File Share Copy". This section details how to configure a separate retention policy for the copied files

stating

"For each file share copy job

you can define a separate retention policy."

3. Veeam Backup & Replication V12 User Guide for VMware vSphere

"File to Tape Jobs

" Page 1

Section: "File to Tape Jobs". This confirms that the purpose of this job is to "archive files from file shares to tape."

4. Veeam Backup & Replication V12 User Guide for VMware vSphere

"Backup Copy

" Page 1

Section: "Backup Copy". This section clarifies that Backup Copy jobs are for image-level backups (VMs

physical machines)

not file shares.

Veeam Explorer for Microsoft Exchange provides granular recovery capabilities for Microsoft Exchange Server databases. A key feature is its ability to browse and restore items from the "Recoverable Items" folder within a user's mailbox. This includes items that have been placed on Litigation Hold or In-Place Hold for e-discovery and compliance purposes. This allows administrators to recover items that are not visible in the user's primary mailbox but are retained by Exchange policies, directly from the backup without needing to restore the entire database.

A. Export to BAK file: This is incorrect. A .BAK file is a standard backup format for Microsoft SQL Server. Veeam Explorer for Microsoft Exchange exports items to .PST or .MSG files.

B. Restore databases from backups created with Veeam RMAN plug-in: This is incorrect. The Veeam Plug-in for Oracle RMAN is used for backing up and restoring Oracle databases, not Microsoft Exchange databases.

D. Restore original password for account objects: This is incorrect. Restoring user account objects and their attributes, including passwords, is a function of Veeam Explorer for Active Directory, not Veeam Explorer for Microsoft Exchange.

1. Veeam Backup & Replication User Guide for VMware vSphere v12

"Veeam Explorer for Microsoft Exchange > Viewing Items

" page 1118. The guide states

"Veeam Explorer for Microsoft Exchange allows you to view items that were placed on In-Place Hold or Litigation Hold. These items are located in the Recoverable Items folder of a user mailbox."

2. Veeam Backup & Replication User Guide for VMware vSphere v12

"Veeam Explorer for Microsoft Exchange > Exporting and Sending Items

" pages 1124-1127. This section details the supported export formats

which are "Export Mailboxes to PST Files" and "Save Mailbox Items to MSG Files

" with no mention of .BAK files.

3. Veeam Backup & Replication User Guide for VMware vSphere v12

"Veeam Explorer for Active Directory > Restore Scenarios > Restoring Passwords

" page 1098. This section explicitly describes password restoration as a capability of Veeam Explorer for Active Directory.

4. Veeam Backup & Replication User Guide for VMware vSphere v12

"Veeam Plug-in for Oracle RMAN

" page 938. This section details the functionality of the RMAN plug-in

confirming its use is exclusively for Oracle databases.