Comments on visualizations foster collaboration in Tableau Server—let’s break down the requirements:

Commenting Prerequisites :

Site-Level Enablement : Comments must be activated for the site.

Permission : Users need the "Add Comment" capability on the content.

Site Role : Minimum role of Viewer allows commenting if permissions are set.

Option B (Add Comments must be allowed in permissions) : Correct.

Details : In the Permissions dialog (e.g., for a workbook), set "Add Comment" to "Allowed" for users/groups. Default is "Denied" unless explicitly enabled.

How : Content > Workbooks > Actions > Permissions > Edit Rule .

Why : Permissions are granular—site enablement alone isn’t enough.

Option D (Comments must be enabled on the site Settings page) : Correct.

Details : Go to Site > Settings > General > Allow Comments —check the box.

Why : This is a site-wide toggle (default: off). Without it, no one can comment, regardless of permissions.

Option A (Minimum site role of Explorer - can publish) : Incorrect.

Why : Viewer role suffices if permissions allow—Explorer (can publish) isn’t required (it adds publishing, not commenting).

Option C (Server Settings page) : Incorrect.

Why : Comments are a site-level feature, not server-wide—no such toggle exists in TSM’s Server Settings.

Why This Matters : Enabling comments at both site and content levels ensures controlled collaboration—key for team insights.

Comments on Tableau Server visualizations facilitate collaboration. Let’s explore what’s supported:

Comments Feature : Enabled per site (Settings > General > Allow Comments). Users with "Add Comment" permission can post on views.

Option B (Text) : Correct.

Details : The primary content type—users type free-form text in the comment box.

Use : Notes, questions, or feedback (e.g., "Sales spiked here—why?").

Option C (@mentions) : Correct.

Details : Typing @username notifies the mentioned user via email or the UI (if notifications are enabled).

Use : Directs comments to specific people (e.g., "@John, check this trend").

Option A (Interactive snapshots of a view) : Incorrect.

Details : Snapshots (static images) aren’t supported in comments—users must take screenshots externally and can’t embed them interactively.

Option D (Images - jpg, png) : Incorrect.

Details : No attachment or image embedding in comments—text and mentions only. Workaround: Link to an image hosted elsewhere.

Why This Matters : Comments enhance teamwork, but their simplicity (text + mentions) keeps the interface lightweight and focused.

In Tableau Server, schedules manage tasks like extract refreshes and subscriptions. Each task within a schedule has a priority value (ranging from 1 to 100, where 1 is the highest priority and 100 is the lowest). Tasks with higher priority (lower numbers) are executed before tasks with lower priority (higher numbers) when queued by the Backgrounder process. If the Backgrounder is overloaded or delayed, lower-priority tasks may not complete on time, leading to inconsistent refreshes.

In this scenario:

The 7:00 AM Extract Refresh task is critical for the CEO’s workbook, but the data is only refreshed 70% of the time by 9:00 AM.

The server has a single node, meaning a single Backgrounder process handles all tasks. With five schedules (some overlapping in the early morning), contention or delays could prevent the 7:00 AM task from completing reliably before 9:00 AM.

Option C (Set the priority of this task to 1): Correct. Setting the task priority to 1 ensures it has the highest priority among all queued tasks. This increases the likelihood that the Backgrounder executes it promptly at 7:00 AM, completing the refresh before the CEO accesses the workbook at 9:00 AM. You can adjust task priority in the Tableau Server web interface under Schedules > Tasks > Edit Priority.

Option A (Set the default priority of this schedule to 50): Incorrect. The default priority for schedules is already 50, and this option refers to the schedule’s default, not the specific task. It wouldn’t address the contention issue.

Option B (Set the priority for all other tasks to 50): Incorrect. This keeps all tasks at the default priority (50), leaving the 7:00 AM task without a relative advantage. It doesn’t prioritize the CEO’s task.

Option D (Set the priority of this task to 100): Incorrect. Priority 100 is the lowest, which would deprioritize the task, making the refresh even less reliable.

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.

Tableau Server’s performance and stability depend on dedicated resources and proper configuration. Running additional software on the same server is the most likely to cause problems because:

Resource contention : Tableau Server requires significant CPU, RAM, and disk I/O. Other software (e.g., databases, web servers) can compete for these resources, leading to slowdowns, crashes, or failed tasks.

Port conflicts : Tableau uses specific ports (e.g., 80, 443, 8850), and other applications might interfere.

Security risks : Additional software increases the attack surface, potentially compromising Tableau Server.

Tableau recommends running the server on dedicated hardware without unrelated applications.

Option A (Running additional software on the server) : Correct. This is a common cause of performance issues and is explicitly discouraged in Tableau’s best practices.

Option B (Separating the Backgrounder and VizQL processes to different machines) : Incorrect. This is a supported multi-node configuration that can improve performance, not cause problems, if properly set up via TSM.

Option C (Configuring the server to use a static IP address) : Incorrect. A static IP is recommended for Tableau Server to ensure consistent network access, so it’s unlikely to cause issues.

Option D (Using a non-default installation path) : Incorrect. While not default, a custom path is supported (via TSM or installer options) and unlikely to cause problems if permissions and disk space are adequate.

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.

Tableau Server relies on several processes to function, each with a specific role. The Repository process (powered by PostgreSQL) serves as the database for metadata, storing critical information such as:

User and group details.

Permissions and site configurations.

Workbook and data source metadata (e.g., schedules, subscriptions).

Option B (Repository) : Correct. The Repository is the centralized database that holds all metadata, making it the backbone of Tableau Server’s content management. There are typically two instances in an HA setup (one active, one passive), monitored by the Cluster Controller.

Option A (Data Engine) : Incorrect. The Data Engine manages in-memory data processing and extract storage (e.g., .hyper files), not metadata. It’s separate from the Repository.

Option C (Backgrounder) : Incorrect. The Backgrounder handles background tasks like extract refreshes and subscriptions, but it doesn’t store metadata—it interacts with the Repository to retrieve task details.

Option D (File Store) : Incorrect. The File Store manages physical extract files and workbook assets, not metadata, which is stored in the Repository.