Key details for this exam, checked against the published exam outline
Each question shows the correct answer and an explanation of why it is right
Which three items can be contained in a project? (Choose three.)
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.
What two types of users can sign in to Tableau Server and edit the permissions for a workbook in a project, when permissions are NOT set to Locked to the project? (Choose two.)
Editing permissions on a workbook in Tableau Server depends on the user's role and the project's permission settings. Since permissions are not locked (i.e., 'Managed by Owner'), let's dissect who can edit them:
Permission Model:
Not Locked: Owners of content (workbooks, data sources) can set permissions, and Project Leaders can override at the project level.
Site Roles: Define maximum capabilities (e.g., Viewer, Explorer, Creator).
Capabilities: 'Set Permissions' is explicit---only certain users get it.
Option C (The workbook's owner): Correct.
Details: The owner (typically the publisher) has full control over their workbook when permissions are Managed by Owner:
How: In the UI, go to Content > Workbooks > Actions > Permissions---owners can edit rules (e.g., grant Editor to a group).
Site Role: Minimum of Explorer (can publish) or Creator to publish, ensuring 'Set Permissions' capability.
Why: Ownership inherently includes permission management unless locked.
Option D (Users set to Project Leader for the workbook's project): Correct.
Details: Project Leaders are assigned via Content > Projects > Actions > Permissions > Set Project Leader:
Power: Can edit permissions for all content in the project, even if not the owner.
Site Role: Requires Site Administrator or Server Administrator (Creator/Explorer variants suffice).
Why: Overrides ownership in Managed by Owner mode---ensures project-level governance.
Option A (Users with project and workbook Viewer role): Incorrect.
Why: Viewer role (site-level) limits users to viewing---lacks 'Set Permissions' capability, regardless of project/workbook rules.
Option B (Users with workbook Interactor role): Incorrect.
Why: 'Interactor' isn't a standard role---likely a misnomer for Explorer or Viewer with interaction permissions (e.g., Filter). No permission-editing rights exist here.
Why This Matters: Knowing who can edit permissions prevents access control gaps---crucial for collaborative or regulated environments.
You have an existing group subscription. You add a user to the group. What statement correctly describes the result?
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.
A user named John publishes a workbook named Sales Quota to a project named Sales. The All Users group has the View and Download Workbook/Save As capabilities only to the Sales project. A user named Sandy has the Explorer (can publish) site role, on the Sales Quota workbook. No other users or groups have permissions to the Sales project. The Sales project is set to Managed by the owner. What are the effective rights for Sandy?
Which two tasks always require a server administrator? (Choose two.)
In Tableau Server, roles and permissions dictate who can perform specific administrative tasks. A 'server administrator' has full control over the entire Tableau Server deployment, while site administrators manage specific sites. Some tasks are restricted to server administrators due to their server-wide impact.
Option B (Adding a site): Creating a new site in a multi-site Tableau Server environment is a server-level task that only a server administrator can perform. Sites are logical partitions within the server, and adding a site affects the overall server structure. Site administrators cannot create new sites; they can only manage existing ones.
Option D (Adding users): Adding users to Tableau Server (e.g., via the TSM interface or tabcmd) is a server administrator task when it involves adding users at the server level or assigning them to the default site. While site administrators can add users to their specific site in a multi-site environment, the initial addition of users to the server requires server administrator privileges. The question's phrasing (''always require'') suggests a server-wide context, making this a correct choice.
Option A (Creating a schedule): This is incorrect because both server administrators and site administrators can create schedules for tasks like extract refreshes or subscriptions within their scope. It's not exclusive to server administrators.
Option C (Locking project permissions): This is incorrect because locking project permissions can be done by a site administrator or project leader with appropriate permissions. It's a project-level action, not a server-level task requiring a server administrator.
You need to verify the status of the Coordination Service ensemble in a high-availability (HA) Tableau Server cluster. What should you do?
In an HA Tableau Server cluster, the Coordination Service (ZooKeeper ensemble) maintains cluster state---let's find the best way to check it:
Coordination Service:
Runs on multiple nodes (3 or 5 in HA) to ensure quorum and failover.
Status indicates if it's running and synced---critical for cluster health.
Option C (Run tsm status -v): Correct.
Details: tsm status --verbose lists all processes across nodes, including Coordination Service (e.g., 'Coordination Service: RUNNING').
Why Best: Provides detailed, node-specific status in the CLI---e.g., 'Node 1: RUNNING, Node 2: RUNNING.'
Use: Run on the initial node; -v ensures full output.
Option A (TSM web client Status page): Incorrect.
Why: The TSM UI (Server > Status) shows process counts (e.g., 'Coordination Service: 3 instances'), but not detailed per-node status---less granular than CLI.
Option B (tsm maintenance ziplogs): Incorrect.
Why: Generates log archives for troubleshooting, not a real-time status check.
Option D (Tableau Server Status page): Incorrect.
Why: The Server Status page (Server > Status in the web UI) monitors application processes (e.g., VizQL), not TSM's Coordination Service.
Why This Matters: Coordination Service health ensures HA stability---tsm status -v is the admin's go-to for precision.
Exam domains verified against: Official Salesforce Analytics-Admn-201 exam guide, last checked September 2026.
Covers user experience, Tableau Server architecture, version identification, hardware and software requirements including operating systems and browser compatibility, licensing models, server processes and topology, and data source connectivity including file types, extract versus live connections, ports, and database drivers.
Addresses installation steps and options, identity stores and single sign-on methods such as Active Directory, SAML, Kerberos and OpenID Connect, SSL setup, server configuration for caching and process distribution, email alerts and subscriptions, site and project configuration, user management, security configuration across system and project levels, and permission design.
Sample question from this domain above: Q6
Focuses on ongoing operational tasks including data connection maintenance, schedule and subscription management, server analysis and monitoring, backup and restore procedures, user lifecycle management, license updates, server restart and shutdown, command line tools like tsm and tabcmd, REST API usage, log file analysis, workbook and data source revision history, and understanding end-user capabilities versus administrator capabilities.
Covers browser requirements for third-party cookies, password reset procedures for users and service accounts, log file packaging for support cases, server resource validation, search index rebuilding, maintenance analysis reports, and support request procedures.
Addresses the upgrade process and procedures, clean reinstall scenarios, hardware migration strategies, and backwards compatibility considerations.
Common questions about the exam itself
