VMCE Repository and Storage Management 3 — Questions and Answers
Question 1: Which Veeam feature automatically moves older restore points from the performance tier to a lower-cost capacity tier in a Scale-out Backup Repository?
- Backup Copy offload
- Capacity Tier offload policy (Correct answer)
- Archive Tier policy
- GFS retention policy
Correct answer: Capacity Tier offload policy
The capacity tier offload policy in a SOBR automatically moves backup files that exceed a defined age threshold from performance-tier extents to object storage.
Question 2: When using a Veeam hardened Linux repository, which authentication method is required to ensure immutability cannot be bypassed even by privileged Veeam accounts?
- Certificate-based SSH authentication with a root account
- Single-use credentials added during repository setup that are immediately discarded (Correct answer)
- Kerberos authentication with an Active Directory service account
- API key authentication stored in the Veeam configuration database
Correct answer: Single-use credentials added during repository setup that are immediately discarded
Veeam uses single-use credentials during the initial hardened repository setup; after configuration, those credentials are discarded so no persistent privileged access remains.
Question 3: What is the effect of enabling per-VM backup chains on a repository that stores backups from a VMware vSphere job protecting multiple VMs?
- Each VM's backup data is stored in a separate set of backup files, allowing independent retention and restore (Correct answer)
- All VMs share a single VBK file to reduce metadata overhead and improve deduplication
- Per-VM chains automatically enable application-aware processing for all VMs in the job
- Per-VM chains force incremental-forever backup mode regardless of job schedule settings
Correct answer: Each VM's backup data is stored in a separate set of backup files, allowing independent retention and restore
Per-VM backup chains store each virtual machine's data independently, enabling granular retention control and allowing individual VMs to be removed from a job without affecting others.
Question 4: Which object storage provider integration in Veeam supports the S3 Object Lock feature for WORM (write-once-read-many) immutability?
- Amazon S3 and S3-compatible storage that implements the S3 Object Lock API (Correct answer)
- Microsoft Azure Blob Storage using access tiers only
- Wasabi Hot Cloud Storage via proprietary locking APIs
- Google Cloud Storage through lifecycle management rules exclusively
Correct answer: Amazon S3 and S3-compatible storage that implements the S3 Object Lock API
Veeam supports S3 Object Lock for immutability on Amazon S3 and any S3-compatible object storage that correctly implements the S3 Object Lock API.
Question 5: In a Veeam Scale-out Backup Repository, what policy controls how new backup files are distributed across multiple extents?
- Data locality policy and performance policy
- Round-robin and least-used extent policies (Correct answer)
- Active full and synthetic full rotation policies
- Capacity and archive tier placement policies
Correct answer: Round-robin and least-used extent policies
SOBR uses a data locality policy (keeping all files for a VM on the same extent) or a performance policy (writing to the extent with the most free space or least load).
Question 6: What happens when a Veeam backup repository runs out of free space during an active backup job?
- Veeam pauses the job and waits up to 24 hours for space to be freed before failing
- The job fails with an insufficient space error and the incomplete backup file is deleted (Correct answer)
- Veeam automatically removes the oldest restore point from that repository to free space
- The job completes partially and marks the backup chain as corrupted
Correct answer: The job fails with an insufficient space error and the incomplete backup file is deleted
When a repository exhausts its free space mid-job, the job fails with an error and Veeam removes the incomplete backup file to avoid leaving a corrupt chain.
Question 7: Which Veeam repository configuration option should be enabled to optimize performance when writing backups to a Dell EMC Data Domain appliance?
- Enable vPower NFS datastore on this repository
- Use per-VM backup chains
- Enable DDBoost integration for this repository (Correct answer)
- Decompress backup data blocks before storing
Correct answer: Enable DDBoost integration for this repository
Enabling Dell EMC DDBoost allows Veeam to use the DDBoost library for faster, deduplicated data transfer directly to Data Domain, offloading processing to the appliance.
Which Veeam feature automatically moves older restore points from the performance tier to a lower-cost capacity tier in a Scale-out Backup Repository?