Tableau Server supports multi-tenancy via sites, each with customizable settings managed by server or site administrators. Let’s analyze what’s configurable per site:

Site Settings : Found in the web UI under Site > Settings > General . Server admins can override site admin settings.

Option B (Limitation on storage space) : Correct.

Details : Server admins can set a storage quota per site (e.g., 100 GB) to cap disk usage for extracts and workbooks.

How : In TSM or site settings (if enabled)—e.g., tsm configuration set -k site.storage.quota -v 100000.

Impact : Prevents one site from monopolizing resources in multi-site deployments.

Option D (Language and locale) : Correct.

Details : Each site can set its language (e.g., English, French) and locale (e.g., date/number formats).

How : Site settings UI—e.g., " Language: French, Locale: France. "

Impact : Tailors the user experience per site’s audience.

Option A (Ability to embed credentials) : Incorrect.

Details : Embedding credentials (e.g., in data sources) is a server-wide setting (tsm data-access), not per-site. Site admins can’t override it.

Option C (Limitation on number of users) : Incorrect.

Details : User limits are tied to licenses (server-wide), not configurable per site. Site admins manage user assignments, not quotas.

Why This Matters : Site-specific settings enable tailored governance and resource allocation in multi-tenant environments.

Importing an AD group into Tableau Server syncs user management—let’s analyze the process and options:

AD Group Import Process :

How : In the UI ( Users > Groups > Add Group > Active Directory ), enter the AD group name, set a site role, and sync.

Behavior :

Existing Users : If a user is already in Tableau Server, their site role remains unchanged unless manually adjusted—sync applies the minimum role only if it upgrades access.

New Users : Added to Tableau with the site role specified during import.

Config : Requires AD authentication enabled in TSM.

Option D (New users created are assigned the site role specified during import) : Correct.

Details : When importing (e.g., " SalesTeam " group, site role: Explorer):

New users get Explorer.

Existing users keep their role unless it’s below Explorer (e.g., Unlicensed → Explorer).

Why : Ensures consistent onboarding—new users align with the group’s intended access.

Option A (Existing users’ roles change to match import) : Incorrect.

Why : Existing roles persist unless lower than the minimum—e.g., Viewer stays Viewer if import sets Explorer, but Unlicensed upgrades. Not a full overwrite.

Option B (Requires a .csv file) : Incorrect.

Why : AD import uses live sync via LDAP—no .csv needed (that’s for local auth imports).

Option C (Change group name during import) : Incorrect.

Why : The AD group name is fixed—you can’t rename it in Tableau during sync (it mirrors AD). Post-import renaming is possible but not part of the process.

Why This Matters : Accurate AD sync ensures seamless user management—missteps can disrupt access or licensing.

In Tableau Server, roles and permissions dictate who can perform specific administrative tasks. A " server administrator " has full control over the entire Tableau Server deployment, while site administrators manage specific sites. Some tasks are restricted to server administrators due to their server-wide impact.

Option B (Adding a site): Creating a new site in a multi-site Tableau Server environment is a server-level task that only a server administrator can perform. Sites are logical partitions within the server, and adding a site affects the overall server structure. Site administrators cannot create new sites; they can only manage existing ones.

Option D (Adding users): Adding users to Tableau Server (e.g., via the TSM interface or tabcmd) is a server administrator task when it involves adding users at the server level or assigning them to the default site. While site administrators can add users to their specific site in a multi-site environment, the initial addition of users to the server requires server administrator privileges. The question’s phrasing (“always require”) suggests a server-wide context, making this a correct choice.

Option A (Creating a schedule): This is incorrect because both server administrators and site administrators can create schedules for tasks like extract refreshes or subscriptions within their scope. It’s not exclusive to server administrators.

Option C (Locking project permissions): This is incorrect because locking project permissions can be done by a site administrator or project leader with appropriate permissions. It’s a project-level action, not a server-level task requiring a server administrator.

TSM is Tableau Server’s management layer, accessible via CLI or web UI (port 8850). HTTPS secures this access—let’s identify the responsible process:

TSM Architecture :

Administration Controller : Core TSM process, running on the initial node, handling configuration, UI, and CLI commands.

HTTPS : Enabled by default on port 8850 with a self-signed certificate (configurable to custom certs).

Option B (Administration Controller) : Correct.

Details : Hosts the TSM web UI (https:// < server > :8850) and processes CLI requests. It manages the HTTPS listener, serving the interface securely.

Why : It’s the central hub for TSM operations, including secure access.

Option A (License Manager) : Incorrect.

Why : Validates licenses, not responsible for HTTPS or UI access.

Option C (Administration Agent) : Incorrect.

Why : Runs on additional nodes in multi-node setups to relay commands to the Controller—no direct HTTPS role.

Option D (Coordination Service) : Incorrect.

Why : ZooKeeper manages cluster state, not TSM’s web interface or HTTPS.

Why This Matters : Secure TSM access protects server administration—Administration Controller is the linchpin.

Table recommendations in Tableau Server suggest popular tables and data sources to users when they create new content in the web authoring environment. This feature is enabled by default but can be disabled at the site level.

Option A (Disable the option using the site Settings page): Correct. A site administrator can disable table recommendations by navigating to the site’s Settings > General page in the Tableau Server web interface and unchecking the option " Enable table recommendations. " This prevents users on that site from seeing these suggestions, offering a straightforward UI-based solution.

Option B (Use the command: tsm configuration set -k recommendations.enabled -v false): Incorrect. There is no recommendations.enabled key in the TSM configuration settings. This feature is managed per site, not server-wide via TSM.

Option C (Publish data sources only to projects with permissions locked): Incorrect. Locking permissions restricts access but doesn’t disable the recommendation feature itself. Users with access would still see recommendations.

Option D (Disable the option using the server Settings page): Incorrect. Table recommendations are a site-specific setting, not a server-wide setting. The server Settings page (via TSM) controls global configurations, not this feature.

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 to Unlicensed , retaining their account and content ownership.

Resolution : An admin must reassign ownership (e.g., via Users > 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.