Important Salesforce Analytics-Admn-201 Exam Questions

Answer: A, C, D

Explanation:

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: C

Explanation:

In an HA Tableau Server cluster, the Coordination Service (ZooKeeper ensemble) maintains cluster state---let's find the best way to check it:

Coordination Service:

Runs on multiple nodes (3 or 5 in HA) to ensure quorum and failover.

Status indicates if it's running and synced---critical for cluster health.

Option C (Run tsm status -v): Correct.

Details: tsm status --verbose lists all processes across nodes, including Coordination Service (e.g., 'Coordination Service: RUNNING').

Why Best: Provides detailed, node-specific status in the CLI---e.g., 'Node 1: RUNNING, Node 2: RUNNING.'

Use: Run on the initial node; -v ensures full output.

Option A (TSM web client Status page): Incorrect.

Why: The TSM UI (Server > Status) shows process counts (e.g., 'Coordination Service: 3 instances'), but not detailed per-node status---less granular than CLI.

Option B (tsm maintenance ziplogs): Incorrect.

Why: Generates log archives for troubleshooting, not a real-time status check.

Option D (Tableau Server Status page): Incorrect.

Why: The Server Status page (Server > Status in the web UI) monitors application processes (e.g., VizQL), not TSM's Coordination Service.

Why This Matters: Coordination Service health ensures HA stability---tsm status -v is the admin's go-to for precision.

Answer: C, D

Explanation:

In Tableau, data sources can be embedded (stored within a workbook) or published (stored separately on Tableau Server). Let's define these and analyze the advantages:

Embedded Data Source: The connection details and any extract are bundled in the .twb or .twbx file. Each workbook manages its own copy.

Published Data Source: The connection or extract is hosted on Tableau Server, reusable across multiple workbooks.

Now, let's evaluate the options:

Option C (Centralized data management is easier): Correct. Published data sources allow:

Single source of truth: One data source can serve multiple workbooks, ensuring consistency.

Unified updates: Refresh schedules, permissions, and metadata (e.g., calculated fields) are managed in one place via the Server UI.

Governance: Administrators can control access and monitor usage centrally.

In contrast, embedded data sources require individual updates per workbook, leading to duplication and management overhead.

Option D (Storage space is conserved and resource usage during data refreshes is optimized): Correct. With published data sources:

Storage: A single extract on the Server (e.g., a .hyper file) is shared across workbooks, avoiding redundant copies stored in each embedded workbook.

Refreshes: One refresh job updates the shared extract, reducing CPU and memory usage compared to multiple refreshes for duplicate embedded extracts.

Embedded data sources replicate extracts, increasing disk space and refresh load.

Option A (Data is protected so that it is only available in one workbook): Incorrect. This describes embedded data sources, not published ones. Published data sources are shared, not restricted to one workbook---permissions control access, not exclusivity.

Option B (Drivers are automatically installed on each client's machine): Incorrect. Drivers (e.g., for SQL Server, PostgreSQL) must be installed on the Server hosting the published data source, not client machines. This is unrelated to the published vs. embedded distinction.

Why This Matters: Published data sources enhance scalability and efficiency in enterprise deployments, making them a cornerstone of Tableau Server's data strategy.

Answer: B

Answer: A, C, D

Explanation:

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/<ticket>).

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.