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

An enterprise is merging its multiple Tableau sites into a single server for better management and efficiency. What should be the primary focus during this migration?

A. Rapidly migrating all sites without a detailed review to accelerate the process

B. Ensuring the compatibility and proper configuration of data connections across the merged sites

C. Transferring only the most used dashboards and reports, disregarding less frequently used content

D. Maintaining multiple backup servers in case the consolidation fails

B.   Ensuring the compatibility and proper configuration of data connections across the merged sites

✅ Explanation:

When merging multiple Tableau sites into a single server, the primary focus during the migration should be ensuring the compatibility and proper configuration of data connections across the merged sites. This is the most critical success factor because

Why other options are incorrect:

A. Rapidly migrating all sites without a detailed review to accelerate the process:
This is a high-risk approach that often leads to critical failures. Rushing the migration without proper review can result in broken data connections, incorrect permissions, missing content, and prolonged downtime. A "move fast and break things" mentality is not appropriate for a production data platform, as users rely on Tableau for business-critical reporting and decision-making.

C. Transferring only the most used dashboards and reports, disregarding less frequently used content:
This is a poor practice that defeats the purpose of consolidation. The goal of merging sites is to unify all content, not to discard data that may be needed later. Less frequently used content may still be business-critical for certain departments or seasonal reports. Additionally, content owners may need historical reports for audits, compliance, or trend analysis. Archiving or discarding content without business owner approval would be a governance failure.

D. Maintaining multiple backup servers in case the consolidation fails:
While having a rollback plan is a good risk mitigation practice, maintaining multiple backup servers is not the primary focus. This option treats failure as an expectation rather than planning for success. The primary effort should be on ensuring the migration works correctly, not on preparing multiple fallback systems—which would be costly and resource-intensive. A single reliable backup or rollback plan is sufficient.

🔗 References:

Tableau Server Migration Best Practices (Salesforce/Tabular Documentation): Emphasizes that thorough testing of data connections is critical before any site consolidation. The documentation recommends mapping all data sources, validating connection strings, and testing connectivity from the target environment.

When creating a custom administrative view in Tableau to analyze user activity, which table in the Tableau repository should you focus on to understand user login patterns?

A. The 'datasources' table to monitor the data sources each user accesses

B. The 'workbooks' table to see which workbooks are most frequently used by users

C. The 'historical_events' table to analyze specific events like user logins and logouts

D. The 'sites' table to determine which sites users are accessing most frequently

C.   The 'historical_events' table to analyze specific events like user logins and logouts

✅ Explanation:

When creating a custom administrative view in Tableau to analyze user login patterns, you should focus on the historical_events table in the Tableau repository. This is the correct table because it directly captures and stores records of specific user events, including logins, logouts, and other authentication-related activities.

Why other options are incorrect:

A. The 'datasources' table to monitor the data sources each user accesses:
This table contains metadata about data source connections (e.g., database server names, connection types). While useful for understanding data architecture and usage, it does not capture user login events or authentication patterns. It tracks data-related information, not user activity sessions.

B. The 'workbooks' table to see which workbooks are most frequently used by users:
This table stores metadata about workbooks, such as names, owner IDs, creation dates, and paths. It does not track who logs in or when. While it is useful for analyzing content popularity, it is not the source for login pattern analysis. To measure workbook usage, you would typically use the historical_events table or the usage_stats table, which record view events.

D. The 'sites' table to determine which sites users are accessing most frequently:
This table contains metadata about sites (e.g., site names, URL namespaces, site states, and creation dates). It does not log user login activity. While it can help understand site configurations and user assignments, it does not provide the time-series login data needed to analyze user login patterns.

🔗 References
Tableau Server Administrative Repository Documentation: Identifies the historical_events table as the primary source for audit-level event tracking, including user logins, logouts, and authentication failures.

After reviewing observability data, you find that Tableau Server’s data extract refreshes are significantly impacting performance during business hours. What architectural change should be made to address this issue?

A. Moving all data extracts to live connections to avoid refreshes

B. Scheduling extract refreshes during off-peak hours to minimize impact on performance

C. Completely disabling extract refreshes to enhance server performance

D. Upgrading the server's CPU to speed up extract refreshes

B.    Scheduling extract refreshes during off-peak hours to minimize impact on performance

✅ Explanation:

When data extract refreshes are significantly impacting Tableau Server performance during business hours, the most appropriate architectural change is to schedule extract refreshes during off-peak hours. This is a fundamental performance optimization strategy that aligns resource-intensive workloads with periods of low user activity.

Why other options are incorrect:

A. Moving all data extracts to live connections to avoid refreshes:
This is an overcorrection that introduces significant performance trade-offs. Live connections place real-time query loads directly on source databases, which can degrade source system performance and increase latency. It also eliminates the performance benefits of extracts, such as faster dashboard rendering and offline availability. This approach is typically used only when real-time data is absolutely required, not as a primary performance optimization strategy.

C. Completely disabling extract refreshes to enhance server performance:
This is not a viable solution. Disabling refreshes would result in stale data, rendering dashboards and reports obsolete. Users would lose confidence in the data, and business decisions would be based on outdated information. The goal should be to balance performance with data freshness, not to sacrifice one completely for the other.

D. Upgrading the server's CPU to speed up extract refreshes:
While upgrading CPU can improve processing speed, it does not address the underlying issue of resource contention during business hours. Without changing the refresh schedule, the same performance impact would occur—just potentially for a shorter duration. Hardware upgrades are a reactive, costly solution that should be considered only after architectural and scheduling optimizations have been exhausted.

🔗 References

Tableau Server Performance Tuning Guide: Recommends scheduling extract refreshes during off-peak hours to minimize the impact on server performance. The guide also suggests using incremental refreshes and optimizing extract filters to reduce resource consumption.

During the installation of Tableau Server on a Linux system, you encounter a failure with the error message indicating a permissions issue. What is the first step you should take to resolve this issue?

A. Reinstalling the Linux operating system to ensure a clean environment for Tableau Server

B. Checking and modifying the file and directory permissions where Tableau Server is being installed

C. Increasing the RAM and CPU resources allocated to the Linux server

D. Configuring the Linux server to use a different file system

B.   Checking and modifying the file and directory permissions where Tableau Server is being installed

✅ Explanation:

When installing Tableau Server on a Linux system, a permissions error indicates that the user account running the installation does not have the necessary read, write, or execute permissions on the target installation directories, temporary folders, or system configuration files. The first step in resolving this issue is to check and modify the file and directory permissions where Tableau Server is being installed.

Why other options are incorrect:

A. Reinstalling the Linux operating system to ensure a clean environment for Tableau Server:
This is an extreme and unnecessary overreaction. Reinstalling the OS would be time-consuming, disruptive, and does not directly address the permissions issue. A fresh OS installation would still require proper permission configuration, making this a highly inefficient and inappropriate first step.

C. Increasing the RAM and CPU resources allocated to the Linux server:
Resource allocation (memory and CPU) does not cause or resolve permissions errors. Permissions failures are related to user access rights and file ownership, not system performance. Increasing RAM and CPU would have no effect on the file system permissions error.

D. Configuring the Linux server to use a different file system:
Changing the file system (e.g., from ext4 to XFS) is a major infrastructure change that does not address the immediate permissions problem. The error is not related to the file system type; it is related to the permissions set on the directories where the installation is occurring. This option does not resolve the specific issue reported.

🔗 References

Tableau Server Installation Guide (Linux): Requires that the installation user have appropriate permissions to write to the installation directory and that the user is a member of the necessary groups (e.g., sudo or root access may be required for certain operations). The guide explicitly lists "permission denied" errors as a common installation issue and recommends checking directory ownership and permissions.

A large enterprise with a global presence is looking to enhance its Tableau Server deployment to support advanced analytics and machine learning capabilities. Which Tableau Server Add-On should be recommended to meet this requirement?

A. Tableau Bridge to provide better connectivity with external data sources

B. Tableau Catalog for improved data management and governance

C. Tableau Data Management Add-On to enhance data preparation and cataloging

D. Tableau Server Management Add-On to leverage advanced analytics and machine learning capabilities

D.   Tableau Server Management Add-On to leverage advanced analytics and machine learning capabilities

Explanation:

The Tableau Server Management Add-On is specifically designed to provide advanced analytics and machine learning capabilities for Tableau Server deployments. It includes the Resource Monitoring Tool (RMT), which leverages machine learning models to analyze historical performance data, predict resource usage trends, and detect anomalies such as CPU spikes or memory contention before they impact users. This proactive approach enables administrators to optimize server performance, automate issue detection, and minimize downtime. The add-on also includes features like configuration backup and migration tools, which further enhance server manageability and reduce administrative overhead. For a large enterprise with global operations, this add-on is essential for maintaining optimal performance across distributed teams and diverse workloads, enabling IT teams to stay ahead of performance issues through predictive insights and automated alerts.

Why Other Options Are Incorrect

A. Tableau Bridge:
Tableau Bridge enables live connections to on-premises data sources for Tableau Cloud users. It is a connectivity tool and does not provide any analytics, machine learning, or server management capabilities. It addresses a completely different use case.

B. Tableau Catalog:
Tableau Catalog is part of the Data Management Add-On and focuses on data governance, lineage tracking, and impact analysis. While valuable for data discovery, it does not include machine learning capabilities for server management.

C. Tableau Data Management Add-On:
This add-on provides data preparation (Prep Conductor) and cataloging capabilities but does not include machine learning or advanced analytics for server optimization. Its focus is on data quality and preparation.

References
Tableau Server Management Add-On: Advanced analytics and ML capabilities.
Tableau Resource Monitoring Tool: Predictive analytics and proactive alerts.
Tableau Server Add-Ons Overview: Features and use cases.

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