Free Veeam Certified Engineer Plus (VMCE+) practice test: 30 questions with answers

Backup proxies do the data-movement work, and direct storage access reads VM disks from shared storage without sending them over the production network. A second backup server does not take over the processing, a replica job creates a standby VM rather than a backup, and tape is a media target that does not offload source reads.

A hardened Linux repository provides immutability through a locked-down Linux system and single-use credentials, so a stolen standing account cannot delete the backup files. A standing administrator account on a Windows share can delete backups, an NFS export on the hypervisors exposes the repository to production hosts, and versioning without object lock still lets a holder of the credentials delete protected versions.

GFS retention keeps selected weekly, monthly, and yearly restore points for longer than the regular retention, which matches a long-term offsite requirement. A daily synthetic full schedule or active full backups change how full backups are built but do not define long-term retention, and immutability on the source repository does not create an offsite copy.

Instant VM recovery starts the VM directly from the backup file and later migrates its disks to production storage without copying all data first. A full VM restore copies everything before the VM can start, a virtual disk restore only returns disks, and replica failover needs an existing replica rather than a backup file.

Veeam Explorers are built to restore application items, such as SQL Server databases, from a backup without a full VM restore. Copying raw backup files does not give a usable database, replica failover does not use the backup chain, and SureBackup verifies recoverability in a lab rather than restoring data to production.

Application-aware processing uses the guest operating system's VSS writers, so Veeam needs credentials with rights inside the VM to coordinate them. A hardened repository, a tape copy, or a replica is not a requirement for application-consistent backups of a VM.

A backup copy job creates an extra copy of restore points in another location, and it keeps its own retention settings separate from the source job. It does not delete source restore points, it is not limited to one backup mode, and it is not tied to replica failover.

SureBackup boots restore points in an isolated virtual lab and runs verification tests such as heartbeat, ping, or application checks. A health check examines backup files for corruption but does not boot the VM, a tape copy adds a copy without testing it, and a replica job creates a standby VM rather than verifying restore points.

The 3-2-1 rule calls for three copies of data on two different media types, with one copy kept offsite. The other options list backup components or counts that do not describe the rule.

Encrypted backup files need their encryption password to be decrypted, so losing it means those backups cannot be restored. Reinstalling the backup server or waiting for retention to expire does not decrypt existing files, and Veeam does not offer a way to recover the password for you.

A Veeam ONE alarm watches a metric such as datastore free space and triggers when it crosses a threshold, which gives early warning. A monthly report is produced after the fact, a Business View category organizes objects but does not alert, and SureBackup verifies restore points rather than monitoring datastore capacity.

Veeam ONE Monitor provides real-time monitoring and alarms across virtual and backup infrastructure. Veeam ONE Reporter produces reports from collected data, Business View groups infrastructure objects into categories, and Veeam Explorer for Microsoft Exchange restores mailbox items rather than monitoring anything.

Veeam ONE Reporter includes capacity planning and forecasting reports that project growth trends to estimate when capacity runs out. A live alarm shows the present state, a SureBackup session summary covers restore testing, and a Business View category groups objects without predicting growth.

Business View lets administrators group infrastructure objects into categories built from their attributes, so reports and views can cover one customer across clusters. Separate servers add overhead without grouping objects, replica seeding moves data for replicas, and a hardened repository is storage with immutability rather than a grouping feature.

Veeam ONE stores collected metrics in its database, so administrators can look back at past periods in charts and reports. A live dashboard shows only current values, a proxy job log covers backup activity rather than VM performance, and a SureBackup report describes restore verification.

Veeam ONE monitors Veeam Backup & Replication servers and their jobs, and it keeps historical data in its database that reports use. It does not move backup data, it does not need a hardened repository, and it does not perform failover.

A single Veeam ONE deployment can connect to several vCenter Server instances and report across them. The other statements are wrong: one server per vCenter is not required, Veeam ONE is not limited to a local vCenter, and it supports VMware as well as Hyper-V.

Veeam ONE Reporter can schedule reports so they are generated and delivered automatically on a set cadence. A pre-job script runs around backup activity rather than producing management reports, SureBackup reports on restore verification, and Business View categories group objects without sending mail.

A backup coverage report in Veeam ONE Reporter shows which VMs lack recent protection, which fits a gap review. A host CPU alarm tracks performance rather than backup coverage, a SureBackup session tests restores that already exist, and a Business View category groups objects without checking their backup status.

An alarm that triggers on a backup job failure gives immediate notification as the condition occurs. A monthly summary arrives too late, a Business View category groups objects without alerting, and a SureBackup job tests restore points rather than watching job status.

A scale-out backup repository can grow by adding extents, so existing jobs keep pointing at the same logical repository. Creating per-VM jobs, converting jobs to copy jobs, or changing transport modes does not add storage capacity to the repository.

A scale-out backup repository combines one or more extents into one logical repository, which can be extended with capacity or archive tiers. A single NFS export is an ordinary repository rather than a scale-out design, a replica seed file is unrelated to repository design, and one tape drive does not describe scale-out storage.

Scripting with the Veeam PowerShell module or REST API lets the team define settings once and apply them consistently. Direct edits to the configuration database are unsupported and risky, and hand-typing settings or cloning jobs in the console repeats manual steps that invite inconsistencies.

A recovery plan in Veeam Orchestrator sequences the steps that bring systems back, can be tested without disturbing production, and produces documentation for audits. Job schedules, encryption keys, and proxy CPU limits are managed elsewhere and do not describe a recovery plan.

Veeam Orchestrator can test a recovery plan in an isolated network, so the recovery steps are verified without affecting production workloads. A planned failover moves production workloads, disabling replicas stops protection without testing anything, and restoring onto the production datastore risks the live systems.

Least privilege limits the account to the rights needed for backup and restore, so a compromised account can do less damage. Single sign-on, shared credentials, and broad hypervisor rights do not reduce that exposure, and shared or broad rights increase it.

Job creation and restore point queries are standard scripting tasks, so the Veeam PowerShell module and REST API cover them. Manual registry edits, hypervisor firmware upgrades, and hypervisor license changes are outside Veeam's job automation scope.

WAN accelerators at both sites reduce the amount of data sent across the WAN link when a backup copy job transfers restore points. Network transport mode and an extra repository in the same site do not reduce WAN traffic, and turning on replication sends VM changes across the same link.

Secure restore scans restore points with antivirus before they are restored, which helps avoid bringing malware back into production. Instant VM recovery is focused on a fast restart rather than malware scanning, a health check checks file integrity and does not detect malware, and GFS retention controls how long restore points are kept.

The operational restore window keeps recent restore points on the performance tier for fast restores, and older data is offloaded to the capacity tier. The number of VMs per proxy, the transport mode, and the tape media pool size do not control when offload happens.