Analytics-Admn-201 Exam Dumps - Salesforce Administrator Questions and Answers

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.

TSM is Tableau Server’s management layer, accessible via CLI or web UI (port 8850). HTTPS secures this access—let’s identify the responsible process:

TSM Architecture:

Administration Controller: Core TSM process, running on the initial node, handling configuration, UI, and CLI commands.

HTTPS: Enabled by default on port 8850 with a self-signed certificate (configurable to custom certs).

Option B (Administration Controller): Correct.

Details: Hosts the TSM web UI (https:// :8850) and processes CLI requests. It manages the HTTPS listener, serving the interface securely.

Why: It’s the central hub for TSM operations, including secure access.

Option A (License Manager): Incorrect.

Why: Validates licenses, not responsible for HTTPS or UI access.

Option C (Administration Agent): Incorrect.

Why: Runs on additional nodes in multi-node setups to relay commands to the Controller—no direct HTTPS role.

Option D (Coordination Service): Incorrect.

Why: ZooKeeper manages cluster state, not TSM’s web interface or HTTPS.

Why This Matters: Secure TSM access protects server administration—Administration Controller is the linchpin.

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.

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.

Tableau Server supports multi-tenancy via sites, each with customizable settings managed by server or site administrators. Let’s analyze what’s configurable per site:

Site Settings: Found in the web UI under Site > Settings > General. Server admins can override site admin settings.

Option B (Limitation on storage space): Correct.

Details: Server admins can set a storage quota per site (e.g., 100 GB) to cap disk usage for extracts and workbooks.

How: In TSM or site settings (if enabled)—e.g., tsm configuration set -k site.storage.quota -v 100000.

Impact: Prevents one site from monopolizing resources in multi-site deployments.

Option D (Language and locale): Correct.

Details: Each site can set its language (e.g., English, French) and locale (e.g., date/number formats).

How: Site settings UI—e.g., "Language: French, Locale: France."

Impact: Tailors the user experience per site’s audience.

Option A (Ability to embed credentials): Incorrect.

Details: Embedding credentials (e.g., in data sources) is a server-wide setting (tsm data-access), not per-site. Site admins can’t override it.

Option C (Limitation on number of users): Incorrect.

Details: User limits are tied to licenses (server-wide), not configurable per site. Site admins manage user assignments, not quotas.

Why This Matters: Site-specific settings enable tailored governance and resource allocation in multi-tenant environments.

Registering Tableau Server from the command line involves providing configuration details (e.g., identity store, license) via the tsm register command. Let’s explore this fully:

Registration Process:

Run during initial setup or to update settings (e.g., after changing AD/LDAP config).

Uses a configuration file to pass parameters to TSM.

Command: tsm register --file .

File Format:

Tableau Server uses JSON for configuration files in TSM commands like tsm register.

Example:

json

CollapseWrapCopy

{

"identityStore": {

"type": "local",

"domain": "example.com"

}

}

JSON is structured, machine-readable, and aligns with Tableau’s modern CLI design.

Option C (JSON): Correct.

Official format for tsm register, per documentation and practical use.

Option A (YML): Incorrect.

While tabsvc.yml exists internally, it’s not for registration—tsm register uses JSON.

Option B (XML): Incorrect.

Older Tableau configs used XML (e.g., workgroup.yml pre-TSM), but TSM standardized on JSON.

Option D (HTTP): Incorrect.

HTTP is a protocol, not a file format—irrelevant here.

Why This Matters: Correct file format ensures seamless registration, avoiding CLI errors in setup or migrations.

Tableau Server has specific hardware requirements for production environments to ensure stability and performance. The minimum recommended free disk space for a production installation is 50 GB. This accounts for:

The installation itself (approximately 1–2 GB).

Space for log files, temporary files, and extracts managed by the File Store and Data Engine.

Room for backups and operational overhead.

The full minimum hardware recommendations for a single-node production deployment are:

8 CPU cores (2.0 GHz or faster).

32 GB RAM.

50 GB free disk space (on the system drive, typically C: on Windows).

Option A (32 GB): Incorrect. While 32 GB is the minimum RAM requirement, it’s insufficient for disk space in production.

Option B (50 GB): Correct. This matches Tableau’s official recommendation for production environments.

Option C (15 GB): Incorrect. 15 GB is the minimum for a non-production or trial installation, not production.

Option D (64 GB): Incorrect. While 64 GB exceeds the minimum, it’s not the specified requirement—50 GB is sufficient.

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.

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.

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.