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 #91
During further discussions, the 3-2-1 rule was recommended.
What is the most efficient way to protect primary and secondary sites following the 3-2-1 rule?
- A . From existing backups at the primary site, create a backup copy to the secondary site. Offload backup data to object storage using Scale-out Backup Repository capacity tier.
- B . Send replicas directly from the primary to the secondary site. Backup replicas on the secondary site and tier this to object storage using Scale-out Backup Repository capacity tier.
- C . Send backups directly from the primary to the secondary site, avoiding duplicate data storage. Tier backup data to object storage using Scale-out Backup Repository capacity tier.
- D . Use storage snapshot support to backup a virtual machine using the secondary array. Backup snapshots on the secondary site and tier this to object storage using Scale-out Backup Repository capacity tier.
Correct Answer: A
A
Explanation:
Option A follows the 3-2-1 rule by having three copies of data (the original production data, the backup at the primary site, and the backup copy at the secondary site), two different media types (local disk and object storage), and one copy off-site (the backup copy at the secondary site). This option also reduces the amount of traffic sent over the network by using existing backups as seeds for backup copies, and reduces the storage costs by using cloud tier to move older backups to cheaper and unlimited cloud storage1
Reference: What is the 3-2-1 backup rule? – Veeam
A
Explanation:
Option A follows the 3-2-1 rule by having three copies of data (the original production data, the backup at the primary site, and the backup copy at the secondary site), two different media types (local disk and object storage), and one copy off-site (the backup copy at the secondary site). This option also reduces the amount of traffic sent over the network by using existing backups as seeds for backup copies, and reduces the storage costs by using cloud tier to move older backups to cheaper and unlimited cloud storage1
Reference: What is the 3-2-1 backup rule? – Veeam
Question #92
Which of the following areas would benefit from additional analysis on areas mentioned in the case study? (Choose 3)
- A . VMware
- B . MSSQL
- C . NAS
- D . On-premises Exchange
- E . PostgreSQL
- F . Hyper-V
Correct Answer: B C E
B C E
Explanation:
The areas that would benefit from additional analysis on areas mentioned in the case study are MSSQL, NAS, and PostgreSQL. These areas have specific backup and restore requirements that need to be considered and addressed in the design and sizing of the Veeam backup infrastructure. For example, MSSQL requires transaction log backup and application-aware processing to ensure consistent backups and point-in-time recovery. NAS requires file-level backup and storage integration to optimize backup performance and storage efficiency. PostgreSQL requires pre-freeze and post-thaw scripts to quiesce the database before backup and resume it after backup.
References: [MSSQL Server Backup], [NAS Backup], [PostgreSQL Backup]
B C E
Explanation:
The areas that would benefit from additional analysis on areas mentioned in the case study are MSSQL, NAS, and PostgreSQL. These areas have specific backup and restore requirements that need to be considered and addressed in the design and sizing of the Veeam backup infrastructure. For example, MSSQL requires transaction log backup and application-aware processing to ensure consistent backups and point-in-time recovery. NAS requires file-level backup and storage integration to optimize backup performance and storage efficiency. PostgreSQL requires pre-freeze and post-thaw scripts to quiesce the database before backup and resume it after backup.
References: [MSSQL Server Backup], [NAS Backup], [PostgreSQL Backup]
Question #93
Consider the requirements regarding immutable or air gapped and different types of workloads.
Which types of jobs do not support using immutability from S3 Object Lock or Hardened Repository and will need a different solution?
- A . Backup copy jobs with GFS enable.
- B . NAS backups.
- C . Backup Jobs.
- D . Scale-out Backup Repository offloads to Archive Tier to Amazon Glacier.
Correct Answer: B
B
Explanation:
• Backup copy jobs with GFS enabled. This type of job does not support using immutability from S3 Object Lock because it uses synthetic full backups, which require modifying existing backup files. Synthetic full backups are not compatible with immutability settings, as they violate the principle of not changing the backup files.
B
Explanation:
• Backup copy jobs with GFS enabled. This type of job does not support using immutability from S3 Object Lock because it uses synthetic full backups, which require modifying existing backup files. Synthetic full backups are not compatible with immutability settings, as they violate the principle of not changing the backup files.
Question #94
Assuming that you put the backup repositories in the backup network only, what possible issue could arise?
- A . Laptop agents cannot communicate with the repository.
- B . The proxies cannot communicate with the repositories.
- C . Capacity Tier Could offload is no possible.
- D . SQL logs cannot be shipped to repository.
Correct Answer: A
A
Explanation:
A possible issue that could arise if you put the backup repositories in the backup network only is that laptop agents cannot communicate with the repository. This is because laptop agents are not part of the backup network, which is non-routable according to the existing technical environment. Therefore, laptop agents cannot access or write data to the backup repositories in the backup network unless there is a proxy or gateway server that can bridge the communication between them.
References: [Veeam Agents Management Guide], [Veeam Backup Infrastructure Sizing Calculator]
A
Explanation:
A possible issue that could arise if you put the backup repositories in the backup network only is that laptop agents cannot communicate with the repository. This is because laptop agents are not part of the backup network, which is non-routable according to the existing technical environment. Therefore, laptop agents cannot access or write data to the backup repositories in the backup network unless there is a proxy or gateway server that can bridge the communication between them.
References: [Veeam Agents Management Guide], [Veeam Backup Infrastructure Sizing Calculator]
Question #95
Based on the requirements, what should be factored into the physical design when implementing backup copy jobs between sites?
- A . Ensure that the repositories leveraged have CPUs that support hardware encryption offload.
- B . Configure Veeam Backup Enterprise Manager on the same virtual machine as your Veeam Backup & Replication server
- C . Use physical servers for the Veeam backup proxies at each site
- D . Use virtual servers on separate ESXI host the Veeam backup proxies
Correct Answer: C
C
Explanation:
The factor that should be considered in the physical design when implementing backup copy jobs between sites is to use physical servers for the Veeam backup proxies at each site. A Veeam backup proxy is a data mover component that performs data processing and transfer tasks for backup and backup copy jobs. A physical server is preferred over a virtual server for better performance, reliability, and isolation. A physical server can also leverage hardware encryption offload to reduce CPU load and network traffic encryption to secure data in transit.
C
Explanation:
The factor that should be considered in the physical design when implementing backup copy jobs between sites is to use physical servers for the Veeam backup proxies at each site. A Veeam backup proxy is a data mover component that performs data processing and transfer tasks for backup and backup copy jobs. A physical server is preferred over a virtual server for better performance, reliability, and isolation. A physical server can also leverage hardware encryption offload to reduce CPU load and network traffic encryption to secure data in transit.
Question #96
After further discussion, it was determined that the customer has taken sufficient steps to secure the NFS network so that in-flight encryption is no longer required. You have decided to deploy VMware backup proxies as virtual machines per cluster to satisfy the scale out-requirement for proxies.
Which processing modes are preferred for the NFS datastores? (Choose 2)
- A . Backup from Storage Snapshots
- B . Network (NBD) mode
- C . Virtual Appliance (HotAdd) mode
- D . Network mode with Encryption (NBDSSL)
- E . Direct NFS
Correct Answer: A E
A E
Explanation:
Backup from Storage Snapshots and Direct NFS are the preferred processing modes for NFS datastores, as they offer the best performance and reliability for backup and restore operations12.
Backup from Storage Snapshots is a feature of Veeam Backup & Replication that leverages the native snapshot capabilities of the storage system to create a consistent point-in-time copy of the VM data. Veeam Backup & Replication then reads data directly from the storage snapshot, bypassing the ESXi host and reducing the impact on the production environment3. Backup from Storage Snapshots is supported for NFS datastores on NetApp, Nimble, Dell EMC, HPE, and Pure Storage systems4.
Direct NFS is a proprietary transport mode of Veeam Backup & Replication that uses a native NFS client deployed on the backup proxy to read and write data directly from and to the NFS datastore. Veeam Backup & Replication also bypasses the ESXi host and reduces the load on the production environment. Direct NFS is supported for NFS datastores on any storage system that supports NFS version 3 or 4.1.
The other options are not preferred because:
B) Network (NBD) mode is a transport mode that uses the VMware VDDK to communicate with the ESXi host over the network. This mode produces additional load on the ESXi host and the network, and may result in slower backup and restore performance.
C) Virtual Appliance (HotAdd) mode is a transport mode that uses the VMware VDDK to attach the disks of the processed VM to the backup proxy VM. This mode also produces additional load on the ESXi host and the network, and may cause issues with disk alignment or SCSI controller limitations.
D) Network mode with Encryption (NBDSSL) mode is a transport mode that uses the VMware VDDK to communicate with the ESXi host over the network with SSL encryption. This mode provides an extra layer of security, but also adds more overhead and reduces the backup and restore performance.
You can find more information about the processing modes and how to choose the best one for your environment in the following resources:
Transport Modes
Selecting a Transport Mode
Backup from Storage Snapshots
Storage Systems Supported for Backup from Storage Snapshots
[Direct NFS Access]
[Network Mode]
[Virtual Appliance Mode]
[Network Mode with Encryption]
A E
Explanation:
Backup from Storage Snapshots and Direct NFS are the preferred processing modes for NFS datastores, as they offer the best performance and reliability for backup and restore operations12.
Backup from Storage Snapshots is a feature of Veeam Backup & Replication that leverages the native snapshot capabilities of the storage system to create a consistent point-in-time copy of the VM data. Veeam Backup & Replication then reads data directly from the storage snapshot, bypassing the ESXi host and reducing the impact on the production environment3. Backup from Storage Snapshots is supported for NFS datastores on NetApp, Nimble, Dell EMC, HPE, and Pure Storage systems4.
Direct NFS is a proprietary transport mode of Veeam Backup & Replication that uses a native NFS client deployed on the backup proxy to read and write data directly from and to the NFS datastore. Veeam Backup & Replication also bypasses the ESXi host and reduces the load on the production environment. Direct NFS is supported for NFS datastores on any storage system that supports NFS version 3 or 4.1.
The other options are not preferred because:
B) Network (NBD) mode is a transport mode that uses the VMware VDDK to communicate with the ESXi host over the network. This mode produces additional load on the ESXi host and the network, and may result in slower backup and restore performance.
C) Virtual Appliance (HotAdd) mode is a transport mode that uses the VMware VDDK to attach the disks of the processed VM to the backup proxy VM. This mode also produces additional load on the ESXi host and the network, and may cause issues with disk alignment or SCSI controller limitations.
D) Network mode with Encryption (NBDSSL) mode is a transport mode that uses the VMware VDDK to communicate with the ESXi host over the network with SSL encryption. This mode provides an extra layer of security, but also adds more overhead and reduces the backup and restore performance.
You can find more information about the processing modes and how to choose the best one for your environment in the following resources:
Transport Modes
Selecting a Transport Mode
Backup from Storage Snapshots
Storage Systems Supported for Backup from Storage Snapshots
[Direct NFS Access]
[Network Mode]
[Virtual Appliance Mode]
[Network Mode with Encryption]
Question #97
During a proof of concept deployment at Veeam University Hospital, it is noted that only some of the backup files in a specific Scale-out Backup Repository are immutable.
What can cause this behavior?
- A . The ReFS extents do not have immutable enabled.
- B . Not all XFS extents in the Scale-out Backup Repository performance tier have the required flag enable.
- C . All extents in the Scale-out Backup Repository performance tier are ReFS.
- D . Not all EXT in the Scale-out Backup Repository performance archive tier have the required flag enabled.
Correct Answer: B
B
Explanation:
To make backup files immutable in a Scale-out Backup Repository, you need to use XFS extents with the reflink attribute enabled. This attribute allows Veeam Backup & Replication to create immutable backup files using the fast clone technology. If some of the XFS extents do not have this attribute enabled, they will not support immutability and the backup files stored on them will not be protected from deletion or modification1
B
Explanation:
To make backup files immutable in a Scale-out Backup Repository, you need to use XFS extents with the reflink attribute enabled. This attribute allows Veeam Backup & Replication to create immutable backup files using the fast clone technology. If some of the XFS extents do not have this attribute enabled, they will not support immutability and the backup files stored on them will not be protected from deletion or modification1
Question #98
Which strategy will satisfy the customer’s requirements for protection against ransomware?
- A . Deploy a Scale-out Backup Repository with Linux repositories and configure capacity tier to offload to immutable cloud storage.
- B . Deploy ReFS Scale-out Backup Repositories, and perform a backup copy to a different repository at the same time.
- C . Configure Linux Scale-out Backup Repositories in different physical locations and configure backup copy jobs in immediate mode.
- D . Deploy a ReFS Scale-Out Backup Repository and configure for immutability.
Correct Answer: A
A
Explanation:
• Use Linux repositories as the performance tier, which are more secure and resilient than Windows repositories, as they support immutable backups and prevent ransomware from accessing or deleting backup files1.
• Use immutable cloud storage as the capacity tier, which will offload older backup files to a public cloud object storage that supports immutability, such as Amazon S3 Object Lock or Azure Blob Storage with immutable policies2. This will ensure that the backup files cannot be modified or deleted by ransomware or malicious users for a specified period of time.
• Use Scale-out Backup Repository, which is a logical entity that groups several backup repositories into a single pool of storage, allowing for better backup performance, scalability, and management3.
References:
1: Protect against Ransomware with Immutable Backups – Veeam
2: Ransomware Protection: Learn How Veeam Can Protect Your Data
3: Scale-Out Backup Repository – Veeam Backup & Replication Best Practice Guide
A
Explanation:
• Use Linux repositories as the performance tier, which are more secure and resilient than Windows repositories, as they support immutable backups and prevent ransomware from accessing or deleting backup files1.
• Use immutable cloud storage as the capacity tier, which will offload older backup files to a public cloud object storage that supports immutability, such as Amazon S3 Object Lock or Azure Blob Storage with immutable policies2. This will ensure that the backup files cannot be modified or deleted by ransomware or malicious users for a specified period of time.
• Use Scale-out Backup Repository, which is a logical entity that groups several backup repositories into a single pool of storage, allowing for better backup performance, scalability, and management3.
References:
1: Protect against Ransomware with Immutable Backups – Veeam
2: Ransomware Protection: Learn How Veeam Can Protect Your Data
3: Scale-Out Backup Repository – Veeam Backup & Replication Best Practice Guide
Question #99
The customer has stated that synthetic operations and backups copy jobs must be completed in the desired window.
Which components should be sized correctly to ensure that this will be successful?
- A . Proxy and repository servers.
- B . Repository and gateway servers.
- C . Proxy and gateway servers.
- D . Veeam Backup & Replication and gateway servers.
Correct Answer: A
A
Explanation:
According to the Veeam Backup & Replication Best Practice Guide1, the proxy and repository servers are the components that should be sized correctly to ensure that synthetic operations and backup copy jobs can be completed in the desired window.
This is because:
• The proxy server is responsible for retrieving data from the source and sending it to the target. The proxy server performance depends on the CPU, memory, network, and storage resources available. The proxy server should have enough CPU cores and memory to handle concurrent tasks, as well as sufficient network bandwidth and storage throughput to transfer data efficiently.
• The repository server is responsible for storing backup files on the target storage. The repository server performance depends on the CPU, memory, network, and storage resources available. The repository server should have enough CPU cores and memory to handle concurrent tasks, as well as sufficient network bandwidth and storage throughput to write data efficiently. The repository server should also support the backup format and retention policy chosen for the backup copy job.
References: 1: Backup copy jobs – Veeam Backup & Replication Best Practice Guide
A
Explanation:
According to the Veeam Backup & Replication Best Practice Guide1, the proxy and repository servers are the components that should be sized correctly to ensure that synthetic operations and backup copy jobs can be completed in the desired window.
This is because:
• The proxy server is responsible for retrieving data from the source and sending it to the target. The proxy server performance depends on the CPU, memory, network, and storage resources available. The proxy server should have enough CPU cores and memory to handle concurrent tasks, as well as sufficient network bandwidth and storage throughput to transfer data efficiently.
• The repository server is responsible for storing backup files on the target storage. The repository server performance depends on the CPU, memory, network, and storage resources available. The repository server should have enough CPU cores and memory to handle concurrent tasks, as well as sufficient network bandwidth and storage throughput to write data efficiently. The repository server should also support the backup format and retention policy chosen for the backup copy job.
References: 1: Backup copy jobs – Veeam Backup & Replication Best Practice Guide
Question #100
During Veeam deployment, Veeam Financial Services has determined that the latency encountered during backup of the virtualized stock trading application servers running on VSAN is too high.
What is the recommended step Veeam Financial Services can take to improve this?
- A . Use backup from storage snapshot for the virtualized stock trading application servers.
- B . Implement Veeam Agent on the virtualized stock trading application servers.
- C . Use Veeam Replication to create replicas of the virtualized stock trading application servers at the remote site, then back up the replicas.
- D . Turn off application-aware processing for the virtualized stock trading application servers.
Correct Answer: A
A
Explanation:
Backup from storage snapshot is a feature of Veeam Backup & Replication that leverages the native snapshot capabilities of the storage system to create a consistent point-in-time copy of the VM data. Veeam Backup & Replication then reads data directly from the storage snapshot, bypassing the ESXi host and reducing the impact on the production environment1. Backup from storage snapshot is supported for VSAN datastores on NetApp, Nimble, Dell EMC, HPE, and Pure Storage systems2.
Using backup from storage snapshot for the virtualized stock trading application servers can improve the backup performance and reduce the latency, as it minimizes the time that the VM is running on a snapshot and avoids the network overhead of other transport modes3.
The other options are not recommended because:
B) Implementing Veeam Agent on the virtualized stock trading application servers is not necessary, as Veeam Backup & Replication can protect VMware VMs without agents. Veeam Agent is mainly used for physical servers, workstations, or cloud instances4.
C) Using Veeam Replication to create replicas of the virtualized stock trading application servers at the remote site, then back up the replicas is not optimal, as it adds more complexity and cost to the backup process. Veeam Replication is mainly used for disaster recovery purposes, not for backup5.
D) Turning off application-aware processing for the virtualized stock trading application servers is not advisable, as it may compromise the consistency and recoverability of the application data. Application-aware processing is a feature of Veeam Backup & Replication that ensures that the application data is in a consistent state before the backup or replication job starts.
You can find more information about backup from storage snapshot and other backup options for VSAN in the following resources:
Backup from Storage Snapshots
Storage Systems Supported for Backup from Storage Snapshots
Optimizing Veeam Backup & Replication Configuration for VMware VSAN
Veeam Agent Management
Veeam Replication
[Application-Aware Processing]
A
Explanation:
Backup from storage snapshot is a feature of Veeam Backup & Replication that leverages the native snapshot capabilities of the storage system to create a consistent point-in-time copy of the VM data. Veeam Backup & Replication then reads data directly from the storage snapshot, bypassing the ESXi host and reducing the impact on the production environment1. Backup from storage snapshot is supported for VSAN datastores on NetApp, Nimble, Dell EMC, HPE, and Pure Storage systems2.
Using backup from storage snapshot for the virtualized stock trading application servers can improve the backup performance and reduce the latency, as it minimizes the time that the VM is running on a snapshot and avoids the network overhead of other transport modes3.
The other options are not recommended because:
B) Implementing Veeam Agent on the virtualized stock trading application servers is not necessary, as Veeam Backup & Replication can protect VMware VMs without agents. Veeam Agent is mainly used for physical servers, workstations, or cloud instances4.
C) Using Veeam Replication to create replicas of the virtualized stock trading application servers at the remote site, then back up the replicas is not optimal, as it adds more complexity and cost to the backup process. Veeam Replication is mainly used for disaster recovery purposes, not for backup5.
D) Turning off application-aware processing for the virtualized stock trading application servers is not advisable, as it may compromise the consistency and recoverability of the application data. Application-aware processing is a feature of Veeam Backup & Replication that ensures that the application data is in a consistent state before the backup or replication job starts.
You can find more information about backup from storage snapshot and other backup options for VSAN in the following resources:
Backup from Storage Snapshots
Storage Systems Supported for Backup from Storage Snapshots
Optimizing Veeam Backup & Replication Configuration for VMware VSAN
Veeam Agent Management
Veeam Replication
[Application-Aware Processing]