VEEAM VMCA2022 Practice Exams
Last updated on Oct 22,2026- Exam Code: VMCA2022
- Exam Name: Veeam Certified Architect 2022
- Certification Provider: VEEAM
- Latest update: Oct 22,2026
Question #61
Veeam Life and Indemnity informs you that they have experienced issues with the time to back up file data from the existing legacy NAS backup. The NAS is being backed up at file level with a low change rate. The source capacity to back up is 12 TB connected to a 10 GbE switch over eight hours.
What assumptions about the current environment could you draw from this?
- A . The file path is over 256 characters long.
- B . AD permissions are set at file level.
- C . The files on the NAS are large
- D . The files on the NAS are small.
Correct Answer: D
Question #62
What information related to sizing the NAS infrastructure is missing and must be collected during the discovery? (Choose 2)
- A . Total number of network shares
- B . Size of the source data set
- C . Backup windows
- D . Recovery point objective
- E . Number of Scale-out Backup Repository extents currently used
Correct Answer: B D
B D
Explanation:
The information related to sizing the NAS infrastructure that is missing and must be collected during the discovery are the size of the source data set and the recovery point objective (RPO). These information are important for designing and sizing the NAS backup jobs and repositories. For example, you can use the size of the source data set to estimate how much storage space and network bandwidth are required for backing up NAS devices. You can also use the RPO to determine how frequently you need to run NAS backup jobs and how many restore points you need to keep on the backup repositories.
B D
Explanation:
The information related to sizing the NAS infrastructure that is missing and must be collected during the discovery are the size of the source data set and the recovery point objective (RPO). These information are important for designing and sizing the NAS backup jobs and repositories. For example, you can use the size of the source data set to estimate how much storage space and network bandwidth are required for backing up NAS devices. You can also use the RPO to determine how frequently you need to run NAS backup jobs and how many restore points you need to keep on the backup repositories.
Question #63
How would you configure replication with seeding, considering this deployment will have a Veeam Backup Server in both the primary and secondary site?
- A . On the Veeam Backup & Replication server at the primary site, create a backup job of the source machine from the primary site. At the secondary site import seeding data from this backup job. Create a replica job pointing to this backup job using re-mapping.
- B . On the Veeam Backup & Replication server at the primary site, create a backup job and backup copy job sending data to the secondary site. At the secondary site, create a replica job pointing to the repository with the backup copy data.
- C . On the Veeam Backup & Replication server at the primary site, create a backup job of the source virtual machine from the primary site. At the secondary site, create a replica job pointing to the repository with the backup job data.
- D . On the Veeam Backup & Replication server at the secondary site, create a backup job of the source virtual machine from the primary site. At the secondary site, create a backup copy job pulling the data from the primary and create a replica job pointing to the repository with the backup copy data.
Correct Answer: C
C
Explanation:
Option C uses replica seeding to reduce the network traffic during the initial replication. By creating a backup job of the source VM at the primary site and pointing the replica job to that backup repository at the secondary site, Veeam Backup & Replication can restore the VM from the backup and synchronize it with the latest state of the source VM. Then it can use the restored VM as a replica2
Reference: Replica Seeding and Mapping – User Guide for VMware vSphere
C
Explanation:
Option C uses replica seeding to reduce the network traffic during the initial replication. By creating a backup job of the source VM at the primary site and pointing the replica job to that backup repository at the secondary site, Veeam Backup & Replication can restore the VM from the backup and synchronize it with the latest state of the source VM. Then it can use the restored VM as a replica2
Reference: Replica Seeding and Mapping – User Guide for VMware vSphere
Question #64
For any replicated virtual workloads, the data must not be more than one hour old.
What could be a potential risk to the SLA for the offsite disaster recovery aspect of this requirement?
- A . The quantity of network hops.
- B . Data change rate.
- C . Average virtual machine size
- D . Local area network bandwidth.
Correct Answer: B
B
Explanation:
To design a disaster recovery solution that meets the requirement of having the replicated virtual workloads data not more than one hour old, you need to consider some of the potential risks and challenges that may affect the service level agreement (SLA) for the offsite disaster recovery aspect of this requirement. This will help you to ensure the availability and reliability of the replication and failover processes, as well as the recovery time objective (RTO) and recovery point objective (RPO) of the organization.
According to the Veeam Backup & Replication Best Practice Guide, one of the potential risks to the SLA for the offsite disaster recovery aspect of this requirement is B. Data change rate.
This risk means that:
• The data change rate is the amount of data that is modified, added, or deleted in a given time period. It is usually measured in percentage or megabytes per hour.
• The data change rate affects the replication performance and efficiency, as it determines how much data needs to be transferred and processed between the source and target sites.
• The data change rate also affects the replication frequency and consistency, as it determines how often and how accurately the replicas are updated and synchronized with the source workloads.
• The data change rate may vary depending on the type and activity of the workloads, such as database, file server, web server, etc. Some workloads may have a high data change rate, while others may have a low data change rate.
• The data change rate may exceed the available bandwidth or storage capacity between the source and target sites, which may result in replication failures, delays, or errors. This may compromise the SLA for the offsite disaster recovery aspect of this requirement, as it may cause the replicated virtual workloads data to be more than one hour old.
This risk has some implications for designing a solution with Veeam products and features, such as:
• The customer or a third-party vendor must monitor and measure the data change rate of the workloads that need to be replicated, as well as the available bandwidth and storage capacity between the source and target sites. This will help to plan and optimize the replication infrastructure, such as the proxy servers, repository servers, WAN accelerators, and failover plans, based on the data change rate.
• The customer or a third-party vendor must configure and adjust the replication settings and policies, such as the replication method, schedule, frequency, retention, compression, deduplication, etc., based on the data change rate. This will help to improve the replication performance and efficiency, as well as to meet the SLA for the offsite disaster recovery aspect of this requirement.
B
Explanation:
To design a disaster recovery solution that meets the requirement of having the replicated virtual workloads data not more than one hour old, you need to consider some of the potential risks and challenges that may affect the service level agreement (SLA) for the offsite disaster recovery aspect of this requirement. This will help you to ensure the availability and reliability of the replication and failover processes, as well as the recovery time objective (RTO) and recovery point objective (RPO) of the organization.
According to the Veeam Backup & Replication Best Practice Guide, one of the potential risks to the SLA for the offsite disaster recovery aspect of this requirement is B. Data change rate.
This risk means that:
• The data change rate is the amount of data that is modified, added, or deleted in a given time period. It is usually measured in percentage or megabytes per hour.
• The data change rate affects the replication performance and efficiency, as it determines how much data needs to be transferred and processed between the source and target sites.
• The data change rate also affects the replication frequency and consistency, as it determines how often and how accurately the replicas are updated and synchronized with the source workloads.
• The data change rate may vary depending on the type and activity of the workloads, such as database, file server, web server, etc. Some workloads may have a high data change rate, while others may have a low data change rate.
• The data change rate may exceed the available bandwidth or storage capacity between the source and target sites, which may result in replication failures, delays, or errors. This may compromise the SLA for the offsite disaster recovery aspect of this requirement, as it may cause the replicated virtual workloads data to be more than one hour old.
This risk has some implications for designing a solution with Veeam products and features, such as:
• The customer or a third-party vendor must monitor and measure the data change rate of the workloads that need to be replicated, as well as the available bandwidth and storage capacity between the source and target sites. This will help to plan and optimize the replication infrastructure, such as the proxy servers, repository servers, WAN accelerators, and failover plans, based on the data change rate.
• The customer or a third-party vendor must configure and adjust the replication settings and policies, such as the replication method, schedule, frequency, retention, compression, deduplication, etc., based on the data change rate. This will help to improve the replication performance and efficiency, as well as to meet the SLA for the offsite disaster recovery aspect of this requirement.
Question #65
You are trying to determine which feature would work the reliably for excluding the H: drive on MSSQL server virtual machines. The MSSQL servers are built on demand, not from virtual machine templates.
Which is the preferred method to achieve this requirement?
- A . Set up VMDK exclusion for the disk on which the H: resides in the Virtual Machines > Exclusions page for each virtual machine.
- B . Use the Exclusion tab under Guest Processing > Applications for VM backups to exclude the H: volume in MSSQL jobs.
- C . Use Veeam Agent Backups and set up Volume Backups and include everything but H:
- D . Use Veeam Agent Backups and use the Exclusions tab under Gest Processing > Application for MSSQL jobs.
Correct Answer: A
A
Explanation:
The preferred method to achieve the requirement of excluding the H: drive on MSSQL server virtual machines is to set up VMDK exclusion for the disk on which the H: resides in the Virtual Machines > Exclusions page for each virtual machine. This method allows you to exclude specific virtual disks from being processed by backup jobs based on their SCSI IDs or disk labels. This can save backup time and storage space by skipping unnecessary data. This method also works reliably regardless of whether the MSSQL servers are built on demand or from virtual machine templates.
A
Explanation:
The preferred method to achieve the requirement of excluding the H: drive on MSSQL server virtual machines is to set up VMDK exclusion for the disk on which the H: resides in the Virtual Machines > Exclusions page for each virtual machine. This method allows you to exclude specific virtual disks from being processed by backup jobs based on their SCSI IDs or disk labels. This can save backup time and storage space by skipping unnecessary data. This method also works reliably regardless of whether the MSSQL servers are built on demand or from virtual machine templates.
Question #66
It has been determined that the onsite repositories need to be immutable.
How should the repositories be configured to easily allow for additional capacity to be added?
- A . Stand-alone repositories using NTFS.
- B . Scale-out Backup Repositories consisting of hardened ReFS repositories.
- C . Stand-alone repositories using the XFS file system.
- D . Scale-out Backup Repositories consisting of hardened repositories.
Correct Answer: D
D
Explanation:
The repositories should be configured as Scale-out Backup Repositories consisting of hardened repositories to easily allow for additional capacity to be added and to meet the immutability requirement. Scale-out Backup Repository is a logical entity that groups several backup repositories into a single pool of storage, and allows to add or remove backup repositories as needed1. Hardened repository is a Linux-based backup repository with immutability enabled, which prevents backup files from being modified or deleted until the specified retention period expires2. The other options are either not immutable (option A and C, as NTFS and XFS do not support immutability) or not scalable (option B, as ReFS does not support adding or removing extents in a Scale-out Backup Repository3). References: Scale-out Backup Repository, Hardened Repository, ReFS Limitations.
D
Explanation:
The repositories should be configured as Scale-out Backup Repositories consisting of hardened repositories to easily allow for additional capacity to be added and to meet the immutability requirement. Scale-out Backup Repository is a logical entity that groups several backup repositories into a single pool of storage, and allows to add or remove backup repositories as needed1. Hardened repository is a Linux-based backup repository with immutability enabled, which prevents backup files from being modified or deleted until the specified retention period expires2. The other options are either not immutable (option A and C, as NTFS and XFS do not support immutability) or not scalable (option B, as ReFS does not support adding or removing extents in a Scale-out Backup Repository3). References: Scale-out Backup Repository, Hardened Repository, ReFS Limitations.
Question #67
One of Veeam Financial Services’ mission critical applications needs to be backed up daily. This Linux virtual machine is susceptible to snapshot stun.
Based on business requirements, how should this be accomplished?
- A . Perform the backup using a Veeam agent.
- B . Perform a normal virtual machine backup on the workload without application aware processing.
- C . Run pre-freeze and post-thaw scripts before backing up the workload.
- D . Perform the backup using application aware processing.
Correct Answer: C
C
Explanation:
Snapshot stun is a phenomenon that occurs when a VMware snapshot is removed and the virtual machine (VM) experiences a temporary freeze or performance degradation1. This can affect the availability and consistency of mission critical applications running on the VM.
To avoid snapshot stun, Veeam Backup & Replication offers several options for backing up Linux VMs, such as backup from storage snapshots, direct SAN access, or hot-add2. However, based on the business requirements, the best option is to run pre-freeze and post-thaw scripts before backing up the workload.
Pre-freeze and post-thaw scripts are custom scripts that you can configure to run on the Linux VM before and after the snapshot is taken. The pre-freeze script can be used to quiesce the application and flush its data to disk, ensuring a consistent backup. The post-thaw script can be used to resume the application and perform any necessary cleanup actions3.
By using pre-freeze and post-thaw scripts, you can achieve application consistency and minimize the impact of snapshot stun on the Linux VM. You can use the Veeam Backup & Replication user interface or the Veeam
PowerShell snap-in to configure the scripts for the backup job3.
You can find more information about pre-freeze and post-thaw scripts and how to use them in the following resources:
Pre-Freeze and Post-Thaw Scripts
Best Practice for Backing Up Linux VMs
Snapshot Stun Issue
C
Explanation:
Snapshot stun is a phenomenon that occurs when a VMware snapshot is removed and the virtual machine (VM) experiences a temporary freeze or performance degradation1. This can affect the availability and consistency of mission critical applications running on the VM.
To avoid snapshot stun, Veeam Backup & Replication offers several options for backing up Linux VMs, such as backup from storage snapshots, direct SAN access, or hot-add2. However, based on the business requirements, the best option is to run pre-freeze and post-thaw scripts before backing up the workload.
Pre-freeze and post-thaw scripts are custom scripts that you can configure to run on the Linux VM before and after the snapshot is taken. The pre-freeze script can be used to quiesce the application and flush its data to disk, ensuring a consistent backup. The post-thaw script can be used to resume the application and perform any necessary cleanup actions3.
By using pre-freeze and post-thaw scripts, you can achieve application consistency and minimize the impact of snapshot stun on the Linux VM. You can use the Veeam Backup & Replication user interface or the Veeam
PowerShell snap-in to configure the scripts for the backup job3.
You can find more information about pre-freeze and post-thaw scripts and how to use them in the following resources:
Pre-Freeze and Post-Thaw Scripts
Best Practice for Backing Up Linux VMs
Snapshot Stun Issue
Question #68
Based on the requirements, and the assumption that Veeam University Hospital will keep their existing backup storage, which answer describes which components are needed for the on-premises design?
- A . Backup server, backup proxy, Backup Enterprise Manager, log shipping servers.
- B . Backup server, backup proxy, Backup Enterprise Manager, mount server, backup repository.
- C . Backup server, backup proxy, backup repository, Veeam vPower NFS service.
- D . Backup server, backup proxy, backup repository, mount server, guest interaction proxy, gateway server.
Correct Answer: D
D
Explanation:
To design a solution that meets the backup and replication requirements for Veeam University Hospital, you need to consider some of the components that are needed for the on-premises design. This will help you to ensure the performance and reliability of the backup and replication operations, as well as the scalability and manageability of the backup infrastructure.
According to the Veeam Backup & Replication Best Practice Guide1, some of the components that are needed for the on-premises design are:
• Backup server. This is the core component of Veeam Backup & Replication that controls and coordinates backups, replication, recovery verification, and restore tasks. It also manages backup infrastructure components, such as proxy servers, repository servers, WAN accelerators, etc. You need to have a backup server at each site, as recommended by the best practice guide2.
• Backup proxy. This is a component that retrieves data from the source host, processes it and transfers to the backup repository. It also performs data compression, deduplication, encryption, etc. You need to have at least one backup proxy at each site, as recommended by the best practice guide3.
• Backup repository. This is a server where Veeam Backup & Replication keeps backup files, backup copies and metadata of replicated VMs. It can be a Windows or Linux server, a NAS device, a deduplication appliance, etc. You need to have at least one backup repository at each site, as recommended by the best practice guide4.
• Mount server. This is a component that mounts backup files from the backup repository to the backup proxy during restore operations. It also performs data decompression, deduplication, decryption, etc. You need to have a mount server at each site where you plan to perform restores, as recommended by the best practice guide5.
• Gateway server. This is a component that acts as a data mover between the backup proxy and the backup repository when they are located in different sites or networks. It also performs data encryption and decryption for secure data transfer. You need to have a gateway server at each site where you have a backup repository that is accessed by a remote backup proxy, as recommended by the best practice guide.
Therefore, based on these components, the answer that describes which components are needed for the on-premises design is D. Backup server, backup proxy, backup repository, mount server, gateway server.
D
Explanation:
To design a solution that meets the backup and replication requirements for Veeam University Hospital, you need to consider some of the components that are needed for the on-premises design. This will help you to ensure the performance and reliability of the backup and replication operations, as well as the scalability and manageability of the backup infrastructure.
According to the Veeam Backup & Replication Best Practice Guide1, some of the components that are needed for the on-premises design are:
• Backup server. This is the core component of Veeam Backup & Replication that controls and coordinates backups, replication, recovery verification, and restore tasks. It also manages backup infrastructure components, such as proxy servers, repository servers, WAN accelerators, etc. You need to have a backup server at each site, as recommended by the best practice guide2.
• Backup proxy. This is a component that retrieves data from the source host, processes it and transfers to the backup repository. It also performs data compression, deduplication, encryption, etc. You need to have at least one backup proxy at each site, as recommended by the best practice guide3.
• Backup repository. This is a server where Veeam Backup & Replication keeps backup files, backup copies and metadata of replicated VMs. It can be a Windows or Linux server, a NAS device, a deduplication appliance, etc. You need to have at least one backup repository at each site, as recommended by the best practice guide4.
• Mount server. This is a component that mounts backup files from the backup repository to the backup proxy during restore operations. It also performs data decompression, deduplication, decryption, etc. You need to have a mount server at each site where you plan to perform restores, as recommended by the best practice guide5.
• Gateway server. This is a component that acts as a data mover between the backup proxy and the backup repository when they are located in different sites or networks. It also performs data encryption and decryption for secure data transfer. You need to have a gateway server at each site where you have a backup repository that is accessed by a remote backup proxy, as recommended by the best practice guide.
Therefore, based on these components, the answer that describes which components are needed for the on-premises design is D. Backup server, backup proxy, backup repository, mount server, gateway server.
Question #69
What is the retention requirement for this project?
- A . 12 weekly backups, six monthly backups and seven yearly backups.
- B . Have on-premises backups on hardened backup repositories.
- C . Have at least one copy of protected data on-premises.
- D . On-premises retention consists of 14 daily backups.
Correct Answer: A
A
Explanation:
The retention requirement for this project is 12 weekly backups, six monthly backups and seven yearly backups. This is stated in the business requirements section of the scenario, where it says “To meet regulatory requirements, backups must be retained for four years.” This implies that the backup data must be archived for long-term retention, and the Veeam solution supports the 3-2-1 rule, which means having three copies of data, on two different types of media, with one copy off-site1. The other options are not retention requirements, but rather technical requirements or design choices, such as having on-premises backups on hardened repositories, having at least one copy of data on-premises, or having 14 daily backups on-site. References: Veeam Certified Architect 2022 Exam Guide, page 9; Veeam Backup & Replication v11: Architecture and Design course, module 4.
A
Explanation:
The retention requirement for this project is 12 weekly backups, six monthly backups and seven yearly backups. This is stated in the business requirements section of the scenario, where it says “To meet regulatory requirements, backups must be retained for four years.” This implies that the backup data must be archived for long-term retention, and the Veeam solution supports the 3-2-1 rule, which means having three copies of data, on two different types of media, with one copy off-site1. The other options are not retention requirements, but rather technical requirements or design choices, such as having on-premises backups on hardened repositories, having at least one copy of data on-premises, or having 14 daily backups on-site. References: Veeam Certified Architect 2022 Exam Guide, page 9; Veeam Backup & Replication v11: Architecture and Design course, module 4.
Question #70
In order to satisfy the customer´s data scrubbing requirement, what Veeam components will be required?
- A . SureReplica job and application group.
- B . SureBackup job, virtual lab and application group.
- C . Virtual lab, proxy appliance and SureBackup job.
- D . Virtual lab, application group and script.
Correct Answer: D
D
Explanation:
Data scrubbing is the process of removing sensitive or confidential data from backups before restoring them, to comply with regulatory or legal requirements1. Veeam Backup & Replication supports data scrubbing for VMware VMs by using a custom script that runs inside the virtual lab2.
To perform data scrubbing, you need to create a virtual lab, an application group, and a SureBackup job. The virtual lab is a fenced-off environment where you can test and verify your backups without affecting the production network3. The application group is a collection of VMs that you want to restore and scrub. The SureBackup job is a task that automates the verification and restoration of VMs in the virtual lab.
The custom script is a PowerShell script that you need to write and configure to run on the VMs in the application group. The script should perform the necessary actions to delete or modify the data that you want to scrub, such as files, folders, registry keys, database records, etc2. You can use the Veeam PowerShell snap-in to access the Veeam functionality and objects from the script.
You can find more information about data scrubbing and how to configure it in the Veeam Backup & Replication User Guide for VMware vSphere2.
D
Explanation:
Data scrubbing is the process of removing sensitive or confidential data from backups before restoring them, to comply with regulatory or legal requirements1. Veeam Backup & Replication supports data scrubbing for VMware VMs by using a custom script that runs inside the virtual lab2.
To perform data scrubbing, you need to create a virtual lab, an application group, and a SureBackup job. The virtual lab is a fenced-off environment where you can test and verify your backups without affecting the production network3. The application group is a collection of VMs that you want to restore and scrub. The SureBackup job is a task that automates the verification and restoration of VMs in the virtual lab.
The custom script is a PowerShell script that you need to write and configure to run on the VMs in the application group. The script should perform the necessary actions to delete or modify the data that you want to scrub, such as files, folders, registry keys, database records, etc2. You can use the Veeam PowerShell snap-in to access the Veeam functionality and objects from the script.
You can find more information about data scrubbing and how to configure it in the Veeam Backup & Replication User Guide for VMware vSphere2.