How is the user user01 from DOMA granted the right to manage printers on a Samba print server?

Question

Options

• Anet ads rights 'DOMA\user01' +SePrintOperatorPrivilege
• Bnet -S server -U domadmin rpc rights grant 'DOMA\user01' SePrintOperatorPrivilege
• Cpdbedit --user=user01 -I=DOMA --policies=SePrintOperatorPrivilege
• Dpdbedit DOMA\user01 +PrintOperator
• Ecupsaddsmb DOMA\user01 +PrintOperator

• A
  8% (3)
• B
  74% (28)
• C
  3% (1)
• D
  3% (1)
• E
  13% (5)

Explanation

Option B is correct because net rpc rights grant is the proper Samba command for assigning privileges to domain users - it connects to the server (-S server), authenticates as a domain admin (-U domadmin), and grants SePrintOperatorPrivilege, which is the Windows privilege token that allows a user to manage printers on a Samba print server.

Why the distractors are wrong:

• A uses net ads rights, which is not a valid subcommand - net ads is used for Active Directory operations like joining a domain, not privilege assignment.
• C uses pdbedit with fabricated flags (-I, --policies) - pdbedit manages the Samba user database (passwords, account info), not privilege rights.
• D also uses pdbedit with a +PrintOperator syntax that doesn't exist in Samba; this looks like a confused mix of Linux group syntax.
• E uses cupsaddsmb, which is a tool for installing Windows printer drivers into Samba shares - it has nothing to do with user privilege assignment.

Memory tip: Think "RPC = Rights Privilege Command" - the net rpc rights grant chain is the only one that contains all three necessary elements: the transport (rpc), the action (rights grant), and the privilege token (SePrintOperatorPrivilege). If you see SePrintOperatorPrivilege, the correct tool is always net rpc rights grant.

No community discussion yet for this question.