[Q26-Q41] 100% Passing Guarantee – Brilliant VMCA2022 Exam Questions PDF [Jul-2024]

Immutable repositories are backup storage locations that prevent unauthorized modifications or deletions of backup data, ensuring its integrity and recoverability. Immutable repositories are essential for protecting backups against ransomware attacks, accidental deletions, or malicious insiders1.
Veeam Backup & Replication supports several types of immutable repositories, such as hardened repositories, immutable object storage repositories, and immutable deduplicating storage appliances2. Among these options, the best configuration for ensuring SLA compliance and providing protection against ransomware is to leverage hardened repositories at both primary and secondary sites, and offload to object storage in a public cloud with immutability enabled.
Hardened repositories are Linux-based repositories that use XFS file system with immutability flag to protect backup files from changes or removals. Hardened repositories can be used as primary or secondary backup targets, and can be combined with Veeam Scale-out Backup Repository to simplify backup management and optimize storage utilization3.
Object storage repositories are cloud-based repositories that use object storage services, such as Amazon S3, Microsoft Azure Blob Storage, or Google Cloud Storage, to store backup data. Object storage repositories can be used as secondary backup targets, and can leverage the immutability feature of the cloud provider to prevent backup data from being overwritten or deleted.
By using hardened repositories at both primary and secondary sites, you can achieve high availability and redundancy for your backup data, as well as fast and reliable restores. By offloading to object storage in a public cloud with immutability enabled, you can achieve long-term retention and compliance, aswell as cost savings and scalability. This configuration also follows the 3-2-1-1 backup rule, which recommends having three copies of data, on two different types of media, with one copy off-site and one copy immutable.
You can find more information about immutable repositories and how to configure them in the following resources:
* Immutable Backup Solutions: Linux Hardened Repository
* Unstructured Data Backups in Immutable Repositories
* Hardened Repository
* [Immutability for Object Storage Repositories]
* [3-2-1-1 Backup Rule]

Explanation
*MFA is a security method that requires users to provide two or more pieces of evidence to verify their identity, such as a password, a code, a token, or a biometric factor3.
*MFA adds an extra layer of protection against ransomware attacks, as it prevents attackers from accessing the Veeam components even if they manage to steal or guess the passwords of the administrative accounts12.
*MFA also helps to prevent unauthorized changes or deletions of backup data, as well as unauthorized restores or failovers of VMs or applications12.
The other options are not as effective or feasible, as they either do not provide enough security, limit the functionality, or disrupt the integration of the Veeam infrastructure.
References: 1: 6 Best Practices For Ransomware Protection | Veeam 2: Ransomware Prevention Best Practices
– Veeam 3: Multi-factor authentication – Wikipedia

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.

*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

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.

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]

The repository type that will be most impacted by using Veeam’s native encryption is dedupe repositories.
Dedupe repositories are backup repositories that use deduplication appliances or software to reduce backup size and optimize storage utilization. However, if you use Veeam’s native encryption for backup jobs that target dedupe repositories, you will lose most of the deduplication benefits, as encrypted data blocks cannot be deduplicated effectively. Therefore, it is recommended to use either the encryption feature of the deduplication device or software, or avoid encryption altogether for dedupe repositories.

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.

Explanation
The gold tier backup jobs have the most stringent recovery point objective (RPO) of one hour for image backup and 15 minutes for transaction log backup. This means that they need to run more frequently than the other backup jobs and create more restore points per day. Therefore, to properly plan the backup copy job settings, you will need more information on the gold tier backup jobs, such as the number of VMs, the size of backups, the change rate, the retention policy, and the bandwidth available for copying backups to the offsite location.
References: [Backup Copy], [Backup Methods], [Continuous Data Protection]

The additional Veeam capabilities that must be included in the conceptual design for gold level systems are SureBackup and Secure Restore. SureBackup is a feature that allows you to automatically verify the recoverability of your backups by running them in an isolated virtual lab. This can help you meet the requirement of testing the gold tier backups to verify recoverability. Secure Restore is a feature that allows you to scan your backups for malware before restoring them to the production environment. This can help you meet the requirement of scanning all backups for malware before restoring.
References: [SureBackup], [Secure Restore]

Explanation
To design a solution that meets the virtual infrastructure requirements for Veeam University Hospital, you need to collect some information during the discovery phase. This information will help you to understand the configuration and performance of the VMware clusters, the size and type of the data, and the backup and recovery objectives.
According to the Veeam Backup & Replication Best Practice Guide, some of the information related to the virtual infrastructure that is missing and must be collected during the discovery phase are:
*Local area network speed. This information will help you to determine the network bandwidth and throughput that are available for backup and replication traffic, as well as the impact of backup and replication activities on the network performance and latency.
*Size of the source data set. This information will help you to estimate the backup storage requirements, as well as the backup compression and deduplication ratios, based on the size and type of the data.
Therefore, the correct answer is A and D.

Explanation
To design a solution that meets the backup retention requirements for Veeam University Hospital, you need to consider the minimum requirement for on-premises backup retention for this project. This will help you to ensure the availability and reliability of your backup data, as well as the compliance and security of your backup storage.
According to the case study, the minimum requirement for on-premises backup retention for this project is B.
On-premises retention must be 14 daily, and two weekly backups.
This requirement means that:
*The on-premises backup retention is the policy that defines how long the backup data should be kept on the local backup storage, such as NFS storage, deduplication appliance, etc.
*The on-premises backup retention must be 14 daily and two weekly backups, which means that you need to keep at least 14 copies of the daily backups and two copies of the weekly backups on the local backup storage.
*The on-premises backup retention must be applied to all types of workloads that are backed up by Veeam Backup & Replication, such as virtual machines, physical servers, NAS systems, etc.
This requirement is based on the business and compliance needs of Veeam University Hospital, which are:
*To have a fast and reliable restore option for the most recent backups in case of a disaster or failure.
*To comply with the HIPAA regulations that require health care organizations to retain backup data for at least six years1.

To design a solution that meets the SureBackup job design requirements for Veeam University Hospital, you need to consider some of the environmental parameters that may affect the possible SureBackup job design.
This will help you to ensure the functionality and reliability of the SureBackup feature, which allows you to verify the recoverability of your backups in an isolated environment.
According to the Veeam Backup & Replication Best Practice Guide, some of the environmental parameters that may affect the possible SureBackup job design are:
*Virtual machines are stored on VMware encrypted datastores. This parameter may affect the possible SureBackup job design because VMware encrypted datastores require special handling and configuration for backup and restore operations. You need to enable encryption support in the backup infrastructure settings, as well as provide the necessary credentials and permissions for accessing the encrypted datastores. You also need to ensure that the virtual lab where the SureBackup jobs run supports encrypted datastores, which may require additional resources and licenses.
*Each site has 20 vLANs in use, with 16 being used for VMware workloads. This parameter may affect the possible SureBackup job design because vLANs require network mapping and routing for backup and restore operations. You need to configure the network settings and rules for the virtual lab where the SureBackup jobs run, as well as for the application group and backup job that are included in the SureBackup job. You also need to ensure that the network isolation and connectivity are maintained and tested for the virtual machines that are verified by the SureBackup job.

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]

Explanation
WAN accelerators are dedicated components that Veeam Backup & Replication uses for WAN acceleration.
WAN accelerators are responsible for global data caching and data deduplication, which reduce the amount of data that needs to be transferred over the network. By adding WAN accelerators to each site, you can improve the performance of backup copy jobs between sites, and reduce the bandwidth consumption and network traffic3 References:
1: Gateway Server – User Guide for VMware vSphere 2: Gateway Server – User Guide for VMware vSphere
3: WAN Accelerators – User Guide for VMware vSphere

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.