Explanation:

It's important to distinguish between the absolute minimum requirements to run the software and the recommended minimum for a production environment. Tableau provides different specifications for evaluation/testing versus production use to ensure performance and stability.

Why C is Correct: This option matches Tableau's official minimum recommended hardware for a production environment on a single server. A production server must handle multiple concurrent users, background tasks, and reliable performance, which requires more resources than a basic installation. The 8-core CPU and 32 GB RAM provide the necessary headroom for core processes and user activity.

Why A is Incorrect: This configuration (4 cores, 16 GB RAM) is the minimum requirement for an evaluation or test installation. It is sufficient to install the software and perform basic testing with a very light load but is explicitly not recommended for production use as it would likely suffer from performance issues under real-world conditions.

Why B is Incorrect: This configuration is below even the minimum requirements for a test installation and is insufficient for any meaningful Tableau Server deployment.

Why D is Incorrect: While the CPU and disk space are acceptable, 64 GB of RAM is above the minimum recommendation for a standard production server. It represents a larger, more powerful configuration that might be used for a heavier workload, but it is not the minimum recommendation.

Reference:
Tableau Help: Server Minimum Requirements - This page clearly distinguishes between the requirements. It states:
For a proof-of-concept or evaluation: 4 cores, 16 GB RAM.
For a production environment: 8 cores, 32 GB RAM, 50 GB disk space.

Explanation:

Why D is Correct:
Tableau Server has a safeguard to prevent accidental data loss. If a user owns any content (such as workbooks, data sources, or projects), the system will not allow you to delete them. Instead, the delete action fails, and the user's site role is automatically changed to "Unlicensed". This effectively removes their access to the server without deleting their account or the content they own. To fully delete the user, an administrator must first reassign all of their content to another user.

Why A is Incorrect:
This does not happen automatically. While the server administrator has the permission to reassign content, they must do so manually before the user can be deleted. The delete action itself will not trigger an automatic reassignment to the admin.

Why B is Incorrect:
Reassignment to a project leader is not an automatic process in Tableau Server. Project leaders do not automatically inherit content from users being deleted. The administrator must explicitly manage the reassignment.

Why C is Incorrect:
This would be a dangerous default behavior, as it could lead to massive, unintended data loss. Tableau Server is designed to protect content by preventing the deletion of users who own it.

Reference:
Tableau Help: Delete Users - The documentation clearly states: "You can't delete a user who is the owner of content on the site... If the user owns content, Tableau Server changes the user's site role to Unlicensed. To delete the user, you must first assign ownership of the user's content to another user."

Explanation:

When Tableau Server is installed on a machine with four processor cores, the installer configures one instance of each core Tableau Server process by default. This includes:

VizQL Server
Backgrounder
Data Engine
Application Server (VizPortal)
Cache Server
Repository (PostgreSQL)

The number of default instances is determined by Tableau’s installation logic, which scales based on available CPU cores. For servers with fewer than 8 cores, Tableau installs only one instance per process to avoid overloading the system.

❌ Why not the others?
A. 2, C. 8, D. 4: These values exceed the default configuration for a 4-core machine. Tableau only scales up process instances on servers with more cores (e.g., 8, 16, or more).

🔗 Reference:
See Tableau’s official documentation on Default Process Configuration.

Explanation:

Tableau Server's caching mechanism is designed to balance performance with data freshness. By default, it will recompute queries and refresh the cache for a workbook only when certain conditions are met to avoid unnecessary load on the server.

The workbook has upcoming scheduled refresh tasks (B): This is the trigger. Tableau Server knows that the underlying data for the workbook is being updated, so it needs to prepare new, fresh data for a user to view.

The workbook has been viewed recently (D): Tableau Server is smart about managing resources. It will only "warm the cache" for workbooks that users are actually interacting with. The definition of "recently viewed" is a configurable threshold (backgrounder.externalquerycachewarmup.view_threshold). If a workbook hasn't been viewed in a while, Tableau Server won't spend resources on re-computing the cache because it's unlikely a user will access it soon.

Explanation:

tsm reset returns Tableau Server to the post-install, pre-initialization state (without doing a full reinstall). After a reset, the next time you access the server you’ll be prompted to set up the initial administrator again.

Eliminations:
A) Edit tabsvc.yml – legacy (pre-TSM) and not how you reset the initial admin in modern Tableau Server.
C) tsm register – registers licensing/contact info; it doesn’t affect the admin account flow.
D) Reinstall Tableau Server – unnecessary; tsm reset achieves the goal without a full reinstall.