Which of the following statements about the Samba 3 server are true? (Select THREE correct answers.)

While Samba 3 could act as a Primary Domain Controller (PDC) for an NT4-style domain, it could *not* function as a full Active Directory Domain Controller (DC) for an ADS domain; that functionality was introduced with Samba 4.

Samba 3 servers were capable of joining an Active Directory (ADS) domain as a member server, allowing them to authenticate users against the ADS domain controllers and participate in the domain as a file and print server.

Provided the necessary UNIX groups are created and mapped, Samba 3 could automatically map Windows Security Identifiers (SIDs) to UNIX GIDs for groups, which is essential for consistent access control between Windows and UNIX environments when sharing resources.

User and group IDs are *not* mapped to an LDAP backend by default in Samba 3; administrators must explicitly configure `idmap backend` directives in `smb.conf` to enable LDAP-based ID mapping.

Samba 3 supported LDAP as a backend for storing user and group information, including password hashes, through modules like `passdb backend = ldapsam`. This enabled centralized user management where Samba could query and update passwords directly in an LDAP directory.