An administrator wants to allow users to login to the vSphere Web Client using the Use Windows session authentication check box for faster authentication. Which three requirements must be met for this

The Client Integration plug-in is installed on each client workstation, not on the vCenter Server or Platform Services Controller - installing it server-side has no effect on enabling the feature for end users.

The Client Integration plug-in must be installed on each user's workstation because it provides the browser-level hook that captures the current Windows Kerberos token and passes it to vCenter for authentication. Without it on the local machine, the 'Use Windows session authentication' checkbox is not available in the browser. This is a per-client requirement, not a server-side installation.

The feature relies on pass-through of the currently active Windows session credentials, so the user must be authenticated to Windows via an Active Directory domain account - local accounts cannot be forwarded to vCenter SSO.

vCenter SSO must have a valid Identity Source configured for the user's AD domain so it can validate the forwarded Kerberos credentials against a known directory service.

This option rephrases the Identity Source requirement already covered by D; configuring a standard AD Identity Source in SSO is sufficient and 'Integrated Windows Authentication' as a separate distinct step is not a separate requirement.