An administrator must configure identity access for VMware vSphere Foundation (VVF) to allow admin accounts from the enterprise Active Directory domain corp.local to log in using domain credentials…

Question

Options

• AAdd the domain controller certificate to the Trusted Root store in vCenter.
• BConfigure Identity Federation using SAML with corp.local.
• CConfigure a trusted identity provider using OpenID Connect (OIDC).
• DAdd Active Directory over LDAP as an identity source.

• A
  5% (1)
• B
  14% (3)
• C
  5% (1)
• D
  76% (16)

Explanation

Adding Active Directory over LDAP as an identity source (D) is the correct step because vCenter natively supports AD over LDAP as a built-in identity source, allowing domain users to authenticate using standard AD credentials without any federation technology - exactly what "default Active Directory protocol, without federation" describes.

Why the distractors are wrong:

• A - Adding a domain controller certificate to the Trusted Root store is only needed for LDAPS (secure LDAP), not to enable AD authentication itself; the certificate alone doesn't configure an identity source.
• B - Identity Federation with SAML is an entirely different authentication model that uses a federated identity provider (like AD FS or Okta), which the question explicitly rules out by saying "without federation."
• C - OpenID Connect (OIDC) is also a federation/modern-auth protocol - used when configuring an external identity provider - not the native AD/LDAP integration vCenter offers out of the box.

Memory tip: Think of it this way - "default AD protocol" = LDAP. vCenter's identity source menu has two AD options: AD (Windows Integrated) and AD over LDAP. When you need to manually point vCenter at a specific domain, you pick AD over LDAP - that's your go-to for standard, non-federated domain auth.

No community discussion yet for this question.