AZ-800 Question #230: Real Exam Question with Answer & Explanation

Question

SIMULATION You need to configure Hyper-V to ensure that running virtual machines can be moved between SRV1 and SRV2 without downtime. You do NOT need to move any virtual machines at this time. To complete this task, sign in the required computer or computers. Answer: Windows Server, Hyper-V, Set up hosts for live migration without Failover Clustering You can set up hosts that aren't clustered so you can do live migrations between them. Phase 1: Configure constrained delegation (optional) [Skip] If you have decided to use Kerberos to authenticate live migration traffic, configure constrained delegation using an account that is a member of the Domain Administrators group. Phase 2: Set up the source and destination computers for live migration This step includes choosing options for authentication and networking. Use Hyper-V Manager to set up the source and destination computers for live migration Step 1: Open Hyper-V Manager. (From Server Manager, click Tools >>Hyper-V Manager.) Step 2: In the navigation pane, select one of the servers. (If it isn't listed, right-click Hyper-V Manager, click Connect to Server, type the server name, and click OK. Repeat to add more servers.) [Here: SRV1] Step 3: In the Action pane, click Hyper-V Settings >>Live Migrations. Step 4: In the Live Migrations pane, check Enable incoming and outgoing live migrations. Step 5: Under Simultaneous live migrations, specify a different number if you don't want to use the default of 2. Step 6: Under Incoming live migrations, if you want to use specific network connections to accept live migration traffic, click Add to type the IP address information. Otherwise, click Use any available network for live migration. Click OK. Step 7: To choose Kerberos and performance options, expand Live Migrations and then select Advanced Features. If you have configured constrained delegation, under Authentication protocol, select Kerberos. Under Performance options, review the details and choose a different option if it's appropriate for your environment. Step 8: Click OK. Step 9: Select the other server [Here SRV2] in Hyper-V Manager and repeat the steps. Reference: https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/set-up-hosts-for- live-migration-without-failover-clustering

Options

• ALACP teaming mode
• BSwitch Embedded Teaming (SET)
• CLoad balancing and failover (LBFO)
• DStatic teaming mode

Explanation

This question is malformed, as the choices presented are unrelated to the initial task of configuring Hyper-V for live migration, instead focusing on network adapter teaming options. However, Switch Embedded Teaming (SET) is highly recommended for Hyper-V environments.

Common mistakes.

• A. LACP teaming mode is a general-purpose NIC teaming standard that does not provide the specific Hyper-V integration and performance benefits offered by SET.
• C. Load Balancing and Failover (LBFO) is the traditional Windows NIC Teaming solution, which provides basic fault tolerance and load balancing but lacks the Hyper-V-specific optimizations of SET.
• D. Static teaming mode is a fundamental NIC teaming configuration that offers less flexibility and fewer advanced features compared to SET for Hyper-V deployments.

Concept tested. Switch Embedded Teaming (SET) for Hyper-V networking

Reference. https://learn.microsoft.com/en-us/windows-server/networking/technologies/nic-teaming/set-overview

No community discussion yet for this question.