VEEAM VMCA2022 Veeam Certified Architect 2022 Exam Practice Test

Answer : B

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.

Answer : D

The component that should be deployed based on the customer's security requirements around restore capabilities is Enterprise Manager with granular RBAC policies defined. Enterprise Manager is a web-based interface that allows centralized management of multiple Veeam backup servers. It also provides granular RBAC policies that enable control over user permissions and access to restore data. For example, you can assign different roles to different users or groups based on their responsibilities and needs, such as backup administrator, restore operator, security officer, etc. You can also define custom scopes and rules for each role to limit their access to specific objects, jobs, or actions.

Answer : A

The recovery point objective (RPO) requirement of periodic backups every hour for gold tier virtual machines directly conflicts with the technical requirement of all backups must complete within the hours of 5 p.m. to 8 a.m. local time. This is because these two requirements are mutually exclusive, as hourly backups would need to run during the daytime as well as the nighttime, while the backup window only allows backups to run during the nighttime. Therefore, you need to get clarification from the customer on which requirement has priority and how to adjust the other one accordingly.

Answer : B

The additional information that is needed to define the implementation process later is how much backup data is stored on the old hardware. This information is important for designing and sizing the migration strategy and timeline for moving the backups from the old hardware to the new hardware. For example, you can use the amount of backup data to estimate how long it will take to copy or move the backups to the new storage devices. You can also use the amount of backup data to determine whether you need to use compression, deduplication, or WAN acceleration to optimize the migration traffic.

Answer : B, E

The information related to the virtual infrastructure that is missing and must be collected during the discovery are the total number of virtual machines and the size of the source data set. These are essential metrics for sizing the backup components, such as proxies, repositories, and transporters, as well as estimating the backup storage requirements and bandwidth consumption. The other options are either already provided in the scenario (recovery time objective, backup window) or not relevant for the Veeam solution (speed of Fibre Channel fabric).Reference:Veeam Certified Architect 2022 Exam Guide, page 10;Veeam Backup & Replication v11: Architecture and Design course, module 3.

Answer : B

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.

Answer : B

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.