Download the Latest VMCA2022 Dumps – 2023 VMCA2022 Exam Questions [Q29-Q50]

Explanation
The transport modes that could be used during the redesign for gold tier virtual machines with a one-hour RPO are Virtual Appliance (HotAdd) and Backup from Storage Snapshots. A transport mode is a method of retrieving VM data from the source storage during backup or replication. Virtual Appliance (HotAdd) is a transport mode that allows a proxy server running on a VM to attach disks of another VM to itself via hot-add SCSI commands and read data directly from these disks. Backup from Storage Snapshots is a transport mode that allows a proxy server to retrieve data from storage snapshots created by supported storage systems without affecting the production VMs or hosts. Both transport modes can improve backup performance, reduce backup window, and minimize impact on the production environment.

Explanation
To design a solution that meets the needs and requirements of Veeam University Hospital, you need to conduct a thorough analysis on the areas mentioned in the case study. This 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 areas that would benefit from additional analysis are:
*NAS. This area would benefit from additional analysis because NAS systems are used to store confidential patient data as unstructured data, which need to be backed up consistently and securely. You need to collect more information about the characteristics and performance of the NAS systems, such as the size and type of data, the number and distribution of files, the largest file size, the version of SMB protocol, the deduplication and compression ratios, etc. This will help you to design a solution that can meet the backup and recovery objectives, as well as the regulatory and security requirements, for the NAS data.
*PostgreSQL. This area would benefit from additional analysis because PostgreSQL databases are used by some of the departments, with a mix of virtual and physical deployments. You need to collect more information about the configuration and performance of the PostgreSQL databases, such as the version and edition, the operating system and platform, the backup and restore methods and tools, the consistency and integrity requirements, etc. This will help you to design a solution that can support and integrate with PostgreSQL databases, as well as provide consistent and reliable backups and restores.
*OneDrive. This area would benefit from additional analysis because OneDrive is used by all doctor and lab staff to store their user data on their laptops, which also need to be backed up. You need to collect more information about the usage and performance of OneDrive, such as the number and size of files, the synchronization frequency and settings, the authentication and authorization methods, etc. This will help you to design a solution that can protect and recover OneDrive data, as well as exclude any operating system or personal files from backup.
Topic 2, Veeam Life and Indemnity
Executive Summary:
Veeam Life and Indemnity is expanding its existing Veeam backup infrastructure to protect additional virtual machines, physical server and NAS workloads at their Fresno, CA and Carson City, NY data centers.
The original installation and configuration of Veeam software occurred two years ago. Since the installation, the organization has grown, and as a result, the Veeam Infrastructure needs to be resized to accommodate the existing and new workloads.
For the past three months, Veeam Life and Indemnity has noticed that they are having issues with backups completing within the allotted backup window. Only 40% of backup jobs complete successfully, so they have broken the backups into two sets, and they run them on alternating days. They have also stopped all backups for their development environment.
In addition, the original configuration required a daily backup copy job, but to the issue with backups completing, this has been modified to run only on Sundays.
They have also noticed a degradation in storage performance and are having to purchase new storage on a quarterly basis to accommodate data growth.
Solution Concept:
Veeam Life and Indemnity is upgrading Veeam Backup & Replication to the last version. They are also replacing all legacy physical hardware and storage with current generation equipment. Veeam Life and Indemnity wants to be able to ensure that all backups, including production and dev test workloads, can run every night and that all backups complete within the required backup window. In addition, Veeam Life and Indemnity would like to run daily copy jobs to ensure that a copy of all backed up data resides at both physical sites.
Veeam Life and Indemnity has also expressed concern about the threat of ransomware. They have not experienced a data breach of any kind but would like to ensure the ability of recover should one occur.
Existing Technical Environment:
Veeam Life and Indemnity has VMware clusters in all locations. These clusters are broken into two categories:
general use virtual workloads, and application specific workloads, such as MSSQL and Oracle.
All customer data is subject to government regulation and must be kept secure at all times.
Veeam Life and Indemnity has a proprietary CRM system that must be quiesced prior to backup.
All email is hosted in Office 365.
All database servers are virtualized.
All virtual machines are categorized as either gold, silver, or bronze, with different service-level agreements based on tier.
All backups currently encrypted in flight and at rest.
Internet connectivity at both sites is current 1 Gbps, with plans to increase to 2 Gbps soon.
All field sales reps are assigned a company laptop that runs a CRM client.
The LAN at each location supports up to 40 Gbps bandwidth.
All backups are currently written to Scaled-out Backup Repositories with each extent residing on a CIFS share.
Each department has its own vLAN, with a total of 30 vLANs for production traffic.
A single management vLAN is stretched between sites.
All unstructured data resides either on 10 NFS shares on the company’s incumbent NAS devices, or Windows file servers as file shares.
VMware uses vSAN for VM datastores.
All vLAN must traverse a firewall to communicate, and the backup network itself is no routable.
All network traffic between clusters is required to traverse a firewall.
The firewall devices can support up to 20 Gbps.
Business Requirements:
Due to limited manpower, all backups should be dynamically scope.
All backups must be copied across site outside of the current backup window to avoid any backup performance issues.
Due to the sensitivity of customer data, tier 1 helpdesk personnel must not be able to access these backups.
They should have access to restore non-customer data.
Backup administrators are subject toa rigorous background check and should be the only staff able to perform restores of confidential customer data.
For any legal issues, fast and timely discovery from backup data should be supported.
For security purposes, all storage should be hardened to prevent data breaches.
Remote sales staff should have the ability to start a backup oh their devices.
Due to regulatory requirements, audits must be performed periodically to ensure successful and consistent backups, as well adherence to security policies.
Technical Requirements:
All backups must complete within the hours of 5 p.m. to 8 a.m. local time Backup copy jobs must successfully complete daily outside of the backup window.
Gold tier virtual machines have a recovery point objective of the one hour for image backup, and 15 minutes for traction log backup, with a recovery time objective of four hours.
Silver tier virtual machines have a recovery point objective of 24 hours, with a recovery time objective of eight hours.
Bronze tier virtual machines have a recovery point objective of seven days, with no defined recovery time objective.
NAS devices and file servers have a recovery point objective of four hours, with no specified recovery time objective.
Eight weekly backup, three monthly backups, and seven yearly backups should be retained for regulatory requirements.
All data must be encrypted in flight and rest.
Alternative decryption capabilities on encrypted backups must be possible in the event of lost passwords.
Role Based Access Control must be used to prevent unauthorized access to backup data.
New storage must be hardened to prevent intrusion, and if possible, the data written must be unchangeable to prevent ransomware attacks.
All backups must be scanned prior to any restore operations for malware.
All gold level systems must have a custom script run before restore to ensure compliance to specific legal statutes.
Gold tier backups must be tested to verify recoverability.
Only silver tier systems should be indexed during backups, with the exception of laptops belonging to the sales field.
All personal files on laptops should be excluded from backup
All MSSQL server backups should exclude the H: drive.

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]

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]

Explanation
To design a solution that meets the needs and requirements of Veeam University Hospital, you need to gather some 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 Veeam Backup & Replication Best Practice Guide1, some of the information that is necessary for designing a solution and must be gathered during discovery are:
*Operating systems used to run the workloads. This information will help you to determine the compatibility and supportability of the workloads with Veeam products and features, as well as the licensing and configuration requirements.
*Allowed backup windows. This information will help you to plan and schedule the backup jobs according to the availability and performance of the workloads, as well as the service level agreements (SLAs) and recovery point objectives (RPOs) of the organization.
*Amount of used disk space. This information will help you to estimate the backup storage requirements, as well as the backup compression and deduplication ratios, based on the type and size of the data.

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]

Explanation
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, youcan disable data encryption or use the encryption feature on the deduplicating appliance itself1

Explanation
The component that can help meet the requirement of alternative decryption capabilities on encrypted backups in the event of lost passwords is Veeam Backup Enterprise Manager. Veeam Backup Enterprise Manager is a web-based interface that allows centralized management of multiple Veeam backup servers. It also provides a password loss protection feature that enables authorized users to restore encrypted backups without entering passwords if they forget or lose them. This feature requires enabling password loss protection in Veeam Backup Enterprise Manager settings and assigning a security officer role to a user who can approve password recovery requests.
References: [Veeam Backup Enterprise Manager], [Password Loss Protection]

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.

Explanation
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.

Explanation
If the repositories are able to accomplish much higher throughput, a new issue that might come up is that the bandwidth between sites might not be sufficient to support the backup copy jobs that need to run daily between Fresno and Carson City. This could cause the backup copy jobs to fail, take longer than expected, or consume too much network resources. Therefore, it is important to measure the available bandwidth between the sites and compare it with the backup copy data size and window. If the bandwidth is not sufficient, some possible solutions are to use compression, deduplication, or WAN acceleration to reduce the backup copy traffic.

Explanation
To design a solution that meets the backup and replication requirements for Veeam University Hospital, you need to consider some of the components that are needed for the on-premises design. This will help you to ensure the performance and reliability of the backup and replication operations, as well as the scalability and manageability of the backup infrastructure.
According to the Veeam Backup & Replication Best Practice Guide1, some of the components that are needed for the on-premises design are:
*Backup server. This is the core component of Veeam Backup & Replication that controls and coordinates backups, replication, recovery verification, and restore tasks. It also manages backup infrastructure components, such as proxy servers, repository servers, WAN accelerators, etc. You need to have a backup server at each site, as recommended by the best practice guide2.
*Backup proxy. This is a component that retrieves data from the source host, processes it and transfers to the backup repository. It also performs data compression, deduplication, encryption, etc. You need to have at least one backup proxy at each site, as recommended by the best practice guide3.
*Backup repository. This is a server where Veeam Backup & Replication keeps backup files, backup copies and metadata of replicated VMs. It can be a Windows or Linux server, a NAS device, a deduplication appliance, etc. You need to have at least one backup repository at each site, as recommended by the best practice guide4.
*Mount server. This is a component that mounts backup files from the backup repository to the backup proxy during restore operations. It also performs data decompression, deduplication, decryption, etc. You need to have a mount server at each site where you plan to perform restores, as recommended by the best practice guide5.
*Gateway server. This is a component that acts as a data mover between the backup proxy and the backup repository when they are located in different sites or networks. It also performs data encryption and decryption for secure data transfer. You need to have a gateway server at each site where you have a backup repository that is accessed by a remote backup proxy, as recommended by the best practice guide.
Therefore, based on these components, the answer that describes which components are needed for the on-premises design is D. Backup server, backup proxy, backup repository, mount server, gateway server.

Explanation
*Virtual machine backup jobs with log shipping enabled allow you to create image-level backups of SQL Server databases and also back up the transaction logs periodically12.
*Scale-out Backup Repository is a logical entity that groups several backup repositories into a single pool of storage, allowing for better backup performance, scalability, and management3.
*Scale-out Backup Repository capacity tier is a feature that allows you to offload older backup files to a public cloud object storage, such as Amazon S3 or Azure Blob Storage .
The other options are not as effective or efficient, as they either do not use Veeam features, do not offload to object storage, or do not create image-level backups.
References: 1: Transaction Log Shipping – User Guide for VMware vSphere 2: How to Back Up SQL Server Transaction Logs – Veeam 3: Scale-Out Backup Repository – Veeam Backup & Replication Best Practice Guide : Capacity Tier – User Guide for VMware vSphere : How to Use Capacity Tier in Veeam – Veeam

Explanation
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.

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 tocross the WAN or VPN connections between sites.
Topic 1, Veeam University Hospital
Executive Overview:
Veeam University Hospital is a healthcare network with located is Boston, Salt Lake City and Columbus.
They are considered a pioneer in breakthrough treatments to many illnesses and recognized worldwide as a leader in their field. They have decided to modernize their data protection strategy due to new regulatory requirements as well as ever evolving malware issues. They suffereda ransomware attack recently as well, which affected several systems with patient treatment.
Furthermore, they have expressed interest in replication of virtual workloads between sites in case of a disaster to allow for timely failover between sites with would ensure continuity in the level of patient care offered.
Their board of directors is concerned that all virtual workloads at this point can be considered a single point of failure.
Veeam University Hospital has also been experiencing issues with the time required to back up NAS systems.
Not only are they taking too long, the amount of space required is considered excessive, and a reduction of storage space for these backups is desired.
Veeam University Hospital had issues with the time required to restore Exchange items. The current solution will only restore entire mailboxes, and no granularity is possible.
For this implementation to be successful, backups must complete in the allotted backup window, and the recovery of data should be faster than the current solution, which can amount to 24 to 48 hours for a full system restore.
Solution Concept:
Veeam University Hospital is replacing their current backup solution Veeam. They plan to protect data at all three sites, with backups copied off-site for disaster recovery purposes. They have also expressed an interest in taking action to prevent another data lost due to ransomware. The offenders were also able to encrypt the existing backups as part of the attack, so data recovery is impossible. Veeam University Hospital is also interested in any posible public cloud technologies that might help mitigate this risk.
In addition, replication of running workloads to secondary sites will also be implemented to allow for site failover in the event of a disaster for reduced down time.
Existing Technical Environment:
Veeam University Hospital has VMware cluster in all locations. For security purposes, each cluster is dedicated to the department that it servers. No communication between cluster is possible. These cluster are broken into two categories, one hosting database workloads and the other hosting general use virtual machines.
Confidential patient data exists on several NAS systems as unstructured data. These NAS systems are only presenting backups to ensure consistency of the database.
Veeam University Hospital has an in-house patient database required a custom script to be execute before backups to ensure consistency of the database.
MSSQL and Oracle are used by most of the departments, with a mix of virtual and physical deployments.
Each site as a 10 GbE link to the public internet, and all traffic between sites is routed through these connections via VPN.
Each site has 20 vLANs in use, with 16 being used for VMware workloads.
For security and regulatory purposes, all vLANs are firewalled off from each other.
The current backups write to NFS storage.
All doctor and lab staff are assigned their laptops, which will also need to be protected. The location of data on these devices is enforced through group policy, and consistent throughout the organization.
No current disaster recovery solution, apart from restoring from backup files, exists at this time.
Business Requirements:
Any new solution must take advantage of automation and self-service functionality. Both features are needed to cut down on administrative costs. Role based access (RBAC) is mandatory. Forexample, only Oracle administrators can have the ability to perform self-service restore of Oracle Data.
Mission critical applications must not be impacted during business hours. All backups must complete between
6 p.m. and 8 a.m. local time.
To meet regulatory requirements all data must be retained for three years.
For archival purposes, 12 monthly backups and three yearly backups must be stored offsite.
Veeam University Hospital will only purchase on-premises storage to accommodate growth for three years of backup retention.
For any replicated virtual workloads, the data must not more than one hour old.
Due regulatory requirements, all protected data must be encrypted in flight and rest.
To meet customer service-level agreements, a commercially available helpdesk ticketing system is in use. All alerts generated must be integrated with this system to create support tickets.
Technical requirements:
Backups must take advantage of public cloud storage for long term archival purposes.
The solution must keep a local backup and be able to create an additional copy of production data. Both backups should reside on site with production systems being protected.
For quick restores and recovery, at least copy of protected data must reside on-premises.
Due to the threat of ransomware, at least one immutable or air gapped copy of protected data must reside off-side.
To ensure data integrity, backups must be verified and scanned for malware before any restore Is performed.
In addition to Self-service Oracle restores, native Oracle tools must be available and PowerShell script ready to perform ad-hoc backups and restores.
The backup solution must support VMware encrypted datastores.
Backups must be stored in logical scalable storage systems that can be expanded non-disruptively.
For end user laptop backups, only user data should be backed up. Operating system files should be excluded.
Personal files such as music, photos, and videos must be excluded for backup.

Explanation
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.
References: [Migrating Backup Files], [WAN Acceleration]

Explanation
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 assignedto 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.

Explanation
Thank you for your question. I’m glad to help you with your VMCA 2022 project.
To design a solution that meets the database requirements for Veeam University Hospital, you need to consider some of the options and features that can support and integrate with Oracle databases. This will help you to ensure the consistency and reliability of the Oracle backups and restores, as well as the compatibility and supportability of the native Oracle tools with Veeam products and features.
According to the Veeam Backup & Replication Best Practice Guide, the option that most closely matches the requirements of having native Oracle utilities available for backups and restores is D. Install the Veeam RMAN Plug-in to allow native RMAN backups and restores to leverage Veeam repository directly from the Oracle servers.
This option means that:
*The Veeam RMAN Plug-in is a solution that integrates with Oracle Recovery Manager (RMAN) and allows you to back up and restore Oracle databases using Veeam repositories as targets.
*The Veeam RMAN Plug-in supports both virtual and physical Oracle servers, as well as different versions and editions of Oracle databases.
*The Veeam RMAN Plug-in enables you to use native Oracle tools and commands, such as RMAN, SQL*Plus, Data Pump, etc., to perform backups and restores of Oracle databases, without requiring any additional scripts or configurations.
*The Veeam RMAN Plug-in leverages the benefits and features of Veeam Backup & Replication, such as backup compression, deduplication, encryption, immutability, etc., to improve the backup performance and efficiency, as well as the backup security and integrity.
This option is the best match for the requirements, as it allows you to use native Oracle utilities for backups and restores, while also taking advantage of Veeam products and features.

Explanation
The recommended method to replicate VMware virtual machines with a less than five-minute RPO is Veeam Continuous Data Protection (CDP). CDP is a feature that allows near-continuous replication of VMware virtual machines to a secondary site or cluster with minimal data loss and downtime. CDP uses VMware vSphere APIs for I/O Filtering (VAIO) to capture every write operation from the source VMs and send them to the target VMs in near real-time. CDP can achieve RPOs as low as seconds and enable fast failover and failback in case of a disaster.

Explanation
Thank you for your question. I’m glad to help you with your VMCA 2022 project.
To design a solution that meets the needs and requirements of Veeam University Hospital, you need to consider the impact and benefit of adding extra proxy servers to your backup infrastructure. This will help you to optimize the performance and efficiency of your backup and restore operations, as well as to prepare for future growth and expansion.
According to the web search results, a proxy server is a component that retrieves data from the source host, processes it and transfers to the backup repository. It also performs data compression, deduplication, encryption, etc. You can deploy backup proxies both in the primary site and in remote sites1.
The immediate result of adding the extra proxy server is A. The time for backup to complete could be reduced.
This result means that:
*The time for backup to complete is a metric that measures how long it takes to perform a backup job from start to finish. It depends on various factors, such as the size and type of data, the backup method and frequency, the network bandwidth and latency, etc.
*Adding an extra proxy server can reduce the time for backup to complete, by distributing the backup workload between available proxy servers. This can improve the backup performance and efficiency, as well as reduce the impact on the production environment.
*Reducing the time for backup to complete can also help you to meet your backup window and recovery point objective (RPO) requirements, as well as to free up more resources for other tasks or jobs.

Explanation
To design a solution that meets the database requirements for Veeam University Hospital, you need to consider some of the assumptions and implications of using the script for the in-house database. This will help you to ensure the consistency and reliability of the database backups and restores, as well as the compatibility and supportability of the script with Veeam products and features.
According to the Veeam Backup & Replication Best Practice Guide, one of the assumptions that using the script for the in-house database presents is C. The script already exists and is solely managed by the customer.
This assumption means that:
*The script is not provided or maintained by Veeam, but by the customer or a third-party vendor. Therefore, Veeam is not responsible for the functionality or quality of the script, nor for any issues or errors that may arise from using it.
*The script is already tested and verified by the customer or a third-party vendor. Therefore, Veeam does not need to validate or certify the script, nor to provide any documentation or guidance on how to use it.
*The script is already integrated and configured with the in-house database. Therefore, Veeam does not need to modify or customize the script, nor to provide any support or troubleshooting for it.
This assumption has some implications for designing a solution with Veeam products and features, such as:
*The customer or a third-party vendor must ensure that the script is compatible and compliant with the latest versions and updates of Veeam Backup & Replication, as well as with the in-house database.
*The customer or a third-party vendor must provide Veeam with the necessary information and access to run the script before and after the backup or restore operations, such as the script location, parameters, credentials, etc.
*The customer or a third-party vendor must monitor and manage the script performance and results, as well as handle any exceptions or failures that may occur during or after the backup orrestore operations.

Explanation
To design a solution that meets the offsite copies and archives requirements for Veeam University Hospital, you need to clarify some of the assumptions and expectations of the customer. This will help you to avoid any misunderstandings or conflicts that may arise during the implementation or operation of the solution.
According to the Veeam Backup & Replication Best Practice Guide, offsite copies and archives are two different concepts that serve different purposes. Offsite copies are backups that are stored in a different location than the primary backup storage, and are used for disaster recovery purposes. Archives are backups that are stored for a longer retention period than the regular backups, and are used for compliance or historical purposes.
Based on these definitions, the requirement that needs additional information to help clarify the customer expectation is C. Backups must take advantage of public cloud storage for long term archival purposes.