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

Azure Migrate provides a centralized hub to assess and migrate to Azure on-premises servers, infrastructure, applications, and data. It provides the following:

Unified migration platform: A single portal to start, run, and track your migration to Azure.

Range of tools: A range of tools for assessment and migration. Azure Migrate tools include Server

Assessment and Azure Migrate: Server Migration. Azure Migrate also integrates with other Azure services and tools, and with independent software vendor (ISV) offerings.

Assessment and migration: In the Azure Migrate hub, you can assess and migrate:

Servers: Assess on-premises servers and migrate them to Azure virtual machines or Azure VMware

Solution (AVS) (Preview).

Databases: Assess on-premises databases and migrate them to Azure SQL Database or to SQL Managed Instance.

Web applications: Assess on-premises web applications and migrate them to Azure App Service by using the Azure App Service Migration Assistant.

Virtual desktops: Assess your on-premises virtual desktop infrastructure (VDI) and migrate it to Windows Virtual Desktop in Azure.

Data: Migrate large amounts of data to Azure quickly and cost-effectively using Azure Data Box products.

Based on this information let's analyze each option:

NYC-FS01 : Its role "Server" fall under above categories. Hence it can be accessed by using Azure migrate.

BOS-DB01 : Its role "server" fall under above categories. Hence it can be accessed by using Azure migrate.

Sea-CA01 : Its role "CA" does not fall under above categories. Hence it can not be accessed by using

Azure migrate.

Hou-NW01 : Its role "DNS" does not fall under above categories. Hence it can not be accessed by using Azure migrate.

Sea-DC01 : Its role "DC" does not fall under above categories. Hence it can not be accessed by using

Azure migrate.

Reference:

https://docs.microsoft.com/en-us/azure/migrate/migrate-services-overview

Scale up ASP1 : Correct

Basic App service plan does not support backup/restore.

The Backup and Restore feature requires the App Service plan to be in the Standard, Premium or Isolated tier. Since in question it is mentioned as a Basic service plan app so at first you need to do it to Scale up the service plan so that backup can be enabled on App1.

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.

Configure a WebJob for App1 : Incorrect

WebJobs is a feature of Azure App Service that enables you to run a program or script in the same instance as a web app, API app, or mobile app. There is no additional cost to use WebJobs

Scale out ASP1 : Incorrect

Scale out: Increase the number of VM instances that run your app. You can scale out to as many as 30 instances, depending on your pricing tier.

Configure the application settings for App1 : Incorrect

This is the 2nd step you need to perform once azure service plan upgraded to standard.

Most folks don't realize how easy it is to configure a backup copy of your Azure App Service to ensure you have restorable archive copies of your app and database. In order to take advantage of this, you'll need to log into your Azure account and go to your App Service that you created and look under Settings then you will see Backup

Reference:

https://azure.microsoft.com/en-in/pricing/details/app-service/windows/

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

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

https://microsoft.github.io/AzureTipsAndTricks/blog/tip28.html

Box 1: From the Scale up (App Service Plan) settings blade, change the pricing tier

The B1 pricing tier only allows for 1 core. We must choose another pricing tier.

Box 2: From the Scale out (App Service Plan) settings blade, enable autoscale

1. Log in to the Azure portal at http://portal.azure.com

1. Navigate to the App Service you would like to autoscale.

2. Select Scale out (App Service plan) from the menu

3. Click on Enable autoscale. This activates the editor for scaling rules.

Box 3: From the Scale mode to Scale based on metric, add a rule, and set the instance limits.

Click on Add a rule. This shows a form where you can create a rule and specify details of the scaling.

Reference:

https://azure.microsoft.com/en-us/pricing/details/app-service/windows/

https://blogs.msdn.microsoft.com/hsirtl/2017/07/03/autoscaling-azure-web-apps/

Box 1: storageaccount1 and storageaccount2 only

Box 2: All the storage accounts

Note: The three different storage account options are: General-purpose v2 (GPv2) accounts, Generalpurpose v1 (GPv1) accounts, and Blob storage accounts.

General-purpose v2 (GPv2) accounts are storage accounts that support all of the latest features for blobs, files, queues, and tables.

Blob storage accounts support all the same block blob features as GPv2, but are limited to supporting only block blobs.

General-purpose v1 (GPv1) accounts provide access to all Azure Storage services, but may not have the latest features or the lowest per gigabyte pricing.

Reference: https://docs.microsoft.com/en-us/azure/storage/common/storage-account-options

Ensure port 445 is open: The SMB protocol requires TCP port 445 to be open; connections will fail if port 445 is blocked.

Reference: https://docs.microsoft.com/en-us/azure/storage/files/storage-how-to-use-files-windows

Step 1: Stop VM1.

Step 2: Detach Disk1 from VM1.

Step 3: Start VM1.

Detach a data disk using the portal

In the left menu, select Virtual Machines.

Select the virtual machine that has the data disk you want to detach and click Stop to deallocate the VM.

In the virtual machine pane, select Disks.

At the top of the Disks pane, select Edit.

In the Disks pane, to the far right of the data disk that you would like to detach, click the Detach button image detach button.

After the disk has been removed, click Save on the top of the pane.

In the virtual machine pane, click Overview and then click the Start button at the top of the pane to restart the VM.

The disk stays in storage but is no longer attached to a virtual machine.

Step 4: Attach Disk1 to VM2

Attach an existing disk

Follow these steps to reattach an existing available data disk to a running VM.

Select a running VM for which you want to reattach a data disk.

From the menu on the left, select Disks.

Select Attach existing to attach an available data disk to the VM.

From the Attach existing disk pane, select OK.

Reference:

https://docs.microsoft.com/en-us/azure/virtual-machines/windows/detach-disk

https://docs.microsoft.com/en-us/azure/lab-services/devtest-lab-attach-detach-data-disk

We cannot just move a virtual machine between networks. What we need to do is identify the disk used by the VM, delete the VM itself while retaining the disk, and recreate the VM in the target virtual network and then attach the original disk to it.

First action: Delete VM1

Second action: Create a new virtual machine

Reference:

https://docs.microsoft.com/en-us/archive/blogs/canitpro/step-by-step-move-a-vm-to-a-differentvnet-on-azure

https://4sysops.com/archives/move-an-azure-vm-to-another-virtual-network-vnet/#migrate-anazure-vmbetween-vnets

Azure Backup provides backup for virtual machines ó created through both the classic deployment model and the Azure Resource Manager deployment model ó by using custom-defined backup policies in a Recovery Services vault.

With the release of backup policy management, customers can manage backup policies and model them to meet their changing requirements from a single window. Customers can edit a policy, associate more virtual machines to a policy, and delete unnecessary policies to meet their compliance requirements.

Incorrect Answers:

You can't delete a Recovery Services vault if it is registered to a server and holds backup data. If you try to delete a vault, but can't, the vault is still configured to receive backup data.

Reference:

https://azure.microsoft.com/en-in/updates/azure-vm-backup-policy-management/

You can find unused disks in the Azure Storage Explorer console.Once you drill down to the Blob containers under a storage account, you can see the lease state of the residing VHD (the lease state determines if the VHD is being used by any resource) and the VM to which it is leased out. If you find that the lease state and the VM fields are blank, it means that the VHD in question is unused. The screenshot below shows two active VHDs being used by VMs as data and OS disks. The name of the VM and lease state are shown in the "VM Name" and "Lease State" columns, respectively.

Reference:

https://cloud.netapp.com/blog/reduce-azure-storage-costs