VEEAM VMCA2022 Practice Exams
Last updated on Oct 21,2026- Exam Code: VMCA2022
- Exam Name: Veeam Certified Architect 2022
- Certification Provider: VEEAM
- Latest update: Oct 21,2026
During deeper technical discovery it was uncovered that that the customer also has a Fibre Channel SAN that needs protection. Veeam University Hospital asks about the option of performing backup from storage snapshots.
What component(s) will this require?
- A . Veeam backup proxies and repositories running on the servers.
- B . Veeam backup proxies running on physical servers.
- C . Veeam backup proxies running the Windows servers.
- D . Veeam backup proxies running on Linux serves.
B
Explanation:
To perform backup from storage snapshots for a Fibre Channel SAN, you need to deploy one or more physical servers that will act as backup proxies and connect them to the SAN fabric. This is because Veeam Backup & Replication needs to access the storage system over the Fibre Channel protocol, which is not supported by virtual machines. The backup proxies will read data from the storage snapshots and transfer it to the backup repositories1
A remote office has an eight-node vSphere cluster with VSAN storage. After performing the sizing
calculations, it is determined that the proxy role will require 64 CPUs and 128 GB of RAM to meet the stated backup SLAs.
How should these proxies be deployed?
- A . Deploy a single physical server with 64 CPUs and 128 GB of RAM.
- B . Deploy two physical proxies with 32 CPUs and 64 GB of RAM.
- C . Deploy four virtual proxies with 16 CPUs and 32 GB of RAM.
- D . Deploy eight virtual proxies with eight CPUs and 16 GB of RAM.
D
Explanation:
The best way to deploy the proxies for the remote office is to deploy eight virtual proxies with eight CPUs and 16 GB of RAM each. This option allows to leverage the Virtual appliance (Hot-Add) mode, which is the recommended transport mode for VSAN storage1. Virtual appliance mode enables LAN-free data transfer between the source datastore and the proxy, as well as load balancing and fault tolerance across multiple proxies2. The other options are either not optimal (option A and B, as physical proxies require LAN or SAN connection to access the source data, which may impact the network performance and backup SLAs3) or not supported (option C, as virtual proxies with more than eight CPUs are not compatible with Virtual appliance mode). References: Transport Modes, Virtual Appliance Mode, Direct Storage Access Mode, [Requirements and Limitations for VMware Backup Proxies].
When talking to someone who works for the customer, they mention they are working on a different project with a major cloud provider that does not currently support immutability.
Which of the following is the best option to still satisfy the requirement for offsite, immutable or air gapped backups if that cloud provider is selected for archive storage?
- A . Backup copy to a hardened repository at a different site.
- B . Set up Scale-out Backup Repository capacity tier to a different cloud provider than the archive tier.
- C . Backup copy to a Windows repository in the cloud that is scheduled to turn off outside the backup window.
- D . Set up capacity tier to local on-premises object storage that supports immutability.
B
Explanation:
The best option to still satisfy the requirement for offsite, immutable or air gapped backups if the cloud provider selected for archive storage does not support immutability is to set up Scale-out Backup Repository capacity tier to a different cloud provider than the archive tier. Scale-out Backup Repository is a logical entity that groups several backup repositories into a single pool of storage, and allows to move backup files between performance and capacity tiers1. The capacity tier can be configured to use Amazon S3 or Microsoft Azure Blob Storage, which support Object Lock feature for immutability2. By using a different cloud provider for the capacity tier than the archive tier, the backup data can be stored in two separate locations, with one copy being immutable or air gapped. The other options are either not feasible (option A, as the scenario does not mention another site), not secure (option C, as the backup data can still be accessed or modified when the repository is online), or not offsite (option D, as the scenario requires a copy of backup data in a public cloud). References: Scale-out Backup Repository, Object Storage Immutability.
What information is missing form discovery?
- A . What the current LAN bandwidth is at Fresno.
- B . What backup transport mode is currently used.
- C . What type of backup storage is currently used.
- D . What the available bandwidth is between Fresno and Carson City.
D
Explanation:
The information that is missing from discovery is what the available bandwidth is between Fresno and Carson City. This information is important for designing and sizing the backup copy jobs that need to run daily between the two sites. The available bandwidth can affect the backup copy performance, duration, and size. For example, you can use the available bandwidth to estimate how much data can be transferred between the sites within the backup copy window. You can also use the available bandwidth to determine whether you need to use compression, deduplication, or WAN acceleration to optimize the backup copy traffic.
You are examining the requirement: “If possible, the data written must be unchangeable to prevent ransomware attacks.”
Which types of jobs do not support using immutability from S3 Object Lock or hardened repositories? (Choose two)
- A . NAS backups
- B . Linux Agent backup copy jobs
- C . VMware backup jobs
- D . Agent for Mac backups
A D
Explanation:
The types of jobs that do not support using immutability from S3 Object Lock or hardened repositories are NAS backups and Agent for Mac backups. These types of jobs do not have the option to enable immutability in their settings, unlike VMware, Hyper-V, Linux Agent, or Windows Agent backup jobs. Therefore, they cannot leverage the immutability feature of S3 Object Lock or hardened repositories to protect their backups from ransomware or malicious deletion.
References: [S3 Object Lock Immutability], [Hardened Linux Repository], [NAS Backup], [Agent for Mac]
Which Veeam feature can be used to help achieve compliance with privacy regulations?
- A . Preferred networks.
- B . Location tags on Veeam Backup & Replication servers.
- C . Location tags on the subnets.
- D . Location tags on repositories.
D
Explanation:
The Veeam feature that can be used to help achieve compliance with privacy regulations is location tags on repositories. Location tags are labels that can be assigned to backup repositories to indicate their physical or logical location, such as country, region, or data center1. Location tags can help ensure that backup data is stored and processed in compliance with data residency and privacy laws, such as GDPR or CCPA, by allowing backup administrators to create backup policies based on the location of the source and target data2. The other options are not related to privacy compliance, as they are either used for network optimization (preferred networks), server identification (location tags on Veeam Backup & Replication servers), or backup scope (location tags on subnets). References: Location Tags, Using Location Tags.
Why is it recommended to have a Veeam backup server at each of the three sites?
- A . VMware cluster isolation.
- B . Replication requires a backup server at each site.
- C . VPN connections sites.
- D . Each site has production data.
D
Explanation:
According to the Veeam Backup & Replication Best Practice Guide1, some of the reasons why it is recommended to have a Veeam backup server at each of the three sites are:
• Each site has production data. This reason is based on the principle of locality, which states that backup data should be stored as close as possible to the source data, to reduce network traffic and latency, and to improve backup and restore speed and efficiency. Having a Veeam backup server at each site allows you to perform local backups of the production data at each site, without having to cross the WAN or VPN connections between sites.
What critical information was missing from discovery? (Choose 2)
- A . Type of backup storage currently used.
- B . Percentage split between Windows and Linux virtual machines.
- C . Size of current data sets.
- D . Virtualization platform Veeam University Hospital uses.
- E . Backup retention policy.
C E
Explanation:
To design a solution that meets the needs and requirements of Veeam University Hospital, you need to collect some critical information during the discovery phase. This information will help you to understand the current state of the environment, the goals and expectations of the stakeholders, and the constraints and challenges of the project.
According to the case study, some of the critical information that was missing from discovery are:
• Size of current data sets. This information is critical because it helps you to estimate the backup storage requirements, as well as the backup performance and efficiency, based on the size and type of data. You need to know how much data is stored on each workload, such as virtual machines, physical servers, NAS systems, etc., as well as how much data is changed or added on a daily or weekly basis.
• Backup retention policy. This information is critical because it helps you to define the backup retention settings and policies, such as the number and frequency of backup copies, the backup storage tiers, the backup deletion rules, etc. You need to know how long the backup data should be kept for compliance or historical purposes, as well as how much backup storage capacity is available or needed.
Which of the following could cause failures to meet the requirement to test gold tier backups?
- A . Backup jobs run every hour.
- B . You cannot firewall traffic between vLANs in the SureBackup job configuration.
- C . The LAN bandwidth is not sufficient for vPower NFS datastores.
- D . There may be too many networks.
B
Explanation:
A possible cause of failures to meet the requirement to test gold tier backups is that you cannot firewall traffic between vLANs in the SureBackup job configuration. This could prevent the gold tier virtual machines from communicating with each other or with other required services in the isolated virtual lab. For example, if a gold tier virtual machine needs to access a database server or a domain controller in another vLAN, it might fail to start or function properly in the SureBackup job. Therefore, it is important to ensure that all necessary vLANs and network settings are configured correctly in the SureBackup job.
While deciding which transport mode to use for the proxies, you notice that one of the requirements is support the encrypted datastore in VMware.
Which processing modes can you leverage for the backup proxies? (Choose 3)
- A . Network mode with Encryption (NBDSSL).
- B . Virtual Appliance (HotAdd) mode.
- C . Network (NBD) mode.
- D . Direct SAN.
- E . Direct SMB.
- F . Direct NFS.
A B E
Explanation:
To access encrypted datastores in VMware, you need to use a transport mode that supports encryption.
The following transport modes support encryption:
• Network mode with Encryption (NBDSSL): This mode uses an encrypted network connection between the backup proxy and the ESXi host to read and write data from the encrypted datastore. This mode does not require direct access to the datastore, but it can be slower than other modes due to network traffic and encryption overhead2
• Virtual Appliance (HotAdd) mode: This mode uses a virtual backup proxy that runs on an ESXi host and attaches virtual disks of the encrypted VMs to itself using the VMware vSphere API. This mode requires that the backup proxy and the source VMs reside on the same datastore or on datastores that are accessible by the same ESXi host. This mode can offer better performance than network mode, but it can also cause SCSI reservation conflicts if multiple backup proxies access the same datastore simultaneously3
• Direct SMB: This mode uses a physical backup proxy that accesses the encrypted datastore over the SMB protocol. This mode requires that the datastore is configured as an SMB share and that the backup proxy has read and write permissions on it. This mode can offer high performance and scalability, but it also requires additional configuration steps and security considerations4
The following transport modes do not support encryption:
• Network (NBD) mode: This mode uses an unencrypted network connection between the backup proxy and the ESXi host, which cannot access encrypted datastores2
• Direct SAN: This mode uses a physical backup proxy that accesses the encrypted datastore over the SAN fabric, which cannot decrypt encrypted data5
• Direct NFS: This mode uses a physical backup proxy that accesses the encrypted datastore over the NFS protocol, which does not support encryption6
References:
1: Hardened Repository – User Guide for VMware vSphere
2: Network Mode – User Guide for VMware vSphere
3: Virtual Appliance Mode – User Guide for VMware vSphere
4: Direct SMB Access Mode – User Guide for VMware vSphere
5: Direct SAN Access Mode – User Guide for VMware vSphere
6: Direct NFS Access Mode – User Guide for VMware vSphere