Free Veeam VMCA2022 Practice Exam with Questions & Answers | Set: 2

•Veeam CDP is a technology that helps you protect mission-critical VMware virtual machines when data loss for seconds or minutes is unacceptable12.

•Veeam CDP leverages vSphere APIs for I/O filtering (VAIO) to constantly replicate I/O operations performed on VMs without creating snapshots12.

•Veeam CDP allows you to configure the RPO per second and achieve near-zero RPO, which means almost no data loss12.

•Veeam CDP also provides minimum recovery time objective (RTO) in case of a disaster, as CDP replicas are in a ready-to-start state1.

Veeam image-based replication is not the best option, as it relies on snapshots and has a higher RPO than CDP3. Custom PowerShell scripting is not a reliable or scalable solution, as it requires manual coding and maintenance. Veeam Backup Copy with immediate mode is not suitable for replication, as it is designed for copying backup files, not VM replicas4.

References: 1: Continuous Data Protection (CDP) - User Guide for VMware vSphere 2: Veeam v11: Continuous Data Protection (CDP) configuration 3: Replication - User Guide for VMware vSphere 4: Backup Copy Modes - User Guide for VMware vSphere

The component that will help the customer meet their stated objectives is to leverage Backup Enterprise Manager to allow end-users to restore files within their scope. Backup Enterprise Manager is a web-based interface that provides access to Veeam Backup & Replication functionality, such as backup, replication, and restore1. One of the customer’s business requirements is to develop a self-service portal and integrate it with the new backup solution. Backup Enterprise Manager can fulfill this requirement by enabling self-service file-level restores for end-users, as well as integration with help desk systems2. The other options are not related to the customer’s recovery requirements, as they are either not necessary (option A, as indexing and RBAC policies are optional features), not sufficient (option B, as deploying the console and setting RBAC policies do not enable self-service restores), or not native to Veeam software (option C, as the technical requirements state that Oracle backups must be managed by Veeam, not RMAN). References: Backup Enterprise Manager, Self-Service File Restore.

The tiers of Veeam Financial Services’ backups that will require SureBackup jobs are the silver and gold tiers. SureBackup jobs are used to verify the recoverability of backup files by running virtual machines from backups in an isolated environment and performing tests against live applications1. This feature is suitable for the silver and gold tiers, which have recovery time objectives of six hours and 30 minutes, respectively, and require backups to be verified. The bronze tier, which consists of development machines and field portables, has a recovery point target of seven days, with no recovery time target set, and does not require backup verification. Therefore, SureBackup jobs are not necessary for the bronze tier. Laptop backups are performed by Veeam Agent for Microsoft Windows, which does not support SureBackup jobs2. References: SureBackup, Veeam Agent for Microsoft Windows.

The additional information that is necessary for sizing the backup solution and must be gathered during further discovery are the amount of virtual machines to be protected and the total amount of production storage provisioned space. These metrics are used to calculate the backup storage requirements, the backup proxy and transporter resources, and the backup job configuration. The other options are either not relevant for sizing the backup solution (repository storage file system, replication schedule) or already provided in the scenario (the available bandwidth per site). References: Veeam Certified Architect 2022 Exam Guide, page 10; Veeam Backup & Replication v11: Architecture and Designcourse, module 3.

Reducing the recovery point objective (RPO) for silver tier workloads means that the backup frequency will increase, resulting in more backup data being generated and transferred. This will affect the sizing requirements of the Veeam components that are responsible for storing and processing the backup data, namely the Veeam repository and proxy roles1.

The Veeam repository is a storage location where the backup files are stored. The repository size depends on the amount of data to be backed up, the backup method, the retention policy, and the compression and deduplication settings2. Reducing the RPO will increase the amount of data to be backed up, and may require more frequent synthetic full backups or active full backups to maintain the retention policy. This will increase the repository size and the disk space consumption.

The Veeam proxy is a data mover that performs backup, replication, and restore tasks. The proxy size depends on the number of concurrent tasks, the transport mode, the backup method, and the compression and deduplication settings3. Reducing the RPO will increase the number of concurrent tasks and the amount of data to be processed by the proxy. This will increase the proxy size and the CPU and memory consumption.

You can find more information about the sizing requirements and best practices for the Veeam repository and proxy roles in the following resources:

• Veeam Backup & Replication Best Practices
• Veeam Backup Repository Sizing Calculator
• Veeam Proxy Sizing Calculator

The configuration that is unsupported by Veeam Plug-in for Oracle RMAN based on the technical requirements is physical windows server with Oracle. Veeam Plug-in for Oracle RMAN only supports Oracle databases running on Linux, Solaris, or AIX operating systems1. The other configurations are supported by either Veeam Plug-in for Oracle RMAN or Veeam Backup & Replication. References: Veeam Plug-in for Oracle RMAN, Oracle | Veeam Backup & Replication Best Practice Guide.

The requirement C will act as a constraint on the decision of whether to use a local repository or not for the remote sites. Data locality and privacy laws may vary by country or region, and may impose restrictions on where the backup data can be stored or transferred. For example, some countries may prohibit the export of personal data outside their borders, or require encryption or anonymization of sensitive data. Therefore, the Veeam solution must comply with these laws and regulations, and may need to use a local repository for each remote site, or use a cloud provider that has a local presence in each region. The other requirements are not constraints, as they can be met with either a local or a central repository, using the features and options of the Veeam solution. References: Veeam Certified Architect 2022 Exam Guide, page 11; Veeam Backup & Replication v11: Architecture and Design course, module 5.

The things that can be done to validate that the design meets target SLAs and reduces the headcount required to manage the solution are:

• Use tagging and scripts to auto-generate backup jobs, set the start time and windows, letting the backup server manage resource allocation. This option allows to automate the backup job creation and configuration, based on the tags assigned to the source objects, such as VMs, hosts, or clusters1. This reduces the manual effort and human error involved in managing the backup jobs, and ensures that the backup server allocates the optimal resources for each job, based on the load balancing and performance settings2.
• Explain how to detect configuration changes, reporting and using backup job templates to maintain consistency. Document self-service restore the streamline service desk engagement. This option allows to monitor the backup infrastructure and detect any changes that may affect the backup performance or reliability, such as adding or removing VMs, hosts, or clusters3. It also allows to use backup job templates to create consistent and standardized backup policies, and apply them to multiple backup jobs4. Additionally, it allows to document the self-service restore process, which enables end-users to perform file-level restores from their own backups, without involving the backup administrator or the service desk5.
• Review the design so that the slowest part of the infrastructure is fast enough to meet backup window requirements. This option allows to identify and optimize the bottleneck in the backup infrastructure, which is the component that limits the backup speed and throughput. By reviewing the design and ensuring that the slowest part of the infrastructure can meet the backup window requirements, the backup SLAs can be achieved and the backup performance can be improved.

The other options are either not relevant for validating the design (option A and E, as exporting the configuration, scheduling a review, and reviewing the design for bottlenecks are part of the design process, not the validation process) or not effective for meeting the SLAs and reducing the headcount (option C, as using inventory information, backup chaining, and fine tuning are manual and complex tasks that may not guarantee the backup window compliance or resource efficiency). References: Tagging, Load Balancing and Performance, Configuration Change Tracking, Backup Job Templates, Self-Service File Restore, [Bottleneck Statistics]

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.

The information that is still needed for a complete architectural design is how often backups are required for silver machines. This is not stated in the technical requirements, where only the recovery time objective and recovery point objective are given for the silver tier. The backup frequency affects the backup storage consumption, the backup window, and the restore point granularity. The other options are either already provided in the technical requirements (daily backup retention, amount of time required for a successful restore for gold machine) or not relevant for the architectural design (RMAN configuration guidelines). References: Veeam Certified Architect 2022 Exam Guide, page 10; Veeam Backup & Replication v11: Architecture and Design course, module 4.