AZ-104 Exam Dumps and Practice Questions

When you swap deployment slots, Azure swaps the Virtual IP addresses of the source and destination slots, thereby swapping the URLs of the slots. We can easily revert the deployment by swapping back. Deployment slots are live apps with their own host names. App content and configurations elements can be swapped between two deployment slots, including the production slot. Deploying your application to a non-production slot has the following benefits: 1. You can validate app changes in a staging deployment slot before swapping it with the production slot. 2. Deploying an app to a slot first and swapping it into production makes sure that all instances of the slot are warmed up before being swapped into production. Reference: https://docs.microsoft.com/en-us/azure/app-service/deploy-staging-slots

According to theMicrosoft documentation, when you assign a license to a group, all members of that group are automatically assigned the license. However, if a user is already assigned the same license directly or through another group, the license is not duplicated.

In your scenario, you assigned the Azure AD Premium P2 license to Group1 and User4. This means that all members of Group1, which are User1 and User2, will also get the license. User4 will get the license directly.

User3 will not get the license because they are not a member of Group1 or assigned the license directly.

Therefore, the users who are assigned the Azure AD Premium P2 license are User1, User2, and User4 only.

Microsoft Fabric licenses can be assigned to specific identity types in Microsoft Entra. Typically, Fabric licenses can be assigned to user identities and service principals, but NOT to guest accounts, groups, or external identities in most standard configurations. The specific answer depends on the tenant configuration shown in the exhibit and the table of identities. Generally, licenses are assigned to individual user accounts and service principals that have appropriate access to the tenant. Without seeing the specific exhibit and identity table, the most common supported identities would be member users and service principals.

In Azure, load balancer configurations must have consistent SKU compatibility between the load balancer and its associated backend pool members. The Standard SKU Load Balancer requires that all backend pool members --- such as virtual machines, network interfaces, or virtual machine scale sets --- use Standard SKU public IPs or Standard SKU configurations if external, and proper network interface associations if internal.

However, in this question:

LB1 is

an internal Standard SKU load balancer.

Internal load balancers do not require or support public IP addresses on the backend virtual machines.

Backend pool members of an internal load balancer are identified by private IP addresses from the virtual network, not public IPs.

According to Microsoft Azure Load Balancer documentation (Azure Administrator Guide, ''Configure Standard Load Balancer''),

''For a Standard internal load balancer, the backend pool can contain only virtual machines or NICs that are in the same virtual network as the load balancer. Public IP addresses are not required and not supported for backend members.''

To correctly meet the goal, the proper solution is to:

Ensure that VM1 and VM2 are deployed within the same virtual network (VNET1) and subnet as LB1.

Ensure that the NICs of both VMs are configured with Standard SKU (if public IPs are attached elsewhere) to match the load balancer SKU.

Add these NICs or virtual machines directly to the backend pool of LB1.

Creating and assigning Standard SKU public IP addresses to each VM is unnecessary and does not help connect them to the internal load balancer. In fact, it contradicts Azure's design for internal load balancers, which only route traffic using private addresses within the virtual network scope.

Therefore, the given solution does not meet the goal.

In Azure Container Registry (ACR), the admin user account provides a simple authentication mechanism using a username and password. Enabling the admin account and retrieving its credentials is done exclusively through the Access keys blade.

According to Azure Container Registry documentation:

The admin user is enabled/disabled from Access keys

The passwords (primary and secondary) are displayed and regenerated there

Other blades such as Networking, Properties, or Identity do not manage admin credentials

Final Answer: