You attempt to delete a user who owns content on a Tableau Server.

Deleting a user in Tableau Server involves handling their owned content (workbooks, data sources)—let’s analyze the process:

Deletion Rules:

Ownership Check: Tableau prevents deletion if the user owns content to avoid orphaning it.

Action: Instead of deleting, the user’s site role is set toUnlicensed, retaining their account and content ownership.

Resolution: An admin must reassign ownership (e.g., viaUsers > Actions > Change Owner) before deletion.

Option D (User switched to Unlicensed and NOT deleted): Correct.

Details: Attempting deletion (e.g.,Users > Select User > Actions > Delete) triggers a check. If content exists, the user becomes Unlicensed—still in the system but unable to log in.

Why: Protects data integrity—content remains accessible for reassignment.

Option A (Deleted, content to server admin): Incorrect.

Why: No automatic reassignment to the server admin—manual action is required first.

Option B (Deleted, content to project leader): Incorrect.

Why: Project leaders don’t automatically inherit content—no such mechanism exists.

Option C (User and content deleted): Incorrect.

Why: Tableau avoids deleting content with the user—too destructive without explicit intent.

Why This Matters: This safeguard prevents accidental data loss, ensuring admins manage ownership transitions deliberately.