AZ-104 Practice Questions

Explanation

Scenario:

1. Web administrators will deploy Azure web apps for the marketing department.

2. Each web app will be added to a separate resource group.

3. The initial configuration of the web apps will be identical.

4. The web administrators have permission to deploy web apps to resource groups.

Steps:

1 -- > Create a resource group, and then deploy a web app to the resource group.

2 -- > From the Automation script blade of the resource group , click Add to Library.

3 -- > From the Templates service, select the template, and then share the template to the web administrators .

When deploying Azure Bastion using an Azure Resource Manager (ARM) template, Microsoft requires that the subnet dedicated to Bastion follows strict configuration guidelines. According to the Microsoft Azure Administrator documentation, the Azure Bastion service must be deployed within a specifically named subnet called “AzureBastionSubnet”.

This subnet name is case-sensitive and mandatory — any deviation from this name (e.g., “BastionSubnet” or “AzureBastion”) will cause deployment failure.

Additionally, the subnet must have a minimum prefix of /27 to provide sufficient IP addresses for the Bastion-managed instances and scaling operations. Subnets smaller than /27 (such as /28 or /29) are not supported because Bastion requires multiple internal IP addresses for operations like scaling, management, and secure connectivity.

In the ARM template structure:

{

" type " : " Microsoft.Network/virtualNetworks " ,

" name " : " VNET1 " ,

" apiVersion " : " 2019-02-01 " ,

" location " : " [resourceGroup().location] " ,

" properties " : {

" addressSpace " : {

" addressPrefixes " : [ " 10.10.10.0/24 " ]

},

" subnets " : [

{

" name " : " AzureBastionSubnet " ,

" properties " : {

" addressPrefix " : " 10.10.10.0/27 "

}

},

{

" name " : " LAN02 " ,

" properties " : {

" addressPrefix " : " 10.10.10.128/25 "

}

}

]

}

}

This ensures that Azure Bastion can be deployed properly within the virtual network VNET1, providing secure RDP/SSH connectivity to VMs without exposing public IPs.

Extract from Microsoft Documentation:

“Azure Bastion must be deployed in a dedicated subnet named ‘AzureBastionSubnet’. The subnet must be at least /27 or larger (/26, /25, etc.). This subnet is used exclusively by the Bastion host and cannot contain other resources.”

(Source: Microsoft Learn — Deploy Azure Bastion using Azure Resource Manager templates, and Azure Bastion service configuration requirements)

To meet the specified requirements for creating an Azure Storage account that supports Azure Data Lake Storage, minimizes costs, and automatically replicates to a secondary region, the following settings are appropriate:

1️⃣ Support Azure Data Lake Storage → Enable Hierarchical Namespace

Azure Data Lake Storage Gen2 requires the Hierarchical Namespace feature to be enabled in the storage account. This allows directory-based organization and fine-grained access control for big data analytics.

✅ Answer:

C.  

2️⃣ Minimize costs for infrequently accessed data → Cool Access Tier

Azure Storage provides Hot, Cool, and Archive access tiers.

Hot = optimized for frequent access.

Cool = optimized for infrequent access (lower storage cost, higher access cost).

Archive = for offline, rarely accessed data.

For data that is infrequently accessed but still available online, Cool tier minimizes cost while maintaining accessibility.

✅ Answer:

A.  

3️⃣ Automatically replicate data to a secondary region → Geo-Redundant Storage (GRS)

Replication options include:

LRS (Locally Redundant Storage) – single-region redundancy.

ZRS (Zone Redundant Storage) – replication within one region.

GRS (Geo-Redundant Storage) – replicates data to a secondary Azure region automatically.

RA-GRS (Read-Access GRS) – allows read access to the secondary region.

For automatic replication to a secondary region, GRS is required.

✅ Answer:

E.  

Microsoft Documentation Extract Summary:

“Azure Data Lake Storage Gen2 is built on Azure Blob storage and requires the Hierarchical namespace setting to be enabled.”

“The Cool access tier is designed for infrequently accessed data, offering reduced storage costs.”

“Geo-redundant storage (GRS) replicates data to a secondary region for durability and disaster recovery.”

(Source: Microsoft Learn – Create and configure Azure Storage accounts)