Free Salesforce Analytics-Admn-201 Exam Dumps July 2026

Tableau Desktop and Tableau Server have versioning considerations when publishing content, particularly regarding compatibility between older Desktop versions (e.g., 10.5) and newer Server versions (e.g., 2020.1). Let's break this down step-by-step:

Publishing Process: With a Creator site role and Publisher permissions, you have the rights to publish workbooks to the specified project. Tableau Server accepts workbooks from older Desktop versions (e.g., 10.5) and upgrades them to the current Server version (2020.1) during publishing. This process is seamless for the workbook itself, but extracts require special handling.

Extract Handling: If the workbook contains embedded .tde extracts (stored within the .twb or .twbx file), Tableau Server 2020.1 converts these to .hyper format upon publishing. This conversion is necessary because .hyper replaced .tde as the default extract engine starting in Tableau 10.5 and beyond, offering better performance and scalability. During this process, Tableau Desktop or Server displays a warning to inform the user of the upgrade, as it's a one-way conversion (you can't revert to .tde on the Server).

Now, let's evaluate the options:

Option A (You will successfully publish without any errors or warnings): Incorrect. While the publishing succeeds, a warning about the .tde to .hyper conversion appears if the workbook contains embedded extracts. Without extracts, no warning occurs, but the question's context implies extracts are likely involved (common in visualizations).

Option B (Error message: unable to publish to a newer version): Incorrect. Tableau supports publishing from older Desktop versions to newer Server versions. There's no outright error blocking this; compatibility is maintained.

Option C (Warning: embedded .tde extracts will be upgraded to .hyper): Correct. This is the precise warning displayed when a workbook with .tde extracts is published to a Server version that uses .hyper. It ensures the user is aware of the format change, which might affect extract refresh schedules or performance expectations.

Option D (Warning: workbook will be upgraded to a new version): Partially correct but less specific. The workbook is upgraded to 2020.1 compatibility, but the warning focuses on the extract format change (.tde to .hyper), not the workbook version generically. Option C is more accurate.

Why This Matters: The .tde to .hyper shift improves query performance and supports larger datasets, but users need to know about it for planning (e.g., extract refresh schedules might need adjustment). The warning ensures transparency.

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.

Single Sign-On (SSO) allows users to authenticate once (e.g., via a corporate identity provider) and access Tableau Server without re-entering credentials. Tableau Server supports several SSO methods:

OpenID Connect (OIDC): An OAuth 2.0-based protocol for SSO, configured via Tableau's SAML settings with an OIDC-compatible IdP (e.g., Google, Okta).

Kerberos with Active Directory: A ticket-based SSO protocol, widely used in Windows environments with AD integration.

SAML: A flexible SSO standard using XML assertions, supporting various IdPs (e.g., ADFS, PingFederate).

Let's evaluate:

Option A (OpenID Connect): Correct. OIDC is an SSO method, implemented as a SAML variant in Tableau Server, enabling seamless login.

Option C (Kerberos with Active Directory): Correct. Kerberos provides SSO in AD environments, delegating authentication to the domain controller.

Option D (Security Assertion Markup Language - SAML): Correct. SAML is a core SSO method in Tableau, widely adopted for enterprise integrations.

Option B (Local Authentication): Incorrect. Local Authentication uses Tableau's internal user database, requiring manual credential entry---no SSO support.

Why This Matters: SSO enhances user experience and security by leveraging existing identity systems, reducing password fatigue.

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.

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.

Option A (Deleted, content to server admin): Incorrect.

Why: No automatic reassignment to the server admin---manual action is required first.

Option B (Deleted, content to project leader): Incorrect.

Why: Project leaders don't automatically inherit content---no such mechanism exists.

Option C (User and content deleted): Incorrect.

Why: Tableau avoids deleting content with the user---too destructive without explicit intent.

Why This Matters: This safeguard prevents accidental data loss, ensuring admins manage ownership transitions deliberately.

Kerberos delegation allows Tableau Server to pass a user's Kerberos credentials to a data source for seamless authentication (SSO)---let's explore which sources support it:

Kerberos Overview:

Used with Active Directory (AD) for SSO in Windows environments.

Tableau Server delegates the user's ticket to the data source, avoiding embedded credentials.

Requires:

Data source support for Kerberos.

Proper configuration (e.g., SPN, constrained delegation).

Supported Data Sources: Per Tableau's documentation:

Option A (Teradata): Correct.

Details: Supports Kerberos delegation---common in enterprise data warehouses.

Config: Enable in TSM (tsm authentication kerberos configure) and set SPN for Teradata.

Option C (SQL Server): Correct.

Details: Fully supports Kerberos---widely used with AD-integrated SQL Server instances.

Config: Requires AD setup and 'Trustworthy' delegation in SQL Server.

Option D (SAP HANA): Correct.

Details: Supports Kerberos SSO via delegation---popular in SAP ecosystems.

Config: Needs HANA Kerberos setup (e.g., keytab) and Tableau Server integration.

Option B (PostgreSQL): Incorrect.

Why: Supports Kerberos authentication natively, but Tableau Server doesn't enable delegation to PostgreSQL---users must embed credentials or use other methods (e.g., OAuth).

Why This Matters: Kerberos delegation enhances security by avoiding stored passwords---knowing supported sources ensures SSO feasibility.

Table recommendations in Tableau Server suggest popular tables and data sources to users when they create new content in the web authoring environment. This feature is enabled by default but can be disabled at the site level.

Option A (Disable the option using the site Settings page): Correct. A site administrator can disable table recommendations by navigating to the site's Settings > General page in the Tableau Server web interface and unchecking the option 'Enable table recommendations.' This prevents users on that site from seeing these suggestions, offering a straightforward UI-based solution.

Option B (Use the command: tsm configuration set -k recommendations.enabled -v false): Incorrect. There is no recommendations.enabled key in the TSM configuration settings. This feature is managed per site, not server-wide via TSM.

Option C (Publish data sources only to projects with permissions locked): Incorrect. Locking permissions restricts access but doesn't disable the recommendation feature itself. Users with access would still see recommendations.

Option D (Disable the option using the server Settings page): Incorrect. Table recommendations are a site-specific setting, not a server-wide setting. The server Settings page (via TSM) controls global configurations, not this feature.