AnswerA
ExplanationSupported Directory Services: Pure Storage FlashArray File Services (FA File) is designed to integrate seamlessly into existing enterprise identity infrastructures. To manage file permissions (SMB ACLs and NFS POSIX/NFSv4 permissions), Purity supports joining the array to a directory service.
Active Directory (AD): This is the most common integration for FA File, specifically for SMB environments. Purity allows the array to join an AD Domain, creating a computer account and enabling the resolution of SIDs to usernames.
OpenLDAP: For Linux/Unix-heavy environments using NFS, Purity supports OpenLDAP. This allows the array to look up UID/GID information and group memberships to enforce security across the file system.
Authentication vs. Management: It is important to distinguish between Data Access (FA File) and Management Access (GUI/CLI login).
FA File (Data Access): Uses AD and OpenLDAP to authorize users accessing shares/exports.
Management (GUI/CLI): Uses SAML (Option C) or LDAP for Single Sign-On (SSO) (Option B) to allow administrators to log into the array.
The 'Either/Or' Logic: While a FlashArray can be configured with multiple directory services, for a specific File System/Export mapping, the system relies on the primary identity provider configured---either Microsoft AD or an LDAP-compliant service like OpenLDAP---to validate the users' identity.