Tableau Server Certified Associate Exam SCA-C01 Exam Questions with Experts Answers Updated Recently

Kerberos delegationallows 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.

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 toSite > 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 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.