Free Analytics-Admn-201 Practice Test Questions and Answers (2026)

Tableau Server supports Kerberos constrained delegation only for data connectors whose ODBC/JDBC drivers are written to accept the forwarded Kerberos ticket. According to Tableau Server Help, the supported connectors are Microsoft SQL Server, SAP HANA, and Teradata. When Kerberos is enabled on Tableau Server and delegation is configured in Active Directory, a viewer’s Kerberos ticket can be forwarded to these three databases so that the database enforces its own row-level security. PostgreSQL’s driver does not accept a delegated ticket; therefore, Kerberos single sign-on to PostgreSQL from Tableau Server is not possible.

B. PostgreSQL – Tableau can use username/password or OAuth, but its driver cannot consume a delegated Kerberos ticket; delegation configuration is not supported.

1. Tableau Server Help “Configure Kerberos Delegation for SSO to Data Sources,” Tableau 2023.3, Section “Supported Connectors” (lists Microsoft SQL Server, SAP HANA, Teradata).

https://help.tableau.com/current/server/en-us/kerberosdelegation.htm

2. Tableau Server Help “Kerberos Database Connections,” 2023.3, Paragraph 2 (states PostgreSQL not supported for delegation).

https://help.tableau.com/current/server/en-us/kerberosdatabase.htm

3. Tableau Whitepaper “Kerberos in Tableau Server,” v2022-01, p. 6-7 (Supported Data Sources table).

4. MIT OpenCourseWare 6.858 Lecture Notes “Kerberos Delegation,” Fall 2020, slide 15 (explains requirement that backend service accept delegated ticket; aligns with Tableau’s list).

In Salesforce report or dashboard subscriptions, recipients can be specified as public groups or roles. Salesforce evaluates the membership of those groups/roles each time the scheduled subscription runs. When a new user is added to the public group, the system automatically includes that user in the next execution of the subscription without any manual action or approval. Therefore, the subscription dynamically updates to reflect the current membership of the group.

A. No approval workflow exists for adding users to an already-subscribed group; inclusion is automatic.

B. The creator doesn’t need to edit the subscription; group membership is re-evaluated automatically.

D. Membership is not frozen at creation time; Salesforce reevaluates the group each run, so new users are included.

1. Salesforce Help, “Subscribe to Reports in Lightning Experience,” section “Add Others” – “If you add or remove users from a public group or role, the changes are reflected the next time the report runs.” (Doc ID: sf.reportssubscribelightning.htm, para 6, accessed 2025-11-28).

2. Salesforce Help, “Subscribe to Dashboards in Lightning Experience,” section “Add Recipients” – “New users added to a subscribed group or role begin receiving the dashboard on the next refresh.” (Doc ID: sf.dashboardssubscribe.htm, para 5).

3. Trailhead (Official Salesforce), “Report and Dashboard Subscriptions,” unit “Subscribe Others” – “When group membership changes, the subscription automatically updates for the next run.” (Trailhead Module URL, accessed 2025-11-28).

The tsm reset command is specifically designed to remove all configurations, content, and user data from a Tableau Server installation, effectively returning it to a pre-initialized state. After this command is executed, the server must be re-initialized. This re-initialization process requires the administrator to configure the server from scratch, which includes the mandatory step of creating a new initial administrator account. This directly addresses the requirement to set up a new administrator account upon the next login/setup attempt.

A. Edit tabsvc.yml: Manually editing the tabsvc.yml file is not the standard procedure for resetting an administrator account and is strongly discouraged unless directed by Tableau Support, as it can cause instability.

C. Run the tsm register command: The tsm register command is used exclusively for managing product keys and the registration of the Tableau Server software. It has no function related to user account management.

D. Reinstall Tableau Server: While a full reinstallation would achieve the goal, it is an unnecessarily drastic and time-consuming solution. The tsm reset command provides a more direct and efficient method to achieve the same outcome.

1. Tableau Server Help - tsm reset: "Use the tsm reset command to remove all configuration and return Tableau Server to the state it was in just after it was installed. ... After you run the tsm reset command, you must run the tsm initialize command..." The initialization process includes creating the initial administrator user.

Source: Tableau Official Documentation, tsm reset, https://help.tableau.com/current/server/en-us/clireset.htm

2. Tableau Server Help - Step 1: Install and Initialize TSM: This document outlines the initial setup process which is triggered after a fresh install or a tsm reset. Step 1.5 describes creating the initial administrator account.

Source: Tableau Official Documentation, Install and Configure Tableau Server, https://help.tableau.com/current/server/en-us/installinstall.htm (See section on initializing TSM).

3. Tableau Server Help - tsm licenses: This documentation details the commands for licensing, including register, confirming its purpose is unrelated to user accounts.

Source: Tableau Official Documentation, tsm licenses, https://help.tableau.com/current/server/en-us/clilicensestsm.htm

4. Tableau Server Help - tabsvc.yml Configuration File: This document explicitly warns against modifying the tabsvc.yml file without guidance from support.

Source: Tableau Official Documentation, Configuration File, https://help.tableau.com/current/server/en-us/configfile.htm

An administrator can create and manage content like groups and projects in Tableau Server through three primary methods. The Tableau Server browser interface is the standard graphical user interface for manual administration. For scripting and automation of administrative tasks, the tabcmd command-line utility provides specific commands such as createproject and creategroup. For more advanced programmatic control and integration with other systems, the Tableau Server REST API offers dedicated endpoints to create and manage projects and groups. These three methods provide comprehensive options for content management.

A. tsm customize: The tsm customize command is part of the Tableau Services Manager (TSM) toolset, which is used for server-level configuration and topology management, not content administration like creating projects or groups.

1. Tableau Server Browser Interface:

Source: Official Tableau Server Help Documentation

Reference: "Add Projects and Move Content" section. The documentation states, "As a server or site administrator, you can create projects... On the top-level Projects page, click New > Project." This confirms the use of the browser interface.

2. tabcmd:

Source: Official Tableau Server Help Documentation

Reference: "tabcmd Commands" page. The documentation lists createproject "projectname" and creategroup "groupname" as valid commands for creating projects and groups respectively via the command-line interface.

3. REST API:

Source: Official Tableau Server REST API Reference

Reference: The "Create Project" method (POST /api/api-version/sites/site-id/projects) and "Create Group" method (POST /api/api-version/sites/site-id/groups) are documented as the standard API calls for programmatically creating these resources.

4. tsm customize (for incorrect option):

Source: Official Tableau Server Help Documentation

Reference: "tsm customize" page. The documentation specifies that this command is used to "Customize the look and feel of the Tableau Server client browser experience," including server name, logo, and sign-in information, confirming it is not for content creation.

Tableau Server is an enterprise-level analytics platform designed for production environments, which requires a server-class operating system for stability, performance, and security. According to the official Tableau Server technical specifications, supported Microsoft Windows operating systems include Windows Server 2016 and Windows Server 2019. Client operating systems such as Windows 7 and Windows 10 are not supported for production installations of Tableau Server. The installer will block installation on these unsupported operating systems.

A. Windows 7 is an end-of-life client operating system and is not supported for Tableau Server installations.

B. Windows 10 is a client operating system and is not supported for production Tableau Server installations.

1. Tableau Help | Tableau Server: All Technical Specifications for Tableau Server on Windows. In the "Hardware and software requirements" section, under "Operating Systems," the documentation explicitly lists "Microsoft Windows Server 2019" and "Microsoft Windows Server 2016" as supported. It does not list any client operating systems. (URL: https://help.tableau.com/current/server/en-us/techspecs.htm)

2. Tableau Help | Tableau Server: Before you install.... This guide outlines the necessary planning steps before installation. In the "Confirm requirements" section, it directs administrators to the Technical Specifications page, which confirms that only server operating systems are supported. (URL: https://help.tableau.com/current/server/en-us/serverpreinstall.htm, Section: "General requirements and recommendations")

The Tableau Server Repository is the primary database for storing all server metadata. It is implemented using a PostgreSQL database. This metadata includes crucial information such as user accounts, groups, permissions, project structures, workbook and data source definitions, and metadata about data extracts. The Repository acts as the central catalog for all assets and configurations on the Tableau Server, enabling the system to manage content and enforce security.

A. Data Engine: The Data Engine (Hyper) is responsible for creating and querying Tableau data extracts (.hyper files). It manages the actual data within extracts, not the server's metadata.

C. Backgrounder: The Backgrounder process executes asynchronous, long-running tasks like extract refreshes, subscriptions, and flow runs. It does not store metadata.

D. File Store: The File Store process manages the physical storage of content files, such as data extracts and workbook revisions, but it is not the metadata database itself.

1. Tableau Server Help (Official Vendor Documentation). "Tableau Server Processes." This document provides a comprehensive overview of all server processes.

Repository: "The Repository is the PostgreSQL database that stores server metadata. This includes information about Tableau Server users, groups and group assignments, permissions, projects, data sources, and workbooks and extract metadata."

Data Engine: "The Data Engine creates, stores and queries data extracts."

Backgrounder: "The Backgrounder runs server tasks, such as extract refreshes, subscriptions, flow runs..."

File Store: "When Tableau Server is configured for external file store, this process is no longer used." (In a default configuration, it "manages the storage of extracts and workbook revisions.")

Reference Location: Tableau Server Help > Administrator Guide > Server Processes.

2. Tableau Server Help (Official Vendor Documentation). "Work with the Tableau Server Repository." This section details the function and structure of the Repository.

Section: "About the Tableau Server Repository"

Content: "The Tableau Server repository is a PostgreSQL database that stores data about all user interactions, extract refreshes, and more." This confirms its role as the central metadata store.

Reference Location: Tableau Server Help > Administrator Guide > Server Management > Administrative Views > Work with the Tableau Server Repository.

To ensure that server tasks run sequentially, or "one-at-a-time," the execution mode must be set to serial. Serial execution processes tasks one after another, where a subsequent task only begins after the preceding one has completed. This is in contrast to parallel execution, where multiple tasks run concurrently. In CRM Analytics, this can be achieved by scheduling jobs to run based on an event, such as the completion of a previous data sync or recipe, effectively creating a serial chain of execution.

B. Set Default priority to 0: Priority influences which job runs first when multiple jobs are queued, but it does not prevent them from running concurrently if resources are available.

C. Set Frequency to Hourly: Frequency determines how often a schedule is initiated (e.g., hourly, daily). It does not control how the tasks within that schedule are executed (serially or in parallel).

D. Set Execution to Parallel: This is the opposite of the requirement. Parallel execution runs multiple tasks simultaneously, not one-at-a-time.

1. Salesforce Help, CRM Analytics Documentation, "Schedule Data Sync and Recipes to Run After Each Other": This document explains the concept of event-based scheduling to create dependencies. It states, "To run a recipe or dataflow after the sync for a specific connection completes, schedule them to run after the connection syncs. You can also chain jobs to run after a recipe or dataflow finishes." This chaining is the mechanism for enforcing serial execution.

2. Salesforce Help, CRM Analytics Documentation, "Schedule, Run, and Monitor Analytics Jobs": This guide details scheduling options. In the context of data sync, it mentions, "To run a connection’s sync jobs one after another, you can schedule them in serial." This directly confirms that "serial" is the correct term for "one-at-a-time" execution.

3. Salesforce Help, CRM Analytics Documentation, "Data Integration Guide", Chapter: Run Data Integration Jobs: This guide discusses job scheduling and dependencies. It notes, "To ensure that a dataflow has the latest data from a particular Salesforce object, run the dataflow after the data sync for that object is complete. You can schedule a dataflow to run after data sync." This describes a practical application of serial execution.

Tableau Server can proactively warm the cache for a workbook after its underlying data extract is refreshed on a schedule. This process, known as pre-computation, improves performance by running queries and storing results before a user requests the view. For this to occur, Tableau Server checks two primary conditions: the workbook must be part of a scheduled extract refresh, and it must be considered relevant based on recent user activity. If a workbook has not been viewed recently, the server will not expend resources to pre-compute its cache, even if its data source is refreshed. Both conditions must be met for the cache warming to be initiated.

A. The publication date of a workbook is not a criterion for cache warming. A heavily used, older workbook is a better candidate for caching than a newly published, unused one.

C. Permissions, such as those for the 'All Users' group, govern access control, not the server's internal logic for performance optimization and cache management.

1. Tableau Server Help, "Configure Workbook Performance after a Scheduled Refresh": This official documentation outlines the specific criteria for warming the cache. It states, "Tableau Server will only warm the cache for a workbook if it meets all of the following criteria:

The workbook has been viewed in the last 30 days.

The workbook is part of a scheduled extract refresh."

This directly supports answers B and D.

2. Tableau Server Help, "Tableau Server Processes": The documentation for the Cache Server process explains its role in storing and managing query caches. It notes that the Backgrounder process can trigger cache warming for recently viewed workbooks after data extract refreshes, reinforcing the link between scheduled tasks (handled by Backgrounder) and recent usage as triggers for caching.

The tsm status -v command is the most direct and comprehensive method for verifying the status of all Tableau Server processes, including each instance within the Coordination Service ensemble. In a high-availability (HA) cluster, the Coordination Service runs on multiple nodes. The verbose (-v) flag provides a detailed, node-by-node status report for every process, allowing an administrator to confirm that the ensemble is fully operational and has achieved quorum. This command-line interface (CLI) tool provides an immediate, real-time health check essential for managing an HA environment.

A. Examine the Tableau Services Manager (TSM) web client Status page

While the TSM web UI does show process status, the tsm status -v command offers a more granular and scriptable output, which is standard for server administration checks.

B. Run the command tsm maintenance ziplogs

This command collects and archives log files for troubleshooting past events. It does not provide the current, real-time operational status of server processes.

D. Examine the Tableau Server Status page

This refers to the legacy administrative views within the Tableau Server UI. The Tableau Services Manager (TSM) is the modern and authoritative tool for managing core service topology and status.

---

1. Tableau Server Help (Official Vendor Documentation). "tsm status". This document explicitly describes the command for checking server status. It states, "tsm status -v Displays the status for Tableau Server. The verbose option shows the status of each individual process." This directly supports using the command to check the Coordination Service.

Source: https://help.tableau.com/current/server/en-us/clistatustsm.htm

2. Tableau Server Help (Official Vendor Documentation). "View Server Process Status". This guide details the methods for monitoring processes. It presents both the TSM web UI and the tsm status -v command as valid options, but highlights the detailed, per-process information provided by the CLI command, which is critical for verifying an ensemble.

Source: https://help.tableau.com/current/server/en-us/adminviewprocessstatus.htm

3. Tableau Server Help (Official Vendor Documentation). "Deploy a Coordination Service Ensemble". This document explains the function of the Coordination Service in an HA deployment. It underscores the importance of maintaining a healthy quorum, the status of which is verified using TSM status commands.

Source: https://help.tableau.com/current/server/en-us/distribhacoord.htm

When content permissions are not locked to the project, Tableau Server uses a delegated administration model. In this model, the user who owns the content (the workbook's owner) has the authority to manage its permissions. Additionally, users assigned the Project Leader role for the project containing the workbook are granted administrative capabilities over all content within that project, which includes setting permissions. This allows for granular control over individual assets by those most familiar with them.

A. Users that have the project and workbook Viewer role: The Viewer role is strictly for consumption. Users with this role can only view published content and have no administrative capabilities, including editing permissions.

B. Users that have the workbook Interactor role: The Interactor role allows users to interact with views (e.g., filter, sort, download data) but does not grant permissions to change the security or access rules for the workbook.

1. Tableau Server Help, "Set Permissions on Individual Content": This document explicitly states, "To set permissions on content, you must be an administrator, or have one of the following user roles: Project Owner, Project Leader, or a content owner." This directly supports that both the workbook's owner (content owner) and the Project Leader can edit permissions.

2. Tableau Server Help, "Projects and Content Permissions": Under the section "Who can set permissions," it clarifies that when permissions are customizable (not locked), "Content owners and project leaders (and administrators) can modify permission rules for their content." This confirms the roles of both the owner and Project Leader in this scenario.

3. Tableau Server Help, "Permissions Capabilities": This reference details the capabilities granted by different roles. It shows that the "Set Permissions" capability is not granted to the Viewer or Interactor site roles by default, reinforcing why options A and B are incorrect.

To perform a full server-level restore you must have two artifacts:

1) a .tsbak file created with tsm maintenance backup, which contains all PostgreSQL repository data;

2) an export (.json) created with tsm settings export –f, which captures every server secret (including repository passwords) and all configuration settings.

Topology information is regenerated automatically from the exported configuration and therefore does not need a separate backup.

Hence, the three data categories that must be backed up are Server secrets & repository passwords, Configuration data, and Repository data.

B. Topology data – Re-created when configuration JSON is applied; Tableau docs specify no separate topology backup is required for restore.

1. Tableau Software. “Back up Tableau Server Data.” Server Admin Guide 2023.3, section “Back up data you must have for a restore.”

https://help.tableau.com/current/server/en-us/backups.htm (para. 2–5).

2. Tableau Software. “tsm maintenance backup.” Server Admin Guide 2023.3, section “Creates a .tsbak file of repository data.”

https://help.tableau.com/current/server/en-us/tsmcmd.htm#maintenancebackup (entire page).

3. Tableau Software. “tsm settings export.” Server Admin Guide 2023.3, section “Exports configuration settings and security secrets.”

https://help.tableau.com/current/server/en-us/tsmcmd.htm#settingsexport (para. 1–4).

Tableau Server checks for data-driven alert conditions based on two primary triggers. First, there is a server-wide background process that checks alerts at a configurable frequency. By default, this interval is set to every 60 minutes. Second, for any view that is built upon a data extract, the alert condition is specifically checked immediately after the scheduled refresh for that extract completes. This ensures that alerts are evaluated against the most current data available in the extract. These two mechanisms work together to provide timely notifications when data crosses a specified threshold.

B. Every 10 minutes: This frequency is too high. The default and most frequent server-wide check interval for data-driven alerts is 60 minutes, not 10.

C. Whenever a new extract is published: Publishing a new extract is a one-time setup event. Alert checks are recurring processes tied to scheduled refreshes of existing extracts, not the initial publication.

1. Tableau Server Documentation, "Send Data-Driven Alerts from Tableau Server":

Reference for A: In the section "How data-driven alerts work," the documentation states, "By default, Tableau Server checks every 60 minutes to see if data conditions for alerts are true." This directly supports the 60-minute interval.

Reference for D: In the same section, it clarifies the behavior for extracts: "If the view uses an extract, the alert runs on the extract's refresh schedule." This confirms that extract refreshes are a primary trigger.

2. Tableau Server Documentation, "tsm configuration set Options":

Reference for A & B: The configuration key dataAlerts.checkIntervalInMinutes controls the server-wide check frequency. The documentation specifies its default value is 60. This confirms that 60 minutes is the standard interval and that 10 minutes is not the default.

Tableau Server is a resource-intensive application that requires significant CPU, memory, and I/O resources to function optimally. Running additional software on the same machine, particularly applications like antivirus, backup agents, or other server-grade software, creates resource contention. This competition for system resources can lead to severe performance degradation, instability, and unpredictable behavior for Tableau Server. Official Tableau deployment guidelines strongly recommend installing Tableau Server on a dedicated computer that meets or exceeds the minimum hardware requirements to ensure reliability and performance.

B. Separating the Backgrounder and VizQL processes to different machines: This is a recommended scaling strategy for multi-node deployments to improve performance, not a cause of problems.

C. Configuring the server to use a static IP address: This is a best practice and often a requirement for stable client connections and reliable server operation.

D. Using a non-default installation path: Tableau Server fully supports installation to a non-default directory; this action itself does not cause operational issues.

1. Tableau Server Help, "Before you install...", Section: "General Installation Guidelines for Tableau Server": This official documentation explicitly states, "For best performance, we recommend you install Tableau Server on a dedicated computer... For example, running other applications, such as anti-virus software or other databases, on the same computer as Tableau Server can degrade performance." This directly supports option A as the most likely cause of problems.

2. Tableau Server Help, "Performance Tuning", Section: "General performance guidelines": This section details how Tableau Server processes consume resources and emphasizes avoiding resource contention. It notes, "Contention for resources such as CPU, memory, and I/O can cause slower performance." This reinforces the reasoning behind why running other software is problematic.

3. Tableau Server Help, "Distributed and High Availability Tableau Server Installations", Section: "Example: Two-Node Installation": This documentation provides examples of separating processes like the Backgrounder and VizQL onto different nodes (machines) to balance the server load and improve performance, directly contradicting option B as a problem.

To allow users to post comments on a Tableau visualization, two primary configurations are required. First, the commenting feature must be enabled at the site level within the Tableau Server or Tableau Cloud settings. This acts as a master switch for that specific site. Second, the relevant users or groups must be explicitly granted the "Add Comments" permission capability on the specific workbook or view. Without this permission, even if commenting is enabled for the site, users will not be able to add comments.

A. The relevant users must have a minimum site role of Explorer (can publish)

This is incorrect. Users with a "Viewer" site role can add comments, provided they have the specific "Add Comments" permission. An Explorer role is not the minimum requirement.

C. Comments must be enabled on the server Settings page

While a server-wide setting to enable comments does exist and must be active, the site-level setting is more specific and is the direct control for a particular site's functionality. The question implies configuration for a set of users, which is managed at the site and content level.

1. Tableau Server Help - Manage Site Settings (for option D):

In the "General" tab of the site settings, an administrator can configure commenting. The documentation states, "Allow users to comment on views. When you turn off comments, any existing comments are archived on the server." This confirms the site-level setting is required.

Source: Tableau Server Help, "Manage Site Settings," Section: "General tab settings."

2. Tableau Server Help - Permissions (for option B):

The official documentation on capabilities granted by permissions lists "Add Comments" as a distinct capability. It states, "To see and add comments, users need the View Comments and Add Comments permission capabilities." This confirms that the specific permission must be granted.

Source: Tableau Server Help, "Permissions," Section: "Capabilities granted by permissions."

3. Tableau Server Help - Set Users’ Site Roles (for option A):

The documentation outlines the capabilities for each site role. The "Viewer" role description includes the ability to "Add comments to views." This directly refutes the claim that Explorer (can publish) is the minimum required role.

Source: Tableau Server Help, "Set Users’ Site Roles," Section: "General capabilities for each site role."

By default, Tableau Server is configured to allow data-driven alerts. The server-wide setting dataAlerts.enabled is set to true by default. Furthermore, when a new site is created, the site-level setting "Let users create and receive data-driven alerts" is also enabled by default. Since the scenario specifies that both the Tableau Server installation and the site use default settings, no additional configuration is necessary for users to begin setting up data-driven alerts.

A. This is incorrect because data-driven alerts are enabled by default at the server level in TSM. No action is required on the configuration page.

B. This command configures the frequency at which Tableau Server checks for alert conditions, it does not enable the feature itself. The default interval is already 60 minutes.

C. This is incorrect because the data-driven alerts setting is enabled by default on a new site's Settings page. A change would only be necessary if it were manually disabled.

1. Tableau Server Help - Set Up for Data-Driven Alerts.

Reference: In the section "Enable data-driven alerts (server-wide setting)", the documentation states: "By default, data-driven alerts are enabled."

Reference: In the section "Control data-driven alerts (site-level setting)", it states: "Go to a site's Settings page... Under Data-Driven Alerts, clear or select Let users create and receive data-driven alerts. By default, this option is selected."

Source: Salesforce, Tableau Server Help for Administrators. (This information is consistent across recent versions of Tableau Server documentation).

2. Tableau Server Help - tsm configuration set Options.

Reference: The documentation for the key dataAlerts.enabled specifies its default value is true.

Reference: The documentation for the key dataAlerts.checkIntervalInMinutes specifies its default value is 60. This confirms that option B does not change the default behavior and is not an enabling step.

Source: Salesforce, Tableau Server Help for Administrators.