SCA-C01 Exam Dumps : Tableau Server Certified Associate Exam

TSM commands manage Tableau Server maintenance—let’s validate their syntax:

Command Requirements:

Some need arguments (e.g., file paths); others are standalone.

Valid and Complete: Must work as-is without errors.

Option C (tsm maintenance cleanup): Correct.

Details: Removes temporary files and old logs—no arguments required (optional flags like -l exist).

Use: tsm maintenance cleanup—runs fully.

Option D (tsm maintenance ziplogs): Correct.

Details: Creates a zip of logs (e.g., tsm-logs.zip)—no arguments needed (optional -d for date range).

Use: tsm maintenance ziplogs—complete and valid.

Option A (tsm maintenance backup): Incorrect.

Why: Requires -f .tsbak (e.g., tsm maintenance backup -f backup.tsbak)—incomplete without it.

Option B (tsm maintenance restore): Incorrect.

Why: Needs -f .tsbak (e.g., tsm maintenance restore -f backup.tsbak)—not standalone.

Why This Matters: Correct syntax ensures maintenance tasks execute without errors—critical for server health.

TSM is Tableau Server’s management layer, accessible via CLI or web UI (port 8850). HTTPS secures this access—let’s identify the responsible process:

TSM Architecture:

Administration Controller: Core TSM process, running on the initial node, handling configuration, UI, and CLI commands.

HTTPS: Enabled by default on port 8850 with a self-signed certificate (configurable to custom certs).

Option B (Administration Controller): Correct.

Details: Hosts the TSM web UI :8850) and processes CLI requests. It manages the HTTPS listener, serving the interface securely.

Why: It’s the central hub for TSM operations, including secure access.

Option A (License Manager): Incorrect.

Why: Validates licenses, not responsible for HTTPS or UI access.

Option C (Administration Agent): Incorrect.

Why: Runs on additional nodes in multi-node setups to relay commands to the Controller—no direct HTTPS role.

Option D (Coordination Service): Incorrect.

Why: ZooKeeper manages cluster state, not TSM’s web interface or HTTPS.

Why This Matters: Secure TSM access protects server administration—Administration Controller is the linchpin.

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.