Last Updated On : 17-Nov-2026


Salesforce Certified Tableau Architect Practice Test

Prepare with our free Salesforce Certified Tableau Architect sample questions and pass with confidence. Our Salesforce-Tableau-Architect practice test is designed to help you succeed on exam day.

200 Questions
Salesforce 2026

In a Tableau Server deployment, what is a key consideration when configuring an unlicensed node?

A. The unlicensed node should have a higher processing power than the licensed nodes to manage intensive tasks

B. The unlicensed node must be in the same physical location as the licensed nodes for effective communication

C. Ensure the unlicensed node is properly networked and configured to communicate with the licensed nodes

D. The unlicensed node requires a separate storage system from the licensed nodes

C.   Ensure the unlicensed node is properly networked and configured to communicate with the licensed nodes

Explanation:

In a Tableau Server deployment, an unlicensed node can still perform certain functions without consuming additional core-based licenses, such as handling authentication requests, acting as a gateway, or running specific services like the Repository or Coordination Service in a high-availability setup. However, for the unlicensed node to effectively serve these roles, it must be properly networked and configured to communicate with the licensed nodes. This includes correct network configuration, firewall rules, DNS resolution, and time synchronization. Without proper communication, the unlicensed node cannot participate in the cluster or perform its designated functions, potentially causing authentication delays or service disruptions.

Why Other Options Are Incorrect

A. Higher processing power:
Unlicensed nodes typically handle lightweight tasks like authentication or gateway services, not resource-intensive tasks such as VizQL or Backgrounder processing. They do not require higher processing power than licensed nodes.

B. Same physical location:
While low latency is beneficial, the unlicensed node does not need to be in the same physical location as licensed nodes. Network connectivity is more important than physical proximity.

D. Separate storage system:
Unlicensed nodes do not require a separate storage system. Storage requirements depend on the services the node runs, not its licensing status.

References
Tableau Server Licensing: Licensed vs. unlicensed node capabilities.
Tableau Server Architecture: Role of unlicensed nodes in the cluster.
Tableau Server Networking: Configuration requirements for cluster communication.

When troubleshooting an issue in Tableau Server, you need to locate and interpret installation logs. Where are these logs typically found, and what information do they primarily provide?

A. In the database server, providing information about database queries

B. In the Tableau Server data directory, offering details on user interactions

C. In the Tableau Server logs directory, containing details on installation processes and errors

D. In the operating system's event viewer, showing system-level events

C.   In the Tableau Server logs directory, containing details on installation processes and errors

Explanation:

When troubleshooting Tableau Server issues, installation logs are found in the Tableau Server logs directory. On Windows, this is typically C:\ProgramData\Tableau\Tableau Server\data\tabsvc\logs\; on Linux, it is /var/opt/tableau/tableau_server/data/tabsvc/logs/. These logs provide detailed information about installation or upgrade processes, recording each step along with errors and status messages that help administrators identify root causes. Installation logs are essential for diagnosing failures, especially when combined with the tabadmin command-line tool.

Why Other Options Are Incorrect
A. Database server:Database logs store query execution details and database performance information, not Tableau Server installation logs. This is a separate system with different log files.

B. Data directory: The data directory stores user content like extracts and repository data. It does not contain installation-related logs.

D. Operating system's event viewer:
While the Windows Event Viewer may contain some system-level events related to Tableau Server, the detailed installation logs are specifically stored in the Tableau Server logs directory, as these logs are generated by Tableau's own installation processes rather than the OS.

References
Tableau Server Log Locations: Installation log file paths.
Tableau Server Administrator Guide: Log file troubleshooting.
Tableau Server Logging: Installation and configuration logs.

When troubleshooting Connected App authentication issues in Tableau Server, what factor should be primarily investigated?

A. The speed and stability of the internet connection between the connected app and Tableau Server

B. The correctness and validity of the client credentials used by the connected app

C. The version compatibility of Tableau Server with the connected app

D. The frequency of data synchronization between the connected app and Tableau Server

B.   The correctness and validity of the client credentials used by the connected app

Explanation:

When troubleshooting Connected App authentication issues in Tableau Server, the primary factor to investigate is the correctness and validity of the client credentials—specifically the Client ID and Client Secret. Connected Apps use OAuth 2.0 for authentication and authorization, and the most common cause of authentication failures is incorrect, expired, or misconfigured credentials. If the Client ID or Client Secret is invalid, expired, or not properly matched between the Connected App configuration in Tableau Server and the external application, the authentication handshake will fail, preventing access. Administrators should verify that the credentials are correctly configured, have not expired, and that the Connected App has the appropriate permissions and scope settings to access the required Tableau resources.

Why Other Options Are Incorrect

A. Internet connection speed: While connectivity is required, the primary authentication issue is credential validation, not network speed. A slow connection would cause timeouts but not authentication failures.

C. Version compatibility: Tableau Server generally supports a stable OAuth 2.0 implementation across versions. Version compatibility issues are rare compared to credential misconfiguration.

D. Data synchronization frequency: The frequency of data synchronization does not affect the authentication process. Authentication is a prerequisite for data access, not dependent on sync timing.

References
Tableau Connected Apps: Authentication using Client ID and Client Secret.
Tableau Server OAuth 2.0: Troubleshooting credential issues.
Tableau Server Administrator Guide: Connected App authentication troubleshooting.

During the installation of Tableau Server on a Windows system, you encounter a permissions error. What should be your initial action to address this issue?

A. Disabling User Account Control (UAC) on the Windows system

B. Checking and adjusting the security permissions of the Tableau Server installation directory

C. Granting administrator privileges to all user accounts on the Windows system

D. Reinstalling the Windows operating system to reset system permissions

B.   Checking and adjusting the security permissions of the Tableau Server installation directory

Explanation:

When encountering a permissions error during Tableau Server installation on Windows, the most appropriate initial action is to check and adjust the security permissions of the installation directory. Tableau Server installation requires that the user running the installation has Write and Modify permissions to the target installation directory (typically C:\Program Files\Tableau\Tableau Server). Insufficient permissions can cause the installer to fail when creating files or writing registry entries. By verifying and correcting these permissions, you can resolve most common installation permissions issues without drastic measures.

Why Other Options Are Incorrect

A. Disabling UAC:
Temporarily disabling UAC may resolve some issues but is a security risk and should be avoided as a first step. UAC is designed to prevent unauthorized system changes, and it is better to understand and resolve the underlying permissions issue.

C. Granting admin privileges to all users:
This is a security risk and unnecessary. Only the account performing the installation needs appropriate permissions, not all users.

D. Reinstalling Windows:
This is an extreme measure that is rarely required. It is time-consuming and should only be considered after all other troubleshooting options have failed.

References
Tableau Server Windows Installation: Permissions requirements.
Windows File System Permissions: Setting permissions for installation directories.
Tableau Server Administrator Guide: Troubleshooting installation errors.

In the context of a Tableau Server high-availability setup, what is a crucial consideration when con-figuring a coordination ensemble?

A. The ensemble should be configured on a single node to centralize coordination control

B. Ensemble nodes should be distributed across different physical locations for geographical redundancy

C. It's important to configure an odd number of ensemble nodes to prevent split-brain scenarios

D. Coordination ensemble nodes require significantly more storage than other nodes in the cluster

C.   It's important to configure an odd number of ensemble nodes to prevent split-brain scenarios

Explanation:

In a Tableau Server high-availability setup, the coordination ensemble (based on ZooKeeper) is responsible for managing the election process for the active repository and synchronizing cluster configurations. A critical consideration when configuring this ensemble is to use an odd number of nodes (typically 3, 5, or 7) to prevent split-brain scenarios. In distributed systems, a split-brain occurs when two nodes simultaneously believe they are the active coordinator, leading to conflicting writes and data corruption. The ZooKeeper ensemble uses a majority-based quorum mechanism to elect the active repository and maintain consensus. An odd number of nodes ensures that a clear majority can always be established, even during network partitions. The recommended ensemble size for Tableau Server is typically 3 nodes for most deployments, with at least 3 nodes required for high availability. This configuration ensures that the cluster can continue operating even if one node fails, maintaining a stable coordination service for the entire Tableau Server deployment.

Why Other Options Are Incorrect

A. Single-node ensemble:
This creates a single point of failure and does not provide high availability. The coordination ensemble must be distributed to ensure fault tolerance.

B. Geographical redundancy:
While distributing ensemble nodes across different physical locations is a good practice for disaster recovery, the most critical consideration for avoiding split-brain scenarios is the odd number of nodes.

D. Significantly more storage:
Coordination ensemble nodes store metadata and configuration data, not user content or extracts. Their storage requirements are minimal compared to nodes running other processes.

References
Tableau Server Coordination Ensemble: Importance of odd number of nodes.
Tableau Server High Availability: ZooKeeper ensemble configuration.
Tableau Server Repository and Coordination Services: Split-brain prevention and quorum.

Salesforce-Tableau-Architect Exam Questions - Home Previous
Page 7 out of 40 Pages