Tableau SCA-C01 Exam Dumps & Practice Test Questions

Question 1:

A user complains that a recently published Tableau workbook is performing slowly. What is the most appropriate first question to ask to begin troubleshooting the issue?

A. Does the workbook always run slowly or does performance vary?
B. Did you enable caching on the workbook?
C. Does it run any faster in Tableau Desktop?
D. How many times have you opened the workbook in Tableau Server?

Correct Answer: A

Explanation:

When addressing a performance issue in Tableau, the first and most insightful question to ask the user is whether the workbook always runs slowly or if the performance issue is intermittent. This helps establish whether the cause is inherent to the workbook itself or due to external environmental factors.

If the workbook is consistently slow, the problem likely lies in the design or structure of the workbook. This could include overly complex calculations, unoptimized filters, large datasets being rendered in real-time, or inefficient live data connections. These issues often require workbook-level optimization strategies.

However, if the slowness is inconsistent, it could be influenced by external variables such as server load, network latency, concurrent user sessions, or scheduled background processes (like data extracts refreshing). In this case, a server-side investigation would be more appropriate.

Now let's examine why the other options are less ideal as the first question:

• B. While caching impacts performance, asking about it before understanding the frequency or consistency of the slowness skips over the broader diagnostic process. Also, caching is generally a server-level setting, not controlled directly by workbook authors.

• C. Asking if it runs faster in Tableau Desktop can help isolate server-related issues later, but without knowing the pattern of the slowness, this question may not be meaningful early in the troubleshooting process.
  
  

• D. The number of times the workbook has been opened provides usage insights, not direct help in determining why it's slow. It doesn’t diagnose performance and could mislead the analysis.

In conclusion, determining whether the issue is constant or variable sets the foundation for effective troubleshooting. Therefore, Option A is the best first question to ask.

Question 2:

In Tableau Server, when workbook permissions are not locked to the project, which two user types can sign in and edit the permissions for a workbook? (Choose two.)

A. The workbook's owner
B. Users assigned as Project Leaders for the project
C. Users with the Viewer role on both the project and workbook
D. Users with the Interactor role on the workbook

Correct Answers: A, B

Explanation:

Tableau Server’s permission model is built on a combination of user roles and project-level privileges. When workbook permissions are not locked to the project, specific users can edit workbook permissions based on their access rights.

• A. The workbook's owner: The owner of a workbook automatically has full control over that content, including the ability to edit permissions, delete, or transfer ownership, unless explicitly restricted by site-level settings. This makes the owner one of the primary users capable of managing permissions directly.

• B. Users assigned as Project Leaders: A Project Leader has administrator-level rights over the project and all its contents, including workbooks. They can edit permissions, even if they didn’t create the workbook. As long as the project isn’t locked, their elevated role allows them to manage access control for all content in that project.

The incorrect options:

• C. Users with the Viewer role: Viewers are limited to read-only access. They can view dashboards and reports but cannot modify or change permissions. Assigning Viewer role alone does not provide administrative privileges.

• D. Users with the Interactor role: Interactors can interact with workbooks (e.g., apply filters, use drill-downs), but they do not have rights to edit permissions. They are typical consumers of the content, not administrators.

In summary, only owners of the workbook and Project Leaders for the respective project have the necessary authority to modify permissions when the project’s permissions are not locked. Therefore, the correct answers are A and B.

Question 3

While preparing to install Tableau Server on a Windows system, which type of user account should be used to initiate the installation process?

A. NT AUTHORITY\NetworkService account
B. A standard local user account
C. An account that belongs to the local administrator group
D. A general domain user account

Correct Answer: C

Explanation:

Installing Tableau Server requires elevated system-level access to properly configure services, modify protected directories, adjust firewall settings, and apply system-wide permissions. Therefore, the installer must be executed using an account that has local administrative privileges on the server.

Option C, which refers to an account that is part of the local administrator group, is the most appropriate choice. This ensures the user has the authority to perform the necessary operations that modify system components during the installation process. Without administrative rights, Tableau Server installation may fail, cause partial configuration, or leave the server in an unstable or nonfunctional state.

Let’s break down the reasons why the other options are not suitable:

• A. NT AUTHORITY\NetworkService account: This is a special built-in Windows service account intended for low-privilege background services. It cannot be used for initiating software installations, especially ones requiring administrative access. While some Tableau services may later run under accounts with similar permissions, this account is not interactive and lacks installation rights.

• B. A standard local user account: While a local user may have access to basic system functions, unless it is explicitly granted administrative privileges, it won’t have sufficient access to install software like Tableau Server. This type of account is likely to fail during installation steps that involve changing system settings or starting services.

• D. A domain user account: Domain accounts are typically used in enterprise networks managed via Active Directory. However, a domain user doesn’t automatically have local admin rights unless it has been added to the server’s local administrator group. Therefore, unless that domain user has elevated privileges, this option alone is not sufficient.

In conclusion, the safest and most compliant way to install Tableau Server is by using a user account that is part of the local administrator group. This ensures the account has the correct access levels to configure services, manage Windows components, and complete the installation process reliably. Therefore, Option C is the best and most accurate choice.

Question 4:

Which three tools can an administrator use to create groups or projects in Tableau Server? (Select three options.)

A. Tableau Server browser-based user interface
B. Tableau Server REST API
C. tsm customize command
D. tabcmd command-line utility

Correct Answers: A, B, D

Explanation:

Creating groups and projects is a routine administrative task in Tableau Server used to manage users and organize content. There are multiple tools available to perform these operations, each suited to different contexts such as manual configuration, scripting, or API-based integration.

A. Tableau Server browser interface: This is the most accessible and user-friendly method for managing Tableau Server content. It provides a graphical interface where administrators can navigate to the appropriate sections and create groups or projects with just a few clicks. It’s ideal for one-time or ad hoc management tasks.

B. REST API: The REST API provides programmatic access to Tableau Server for a wide range of administrative operations, including creating groups and projects. This is particularly useful in environments that require automation, integration with other enterprise systems, or DevOps-style deployments. Scripts using the REST API can dynamically manage users, groups, and projects in real time.

D. tabcmd: The tabcmd (Tableau Command Line Utility) is a powerful scripting tool that allows administrators to perform bulk or repetitive tasks, including creating projects and groups. It’s useful for automating Tableau Server operations in scripts or batch jobs and works well in environments without the need for custom API development.

Now, let’s clarify why Option C is incorrect:

• C. tsm customize: The TSM (Tableau Services Manager) commands are used primarily for configuring Tableau Server settings, such as enabling SSL, setting port numbers, and customizing branding. The tsm customize command in particular is used for interface and configuration customizations (like logos or fonts), not for managing users, groups, or projects.

In summary, administrators who wish to create Tableau Server groups or projects should use one of the three correct tools—the web interface, REST API, or tabcmd—depending on their preferences and environment. These tools ensure that administrators can manage content both manually and through automation. Therefore, the correct answers are A, B, and D.

Question 5:

What are two benefits of using published data sources in Tableau compared to embedded data sources? (Select two.)

A. Restricts access to data by keeping it limited to a single workbook
B. Simplifies centralized management of data assets
C. Saves storage and optimizes resource use during refresh operations
D. Automatically installs necessary drivers on client machines

Correct Answers: B and C

Explanation:

When using Tableau in an enterprise or collaborative environment, published data sources offer several advantages over embedded data sources, particularly in areas of efficiency, governance, and scalability.

Option B: Centralized data management is easier
This is one of the main advantages of using published data sources. A published data source exists independently of any single workbook and resides on Tableau Server or Tableau Cloud. This allows multiple workbooks and users to connect to the same source, ensuring consistency in definitions, calculated fields, and data structures. With this setup, changes made to the data source can be centrally managed, reducing redundancy and improving data governance. It becomes easier for data stewards to update shared dimensions, hierarchies, or calculated metrics, while guaranteeing all connected dashboards reflect these changes consistently.

Option C: Storage space is conserved and refreshes are optimized
Published data sources also support more efficient use of system resources. When an extract is embedded in multiple workbooks, each one stores its own copy of the data and independently performs refreshes, leading to redundancy and higher load on storage and processing power. However, if a single published extract is used across multiple workbooks, only one copy of the data exists and only one scheduled refresh is required. This reduces the server workload, saves storage space, and enhances performance—especially useful when working with large datasets or scheduled data updates.

Now consider why the other options are incorrect:

Option A: Data is protected so that it is only available in one workbook
This describes a limitation of embedded data sources, not an advantage. Embedded data sources are confined to a specific workbook, making them less flexible. While this may offer control in isolated use cases, it restricts collaboration and reuse—two key strengths of published sources.

Option D: Drivers are automatically installed on each client’s machine
This is factually incorrect. Tableau does not automatically install database drivers. Each client machine must manually install the appropriate drivers if connecting to live data sources. This has nothing to do with whether the data source is embedded or published.

In summary, the primary benefits of using published data sources are centralized control and optimized resource usage. These features make them the preferred choice in environments that demand consistency and performance.

Question 6:

Which three of the following data platforms support Kerberos delegation when used with Tableau Server? (Select three.)

A. PostgreSQL
B. SAP HANA
C. Teradata
D. SQL Server

Correct Answers: B, C, D

Explanation:

Kerberos delegation allows Tableau Server to securely forward the user’s credentials to the underlying data source, enabling Single Sign-On (SSO) and ensuring that user-level security policies are respected at the database level. This is critical in environments with strong authentication requirements and helps maintain a seamless, secure user experience.

Option B: SAP HANA (Correct)
SAP HANA supports Kerberos authentication and is compatible with Kerberos delegation via Tableau Server. When properly configured, Tableau Server can delegate the authenticated user's credentials to HANA, so the user can be granted appropriate access without needing to re-authenticate. This helps enforce role-level security directly at the data layer and supports enterprise-grade security models.

Option C: Teradata (Correct)
Teradata also supports Kerberos delegation. Through this method, Tableau can pass the identity of the logged-in user to Teradata, allowing for authentication and authorization to be handled at the database level. This ensures accurate data access control and aligns with corporate SSO practices.

Option D: SQL Server (Correct)
SQL Server is one of the most widely used relational databases and fully supports Kerberos delegation. With proper configuration—including Service Principal Names (SPNs) and delegation permissions—Tableau Server can delegate the user’s identity to SQL Server, enabling secure access to data without prompting the user to log in again.

Option A: PostgreSQL (Incorrect)
While Tableau can connect to PostgreSQL using traditional authentication methods, it does not support Kerberos delegation with PostgreSQL. Therefore, identity propagation from Tableau Server to PostgreSQL for SSO is not available out of the box. This limits PostgreSQL’s integration with enterprise Kerberos-based authentication environments.

To summarize, Kerberos delegation is essential for ensuring secure identity propagation in a multi-tier architecture, and only SAP HANA, Teradata, and SQL Server support this functionality when used with Tableau Server. These data platforms allow organizations to apply consistent security policies and streamline user access.

Question 7:

To guarantee a full restoration of Tableau Server in case of system failure or migration, which three types of file formats should be included in the backup process? (Select three options.)

A. YML
B. HTTP
C. XML
D. JSON

Correct Answers: A, C, and D

Explanation:

When preparing a comprehensive backup strategy for Tableau Server, it’s not sufficient to only back up data like workbooks and user information. A complete and restorable backup should also include critical configuration and metadata files that govern how Tableau Server operates and integrates with your environment. Three key file types that should always be backed up are YML, XML, and JSON files, as they each play a distinct role in maintaining the server's functionality and behavior.

YML files, especially files like workgroup.yml, hold Tableau’s configuration settings. These settings include important parameters such as server port numbers, SSL settings, and other environmental configurations. Backing up these files ensures that during a restore or migration, the Tableau Server instance will retain its operational identity and behave exactly as before, avoiding misconfigurations or service failures.

XML files are also essential because many of Tableau's resources—such as Tableau Workbook files (.twb)—are built in XML format. These files include structured data about dashboards, filters, parameters, and data source connections. Ensuring you retain these files as part of the backup allows you to recover full workbooks and their embedded configurations, preserving user-designed logic and visualizations.

JSON files come into play particularly in REST API responses, automation scripts, or integration setups. These files often contain permission structures, user-role mappings, and deployment logic. For organizations leveraging scripting or DevOps pipelines to manage Tableau deployments, JSON files are critical for reapplying those automation configurations post-restore.

Now, let’s consider the incorrect option:

HTTP is not a file format; it is a communication protocol used to transmit requests and responses between clients (like browsers or Tableau Desktop) and Tableau Server. Since it’s not a data or configuration file, there is nothing to “back up” in the form of HTTP.

In summary, to ensure the continuity and integrity of your Tableau Server deployment, your backup must cover both data content and its underlying configuration. Including YML, XML, and JSON files in your backup strategy ensures a consistent, accurate recovery in the event of a failure, upgrade, or environment migration.

Question 8:

In Tableau, which three of the following items can be directly contained within a project folder? (Choose three.)

A. Workbooks
B. Nested Projects
C. Groups
D. Data Sources

Correct Answers: A, B, and D

Explanation:

In Tableau Server or Tableau Online, a project serves as a container to organize and manage various content resources. These containers help implement role-based access control, promote content discoverability, and facilitate collaboration among users. Understanding what can and cannot be stored within a project is crucial for effective Tableau administration.

A. Workbooks are the primary analytical deliverables in Tableau. They consist of dashboards and sheets that visualize insights from connected data. Projects provide a structured place to store workbooks related to a specific department or business purpose—for instance, a "Finance Analytics" project could house all financial reporting dashboards. This grouping not only promotes logical organization but also allows administrators to apply uniform permissions to all contained workbooks.

B. Nested Projects allow administrators to build hierarchical structures within Tableau. For example, under a parent project called “Regional Sales,” sub-projects like “North America,” “Europe,” and “Asia” can be created. Each nested project can inherit or override permissions from its parent. This is especially useful in large organizations that need scalable content segmentation and governance.

D. Data Sources are another critical component that can reside within projects. A data source might include connections to databases like SQL Server or Google BigQuery and can be shared across multiple workbooks. Storing data sources inside projects ensures they’re easily discoverable and access-controlled alongside the workbooks that use them. This helps with versioning, reuse, and ensuring data consistency across the organization.

Now let’s discuss the incorrect option:

C. Groups refer to collections of users, not content. Groups are used for access control, allowing administrators to grant permissions at the project, workbook, or data source level based on team membership or roles. However, groups are not stored inside projects; they exist as part of the user and security management system.

To summarize, projects in Tableau serve as flexible content containers capable of holding workbooks, nested sub-projects, and data sources, thereby supporting organized, secure, and scalable content management. Groups, while essential to permissioning, do not reside within projects, and thus, the correct items that can be contained in a project are A, B, and D.

Question 9:

Your Tableau Server is configured to authenticate users via Active Directory. Which statement best describes what happens when you import a group from Active Directory into Tableau Server?

A. You can change the name of a group during import, although this will not change the group’s name in Active Directory.
B. New users created as a result of importing a group are assigned the site role specified during the import.
C. If an imported group contains users that already exist in Tableau Server, their site role will be updated to match the imported setting.
D. Importing a group from Active Directory requires a .csv file listing user IDs.

Correct Answer: B

Explanation:

When importing a group from Active Directory (AD) into Tableau Server, you enable centralized management of user accounts and streamline access control. Tableau automatically identifies which users in the AD group do not yet have accounts in Tableau Server and creates them during import, assigning them the site role specified during the process.

This makes Option B correct. It reflects a key functionality of Tableau Server’s integration with Active Directory—automating the account creation and site role assignment process for new users based on your configuration.

Let’s examine why the other choices are incorrect:

• A is partially correct but focuses on the display name aspect. While you can rename groups in Tableau for internal visibility, the AD group name remains unchanged. Still, the core of the import process concerns user provisioning, not naming.

• C is incorrect because existing users who are already registered in Tableau Server will retain their current site roles during group import. Their roles are not overridden by the import settings unless explicitly updated afterward.

• D is false. You do not need a .csv file to import an AD group. Tableau supports direct synchronization with Active Directory through its admin interface or CLI, making the process seamless without needing manual file inputs.

In summary, Tableau Server uses Active Directory integration to simplify administration. When importing groups, only new users get assigned the specified role, and existing users are unaffected. Hence, B is the most accurate and complete answer.

Question 10:

A workbook was published on Tableau Server ten days ago. The workbook is visible but does not appear in search results. 

What action should the administrator take to resolve this issue?

A. Run the tsm maintenance reindex-search command.
B. Instruct the user to add tags to the workbook.
C. Instruct the user to log out and log back in.
D. Instruct the user to re-publish the workbook with keywords.

Correct Answer: A

Explanation:

This scenario indicates that the workbook is published and accessible, but cannot be located via the search function. This suggests a likely issue with Tableau Server’s search indexing system, not with workbook visibility or user permissions.

The correct course of action is to rebuild the search index using the tsm maintenance reindex-search command. This command instructs Tableau Server to regenerate the internal search index, ensuring that all content—workbooks, dashboards, datasources—is correctly catalogued and discoverable.

Let’s break down why the other options fall short:

• B (add tags) might improve visibility once the index is functional, but tags alone won’t correct an out-of-date or corrupted index. If the system isn’t indexing new content properly, tags won’t solve the root issue.

• C (logging out and back in) has no impact on how the server indexes content. The problem is with the backend index, not the user’s session.

• D (re-publish with keywords) only helps if the issue is related to metadata or title inconsistencies. However, it does not resolve indexing problems. Even a perfectly described workbook won’t appear if it's not indexed.

In conclusion, the inability to locate a visible workbook through search typically points to a search indexing issue. The tsm maintenance reindex-search command is the most effective way to resolve this, making A the correct answer.