Microsoft AZ-104 Exam Dumps, Practice Test Questions

Disabling source lifecycle rules removes the mechanism that was managing local blob versions. The vaulted backup policy does not automatically replace version-level retention controls on the source service.

Soft delete is a source-account data protection capability, not a setting that rewrites Vault-level recovery-point retention or cleans up historical source versions.

Increasing vault retention affects how long stored backup recovery points remain, not the expiration rules for versions in the source account. It cannot perform the requested source cleanup.

A vault provides the management destination, but without a protection policy on the VM no requested daily schedule and 30-day retention are established.

One manual backup can provide an isolated point, but it does not create new recovery points every day for continuing protection.

Monitoring can detect missing or failed jobs, but it cannot create the schedule and retention needed to generate actual backup recovery points.

Instant Restore can accelerate eligible recent VM restores from snapshots, but it does not change the retention policy or create six-month-old month-end recovery points. Specify the required monthly backup retention and schedule in advance.

Recreating the vault risks losing or complicating protection and cannot retroactively preserve an expired month-end recovery point.

GRS changes where backup data is redundantly stored, not how long individual daily or monthly recovery points remain. Redundancy and retention are independent policy dimensions; the existing two-week daily schedule still cannot supply a point from six months earlier.

Retention length and capture frequency are separate settings. A long retention window does not increase how often new copies are created.

Soft delete protects existing backup data against accidental deletion; it does not change how frequently fresh recovery points are captured. An ordinary daily backup policy can still miss an RPO that demands a point within several hours.

Keeping older recovery points for another year increases historical depth, not the freshness of the latest recovery point. The capture schedule remains daily, so it does not satisfy a several-hour recovery point objective.

Weekly retention applies to designated weekly restore points, not every recovery point initially produced by the daily schedule. Daily retention still governs ordinary daily points.

Storage access tier is not the VM backup policy retention control. Even a cost or tier change does not cause every daily backup to be kept beyond daily retention.

ARM locks protect certain management-plane operations but do not rewrite the backup engine’s recovery-point lifecycle. Explicit retention settings govern pruning and selected protected points.

Retention determines how long recovery points persist, not the local time when a backup job is initiated. The scheduled hour would still be interpreted using the selected timezone.

The VM guest time-zone setting controls how the operating system displays local time, not when the Recovery Services vault executes its own backup policy. Leaving the backup policy on an unchanged UTC schedule does not establish a 19:00 Eastern run. Set the schedule time zone and local hour in the supported backup policy, then validate the effective UTC execution time.

19:00 UTC is not 19:00 Eastern local time: the Eastern offset is normally UTC−5 or UTC−4 depending on daylight-saving time. Using the same number for a UTC policy hour would therefore schedule backup several hours before the requested 19:00 local window. Configure the intended policy time zone and local hour, and manage later daylight-saving changes separately.

Retention governs how long successful recovery points remain, not whether any point exists yet. Extending it cannot fabricate a completed first backup immediately after enrollment.

A resource-group management operation does not execute Azure Backup. The new protected VM can still lack a completed recovery point for immediate restoration.

Soft delete protects already-created recovery data from accidental deletion for a retention window. It does not execute the first backup job after protection enrollment or make an unscheduled recovery point appear.

Vault soft-delete retention governs recoverability of deleted backup items; it does not set how long each VM Instant Restore snapshot stays in the operational snapshot tier. The incident responders need a 21-day history of eligible recent snapshots, so the enhanced VM backup policy’s snapshot-retention setting is the direct control.

Additional backup events create more recovery points but do not extend the age for which each operational snapshot remains available. Set the Enhanced policy's snapshot-tier retention to 21 days, subject to frequency and vault retention support.

Vault-tier retention preserves recovery points in backup storage, but it does not extend the lifetime of locally accessible operational snapshots. With the Instant Restore snapshot tier still configured for seven days, an older recent restore can require the vault rather than the desired fast snapshot. Increase the Enhanced policy snapshot-retention period separately.

Display settings help administrators interpret the timestamps of completed jobs but do not rewrite when Azure Backup schedules the next job. The desired operational outcome is a consistent local wall-clock backup window across the upcoming daylight-saving transition, which requires a policy timing change.

The Recovery Services vault executes the backup policy independently of the guest operating system’s local clock. Updating the VM’s daylight-saving behavior does not automatically shift the policy’s scheduled time, and Microsoft explicitly documents that Azure VM Backup schedules do not adjust automatically for daylight-saving changes.

More scheduled backup executions increase frequency or alter recovery-point behavior but do not guarantee that any run starts exactly at the desired 19:00 local hour after a daylight-saving transition. The requirement is precise wall-clock scheduling, which must be corrected in the backup policy itself.

Resource group movement changes management scope, not VM disk contents or the recovery-point state. Moving a VM doesn't reconstruct its earlier configuration from Azure Backup and may have additional resource move constraints. The task requires selecting a recovery point for a restore operation.

Vault-tier recovery is an important durable backup path but can require transferring data from vault storage to the restore location. When a valid snapshot-tier recovery point is already available, Instant Restore avoids that extra transfer for a faster recovery. The premise doesn't require choosing the slower vault tier.

Yearly retention controls how long designated backup recovery points remain available. It doesn't accelerate retrieval of the current snapshot, shorten transfer distance, or select a faster restore method. The time-sensitive action is to restore from an eligible snapshot-tier point rather than change retention policy.

Job completion and usability of a selected restore are distinct. Corruption, missed application components or procedural gaps can remain undetected.

Soft delete helps protect backup data from accidental or malicious removal. It does not demonstrate that a specific file exists, is usable, or can be restored; perform a representative restore test.

More frequent successful jobs increase recovery points but do not prove the selected application file is present and recoverable. A safe trial restore is direct evidence.