Importing an AD group into Tableau Server syncs user management-let's analyze the process and options:
* AD Group Import Process:
* How: In the UI (Users > Groups > Add Group > Active Directory), enter the AD group name, set a site role, and sync.
* Behavior:
* Existing Users: If a user is already in Tableau Server, their site role remains unchanged unless manually adjusted-sync applies the minimum role only if it upgrades access.
* New Users: Added to Tableau with the site role specified during import.
* Config: Requires AD authentication enabled in TSM.
* Option D (New users created are assigned the site role specified during import): Correct.
* Details: When importing (e.g., "SalesTeam" group, site role: Explorer):
* New users get Explorer.
* Existing users keep their role unless it's below Explorer (e.g., Unlicensed # Explorer).
* Why: Ensures consistent onboarding-new users align with the group's intended access.
* Option A (Existing users' roles change to match import): Incorrect.
* Why: Existing roles persist unless lower than the minimum-e.g., Viewer stays Viewer if import sets Explorer, but Unlicensed upgrades. Not a full overwrite.
* Option B (Requires a .csv file): Incorrect.
* Why: AD import uses live sync via LDAP-no .csv needed (that's for local auth imports).
* Option C (Change group name during import): Incorrect.
* Why: The AD group name is fixed-you can't rename it in Tableau during sync (it mirrors AD).
Post-import renaming is possible but not part of the process.
Why This Matters: Accurate AD sync ensures seamless user management-missteps can disrupt access or licensing.
Reference: Tableau Server Documentation - "Synchronize Active Directory Groups" (https://help.tableau.com
/current/server/en-us/groups_sync.htm).

Tableau Server has specific hardware requirements for production environments to ensure stability and performance. The minimum recommended free disk space for a production installation is 50 GB. This accounts for:
* The installation itself (approximately 1-2 GB).
* Space for log files, temporary files, and extracts managed by the File Store and Data Engine.
* Room for backups and operational overhead.
The full minimum hardware recommendations for a single-node production deployment are:
* 8 CPU cores (2.0 GHz or faster).
* 32 GB RAM.
* 50 GB free disk space (on the system drive, typically C: on Windows).
* Option A (32 GB): Incorrect. While 32 GB is the minimum RAM requirement, it's insufficient for disk space in production.
* Option B (50 GB): Correct. This matches Tableau's official recommendation for production environments.
* Option C (15 GB): Incorrect. 15 GB is the minimum for a non-production or trial installation, not production.
* Option D (64 GB): Incorrect. While 64 GB exceeds the minimum, it's not the specified requirement-
50 GB is sufficient.
Reference: Tableau Server Documentation - "Minimum Hardware Recommendations" (https://help.tableau.
com/current/server/en-us/requirements.htm).

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.
Reference: Tableau Server Documentation - "Manage Schedules and Tasks" (https://help.tableau.com/current
/server/en-us/schedule_manage.htm).

Tableau Server supports multiple authentication methods, including Local Authentication, Active Directory, Kerberos, SAML, and OpenID Connect. OpenID Connect (OIDC) is an identity layer built on OAuth 2.0, commonly used for single sign-on (SSO). In Tableau Server, OIDC is implemented as a variant of SAML (Security Assertion Markup Language) authentication because both are SSO protocols managed through the same configuration workflow.
To use OpenID Connect:
* Configure Tableau Server for SAML/SSO.
* Provide an OIDC-compatible identity provider (IdP) configuration (e.g., Google, Okta).
* Set up the IdP metadata and certificates in TSM.
* Option D (SAML): Correct. Tableau Server treats OIDC as a subset of its SAML authentication framework, so you configure it under the SAML settings in TSM.
* Option A (Local Authentication): Incorrect. Local Authentication uses Tableau's internal user database, not an external SSO protocol like OIDC.
* Option B (Kerberos): Incorrect. Kerberos is a network authentication protocol for Windows environments, unrelated to OIDC.
* Option C (Active Directory): Incorrect. AD uses LDAP or Kerberos, not OIDC, for authentication.
Reference: Tableau Server Documentation - "Configure SAML and OpenID Connect" (https://help.tableau.
com/current/server/en-us/saml_config.htm).

Tableau Services Manager (TSM) is the administrative tool for managing Tableau Server's configuration, processes, and topology. To log in to TSM (via the web UI at https://<server>:8850 or CLI), you need:
* TSM administrator credentials: These are distinct from site roles and are set during installation or reset via tsm reset.
* Local administrative rights: On Windows, the account used to access TSM must be in the local Administrators group on the initial node, as TSM interacts with system-level services.
In a test cluster, the engineer's inability to log in suggests they lack either the correct TSM credentials or sufficient OS-level permissions. Since the question focuses on a Windows environment and "initial node," the most immediate requirement is local administrative rights to run TSM commands or access the UI.
* Option C (An account with administrative rights to the computer): Correct. The engineer must use an account in the local Administrators group on the initial node to authenticate to TSM. After that, they' ll need the TSM admin username/password set during installation.
* Option A (An account with a Creator site role): Incorrect. Site roles (e.g., Creator) apply to content access within Tableau Server, not TSM administration.
* Option B (An account with a Site Administrator role): Incorrect. Site Administrators manage site content, not server-level TSM functions.
* Option D (An account for the Tableau Server administrator): Partially correct but incomplete. This likely refers to the TSM admin account, but without local admin rights on the machine, login will fail.
Option C is more precise.
Reference: Tableau Server Documentation - "TSM Authentication" (https://help.tableau.com/current/server
/en-us/tsm_overview.htm#authentication).