Microsoft AZ-104 Exam With Confidence Using Practice Dumps

Scenario: Licensing Issue

1. You attempt to assign a license in Azure to several users and receive the following error message: " Licenses not assigned. License agreement failed for one user. "

2. You verify that the Azure subscription has the available licenses.

Solution:

License cannot be assigned to a user without a usage location specified.

Some Microsoft services aren ' t available in all locations because of local laws and regulations. Before you can assign a license to a user, you must specify the Usage location property for the user. You can specify the location under the User  >  Profile  >  Settings section in the Azure portal.

You can add a virtual network link only to zone3.com , the Azure Private DNS zone. Microsoft states that after creating a private DNS zone in Azure, you link a virtual network to it so that virtual machines hosted in that virtual network can resolve records in the private DNS zone. The documentation further explains that every private DNS zone has a collection of virtual network link child resources, where each link represents a connection to a virtual network.

The standard primary DNS zone zone1.com is hosted inside the Windows Server DNS role on VM1. It is not an Azure Private DNS zone resource and therefore does not support Azure virtual network links. The Azure DNS zone zone2.com is a public DNS zone, used for authoritative public DNS hosting, and it is not linked to VNets by using private DNS virtual network links. Only Azure Private DNS zones provide VNet linking for private name resolution and optional autoregistration. This maps to AZ-104 Configure and manage virtual networking , specifically DNS name resolution, Azure DNS, Azure Private DNS zones, and virtual network links.

In Microsoft Azure, encryption scopes are a StorageV2 (general-purpose v2) storage account feature that allows fine-grained control over encryption settings for data stored within a single account. According to Microsoft Azure Storage documentation, an encryption scope defines a specific encryption context that can be applied at the container or blob level and is supported in non-hierarchical namespace storage accounts (those without Data Lake Gen2 enabled).

In the given scenario:

storage1 has Hierarchical namespace = Yes (Data Lake Storage Gen2 enabled).

storage2 has Hierarchical namespace = No.

The plan was to create an encryption scope named Scope1 in storage2.

The technical requirement specifies that Scope1 must be used to encrypt storage services.

According to the Azure Administrator documentation on encryption scopes:

“Encryption scopes are supported for block blobs, append blobs, page blobs, Azure Files, queues, and tables in standard StorageV2 accounts. Encryption scopes are not supported in hierarchical namespace (Data Lake Gen2) enabled accounts.”

This means that Scope1—created in storage2, which does not have hierarchical namespace—can encrypt all blob data (containers and blobs) as well as file shares, queues, and tables.

However, storage1 cannot use encryption scopes because hierarchical namespace storage accounts (ADLS Gen2) manage encryption at the account level and do not support per-scope encryption.

Therefore, only storage2 can apply Scope1, and it can encrypt containers, blobs, file shares, queues, and tables.