Free Practice Questions for the Salesforce Administrator Analytics-Admn-201 Exam (2026 Updated)

Tableau Server’s minimum hardware recommendations for a production single-node deployment ensure reliable performance for small to medium workloads. As of the latest documentation:

CPU : 8 cores (2.0 GHz or higher) to handle concurrent users, rendering, and background tasks.

RAM : 32 GB to support in-memory processing (e.g., VizQL, Data Engine) and caching.

Disk Space : 50 GB free for installation, logs, extracts, and temporary files.

Let’s break it down:

Option C (8-Core CPU, 32 GB RAM, 50 GB free disk space) : Correct. This matches Tableau’s official minimum for production:

8 cores ensure sufficient parallelism for processes like Backgrounder and VizQL.

32 GB RAM supports multiple users and extract refreshes.

50 GB disk space accommodates growth (initial install is ~1–2 GB, but logs and extracts expand).

Option A (4-Core, 16 GB RAM, 50 GB) : Incorrect. Too low for production—4 cores and 16 GB RAM are below the threshold for reliable performance under load.

Option B (2-Core, 8 GB RAM, 15 GB) : Incorrect. This is for non-production (e.g., trial) setups, insufficient for production stability.

Option D (4-Core, 64 GB RAM, 50 GB) : Incorrect. 4 cores are inadequate, though 64 GB RAM exceeds the minimum (32 GB).

Why This Matters : Under-spec hardware can lead to slow performance, failed refreshes, or crashes in production—adhering to the minimum ensures stability.

Tableau Server uses a role-based licensing model with three primary license levels: Creator, Explorer, and Viewer. Each license level corresponds to specific site roles that define what users can do on the server.

Viewer License: This is the most restrictive license, allowing users to view and interact with published content (e.g., dashboards and visualizations) but not to create or publish new content.

Site Role: The Viewer license can only be associated with the Viewer site role. This role restricts users to viewing capabilities, aligning with the license’s purpose.

Option A (Creator): Incorrect. The Creator license is for users who can create, edit, and publish content using Tableau Desktop and the web interface. It corresponds to the Creator site role, not Viewer.

Option B (Explorer (can publish)): Incorrect. This is a variation of the Explorer license, which allows users to edit and publish content within limits. It’s more permissive than Viewer.

Option C (Viewer): Correct. The Viewer site role matches the Viewer license level perfectly.

Option D (Explorer): Incorrect. The Explorer license allows users to explore data and create content in the web interface, exceeding the Viewer license’s capabilities.

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 < filename > .tsbak (e.g., tsm maintenance backup -f backup.tsbak)—incomplete without it.

Option B (tsm maintenance restore) : Incorrect.

Why : Needs -f < filename > .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.

To force Tableau Server to require the setup of a new administrator account (e.g., resetting the server to an initial setup state), the tsm reset command is the appropriate tool. This command resets Tableau Server’s administrative configuration, including the TSM administrator account, while preserving content like workbooks and data sources.

Option B (Run the tsm reset command): Correct. Running tsm reset clears the current TSM administrator credentials and configuration settings. The next time you access TSM (e.g., via the web interface or CLI), it prompts you to set up a new administrator account, mimicking the initial setup process. Command: tsm reset --username < new-username > --password < new-password > .

Option A (Edit tabsvc.yml): Incorrect. The tabsvc.yml file contains service configuration data, but manually editing it is not supported or recommended for resetting the administrator account. It could also corrupt the installation.

Option C (Run the tsm register command): Incorrect. The tsm register command is used to register Tableau Server with a new product key or identity store, not to reset the administrator account.

Option D (Reinstall Tableau Server): Incorrect. Reinstallation wipes the entire server, including content, and is overkill for this task. The tsm reset command achieves the goal without data loss.

Single Sign-On (SSO) allows users to authenticate once (e.g., via a corporate identity provider) and access Tableau Server without re-entering credentials. Tableau Server supports several SSO methods:

OpenID Connect (OIDC) : An OAuth 2.0-based protocol for SSO, configured via Tableau’s SAML settings with an OIDC-compatible IdP (e.g., Google, Okta).

Kerberos with Active Directory : A ticket-based SSO protocol, widely used in Windows environments with AD integration.

SAML : A flexible SSO standard using XML assertions, supporting various IdPs (e.g., ADFS, PingFederate).

Let’s evaluate:

Option A (OpenID Connect) : Correct. OIDC is an SSO method, implemented as a SAML variant in Tableau Server, enabling seamless login.

Option C (Kerberos with Active Directory) : Correct. Kerberos provides SSO in AD environments, delegating authentication to the domain controller.

Option D (Security Assertion Markup Language - SAML) : Correct. SAML is a core SSO method in Tableau, widely adopted for enterprise integrations.

Option B (Local Authentication) : Incorrect. Local Authentication uses Tableau’s internal user database, requiring manual credential entry—no SSO support.

Why This Matters : SSO enhances user experience and security by leveraging existing identity systems, reducing password fatigue.

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.

Comments on visualizations foster collaboration in Tableau Server—let’s break down the requirements:

Commenting Prerequisites :

Site-Level Enablement : Comments must be activated for the site.

Permission : Users need the " Add Comment " capability on the content.

Site Role : Minimum role of Viewer allows commenting if permissions are set.

Option B (Add Comments must be allowed in permissions) : Correct.

Details : In the Permissions dialog (e.g., for a workbook), set " Add Comment " to " Allowed " for users/groups. Default is " Denied " unless explicitly enabled.

How : Content > Workbooks > Actions > Permissions > Edit Rule .

Why : Permissions are granular—site enablement alone isn’t enough.

Option D (Comments must be enabled on the site Settings page) : Correct.

Details : Go to Site > Settings > General > Allow Comments —check the box.

Why : This is a site-wide toggle (default: off). Without it, no one can comment, regardless of permissions.

Option A (Minimum site role of Explorer - can publish) : Incorrect.

Why : Viewer role suffices if permissions allow—Explorer (can publish) isn’t required (it adds publishing, not commenting).

Option C (Server Settings page) : Incorrect.

Why : Comments are a site-level feature, not server-wide—no such toggle exists in TSM’s Server Settings.

Why This Matters : Enabling comments at both site and content levels ensures controlled collaboration—key for team insights.

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:// < server > :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.

In Tableau Server, schedules manage tasks such as extract refreshes and subscriptions. The execution mode of a schedule determines how tasks within that schedule are processed by the Backgrounder process:

Parallel : Tasks run simultaneously (up to the Backgrounder’s capacity), which is the default setting.

Serial : Tasks run one-at-a-time in sequence, ensuring that one task completes before the next begins.

To ensure tasks associated with a particular schedule run one-at-a-time, you must configure the schedule’s execution mode to Serial . This is done in the Tableau Server web interface:

Go to Schedules .

Select the schedule, click Actions > Edit Schedule .

Under Execution , choose Serial instead of Parallel .

Option A (Set Execution to Serial) : Correct. This directly addresses the requirement by forcing tasks to execute sequentially.

Option B (Set Default priority to 0) : Incorrect. Priority (1–100) determines the order of task execution across all schedules, not whether tasks run one-at-a-time within a single schedule. Also, 0 is not a valid priority value (minimum is 1).

Option C (Set Frequency to Hourly) : Incorrect. Frequency (e.g., hourly, daily) controls when the schedule runs, not how tasks within it are executed.

Option D (Set Execution to Parallel) : Incorrect. Parallel execution allows tasks to run simultaneously, which contradicts the requirement.

In Tableau Server, projects are containers for organizing and securing content. They help manage permissions and structure content hierarchically. Let’s define what can be contained:

Workbooks : Visualizations and dashboards published to the Server.

Data Sources : Published connections or extracts reusable across workbooks.

Nested Projects : Sub-projects within a parent project, introduced in later versions (e.g., 2018.2) for deeper organization.

Option B (Workbooks) : Correct. Workbooks are the primary content type in projects, containing views and dashboards.

Option C (Nested Projects) : Correct. Nested projects allow hierarchical structuring (e.g., a " Sales " project with " Q1 " and " Q2 " sub-projects), with inherited or custom permissions.

Option D (Data Sources) : Correct. Published data sources reside in projects, providing reusable data connections.

Option A (Groups) : Incorrect. Groups are collections of users managed at the site or server level, not stored within projects. Projects contain content, not user entities.

Why This Matters : Projects are key to content governance—knowing what they hold helps administrators organize and secure assets effectively.

Tableau Server’s installer configures process instances based on hardware and deployment type (single-node vs. multi-node). For a single-node installation with 4 cores, we need to consider the default process topology . Let’s break this down exhaustively:

Key Processes :

Gateway : Handles incoming requests (1 instance).

Application Server (VizPortal) : Manages UI and sessions (1 instance).

VizQL Server : Renders visualizations (2 instances).

Backgrounder : Runs extract refreshes, subscriptions (1 instance).

Data Server : Manages data connections (1 instance).

File Store : Stores extracts (1 instance).

Repository : Metadata database (1 instance, active).

Cluster Controller, Cache Server, etc. : Supporting processes (typically 1 each).

Default Configuration :

On a single-node install, Tableau sets 1 instance per process unless specified otherwise, except for VizQL, which defaults to 2.

The installer doesn’t scale instances linearly with cores (e.g., 4 cores ≠ 4 instances). Post-install, TSM can adjust this (e.g., tsm topology set-process), but the question asks for the installed default .

Minimum hardware (8 cores, 32 GB RAM) suggests higher defaults, but 4 cores still triggers a minimal setup.

Option B (1) : Correct with Caveat.

Most processes (e.g., Backgrounder, Gateway, Data Server) default to 1 instance on install, regardless of 4 cores.

VizQL defaults to 2, but the question’s phrasing ( " each process " ) implies a general rule. Historically (and per docs), 1 is the baseline for most, with VizQL as the exception.

Interpretation : Assuming " each " means the typical case, 1 fits most processes on a 4-core single-node setup.

Option A (2) : Incorrect. Only VizQL defaults to 2; others don’t.

Option C (8) : Incorrect. Far exceeds defaults—8 cores might justify more, but not 4.

Option D (4) : Incorrect. Not tied to core count by default; manual config would be needed.

Why This Matters : Understanding defaults aids capacity planning—4 cores is below production minimum (8), so performance tuning may be needed post-install.

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.

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.