Microsoft AZ-104 Based on Real Exam Environment

The first step is to stop the existing backup of VM2 from RSV1 . Azure Backup does not allow the same Azure VM to be actively protected by multiple Recovery Services vaults at the same time. Microsoft’s Azure VM backup guidance states that VMs can only be backed up in a single vault, and to change the Recovery Services vault of a VM, you must stop the backup and then assign a new vault to the VM.

Therefore, you must open RSV1 , go to Backup items , select the VM2 backup item, and stop protection before configuring VM2 for backup in RSV2 . Depending on retention requirements, you can stop protection and retain backup data, or stop protection and delete backup data. Microsoft’s backup management guidance explains both stop-backup options and confirms that stopping protection halts future backup jobs for that VM.

Option A refers to disaster recovery replication, not Azure Backup vault reassignment. Option C exports job information only and does not change protection. Option D cannot be completed first because VM2 is still protected by RSV1. Study Guide reference: AZ-104 Monitor and back up Azure resources > Azure Backup, Recovery Services vaults, backup items, and VM backup protection management.

When deploying a virtual machine via an ARM template, dependencies must ensure resources are created in the proper order. A VM requires a network interface (NIC) at creation time; therefore, the VM resource must depend on the NIC.

The NIC itself depends on the virtual network, subnet, network security group, and public IP (if applicable). Microsoft ARM template guidance specifies that the VM’s dependsOn should reference the NIC, allowing Azure Resource Manager to implicitly handle the remaining network dependencies.

No, Yes, Yes

Azure Blob Storage early deletion penalties apply to cooler access tiers, not the Hot tier. Microsoft states that blobs are subject to an early deletion penalty if they are deleted, overwritten, or moved to a different tier before the minimum number of days required by that tier has elapsed. For a general-purpose v2 account, the Cool tier has a minimum retention period of 30 days, and the Archive tier has a minimum retention period of 180 days.

File1 is in the Hot tier and is deleted on January 5. The Hot tier has no early deletion retention requirement, so no early deletion penalty applies. Also, because blob soft delete is enabled, Microsoft notes that a blob is considered deleted only after the soft-delete retention period expires; until then, it is soft-deleted and not subject to the early deletion penalty.

File2 is placed in the Cool tier on January 1 and moved to Archive on January 15, before the 30-day Cool retention period is met, so an early deletion penalty applies. File3 is placed in Archive on January 1 and rehydrated on April 5, which is before 180 days, so the Archive early deletion penalty applies. Study Guide reference: AZ-104 Implement and manage storage , Blob access tiers, lifecycle management, and storage cost behavior.