What Tableau Server authentication method should you configure to use OpenID Connect?
Answer(s): D
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.
Tableau Server Documentation - "Configure SAML and OpenID Connect" (https://help.tableau.com/current/server/en-us/saml_config.htm).
A new engineer reports that he is unable to log on to Tableau Services Manager (TSM) from the initial node of a Windows test cluster. Which account credentials should you instruct the engineer to use?
Answer(s): C
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.
Tableau Server Documentation - "TSM Authentication" (https://help.tableau.com/current/server/en-us/tsm_overview.htm#authentication).
If a user already exists as part of a group in Tableau Server, and Active Directory synchronization then applies a minimum site role to the group, what will happen to the existing user's site role?
Answer(s): A
When Tableau Server uses Active Directory (AD) for authentication, group synchronization imports AD groups and assigns a minimum site role (e.g., Viewer, Explorer) to users in that group. This ensures users meet a baseline access level. The behavior for existing users during sync is:If the user's current site role provides more access than the minimum (e.g., Explorer vs. Viewer), their role remains unchanged.If the user's current role provides less access than the minimum (e.g., Unlicensed vs. Viewer), their role is upgraded to the minimum.This preserves higher privileges while enforcing a floor. "Reduces access" means the minimum role is lower than the current role (e.g., Viewer vs. Explorer), in which case the existing role stays. Option A (It will change to the minimum site role only if the minimum site role reduces access):Correct. The user's role changes only if the minimum increases access (e.g., Unlicensed to Viewer); otherwise, it stays higher.Option B (It will change only if the minimum provides more access): Incorrect wording. This is the inverse of the actual behavior--change occurs when needed to meet the minimum, not to exceed it. Option C (It will always change): Incorrect. Existing higher roles are preserved. Option D (It will never change): Incorrect. It changes if the current role is below the minimum.
Tableau Server Documentation - "Synchronize Active Directory Groups" (https://help.tableau.com/current/server/en-us/groups_sync.htm).
What command should you run to update the automatically-generated secrets that are created during a Tableau Server installation?
Tableau Server uses internal secrets (tokens) for secure communication between its processes (e.g., Repository, File Store). These are automatically generated during installation and can be regenerated if compromised or for security maintenance. The command to update these is:tsm security regenerate-internal-tokens: This regenerates the internal security tokens, ensuring all processes use the new tokens after a restart.Option C (tsm security regenerate-internal-tokens): Correct. This is the documented command for updating internal secrets.Option A (tsm data-access caching set -r 1): Incorrect. This command configures caching behavior, not security tokens.Option B (tsm licenses refresh): Incorrect. This refreshes license data, unrelated to internal secrets. Option D (tsm security validate-asset-keys): Incorrect. This validates encryption keys for assets, not internal tokens.
Tableau Server Documentation - "Regenerate Internal Tokens" (https://help.tableau.com/current/server/en-us/cli_security.htm#regenerate-internal-tokens).
What are two features of the Tableau Server user-based license? (Choose two.)
Answer(s): A,B
Tableau Server's user-based licensing model assigns licenses to individual users (Creator, Explorer, Viewer) rather than machines or cores. Key features include:Subscription license: Licenses are typically subscription-based, renewed annually or monthly, aligning with Tableau's pricing model.Distinct user roles: It supports three roles (Creator, Explorer, Viewer), each with specific capabilities, enabling granular access control.Option A (A subscription license): Correct. User-based licenses are subscription-based by default. Option B (Enables distinct user roles): Correct. The model defines Creator, Explorer, and Viewer roles. Option C (Restricts the number of machine cores): Incorrect. This applies to core-based licensing, not user-based.Option D (A perpetual license): Incorrect. Perpetual licenses were phased out; user-based licenses are subscription-based as of recent models.
Tableau Server Documentation - "Licensing Overview" (https://help.tableau.com/current/server/en-us/license_usage.htm).
Post your Comments and Discuss Salesforce Analytics-Admn-201 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the Analytics-Admn-201 content, but please register or login to continue.