A backup engineer is reviewing policy-related settings in a Recovery Services vault. Match each backup setting to the behavior it controls.
Drag a concept onto its matching description — or click a concept then click the description.
Determines when the VM backup job runs, such as daily at a specific time.
Determines how long a recovery point is kept before it expires.
Keeps short-term snapshots available for quick restores before they age out.
Preserves deleted backup data for a recovery window instead of removing it immediately.
Represents the protected VM that is registered in the vault.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Backup frequency: How often backups are performed (e.g., daily, weekly).
Backup frequency sets how often; retention range sets how long; snapshot retention keeps local copy; schedule sets time; tier defines storage type; alerts notify on issues.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Backup frequency: How often backups are performed (e.g., daily, weekly).
Why this is correct
Backup frequency defines the recurring interval at which backup jobs are initiated, such as every 24 hours or every 7 days. In Azure Backup, this setting is configured in the backup policy and determines how many restore points are created over a given period based on the chosen schedule. A shorter frequency means more frequent recovery points and a lower recovery point objective (RPO), but it also increases storage consumption and associated costs. It is distinct from the backup schedule, which specifies the exact clock time at which those frequency-based jobs run.
Retention range: How long backups are retained (e.g., 30 days).
Why this is correct
Retention range specifies the maximum duration, usually expressed in days, months, or years, that backup data is preserved before it is automatically purged. Azure Backup retention rules are defined per backup point type (daily, weekly, monthly, yearly) using a tiered or grandfather-father-son scheme. This setting directly controls storage costs and compliance obligations, because longer retention increases the total amount of backup data stored. Retention differs from frequency in that a policy can run daily backups but keep those backups for only 30 days, or retain daily backups for years.
Snapshot retention: How long local snapshots are kept (e.g., for Azure VM backup).
Why this is correct
Snapshot retention refers specifically to the duration that crash-consistent local snapshots are maintained on the source disk or within the same region before they are transferred to the Recovery Services vault. In Azure VM backup, an initial snapshot is taken and kept for the configured snapshot retention (typically 1-5 days) to enable fast restoration without relying on vault data. This setting is important for rapid recovery and is independent of the longer-term vault retention used for completed backup jobs. It also has cost implications because snapshots occupy storage on the source side.
Backup schedule: Time at which backups are initiated (e.g., 2:00 AM).
Why this is correct
Backup schedule defines the exact time of day (and optionally day of week or month) when the backup job is triggered, for example daily at 2:00 AM. While backup frequency sets the recurrence interval, the schedule determines when those recurring runs start, affecting operational impact and the timing of restore points. For production workloads, the schedule is often chosen during off-peak hours to minimize I/O contention and performance degradation. In Azure Backup, the schedule is part of a backup policy and can also be used to meet time-of-day compliance requirements, such as a legal mandate to create a nightly backup.
Backup frequency: How long backups are retained.
Why it's wrong here
This is incorrect because backup frequency is about the cadence of backup jobs, not the duration data are kept. Retention is the concept that determines how long backup copies are stored, often expressed in days, months, or years. Confusing the two would lead an administrator to believe that setting frequency to 'daily' means data is kept for one day, when in fact daily just means a backup is run every 24 hours. This mix-up can cause misconfigured policies, unexpected data loss (if retention is set too short), or excessive storage costs.
Snapshot retention: How often backups are taken.
Why it's wrong here
This is incorrect because snapshot retention is a duration setting, not a frequency interval. How often backups are taken clearly refers to backup frequency, such as hourly, daily, or weekly. Snapshot retention instead controls how long a local snapshot remains available before it is aged out or transferred to the vault. Mislabeling this relationship could cause an operator to extend snapshot retention to improve RPO, which actually does nothing to change backup cadence; instead, you would need to adjust the backup schedule or frequency.
Go deeper
Learn chapter
Customer-Managed Keys (CMK) for Storage Encryption
Key term
Policy
A policy is a set of rules or guidelines that defines how an organization manages, secures, and operates its IT systems and services.
Key term
Recovery Services vault
A Recovery Services vault is a secure storage container in Microsoft Azure that holds backup data and replication settings for virtual machines, databases, and other cloud resources, enabling you to restore them if something goes wrong.
About these practice questions
This AZ-104 question is part of Courseiva's 1,049-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-104 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-104 exam.