AZ-104 Practice test with complete solutions

Q1. Your company is planning to use Azure Container Instances to deploy simple cloud applications. You are tasked with determining if multi-container groups hosting multiple container instances meet your solution requirements. You need to identify features and requirements for multi-container groups with each group hosting an application container, a logging container, and a monitoring container. For each of the following statements, select Yes if the statement is true. Otherwise, select No. Statement: 1- Multi-container groups support Linux containers only. 2- You can deploy a multi-container group from a Resource Manager template or a YAML file. 3- Container groups can scale up as necessary to create additional container instances as necessary. - ANSWER Answer: 1-Yes. 2-Yes. 3-No. Explanation: 1- Yes. Multi-container groups support Linux containers only. This is a current restriction for multi-container groups. Windows Containers are limited to Azure Container Instances that support deployment of a single container instance only. 2- Yes. You can deploy a multi-container group from a Resource Manager template or a YAML file. It is recommended that you use a Resource Manager template when you need to deploy additional Azure resources when deploying container instances, and this is the preferred method for deploying multi-container groups. 3- No. Container groups and container instances do not support scaling. If additional container groups or container instances are needed, they must be explicitly created. Q2. You create a FileStorage premium storage account and create a premium tier Azure file share. You plan to mount the file share directly on-premises using the Service Message Block (SMB) 3.0 protocol. You need to ensure that your network is configured to support mounting an Azure file share on-premises. You want to minimize the administrator effort necessary to accomplish this. What should you do? A-Create an ExpressRoute circuit. B-Install and configure Azure File Sync. C-Configure TCP port 445 as open in your on-premises internet firewall. D-Configure TCP port 443 as open in your on-premises internet firewall. - ANSWER Answer: C Explanation: You should configure TCP port 445 as open in your on-premises internet firewall. This is the only requirement for mounting an Azure file share as an on-premises SMB file share on your on-premises network. You should not configure TCP port 443 as open in your on-premises internet firewall. This would be a requirement if you were configuring Azure File Sync and not using ExpressRoute. You should not install and configure Azure File Sync. This is not a requirement for mounting a file share on-premises. You would use Azure File Sync if you wanted to cache several Azure file shares on-premises or in cloud VMs. You should not create an ExpressRoute circuit. An ExpressRoute circuit provides a private connection between your on-premises network and the Microsoft cloud. By using ExpressRoute you do not need to configure the on-premises firewall, but this solution requires more administrative effort to implement and maintain. Q3. You deploy a line of business (LOB) application. All resources that are part of the LOB application are deployed in a single resource group. The resources were added in different phases. You need to export the current configuration of the LOB application resources to an Azure Resource Manager (ARM) template. You will later use this template for deploying the LOB application infrastructure in different environments for testing or development purposes. For each of the following statements, select Yes if the statement is true. Otherwise, select No. Statement: 1- You need to export the ARM template from the latest deployment. 2- Each deployment contains only the resources that have been added in that deployment. 3- The parameters file contains the values used during the deployment. 4- The template contains the needed scripts for deploying the template. - ANSWER Answer: 1-No. 2-Yes. 3-Yes. 4-No. Explanation 1- No. You do not need to export the ARM template from the latest deployment. In this scenario, the LOB application was deployed in several phases. The latest deployment will export only the latest resources added to the application. If you want to export the ARM template with all the needed resources for the LOB application, you need to export the ARM template from the resource group. 2- Yes. Each deployment contains only the resources that have been added in that deployment. When you export an ARM template from a deployment, the template only contains the resources created during that deployment. 3- Yes. The parameters file contains the values used during the deployment. The parameters file is a JSON file that stores all the parameters used in the ARM template. You can use this file to reuse the template in different deployments, just changing the values of the parameters file. If you use this file in templates created from resource groups, you need to make significant edits to the template before you can effectively use the parameters file. 4- No. The template does not contain the needed scripts for deploying the template. When you download an ARM template from a deployment or a resource group, the downloaded package contains only the ARM template and the parameters file. You can reference Azure CLI scripts or a PowerShell script in the Azure docs linked in the export template pane. Q4. You use taxonomic tags to logically organize resources and to make billing reporting easier. You use Azure PowerShell to append an additional tag on a storage account named corpstorage99. The code is as follows: $r = Get-AzResource --ResourceName "corpstorage99" --ResourceGroupName "prod- rg" Set-AzResource --Tag --Resourceld $r.ResourceId --Force The code returns unexpected results. You need to append the additional tag as quickly as possible. What should you do? A-Refactor the code by using the Azure Command-Line Interface (CLI). B-Deploy the tag by using an Azure Resource Manager template. C-Edit the script to call the Add() method after getting the resource to append the new tag. D-Assign the Enforce tag and its value Azure Policy to the resource group. - ANSWER Answer: C Explanation: You should edit the script to call the Add() method after getting the resource to append the new tag as shown in the second line of this refactored Azure PowerShell code: $r = Get-AzResource --ResourceName "corpstorage99" --ResourceGroupName "prod- rg" $r.Tags.Add ( " Dept " , "IT") Set-AzResource --Tag $r.Tags --ResourceId $r.Resourceld --Force Unless you call the Add() method, the Set-AzResource cmdlet will overwrite any existing taxonomic tags on the resource. The Add() method preserves existing tags and includes one or more tags to the resource tag list. You should not deploy the tag by using an Azure Resource Manager template. Doing so is unnecessary in this case because the Azure PowerShell is mostly complete as-is. Furthermore, you must find the solution as quickly as possible. You should not assign the Enforce tag and its value Azure Policy to the resource group. Azure Policy is a governance feature that helps businesses enforce compliance in resource creation. In this case, the solution involves too much administrative overhead to be a viable option. Moreover, the scenario makes no mention of the need for governance policy in specific terms. You should not refactor the code by using the Azure Command-Line Interface (CLI). Either Azure PowerShell or Azure CLI can be used to institute this solution. It makes no sense to change the development language