Analytics-Admn-201 Practice Exam Questions with Answers Salesforce Certified Tableau Server Administrator Certification

Subscriptions in Tableau Server deliver workbook views to users via email on a schedule. Group subscriptions apply to all group members—let’s unpack this:

Group Subscription Mechanics:

Created via Workbooks > Actions > Subscribe > Select Group.

Delivers content to all users in the group at the time the subscription runs (e.g., daily PDF).

Dynamic: Membership updates (additions/removals) are reflected automatically on the next run.

Option C (The subscription updates automatically to include the new user): Correct.

Details: When you add a user to the group (e.g., via Users > Groups > Add Users), Tableau Server’s subscription process queries the group’s current membership at runtime. The new user receives the subscription on the next scheduled delivery—no manual action needed.

Example: Group "Sales" has a 9 AM subscription. Add a user at 8 AM—they get the email tomorrow at 9 AM.

Option A (Admin receives notice to approve/deny): Incorrect.

Why: No approval workflow exists for group membership changes in subscriptions—it’s automatic.

Option B (Creator must manually edit): Incorrect.

Why: Subscriptions are tied to the group, not a static user list—manual edits aren’t required for membership changes.

Option D (Only members at creation time): Incorrect.

Why: This would be true for individual subscriptions (static list), but group subscriptions are dynamic.

Why This Matters: Dynamic group subscriptions streamline content delivery as teams evolve, reducing admin overhead.

Backing up Tableau Server ensures recovery from failures or migrations. A full backup includes multiple data types—let’s dissect this comprehensively:

Backup Components:

Repository Data: PostgreSQL database with metadata (users, permissions, workbooks). Backed up via tsm maintenance backup -f .tsbak.

Configuration Data: Server settings (e.g., ports, authentication) also in the .tsbak file.

Server Secrets: Encryption keys, internal tokens, Repository passwords—critical for restoring functionality.

Extracts: .hyper files in File Store (optional, separate backup).

Option A (Server secrets and Repository passwords): Correct.

Details: Includes encryption keys (for extracts), internal tokens (process communication), and Repository credentials. Backed up separately or stored securely (e.g., tsm security export-keys).

Why Critical: Without these, restored data may be inaccessible or services may fail.

Option C (Configuration data): Correct.

Details: Ports, authentication settings, process topology—part of the .tsbak file.

Why Critical: Restores server behavior and connectivity post-recovery.

Option D (Repository data): Correct.

Details: Core metadata database—also in .tsbak.

Why Critical: Without it, all content and user data is lost.

Option B (Topology data): Incorrect.

Details: Topology (process distribution) is part of configuration data in the .tsbak, not a separate entity. It’s not distinctly backed up as “topology data.”

Why This Matters: A complete backup (secrets, config, repository) ensures full restoration—missing any piece risks an unusable server.

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.

Tableau Server’s user-based licensing (Creator, Explorer, Viewer) ties licenses to individual users—let’s determine compatible authentication methods:

User-Based Licensing:

Licenses are assigned per user, tracked by username.

Authentication determines how users log in—must integrate with licensing.

Option A (Local authentication): Correct.

Details: Users are managed in Tableau Server’s internal database—username/password set manually or via import.

Why: Directly ties to user accounts, fully compatible with licensing.

Option C (Trusted authentication): Correct.

Details: Allows external apps to authenticate users via tickets (e.g., /trusted/).

Why: Maps to Tableau usernames, integrating with licensing—common for embedded analytics.

Config: Trusted IPs or credentials set in TSM.

Option D (Active Directory): Correct.

Details: Uses AD for authentication (LDAP or Kerberos)—users sync to Tableau Server.

Why: AD usernames align with licensing—supports SSO and user management.

Config: Enable via tsm authentication active-directory configure.

Option B (Reliance authentication): Incorrect.

Why: Not a recognized Tableau authentication method—likely a typo (e.g., for "Resilience" or misheard term). No such feature exists.

Why This Matters: Authentication flexibility ensures user-based licensing fits diverse IT environments—critical for adoption.

Installing Tableau Server on Windows requires an account with sufficient privileges to configure services, write to the file system, and manage registry settings. Let’s analyze this in depth:

Installation Requirements:

The installer creates services (e.g., Tableau Server Gateway), writes to Program Files and ProgramData, and configures TSM.

It needs local administrative privileges on the machine to perform these tasks.

Post-install, a "Run As" account can be set for services (e.g., NT AUTHORITY\NetworkService), but this is separate from the install account.

Option C (An account in the local administrator group): Correct.

Why: The account must be in the local Administrators group to:

Install software (UAC elevation).

Configure services and ports.

Write to protected directories (e.g., C:\Program Files\Tableau).

Examples: A local admin (e.g., Administrator) or a domain user added to the Administrators group (e.g., DOMAIN\AdminUser).

Process: Log in as this account, run the installer, and provide TSM admin credentials during setup.

Option A (A local user account): Incorrect.

A standard local user (not in Administrators) lacks permissions—installation would fail with "Access Denied" errors.

Option B (A domain user account): Incorrect unless clarified.

A domain user without local admin rights can’t install. If it’s in the Administrators group, it qualifies, but C is more specific.

Option D (NT AUTHORITY\NetworkService): Incorrect.

This is a built-in service account for running services (default "Run As" post-install), not for executing the installer—an interactive user account is required.

Why This Matters: Using the right account prevents install failures and ensures secure configuration—critical for production setups.

Tableau Services Manager (TSM) is the administrative tool for managing Tableau Server’s configuration, processes, and topology. To log in to TSM (via the web UI at https:// :8850 or CLI), you need:

TSM administrator credentials: These are distinct from site roles and are set during installation or reset via tsm reset.

Local administrative rights: On Windows, the account used to access TSM must be in the local Administrators group on the initial node, as TSM interacts with system-level services.

In a test cluster, the engineer’s inability to log in suggests they lack either the correct TSM credentials or sufficient OS-level permissions. Since the question focuses on a Windows environment and “initial node,” the most immediate requirement is local administrative rights to run TSM commands or access the UI.

Option C (An account with administrative rights to the computer): Correct. The engineer must use an account in the local Administrators group on the initial node to authenticate to TSM. After that, they’ll need the TSM admin username/password set during installation.

Option A (An account with a Creator site role): Incorrect. Site roles (e.g., Creator) apply to content access within Tableau Server, not TSM administration.

Option B (An account with a Site Administrator role): Incorrect. Site Administrators manage site content, not server-level TSM functions.

Option D (An account for the Tableau Server administrator): Partially correct but incomplete. This likely refers to the TSM admin account, but without local admin rights on the machine, login will fail. Option C is more precise.

Tableau Server can record performance metrics for workbooks to troubleshoot slow-loading views. This feature must be enabled at the site level (via Settings > General > Allow Performance Recording). Once enabled, you can trigger recording for a specific view by modifying its URL.

The correct syntax is to append :record_performance=yes& to the view URL, immediately after the session ID. For example:

Original URL: http://server/#/site/my-site/views/workbook/view?:iid=1

Modified URL: http://server/#/site/my-site/views/workbook/view?:iid=1:record_performance=yes &

After loading the view with this parameter, a performance recording is generated and accessible via the Performance option in the toolbar.

Option B (Type :record_performance=yes& at the end of the view URL, immediately after the session ID): Correct. This follows Tableau’s documented method for enabling performance recording.

Option A (Click the Performance link in the toolbar): Incorrect. The Performance link appears only after recording is triggered via the URL; it’s not the method to enable it.

Option C (Type :record_performance=yes& immediately before the session ID): Incorrect. The parameter must follow the session ID (e.g., :iid=1) to function correctly.

Option D (Delete the session ID in the URL and reload the view): Incorrect. The session ID is required for the view to load properly; removing it breaks the URL.

TSM commands manage Tableau Server maintenance—let’s validate their syntax:

Command Requirements:

Some need arguments (e.g., file paths); others are standalone.

Valid and Complete: Must work as-is without errors.

Option C (tsm maintenance cleanup): Correct.

Details: Removes temporary files and old logs—no arguments required (optional flags like -l exist).

Use: tsm maintenance cleanup—runs fully.

Option D (tsm maintenance ziplogs): Correct.

Details: Creates a zip of logs (e.g., tsm-logs.zip)—no arguments needed (optional -d for date range).

Use: tsm maintenance ziplogs—complete and valid.

Option A (tsm maintenance backup): Incorrect.

Why: Requires -f .tsbak (e.g., tsm maintenance backup -f backup.tsbak)—incomplete without it.

Option B (tsm maintenance restore): Incorrect.

Why: Needs -f .tsbak (e.g., tsm maintenance restore -f backup.tsbak)—not standalone.

Why This Matters: Correct syntax ensures maintenance tasks execute without errors—critical for server health.

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.

In Tableau Server, roles and permissions dictate who can perform specific administrative tasks. A "server administrator" has full control over the entire Tableau Server deployment, while site administrators manage specific sites. Some tasks are restricted to server administrators due to their server-wide impact.

Option B (Adding a site): Creating a new site in a multi-site Tableau Server environment is a server-level task that only a server administrator can perform. Sites are logical partitions within the server, and adding a site affects the overall server structure. Site administrators cannot create new sites; they can only manage existing ones.

Option D (Adding users): Adding users to Tableau Server (e.g., via the TSM interface or tabcmd) is a server administrator task when it involves adding users at the server level or assigning them to the default site. While site administrators can add users to their specific site in a multi-site environment, the initial addition of users to the server requires server administrator privileges. The question’s phrasing (“always require”) suggests a server-wide context, making this a correct choice.

Option A (Creating a schedule): This is incorrect because both server administrators and site administrators can create schedules for tasks like extract refreshes or subscriptions within their scope. It’s not exclusive to server administrators.

Option C (Locking project permissions): This is incorrect because locking project permissions can be done by a site administrator or project leader with appropriate permissions. It’s a project-level action, not a server-level task requiring a server administrator.

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 in Schedules > 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.