Explanation:

When importing an Active Directory (AD) group into Tableau Server, the process synchronizes the group membership. For users who are entirely new to Tableau Server, the system must create an account for them. A key part of the import configuration is specifying the default site role these new users will receive, ensuring they have the appropriate permissions immediately.

✅ Correct Option:

D. New users created as a result of importing a group are assigned the site role specified during the import
🔹 This statement is accurate. During the import process, the administrator must select a default site role (e.g., Viewer, Explorer).
🔹 This selected role is automatically assigned to any user from the AD group who did not have a pre-existing Tableau Server account.
🔹 It is the mechanism for bulk-provisioning new users with a standardized set of permissions, streamlining user management.

❌ Incorrect Options:

A. If an imported group contains any users that have Tableau Server accounts, their site role will be changed to match the site role specified during the import
This is incorrect. For users who already have a Tableau Server account, importing them via an AD group does not change their existing site role. Their current role is preserved. The import role specified only applies to brand-new users.

B. Importing a group from Active Directory requires a .csv file that lists user IDs
This is false. The primary method for importing an AD group is by directly connecting to and selecting the group from the Active Directory service itself. A CSV file is used for a different process, such as creating a local group or adding users manually, not for syncing with an AD group.

C. You can change the name of a group during import, although this will not change the group’s name in Active Directory
This is incorrect. When importing an AD group, you cannot rename it during the import process. The group name in Tableau Server is directly derived from and synchronized with the group's name in Active Directory.

📚 Reference:
Tableau Help Documentation: "Add Users to Tableau Server" - The documentation explains that when adding an Active Directory group, you specify a site role, and "Any new users are assigned that site role." It also clarifies that existing users' roles are not modified by the import.

Explanation:

This question tests knowledge of how Active Directory (AD) synchronization affects site roles in Tableau Server. Site roles define the highest level of access a user can have. When syncing groups from AD, administrators can specify a minimum site role for that group. Tableau uses this rule to ensure users don’t lose permissions unnecessarily — the sync only restricts roles when it lowers, not raises, access.

✅ Correct Option: A. It will change to the minimum site role only if the minimum site role reduces access 🔐
When an AD group with a defined minimum site role syncs to Tableau Server, each member’s site role adjusts only if the new minimum role lowers their current access. Tableau never automatically promotes a user’s access level during synchronization; it ensures roles remain at or below the minimum defined by the group policy to maintain security and consistency.

❌ Incorrect Option: B. It will change to the minimum site role only if the minimum site role provides more access 🚫
Tableau will never increase access through synchronization. The term “minimum” is key — it represents a lower boundary, not an upper opportunity. Users’ roles cannot be upgraded automatically; such changes must be made manually by administrators.

❌ Incorrect Option: C. It will always change to the minimum site role 🚫
This is inaccurate because Tableau does not overwrite site roles indiscriminately. If a user already has a role equal to or lower in access level than the group’s minimum role, their role remains unchanged during synchronization.

❌ Incorrect Option: D. It will never change as a result of synchronization 🚫
Group synchronization can change user roles — but only to reduce access if the current role exceeds the defined minimum. This ensures consistent role enforcement across group members while maintaining proper security boundaries.

📚 Reference:
Tableau Help – Site roles and Active Directory synchronization

Explanation:

The most significant and common cause of problems for a Tableau Server installation is resource contention. Tableau Server is designed to consume substantial CPU, memory, and disk I/O, as it runs many concurrent processes (VizQL Server, Backgrounder, Data Engine, etc.) to handle user requests, data queries, and extract refreshes. Running any additional software on the same machine introduces competition for these critical resources, leading directly to severe performance degradation, instability, slow dashboard load times, and potential service failures.

Correct Option:

A. Running additional software on the server ✅
Tableau Server requires its dedicated system resources to operate reliably and performantly. When you install other major applications, such as large database systems, corporate backup tools, or enterprise antivirus software without proper exclusions, they often compete directly with core Tableau processes for CPU cycles, RAM, and disk I/O. This competition is a top cause of slow performance and unpredictable service crashes, which is why Tableau documentation strongly recommends dedicating the machine solely to Tableau Server.

Incorrect Option:

B. Separating the Backgrounder and VizQL processes to different machines 💣
This is actually a recommended best practice in a distributed (multi-node) high-availability (HA) environment. VizQL Server handles live user visualization requests (foreground tasks), while Backgrounder runs extract refreshes and subscriptions (background tasks). Separating them prevents resource-intensive background jobs from degrading the interactive user experience, thereby improving the server's overall stability and performance.

C. Configuring the server to use a static IP address 🌐
Using a static IP address is a fundamental requirement and best practice for any professional server installation, including Tableau Server. A static IP ensures that the server's network location remains constant, preventing connectivity issues that can occur if the IP address were to change (a dynamic IP), which could break internal communication between cluster nodes and external access.

D. Using a non-default installation path ⚙️
While the default path is convenient, changing the installation path is a supported configuration feature of Tableau Server, especially if you need to install it on a drive other than the system's primary disk (e.g., to allocate more space). As long as the path follows standard operating system rules and permissions are set correctly, it will not inherently cause problems for the server's operation.

Reference:
General Performance Guidelines - Tableau Help

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:

Published data sources are a cornerstone of a well-governed Tableau environment. When a data source is published to Tableau Server, it becomes a standalone asset that can be connected to by multiple workbooks. This contrasts with an embedded data source, which is part of a specific workbook and not shared.

Centralized Data Management (C):
A published data source acts as a "single source of truth." This means that data cleaning, modeling, calculations, and security can all be managed in one central location. If the underlying data source changes or new fields need to be added, the administrator only has to update the published data source once, and those changes are automatically propagated to all connected workbooks. This prevents inconsistencies and ensures everyone is working with the same, trusted data.

Optimized Resources (D):
With published data sources, the extract refresh process is performed once on the server, not for every single workbook that uses the data. This significantly reduces redundant work. For example, if ten workbooks all use the same data extract, an embedded approach would require ten separate refresh tasks, consuming valuable server resources and disk space. A published data source only needs a single refresh, saving both storage and processing power.