True or False: If the server is configured to use Active Directory for authentication, user passwords are managd by Active Directory, so you can leave the password field in the CSV file blank when importing the users.
Correct Answer: B
Explanation Link to Tableau Server documentation: https://help.tableau.com/current/server/en-us/users_import.htm
Question 2
Which of the following statements correctly describe the concept of project leaders and project owners as it relates to project ownership?
Correct Answer: A
Explanation Link to Tableau Server documentation: https://help.tableau.com/current/server/en-us/permissions_projects.htm#projectpermissions
Question 3
Which three types of data should you backup to ensure that you can restore a Tableau Server? (Choose three.)
Correct Answer: A,C,D
Backing up Tableau Server ensures recovery from failures or migrations. A full backup includes multiple data types-let's dissect this comprehensively: * Backup Components: * Repository Data: PostgreSQL database with metadata (users, permissions, workbooks). Backed up via tsm maintenance backup -f <filename>.tsbak. * Configuration Data: Server settings (e.g., ports, authentication) also in the .tsbak file. * Server Secrets: Encryption keys, internal tokens, Repository passwords-critical for restoring functionality. * Extracts: .hyper files in File Store (optional, separate backup). * Option A (Server secrets and Repository passwords): Correct. * Details: Includes encryption keys (for extracts), internal tokens (process communication), and Repository credentials. Backed up separately or stored securely (e.g., tsm security export-keys). * Why Critical: Without these, restored data may be inaccessible or services may fail. * Option C (Configuration data): Correct. * Details: Ports, authentication settings, process topology-part of the .tsbak file. * Why Critical: Restores server behavior and connectivity post-recovery. * Option D (Repository data): Correct. * Details: Core metadata database-also in .tsbak. * Why Critical: Without it, all content and user data is lost. * Option B (Topology data): Incorrect. * Details: Topology (process distribution) is part of configuration data in the .tsbak, not a separate entity. It's not distinctly backed up as "topology data." Why This Matters: A complete backup (secrets, config, repository) ensures full restoration-missing any piece risks an unusable server.
Question 4
Which of the following IS NOT a recommended course of action when investigating Tableau Server issues with respect to log files?
Correct Answer: D
Explanation Link to Tableau Server documentation: https://help.tableau.com/current/server/en-us/logs_working_with.htm
Question 5
What process decides when a Repository failover is required?
Correct Answer: A
In a high-availability (HA) Tableau Server setup, theRepository(PostgreSQL) has an active and passive instance. Failover occurs if the active Repository fails. Let's dive into the process: * HA Setup: * Two Repository instances across nodes (active/passive). * Failover switches to the passive instance if the active one becomes unavailable (e.g., crash, network issue). * Cluster Controller: * Role: Monitors all processes (e.g., Repository, File Store) across nodes, detecting failures via heartbeats and status checks. * Failover Decision: If the active Repository stops responding, Cluster Controller initiates failover, promoting the passive instance to active. * Coordination: Works with Coordination Service (ZooKeeper) to update topology but makes the initial detection call. * Option A (Cluster Controller): Correct. * Why: It's the watchdog process, constantly monitoring Repository health and triggering failover when needed. * Option B (Coordination Service): Incorrect. * Role: ZooKeeper maintains cluster state and coordinates topology updates post-failover, but doesn't detect the failure-Cluster Controller does. * Option C (Gateway): Incorrect. * Role: Routes client requests-unrelated to internal process monitoring or failover. * Option D (Backgrounder): Incorrect. * Role: Executes background tasks-no involvement in Repository failover decisions. Why This Matters: Understanding failover ensures HA reliability-Cluster Controller is the linchpin for resilience.
