Salesforce Certified Tableau Server Administrator Analytics-Admn-201 Exam Questions

Answer : C

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.

Answer : C, D

Editing permissions on a workbook in Tableau Server depends on the user's role and the project's permission settings. Since permissions are not locked (i.e., 'Managed by Owner'), let's dissect who can edit them:

Permission Model:

Not Locked: Owners of content (workbooks, data sources) can set permissions, and Project Leaders can override at the project level.

Site Roles: Define maximum capabilities (e.g., Viewer, Explorer, Creator).

Capabilities: 'Set Permissions' is explicit---only certain users get it.

Option C (The workbook's owner): Correct.

Details: The owner (typically the publisher) has full control over their workbook when permissions are Managed by Owner:

How: In the UI, go to Content > Workbooks > Actions > Permissions---owners can edit rules (e.g., grant Editor to a group).

Site Role: Minimum of Explorer (can publish) or Creator to publish, ensuring 'Set Permissions' capability.

Why: Ownership inherently includes permission management unless locked.

Option D (Users set to Project Leader for the workbook's project): Correct.

Details: Project Leaders are assigned via Content > Projects > Actions > Permissions > Set Project Leader:

Power: Can edit permissions for all content in the project, even if not the owner.

Site Role: Requires Site Administrator or Server Administrator (Creator/Explorer variants suffice).

Why: Overrides ownership in Managed by Owner mode---ensures project-level governance.

Option A (Users with project and workbook Viewer role): Incorrect.

Why: Viewer role (site-level) limits users to viewing---lacks 'Set Permissions' capability, regardless of project/workbook rules.

Option B (Users with workbook Interactor role): Incorrect.

Why: 'Interactor' isn't a standard role---likely a misnomer for Explorer or Viewer with interaction permissions (e.g., Filter). No permission-editing rights exist here.

Why This Matters: Knowing who can edit permissions prevents access control gaps---crucial for collaborative or regulated environments.

Answer : A, B

Tableau Server's user-based licensing model assigns licenses to individual users (Creator, Explorer, Viewer) rather than machines or cores. Key features include:

Subscription license: Licenses are typically subscription-based, renewed annually or monthly, aligning with Tableau's pricing model.

Distinct user roles: It supports three roles (Creator, Explorer, Viewer), each with specific capabilities, enabling granular access control.

Option A (A subscription license): Correct. User-based licenses are subscription-based by default.

Option B (Enables distinct user roles): Correct. The model defines Creator, Explorer, and Viewer roles.

Option C (Restricts the number of machine cores): Incorrect. This applies to core-based licensing, not user-based.

Option D (A perpetual license): Incorrect. Perpetual licenses were phased out; user-based licenses are subscription-based as of recent models.

Answer : C

Tableau Desktop and Tableau Server have versioning considerations when publishing content, particularly regarding compatibility between older Desktop versions (e.g., 10.5) and newer Server versions (e.g., 2020.1). Let's break this down step-by-step:

Publishing Process: With a Creator site role and Publisher permissions, you have the rights to publish workbooks to the specified project. Tableau Server accepts workbooks from older Desktop versions (e.g., 10.5) and upgrades them to the current Server version (2020.1) during publishing. This process is seamless for the workbook itself, but extracts require special handling.

Extract Handling: If the workbook contains embedded .tde extracts (stored within the .twb or .twbx file), Tableau Server 2020.1 converts these to .hyper format upon publishing. This conversion is necessary because .hyper replaced .tde as the default extract engine starting in Tableau 10.5 and beyond, offering better performance and scalability. During this process, Tableau Desktop or Server displays a warning to inform the user of the upgrade, as it's a one-way conversion (you can't revert to .tde on the Server).

Now, let's evaluate the options:

Option A (You will successfully publish without any errors or warnings): Incorrect. While the publishing succeeds, a warning about the .tde to .hyper conversion appears if the workbook contains embedded extracts. Without extracts, no warning occurs, but the question's context implies extracts are likely involved (common in visualizations).

Option B (Error message: unable to publish to a newer version): Incorrect. Tableau supports publishing from older Desktop versions to newer Server versions. There's no outright error blocking this; compatibility is maintained.

Option C (Warning: embedded .tde extracts will be upgraded to .hyper): Correct. This is the precise warning displayed when a workbook with .tde extracts is published to a Server version that uses .hyper. It ensures the user is aware of the format change, which might affect extract refresh schedules or performance expectations.

Option D (Warning: workbook will be upgraded to a new version): Partially correct but less specific. The workbook is upgraded to 2020.1 compatibility, but the warning focuses on the extract format change (.tde to .hyper), not the workbook version generically. Option C is more accurate.

Why This Matters: The .tde to .hyper shift improves query performance and supports larger datasets, but users need to know about it for planning (e.g., extract refresh schedules might need adjustment). The warning ensures transparency.

Answer : A, C, D

Kerberos delegation allows Tableau Server to pass a user's Kerberos credentials to a data source for seamless authentication (SSO)---let's explore which sources support it:

Kerberos Overview:

Used with Active Directory (AD) for SSO in Windows environments.

Tableau Server delegates the user's ticket to the data source, avoiding embedded credentials.

Requires:

Data source support for Kerberos.

Proper configuration (e.g., SPN, constrained delegation).

Supported Data Sources: Per Tableau's documentation:

Option A (Teradata): Correct.

Details: Supports Kerberos delegation---common in enterprise data warehouses.

Config: Enable in TSM (tsm authentication kerberos configure) and set SPN for Teradata.

Option C (SQL Server): Correct.

Details: Fully supports Kerberos---widely used with AD-integrated SQL Server instances.

Config: Requires AD setup and 'Trustworthy' delegation in SQL Server.

Option D (SAP HANA): Correct.

Details: Supports Kerberos SSO via delegation---popular in SAP ecosystems.

Config: Needs HANA Kerberos setup (e.g., keytab) and Tableau Server integration.

Option B (PostgreSQL): Incorrect.

Why: Supports Kerberos authentication natively, but Tableau Server doesn't enable delegation to PostgreSQL---users must embed credentials or use other methods (e.g., OAuth).

Why This Matters: Kerberos delegation enhances security by avoiding stored passwords---knowing supported sources ensures SSO feasibility.

Answer : B, D

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.

Answer : B, C, D

Tableau Server provides multiple methods to create groups (collections of users) and projects (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 to Users > Groups > Add Group, name it, and optionally sync with Active Directory.

Projects: Go to Content > 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.