Salesforce Certified Tableau Server Administrator Analytics-Admn-201 Exam Practice Test

Answer : C

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.

Answer : C

Registering Tableau Server from the command line involves providing configuration details (e.g., identity store, license) via the tsm register command. Let's explore this fully:

Registration Process:

Run during initial setup or to update settings (e.g., after changing AD/LDAP config).

Uses a configuration file to pass parameters to TSM.

Command: tsm register --file .

File Format:

Tableau Server uses JSON for configuration files in TSM commands like tsm register.

Example:

json

CollapseWrapCopy

{

'identityStore': {

'type': 'local',

'domain': 'example.com'

}

}

JSON is structured, machine-readable, and aligns with Tableau's modern CLI design.

Option C (JSON): Correct.

Official format for tsm register, per documentation and practical use.

Option A (YML): Incorrect.

While tabsvc.yml exists internally, it's not for registration---tsm register uses JSON.

Option B (XML): Incorrect.

Older Tableau configs used XML (e.g., workgroup.yml pre-TSM), but TSM standardized on JSON.

Option D (HTTP): Incorrect.

HTTP is a protocol, not a file format---irrelevant here.

Why This Matters: Correct file format ensures seamless registration, avoiding CLI errors in setup or migrations.

Answer : D

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.

Answer : C

Subscriptions in Tableau Server deliver workbook views to users via email on a schedule. Group subscriptions apply to all group members---let's unpack this:

Group Subscription Mechanics:

Created via Workbooks > Actions > Subscribe > Select Group.

Delivers content to all users in the group at the time the subscription runs (e.g., daily PDF).

Dynamic: Membership updates (additions/removals) are reflected automatically on the next run.

Option C (The subscription updates automatically to include the new user): Correct.

Details: When you add a user to the group (e.g., via Users > Groups > Add Users), Tableau Server's subscription process queries the group's current membership at runtime. The new user receives the subscription on the next scheduled delivery---no manual action needed.

Example: Group 'Sales' has a 9 AM subscription. Add a user at 8 AM---they get the email tomorrow at 9 AM.

Option A (Admin receives notice to approve/deny): Incorrect.

Why: No approval workflow exists for group membership changes in subscriptions---it's automatic.

Option B (Creator must manually edit): Incorrect.

Why: Subscriptions are tied to the group, not a static user list---manual edits aren't required for membership changes.

Option D (Only members at creation time): Incorrect.

Why: This would be true for individual subscriptions (static list), but group subscriptions are dynamic.

Why This Matters: Dynamic group subscriptions streamline content delivery as teams evolve, reducing admin overhead.

Answer : A, C, D

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.

Answer : C

Tableau Server's minimum hardware recommendations for a production single-node deployment ensure reliable performance for small to medium workloads. As of the latest documentation:

CPU: 8 cores (2.0 GHz or higher) to handle concurrent users, rendering, and background tasks.

RAM: 32 GB to support in-memory processing (e.g., VizQL, Data Engine) and caching.

Disk Space: 50 GB free for installation, logs, extracts, and temporary files.

Let's break it down:

Option C (8-Core CPU, 32 GB RAM, 50 GB free disk space): Correct. This matches Tableau's official minimum for production:

8 cores ensure sufficient parallelism for processes like Backgrounder and VizQL.

32 GB RAM supports multiple users and extract refreshes.

50 GB disk space accommodates growth (initial install is ~1--2 GB, but logs and extracts expand).

Option A (4-Core, 16 GB RAM, 50 GB): Incorrect. Too low for production---4 cores and 16 GB RAM are below the threshold for reliable performance under load.

Option B (2-Core, 8 GB RAM, 15 GB): Incorrect. This is for non-production (e.g., trial) setups, insufficient for production stability.

Option D (4-Core, 64 GB RAM, 50 GB): Incorrect. 4 cores are inadequate, though 64 GB RAM exceeds the minimum (32 GB).

Why This Matters: Under-spec hardware can lead to slow performance, failed refreshes, or crashes in production---adhering to the minimum ensures stability.

Answer : 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.