To perform a full server-level restore you must have two artifacts:

1) a .tsbak file created with tsm maintenance backup, which contains all PostgreSQL repository data;

2) an export (.json) created with tsm settings export –f, which captures every server secret (including repository passwords) and all configuration settings.

Topology information is regenerated automatically from the exported configuration and therefore does not need a separate backup.

Hence, the three data categories that must be backed up are Server secrets & repository passwords, Configuration data, and Repository data.

B. Topology data – Re-created when configuration JSON is applied; Tableau docs specify no separate topology backup is required for restore.

1. Tableau Software. “Back up Tableau Server Data.” Server Admin Guide 2023.3, section “Back up data you must have for a restore.”

https://help.tableau.com/current/server/en-us/backups.htm (para. 2–5).

2. Tableau Software. “tsm maintenance backup.” Server Admin Guide 2023.3, section “Creates a .tsbak file of repository data.”

https://help.tableau.com/current/server/en-us/tsmcmd.htm#maintenancebackup (entire page).

3. Tableau Software. “tsm settings export.” Server Admin Guide 2023.3, section “Exports configuration settings and security secrets.”

https://help.tableau.com/current/server/en-us/tsmcmd.htm#settingsexport (para. 1–4).

Tableau Server checks for data-driven alert conditions based on two primary triggers. First, there is a server-wide background process that checks alerts at a configurable frequency. By default, this interval is set to every 60 minutes. Second, for any view that is built upon a data extract, the alert condition is specifically checked immediately after the scheduled refresh for that extract completes. This ensures that alerts are evaluated against the most current data available in the extract. These two mechanisms work together to provide timely notifications when data crosses a specified threshold.

B. Every 10 minutes: This frequency is too high. The default and most frequent server-wide check interval for data-driven alerts is 60 minutes, not 10.

C. Whenever a new extract is published: Publishing a new extract is a one-time setup event. Alert checks are recurring processes tied to scheduled refreshes of existing extracts, not the initial publication.

1. Tableau Server Documentation, "Send Data-Driven Alerts from Tableau Server":

Reference for A: In the section "How data-driven alerts work," the documentation states, "By default, Tableau Server checks every 60 minutes to see if data conditions for alerts are true." This directly supports the 60-minute interval.

Reference for D: In the same section, it clarifies the behavior for extracts: "If the view uses an extract, the alert runs on the extract's refresh schedule." This confirms that extract refreshes are a primary trigger.

2. Tableau Server Documentation, "tsm configuration set Options":

Reference for A & B: The configuration key dataAlerts.checkIntervalInMinutes controls the server-wide check frequency. The documentation specifies its default value is 60. This confirms that 60 minutes is the standard interval and that 10 minutes is not the default.

Tableau Server is a resource-intensive application that requires significant CPU, memory, and I/O resources to function optimally. Running additional software on the same machine, particularly applications like antivirus, backup agents, or other server-grade software, creates resource contention. This competition for system resources can lead to severe performance degradation, instability, and unpredictable behavior for Tableau Server. Official Tableau deployment guidelines strongly recommend installing Tableau Server on a dedicated computer that meets or exceeds the minimum hardware requirements to ensure reliability and performance.

B. Separating the Backgrounder and VizQL processes to different machines: This is a recommended scaling strategy for multi-node deployments to improve performance, not a cause of problems.

C. Configuring the server to use a static IP address: This is a best practice and often a requirement for stable client connections and reliable server operation.

D. Using a non-default installation path: Tableau Server fully supports installation to a non-default directory; this action itself does not cause operational issues.

1. Tableau Server Help, "Before you install...", Section: "General Installation Guidelines for Tableau Server": This official documentation explicitly states, "For best performance, we recommend you install Tableau Server on a dedicated computer... For example, running other applications, such as anti-virus software or other databases, on the same computer as Tableau Server can degrade performance." This directly supports option A as the most likely cause of problems.

2. Tableau Server Help, "Performance Tuning", Section: "General performance guidelines": This section details how Tableau Server processes consume resources and emphasizes avoiding resource contention. It notes, "Contention for resources such as CPU, memory, and I/O can cause slower performance." This reinforces the reasoning behind why running other software is problematic.

3. Tableau Server Help, "Distributed and High Availability Tableau Server Installations", Section: "Example: Two-Node Installation": This documentation provides examples of separating processes like the Backgrounder and VizQL onto different nodes (machines) to balance the server load and improve performance, directly contradicting option B as a problem.

To allow users to post comments on a Tableau visualization, two primary configurations are required. First, the commenting feature must be enabled at the site level within the Tableau Server or Tableau Cloud settings. This acts as a master switch for that specific site. Second, the relevant users or groups must be explicitly granted the "Add Comments" permission capability on the specific workbook or view. Without this permission, even if commenting is enabled for the site, users will not be able to add comments.

A. The relevant users must have a minimum site role of Explorer (can publish)

This is incorrect. Users with a "Viewer" site role can add comments, provided they have the specific "Add Comments" permission. An Explorer role is not the minimum requirement.

C. Comments must be enabled on the server Settings page

While a server-wide setting to enable comments does exist and must be active, the site-level setting is more specific and is the direct control for a particular site's functionality. The question implies configuration for a set of users, which is managed at the site and content level.

1. Tableau Server Help - Manage Site Settings (for option D):

In the "General" tab of the site settings, an administrator can configure commenting. The documentation states, "Allow users to comment on views. When you turn off comments, any existing comments are archived on the server." This confirms the site-level setting is required.

Source: Tableau Server Help, "Manage Site Settings," Section: "General tab settings."

2. Tableau Server Help - Permissions (for option B):

The official documentation on capabilities granted by permissions lists "Add Comments" as a distinct capability. It states, "To see and add comments, users need the View Comments and Add Comments permission capabilities." This confirms that the specific permission must be granted.

Source: Tableau Server Help, "Permissions," Section: "Capabilities granted by permissions."

3. Tableau Server Help - Set Users’ Site Roles (for option A):

The documentation outlines the capabilities for each site role. The "Viewer" role description includes the ability to "Add comments to views." This directly refutes the claim that Explorer (can publish) is the minimum required role.

Source: Tableau Server Help, "Set Users’ Site Roles," Section: "General capabilities for each site role."

By default, Tableau Server is configured to allow data-driven alerts. The server-wide setting dataAlerts.enabled is set to true by default. Furthermore, when a new site is created, the site-level setting "Let users create and receive data-driven alerts" is also enabled by default. Since the scenario specifies that both the Tableau Server installation and the site use default settings, no additional configuration is necessary for users to begin setting up data-driven alerts.

A. This is incorrect because data-driven alerts are enabled by default at the server level in TSM. No action is required on the configuration page.

B. This command configures the frequency at which Tableau Server checks for alert conditions, it does not enable the feature itself. The default interval is already 60 minutes.

C. This is incorrect because the data-driven alerts setting is enabled by default on a new site's Settings page. A change would only be necessary if it were manually disabled.

1. Tableau Server Help - Set Up for Data-Driven Alerts.

Reference: In the section "Enable data-driven alerts (server-wide setting)", the documentation states: "By default, data-driven alerts are enabled."

Reference: In the section "Control data-driven alerts (site-level setting)", it states: "Go to a site's Settings page... Under Data-Driven Alerts, clear or select Let users create and receive data-driven alerts. By default, this option is selected."

Source: Salesforce, Tableau Server Help for Administrators. (This information is consistent across recent versions of Tableau Server documentation).

2. Tableau Server Help - tsm configuration set Options.

Reference: The documentation for the key dataAlerts.enabled specifies its default value is true.

Reference: The documentation for the key dataAlerts.checkIntervalInMinutes specifies its default value is 60. This confirms that option B does not change the default behavior and is not an enabling step.

Source: Salesforce, Tableau Server Help for Administrators.