Q: 3
You have an Active Directory Domain Services (AD DS) domain. The domain contains three servers named Server 1, Server2, and Server3 that run Windows Server. You sign in to Server1 by using a domain account and start a remote PowerShell session to Server2. From the remote PowerShell session, you attempt to access a resource on Server3. but access to the resource is denied. You need to ensure that your credentials are passed from Server1 to Server3. The solution must minimize administrative effort. What should you do?
Options
Discussion
Option A makes sense here since it's the double-hop issue with PowerShell remoting. Kerberos constrained delegation lets Server2 pass your credentials on to Server3 securely. I think that's the least work for admins too, but open if anyone sees a catch.
I don’t think it’s D. 6516 is used if you pick a custom port, but here the question says default install. A makes sense since Windows Admin Center listens on 443 out of the box for HTTPS. Some might confuse it with RDP (3389) but that's not needed for WAC. Pretty sure A is right, unless I missed something.
I’d say A, since default WAC gateway uses 443, not 6516 like some might assume.
A is what I've seen in similar exam reports, Windows Admin Center defaults to 443 unless you set something custom.
A , 3389 is RDP and D is a common trap here.
A tbh
Option D seems possible if the defaults were actually changed during setup. I remember reading that 6516 is sometimes used for Windows Admin Center but not by default. Pretty sure A is right if you go with a standard install, but I might be mixing that up.
Probably A, 3389 is tempting but that's for RDP not WAC, seen similar in practice tests.
A
Yeah A is the way to go here, since Windows Admin Center uses 443 by default for web access. If you picked something else during setup, it could be different, but defaults mean HTTPS. Anyone see this behave differently?
Be respectful. No spam.