Explanation:

Single Sign-On (SSO) allows users to access Tableau Server without re-entering credentials after logging into a central identity provider. Tableau Server supports several industry-standard protocols to integrate with enterprise authentication systems, enabling a seamless and secure login experience. Local authentication is explicitly not an SSO method.

✅ Correct Options:

A. OpenID Connect
OpenID Connect (OIDC) is a modern, standards-based authentication layer built on OAuth 2.0. It allows Tableau Server to delegate authentication to external identity providers like Azure AD, Okta, or Ping Identity. Upon successful login with the provider, a token is passed to Tableau, granting access without a separate password, making it a primary method for cloud and modern SSO.

C. Kerberos with Active Directory
Kerberos is a ticket-based network authentication protocol integrated with Active Directory. When configured for Tableau Server, it enables "true" silent SSO for domain-joined machines. The user's Windows login ticket is automatically passed to Tableau, granting access without any prompt for a username or password, providing a seamless desktop-like experience.

D. Security Assertion Markup Language (SAML)
SAML is an open standard and one of the most widely used protocols for enterprise SSO. It allows an identity provider (like Okta or ADFS) to pass authentication credentials and user data to Tableau Server (the service provider). Users logging into their company portal can click a Tableau tile and be automatically signed in, making SAML a cornerstone of web-based SSO.

❌ Incorrect Option:

B. Local Authentication
Local authentication is the default method where Tableau Server itself stores and manages usernames and passwords in its internal repository. This is the direct opposite of SSO, as it requires users to maintain a separate, Tableau-specific password and enter it manually upon each login. It does not integrate with or delegate to an external identity provider.

📚 Reference:
Tableau Help Documentation: "Ways to Sign In" - This official page lists the supported authentication methods, explicitly naming SAML, OpenID Connect, and Trusted Authentication (which often uses Kerberos) as methods that enable single sign-on, while clearly differentiating them from local authentication.

Explanation:

This question examines your understanding of Tableau Server's backup strategy and the critical data components needed for complete disaster recovery. A comprehensive backup approach ensures you can fully restore server functionality, user content, permissions, and configurations after system failures. Knowing what to backup is fundamental to maintaining business continuity and data integrity in production environments.

✅ Correct Options:

Option A: Server secrets and Repository passwords 🔐
Server secrets and repository passwords contain critical encryption keys and authentication credentials that protect sensitive data. These elements include:

✔️ Master keystore file containing encryption keys
✔️ Repository database passwords
✔️ SSL certificate passphrases
✔️ Internal service authentication tokens

Without backing up these secrets, you cannot decrypt the repository backup or restore server security configurations. The secrets are stored separately from regular backups and must be explicitly exported using tsm settings export command before system failures occur.

Option C: Configuration data ⚙️
Configuration data encompasses all server settings, customizations, and deployment specifications necessary to recreate your Tableau Server environment. This includes:

✔️ Server topology and process configurations
✔️ Authentication settings (SAML, Active Directory, etc.)
✔️ Site configurations and storage quotas
✔️ Gateway settings and port configurations
✔️ Scheduling and subscription settings

Configuration backups are created using tsm settings export and contain the blueprint for rebuilding your server infrastructure with identical settings after restoration.

Option D: Repository data 📊
The repository database is the heart of Tableau Server, containing all metadata, user content, and operational data. Key components include:

✔️ Published workbooks, data sources, and flows
✔️ User accounts, groups, and permissions
✔️ Projects, schedules, and subscriptions
✔️ Historical metrics and audit logs
✔️ Extract metadata and refresh schedules

Repository backups are created using tsm maintenance backup command and are essential for recovering all user-generated content and system metadata after failures.

❌ Incorrect Option:

Option B: Topology data 🚫
Topology data is NOT separately backed up because it's already included within the configuration data (Option C). Topology information defines how Tableau Server processes are distributed across nodes, but this is captured automatically when you backup configurations using tsm settings export. The topology and configuration are interrelated—your configuration backup contains topology details like which processes run on which nodes, resource allocations, and clustering setup. Attempting to backup topology separately would be redundant and isn't a distinct backup category in Tableau Server's backup procedures. When restoring, you apply the configuration file which inherently restores the topology structure.

Reference:
Official Tableau Documentation: Back up Tableau Server Data

Explanation:

When publishing a visualization from Tableau Desktop 10.5 to Tableau Server 2020.1, the key consideration is the compatibility between the versions and the extract format. Starting with Tableau 10.5, extracts use the .tde (Tableau Data Extract) format. In Tableau Server 2018.2 and later, including 2020.1, the default extract format is .hyper, which replaced .tde for improved performance.

Explanation:

Question Analysis:
📊 This question tests your knowledge of Tableau Server's hardware requirements for production environments. Understanding minimum disk space requirements is crucial for successful server deployment and ensuring adequate storage for application files, logs, temporary files, and data caching. Production environments require more space than development environments due to higher usage and data volumes.

✅ Correct Option: B. 50 GB

💡 Why This Is Correct:
Tableau Server requires a minimum of 50 GB of free hard disk space for production installations. This space allocation accounts for:
🔹 Core application binaries and system files
🔹 Repository database storage
🔹 Extract files and cached data
🔹 Log files and temporary processing space
🔹 Future growth and system updates
The 50 GB minimum ensures the server operates smoothly without running into disk space issues that could cause performance degradation or service interruptions during peak usage periods.

❌ Incorrect Options:

Option A: 32 GB 🚫
While 32 GB might seem sufficient, it falls short of Tableau's official production requirements. This amount could lead to disk space exhaustion quickly in production environments where multiple users publish workbooks, extracts accumulate, and log files grow. Insufficient disk space can cause extract refresh failures, slow performance, and potential system crashes during high-demand periods.

Option C: 15 GB 🚫
15 GB is the minimum requirement for non-production environments (development/test), not production. Using this minimal allocation in production would be risky and inadequate. Production servers handle more concurrent users, larger datasets, more published content, and generate significantly more logs. Operating with only 15 GB would result in frequent disk space alerts and operational issues.

Option D: 64 GB 🚫
Although 64 GB provides more buffer space and is actually recommended for optimal performance, it exceeds the stated minimum requirement. The question specifically asks for the minimum, not the recommended or ideal amount. While having extra space is beneficial, 64 GB is not the official minimum threshold that Tableau specifies for production installations.

📚 Reference:
Official Tableau Documentation: Tableau Server Hardware

Explanation:

Data-driven alerts in Tableau Server allow users to receive notifications when data in a visualization meets specific conditions. By default, a new Tableau Server installation and site may not have data-driven alerts enabled for user access. This question tests your knowledge of enabling this feature for a specific site, focusing on the correct configuration steps to allow users to create and manage these alerts effectively.

Correct Option:

✅ C. Change the data-driven alerts setting on the new site's Settings page
To enable data-driven alerts, administrators must navigate to the site’s Settings page in Tableau Server and explicitly enable the “Allow users to create and manage data-driven alerts” option. This setting is disabled by default for new sites, so enabling it ensures users can set up alerts for their visualizations. This is done per site, making it the precise action needed.

Incorrect Options:

❌ A. Enable data-driven alerts on the Tableau Services Manager Configuration page
The Tableau Services Manager (TSM) Configuration page manages server-wide settings, like topology or authentication, but does not control site-specific features like data-driven alerts. This option is incorrect because data-driven alerts are configured at the site level, not through TSM, which is more for server infrastructure settings.

❌ B. Run the tsm configuration set -k dataAlerts.checkIntervalInMinutes -v 60 command
This TSM command adjusts the frequency (in minutes) at which Tableau Server checks for data-driven alert conditions. While it fine-tunes alert behavior, it doesn’t enable the feature itself. Users still can’t create alerts unless the site’s Settings page enables them, making this option irrelevant for enabling user access.

❌ D. No action is necessary: the default settings enable data-driven alerts for the site
By default, data-driven alerts are disabled for new sites in Tableau Server. Assuming no action is needed is incorrect, as administrators must explicitly enable this feature on the site’s Settings page to allow users to create alerts. This option misleads by suggesting default settings are sufficient.

Reference:
Tableau Server Help: Enable Data-Driven Alerts for a Site
Tableau Server Help: Manage Site Settings