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 troubleshooting Mutual SSL authentication issues on Tableau Server, what is a common area to investigate?

A. The compatibility of SSL certificates with different web browsers

B. The expiration dates of the SSL certificates on both the client and server

C. The network bandwidth between the client and the Tableau Server

D. The version of Tableau Server in relation to the SSL protocol version

B.   The expiration dates of the SSL certificates on both the client and server

Explanation:

When troubleshooting Mutual SSL authentication issues on Tableau Server, certificate expiration is a common area to investigate. Mutual SSL requires both the client and server to present valid certificates during the TLS handshake. If either certificate has expired, the authentication fails. Tableau Server logs may display errors such as "Certificate Expired" or "SSL Handshake Failed." It is essential to verify that the server certificate, client certificate, and the Certificate Authority (CA) chain are all current and within their validity periods.

Why Other Options Are Incorrect

A. Browser compatibility:
Browsers may display warnings for untrusted certificates, but the handshake uses standard TLS protocols; it is not browser-specific.

C. Network bandwidth:
Network speed does not affect the outcome of Mutual SSL authentication.

D. SSL protocol version:
While protocol compatibility is relevant, Tableau Server typically supports a range of TLS versions. Expired certificates are a more common issue.

References
Tableau Server Mutual SSL: Certificate expiration troubleshooting.
Tableau Server Security: SSL certificate lifecycle management.
Tableau Server Administrator Guide: Common authentication errors.

During the installation of Tableau Server on Linux, what step must be taken to ensure a smooth installation process using either CLI or the Installation Wizard?

A. Ensuring that the Linux server has a minimum of 16GB of RAM

B. Running a pre-installation script to automatically configure all server dependencies

C. Creating a dedicated Tableau user account and group on the Linux system

D. Temporarily disabling the SELinux policy on the Linux server

C.   Creating a dedicated Tableau user account and group on the Linux system

Explanation:

When installing Tableau Server on Linux, one of the most critical preparatory steps is creating a dedicated Tableau user account and group. This account, typically named tableau, is used to run Tableau Server processes and own the Tableau Server directories. The official installation documentation emphasizes that "you must create a user account for the Tableau Server installation." This account should have a home directory and be configured to start automatically at system boot. The account ownership ensures proper file system permissions, maintains security isolation from other system processes, and allows Tableau Server services to operate with the necessary privileges without requiring root access. Additionally, the installation script initialize-tsm can be run with the --create-user option to automatically set up the required user account and permissions during installation.

Why Other Options Are Incorrect

A. Minimum 16GB RAM:
While Tableau Server has minimum system requirements, the specific amount varies by deployment scale. RAM is a system requirement, not a step that ensures smooth installation.

B. Running pre-installation script:
While Tableau Server on Linux includes a dependency checker, it does not automatically configure all server dependencies. Many dependencies must be installed manually.

D. Disabling SELinux:
Temporarily disabling SELinux is sometimes used as a troubleshooting step but is not required for installation. Proper SELinux configuration is recommended over disabling.

References

Tableau Server on Linux Installation Guide: Creating a dedicated Tableau user account.
Tableau Server Linux Requirements: Service account and group prerequisites. Tableau Server Administrator Guide: Installation steps for Linux.

In preparing for a Tableau deployment in an educational institution, the IT team must evaluate user role distributions among faculty, administrative staff, and students. Which of the following strategies best aligns with this requirement?

A. Provide "Creator" roles to students, "Explorer" roles to faculty, and "Viewer" roles to administrative staff

B. Assign "Creator" roles to administrative staff, "Explorer" roles to students, and "Viewer" roles to faculty

C. Distribute roles based on individual data usage needs and responsibilities within the institution

D. Assign the same "Explorer" role to all users to facilitate uniform access and usage

C.   Distribute roles based on individual data usage needs and responsibilities within the institution

Explanation:

In an educational institution, users across faculty, administrative staff, and students have distinct data needs and responsibilities. Faculty may need to create dashboards for research and teaching (Creator), administrative staff may need to interact with dashboards for reporting (Explorer), and students may primarily need to view published content (Viewer). However, these are general patterns; an individual faculty researcher may need advanced creation capabilities while an administrative user in analytics may also need Creator access. The most effective strategy is to distribute roles based on actual job functions, data interaction requirements, and specific responsibilities rather than applying a blanket role assignment by user category. This approach optimizes licensing costs while ensuring users have appropriate access levels.

Why Other Options Are Incorrect

A. Students as Creators:
This is inefficient for licensing costs as students typically need View access only; assigning Creator roles to all students would be wasteful.

B. Admin staff as Creators:
Not all administrative staff need creation capabilities; many only need to view reports.

D. Same Explorer role for all:
This fails to match varying needs, resulting in either under-licensed users lacking necessary access or over-licensed users wasting capacity.

References
Tableau Licensing Roles: Creator, Explorer, Viewer definitions.
Tableau Server User Management: Role-based access control.
Tableau License Optimization: Matching roles to user needs.

In the context of implementing database encryption for Tableau Server, what factor is important to ensure ongoing data security?

A. Increasing the processing power of the database server to handle the additional load from encryption and decryption processes

B. Ensuring that backup copies of the database are also encrypted

C. Implementing a network monitoring system to track all access to the database server

D. Setting up a redundant database server to take over in case the primary server fails

B.    Ensuring that backup copies of the database are also encrypted

Explanation:

When implementing database encryption for Tableau Server, ensuring that backup copies of the database are also encrypted is critical for maintaining ongoing data security. The Tableau Server repository (PostgreSQL database) stores sensitive metadata, including user information, permissions, and content metadata. While encryption at rest protects the primary database files, unencrypted backups represent a significant vulnerability. If a backup is stolen or accessed without authorization, it could expose sensitive data. Therefore, backup encryption must be part of a comprehensive security strategy, ensuring that all copies of the data remain protected throughout their lifecycle, both in transit and at rest. This aligns with security best practices for data protection and compliance requirements such as GDPR and HIPAA.

Why Other Options Are Incorrect

A. Increasing processing power:
While encryption introduces some performance overhead, the primary security consideration is ensuring all copies of the data are encrypted. Performance tuning should be addressed separately.

C. Network monitoring:
Network monitoring is important for security auditing but does not directly address data-at-rest protection. Backup encryption specifically protects data stored outside the primary database.

D. Redundant database server:
High availability ensures uptime but does not provide data security. Redundancy addresses fault tolerance, not confidentiality or integrity of backed-up data.

References
Tableau Server Encryption: Database and backup encryption.
Tableau Server Security: Backup protection and compliance.
Tableau Server Administrator Guide: Backup and restore with encryption.

When configuring Kerberos authentication for Tableau Server, what step is critical to ensure seam-less single sign-on (SSO) functionality?

A. Installing a third-party SSO software on the Tableau Server

B. Setting up a trust relationship between Tableau Server and the Kerberos Key Distribution Center (KDC)

C. Configuring all Tableau Server users to have administrative privileges

D. Enabling anonymous access on the Tableau Server to facilitate Kerberos ticket exchange

B.   Setting up a trust relationship between Tableau Server and the Kerberos Key Distribution Center (KDC)

Explanation:

For Kerberos authentication to provide seamless Single Sign-On (SSO) functionality, Tableau Server must establish a trust relationship with the Kerberos Key Distribution Center (KDC), typically a domain controller in Active Directory. This trust is established by properly registering Service Principal Names (SPNs) for the Tableau Server service account. The SPNs uniquely identify the Tableau Server service to the KDC, allowing the KDC to issue valid service tickets to authenticated users. When a user attempts to access Tableau Server, their client presents a ticket-granting ticket (TGT) to the KDC, which then issues a service ticket for Tableau Server. The server validates this ticket using its registered SPN and the shared secret (the service account's password hash). Without this trust relationship, the KDC cannot issue valid tickets, and the authentication handshake fails, preventing SSO from functioning.

Why Other Options Are Incorrect

A. Installing third-party SSO software: Kerberos is a native authentication protocol integrated with Active Directory, not a third-party solution. No additional SSO software is required.

C. Configuring all users with administrative privileges:Granting administrative privileges to all users is a severe security risk and has no relevance to Kerberos SSO functionality. SPN registration is the critical step.

D. Enabling anonymous access: Anonymous access bypasses authentication entirely, which defeats the purpose of SSO. Kerberos requires authenticated access, not anonymous.

References
Tableau Server Kerberos Configuration: Trust relationship with KDC.
Tableau Server Authentication: Service Principal Names and SSO.
Microsoft Kerberos Documentation: Trust relationship requirements.

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