Microsoft Updated AZ-104 Exam Questions and Answers by delilah-rose

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.

All three VMs are in VNET2. Auto registration is enabled for private Azure DNS zone named contoso.com, which is linked to VNET2. So, VM1, VM2 and VM3 will auto-register their host records to contoso.com.

None of the VM will auto-register to the public Azure DNS zone named adatum.com. You cannot register private IPs on the internet (adatum.com)

Box 1: Yes

Auto registration is enabled for private Azure DNS zone named contoso.com.

Box 2: Yes

Auto registration is enabled for private Azure DNS zone named contoso.com.

Box 3: No

None of the VM will auto-register to the public Azure DNS zone named adatum.com

LB1 will be connected to a subnet named LB1 in VNET1. Yes, this is correct. The template specifies that the load balancer resource named LB1 has a property called frontendIPConfigurations, which defines the subnet where the load balancer is located. The value of this property is a reference to the resource ID of the subnet named LB1 in VNET1. You can see this reference in line 38 of the template1.

LB1 can be deployed only to the resource group that contains VNET1. No, this is not correct. The template does not specify a resource group for the load balancer resource, which means it can be deployed to any resource group in the same subscription as VNET1. However, if you want to deploy the load balancer to a specific resource group, you can add a property called resourceGroup to the reference of the subnet in line 382.

The value of the sku variable can be provided as a parameter when the template is deployed. No, this is not correct. The template defines the sku variable as a constant value of “Standard” in line 9. This means that the value cannot be changed or overridden by a parameter when the template is deployed. If you want to make the sku value configurable, you need to change the variable definition to a parameter definition, and use the parameter reference instead of the variable reference in line 363.

Azure provides two different vault types for backup, each designed for specific workloads: Azure Backup vaults and Recovery Services vaults. Selecting the correct vault depends on the resource type being protected.

An Azure Backup vault is the newer vault type introduced to support Azure Disk Backup. According to the Azure Administrator documentation, Backup vaults are specifically designed for Azure managed disks and use a simplified policy model. They do not support backing up full virtual machines, Azure App Service apps, or Azure SQL Database (PaaS). Therefore, from the listed resources, Disk1 (Disk) is the only supported resource that can be backed up to Backup1.

A Recovery Services vault is the traditional and more feature-rich vault used to back up Azure Virtual Machines, as well as workloads such as SQL Server running inside Azure VMs. The documentation clearly states that Azure VMs must be backed up using a Recovery Services vault, not a Backup vault. As a result, VM1 (Virtual machine) must be backed up to Recovery1.

The remaining resources are not supported in either vault for this scenario:

App1 (Azure App Service web app) uses App Service backup, not Azure Backup.

DB1 (Azure SQL Database) uses built-in Azure SQL backup, not Recovery Services or Backup vaults.

Final Verified Answers:

Backup1 → Disk1

Recovery1 → VM1