Explanation:

To manually record performance metrics for a specific workbook view when site-wide recording is enabled, you must append a specific parameter to its URL. This action triggers a detailed performance capture for that single viewing session, which is then available for analysis in the Tableau Server Performance recording section. The key is placing the parameter correctly within the existing URL structure.

✅ Correct Option:

B. Type :record_performance=yes& at the end of the view URL, immediately after the session ID
🔹 This is the precise method prescribed by Tableau for on-demand performance recording. The parameter record_performance=yes is the command that initiates the capture.
🔹 It must be placed after the session ID (which typically looks like :iid=... or :session_id=...) but before any other URL parameters. Using the colon (:) and ampersand (&) ensures it is properly appended as a new URL parameter.
🔹 Once added and the page is reloaded, Tableau Server will record a detailed performance event for that specific workbook load, which administrators can then analyze.

❌ Incorrect Options:

A. Click the Performance link in the toolbar at the top of the view
This option is incorrect because there is no "Performance link" in the toolbar for a standard user viewing a workbook. Performance recording is either a background site setting or requires the manual URL parameter modification described in the correct answer.

C. Type :record_performance=yes& at the end of the view URL, immediately before the session ID
Placing the parameter before the session ID will break the URL and likely cause an error or prevent the view from loading correctly. The URL syntax is specific, and parameters must be appended in the correct sequence to function.

D. Delete the session ID in the URL and reload the view
Deleting the session ID will invalidate the current viewing session. This will either force a new login or generate an error, but it will not trigger a performance recording. The session ID is a crucial part of the URL for maintaining your connection to Tableau Server.

📚 Reference:
Tableau Help Documentation: "Record Performance Metrics" - This document explicitly states: "To record performance for a specific view, add the parameter :record_performance=yes to the end of the view URL, after the session ID, and then press Enter."

Explanation:

The Coordination Service is a critical component for high-availability clusters that manages synchronization and consensus between nodes. Checking its status is a fundamental administrative task.

Why C is Correct: The tsm status -v command is the primary CLI tool for checking the detailed status of all Tableau Server processes, including the underlying infrastructure services. The -v flag stands for "verbose," and it provides extended information that includes the status of the Coordination Service ensemble (ZooKeeper), the file service, and the client file service. This command will clearly show if the ensemble is healthy and which nodes are active members.

Why A is Incorrect: The TSM web client Status page (accessed via https://:8850) provides a high-level overview of the service status (e.g., "Active," "Degraded") and the status of core Tableau processes (VizQL, Backgrounder, etc.). However, it does not provide a detailed, verbose status of the underlying Coordination Service ensemble.

Why B is Incorrect: The tsm maintenance ziplogs command is used to collect log files for troubleshooting. It does not display the current operational status of any service; it merely packages existing log data.

Why D is Incorrect: The Tableau Server Status page (typically accessed by users at https:///#/site//status) shows the status of server content and connectivity from a user's perspective (e.g., is a data source refresh failing?). It does not show the status of the backend infrastructure like the Coordination Service.

Reference:
Tableau Help: tsm status - The documentation notes that the -v option "returns additional status information for the Coordination Service, File Service, and Client File Service." This is the definitive command for this task.

Explanation:

Tableau Server's caching mechanism is designed to balance performance with data freshness. By default, it will recompute queries and refresh the cache for a workbook only when certain conditions are met to avoid unnecessary load on the server.

The workbook has upcoming scheduled refresh tasks (B): This is the trigger. Tableau Server knows that the underlying data for the workbook is being updated, so it needs to prepare new, fresh data for a user to view.

The workbook has been viewed recently (D): Tableau Server is smart about managing resources. It will only "warm the cache" for workbooks that users are actually interacting with. The definition of "recently viewed" is a configurable threshold (backgrounder.externalquerycachewarmup.view_threshold). If a workbook hasn't been viewed in a while, Tableau Server won't spend resources on re-computing the cache because it's unlikely a user will access it soon.

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:

The Administration Controller manages the Tableau Services Manager (TSM) web interface, enabling secure access over HTTPS (e.g., at https://:8850). It handles TSM operations and SSL configuration for secure communication.

Why not others?
A. License Manager: Manages licenses, not HTTPS access.
C. Administration Agent: Executes TSM commands on nodes, doesn’t handle HTTPS.
D. Coordination Service: Ensures node consistency, not related to TSM HTTPS access.

Reference:
Tableau Help: Configure SSL for TSM