Analytics-Admn-201 Online Practice Questions

Explanation:
Data-driven alerts notify users when data meets conditions (e.g., sales > $10K). Let’s examine when
Tableau checks these:
Alert Mechanics:
Enabled per site (Settings > General > Data-Driven Alerts).
Backgrounder evaluates conditions against extract data.
Check Intervals: Configurable via tsm configuration set -k dataAlerts.checkIntervalInMinutes (default:
60 minutes).
Refresh Trigger: Also checks post-extract refresh for immediate updates.
Option A (Every 60 minutes): Correct.
Details: Default interval―Backgrounder polls every hour to evaluate alert conditions.
Config: Adjustable (e.g., -v 30 for 30 minutes).
Option D (Whenever extracts in the related workbook are refreshed): Correct.
Details: An extract refresh updates the data, triggering an immediate alert check to catch changes promptly.
Why: Ensures timely notifications without waiting for the next poll.
Option B (Every 10 minutes): Incorrect.
Why: Not the default―possible via config, but not standard.
Option C (Whenever a new extract is published): Incorrect.
Why: Publishing creates the extract; alerts trigger on refreshes or polling, not initial publication.
Why This Matters: Timing affects alert responsiveness―balancing frequency and server load is key.
Reference: Tableau Server Documentation - "Data-Driven Alerts" (https://help.tableau.com/current/server/en-us/data_alerts.htm).

Explanation:
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.
Reference: Tableau Server Documentation - "Authentication" (https://help.tableau.com/current/server/en-us/auth_overview.htm).

Explanation:
Tableau Server uses caching to speed up workbook loading by storing query results. After a
scheduled extract refresh updates the data, the cache may need recomputing―let’s dive into the
mechanics:
Caching Basics:
VizQL Cache: Stores rendered views and query results for faster access.
Refresh Trigger: A scheduled refresh updates the underlying extract (.hyper), but the cache isn’t automatically invalidated―it’s demand-driven.
Recompute Conditions: Tableau recomputes the cache when the workbook is accessed (viewed) and
its data has changed (e.g., via refresh).
Evaluation:
Option B (The workbook has upcoming scheduled refresh tasks): Correct.
Why: An upcoming refresh task indicates the workbook relies on an extract with a schedule. After the refresh runs, the data changes, priming the cache for recomputation on next view. Without a schedule, no refresh occurs, so this is a prerequisite.
Detail: Schedules are set in Schedules > Tasks―e.g., "Daily at 2 AM."
Option D (The workbook has been viewed recently): Correct.
Why: Viewing triggers cache recomputation if the data has changed (e.g., post-refresh). Tableau uses a "lazy caching" model―cache updates only when a user loads the workbook, ensuring fresh results. Detail: "Recently" isn’t strictly defined but implies post-refresh access. Option A (Published in the last month): Incorrect.
Why: Publish date is irrelevant―cache recomputation ties to data changes and access, not publication timing.
Option C (All Users group has permission rule allowing access): Incorrect.
Why: Permissions enable viewing, but recomputation requires actual access (viewing) and a refresh event, not just potential access.
Why This Matters: Caching balances performance and freshness―understanding triggers prevents stale data surprises.
Reference: Tableau Server Documentation - "Caching and Performance"
(https://help.tableau.com/current/server/en-us/perf_cache.htm).

Explanation:
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.
Reference: Tableau Server Documentation - "Licensing Overview" (https://help.tableau.com/current/server/en-us/license_usage.htm).

Explanation:
Tableau Server’s search functionality relies on an indexed catalog of content (workbooks, data sources, etc.) stored in the Repository. If a user can see a workbook in the UI (e.g., under Content > Workbooks) but not find it via search, the search index may be outdated or corrupted. This can happen due to:
Indexing delays after publishing.
Server maintenance or crashes affecting the index.
Option D (Run the tsm maintenance reindex-search command): Correct. This command rebuilds the search index, ensuring all content (including the user’s workbook) is properly cataloged and searchable. Steps:
Stop Tableau Server (tsm stop).
Run tsm maintenance reindex-search.
Start Tableau Server (tsm start).
This is a server administrator task and resolves systemic search issues.
Option A (Re-publish the workbook with keywords): Incorrect. Re-publishing might update the index for that workbook, but it doesn’t fix a broader indexing problem. Keywords enhance relevance, not indexing itself.
Option B (Add tags to the workbook): Incorrect. Tags improve searchability but don’t address an index failure. If the workbook isn’t indexed, tags won’t help.
Option C (Log out, and then log back in): Incorrect. This refreshes the user session but doesn’t affect the server-side search index.
Why This Matters: A reliable search index is critical for content discovery in large deployments― reindex-search ensures consistency.
Reference: Tableau Server Documentation - "Reindex Search" (https://help.tableau.com/current/server/en-us/cli_maintenance_tsm.htm#reindex-search).