Salesforce Analytics-Admn-201 Exam Dumps

In Tableau Server, projects organize content (workbooks, data sources) and use permissions to control access. 'Locking permissions' restricts how permissions are managed within a project---let's explore this exhaustively:

Permission Management Modes:

Managed by Owner: Default mode. Content owners (e.g., workbook publishers) can set permissions on their items, inheriting project defaults as a starting point.

Locked to the Project: Project-level permissions are enforced, and content owners cannot modify them. This ensures consistency across all items in the project.

How to Lock:

In the Tableau Server web UI:

Go to Content > Projects.

Select a project, click Actions > Permissions.

In the Permissions dialog, change Permissions Management from 'Customizable' (Managed by Owner) to 'Locked.'

Set the desired permissions (e.g., Viewer, Editor) for users/groups, which then apply uniformly to all content.

Via REST API: Use the updateProject endpoint with 'permissionsLocked': true.

Option B (You can lock permissions to a project by changing Customizable to Locked): Correct.

Details: This is the precise action in the UI---switching from 'Customizable' to 'Locked' locks permissions at the project level.

Impact: Owners lose the ability to override permissions on individual workbooks/data sources, enforcing governance.

Example: Set 'All Users' to Viewer (Locked)---all content in the project is view-only, regardless of owner intent.

Option A (Locking permissions must be enabled on the Server Settings page): Incorrect.

Why: Locking is a per-project setting, not a server-wide toggle. The Server Settings page (via TSM) controls global configs (e.g., authentication), not project permissions.

Option C (Content permissions are locked by default): Incorrect.

Default: New projects are 'Managed by Owner' (Customizable), allowing flexibility unless explicitly locked by an admin.

Option D (By setting the appropriate Project permission role): Incorrect.

Confusion: 'Project permission role' isn't a term---permissions are set via rules (e.g., Viewer, Editor), but locking is a separate action (Customizable Locked).

Why This Matters: Locking permissions ensures uniform access control, critical for regulated environments or large teams where consistency trumps flexibility.

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 <filename>.tsbak (e.g., tsm maintenance backup -f backup.tsbak)---incomplete without it.

Option B (tsm maintenance restore): Incorrect.

Why: Needs -f <filename>.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.

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.

Tableau Server consists of multiple processes managed by TSM. When you stop Tableau Server (e.g., via tsm stop), most application processes halt, but some TSM-specific processes remain active to manage the server's infrastructure. Let's examine each:

TSM Processes: These include the Administration Controller, Administration Agent, and License Manager, which handle configuration, monitoring, and licensing.

Application Processes: These include VizQL Server, Backgrounder, Data Server, etc., which deliver Tableau's core functionality and stop when the server is stopped.

When tsm stop is executed:

The Administration Controller (port 8850) continues running to manage TSM operations (e.g., restarts, status checks).

The License Manager remains active to validate licenses and ensure compliance, even when the server is offline.

Application processes like VizQL Server and Backgrounder shut down, as they're tied to user-facing services.

Option B (License Manager): Correct. It persists to handle licensing tasks, ensuring the server can restart without license issues.

Option D (Administration Controller): Correct. It's the core TSM process, always running to accept commands and manage the server state.

Option A (VizQL Server): Incorrect. VizQL stops, as it renders visualizations for users---an application process tied to active server operation.

Option C (Backgrounder): Incorrect. Backgrounder stops, as it processes background tasks (e.g., extract refreshes), which halt when the server is down.

Why This Matters: Understanding which processes persist helps administrators troubleshoot and manage server lifecycle events effectively.

Tableau Services Manager (TSM) is the administrative tool for managing Tableau Server's configuration, processes, and topology. To log in to TSM (via the web UI at https://<server>:8850 or CLI), you need:

TSM administrator credentials: These are distinct from site roles and are set during installation or reset via tsm reset.

Local administrative rights: On Windows, the account used to access TSM must be in the local Administrators group on the initial node, as TSM interacts with system-level services.

In a test cluster, the engineer's inability to log in suggests they lack either the correct TSM credentials or sufficient OS-level permissions. Since the question focuses on a Windows environment and ''initial node,'' the most immediate requirement is local administrative rights to run TSM commands or access the UI.

Option C (An account with administrative rights to the computer): Correct. The engineer must use an account in the local Administrators group on the initial node to authenticate to TSM. After that, they'll need the TSM admin username/password set during installation.

Option A (An account with a Creator site role): Incorrect. Site roles (e.g., Creator) apply to content access within Tableau Server, not TSM administration.

Option B (An account with a Site Administrator role): Incorrect. Site Administrators manage site content, not server-level TSM functions.

Option D (An account for the Tableau Server administrator): Partially correct but incomplete. This likely refers to the TSM admin account, but without local admin rights on the machine, login will fail. Option C is more precise.