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.
Reference: Tableau Server Documentation - "Manage Site Settings" (https://help.tableau.com/current/server
/en-us/site_settings.htm).

Trusted Tickets is an authentication method in Tableau Server for embedding views in external applications (e.g., portals) without requiring users to log in manually. Here's how it works:
A trusted application (e.g., a web server) authenticates with Tableau Server using a trusted IP or username/password.
Tableau Server issues a temporary ticket (a unique string). The ticket is embedded in a view URL (e.g., /trusted/<ticket>/views/...), granting access to the view for a short period (configurable, default 5 minutes).
Option A (Access embedded views without being prompted for credentials): Correct. Trusted tickets enable SSO-like behavior for embedded content, bypassing the login prompt if the ticket is valid. This is ideal for seamless integration into external systems.

When Tableau Server uses Active Directory (AD) for authentication, group synchronization imports AD groups and assigns a minimum site role (e.g., Viewer, Explorer) to users in that group. This ensures users meet a baseline access level. The behavior for existing users during sync is:
If the user's current site role provides more access than the minimum (e.g., Explorer vs. Viewer), their role remains unchanged.
If the user's current role provides less access than the minimum (e.g., Unlicensed vs. Viewer), their role is upgraded to the minimum.
This preserves higher privileges while enforcing a floor. "Reduces access" means the minimum role is lower than the current role (e.g., Viewer vs. Explorer), in which case the existing role stays.
Option A (It will change to the minimum site role only if the minimum site role reduces access):
Correct. The user's role changes only if the minimum increases access (e.g., Unlicensed to Viewer); otherwise, it stays higher.

In an HA Tableau Server cluster, the Coordination Service (ZooKeeper ensemble) maintains cluster state--let's find the best way to check it:
Coordination Service:
Runs on multiple nodes (3 or 5 in HA) to ensure quorum and failover. Status indicates if it's running and synced--critical for cluster health.
Option C (Run tsm status -v): Correct.
Details: tsm status --verbose lists all processes across nodes, including Coordination Service (e.g., "Coordination Service: RUNNING").
Why Best: Provides detailed, node-specific status in the CLI--e.g., "Node 1: RUNNING, Node 2:
RUNNING."
Use: Run on the initial node; -v ensures full output.

Tableau Server relies on several processes to function, each with a specific role. The Repository process (powered by PostgreSQL) serves as the database for metadata, storing critical information such as:
User and group details.
Permissions and site configurations.
Workbook and data source metadata (e.g., schedules, subscriptions). Option B (Repository):
Correct. The Repository is the centralized database that holds all metadata, making it the backbone of Tableau Server's content management. There are typically two instances in an HA setup (one active, one passive), monitored by the Cluster Controller.