4 of the 11 questions we have for this objective, shown with the answer and the reasoning.
Implement backup and recovery
Marlow Fintech runs a transaction-processing application on three Trusted Launch virtual machines in a Recovery Services vault named rsv-mf-prod. The business requires a recovery point every 4 hours, instant-restore snapshots kept for 7 days, daily recovery points kept for 60 days, and a monthly recovery point kept for 3 years.
Which backup policy should you create?
- AAn Enhanced policy with an hourly backup frequency of every 4 hours, a 7-day instant restore snapshot retention, 60-day daily retention, and 3-year monthly retention.Only the Enhanced policy supports multiple backups per day and snapshot retention beyond 5 days; it is also the policy type the portal offers for Trusted Launch virtual machines.
- BA Standard policy with a daily backup, a 5-day instant restore snapshot retention, 60-day daily retention, and 3-year monthly retention.A Standard policy backs up at most once per day and caps instant restore snapshots at 5 days, so it misses two requirements.
- CSix Standard policies with daily schedules staggered 4 hours apart, each assigned to all three virtual machines.A virtual machine can be associated with only one backup policy in a vault, so this is not possible.
- DA Backup vault policy with a 4-hour schedule and 60-day retention.Backup vault policies apply to workloads such as disks and blobs; Azure virtual machine backup is governed by Recovery Services vault policies.
Why: Azure virtual machine backup offers two policy types. The Standard policy runs once a day and keeps instant restore snapshots for 1 to 5 days. The Enhanced policy supports multiple backups per day (as frequent as every 4 hours), instant restore snapshot retention of up to 30 days (reduced to 17 days at a 4-hour frequency), and is required for Ultra Disk and Premium SSD v2 virtual machines; Trusted Launch virtual machines can use the Standard policy only through CLI, PowerShell, or REST, not the portal. The 4-hour recovery point objective and the 7-day snapshot retention each independently force the Enhanced policy; the one-policy-per-machine rule eliminates the stacked-policy workaround.
Implement backup and recovery
Copperleaf Bank replicates its loan-processing virtual machines from North Europe to West Europe with Azure Site Recovery. An auditor requires evidence, once per quarter, that the machines can be started in West Europe and that the application works. The production machines in North Europe must keep running, replication must not be interrupted, and the drill must not interfere with any production network.
What should you do?
- ARun a test failover to an isolated virtual network in West Europe, validate the application, then clean up the test failover.Test failover creates copies of the machines in an isolated network from a chosen recovery point while production and replication continue unaffected; cleanup removes the test resources.
- BRun a failover to West Europe, validate the application, then re-protect the machines and fail back to North Europe.A real failover stops the production machines and reverses replication; it is a disruptive operation, not a drill.
- CDisable replication, create the machines manually in West Europe from the replica disks, then re-enable replication.Disabling replication discards the replication state and forces a full initial replication afterward, which violates the requirement that replication is not interrupted.
- DRun a test failover into the production virtual network in West Europe so the application can be tested with real dependencies.Using the production network can cause IP conflicts and let the test machines interact with live systems, which the scenario forbids.
Why: Site Recovery distinguishes between a test failover, which is a non-disruptive disaster recovery drill, and a failover, which is the real thing. A test failover spins up the replicated machines in a network you choose, ideally an isolated one, from a selected recovery point, without touching the source machines or the ongoing replication; when you are finished you run Cleanup test failover. The audit requirement combined with the constraints on production availability, replication continuity, and network isolation makes the isolated test failover the only acceptable option.
Implement backup and recovery
Dunmore Architects backs up a Windows virtual machine named vm-cad01 daily to a Recovery Services vault named rsv-dm. A designer accidentally deleted a single project folder from the D: drive this morning. The virtual machine is otherwise healthy and is in use by other designers. You need to recover the folder with the least disruption to the running machine.
What should you do?
- AFrom the backup item in rsv-dm, select File Recovery, choose yesterday's recovery point, run the generated script on vm-cad01 to mount the recovery point as a drive, and copy the folder back.File Recovery mounts the recovery point disks as iSCSI volumes on a running machine so individual files and folders can be copied without restoring the whole machine.
- BFrom the backup item in rsv-dm, select Restore VM, choose Replace existing, and restore yesterday's recovery point.Replacing the disks rolls back every file on the machine, discarding today's work by the other designers, and requires the machine to be shut down.
- CFrom the backup item in rsv-dm, select Restore VM, choose Create new, and deploy a second virtual machine named vm-cad01-restore.A full restore to a new machine works but takes much longer and creates billable resources for a single folder.
- DCreate a snapshot of the current D: data disk and attach the snapshot to vm-cad01 as a new disk.A snapshot taken now captures the disk after the deletion, so the folder is not in it.
Why: Azure virtual machine backup supports two levels of restore. A full restore (create new machine, restore disks, or replace existing disks) is for machine-level loss. File Recovery is the item-level option: the vault generates a script that mounts the selected recovery point as local drives on any Windows or Linux machine, including the original, so you copy only what you need. The constraint of least disruption to a machine that is in use by others makes File Recovery the only sensible choice.
Implement backup and recovery
Greywater Utilities replicates a billing application from Central US to East US 2 with Azure Site Recovery. During an outage in Central US the operations team performed a failover using the latest processed recovery point, and the application is now running in East US 2. The team then committed the failover. Central US is available again. Greywater wants the billing machines in East US 2 to be protected against an East US 2 outage and, at a later date, to move the application back to Central US.
What should you do next?
- ARe-protect the virtual machines so that replication runs from East US 2 to Central US.After a committed failover, re-protect reverses the replication direction; this both protects the machines in their new region and is the prerequisite for a later failover back.
- BEnable replication again from Central US to East US 2 for the original virtual machines.The original machines in Central US are out of date and no longer the live copy; replicating from them would overwrite nothing useful and does not protect the running workload.
- CRun a test failover from East US 2 to Central US.There is no replication in that direction yet, so a test failover is not possible; replication must be established first by re-protecting.
- DDisable replication for the machines and create a new recovery plan in Central US.Disabling replication removes protection entirely and a recovery plan only orchestrates failover of machines that are already replicating.
Why: The Site Recovery lifecycle for a real outage is failover, commit, re-protect, and then, when ready, fail over again in the opposite direction, which is the failback. Commit finalizes the chosen recovery point and deletes the others. Re-protect is the step that establishes replication from the now-active secondary region back to the original region; until it completes, the machines in East US 2 have no disaster recovery protection and failback is impossible. The distractors confuse the direction of replication or skip the step that makes any of the later actions possible.