Microsoft AZ-104 Practice Test - Questions Answers, Page 8

Box 1: 2

There are 10 update domains. The 14 VMs are shared across the 10 update domains so four update domains will have two VMs and six update domains will have one VM. Only one update domain is rebooted at a time.

Therefore, a maximum of two VMs will be offline.

Box 2: 7

There are 2 fault domains. The 14 VMs are shared across the 2 fault domains, so 7 VMs in each fault domain.

A rack failure will affect one fault domain so 7 VMs will be offline.

Reference:

https://docs.microsoft.com/en-us/azure/virtual-machines/windows/manage-availability

Box 1 : Containers will get the IP address from the virtual network subnet CIDr which is 10.244.0.0/16

Box 2 : Services in the AKS cluster will be assigned an IP address in the service CIDR which is 10.0.0.0/16

Reference:

https://docs.microsoft.com/en-us/azure/aks/configure-azure-cni

Reference:

https://docs.microsoft.com/en-us/azure/site-recovery/move-azure-vms-avset-azone

https://docs.microsoft.com/en-us/azure/virtual-machines/windows/create-portal-availability-zone

Scale up: Get more CPU, memory, disk space, and extra features like dedicated virtual machines (VMs), custom domains and certificates, staging slots, autoscaling, and more.

You scale up by changing the pricing tier of the App Service plan that your app belongs to.

Reference:

https://docs.microsoft.com/en-us/azure/app-service/manage-scale-up

You can use a template that allows you to deploy a simple Windows VM by retrieving the password that is stored in a Key Vault. Therefore the password is never put in plain text in the template parameter file.

Reference: https://azure.microsoft.com/en-us/resources/templates/101-vm-secure-password/

Box 1: can connect to the container from any device

In the policy "osType": "window" refer that it will create a container in a container group that runs

Windows but it won't block access depending on device type.

Box 2: the container will restart automatically

Docker provides restart policies to control whether your containers start automatically when they exit, or when Docker restarts. Restart policies ensure that linked containers are started in the correct order. Docker recommends that you use restart policies, and avoid using process managers to start containers.

on-failure : Restart the container if it exits due to an error, which manifests as a non-zero exit code.

As the flag is mentioned as "on-failure" in the policy, so it will restart automatically

Reference:

https://docs.microsoft.com/en-us/cli/azure/container?view=azure-cli-latest

https://docs.docker.com/config/containers/start-containers-automatically/

For Azure AD roles in Privileged Identity Management, only a user who is in the Privileged role administrator or Global administrator role can manage assignments for other administrators. You can grant access to other administrators to manage Privileged Identity Management. Global

Administrators, Security Administrators, Global readers, and Security Readers can also view assignments to Azure AD roles in Privileged Identity Management.

Only owner can create an subscription and only global administrator can perform Privileged Identity

Management changes. So you can create subscription with external user and then promote him to global administrator to get things done.

As it is mentioned as it is associated with azure tenant so that tenant has an AD domain. So in azure

AD the default domain ends with onmicrosoft.com. So you can't have Hotmail IDs there. Moreover always remember the principle of least privileges, when you can get your job done with Global

Administrator then you should not look for owner for security purpose.

[email protected] : Correct Choice

As Admin1 is Global Administrator and part of default AD domain so Admin1 can add an Azure AD

Privileged Identity Management application to Tenant1

[email protected] : Incorrect Choice

As per the above explanation Admin3 is not Global Administrator, so this option is incorrect.

[email protected] : Incorrect Choice

As per the above explanation Admin2 is not Global Administrator, so this option is incorrect.

[email protected] : Incorrect Choice

Although this user is Global Administrator but referring to the least privileges principal and default domain consideration this option is incorrect.

Reference:

https://docs.microsoft.com/en-us/azure/active-directory/privileged-identity-management/pimgetting-started

https://docs.microsoft.com/en-us/azure/active-directory-domain-services/tutorial-create-instance

The equation is: 'core usage x comfort factor'. The comfort factor is 2.0.

So VM 1 is 10 cores at 20% utilization which equals 2 cores. Multiply that the comfort factor and you get 4 cores.

VM 2 is 4 cores at 50% utilization which equals 2 cores. Multiply that the comfort factor and you get 4 cores.