2026 Updated Verified Pass Analytics-Admn-201 Exam - Real Questions and Answers
Dumps Moneyack Guarantee - Analytics-Admn-201 Dumps Approved Dumps
Salesforce Analytics-Admn-201 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
NEW QUESTION # 34
What account should you use to run the Tableau Server installation program?
- A. An NT AUTHORITY\NetworkService account
- B. A local user account
- C. A domain user account
- D. An account in the local administrator group
Answer: D
Explanation:
Installing Tableau Server on Windows requires an account with sufficient privileges to configure services, write to the file system, and manage registry settings. Let's analyze this in depth:
* Installation Requirements:
* The installer creates services (e.g., Tableau Server Gateway), writes to Program Files and ProgramData, and configures TSM.
* It needs local administrative privileges on the machine to perform these tasks.
* Post-install, a "Run As" account can be set for services (e.g., NT
AUTHORITY\NetworkService), but this is separate from the install account.
* Option C (An account in the local administrator group): Correct.
* Why: The account must be in the local Administrators group to:
* Install software (UAC elevation).
* Configure services and ports.
* Write to protected directories (e.g., C:\Program Files\Tableau).
* Examples: A local admin (e.g., Administrator) or a domain user added to the Administrators group (e.g., DOMAIN\AdminUser).
* Process: Log in as this account, run the installer, and provide TSM admin credentials during setup.
* Option A (A local user account): Incorrect.
* A standard local user (not in Administrators) lacks permissions-installation would fail with
"Access Denied" errors.
* Option B (A domain user account): Incorrect unless clarified.
* A domain user without local admin rights can't install. If it's in the Administrators group, it qualifies, but C is more specific.
* Option D (NT AUTHORITY\NetworkService): Incorrect.
* This is a built-in service account for running services (default "Run As" post-install), not for executing the installer-an interactive user account is required.
Why This Matters: Using the right account prevents install failures and ensures secure configuration- critical for production setups.
Reference: Tableau Server Documentation - "Install and Configure Tableau Server" (https://help.tableau.com
/current/server/en-us/install_config.htm).
NEW QUESTION # 35
What statement correctly describes locking permissions to a project?
- A. You can lock permissions to a project by changing Customizable to Locked
- B. Content permissions are locked to a project by default
- C. Locking permissions to projects must be enabled on the Tableau Server Settings page
- D. You can lock permissions to a project by setting the appropriate Project permission role
Answer: A
Explanation:
In Tableau Server, projects organize content (workbooks, data sources) and use permissions to control access. "Locking permissions" restricts how permissions are managed within a project-let's explore this exhaustively:
* Permission Management Modes:
* Managed by Owner: Default mode. Content owners (e.g., workbook publishers) can set permissions on their items, inheriting project defaults as a starting point.
* Locked to the Project: Project-level permissions are enforced, and content owners cannot modify them. This ensures consistency across all items in the project.
* How to Lock:
* In the Tableau Server web UI:
* Go to Content > Projects.
* Select a project, click Actions > Permissions.
* In the Permissions dialog, change Permissions Management from "Customizable" (Managed by Owner) to "Locked."
* Set the desired permissions (e.g., Viewer, Editor) for users/groups, which then apply uniformly to all content.
* Via REST API: Use the updateProject endpoint with "permissionsLocked": true.
* Option B (You can lock permissions to a project by changing Customizable to Locked): Correct.
* Details: This is the precise action in the UI-switching from "Customizable" to "Locked" locks permissions at the project level.
* Impact: Owners lose the ability to override permissions on individual workbooks/data sources, enforcing governance.
* Example: Set "All Users" to Viewer (Locked)-all content in the project is view-only, regardless of owner intent.
* Option A (Locking permissions must be enabled on the Server Settings page): Incorrect.
* Why: Locking is a per-project setting, not a server-wide toggle. The Server Settings page (via TSM) controls global configs (e.g., authentication), not project permissions.
* Option C (Content permissions are locked by default): Incorrect.
* Default: New projects are "Managed by Owner" (Customizable), allowing flexibility unless explicitly locked by an admin.
* Option D (By setting the appropriate Project permission role): Incorrect.
* Confusion: "Project permission role" isn't a term-permissions are set via rules (e.g., Viewer, Editor), but locking is a separate action (Customizable # Locked).
Why This Matters: Locking permissions ensures uniform access control, critical for regulated environments or large teams where consistency trumps flexibility.
Reference: Tableau Server Documentation - "Lock Project Permissions" (https://help.tableau.com/current
/server/en-us/permissions_lock.htm).
NEW QUESTION # 36
What two types of users can sign in to Tableau Server and edit the permissions for a workbook in a project, when permissions are NOT set to Locked to the project? (Choose two.)
- A. Users set to Project Leader for the workbook's project
- B. Users that have the project and workbook Viewer role
- C. The workbook's owner
- D. Users that have the workbook Interactor role
Answer: A,C
Explanation:
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).
NEW QUESTION # 37
What is the minimum hardware recommendation for a single-node production installation of Tableau Server?
- A. 4-Core CPU (2.0 GHz or higher), 16 GB RAM, 50 GB free disk space
- B. 8-Core CPU (2.0 GHz or higher), 32 GB RAM, 50 GB free disk space
- C. 2-Core CPU (1.8 GHz or higher), 8 GB RAM, 15 GB free disk space
- D. 4-Core CPU (2.0 GHz or higher), 64 GB RAM, 50 GB free disk space
Answer: B
Explanation:
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.
Reference: Tableau Server Documentation - "Minimum Hardware Recommendations" (https://help.tableau.
com/current/server/en-us/requirements.htm).
NEW QUESTION # 38
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?
- A. It will always change to the minimum site role
- B. It will never change as a result of synchronization
- C. It will change to the minimum site role only if the minimum site role provides more access
- D. It will change to the minimum site role only if the minimum site role reduces access
Answer: D
Explanation:
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.
Reference: Tableau Server Documentation - "Synchronize Active Directory Groups" (https://help.tableau.com
/current/server/en-us/groups_sync.htm).
NEW QUESTION # 39
What is the minimum required free hard disk space recommended for a Tableau Server installation in production?
- A. 32 GB
- B. 50 GB
- C. 64 GB
- D. 15 GB
Answer: B
Explanation:
Tableau Server has specific hardware requirements for production environments to ensure stability and performance. The minimum recommended free disk space for a production installation is 50 GB. This accounts for:
* The installation itself (approximately 1-2 GB).
* Space for log files, temporary files, and extracts managed by the File Store and Data Engine.
* Room for backups and operational overhead.
The full minimum hardware recommendations for a single-node production deployment are:
* 8 CPU cores (2.0 GHz or faster).
* 32 GB RAM.
* 50 GB free disk space (on the system drive, typically C: on Windows).
* Option A (32 GB): Incorrect. While 32 GB is the minimum RAM requirement, it's insufficient for disk space in production.
* Option B (50 GB): Correct. This matches Tableau's official recommendation for production environments.
* Option C (15 GB): Incorrect. 15 GB is the minimum for a non-production or trial installation, not production.
* Option D (64 GB): Incorrect. While 64 GB exceeds the minimum, it's not the specified requirement-
50 GB is sufficient.
Reference: Tableau Server Documentation - "Minimum Hardware Recommendations" (https://help.tableau.
com/current/server/en-us/requirements.htm).
NEW QUESTION # 40
Which two types of content can you include in comments on a visualization? (Choose two.)
- A. Text
- B. Interactive snapshots of a view
- C. @mentions
- D. Images (jpg, png)
Answer: A,C
Explanation:
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.
Reference: Tableau Server Documentation - "Comment on a View" (https://help.tableau.com/current/server
/en-us/comment.htm).
NEW QUESTION # 41
What should you use to set a preferred active repository?
- A. A tsm configuration set command
- B. The TSM browser client's Configuration Topology page
- C. The TSM browser client's Maintenance page
- D. A tabcmd set command
Answer: A
Explanation:
Tableau Server uses a PostgreSQL database as its repository to store metadata, user information, and permissions. In a high-availability (HA) setup with multiple nodes, there are typically two repository instances: one active and one passive. The "preferred active repository" refers to designating which repository instance should take priority as the active one. This is managed through Tableau Services Manager (TSM).
The correct method to set the preferred active repository is by using the tsm configuration set command.
Specifically, you would use a command like:
tsm configuration set -k pgsql.preferred_host -v <hostname>
This command allows an administrator to specify the preferred host for the active repository, ensuring control over which node takes precedence in an HA environment.
Option B (tabcmd set command) is incorrect because tabcmd is a command-line utility primarily used for administrative tasks like managing users, groups, and content (e.g., publishing workbooks), not for configuring server topology or repository settings.
Option C (TSM browser client's Maintenance page) is incorrect because the Maintenance page in the TSM web interface is used for tasks like backups, restores, and cleanup, but it does not provide an option to set the preferred active repository.
Option D (TSM browser client's Configuration Topology page) is partially relevant since the Topology page displays the current configuration of services across nodes, including the repository. However, it does not allow direct modification of the preferred active repository; this must be done via the tsm command line.
Reference: Tableau Server Documentation - "Configure Tableau Server Repository" (https://help.tableau.com
/current/server/en-us/repository.htm) and "TSM Command Line Reference" (https://help.tableau.com/current
/server/en-us/cli_configuration_set.htm).
NEW QUESTION # 42
What Tableau Server authentication method should you configure to use OpenID Connect?
- A. Local Authentication
- B. SAML
- C. Active Directory
- D. Kerberos
Answer: B
Explanation:
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.
Reference: Tableau Server Documentation - "Configure SAML and OpenID Connect" (https://help.tableau.
com/current/server/en-us/saml_config.htm).
NEW QUESTION # 43
A user reports that a newly-published workbook runs slowly. What should you ask the user first to investigate the problem?
- A. Does the workbook always run slowly or does performance vary?
- B. How many times have you opened the workbook in Tableau Server?
- C. Does it run any faster in Tableau Desktop?
- D. Did you enable caching on the workbook?
Answer: C
Explanation:
When a user reports slow performance for a newly-published workbook on Tableau Server, troubleshooting requires isolating the cause-e.g., data source issues, server load, workbook design, or caching. The first question should establish a baseline to narrow the scope. Let's analyze this step-by-step with depth:
* Performance Context:
* A workbook's speed depends on:
* Data Source: Query complexity, size, network latency (e.g., database vs. extract).
* Workbook Design: Filters, calculations, dashboard complexity.
* Server Resources: VizQL rendering, Backgrounder load, caching.
* "Newly-published" implies it's not yet optimized or cached on the server.
* Option A (Does it run any faster in Tableau Desktop?): Correct.
* Why First: Comparing Desktop vs. Server performance is the most foundational diagnostic step:
* Desktop Baseline: If it's slow in Desktop (local machine), the issue likely lies in the workbook (e.g., complex queries, large data) or data source (e.g., slow database)-not Server-specific.
* Server Difference: If it's fast in Desktop but slow on Server, the problem could be server- side (e.g., resource contention, network latency to the data source from Server).
* Practical Next Steps:
* Slow in Desktop: Optimize workbook (e.g., simplify calcs, use extracts).
* Fast in Desktop: Check Server (e.g., caching, VizQL load).
* Why Critical: Establishes whether the issue is inherent to the workbook/data or introduced by Server-guides all further investigation.
* Option B (Does the workbook always run slowly or does performance vary?): Useful but secondary.
* Why Not First: Variability (e.g., slow at peak times) points to server load, but without a Desktop baseline, you can't rule out workbook design. It's a follow-up question after A.
* Detail: Variability might suggest caching or concurrent user impact, but it assumes Server-side causation prematurely.
* Option C (How many times have you opened the workbook in Tableau Server?): Less relevant initially.
* Why Not First: Frequency of access might affect caching (first load is slower, subsequent loads faster), but it's too specific and doesn't isolate Desktop vs. Server. It's a niche follow-up.
* Option D (Did you enable caching on the workbook?): Misleading and incorrect.
* Why Not First: Caching is server-managed (e.g., VizQL cache settings via tsm data-access caching set), not a user-toggle per workbook. Users don't "enable" it-admins do. Plus, it's premature without a baseline.
Why This Matters: Starting with Desktop performance cuts through assumptions, pinpointing whether the root cause is client-side (workbook/data) or server-side-essential for efficient resolution in production.
Reference: Tableau Server Documentation - "Troubleshoot Performance" (https://help.tableau.com/current
/server/en-us/troubleshoot_performance.htm).
NEW QUESTION # 44
Which Tableau Server process performs the role of a database for metadata?
- A. Data Engine
- B. File Store
- C. Backgrounder
- D. Repository
Answer: D
Explanation:
Tableau Server relies on several processes to function, each with a specific role. The Repository process (powered by PostgreSQL) serves as the database for metadata, storing critical information such as:
* User and group details.
* Permissions and site configurations.
* Workbook and data source metadata (e.g., schedules, subscriptions).
* Option B (Repository): Correct. The Repository is the centralized database that holds all metadata, making it the backbone of Tableau Server's content management. There are typically two instances in an HA setup (one active, one passive), monitored by the Cluster Controller.
* Option A (Data Engine): Incorrect. The Data Engine manages in-memory data processing and extract storage (e.g., .hyper files), not metadata. It's separate from the Repository.
* Option C (Backgrounder): Incorrect. The Backgrounder handles background tasks like extract refreshes and subscriptions, but it doesn't store metadata-it interacts with the Repository to retrieve task details.
* Option D (File Store): Incorrect. The File Store manages physical extract files and workbook assets, not metadata, which is stored in the Repository.
Reference: Tableau Server Documentation - "Tableau Server Processes" (https://help.tableau.com/current
/server/en-us/processes.htm).
NEW QUESTION # 45
You have an installation of Tableau Server and a site that are configured to use default settings. What should you do to ensure that the users on the site can set up data-driven alerts?
- A. Enable data-driven alerts on the Tableau Services Manager Configuration page
- B. No action is necessary: the default settings enable data-driven alerts for the site
- C. Change the data-driven alerts setting on the new site's Settings page
- D. Run the tsm configuration set -k dataAlerts.checkIntervalInMinutes -v 60 command
Answer: C
Explanation:
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).
NEW QUESTION # 46
You have an existing group subscription. You add a user to the group. What statement correctly describes the result?
- A. The administrator receives a notice to approve or deny adding the user to the subscription
- B. The creator of the subscription receives notice of the change and must manually edit the subscription to reflect the new group membership
- C. The subscription updates automatically to include the new user
- D. The subscription will continue to include only the members of the group at the time the subscription was made
Answer: C
Explanation:
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.
Reference: Tableau Server Documentation - "Manage Subscriptions" (https://help.tableau.com/current/server
/en-us/subscribe.htm).
NEW QUESTION # 47
A user published a workbook ten days ago. The user can see the workbook on the Server, but she is unable to find the workbook by using Search. What should you do to resolve the problem?
- A. Run the tsm maintenance reindex-search command
- B. Instruct the user to log out, and then log back in
- C. Instruct the user to add tags to the workbook
- D. Instruct the user to re-publish the workbook with keywords
Answer: A
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).
NEW QUESTION # 48
A user receives an error after attempting to run an extract refresh on the Tableau Server. What should you review to identify the cause of the problem?
- A. Whether the project permissions are set to Locked to the project
- B. The UNC path to the extract's data source
- C. The Background Tasks for Extracts administrative view on the site status page
- D. The status of the Backgrounder process, as shown by the tsm status -v command
Answer: C
Explanation:
When an extract refresh fails on Tableau Server, troubleshooting requires identifying the root cause-e.g., connectivity issues, resource constraints, or configuration errors. The Backgrounder process handles extract refreshes, so it's a key focus, but the best diagnostic tool depends on granularity and context. Let's explore this thoroughly:
* Extract Refresh Process:
* An extract refresh pulls data from a source (e.g., database, file) into a .hyper file stored on Tableau Server.
* The Backgrounder executes these tasks based on schedules or manual triggers.
* Errors could stem from: database connectivity, credentials, file access, resource overload, or task misconfiguration.
* Option B (Background Tasks for Extracts administrative view): Correct. This is the most direct and detailed method:
* Location: In the Tableau Server web UI, go to Server > Status > Background Tasks for Extracts (or site-specific under Site > Status).
* Details Provided:
* Task name, schedule, and workbook/data source.
* Start/end times and status (e.g., Failed, Success).
* Error messages (e.g., "Cannot connect to database," "Permission denied").
* Why It's Best: It pinpoints the exact failure (e.g., "timeout," "invalid credentials") for the specific refresh, offering actionable insights without needing to dig through logs manually. Server or site administrators can access this view to diagnose issues quickly.
* Example: If the error is "Database login failed," you'd check credentials in the data source settings next.
* Option A (Status of the Backgrounder process via tsm status -v): Partially useful but insufficient:
* What It Shows: Running/stopped status of all processes (e.g., "Backgrounder: RUNNING").
* Limitation: It confirms if Backgrounder is operational but doesn't reveal why a specific task failed-no error details or task-level granularity.
* Use Case: If Backgrounder is stopped or crashed, this might indicate a broader issue, but the question implies a single refresh error, not a server-wide failure.
* Option C (The UNC path to the extract's data source): Relevant but secondary:
* Context: If the data source is a file (e.g., CSV on a network share), the UNC path (e.g.,
\\server\share\file.csv) must be accessible.
* Why Not First: The error could be unrelated (e.g., database issue, not file-based). The admin view (B) would reveal if it's a path issue first, guiding you to check the UNC path only if indicated (e.g., "File not found").
* Practical Note: Backgrounder needs share permissions and the Run As account must access it- checking this without context wastes time.
* Option D (Whether project permissions are set to Locked): Unlikely cause:
* Permissions Impact: Locked permissions restrict who can edit/view content, not whether an extract refresh runs-that's tied to the data source's connection settings and Backgrounder execution.
* Exception: If the refresh user lacks "Connect" permission to the data source, it might fail, but this is rare (owner/schedule typically has access). The admin view would flag this.
Why This Matters: The Background Tasks view is Tableau's purpose-built tool for extract diagnostics, saving time and reducing guesswork in production environments.
Reference: Tableau Server Documentation - "Administrative Views: Background Tasks for Extracts" (https://help.tableau.com/current/server/en-us/adminview_background_tasks.htm).
NEW QUESTION # 49
......
Updated PDF (New 2026) Actual Salesforce Analytics-Admn-201 Exam Questions: https://actual4test.practicetorrent.com/Analytics-Admn-201-practice-exam-torrent.html