TCA-C01 Practice Questions

Tableau Server Management Add-On (renamed “Tableau Advanced Management for Server”) supplies enterprise-grade observability, workload orchestration, external repository/file-store options, and resource monitoring. These capabilities let global organisations run compute-intensive advanced analytics and machine-learning extensions (e.g., TabPy, Einstein Discovery) reliably at scale by improving performance, security and manageability of the underlying Tableau Server cluster.

A. Bridge handles hybrid connectivity, not analytics compute or ML scalability.

B. Catalog (part of Data Management) gives lineage and governance, not runtime support for ML workloads.

C. Data Management improves prep & governance but lacks the infrastructure enhancements needed for heavy ML/advanced analytics processing.

1. Tableau “Advanced Management for Tableau Server” datasheet

2023

p. 2 (“Optimise mission-critical

advanced analytics workloads”).

2. Tableau Blog “Why Server Management Add-On Matters for Data Science at Scale

” 15 Jun 2022

para. 4-6.

3. Stanford CS102 Data Systems Course Notes

Week 11

highlighting the need for monitoring & orchestration layers when operationalising ML behind BI platforms.

Future-proofing a globally distributed Tableau deployment centers on meeting diverse legal and compliance obligations (GDPR, HIPAA, APPI, etc.). Architecture, data residency, encryption, and audit capabilities must be designed so each regional office can meet its applicable regulatory requirements now and as laws evolve.

A. Over-engineering raises cost/complexity without addressing compliance risks.

C. Cheapest hosting may breach regional data-protection laws.

D. Static configuration ignores inevitable business and legal changes.

1. Tableau Blueprint

“Security

Compliance

and Data Residency

” pp. 4-6.

2. Tableau Cloud Security Overview

Section “Regional Data Storage & Compliance

” 2023-04 edition.

3. MIT Sloan CISR Working Paper 437

“Global Data Regulation and Analytics Architecture

” pp. 7-8 (cites Tableau case).

When deploying a multi-node Tableau Server cluster behind a load balancer, user session consistency is critical. A user's session is established on a specific node (e.g., one running the VizQL Server process). If subsequent requests from that same user are routed to a different node, the session context is lost, which can force re-authentication or cause errors. Enabling "sticky sessions" (also known as session persistence or affinity) on the load balancer ensures that all requests from a particular client are directed to the same backend server for the duration of the session, preserving a seamless user experience.

A: A standard round-robin method without sticky sessions would break user sessions by distributing requests from the same user across different nodes.

C: Redirecting write operations is not a standard load balancing technique for ensuring session consistency in Tableau Server.

D: Network topology choices like using a separate subnet are for network organization or security, and do not directly enable user session consistency.

1. Tableau Server Documentation. (2023). Add a Load Balancer. Tableau Help. Retrieved from https://help.tableau.com/current/server/en-us/distriblb.htm. (Section: "Configure load balancer for sticky sessions" explicitly states

"Configure your load balancer for sticky sessions. Sticky sessions ensure that a user is connected to the same Tableau Server throughout a session.")

2. Tableau Server Documentation. (2023). Tableau Server Gateway. Tableau Help. Retrieved from https://help.tableau.com/current/server/en-us/gateway.htm. (This document discusses the role of the gateway and its interaction with load balancers

implicitly requiring session persistence for stateful user interactions.)

After installing Tableau Server, it is critical to verify that the file system permissions are correctly configured for the directories Tableau Server uses. The installer should automatically set these permissions for the 'Run As User' account. Verifying that this account has the necessary 'Full Control' or 'Modify' permissions on the data directory (e.g., C:\ProgramData\Tableau\Tableau Server) and its subdirectories is a key post-installation check. Incorrect permissions are a common cause of service startup failures and operational issues.

A. Checking free disk space is a pre-installation requirement, not a verification of file system permissions after installation is complete.

B. Verifying network settings confirms connectivity but does not validate the local file system permissions required for the server to operate.

D. The file system type (e.g., NTFS) is a system prerequisite; it is not a configurable permission setting to be verified post-installation.

1. Tableau Server Help. "Required Run As Service Account Settings". This document explicitly lists the required permissions for the Tableau Server data directory: "The Run As service account requires permissions to the installation location... the installer will create the directories and apply the correct permissions." Verifying these permissions is a standard troubleshooting step. (Document ID: runasacctreq, Tableau Server on Windows documentation).

2. Tableau Knowledge Base. "Tableau Server is in a Degraded State After Installation or Upgrade". This article often points to permission issues as a root cause, stating, "Verify the Run As User has full control of the Tableau Server directory." (Article ID: 000002205).

A deployment for thousands of concurrent global users requires a highly available and scalable architecture. A high-performance server cluster distributes the workload across multiple nodes, preventing any single machine from becoming a bottleneck. A load balancer is essential to intelligently route user requests to available nodes, ensuring optimal performance and high availability. A high-speed, low-latency network is critical to support the heavy traffic between users, the load balancer, and the server nodes, especially in a global operation. This configuration ensures performance, reliability, and scalability.

A. A minimal hardware setup would be immediately overwhelmed by the specified user load, leading to system failure and unacceptable performance.

C. Standard hardware without advanced networking would fail to handle the concurrency and global distribution requirements, causing significant performance bottlenecks.

D. A single server, regardless of its capacity, represents a single point of failure and cannot scale to effectively serve thousands of concurrent users.

1. Tableau. "Tableau Server Scalability: A Technical Deep Dive". Whitepaper. This document discusses multi-node deployments for scalability. It states, "For larger deployments... Tableau Server can be run on a cluster of machines. A load balancer distributes requests across the cluster." (Section: "Scaling Tableau Server").

2. Tableau Server Help. "Tableau Server Gateway". The documentation on the gateway process explains its role in distributing requests and recommends using a load balancer for multi-node environments to achieve scalability and high availability. (Document ID: serverprocessgateway, Tableau Server documentation).

3. Tableau Server Help. "High Availability". The official documentation describes configuring a multi-node installation with a load balancer as the standard approach for enterprise-grade deployments that require redundancy and can handle large user loads. (Document ID: ha, Tableau Server documentation).

The most effective caching strategy involves balancing data freshness with performance. Configuring the cache's Time-To-Live (TTL) policy to align with data refresh schedules ensures that users benefit from cached vizzes without viewing stale data. This is managed via the tsm data-access caching set command. Setting a value like 'low' or a specific timeout configures Tableau Server to reuse cached data as much as possible, reducing the load on the database and speeding up dashboard rendering for frequently accessed views. This is a direct and impactful configuration adjustment for performance optimization.

A. Refreshing the cache on every load negates the performance benefit of caching and is equivalent to querying the live data source each time.

C. Disabling caching entirely would severely degrade performance by forcing all user requests to query the underlying database directly, increasing load and latency.

D. Increasing RAM is a hardware upgrade, not a setting adjustment. While it supports a larger cache, it doesn't optimize the caching behavior itself.

1. Tableau Server Documentation. (2023). Configure Data Cache. Tableau Help. Retrieved from https://help.tableau.com/current/server/en-us/configcache.htm. (This document explains the tsm data-access caching set command and the options for balancing freshness and performance).

2. Tableau Server Documentation. (2023). Performance Tuning. Tableau Help. Retrieved from https://help.tableau.com/current/server/en-us/perftuning.htm. (This guide discusses caching as a key component of server performance tuning).

Tableau Server can authenticate users via Azure AD using the OpenID Connect flow. Microsoft requires that every relying-party application be registered in Azure AD so that a client ID, tenant ID, redirect URI, and client secret can be issued. Tableau Server must be added as an Enterprise/Application entry and granted the “openid” and “profile” delegated permissions; without this registration the authentication handshake cannot be completed.

A. MFA is optional and not mandated for basic Tableau-Azure AD integration.

B. Tableau Server does not poll Azure AD; authentication occurs on-demand via OIDC tokens.

D. Azure AD user information is not locally stored on Tableau Server, so no extra storage is required.

1. Tableau Help – “Configure Azure AD for OpenID Connect”, Server 2023.1, Steps 1-3.

2. Microsoft Docs – “Register an application with the Microsoft identity platform”, v2023-05, Sections 1-2.

3. Stanford CS255 Course Notes – “OpenID Connect”, 2022 edition, page 4.

Using single sign-on with an external identity provider (SAML or OpenID Connect) lets users authenticate once and gain secure, seamless access to both Tableau Cloud and on-premises resources. It aligns with hybrid architectures and corporate credential policies while supporting multi-factor authentication and centralized lifecycle management.

A. Local auth in Tableau Cloud creates separate credentials, undermining seamless access.

C. Separate systems force multiple logins and inconsistent security.

D. Manual entry each session reduces security and user experience; no integration.

1. Tableau Cloud Help

“Configure Single Sign-On (SSO) for Your Site

” v2024.1.

2. Tableau Authentication Whitepaper

“SAML and OpenID Connect for Hybrid Deployments

” pp. 3-5.

3. Stanford CS253 Course Notes

“Enterprise SSO Patterns

” Section 2.2 (Illustrates Tableau Cloud case).

Before installing Tableau Server on a Linux distribution, it is a mandatory prerequisite to create a non-root user account. The installation process must be run by this dedicated user. This ensures that the Tableau Server processes run with appropriate permissions, adhering to security best practices and preventing potential conflicts with system-level services. The official documentation explicitly outlines this as a required step before running the installation script, making it essential for a smooth and secure setup, whether using the CLI or the web-based setup wizard.

A. This is a hardware prerequisite, not an installation step. While important, the question asks for a procedural step during the installation process.

B. Tableau does not provide a single script to configure all dependencies; the administrator is responsible for ensuring prerequisites like package dependencies are met.

D. Disabling SELinux is not always required. It's often preferable to configure it to work with Tableau Server, which is a more secure approach.

1. Tableau Server Help. "Before you install...". Section: "Create a user account and group". States, "Create a group for the Tableau Server run as user... Create a user account that is a member of this group."

2. Tableau Server Help. "Install and Initialize TSM". Step 1: "Log on as a user with sudo access to the computer where you want to install Tableau Server." This implies a specific user context is required.

After installing the Tableau Server package on a Linux system, a crucial and mandatory step is to run the initialize-tsm script. This script initializes Tableau Services Manager (TSM), which is the command-line tool used for all subsequent server configuration and administration. This initialization sets up necessary environment variables, directories, and permissions for TSM to function correctly. Without this step, you cannot proceed with activating licenses, setting configuration options, or starting the Tableau Server services. It is a foundational step in the installation workflow for both CLI and web-based setups.

A. A static IP is a best practice and a prerequisite for a stable environment, but it is not a step performed during the installation process itself.

B. Firewall configuration is a separate system administration task. Allowing all traffic is also a significant security risk and not a recommended practice.

D. A graphical user interface (GUI) is not required to install or manage Tableau Server on Linux; it is designed to be fully managed via the CLI.

1. Tableau Server Help. "Install and Initialize TSM". Step 4: "Run the initialize-tsm script". The document states, "After installing Tableau Server, you must run the initialize-tsm script. This script must be run from the scripts directory."

2. Tableau Server Help. "tsm Command Line Reference". The introduction explains that TSM is the tool for managing installation and configuration, and its initialization is the first step after the package installation.