Which of the following commands exist to define the passwd database entries generated by winbind? (Choose two.)

Question

Options

• Atemplate homedir
• Btemplate gid
• Ctemplate uid
• Dtemplate shell
• Etemplate password

• A
  82% (45)
• B
  11% (6)
• C
  2% (1)
• E
  5% (3)

Explanation

When winbind generates Unix passwd entries for Windows domain users, it must supply values for fields that Active Directory doesn't natively provide in Unix format - specifically the home directory (template homedir, e.g., /home/%D/%U) and the login shell (template shell, e.g., /bin/bash). These are both legitimate smb.conf directives that winbind reads to synthesize complete /etc/passwd-style entries.

The distractors fail because UID and GID ranges for winbind users are configured using winbind uid and winbind gid (no "template" prefix) - the template uid and template gid variants simply don't exist as valid parameters. template password is also invalid; authentication credentials are handled via Kerberos/NTLM, not a static template value.

Memory tip: Think about what a standard /etc/passwd entry needs that AD can't supply automatically - a Unix home directory path and a shell. Those two missing pieces are exactly what the two template directives cover.

No community discussion yet for this question.