Tableau SCA-C01 Exam With Confidence Using Practice Dumps

Tableau Server can record performance metrics for workbooks to troubleshoot slow-loading views. This feature must be enabled at the site level (viaSettings > General > Allow Performance Recording). Once enabled, you can trigger recording for a specific view by modifying its URL.

The correct syntax is to append :record_performance=yes& to the view URL, immediatelyafter the session ID. For example:

Original URL:

Modified URL: &

After loading the view with this parameter, a performance recording is generated and accessible via thePerformanceoption in the toolbar.

Option B (Type :record_performance=yes& at the end of the view URL, immediately after the session ID): Correct. This follows Tableau’s documented method for enabling performance recording.

Option A (Click the Performance link in the toolbar): Incorrect. The Performance link appears only after recording is triggered via the URL; it’s not the method to enable it.

Option C (Type :record_performance=yes& immediately before the session ID): Incorrect. The parameter must follow the session ID (e.g., :iid=1) to function correctly.

Option D (Delete the session ID in the URL and reload the view): Incorrect. The session ID is required for the view to load properly; removing it breaks the URL.

Data-driven alerts notify users when data meets conditions (e.g., sales > $10K). Let’s examine when Tableau checks these:

Alert Mechanics:

Enabled per site (Settings > General > Data-Driven Alerts).

Backgrounder evaluates conditions against extract data.

Check Intervals: Configurable via tsm configuration set -k dataAlerts.checkIntervalInMinutes (default: 60 minutes).

Refresh Trigger: Also checks post-extract refresh for immediate updates.

Option A (Every 60 minutes): Correct.

Details: Default interval—Backgrounder polls every hour to evaluate alert conditions.

Config: Adjustable (e.g., -v 30 for 30 minutes).

Option D (Whenever extracts in the related workbook are refreshed): Correct.

Details: An extract refresh updates the data, triggering an immediate alert check to catch changes promptly.

Why: Ensures timely notifications without waiting for the next poll.

Option B (Every 10 minutes): Incorrect.

Why: Not the default—possible via config, but not standard.

Option C (Whenever a new extract is published): Incorrect.

Why: Publishing creates the extract; alerts trigger on refreshes or polling, not initial publication.

Why This Matters: Timing affects alert responsiveness—balancing frequency and server load is key.

To force Tableau Server to require the setup of a new administrator account (e.g., resetting the server to an initial setup state), the tsm reset command is the appropriate tool. This command resets Tableau Server’s administrative configuration, including the TSM administrator account, while preserving content like workbooks and data sources.

Option B (Run the tsm reset command): Correct. Running tsm reset clears the current TSM administrator credentials and configuration settings. The next time you access TSM (e.g., via the web interface or CLI), it prompts you to set up a new administrator account, mimicking the initial setup process. Command: tsm reset --username --password .

Option A (Edit tabsvc.yml): Incorrect. The tabsvc.yml file contains service configuration data, but manually editing it is not supported or recommended for resetting the administrator account. It could also corrupt the installation.

Option C (Run the tsm register command): Incorrect. The tsm register command is used to register Tableau Server with a new product key or identity store, not to reset the administrator account.

Option D (Reinstall Tableau Server): Incorrect. Reinstallation wipes the entire server, including content, and is overkill for this task. The tsm reset command achieves the goal without data loss.