Q: 2
You have a server that runs Windows Server 2022 and has the network adapters shown in the following table. 
You need to configure NIC learning for LAN2 and LAN3. The solution must support Dynamic Virtual Machine Multi-Queue (d.VMMQ). What should you use?
Options
Discussion
B is correct for this one. SET is the only teaming option that works with d.VMMQ on Server 2022, since LBFO and traditional teaming methods don't support it. Pretty sure Microsoft specifically calls this out in the docs. If anyone has seen d.VMMQ working with LBFO, let me know!
A
Option B since forwarding everything creates a single point of failure trap for Server2/3.
B makes more sense for me. If Server1 goes down or isn't reachable for some reason, then forwarding everything to it from Server2 and Server3 could stop name resolution for both internal and external names. Without redundancy or secondary forwarders, that's risky. I think I'm missing something, so let me know if you disagree.
My vote is A, since forwarding to Server1 means it can handle both internal delegations and root hint lookups for internet hosts. Unless there's some weird config missing. Anyone else think differently?
Its B, unless Server1 is unreachable or misconfigured, Server2 and Server3 might not resolve external names consistently. Edge case but possible.
For me, A. Perfectly clear scenario, matches similar questions in recent dumps.
Probably B, since only Switch Embedded Teaming supports d.VMMQ, LBFO is a common trap here.
A , this works since Server2 and Server3 forward to Server1, which has the parent zone and the delegations so resolution flows. Root hints cover internet. Only thing missing is redundancy but the scenario doesn't require it. Let me know if you see a catch?
Official MS docs and practice exams cover this setup the same way, so I'd trust those if you're double checking.
Be respectful. No spam.
