Microsoft AZ-104 Online Access

When configuring an Azure App Service app (WebApp1), several hosting plans determine scaling capabilities and supported features such as custom domains, SSL, and auto-scaling.

According to Microsoft Azure Administrator Documentation:

Custom Domain Verification:To map a custom domain (like app.contoso.com) to an Azure Web App, Azure must verify that you own the domain.Microsoft documentation specifies:

“To verify a custom domain, create a TXT record in your DNS zone. The TXT record contains a verification token that Azure uses to confirm ownership of the domain before binding it to your App Service.”

(Source: Azure App Service – Map custom domain)

While an A record or CNAME record is eventually used to direct traffic to the app, the TXT record is used solely for domain verification.

Scaling Requirement (Up to 8 Instances):The Free and Shared App Service plans have significant limitations:

Free / Shared: No scaling (only 1 instance, no custom domain SSL support).

Basic: Supports up to 3 instances.

Standard: Supports up to 10 instances, includes auto-scaling, and supports custom domains and SSL.

Premium: Adds advanced scaling and isolation but is more expensive and unnecessary here.

Microsoft documentation states:

“The Standard pricing tier supports auto-scaling up to 10 instances and custom domains, offering a balance between cost and capability.”

(Source: Azure App Service Plan Tiers Overview)

Since the requirement includes automatic scaling up to eight instances and custom domain verification, the Standard plan is the minimum suitable tier — satisfying both performance and cost-efficiency conditions.

✅ Final Verified Answer:

Pricing plan: Standard

Record type: TXT

Justification Summary (from Microsoft Documentation):

Custom domain verification → Requires a TXT record.

Auto-scale up to 8 instances → Requires at least the Standard plan.

Minimize cost and effort → Standard plan is the optimal balance.

According to the Microsoft documentation, Azure Bastion is a service that provides more secure and seamless RDP and SSH access to virtual machines without any exposure through public IP addresses. You can provision the service directly in your local or peered virtual network to get support for all the VMs within it.

In your scenario, you have three virtual networks that are peered with each other. This means that they can communicate with each other as if they were in the same virtual network. Therefore, you can deploy one Bastion host in any of the virtual networks and use it to connect to all the virtual machines in the peered virtual networks. You don’t need to deploy a separate Bastion host for each virtual network or each virtual machine.

For more information about how to deploy and use Azure Bastion, see Tutorial: Deploy Bastion using specified settings: Azure portal.

Box 1: 10 years

The yearly backup point occurs to 1 March and its retention period is 10 years.

Box 2: 36 months

The monthly backup point occurs on the 1

of every month and its retention period is 36 months.

Note: Azure retention policy takes the longest period of retention for each backup. In case of conflict between 2 different policies.

When deploying Azure Virtual Machine Scale Sets (VMSS) using an Azure Resource Manager (ARM) template, you can automatically install and configure applications or services (like NGINX) on the virtual machines using the Azure Custom Script Extension.

According to the Microsoft Azure Administrator documentation, the Custom Script Extension is used to download and execute scripts on Azure virtual machines after deployment. It is ideal for configuration management, application installation, and post-deployment software setup.

The extension can execute PowerShell or Bash scripts stored in Azure Storage or GitHub repositories. When used with an ARM template, you define the extension in the template’s " resources " section under " type " : " Microsoft.Compute/virtualMachines/extensions " or " Microsoft.Compute/virtualMachineScaleSets/extensions " .

Microsoft’s official documentation notes:

“The Custom Script Extension for Windows and Linux downloads and executes scripts on Azure virtual machines. This extension is useful for post-deployment configuration, software installation, or any other configuration or management tasks.”

In this case, using Azure Custom Script Extension allows automatic installation of NGINX on all VM instances as soon as they are created in the scale set — satisfying the requirement that NGINX is available immediately after deployment.

Other options do not fit:

Application Insights is used for monitoring, not configuration.

Publish-AzVMDscConfiguration and New-AzConfigurationAssignment are used for Desired State Configuration (DSC), not lightweight application installation like NGINX.

Hence, the only verified and cost-efficient solution is Azure Custom Script Extension.