VEEAM VMCA2022 Practice Exam Questions & Answers

The backup repository design that would meet the security, throughput, and retention requirements is to use backup jobs to Hardened Linux XFS-based repositories at the same site as the source data and use Backup copy jobs to Hardened Linux XFS-based repositories at the secondary site. A Hardened Linux repository is a type of backup repository that provides immutability and ransomware protection for backup files by using XFS file system features and Linux access control mechanisms. A Backup copy job is a type of backup job that copies backups from one repository to another, either on-site or off-site, with different retention settings. By using these features, you can ensure that your backups are secure, efficient, and compliant with regulatory and business needs.

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.

If using Veeam's native encryption, the repository type that will be impacted the most is the deduplicating storage appliance. This is because Veeam Backup & Replication uses different encryption keys for every job session, which makes the encrypted data blocks appear as different even if they contain duplicate data. This reduces the deduplication ratio and increases the storage consumption on the deduplicating appliance. If you want to achieve a higher deduplication ratio, you can disable data encryption or use the encryption feature on the deduplicating appliance itself1

The methods that should be used to scope virtual machine backups based on customer requirements are to create backups based on tags and to create backup jobs with same retention requirements. Creating backups based on tags allows dynamic scoping of backups based on VMware tags assigned to virtual machines. This can simplify backup management, as new or modified virtual machines will be automatically included or excluded from backup jobs based on their tags. Creating backup jobs with same retention requirements allows consistent application of backup policies based on the backup tiers defined by the customer. This can ensure compliance with regulatory and business needs, as different tiers of virtual machines will have different retention periods and restore points.

The direct risk of having Veeam Backup & Replication on the production domain is that a compromised Domain Admin could gain access to the backup server and its data. This could pose a serious security threat to the backup infrastructure and the customer data, as a malicious Domain Admin could delete, modify, or encrypt the backups, or restore them to a compromised environment. Therefore, it is recommended to isolate the backup server from the production domain and use a separate local administrator account for managing it.