Analytics-Admn-201 Exam Preparation Material | Salesforce Certified Tableau Server Administrator

Explanation:
Tableau Server is designed for production environments and is supported only on server-class operating systems, not desktop operating systems. As of the latest documentation (aligned with knowledge up to March 21, 2025), the supported operating systems for Tableau Server on Windows are:
Windows Server 2016
Windows Server 2019
Windows Server 2022 (added in later versions, but relevant as of 2025).
Desktop operating systems like Windows 7 or Windows 10 are not supported for production installations due to stability, security, and performance requirements.
Option A (Windows 7): Incorrect. Windows 7 is a desktop OS and is not supported for Tableau Server.
It’s also end-of-life as of January 2020.
Option B (Windows 10): Incorrect. Windows 10 is a desktop OS and not supported for production Tableau Server deployments, though it may be used for testing in non-production scenarios. Option C (Windows Server 2019): Correct. This is a supported server OS for Tableau Server. Option D (Windows Server 2016): Correct. This is also a supported server OS for Tableau Server.
Reference: Tableau Server Documentation - "System Requirements for Tableau Server" (https://help.tableau.com/current/server/en-us/requirements.htm).

Explanation:
In Tableau Server, projects are containers for organizing and securing content. They help manage permissions and structure content hierarchically. Let’s define what can be contained: Workbooks: Visualizations and dashboards published to the Server.
Data Sources: Published connections or extracts reusable across workbooks.
Nested Projects: Sub-projects within a parent project, introduced in later versions (e.g., 2018.2) for deeper organization.
Option B (Workbooks): Correct. Workbooks are the primary content type in projects, containing views and dashboards.
Option C (Nested Projects): Correct. Nested projects allow hierarchical structuring (e.g., a "Sales" project with "Q1" and "Q2" sub-projects), with inherited or custom permissions.
Option D (Data Sources): Correct. Published data sources reside in projects, providing reusable data connections.
Option A (Groups): Incorrect. Groups are collections of users managed at the site or server level, not stored within projects. Projects contain content, not user entities.
Why This Matters: Projects are key to content governance―knowing what they hold helps administrators organize and secure assets effectively.
Reference: Tableau Server Documentation - "Projects" (https://help.tableau.com/current/server/en-us/projects.htm).

Explanation:
Tableau Server’s installer configures process instances based on hardware and deployment type (single-node vs. multi-node). For a single-node installation with 4 cores, we need to consider the default process topology. Let’s break this down exhaustively:
Key Processes:
Gateway: Handles incoming requests (1 instance).
Application Server (VizPortal): Manages UI and sessions (1 instance).
VizQL Server: Renders visualizations (2 instances).
Backgrounder: Runs extract refreshes, subscriptions (1 instance).
Data Server: Manages data connections (1 instance).
File Store: Stores extracts (1 instance).
Repository: Metadata database (1 instance, active).
Cluster Controller, Cache Server, etc.: Supporting processes (typically 1 each).
Default Configuration:
On a single-node install, Tableau sets 1 instance per process unless specified otherwise, except for VizQL, which defaults to 2.
The installer doesn’t scale instances linearly with cores (e.g., 4 cores ≠ 4 instances). Post-install, TSM can adjust this (e.g., tsm topology set-process), but the question asks for the installed default. Minimum hardware (8 cores, 32 GB RAM) suggests higher defaults, but 4 cores still triggers a minimal setup.
Option B (1): Correct with Caveat.
Most processes (e.g., Backgrounder, Gateway, Data Server) default to 1 instance on install, regardless of 4 cores.
VizQL defaults to 2, but the question’s phrasing ("each process") implies a general rule. Historically (and per docs), 1 is the baseline for most, with VizQL as the exception.
Interpretation: Assuming "each" means the typical case, 1 fits most processes on a 4-core single-node setup.
Option A (2): Incorrect. Only VizQL defaults to 2; others don’t.
Option C (8): Incorrect. Far exceeds defaults―8 cores might justify more, but not 4.
Option D (4): Incorrect. Not tied to core count by default; manual config would be needed.
Why This Matters: Understanding defaults aids capacity planning―4 cores is below production minimum (8), so performance tuning may be needed post-install.
Reference: Tableau Server Documentation - "Server Process Settings"
(https://help.tableau.com/current/server/en-us/processes.htm).

Explanation:
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 <new-username> --password <new-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.
Reference: Tableau Server Documentation - "TSM Reset Command" (https://help.tableau.com/current/server/en-us/cli_reset.htm).

Explanation:
Subscriptions in Tableau Server deliver workbook views to users via email on a schedule. Group subscriptions apply to all group members―let’s unpack this: Group Subscription Mechanics:
Created via Workbooks > Actions > Subscribe > Select Group.
Delivers content to all users in the group at the time the subscription runs (e.g., daily PDF).
Dynamic: Membership updates (additions/removals) are reflected automatically on the next run.
Option C (The subscription updates automatically to include the new user): Correct.
Details: When you add a user to the group (e.g., via Users > Groups > Add Users), Tableau Server’s subscription process queries the group’s current membership at runtime. The new user receives the subscription on the next scheduled delivery―no manual action needed.
Example: Group "Sales" has a 9 AM subscription. Add a user at 8 AM―they get the email tomorrow at 9 AM.
Option A (Admin receives notice to approve/deny): Incorrect.
Why: No approval workflow exists for group membership changes in subscriptions―it’s automatic.
Option B (Creator must manually edit): Incorrect.
Why: Subscriptions are tied to the group, not a static user list―manual edits aren’t required for membership changes.
Option D (Only members at creation time): Incorrect.
Why: This would be true for individual subscriptions (static list), but group subscriptions are dynamic.
Why This Matters: Dynamic group subscriptions streamline content delivery as teams evolve, reducing admin overhead.
Reference: Tableau Server Documentation - "Manage Subscriptions"
(https://help.tableau.com/current/server/en-us/subscribe.htm).