Tableau Server has specific hardware requirements for production environments to ensure stability and performance. The minimum recommended free disk space for a production installation is 50 GB . This accounts for:

The installation itself (approximately 1–2 GB).

Space for log files, temporary files, and extracts managed by the File Store and Data Engine.

Room for backups and operational overhead.

The full minimum hardware recommendations for a single-node production deployment are:

8 CPU cores (2.0 GHz or faster).

32 GB RAM .

50 GB free disk space (on the system drive, typically C: on Windows).

Option A (32 GB) : Incorrect. While 32 GB is the minimum RAM requirement, it’s insufficient for disk space in production.

Option B (50 GB) : Correct. This matches Tableau’s official recommendation for production environments.

Option C (15 GB) : Incorrect. 15 GB is the minimum for a non-production or trial installation, not production.

Option D (64 GB) : Incorrect. While 64 GB exceeds the minimum, it’s not the specified requirement—50 GB is sufficient.

Tableau Server uses internal secrets (tokens) for secure communication between its processes (e.g., Repository, File Store). These are automatically generated during installation and can be regenerated if compromised or for security maintenance. The command to update these is:

tsm security regenerate-internal-tokens : This regenerates the internal security tokens, ensuring all processes use the new tokens after a restart.

Option C (tsm security regenerate-internal-tokens) : Correct. This is the documented command for updating internal secrets.

Option A (tsm data-access caching set -r 1) : Incorrect. This command configures caching behavior, not security tokens.

Option B (tsm licenses refresh) : Incorrect. This refreshes license data, unrelated to internal secrets.

Option D (tsm security validate-asset-keys) : Incorrect. This validates encryption keys for assets, not internal tokens.

Single Sign-On (SSO) allows users to authenticate once (e.g., via a corporate identity provider) and access Tableau Server without re-entering credentials. Tableau Server supports several SSO methods:

OpenID Connect (OIDC) : An OAuth 2.0-based protocol for SSO, configured via Tableau’s SAML settings with an OIDC-compatible IdP (e.g., Google, Okta).

Kerberos with Active Directory : A ticket-based SSO protocol, widely used in Windows environments with AD integration.

SAML : A flexible SSO standard using XML assertions, supporting various IdPs (e.g., ADFS, PingFederate).

Let’s evaluate:

Option A (OpenID Connect) : Correct. OIDC is an SSO method, implemented as a SAML variant in Tableau Server, enabling seamless login.

Option C (Kerberos with Active Directory) : Correct. Kerberos provides SSO in AD environments, delegating authentication to the domain controller.

Option D (Security Assertion Markup Language - SAML) : Correct. SAML is a core SSO method in Tableau, widely adopted for enterprise integrations.

Option B (Local Authentication) : Incorrect. Local Authentication uses Tableau’s internal user database, requiring manual credential entry—no SSO support.

Why This Matters : SSO enhances user experience and security by leveraging existing identity systems, reducing password fatigue.

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.

TSM commands manage Tableau Server maintenance—let’s validate their syntax:

Command Requirements :

Some need arguments (e.g., file paths); others are standalone.

Valid and Complete : Must work as-is without errors.

Option C (tsm maintenance cleanup) : Correct.

Details : Removes temporary files and old logs—no arguments required (optional flags like -l exist).

Use : tsm maintenance cleanup—runs fully.

Option D (tsm maintenance ziplogs) : Correct.

Details : Creates a zip of logs (e.g., tsm-logs.zip)—no arguments needed (optional -d for date range).

Use : tsm maintenance ziplogs—complete and valid.

Option A (tsm maintenance backup) : Incorrect.

Why : Requires -f < filename > .tsbak (e.g., tsm maintenance backup -f backup.tsbak)—incomplete without it.

Option B (tsm maintenance restore) : Incorrect.

Why : Needs -f < filename > .tsbak (e.g., tsm maintenance restore -f backup.tsbak)—not standalone.

Why This Matters : Correct syntax ensures maintenance tasks execute without errors—critical for server health.

Editing permissions on a workbook in Tableau Server depends on the user’s role and the project’s permission settings. Since permissions are not locked (i.e., "Managed by Owner"), let’s dissect who can edit them:

Permission Model :

Not Locked : Owners of content (workbooks, data sources) can set permissions, and Project Leaders can override at the project level.

Site Roles : Define maximum capabilities (e.g., Viewer, Explorer, Creator).

Capabilities : "Set Permissions" is explicit—only certain users get it.

Option C (The workbook’s owner) : Correct.

Details : The owner (typically the publisher) has full control over their workbook when permissions are Managed by Owner:

How : In the UI, go to Content > Workbooks > Actions > Permissions —owners can edit rules (e.g., grant Editor to a group).

Site Role : Minimum of Explorer (can publish) or Creator to publish, ensuring "Set Permissions" capability.

Why : Ownership inherently includes permission management unless locked.

Option D (Users set to Project Leader for the workbook’s project) : Correct.

Details : Project Leaders are assigned via Content > Projects > Actions > Permissions > Set Project Leader :

Power : Can edit permissions for all content in the project, even if not the owner.

Site Role : Requires Site Administrator or Server Administrator (Creator/Explorer variants suffice).

Why : Overrides ownership in Managed by Owner mode—ensures project-level governance.

Option A (Users with project and workbook Viewer role) : Incorrect.

Why : Viewer role (site-level) limits users to viewing—lacks "Set Permissions" capability, regardless of project/workbook rules.

Option B (Users with workbook Interactor role) : Incorrect.

Why : "Interactor" isn’t a standard role—likely a misnomer for Explorer or Viewer with interaction permissions (e.g., Filter). No permission-editing rights exist here.

Why This Matters : Knowing who can edit permissions prevents access control gaps—crucial for collaborative or regulated environments.