You can change the location in resources. Parameters used to define the value of some variables to be able to use in different places in the template resources. Resources are used only for complicated expressions. In any case, RM will only deploy from resources. In case the value is not mentioned directly, then it will check parameters if it is specified in the resources. Based on this question, the value of location is defined directly in resources. so you change the resources location value.
Use location parameter. To allow flexibility when deploying your template, use a parameter to specify the location for resources. Set the default value of the parameter to resourceGroup().location.
Reference:
https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/resource-location?tabs=azure-powershell
https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/template-syntax#resources

You can ' t delete a vault that contains backup data. So in this case at first you have to delete the backup of ' SQLD01 ' before you attempt to delete the vault.
Reference:
https://docs.microsoft.com/en-us/azure/backup/backup-azure-delete-vault

Explanation:
Stored access policies: # 2
Immutable blob storage policies: # 1
From the scenario in the earlier case study (A. Datum Corporation):
* The planned change requires creating a new container named cont2 in storage1, with the following:
* Three stored access policies (Stored1, Stored2, Stored3)
* A legal hold for immutable blob storage
Also, recall from the table:
* storage1 has Hierarchical namespace = Yes (Data Lake Storage Gen2 enabled).
* storage2 has Hierarchical namespace = No.
The question asks: "What is the maximum number of additional access policies you can create for cont2?" According to Microsoft Azure Storage documentation:
* A blob container can have a maximum of five stored access policies.
* These policies allow shared access signatures (SAS) to be managed centrally, letting you define start times, expiry times, and permissions at the container level.
Since three stored access policies (Stored1, Stored2, Stored3) already exist, the maximum additional policies that can still be created is:
# 5 (maximum allowed) - 3 (already existing) = 2
For immutable blob storage policies:
* A container can have one active immutability policy at a time.
* This can be either a time-based retention policy or a legal hold policy.
* Since cont2 already has a legal hold applied, no additional immutable policy can coexist with it, but it can have one defined policy type (the legal hold).
Therefore:
* Stored access policies: 2 additional policies can still be created.
* Immutable blob storage policies: 1 policy (the existing legal hold).
This aligns exactly with Microsoft Learn: Azure Storage Blob Service limits and immutable storage documentation:
"A container may have up to five stored access policies. Immutable storage supports either a time-based retention policy or legal hold policy per container." Final Verified Answer:
# Stored access policies: 2
# Immutable blob storage policies: 1
Topic 2, Contoso LtdOverview
Contoso, Ltd. is a manufacturing company that has offices worldwide. Contoso works with partner organizations to bring products to market.
Contoso products are manufactured by using blueprint files that the company authors and maintains.
Existing Environment
Currently, Contoso uses multiple types of servers for business operations, including the following:
File servers
Domain controllers
Microsoft SQL Server servers
Your network contains an Active Directory forest named contoso.com. All servers and client computers are joined to Active Directory.
You have a public-facing application named App1. App1 is comprised of the following three tiers:
A SQL database
A web front end
A processing middle tier
Each tier is comprised of five virtual machines. Users access the web front end by using HTTPS only.
Requirements
Planned Changes
Contoso plans to implement the following changes to the infrastructure:
Move all the tiers of App1 to Azure.
Move the existing product blueprint files to Azure Blob storage.
Create a hybrid directory to support an upcoming Microsoft Office 365 migration project.
Technical Requirements
Contoso must meet the following technical requirements:
Move all the virtual machines for App1 to Azure.
Minimize the number of open ports between the App1 tiers.
Ensure that all the virtual machines for App1 are protected by backups.
Copy the blueprint files to Azure over the Internet.
Ensure that the blueprint files are stored in the archive storage tier.
Ensure that partner access to the blueprint files is secured and temporary.
Prevent user passwords or hashes of passwords from being stored in Azure.
Use unmanaged standard storage for the hard disks of the virtual machines.
Ensure that when users join devices to Azure Active Directory (Azure AD), the users use a mobile phone to verify their identity.
Minimize administrative effort whenever possible.
User Requirements
Contoso identifies the following requirements for users:
Ensure that only users who are part of a group named Pilot can join devices to Azure AD.
Designate a new user named Admin1 as the service administrator of the Azure subscription.
Admin1 must receive email alerts regarding service outages.
Ensure that a new user named User3 can create network objects for the Azure subscription.

To prepare Vault1 for Azure Disk Encryption, you need to perform the following actions on Vault1:
Create a new key. A key encryption key (KEK) is an encryption key that is used to encrypt the encryption secrets before they are stored in the key vault. You can create a new KEK by using the Azure CLI, the Azure PowerShell, or the Azure portal1. You can also import an existing KEK from another source, such as a hardware security module (HSM)2. The KEK must be a 2048-bit RSA key or a 256-bit AES key3.
Select Azure Disk Encryption for volume encryption. This is an advanced access policy setting that enables Azure Disk Encryption to access the keys and secrets in the key vault. You can select this setting by using the Azure CLI, the Azure PowerShell, or the Azure portal4. You must also enable access to Microsoft Trusted Services if you have enabled the firewall on the key vault.

Azure virtual machines can occasionally be subject to platform maintenance events. Maintenance can be planned (with notice) or unplanned. Planned maintenance includes updates to the host operating system or hardware that may require moving your VM to another host.
When you receive a maintenance notification, Azure provides options to move your VM proactively to minimize downtime. According to the Microsoft Azure Administrator documentation, the correct action is to use the "Redeploy" option or "Move VM to another host" from the Azure portal. This operation shuts down the VM, migrates it to a new physical node within the same region, and then restarts it - effectively resolving maintenance impact.
The Update management blade, however, is part of Azure Automation Update Management, which is used to schedule and manage operating system updates (Windows or Linux) across Azure and hybrid environments.
Enabling Update Management simply connects the VM to a Log Analytics workspace and does not move or redeploy the VM.
Therefore, enabling Update Management does not achieve the goal of moving VM1 to a different host to avoid maintenance. The correct action would be:
Navigate to VM1 # Help # Redeploy + reapply # Redeploy.
This redeploys the VM to another host server while retaining its network and disk configurations.
Thus, the proposed solution does not meet the goal.