Tableau SCA-C01 Tableau Server Certified Associate Exam Exam Practice Test

Tableau Server uses a PostgreSQL database as its repository to store metadata, user information, and permissions. In a high-availability (HA) setup with multiple nodes, there are typically two repository instances: one active and one passive. The "preferred active repository" refers to designating which repository instance should take priority as the active one. This is managed through Tableau Services Manager (TSM).

The correct method to set the preferred active repository is by using the tsm configuration set command. Specifically, you would use a command like:

tsm configuration set -k pgsql.preferred_host -v

This command allows an administrator to specify the preferred host for the active repository, ensuring control over which node takes precedence in an HA environment.

Option B (tabcmd set command) is incorrect because tabcmd is a command-line utility primarily used for administrative tasks like managing users, groups, and content (e.g., publishing workbooks), not for configuring server topology or repository settings.

Option C (TSM browser client's Maintenance page) is incorrect because the Maintenance page in the TSM web interface is used for tasks like backups, restores, and cleanup, but it does not provide an option to set the preferred active repository.

Option D (TSM browser client's Configuration Topology page) is partially relevant since the Topology page displays the current configuration of services across nodes, including the repository. However, it does not allow direct modification of the preferred active repository; this must be done via the tsm command line.

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.

Tableau Server supports multiple authentication methods, including Local Authentication, Active Directory, Kerberos, SAML, and OpenID Connect.OpenID Connect (OIDC)is an identity layer built on OAuth 2.0, commonly used for single sign-on (SSO). In Tableau Server, OIDC is implemented as a variant ofSAML(Security Assertion Markup Language) authentication because both are SSO protocols managed through the same configuration workflow.

To use OpenID Connect:

Configure Tableau Server for SAML/SSO.

Provide an OIDC-compatible identity provider (IdP) configuration (e.g., Google, Okta).

Set up the IdP metadata and certificates in TSM.

Option D (SAML): Correct. Tableau Server treats OIDC as a subset of its SAML authentication framework, so you configure it under the SAML settings in TSM.

Option A (Local Authentication): Incorrect. Local Authentication uses Tableau’s internal user database, not an external SSO protocol like OIDC.

Option B (Kerberos): Incorrect. Kerberos is a network authentication protocol for Windows environments, unrelated to OIDC.

Option C (Active Directory): Incorrect. AD uses LDAP or Kerberos, not OIDC, for authentication.

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:

Version Context: Tableau Desktop 10.5 was released in 2017 and used the .tde (Tableau Data Extract) format for extracts. Tableau Server 2020.1, released in 2020, introduced the .hyper extract format (starting with version 10.5, but fully standardized later). When publishing from an older Desktop version to a newer Server version, Tableau ensures backward compatibility but may upgrade certain components.

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) duringpublishing. 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.

Tableau Server’suser-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.

In Tableau Server,projectsorganize content (workbooks, data sources) and use permissions to control access. "Locking permissions" restricts how permissions are managed within a project—let’s explore this exhaustively:

Permission Management Modes:

Managed by Owner: Default mode. Content owners (e.g., workbook publishers) can set permissions on their items, inheriting project defaults as a starting point.

Locked to the Project: Project-level permissions are enforced, and content owners cannot modify them. This ensures consistency across all items in the project.

How to Lock:

In the Tableau Server web UI:

Go toContent > Projects.

Select a project, clickActions > Permissions.

In the Permissions dialog, changePermissions Managementfrom "Customizable" (Managed by Owner) to "Locked."

Set the desired permissions (e.g., Viewer, Editor) for users/groups, which then apply uniformly to all content.

Via REST API: Use the updateProject endpoint with "permissionsLocked": true.

Option B (You can lock permissions to a project by changing Customizable to Locked): Correct.

Details: This is the precise action in the UI—switching from "Customizable" to "Locked" locks permissions at the project level.

Impact: Owners lose the ability to override permissions on individual workbooks/data sources, enforcing governance.

Example: Set "All Users" to Viewer (Locked)—all content in the project is view-only, regardless of owner intent.

Option A (Locking permissions must be enabled on the Server Settings page): Incorrect.

Why: Locking is a per-project setting, not a server-wide toggle. The Server Settings page (via TSM) controls global configs (e.g., authentication), not project permissions.

Option C (Content permissions are locked by default): Incorrect.

Default: New projects are "Managed by Owner" (Customizable), allowing flexibility unless explicitly locked by an admin.

Option D (By setting the appropriate Project permission role): Incorrect.

Confusion: "Project permission role" isn’t a term—permissions are set via rules (e.g., Viewer, Editor), but locking is a separate action (Customizable → Locked).

Why This Matters: Locking permissions ensures uniform access control, critical for regulated environments or large teams where consistency trumps flexibility.

Data-driven alerts in Tableau Server allow users to receive notifications when data in a view meets certain conditions (e.g., a sales metric exceeds a threshold). By default, this feature is disabled for a site unless explicitly enabled by an administrator.

Option C (Change the data-driven alerts setting on the new site's Settings page): This is the correct answer. In the Tableau Server web interface, a site administrator can navigate to the site’s Settings > General page and enable the option "Let users create data-driven alerts." This must be done manually because the default setting for a new site is disabled. Once enabled, users with appropriate permissions (e.g., Viewer, Explorer, or Creator roles) can create alerts on views they have access to.

Option A (Enable data-driven alerts on the TSM Configuration page): This is incorrect because the TSM Configuration page (accessed via the TSM web UI or CLI) manages server-wide settings like ports, authentication, and processes, not site-specific features like data-driven alerts.

Option B (Run the tsm configuration set -k dataAlerts.checkIntervalInMinutes -v 60 command): This is incorrect. The dataAlerts.checkIntervalInMinutes key controls how frequently Tableau Server checks alert conditions (default is 60 minutes), but it does not enable the feature itself. The feature must first be turned on at the site level.

Option D (No action is necessary): This is incorrect because the default setting for data-driven alerts is off for new sites, requiring explicit action to enable it.

Trusted Ticketsis an authentication method in Tableau Server for embedding views in external applications (e.g., portals) without requiring users to log in manually. Here’s how it works:

A trusted application (e.g., a web server) authenticates with Tableau Server using a trusted IP or username/password.

Tableau Server issues a temporary ticket (a unique string).

The ticket is embedded in a view URL (e.g., /trusted//views/...), granting access to the view for a short period (configurable, default 5 minutes).

Option A (Access embedded views without being prompted for credentials): Correct. Trusted tickets enable SSO-like behavior for embedded content, bypassing the login prompt if the ticket is valid. This is ideal for seamless integration into external systems.

Option B (Encrypt database connections): Incorrect. Encryption is handled by data source configurations (e.g., SSL), not trusted tickets, which focus on user authentication.

Option C (Save and edit workbooks): Incorrect. Trusted tickets grant view access, not edit permissions—those depend on the user’s site role and permissions.

Option D (Embed database credentials): Incorrect. Trusted tickets authenticate users to Tableau Server, not databases—database credentials are managed separately in the data source.

Why This Matters: Trusted tickets simplify embedding Tableau content securely in custom applications, enhancing user experience.

The VizQL Server process in Tableau Server handles rendering visualizations and processing queries for users viewing dashboards or workbooks. During installation, Tableau Server automatically configures the number of VizQL instances based on the number of processor cores on the machine, following this rule:

Default VizQL instances = 2 per node, unless manually adjusted post-installation.

In multi-node setups, additional instances may be added based on core count, but the question specifies a single server with 16 cores.

The installer does not scale VizQL instances linearly with core count by default (e.g., it doesn’t set 1 instance per 4 cores). Instead:

For a single-node installation, the default is 2 VizQL instances, regardless of core count (assuming the minimum hardware requirements are met: 8 cores, 32 GB RAM).

Administrators can later adjust this using TSM (e.g., tsm topology set-process) based on performance needs, but the question asks for the default configured by the installer.

Option A (4): Incorrect. Four instances might be configured manually for a 16-core server, but it’s not the default.

Option B (6): Incorrect. Six instances exceed the default for a single node.

Option C (10): Incorrect. Ten instances are far beyond the default and would require manual configuration.

Option D (2): Correct. The installer sets 2 VizQL instances by default on a single-node installation.

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.

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:

Version Context: Tableau Desktop 10.5 was released in 2017 and used the .tde (Tableau Data Extract) format for extracts. Tableau Server 2020.1, released in 2020, introduced the .hyper extract format (starting with version 10.5, but fully standardized later). When publishing from an older Desktop version to a newer Server version, Tableau ensures backward compatibility but may upgrade certain components.

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) duringpublishing. 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.

Backing up Tableau Server ensures recovery from failures or migrations. A full backup includes multiple data types—let’s dissect this comprehensively:

Backup Components:

Repository Data: PostgreSQL database with metadata (users, permissions, workbooks). Backed up via tsm maintenance backup -f .tsbak.

Configuration Data: Server settings (e.g., ports, authentication) also in the .tsbak file.

Server Secrets: Encryption keys, internal tokens, Repository passwords—critical for restoring functionality.

Extracts: .hyper files in File Store (optional, separate backup).

Option A (Server secrets and Repository passwords): Correct.

Details: Includes encryption keys (for extracts), internal tokens (process communication), and Repository credentials. Backed up separately or stored securely (e.g., tsm security export-keys).

Why Critical: Without these, restored data may be inaccessible or services may fail.

Option C (Configuration data): Correct.

Details: Ports, authentication settings, process topology—part of the .tsbak file.

Why Critical: Restores server behavior and connectivity post-recovery.

Option D (Repository data): Correct.

Details: Core metadata database—also in .tsbak.

Why Critical: Without it, all content and user data is lost.

Option B (Topology data): Incorrect.

Details: Topology (process distribution) is part of configuration data in the .tsbak, not a separate entity. It’s not distinctly backed up as “topology data.”

Why This Matters: A complete backup (secrets, config, repository) ensures full restoration—missing any piece risks an unusable server.

Importing an AD group into Tableau Server syncs user management—let’s analyze the process and options:

AD Group Import Process:

How: In the UI (Users > Groups > Add Group > Active Directory), enter the AD group name, set a site role, and sync.

Behavior:

Existing Users: If a user is already in Tableau Server, their site role remains unchanged unless manually adjusted—sync applies the minimum role only if it upgrades access.

New Users: Added to Tableau with the site role specified during import.

Config: Requires AD authentication enabled in TSM.

Option D (New users created are assigned the site role specified during import): Correct.

Details: When importing (e.g., "SalesTeam" group, site role: Explorer):

New users get Explorer.

Existing users keep their role unless it’s below Explorer (e.g., Unlicensed → Explorer).

Why: Ensures consistent onboarding—new users align with the group’s intended access.

Option A (Existing users’ roles change to match import): Incorrect.

Why: Existing roles persist unless lower than the minimum—e.g., Viewer stays Viewer if import sets Explorer, but Unlicensed upgrades. Not a full overwrite.

Option B (Requires a .csv file): Incorrect.

Why: AD import uses live sync via LDAP—no .csv needed (that’s for local auth imports).

Option C (Change group name during import): Incorrect.

Why: The AD group name is fixed—you can’t rename it in Tableau during sync (it mirrors AD). Post-import renaming is possible but not part of the process.

Why This Matters: Accurate AD sync ensures seamless user management—missteps can disrupt access or licensing.

Comments on Tableau Server visualizations facilitate collaboration. Let’s explore what’s supported:

Comments Feature: Enabled per site (Settings > General > Allow Comments). Users with "Add Comment" permission can post on views.

Option B (Text): Correct.

Details: The primary content type—users type free-form text in the comment box.

Use: Notes, questions, or feedback (e.g., "Sales spiked here—why?").

Option C (@mentions): Correct.

Details: Typing @username notifies the mentioned user via email or the UI (if notifications are enabled).

Use: Directs comments to specific people (e.g., "@John, check this trend").

Option A (Interactive snapshots of a view): Incorrect.

Details: Snapshots (static images) aren’t supported in comments—users must take screenshots externally and can’t embed them interactively.

Option D (Images - jpg, png): Incorrect.

Details: No attachment or image embedding in comments—text and mentions only. Workaround: Link to an image hosted elsewhere.

Why This Matters: Comments enhance teamwork, but their simplicity (text + mentions) keeps the interface lightweight and focused.

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.

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 underSite > Settings > General. Server admins can override site admin settings.

Option B (Limitation on storage space): Correct.

Details: Server admins can set astorage quotaper 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 itslanguage(e.g., English, French) andlocale(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.