Free TCA-C01 Practice Test Questions and Answers (2026)

In a multi-node Tableau Server deployment, a node can be configured to run processes that do not require a core-based license. The Gateway process is one such example. A primary function of the Gateway is to act as a reverse proxy that handles all incoming user requests. This includes managing the initial authentication of users, which is a critical security function. By isolating the Gateway on an unlicensed node, often in a network DMZ, an organization can enhance security without consuming a license. The Gateway authenticates the user session before passing requests to licensed backend processes like the VizQL Server.

A: A failover node that can run core processes like VizQL Server or the Data Server must be fully licensed to take over those functions.

C: Data extraction and background jobs are executed by the Backgrounder process, which explicitly requires a licensed node to operate.

D: While the Gateway also performs load balancing, authentication is the foundational security step it manages for every user session.

1. Tableau Server Help, "Tableau Server Gateway". The documentation states, "When a client makes a request to Tableau Server, it is first received by the gateway... the gateway authenticates the user... and then sends the request to a Tableau Server process." (https://help.tableau.com/current/server/en-us/gateway.htm)

2. Tableau Server Help, "Tableau Server Independent Gateway". This document describes an architecture where the Gateway runs on a dedicated, unlicensed computer, highlighting its role in handling traffic and authentication from the internet. (https://help.tableau.com/current/server/en-us/independentgateway.htm)

The Tableau Server repository's historicalevents table is specifically designed to log significant actions that occur on the server. This includes events such as user sign-ins, sign-outs, view access, and publishing actions. To analyze user login patterns, such as login frequency, timing, and duration of sessions, querying the historicalevents table is the most direct and accurate method. This table, joined with historicaleventtypes and histusers, provides a comprehensive view of user session activity over time, which is essential for creating custom administrative views on user engagement.

A. The 'datasources' table contains metadata about published data sources, not user login events.

B. The 'workbooks' table contains metadata about published workbooks, not user login activity.

D. The 'sites' table contains information about the sites on the server, but not the individual login events for users within those sites.

1. Tableau Server Help. (2023). Workgroups Database. See the "historicalevents" table definition. The documentation explicitly lists 'Login' and 'Logout' as historicaleventtypeid values, confirming this table tracks user sessions.

2. Tableau Server Help. (2023). Create Custom Administrative Views. This guide explains how to connect to the Tableau Server repository and utilize its tables, with historicalevents being a key table for tracking user actions and server events.

Tableau Server's internal monitoring tools are designed to provide insights into application-level performance (e.g., view load times, query performance, backgrounder jobs). They do not provide comprehensive, real-time metrics for the underlying operating system or hardware. To get a complete picture of server health and identify potential bottlenecks like CPU saturation, memory pressure, or disk I/O latency, a dedicated system monitoring tool is required. These tools collect detailed OS and hardware metrics, enabling proactive performance management, capacity planning, and faster root cause analysis of system-level issues that impact Tableau Server's performance.

A. Relying solely on Tableau's internal tools provides an incomplete view, missing critical OS and hardware context for performance issues.

C. Focusing only on network activity ignores other critical hardware resources like CPU, memory, and disk I/O that heavily influence performance.

D. Manual, weekly recording is too infrequent and inefficient to capture real-time performance issues or establish meaningful, granular trends.

1. Tableau Blueprint. "Tableau Monitoring." Tableau Help, Tableau Software, LLC. Accessed 2023. The "Server and Hardware Monitoring" section explicitly recommends using external tools to monitor hardware utilization (CPU, RAM, Disk) and server processes, as these are outside the scope of Tableau's built-in tools.

2. Tableau Server Help. "Monitor Server Health." Tableau Help, Tableau Software, LLC. Accessed 2023. This guide mentions using performance monitoring tools like Windows Performance Monitor (PerfMon) or sar/vmstat on Linux to collect hardware data, acknowledging the need for external utilities.

3. Tableau Server Help. "Performance Tuning." Tableau Help, Tableau Software, LLC. Accessed 2023. Effective performance tuning requires understanding the interplay between the Tableau application and the underlying hardware, which necessitates collecting data from both sources.

The principle of least privilege is a fundamental security best practice for installing enterprise software on Linux. Creating a dedicated, unprivileged user and group for Tableau Server ensures that the application's processes are isolated from the rest of the operating system. This dedicated account is then given specific ownership and permissions only on the directories it needs to operate. This minimizes the potential attack surface and limits the damage that could be caused if the application account were compromised. This is a mandatory step outlined in the official Tableau Server installation guide for Linux.

A. Assigning the Tableau user to the root group grants excessive, dangerous permissions, directly violating security best practices and creating a significant system vulnerability.

C. Granting all users administrative privileges is a severe security risk, is not required for installation, and complicates permission management post-installation.

D. The system firewall manages network traffic and is unrelated to file system permissions. Disabling it exposes the server to network-based threats.

1. Tableau Server on Linux: Before you install.... (2023). Tableau Help. Retrieved from https://help.tableau.com/current/server-linux/en-us/installpre.htm. (See section: "Create a user and group").

2. Tableau Server on Linux: Install and Initialize TSM. (2023). Tableau Help. Retrieved from https://help.tableau.com/current/server-linux/en-us/installinstall.htm. (See Step 2, which details running the initialize-tsm script with the dedicated user).

The most logical and least disruptive initial step is to investigate the configuration of the component identified in the problem statement—the web proxy. Web proxies often have rules for bandwidth throttling, content filtering, or caching that can directly impact the performance of applications like Tableau Server. Examining these settings allows for a targeted diagnosis without altering the Tableau Server or network infrastructure. Disabling the proxy is a more drastic step and should be considered only after checking its configuration.

A. Disabling the proxy is a valid but more disruptive troubleshooting step; checking its configuration first is the standard initial procedure.

C. Reinstalling Tableau Server is a last-resort action and is unlikely to solve a problem originating from an external network component like a proxy.

D. Bypassing the proxy might not be feasible or compliant with security policies and doesn't diagnose the root cause of the proxy-related issue.

1. Tableau Server Help. "Configuring Proxies and Load Balancers for Tableau Server." Tableau Help, Tableau Software, LLC. Accessed 2024. See section on "Configuring Tableau Server to work with a reverse proxy server" which implies configuration is the key interaction point.

2. Tableau Server Help. "Performance Tuning." Tableau Help, Tableau Software, LLC. Accessed 2024. This section details troubleshooting performance, where external factors like network configuration are primary considerations.

ATR (Authorization-to-Run) licenses periodically validate with Tableau services. Multinationals must pick a license type (role-based or core) and activation strategy that covers users in all regions and ensures each server can meet ATR connectivity and grace-period rules, maintaining compliance and avoiding service interruption.

A. Lowest cost may not supply enough seats or allow regional server pools.

B. ATR compliance is mandatory; ignoring risks license violations.

D. IT preference alone may misalign with legal/user distribution and ATR rules.

1. Tableau Licensing – Authorization-to-Run (ATR) Overview

Sections “Global Deployments” & “Connectivity Requirements

” Feb-2024.

2. Tableau Server Administration Guide

“Selecting a Licensing Model for Distributed Enterprises

” pp. 11-13.

3. University of Washington INFO443 Lecture Slides

“Software Licensing in Global Firms

” Slide 18 (Tableau ATR example).

An air-gapped environment is, by definition, physically isolated from the internet and other unsecured networks. Therefore, any software updates must be managed through an offline process. The correct procedure involves downloading the Tableau Server installer and driver packages on an internet-connected machine, performing security scans and vetting, and then securely transferring these files into the isolated environment for a manual installation and upgrade. This maintains the integrity and security of the air gap.

A. An air-gapped environment has no internet connection, making real-time updates via the internet impossible.

C. Automatic updates require an internet connection to check for and download new versions, which is not available.

D. Establishing a satellite connection would break the air gap, fundamentally compromising the security posture of the environment.

1. Tableau Server Help. "Install Tableau Server in a Disconnected (Air-Gapped) Environment". This guide explicitly outlines the offline installation process

which is a prerequisite for any subsequent offline upgrades.

2. Tableau Server Help. "Upgrade Tableau Server - Overview". Section: "Perform the upgrade". The steps for an offline upgrade follow the same principle as an offline installation: downloading the installer on a separate machine and transferring it.

Consolidating multiple Tableau Server instances is a complex architectural project that goes far beyond technical migration. The most critical consideration for success is comprehensive planning. This plan must account for the integration of disparate content (workbooks, data sources), security models (users, groups, permissions), and operational schedules from each source environment into a unified, coherent target environment. Failing to plan for the integration of these elements will lead to content conflicts, security vulnerabilities, broken workflows, and a poor user experience, ultimately jeopardizing the project's success.

A. A "big bang" or simultaneous consolidation is extremely high-risk and increases the probability of a catastrophic failure and extended downtime.

C. Ignoring user impact and communication is a common reason for project failure; user adoption and training are critical to a successful transition.

D. Decommissioning source servers before the consolidation is complete and verified is illogical and guarantees data loss and service interruption.

1. Tableau Blueprint. "Tableau Migration". The Migration Planning section emphasizes the need for a detailed plan covering content, users, permissions, and data sources before execution.

2. Tableau Blueprint. "Governance". This section highlights the importance of establishing a consistent governance model for users, data, and content, which is a core component of a consolidation plan.

When troubleshooting Connected App authentication, the primary factor to investigate is the correctness and validity of the client credentials. Connected Apps in Tableau Server rely on JSON Web Tokens (JWTs) for authentication, which are generated using a client ID, a client secret, and a secret ID. If any of these components are incorrect, mismatched with the server's configuration, expired, or if the secret has been revoked, the JWT validation will fail, leading to an authentication error. This is the most direct and common point of failure in the authentication handshake between the external application and Tableau Server.

A. A poor internet connection would likely cause a timeout or connectivity error, not a specific authentication failure (e.g., an invalid token error).

C. While version compatibility is important for functionality, authentication failures are more frequently caused by credential errors than by fundamental version incompatibilities.

D. Data synchronization frequency is related to the application's function after a successful connection and is irrelevant to the initial authentication process.

1. Tableau Help. "Configure Tableau Connected Apps". Tableau Server Documentation. This page details the creation and management of Connected Apps, emphasizing the generation and use of a client ID and client secret. It states, "When the external application calls the Tableau REST API, it must include a valid JWT in the request to authenticate the user."

2. Tableau Help. "Embedding API v3". Tableau Developer Documentation. The section on authentication for embedding explicitly describes the process of generating a JWT using the client ID, secret ID, and secret value from the Connected App settings. An error in any of these will invalidate the token.

3. Tableau REST API Help. "Authentication". Tableau Server Documentation. The "Signing In Using JSON Web Tokens (JWT)" section outlines the required claims for the JWT, including the iss (issuer, which is the client ID) and kid (key ID, which is the secret ID), confirming these credentials are central to the process.

A robust disaster recovery (DR) strategy for a critical system like Tableau Server requires a multi-faceted approach. Regular, automated backups are essential to prevent data loss and eliminate human error. Storing these backups off-site protects against localized disasters (e.g., fire, hardware failure). A standby Tableau Server is crucial for business continuity, as it allows for a rapid failover, minimizing downtime (Recovery Time Objective). This combination ensures both data integrity (backups) and high availability (standby server), which are the core tenets of a comprehensive DR plan. Relying on any single element, like manual backups or partial backups, introduces significant risk.

A. Relying solely on manual backups is unreliable, prone to human error, and insufficient for a comprehensive disaster recovery plan which must also address recovery time.

C. Tableau Server does not have a "cloud-based auto-save" feature for DR. A proper DR strategy requires full server backups, not just workbook-level saves.

D. Limiting backups to certain assets risks data integrity and a complete system restore. A full backup of the repository and configuration is necessary for recovery.

1. Tableau Server Documentation. (2023). Disaster Recovery. Tableau Help. Retrieved from the official Tableau website. Section: "Tableau Server on Windows Disaster Recovery" and "Tableau Server on Linux Disaster Recovery". This documentation outlines the best practice of using backups in conjunction with a standby installation.

2. Tableau Server Documentation. (2023). Perform a Full Backup and Restore of Tableau Server. Tableau Help. Retrieved from the official Tableau website. Section: "Best practices for backup and restore". This section emphasizes automating backups and storing the backup file in a safe, separate location.