Correct Answer: D

ScaleSetVM orchestration mode: Virtual machine instances added to the scale set are based on the scale set configuration model. The virtual machine instance lifecycle - creation, update, deletion - is managed by the scale set. It the current default VMSS behavior. (Scale set VMs are created in a single shot).

VM (virtual machines) orchestration mode: Virtual machines created outside of the scale set can be explicitly added to the scale set. The orchestration mode VM will only create an empty VMSS without any instances, and you will have to manually add new VMs into it by specifying the VMSS ID during the creation of the VM. (Separately VMs are created and added to scale set later)

Reference:

https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/orchestration-modes

Correct Answer: B

.NET Core 3.0: Windows and Linux

ASP .NET V4.7: Windows only

PHP 7.3: Windows and Linux

Ruby 2.6: Linux only

Also, you can’t use Windows and Linux Apps in the same App Service Plan, beacuse when you create a new App Service plan you have to choose the OS type. You can't mix Windows and Linux apps in the same App Service plan.

So, you need 2 ASPs.

Reference:

https://docs.microsoft.com/en-us/azure/app-service/overview

Correct Answer:

Box 1: VM1 and VM2 continue to run

The Budget’s scope is RG1, so only VM1 will be handled.

When the budget thresholds you've created are exceeded, only notifications are triggered.

To stop resources, you need to setup additional things, none of which are mentioned in the question.

Box 2: one email notification will be sent each month.

Budget alerts have scope in Resource Group RG1, which includes VM1, but not VM2.

VM1 consumes 20 Euro/day, so 20 euros * 30 days = 600 euros.

The 50%, 500 Euro limit, will be reached in 25 days (25*20 = 500), so an email will be sent.

The 70% and 100% alert conditions will not be reached within a month, and they don't trigger email actions anyway, because AG1 action group contains a user.

Credit alerts: Credit alerts are generated automatically at 90% and at 100% of your Azure credit balance. Whenever an alert is generated, it's reflected in cost alerts and in the email sent to the account owners. 90% and 100% will not be reached though.

Correct Answer: B - No

From the RG1 blade, click Deployments. You see a history of deployment for the resource group.

Reference:

https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/template-tutorial-create-first-template?tabs=azure-powershell

Correct Answer: B - No

Instead, you should delete VM1. Then recreate VM1 and add the network interface for VM1.

To migrate a VM from a VNET to another VNET. The only option is to delete the VM and redeploy it using a new NIC and NIC connected to VNET2.

Note: When you create an Azure Virtual Machine (VM), you must create a Virtual Network (VNet) or use an existing VNet. You can change the subnet a VM is connected to after it's created, but you cannot change the VNet. You can also change the size of a VM.

Reference:

https://docs.microsoft.com/en-us/azure/virtual-machines/windows/network-overview

First the only user who can join Azure AD devices is User 1 . since User1 is admin on machine. So, the machine can be added.

Second, the ones that can be local admins on Windows 10 are managed under "Additional local administrators" , since this is not mentioned, so we can assume default.

By default, the ones are global administrator and device owners (device administrators). This lead us to User1 and User2 only

Box 1: No -

RG2 is read only. ReadOnly means authorized users can read a resource, but they cannot delete or update the resource.

Box 2: Yes -

Box 3: Yes -

Note:

App Service resources are region-specific and cannot be moved across regions. You must create a copy of your existing App Service resources in the target region, then move your content over to the new app. You can then delete the source app and App Service plan.

To make copying your app easier, you can clone an individual App Service app into an App Service plan in another region.

Reference:

https://docs.microsoft.com/en-us/azure/app-service/manage-move-across-regions

https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/move-limitations/app-service-move-limitations

Box 1: "tag1": "value1" only -

Box 2: "tag2": "value2" and "tag3": "value3" only

Tags applied to the resource group are not inherited by the resources in that resource group.

Reference:

https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-using-tags

Box 1: 60 -

One alert per minute will trigger one email per minute.

Box 2: 12 -

No more than 1 SMS every 5 minutes can be send, which equals 12 per hour.

Note: Rate limiting is a suspension of notifications that occurs when too many are sent to a particular phone number, email address or device. Rate limiting ensures that alerts are manageable and actionable.

The rate limit thresholds are:

✑ SMS: No more than 1 SMS every 5 minutes.

✑ Voice: No more than 1 Voice call every 5 minutes.

✑ Email: No more than 100 emails in an hour.

✑ Other actions are not rate limited.

Reference:

https://docs.microsoft.com/en-us/azure/azure-monitor/platform/alerts-rate-limiting

Correct Answer: D

To create a Recovery Services Vault to protect Virtual Machines, the vault must be in the same Region as the Virtual Machines. If you have Virtual Machines in several Regions, create a

Recovery Services Vault in each Region. It works with any resource group or any Operating System.

Reference:

https://docs.microsoft.com/bs-cyrl-ba/azure/backup/backup-create-rs-vault

https://docs.microsoft.com/en-us/azure/backup/backup-azure-arm-vms-prepare