Tableau Server Certified Associate Exam Questions and Answers
What two Tableau Services Manager (TSM) processes continue to run when Tableau Server is stopped? (Choose two.)
Options:
VizQL Server
License Manager
Backgrounder
Administration Controller
Answer:
B, DExplanation:
Tableau Server consists of multiple processes managed by TSM. When you stop Tableau Server (e.g., via tsm stop), most application processes halt, but some TSM-specific processes remain active to manage the server’s infrastructure. Let’s examine each:
TSM Processes: These include the Administration Controller, Administration Agent, and License Manager, which handle configuration, monitoring, and licensing.
Application Processes: These include VizQL Server, Backgrounder, Data Server, etc., which deliver Tableau’s core functionality and stop when the server is stopped.
When tsm stop is executed:
TheAdministration Controller(port 8850) continues running to manage TSM operations (e.g., restarts, status checks).
TheLicense Managerremains active to validate licenses and ensure compliance, even when the server is offline.
Application processes like VizQL Server and Backgrounder shut down, as they’re tied to user-facing services.
Option B (License Manager): Correct. It persists to handle licensing tasks, ensuring the server can restart without license issues.
Option D (Administration Controller): Correct. It’s the core TSM process, always running to accept commands and manage the server state.
Option A (VizQL Server): Incorrect. VizQL stops, as it renders visualizations for users—an application process tied to active server operation.
Option C (Backgrounder): Incorrect. Backgrounder stops, as it processes background tasks (e.g., extract refreshes), which halt when the server is down.
Why This Matters: Understanding which processes persist helps administrators troubleshoot and manage server lifecycle events effectively.
What two events must occur for Tableau Server to recompute queries for a workbook cache after a scheduled refresh? (Choose two.)
Options:
The workbook was published in the last month
The workbook has upcoming scheduled refresh tasks
The All Users group has a permission rule allowing access to the workbook
The workbook has been viewed recently
Answer:
B, DExplanation:
Tableau Server uses caching to speed up workbook loading by storing query results. After a scheduled extract refresh updates the data, the cache may need recomputing—let’s dive into the mechanics:
Caching Basics:
VizQL Cache: Stores rendered views and query results for faster access.
Refresh Trigger: A scheduled refresh updates the underlying extract (.hyper), but the cache isn’t automatically invalidated—it’s demand-driven.
Recompute Conditions: Tableau recomputes the cache when the workbook is accessed (viewed) and its data has changed (e.g., via refresh).
Evaluation:
Option B (The workbook has upcoming scheduled refresh tasks): Correct.
Why: An upcoming refresh task indicates the workbook relies on an extract with a schedule. After the refresh runs, the data changes, priming the cache for recomputation on next view. Without a schedule, no refresh occurs, so this is a prerequisite.
Detail: Schedules are set inSchedules > Tasks—e.g., "Daily at 2 AM."
Option D (The workbook has been viewed recently): Correct.
Why: Viewing triggers cache recomputation if the data has changed (e.g., post-refresh). Tableau uses a "lazy caching" model—cache updates only when a user loads the workbook, ensuring fresh results.
Detail: "Recently" isn’t strictly defined but implies post-refresh access.
Option A (Published in the last month): Incorrect.
Why: Publish date is irrelevant—cache recomputation ties to data changes and access, not publication timing.
Option C (All Users group has permission rule allowing access): Incorrect.
Why: Permissions enable viewing, but recomputation requires actual access (viewing) and a refresh event, not just potential access.
Why This Matters: Caching balances performance and freshness—understanding triggers prevents stale data surprises.
What statement correctly describes locking permissions to a project?
Options:
Locking permissions to projects must be enabled on the Tableau Server Settings page
You can lock permissions to a project by changing Customizable to Locked
Content permissions are locked to a project by default
You can lock permissions to a project by setting the appropriate Project permission role
Answer:
BExplanation:
In Tableau Server,projectsorganize content (workbooks, data sources) and use permissions to control access. "Locking permissions" restricts how permissions are managed within a project—let’s explore this exhaustively:
Permission Management Modes:
Managed by Owner: Default mode. Content owners (e.g., workbook publishers) can set permissions on their items, inheriting project defaults as a starting point.
Locked to the Project: Project-level permissions are enforced, and content owners cannot modify them. This ensures consistency across all items in the project.
How to Lock:
In the Tableau Server web UI:
Go toContent > Projects.
Select a project, clickActions > Permissions.
In the Permissions dialog, changePermissions Managementfrom "Customizable" (Managed by Owner) to "Locked."
Set the desired permissions (e.g., Viewer, Editor) for users/groups, which then apply uniformly to all content.
Via REST API: Use the updateProject endpoint with "permissionsLocked": true.
Option B (You can lock permissions to a project by changing Customizable to Locked): Correct.
Details: This is the precise action in the UI—switching from "Customizable" to "Locked" locks permissions at the project level.
Impact: Owners lose the ability to override permissions on individual workbooks/data sources, enforcing governance.
Example: Set "All Users" to Viewer (Locked)—all content in the project is view-only, regardless of owner intent.
Option A (Locking permissions must be enabled on the Server Settings page): Incorrect.
Why: Locking is a per-project setting, not a server-wide toggle. The Server Settings page (via TSM) controls global configs (e.g., authentication), not project permissions.
Option C (Content permissions are locked by default): Incorrect.
Default: New projects are "Managed by Owner" (Customizable), allowing flexibility unless explicitly locked by an admin.
Option D (By setting the appropriate Project permission role): Incorrect.
Confusion: "Project permission role" isn’t a term—permissions are set via rules (e.g., Viewer, Editor), but locking is a separate action (Customizable → Locked).
Why This Matters: Locking permissions ensures uniform access control, critical for regulated environments or large teams where consistency trumps flexibility.
What process decides when a Repository failover is required?
Options:
Cluster Controller
Coordination Service
Gateway
Backgrounder
Answer:
AExplanation:
In a high-availability (HA) Tableau Server setup, theRepository(PostgreSQL) has an active and passive instance. Failover occurs if the active Repository fails. Let’s dive into the process:
HA Setup:
Two Repository instances across nodes (active/passive).
Failover switches to the passive instance if the active one becomes unavailable (e.g., crash, network issue).
Cluster Controller:
Role: Monitors all processes (e.g., Repository, File Store) across nodes, detecting failures via heartbeats and status checks.
Failover Decision: If the active Repository stops responding, Cluster Controller initiates failover, promoting the passive instance to active.
Coordination: Works with Coordination Service (ZooKeeper) to update topology but makes the initial detection call.
Option A (Cluster Controller): Correct.
Why: It’s the watchdog process, constantly monitoring Repository health and triggering failover when needed.
Option B (Coordination Service): Incorrect.
Role: ZooKeeper maintains cluster state and coordinates topology updates post-failover, but doesn’t detect the failure—Cluster Controller does.
Option C (Gateway): Incorrect.
Role: Routes client requests—unrelated to internal process monitoring or failover.
Option D (Backgrounder): Incorrect.
Role: Executes background tasks—no involvement in Repository failover decisions.
Why This Matters: Understanding failover ensures HA reliability—Cluster Controller is the linchpin for resilience.
What process enables you to access Tableau Services Manager (TSM) over HTTPS?
Options:
License Manager
Administration Controller
Administration Agent
Coordination Service
Answer:
BExplanation:
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
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.
What should you do to disable table recommendations for popular data sources and tables to users?
Options:
Disable the option using the site Settings page
Use the command: tsm configuration set -k recommendations.enabled -v false
Publish data sources only to projects with permissions locked to the project
Disable the option using the server Settings page
Answer:
AExplanation:
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.
Which two operating systems are supported for a Tableau Server installation? (Choose two.)
Options:
Windows 7
Windows 10
Windows Server 2019
Windows Server 2016
Answer:
C, DExplanation:
Tableau Server is designed for production environments and is supported only on server-class operating systems, not desktop operating systems. As of the latest documentation (aligned with knowledge up to March 21, 2025), the supported operating systems for Tableau Server on Windows are:
Windows Server 2016
Windows Server 2019
Windows Server 2022 (added in later versions, but relevant as of 2025).
Desktop operating systems like Windows 7 or Windows 10 are not supported for production installations due to stability, security, and performance requirements.
Option A (Windows 7): Incorrect. Windows 7 is a desktop OS and is not supported for Tableau Server. It’s also end-of-life as of January 2020.
Option B (Windows 10): Incorrect. Windows 10 is a desktop OS and not supported for production Tableau Server deployments, though it may be used for testing in non-production scenarios.
Option C (Windows Server 2019): Correct. This is a supported server OS for Tableau Server.
Option D (Windows Server 2016): Correct. This is also a supported server OS for Tableau Server.
What are two intervals when Tableau Server verifies if data conditions for data-driven alerts are true? (Choose two.)
Options:
Every 60 minutes
Every 10 minutes
Whenever a new extract is published
Whenever extracts in the related workbook are refreshed
Answer:
A, DExplanation:
Data-driven alerts notify users when data meets conditions (e.g., sales > $10K). Let’s examine when Tableau checks these:
Alert Mechanics:
Enabled per site (Settings > General > Data-Driven Alerts).
Backgrounder evaluates conditions against extract data.
Check Intervals: Configurable via tsm configuration set -k dataAlerts.checkIntervalInMinutes (default: 60 minutes).
Refresh Trigger: Also checks post-extract refresh for immediate updates.
Option A (Every 60 minutes): Correct.
Details: Default interval—Backgrounder polls every hour to evaluate alert conditions.
Config: Adjustable (e.g., -v 30 for 30 minutes).
Option D (Whenever extracts in the related workbook are refreshed): Correct.
Details: An extract refresh updates the data, triggering an immediate alert check to catch changes promptly.
Why: Ensures timely notifications without waiting for the next poll.
Option B (Every 10 minutes): Incorrect.
Why: Not the default—possible via config, but not standard.
Option C (Whenever a new extract is published): Incorrect.
Why: Publishing creates the extract; alerts trigger on refreshes or polling, not initial publication.
Why This Matters: Timing affects alert responsiveness—balancing frequency and server load is key.
What event is most likely to cause problems for a Tableau Server?
Options:
Running additional software on the server
Separating the Backgrounder and VizQL processes to different machines
Configuring the server to use a static IP address
Using a non-default installation path
Answer:
AExplanation:
Tableau Server’s performance and stability depend on dedicated resources and proper configuration. Running additional software on the same server is the most likely to cause problems because:
Resource contention: Tableau Server requires significant CPU, RAM, and disk I/O. Other software (e.g., databases, web servers) can compete for these resources, leading to slowdowns, crashes, or failed tasks.
Port conflicts: Tableau uses specific ports (e.g., 80, 443, 8850), and other applications might interfere.
Security risks: Additional software increases the attack surface, potentially compromising Tableau Server.
Tableau recommends running the server on dedicated hardware without unrelated applications.
Option A (Running additional software on the server): Correct. This is a common cause of performance issues and is explicitly discouraged in Tableau’s best practices.
Option B (Separating the Backgrounder and VizQL processes to different machines): Incorrect. This is a supported multi-node configuration that can improve performance, not cause problems, if properly set up via TSM.
Option C (Configuring the server to use a static IP address): Incorrect. A static IP is recommended for Tableau Server to ensure consistent network access, so it’s unlikely to cause issues.
Option D (Using a non-default installation path): Incorrect. While not default, a custom path is supported (via TSM or installer options) and unlikely to cause problems if permissions and disk space are adequate.
You have a server that contains 16 processor cores. What is the default number of VizQL instances configured by the installer?
Options:
4
6
10
2
Answer:
DExplanation:
The VizQL Server process in Tableau Server handles rendering visualizations and processing queries for users viewing dashboards or workbooks. During installation, Tableau Server automatically configures the number of VizQL instances based on the number of processor cores on the machine, following this rule:
Default VizQL instances = 2 per node, unless manually adjusted post-installation.
In multi-node setups, additional instances may be added based on core count, but the question specifies a single server with 16 cores.
The installer does not scale VizQL instances linearly with core count by default (e.g., it doesn’t set 1 instance per 4 cores). Instead:
For a single-node installation, the default is 2 VizQL instances, regardless of core count (assuming the minimum hardware requirements are met: 8 cores, 32 GB RAM).
Administrators can later adjust this using TSM (e.g., tsm topology set-process) based on performance needs, but the question asks for the default configured by the installer.
Option A (4): Incorrect. Four instances might be configured manually for a 16-core server, but it’s not the default.
Option B (6): Incorrect. Six instances exceed the default for a single node.
Option C (10): Incorrect. Ten instances are far beyond the default and would require manual configuration.
Option D (2): Correct. The installer sets 2 VizQL instances by default on a single-node installation.
Which Tableau Server process performs the role of a database for metadata?
Options:
Data Engine
Repository
Backgrounder
File Store
Answer:
BExplanation:
Tableau Server relies on several processes to function, each with a specific role. TheRepositoryprocess (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.
Option A (Data Engine): Incorrect. The Data Engine manages in-memory data processing and extract storage (e.g., .hyper files), not metadata. It’s separate from the Repository.
Option C (Backgrounder): Incorrect. The Backgrounder handles background tasks like extract refreshes and subscriptions, but it doesn’t store metadata—it interacts with the Repository to retrieve task details.
Option D (File Store): Incorrect. The File Store manages physical extract files and workbook assets, not metadata, which is stored in the Repository.
Which three methods should an administrator use to create a Tableau Server group or project? (Choose three.)
Options:
tsm customize
Tableau Server browser interface
tabcmd
REST API
Answer:
B, C, DExplanation:
Tableau Server provides multiple methods to creategroups(collections of users) andprojects(content containers), catering to UI, CLI, and programmatic needs. Let’s dissect each option with depth:
Option B (Tableau Server browser interface): Correct.
Groups: Go toUsers > Groups > Add Group, name it, and optionally sync with Active Directory.
Projects: Go toContent > Projects > New Project, set name, description, and permissions.
Details: The web UI is intuitive, requiring server/site administrator rights. It’s ideal for manual, ad-hoc creation with immediate visibility.
Permissions: For projects, you can set default permissions or lock them here.
Option C (tabcmd): Correct.
Groups: tabcmd creategroup "GroupName" creates a local group. Add users with tabcmd addusers "GroupName" --users "user1,user2".
Projects: tabcmd createproject -n "ProjectName" -d "Description" creates a project.
Details: tabcmd is a command-line tool for batch operations or scripting (e.g., automating group/project setup). It requires a server admin login (tabcmd login).
Limitation: No AD sync via tabcmd—that’s UI or REST API territory.
Option D (REST API): Correct.
Groups: Use the POST /api/api-version/sites/site-id/groups endpoint with a payload (e.g., {"group": {"name": "GroupName"}}). Supports AD import too.
Projects: Use POST /api/api-version/sites/site-id/projects (e.g., {"project": {"name": "ProjectName", "description": "Desc"}}).
Details: The REST API is programmatic, ideal for integration with external systems or bulk automation. Requires authentication via a token and server/site admin rights.
Power: Offers full control, including nested projects and custom permissions.
Option A (tsm customize): Incorrect.
Purpose: tsm customize modifies TSM UI branding (e.g., logos, colors) via commands like tsm customize --logo "path/to/logo.png".
Why Wrong: It’s unrelated to creating groups or projects—it’s for cosmetic server configuration, not content/user management.
Why This Matters: Offering UI, CLI, and API options ensures flexibility—manual for small tasks, automation for scale—critical in enterprise deployments.
What command should you run to update the automatically-generated secrets that are created during a Tableau Server installation?
Options:
tsm data-access caching set -r 1
tsm licenses refresh
tsm security regenerate-internal-tokens
tsm security validate-asset-keys
Answer:
CExplanation:
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.
What should you use to set a preferred active repository?
Options:
A tsm configuration set command
A tabcmd set command
The TSM browser client's Maintenance page
The TSM browser client's Configuration Topology page
Answer:
AExplanation:
Tableau Server uses a PostgreSQL database as its repository to store metadata, user information, and permissions. In a high-availability (HA) setup with multiple nodes, there are typically two repository instances: one active and one passive. The "preferred active repository" refers to designating which repository instance should take priority as the active one. This is managed through Tableau Services Manager (TSM).
The correct method to set the preferred active repository is by using the tsm configuration set command. Specifically, you would use a command like:
tsm configuration set -k pgsql.preferred_host -v
This command allows an administrator to specify the preferred host for the active repository, ensuring control over which node takes precedence in an HA environment.
Option B (tabcmd set command) is incorrect because tabcmd is a command-line utility primarily used for administrative tasks like managing users, groups, and content (e.g., publishing workbooks), not for configuring server topology or repository settings.
Option C (TSM browser client's Maintenance page) is incorrect because the Maintenance page in the TSM web interface is used for tasks like backups, restores, and cleanup, but it does not provide an option to set the preferred active repository.
Option D (TSM browser client's Configuration Topology page) is partially relevant since the Topology page displays the current configuration of services across nodes, including the repository. However, it does not allow direct modification of the preferred active repository; this must be done via the tsm command line.
What process decides when a Repository failover is required?
Options:
Cluster Controller
Coordination Service
Gateway
Backgrounder
Answer:
AExplanation:
In a high-availability (HA) Tableau Server setup, theRepository(PostgreSQL) has an active and passive instance. Failover occurs if the active Repository fails. Let’s dive into the process:
HA Setup:
Two Repository instances across nodes (active/passive).
Failover switches to the passive instance if the active one becomes unavailable (e.g., crash, network issue).
Cluster Controller:
Role: Monitors all processes (e.g., Repository, File Store) across nodes, detecting failures via heartbeats and status checks.
Failover Decision: If the active Repository stops responding, Cluster Controller initiates failover, promoting the passive instance to active.
Coordination: Works with Coordination Service (ZooKeeper) to update topology but makes the initial detection call.
Option A (Cluster Controller): Correct.
Why: It’s the watchdog process, constantly monitoring Repository health and triggering failover when needed.
Option B (Coordination Service): Incorrect.
Role: ZooKeeper maintains cluster state and coordinates topology updates post-failover, but doesn’t detect the failure—Cluster Controller does.
Option C (Gateway): Incorrect.
Role: Routes client requests—unrelated to internal process monitoring or failover.
Option D (Backgrounder): Incorrect.
Role: Executes background tasks—no involvement in Repository failover decisions.
Why This Matters: Understanding failover ensures HA reliability—Cluster Controller is the linchpin for resilience.
You have an installation of Tableau Server and a site that are configured to use default settings. What should you do to ensure that the users on the site can set up data-driven alerts?
Options:
Enable data-driven alerts on the Tableau Services Manager Configuration page
Run the tsm configuration set -k dataAlerts.checkIntervalInMinutes -v 60 command
Change the data-driven alerts setting on the new site's Settings page
No action is necessary: the default settings enable data-driven alerts for the site
Answer:
CExplanation:
Data-driven alerts in Tableau Server allow users to receive notifications when data in a view meets certain conditions (e.g., a sales metric exceeds a threshold). By default, this feature is disabled for a site unless explicitly enabled by an administrator.
Option C (Change the data-driven alerts setting on the new site's Settings page): This is the correct answer. In the Tableau Server web interface, a site administrator can navigate to the site’s Settings > General page and enable the option "Let users create data-driven alerts." This must be done manually because the default setting for a new site is disabled. Once enabled, users with appropriate permissions (e.g., Viewer, Explorer, or Creator roles) can create alerts on views they have access to.
Option A (Enable data-driven alerts on the TSM Configuration page): This is incorrect because the TSM Configuration page (accessed via the TSM web UI or CLI) manages server-wide settings like ports, authentication, and processes, not site-specific features like data-driven alerts.
Option B (Run the tsm configuration set -k dataAlerts.checkIntervalInMinutes -v 60 command): This is incorrect. The dataAlerts.checkIntervalInMinutes key controls how frequently Tableau Server checks alert conditions (default is 60 minutes), but it does not enable the feature itself. The feature must first be turned on at the site level.
Option D (No action is necessary): This is incorrect because the default setting for data-driven alerts is off for new sites, requiring explicit action to enable it.