• Home
• Tableau Exams
• SCA-C01 - Tableau Server Certified Associate

SCA-C01 Tableau Practice Test Questions and Exam Dumps

Question 1

A user reports that a newly published workbook is running slowly. What is the first question you should ask the user to help investigate 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 a user reports that a Tableau workbook is running slowly, the first and most effective question a business analyst or Tableau administrator should ask is whether the performance issue is consistent or intermittent. This foundational question, as stated in option A, helps establish a clear baseline for diagnosing the problem. Understanding whether the workbook always runs slowly or if the slowness varies depending on time or context is essential because it significantly narrows the potential causes.

If the user indicates that the workbook always runs slowly, regardless of the time or environment, it suggests a fundamental issue with the workbook’s design, such as poorly constructed visualizations, excessive use of quick filters, complex calculated fields, or inefficient data source connections. In this case, the analyst would likely focus on workbook optimization strategies like reducing the number of data points rendered, simplifying calculations, or using extracts instead of live connections.

Conversely, if the performance issue is intermittent, it may be tied to external variables such as server load, network latency, background jobs, user concurrency, or data refresh operations. Knowing this, the analyst can then explore usage logs, performance monitoring dashboards, and server health metrics to identify bottlenecks or spikes in activity that coincide with performance degradation.

Now, let’s assess why the other options, while relevant, are not the first question to ask:

• B. Did you enable caching on the workbook?
  While caching can impact performance, this question jumps to a specific configuration detail without first understanding the broader nature of the problem. Moreover, caching behavior in Tableau is often managed at the server or site level, not typically at the workbook level by the end user.

• C. Does it run any faster in Tableau Desktop?
  This is a valuable diagnostic question, but it should come after establishing whether the issue is persistent or intermittent. Comparing performance between Tableau Desktop and Tableau Server can help isolate whether the issue is server-related or inherent to the workbook itself. However, asking this too early may not provide meaningful insight without context.

• D. How many times have you opened the workbook in Tableau Server?
  This question is less relevant to performance troubleshooting. The number of times the workbook has been opened might be helpful in usage analysis, but it does not contribute directly to diagnosing slowness unless combined with server resource metrics or caching considerations. It also may confuse the user or lead them to believe that workbook access count directly impacts performance, which is rarely the case unless dealing with concurrency at scale.

In conclusion, the best first question to ask is whether the workbook always runs slowly or if its performance varies. This initial inquiry lays the foundation for targeted and effective troubleshooting by distinguishing between design-related and environment-related issues. Therefore, the correct answer is A.

Question 2

Which two types of users can sign in to Tableau Server and edit the permissions for a workbook in a project when permissions are NOT set to Locked to the project? (Choose two.)

A. The workbook's owner.
B. Users set to Project Leader for the workbook’s project.
C. Users that have the project and workbook Viewer role.
D. Users that have the workbook Interactor role.

Correct Answer: A, B

Explanation:

1. A. The workbook's owner (Correct): The owner of a workbook has full control over the workbook, including the ability to edit permissions for it. This applies regardless of whether permissions are locked at the project level.

2. B. Users set to Project Leader for the workbook’s project (Correct): Project Leaders have administrative rights at the project level, which include the ability to modify permissions for workbooks within the project. These users can edit permissions even if permissions are not locked to the project.

3. C. Users that have the project and workbook Viewer role (Incorrect): Viewers have only the ability to view the content and are not granted permission to modify or edit the permissions for workbooks or other resources. This would not allow them to edit permissions.

4. D. Users that have the workbook Interactor role (Incorrect): The Interactor role provides users with the ability to interact with the workbook, such as filtering and viewing data. However, they do not have permission to edit the permissions of the workbook.

The two types of users who can sign in and edit the permissions for a workbook when permissions are not locked to the project are the workbook's owner and users set to Project Leader for the workbook's project.

Question 3

When preparing to install Tableau Server, which type of user account should be used to execute the installation program?

A. An NT AUTHORITY\NetworkService account
B. A local user account
C. An account in the local administrator group
D. A domain user account

Correct answer:  C

Explanation:

Installing Tableau Server requires elevated privileges because the installation process performs several critical tasks at the system level. These include creating and modifying services, writing to protected directories, configuring firewall rules, and managing Windows permissions. To perform these actions successfully, the account running the installation must have local administrative rights on the server. Therefore, the correct account type is one that is a member of the local administrator group, as indicated in option C.

An account in the local administrator group provides the necessary level of access to install software, configure services, and make system-wide changes. Without these privileges, the installation process will likely fail or result in a misconfigured Tableau Server instance, which can be difficult to troubleshoot and fix after the fact. This is particularly important for initial installation, as Tableau sets up multiple processes and services that run under specific permissions and may interact with other system-level resources.

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

• A. An NT AUTHORITY\NetworkService account:
  This is a built-in Windows account used to run services with limited permissions. It is not designed for interactive use or for installing software. While Tableau services may be configured to run under this or a similar service account after installation (under specific configurations), the installation itself cannot be initiated using this type of account. It lacks the necessary administrative privileges required to make system-wide changes.

• B. A local user account:
  Local user accounts typically do not have administrative privileges by default. Using a local user account that isn’t part of the administrator group would likely result in insufficient access to install Tableau Server properly. Even if the account is local, unless it is explicitly granted administrative rights, it cannot execute the full scope of required installation tasks.

• D. A domain user account:
  A domain user account is managed through Active Directory and is typically used in enterprise environments. However, simply being a domain user doesn’t automatically grant local administrator privileges. If the domain user has been added to the local administrator group, then it would be suitable. But as described in this option, the account type alone isn’t sufficient—it depends on whether it has the correct permissions. Therefore, the more accurate and complete answer is C, which directly states the necessary privilege level.

In conclusion, the Tableau Server installation must be executed by an account that has local administrative rights, which ensures the account can perform all system-level tasks required during the installation process. This makes C the correct answer.

Question 4

Which three methods should an administrator use to create a Tableau Server group or project? (Choose three.)

A. Tableau Server browser interface
B. REST API
C. tsm customize
D. tabcmd

Correct Answer: A, B, D

Explanation:

1. A. Tableau Server browser interface (Correct): The Tableau Server browser interface allows administrators to easily create groups and projects through the graphical user interface. This is one of the most common and user-friendly methods for administrators to create and manage groups and projects.

2. B. REST API (Correct): The REST API can be used to automate and programmatically create groups and projects. This method is useful for administrators who want to integrate Tableau Server management tasks into custom applications or workflows.

3. C. tsm customize (Incorrect): The tsm customize command is not used to create groups or projects. It is typically used for managing Tableau Server configuration settings (such as customizing the Tableau Server interface, deploying custom configurations, etc.), not for creating groups or projects.

4. D. tabcmd (Correct): The tabcmd command-line utility can be used to automate tasks like creating projects and groups. Administrators can use tabcmd scripts to perform administrative functions in Tableau Server, including creating groups and projects.

Conclusion: The three methods that an administrator should use to create a Tableau Server group or project are through the Tableau Server browser interface, the REST API, and tabcmd.

Question 5

Which two of the following statements describe advantages of using published data sources over embedded data sources? (Select two options.)

A. Data is protected so that it is only available in one workbook.
B. Centralized data management is easier.
C. Storage space is conserved and resource usage during data refreshes is optimized.
D. Drivers are automatically installed on each client’s machine.

Correct answers:  B and C

Explanation:

Published data sources provide several significant benefits over embedded data sources, particularly in environments where data governance, scalability, and performance optimization are priorities. The key advantages include centralized data management and optimized resource usage during data refreshes, both of which are critical in enterprise-level Tableau deployments.

Let’s explore the correct choices in detail:

• B. Centralized data management is easier:
  This is a core advantage of published data sources. When data sources are published to Tableau Server or Tableau Cloud, they can be centrally managed, maintained, and shared across multiple workbooks. This allows data stewards or administrators to make updates to the data source (such as modifying calculated fields, renaming columns, or updating connections) without requiring changes in each individual workbook. It promotes consistency and accuracy, ensuring that all users are working with the same definitions and data structures. It also makes enforcing data governance policies much more practical.

• C. Storage space is conserved and resource usage during data refreshes is optimized:
  Published data sources, especially when used with extracts, can be refreshed once and reused by multiple workbooks and dashboards. This reduces redundancy, as opposed to having separate embedded copies of the same data source in multiple workbooks, which could each perform individual refreshes and consume more server resources. By centralizing data refreshes at the published source level, you conserve storage space and improve efficiency during scheduled extract refreshes and background processing tasks.

Now let’s look at why the other options are incorrect:

• A. Data is protected so that it is only available in one workbook:
  This statement actually describes a limitation of embedded data sources, not an advantage. Embedded data sources are tied to the workbook in which they reside. While this can provide isolation, it limits reusability and consistency. Published data sources, by contrast, are intended to be shared across multiple workbooks and users, facilitating broader access and collaboration (while still allowing for access controls and permissions).

• D. Drivers are automatically installed on each client’s machine:
  This is not true. Tableau does not automatically install database drivers on client machines simply because a data source is published. Users still need the correct database drivers installed locally (for Tableau Desktop) or on the Tableau Server if the data connection is live. Managing drivers is a separate concern from the distinction between embedded and published data sources. This statement therefore has no bearing on the advantages of published sources.

In summary, centralized management and resource-efficient refreshes are two of the most valuable benefits of using published data sources, especially in shared, collaborative environments. These capabilities reduce duplication, promote consistency, and support effective data governance strategies. Thus, the correct answers are B and C.

Question 6

Which three data sources support Kerberos delegation with Tableau Server? (Choose three.)

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

Correct Answer: B, C, D

Explanation:

1. A. PostgreSQL (Incorrect): PostgreSQL does not natively support Kerberos delegation with Tableau Server. While Tableau can connect to PostgreSQL, it does not provide built-in Kerberos delegation for single sign-on (SSO) or identity propagation from Tableau Server to PostgreSQL.

2. B. SAP HANA (Correct): SAP HANA supports Kerberos authentication and can be configured for Kerberos delegation with Tableau Server. This allows Tableau to pass the user’s credentials securely to the database and enables seamless authentication without requiring the user to log in multiple times.

3. C. Teradata (Correct): Teradata supports Kerberos authentication and can be configured for Kerberos delegation with Tableau Server. This allows Tableau to leverage Kerberos to authenticate and delegate user credentials to Teradata, ensuring secure access to data.

4. D. SQL Server (Correct): SQL Server supports Kerberos authentication and can be set up for Kerberos delegation with Tableau Server. By using Kerberos, Tableau can securely pass user credentials to SQL Server, allowing users to authenticate once and access data seamlessly.

Conclusion: The three data sources that support Kerberos delegation with Tableau Server are SAP HANA, Teradata, and SQL Server.

Question 7

To ensure that Tableau Server can be fully restored in the event of failure or migration, which three types of data should you back up? (Select three options.)

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

Correct answers:  A, C, and D

Explanation:

To successfully restore a Tableau Server environment, it's critical to back up not only the repository data (such as content and users) but also the configuration files and other metadata used by the server for setup, security, and customizations. Among the file types most commonly involved in Tableau Server backups are YML, XML, and JSON files, each serving a different function in the system's operation and restoration process.

Let’s break down the correct options:

• A. YML:
  YML (YAML Ain’t Markup Language) files are used by Tableau Server to store configuration settings. The most notable file of this type is the workgroup.yml file, which contains server-specific configuration details like ports, services, and protocol settings. During a restore or migration, having these configuration files ensures that the server environment can be rebuilt consistently and that services will behave as expected. Since these files govern how Tableau Server operates, backing them up is essential.

• C. XML:
  XML files are often used by Tableau to store workbook metadata, site settings, and data source information. Tableau workbook files themselves (with extensions like .twb) are structured in XML. Backing up these files, especially when they are published or integrated into automation or scripting, ensures you have access to workbook definitions, schema details, and other metadata that may be important for recovery or version tracking.

• D. JSON:
  JSON (JavaScript Object Notation) is widely used in Tableau’s REST API responses and may also be part of configurations for scripting or deployment tools. In environments with automated deployment or server configurations maintained via scripting, JSON files often hold user permission settings, site configurations, or custom application integrations. These should be backed up if they're part of your configuration management or automation processes to ensure you can restore system behavior and permissions accurately.

Now, let’s consider the incorrect option:

• B. HTTP:
  HTTP is not a file format but rather a protocol used for communication between clients (e.g., Tableau Desktop, browsers) and Tableau Server. You don't back up HTTP—it is a transport mechanism, not a type of data. Therefore, this option is not applicable to the context of file-based backup and restore operations in Tableau Server.

Backing up Tableau Server effectively requires more than just content; it requires preserving the configuration and operational metadata that govern how Tableau behaves. By securing your YML, XML, and JSON files as part of your backup strategy, you ensure that both the server's infrastructure and its user-facing content can be reliably restored.

Thus, the correct answers are A, C, and D.

Question 8

Which three items can be contained in a project? (Choose three.)

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

Correct Answer: A, B, D

Explanation:

In Tableau, a project is a container or organizational unit used to group and manage various types of resources, including workbooks, data sources, and even nested projects. Understanding what can be contained within a project is essential for effectively managing content in Tableau Server or Tableau Online.

A. Workbooks (Correct):

Workbooks are the primary deliverables in Tableau, containing dashboards, worksheets, and visualizations. A workbook is essentially a file in Tableau that users interact with to visualize and analyze data. Projects serve as organizational units for grouping these workbooks. By placing workbooks in projects, administrators and users can apply consistent access control, organizational structure, and permissions at a granular level. Projects make it easier for teams to work collaboratively on data analysis, as related workbooks can be grouped together.

When working with Tableau Server, users can browse through projects to find workbooks related to specific teams or objectives. For example, a project could be named “Marketing Analytics,” and within that project, several workbooks could focus on different aspects of marketing, such as social media analysis, customer segmentation, or campaign performance.

B. Nested Projects (Correct):

Nested projects allow you to create a hierarchical structure within Tableau Server, where projects are contained within other projects. This feature enables better organization of resources at scale, especially in large organizations. For example, within a primary project called “Sales,” you might have nested projects for “North America Sales,” “Europe Sales,” and “Asia Sales.” Each of these nested projects would contain relevant workbooks and data sources related to the respective regions.

Nested projects can also inherit the permissions of their parent projects, which simplifies the management of access control, reducing the need to manually configure permissions for each individual nested project. This feature helps to improve scalability and provides a logical structure for organizing content.

C. Groups (Incorrect):

While groups are important in Tableau for organizing users and assigning permissions, they are not part of a project’s content. A group in Tableau is used for user management, allowing administrators to assign permissions and control access to projects, workbooks, and data sources based on user roles. Groups allow for more efficient management, especially in larger organizations where different teams need access to different content. However, groups are not "contained" within projects but rather are related to access control and user management.

D. Data Sources (Correct):

A data source in Tableau represents a connection to a data set, and it can be contained within a project. Data sources are used in Tableau workbooks to provide the necessary data for analysis. By grouping related data sources into projects, administrators can control which users and workbooks have access to specific data. Projects also allow for better management of data sources, especially in cases where multiple workbooks rely on the same data.

For instance, in a “Sales” project, there may be a common data source for sales transactions that is used across multiple workbooks. Storing the data source in the same project ensures that all relevant resources are properly organized and accessible to the appropriate users.

Question 9

Your Tableau Server deployment uses Active Directory authentication. Which statement accurately describes the process of importing a group from Active Directory?

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 any users that have Tableau Server accounts, their site role will be changed to match the site role specified during the import.
D. Importing a group from Active Directory requires a .csv file that lists user IDs.

Correct answer B

Explanation:

When you import a group from Active Directory (AD) into Tableau Server, several steps and considerations are involved, particularly related to how the imported users and groups are handled within Tableau. Active Directory integration simplifies user management by allowing Tableau Server to automatically synchronize with AD, avoiding the need to manually create users in Tableau. However, there are some specific nuances regarding site roles, user creation, and group management during the import process. Let’s break down the correct answer and other options:

• B. New users created as a result of importing a group are assigned the site role specified during the import:
  This statement is correct because, when importing a group from Active Directory, new users (users who are part of the group but don’t yet have Tableau Server accounts) are automatically created in Tableau Server. These users are assigned a site role based on the configuration you set during the import process. For example, if you choose to assign the site role as Viewer during the import, all new users from that group will be assigned the Viewer site role. This behavior allows for efficient user role management based on group membership in AD.

Now, let’s examine why the other options are incorrect:

• A. You can change the name of a group during import, although this will not change the group’s name in Active Directory:
  This is not entirely accurate. While you can assign a custom name to a group in Tableau Server during the import process, the group’s name in Active Directory remains unchanged. However, the custom name in Tableau is used within the server for display purposes, and it’s independent of AD. This option does not describe the core process accurately since it focuses on the naming aspect and could be seen as misleading when the focus is more on roles and user management.

• C. If an imported group contains any users that have Tableau Server accounts, their site role will be changed to match the site role specified during the import:
  This statement is incorrect because, when importing a group, users who already have Tableau Server accounts are not automatically assigned new roles during the import process. Existing users in the group retain their current site roles unless manually updated afterward. The import process assigns the specified site role only to newly created users (those not previously registered in Tableau Server).

• D. Importing a group from Active Directory requires a .csv file that lists user IDs:
  This statement is incorrect. You do not need a .csv file to import a group from Active Directory. Tableau Server is designed to directly sync with Active Directory, and the process is handled through Tableau's administrative interface or command-line tools. The synchronization occurs automatically based on the AD group membership, and there is no need for an external .csv file to facilitate this import.

In summary, when you import a group from Active Directory into Tableau Server, the primary task is the automatic creation of users (if they don’t already exist on Tableau Server) and the assignment of site roles based on the import settings. Therefore, the correct answer is B, as it accurately describes the behavior of Tableau Server during this process.

Question 10

A user published a workbook on Tableau Server ten days ago. The workbook is visible on the server, but the user is unable to locate it using the search function. What action should be taken to fix 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 then log back in.
D. Instruct the user to re-publish the workbook with keywords.

Correct answer:  A

Explanation:

The issue described in the question relates to the search functionality within Tableau Server. The user can see the workbook, meaning it has been successfully published, but the workbook is not appearing in search results. This typically suggests that the search index may not have been updated or properly synchronized, which is a common issue in Tableau Server environments.

Let’s break down the correct answer and other options:

• A. Run the tsm maintenance reindex-search command:
  This is the correct solution. Tableau Server uses an index to improve search performance. If the search index becomes outdated or corrupted, it can result in search issues, like the one described in the question, where a workbook is visible but not searchable. Running the tsm maintenance reindex-search command will rebuild the search index, ensuring that all published content, including workbooks, is properly indexed and searchable. This is a common administrative task for resolving search issues in Tableau Server.

Now, let’s examine why the other options are not suitable:

• B. Instruct the user to add tags to the workbook:
  While adding tags to a workbook can help improve searchability by making it easier to categorize and filter content, it won’t directly fix the issue of the workbook not appearing in search results. The underlying problem seems to be related to the search index, which the reindexing command will address. Tags are helpful for improving search results once indexing is properly set up, but they won’t resolve the core problem here.

• C. Instruct the user to log out and then log back in:
  Logging out and logging back in might resolve some session-related issues, but it will not solve problems related to search indexing. The issue described is likely tied to Tableau Server's search index, not the user's session. Therefore, this action would not have any impact on the workbook’s searchability.

• D. Instruct the user to re-publish the workbook with keywords:
  Re-publishing the workbook with keywords might help if the workbook is not appearing because of the lack of metadata, but it won’t resolve an indexing issue. If the underlying problem is that the search index is out of date or not properly synced, re-publishing the workbook will not trigger an automatic reindexing of the search. The reindex-search command is the correct administrative step to ensure that the search functionality works properly across all workbooks.

In summary, to resolve the issue of the workbook not appearing in search results, the most effective action is to reindex the search functionality using the tsm maintenance reindex-search command. This will rebuild the search index and allow the workbook to be found in search queries. Therefore, the correct answer is A.