Guest Access allows embedded Tableau views (e.g., in a portal or intranet page) to be seen by anyone visiting the host page without requiring individual Tableau credentials, via an internal guest account. It does not grant content-creation rights, does not bypass admin login, and does not affect row-level security rules applied to the underlying data.

In Tableau, data sources can be embedded (stored within a workbook) or published (stored separately on Tableau Server). Let's define these and analyze the advantages:
Embedded Data Source: The connection details and any extract are bundled in the .twb or .twbx file.
Each workbook manages its own copy.
Published Data Source: The connection or extract is hosted on Tableau Server, reusable across multiple workbooks.
Now, let's evaluate the options:
Option C (Centralized data management is easier): Correct. Published data sources allow:
Single source of truth: One data source can serve multiple workbooks, ensuring consistency.
Unified updates: Refresh schedules, permissions, and metadata (e.g., calculated fields) are managed in one place via the Server UI.
Governance: Administrators can control access and monitor usage centrally. In contrast, embedded data sources require individual updates per workbook, leading to duplication and management overhead.
Option D (Storage space is conserved and resource usage during data refreshes is optimized):
Correct. With published data sources:
Storage: A single extract on the Server (e.g., a .hyper file) is shared across workbooks, avoiding redundant copies stored in each embedded workbook.
Refreshes: One refresh job updates the shared extract, reducing CPU and memory usage compared to multiple refreshes for duplicate embedded extracts. Embedded data sources replicate extracts, increasing disk space and refresh load.

Deleting a user in Tableau Server involves handling their owned content (workbooks, data sources) -- let's analyze the process:
Deletion Rules:
Ownership Check: Tableau prevents deletion if the user owns content to avoid orphaning it.
Action: Instead of deleting, the user's site role is set to Unlicensed, retaining their account and content ownership.
Resolution: An admin must reassign ownership (e.g., via Users > Actions > Change Owner) before deletion.
Option D (User switched to Unlicensed and NOT deleted): Correct. Details: Attempting deletion (e.g., Users > Select User > Actions > Delete) triggers a check. If content exists, the user becomes Unlicensed--still in the system but unable to log in. Why: Protects data integrity--content remains accessible for reassignment.

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.
Reference: Tableau Server Documentation - "Permissions" (https://help.tableau.com/current/server/en-us
/permissions.htm), "Project Leader Permissions" (https://help.tableau.com/current/server/en-us
/permissions_project_leader.htm).

Data-driven alerts in Tableau Server allow users to receive notifications when data in a view meets certain conditions (e.g., a sales metric exceeds a threshold). By default, this feature is disabled for a site unless explicitly enabled by an administrator.
Option C (Change the data-driven alerts setting on the new site's Settings page): This is the correct answer. In the Tableau Server web interface, a site administrator can navigate to the site's Settings > General page and enable the option "Let users create data-driven alerts." This must be done manually because the default setting for a new site is disabled. Once enabled, users with appropriate permissions (e.g., Viewer, Explorer, or Creator roles) can create alerts on views they have access to.
Option A (Enable data-driven alerts on the TSM Configuration page): This is incorrect because the TSM Configuration page (accessed via the TSM web UI or CLI) manages server-wide settings like ports, authentication, and processes, not site-specific features like data-driven alerts.
Option B (Run the tsm configuration set -k dataAlerts.checkIntervalInMinutes -v 60 command): This is incorrect. The dataAlerts.checkIntervalInMinutes key controls how frequently Tableau Server checks alert conditions (default is 60 minutes), but it does not enable the feature itself. The feature must first be turned on at the site level.
Option D (No action is necessary): This is incorrect because the default setting for data-driven alerts is off for new sites, requiring explicit action to enable it.
Reference: Tableau Server Documentation - "Configure Data-Driven Alerts" (https://help.tableau.com/current
/server/en-us/data_alerts.htm).