- 1 перегляд
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You deploy Azure Migrate to an on-premises network.
You have an on-premises physical server named Server1 that runs Windows Server and has the following configurations:
• Operating system disk: 600 GB
• Data disk: 3 TB
• NIC Teaming: Enabled
• Mobility service: Installed
• Windows Defender Firewall: Enabled
• Microsoft Defender Antivirus: Enabled
You need to ensure that you can use Azure Migrate to migrate Server1.
Solution: You shrink the data disk on Server1.
Does this meet the goal?
- A. Yes
- B. No
- B. No
[Removed]
2 months, 3 weeks ago
Answer: Option B. No. Explanation: Shrinking the data disk on Server1 is not necessary for Azure Migrate, as Azure can handle large disk sizes like the 3 TB data disk. This action does not address any specific requirements or limitations for migrating a server to Azure using Azure Migrate.
upvoted 2 times
Said_kram
3 months, 1 week ago
NIC Teaming not supported https://learn.microsoft.com/en-us/azure/migrate/migrate-support-matrix-hyper-v-migration#hyper-v-vms
upvoted 3 times
smith288
4 months, 1 week ago
Correct. I say the issue is the Mobility service being install. "It is unsupported to install the Azure Migrate Appliance on a server that has the replication appliance or mobility service agent installed. Ensure that the appliance server has not been previously used to set up the replication appliance or has the mobility service agent installed on the server." https://learn.microsoft.com/en-us/azure/migrate/tutorial-discover-physical