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.

Tableau Server’s user-based licensing model assigns licenses to individual users (Creator, Explorer, Viewer) rather than machines or cores. Key features include:

Subscription license: Licenses are typically subscription-based, renewed annually or monthly, aligning with Tableau’s pricing model.

Distinct user roles: It supports three roles (Creator, Explorer, Viewer), each with specific capabilities, enabling granular access control.

Option A (A subscription license): Correct. User-based licenses are subscription-based by default.

Option B (Enables distinct user roles): Correct. The model defines Creator, Explorer, and Viewer roles.

Option C (Restricts the number of machine cores): Incorrect. This applies to core-based licensing, not user-based.

Option D (A perpetual license): Incorrect. Perpetual licenses were phased out; user-based licenses are subscription-based as of recent models.

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.