Azure Administrator Associate AZ-104 Syllabus Exam Questions Answers

To automate the deployment of a virtual machine scale set that uses the Windows Server 2016 Datacenter image and has web server components installed, you need to perform the following actions:

Modify the extensionProfile section of the Azure Resource Manager template. This section defines the extensions that are applied to the scale set virtual machines after they are provisioned. You can use the Custom Script Extension to run PowerShell scripts that install and configure the web server components. For more information, see Deploy an application to an Azure Virtual Machine Scale Set1.

Upload a configuration script. This is the PowerShell script that contains the commands to install and configure the web server components. You can upload the script to a storage account or a GitHub repository, and then reference it in the extensionProfile section of the template. For an example of a configuration script, see Tutorial: Install applications in Virtual Machine Scale Sets with Azure PowerShell2.

When you clone an Azure App Service web app using New-AzWebApp -SourceWebApp, Azure copies application settings and configuration that are part of the app’s configuration metadata. Environment variables (App Settings) are included in the clone.

However, the following are not cloned:

Managed identity (must be enabled separately on the new app)

Deployment slots (slots are not copied to the new web app)

Backup configuration (backup schedules and settings are not cloned)

Therefore, among the listed options, only the environment variable is cloned to WebApp2.

This scenario requires two distinct tasks related to Azure Container Registry (ACR): creating the registry itself and uploading a container image into it. Microsoft Azure Administrator documentation clearly separates these responsibilities between Azure CLI and Docker CLI.

To provision a new Azure Container Registry, Microsoft documentation states that administrators must use the Azure CLI az acr create command. This command creates a private, managed Docker registry in Azure that can store and manage container images. The az acr create command defines the registry name, resource group, and pricing tier (Basic, Standard, or Premium). It is the only supported CLI command used to create an ACR resource. Commands such as az acr build, az container create, or docker create do not create a registry and therefore do not meet the requirement.

Once the registry exists, the container image must be uploaded to it. According to the Microsoft Azure Container Registry documentation, images are uploaded using standard Docker commands. After authenticating to the registry and tagging the image with the registry’s login server name, the image is transferred using the docker push command. Microsoft explicitly states that Azure CLI does not upload local images directly to ACR; instead, Docker is responsible for pushing images.

The documented workflow is:

Create the registry using az acr create.

Authenticate Docker to the registry.

Tag the image with the registry address.

Upload the image using docker push.

Therefore, the only commands that correctly satisfy the requirements are:

az acr create to provision the registry

docker push to add image1 to the registry

Final Verified Answer:

Provision a new container registry: az acr create

Add image1 to the registry: docker push