Pass Your Analytics-Admn-201 Exam Easily - Real Analytics-Admn-201 Practice Dump Updated May 17, 2026
2026 Realistic Verified Free Salesforce Analytics-Admn-201 Exam Questions
Salesforce Analytics-Admn-201 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
NEW QUESTION # 13
What is the minimum hardware recommendation for a single-node production installation of Tableau Server?
- A. 2-Core CPU (1.8 GHz or higher), 8 GB RAM, 15 GB free disk space
- B. 4-Core CPU (2.0 GHz or higher), 64 GB RAM, 50 GB free disk space
- C. 8-Core CPU (2.0 GHz or higher), 32 GB RAM, 50 GB free disk space
- D. 4-Core CPU (2.0 GHz or higher), 16 GB RAM, 50 GB free disk space
Answer: C
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 # 14
What is the maximum number of tasks that a single Backgrounder process can execute simultaneously?
- A. One
- B. Unlimited (based on server resources)
- C. Two
- D. Three
Answer: A
Explanation:
The Backgrounder process in Tableau Server handles tasks like extract refreshes and subscriptions-let's explore its concurrency:
* Backgrounder Behavior:
* Each instance is single-threaded for task execution-one task at a time per Backgrounder.
* Multiple Backgrounders (e.g., in multi-node setups) increase parallelism, but a single Backgrounder is limited to 1 concurrent task.
* Queue: Additional tasks wait in the queue, prioritized by their priority (1-100).
* Option A (One): Correct.
* Details: A single Backgrounder executes one task (e.g., an extract refresh) until completion before starting the next.
* Config: Add more Backgrounders via TSM (tsm topology set-process -n node1 -pr backgrounder
-c 2) for more concurrency.
* Option B (Two): Incorrect.
* Why: Not natively supported-a single Backgrounder doesn't multi-thread tasks.
* Option C (Three): Incorrect.
* Why: Exceeds the single-threaded design.
* Option D (Unlimited): Incorrect.
* Why: Concurrency is fixed at 1 per instance-resources affect queue processing speed, not simultaneous tasks.
Why This Matters: Understanding Backgrounder limits guides scaling-more instances mean more parallel tasks, critical for heavy workloads.
Reference: Tableau Server Documentation - "Backgrounder Process" (https://help.tableau.com/current/server
/en-us/processes.htm#backgrounder).
NEW QUESTION # 15
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 re-publish the workbook with keywords
- C. Instruct the user to add tags to the workbook
- D. Instruct the user to log out, and then log back in
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 # 16
You need to ensure that Tableau Server requires the setup of a new administrator account the next time you attempt to log in. What should you do?
- A. Run the tsm register command
- B. Run the tsm reset command
- C. Edit tabsvc.yml
- D. Reinstall Tableau Server
Answer: B
Explanation:
To force Tableau Server to require the setup of a new administrator account (e.g., resetting the server to an initial setup state), the tsm reset command is the appropriate tool. This command resets Tableau Server's administrative configuration, including the TSM administrator account, while preserving content like workbooks and data sources.
Option B (Run the tsm reset command): Correct. Running tsm reset clears the current TSM administrator credentials and configuration settings. The next time you access TSM (e.g., via the web interface or CLI), it prompts you to set up a new administrator account, mimicking the initial setup process. Command: tsm reset -- username <new-username> --password <new-password>.
Option A (Edit tabsvc.yml): Incorrect. The tabsvc.yml file contains service configuration data, but manually editing it is not supported or recommended for resetting the administrator account. It could also corrupt the installation.
Option C (Run the tsm register command): Incorrect. The tsm register command is used to register Tableau Server with a new product key or identity store, not to reset the administrator account.
Option D (Reinstall Tableau Server): Incorrect. Reinstallation wipes the entire server, including content, and is overkill for this task. The tsm reset command achieves the goal without data loss.
Reference: Tableau Server Documentation - "TSM Reset Command" (https://help.tableau.com/current/server
/en-us/cli_reset.htm).
NEW QUESTION # 17
A user named John publishes a workbook named Sales Quota to a project named Sales. The All Users group has the View and Download Workbook/Save As capabilities only to the Sales project. A user named Sandy has the Explorer (can publish) site role, on the Sales Quota workbook. No other users or groups have permissions to the Sales project. The Sales project is set to Managed by the owner. What are the effective rights for Sandy?
- A. No access
- B. View and Download Workbook/Save As
- C. All of the capabilities associated with the Editor rule
- D. The same rights as John
Answer: B
NEW QUESTION # 18
What should you do to disable table recommendations for popular data sources and tables to users?
- A. Publish data sources only to projects with permissions locked to the project
- B. Use the command: tsm configuration set -k recommendations.enabled -v false
- C. Disable the option using the server Settings page
- D. Disable the option using the site Settings page
Answer: D
Explanation:
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.
Reference: Tableau Server Documentation - "Manage Site Settings" (https://help.tableau.com/current/server
/en-us/site_settings.htm).
NEW QUESTION # 19
What two events must occur for Tableau Server to recompute queries for a workbook cache after a scheduled refresh? (Choose two.)
- A. The workbook has upcoming scheduled refresh tasks
- B. The All Users group has a permission rule allowing access to the workbook
- C. The workbook has been viewed recently
- D. The workbook was published in the last month
Answer: A,C
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).
NEW QUESTION # 20
Which two commands are valid and complete commands? (Choose two.)
- A. tsm maintenance backup
- B. tsm maintenance ziplogs
- C. tsm maintenance cleanup
- D. tsm maintenance restore
Answer: B,C
Explanation:
TSM commands manage Tableau Server maintenance-let's validate their syntax:
* Command Requirements:
* Some need arguments (e.g., file paths); others are standalone.
* Valid and Complete: Must work as-is without errors.
* Option C (tsm maintenance cleanup): Correct.
* Details: Removes temporary files and old logs-no arguments required (optional flags like -l exist).
* Use: tsm maintenance cleanup-runs fully.
* Option D (tsm maintenance ziplogs): Correct.
* Details: Creates a zip of logs (e.g., tsm-logs.zip)-no arguments needed (optional -d for date range).
* Use: tsm maintenance ziplogs-complete and valid.
* Option A (tsm maintenance backup): Incorrect.
* Why: Requires -f <filename>.tsbak (e.g., tsm maintenance backup -f backup.tsbak)-incomplete without it.
* Option B (tsm maintenance restore): Incorrect.
* Why: Needs -f <filename>.tsbak (e.g., tsm maintenance restore -f backup.tsbak)-not standalone.
Why This Matters: Correct syntax ensures maintenance tasks execute without errors-critical for server health.
Reference: Tableau Server Documentation - "TSM Maintenance Commands" (https://help.tableau.com/current
/server/en-us/cli_maintenance_tsm.htm).
NEW QUESTION # 21
Which two settings should you configure to allow users to post comments on a visualization? (Choose two.)
- A. Comments must be enabled on the server Settings page
- B. Comments must be enabled on the site Settings page
- C. Add Comments must be allowed in permissions for the relevant users
- D. The relevant users must have a minimum site role of Explorer (can publish)
Answer: B,C
Explanation:
Comments on visualizations foster collaboration in Tableau Server-let's break down the requirements:
* Commenting Prerequisites:
* Site-Level Enablement: Comments must be activated for the site.
* Permission: Users need the "Add Comment" capability on the content.
* Site Role: Minimum role of Viewer allows commenting if permissions are set.
* Option B (Add Comments must be allowed in permissions): Correct.
* Details: In the Permissions dialog (e.g., for a workbook), set "Add Comment" to "Allowed" for users/groups. Default is "Denied" unless explicitly enabled.
* How: Content > Workbooks > Actions > Permissions > Edit Rule.
* Why: Permissions are granular-site enablement alone isn't enough.
* Option D (Comments must be enabled on the site Settings page): Correct.
* Details: Go to Site > Settings > General > Allow Comments-check the box.
* Why: This is a site-wide toggle (default: off). Without it, no one can comment, regardless of permissions.
* Option A (Minimum site role of Explorer - can publish): Incorrect.
* Why: Viewer role suffices if permissions allow-Explorer (can publish) isn't required (it adds publishing, not commenting).
* Option C (Server Settings page): Incorrect.
* Why: Comments are a site-level feature, not server-wide-no such toggle exists in TSM's Server Settings.
Why This Matters: Enabling comments at both site and content levels ensures controlled collaboration-key for team insights.
Reference: Tableau Server Documentation - "Enable Comments" (https://help.tableau.com/current/server/en- us/comment.htm#enable).
NEW QUESTION # 22
What type of information is stored in the tsm maintenance backup -f <filename>.tsbak command?
- A. Notification settings
- B. Repository data
- C. SMTP server settings
- D. Topology data
Answer: B
Explanation:
The tsm maintenance backup command creates a backup file (with a .tsbak extension) that captures critical data needed to restore Tableau Server in case of failure or migration. This backup primarily includes:
Repository data: This encompasses the PostgreSQL database, which stores metadata such as workbooks, data sources, user information, permissions, schedules, and subscriptions.
Configuration data: This includes server settings like authentication methods, port configurations, and service layouts, but it does not include topology data as a separate entity (topology is part of the configuration).
The command does not back up the following:
Extract files (stored in the File Store), which must be backed up separately if needed.
Log files, which are archived using tsm maintenance ziplogs.
Option A (Notification settings) is incorrect because while notification settings are part of the configuration data stored in the repository, they are not the primary focus of the backup. The broader category is "repository data." Option B (SMTP server settings) is also incorrect for the same reason-SMTP settings are configuration data within the repository, but the backup is not limited to just these settings.
Option D (Topology data) is incorrect because topology data (e.g., how services are distributed across nodes) is part of the configuration included in the backup, but it's not stored as a standalone item. The .tsbak file is centered on the repository database.
Reference: Tableau Server Documentation - "Back Up Tableau Server Data" (https://help.tableau.com/current
/server/en-us/backup_restore.htm).
NEW QUESTION # 23
Several Tableau Server users published workbooks that have large extracts. After several weeks of use, the users abandoned the workbooks. What should you do to identify the abandoned workbooks?
- A. Delete all extracts and allow them to be re-generated automatically if they are still in use
- B. Examine the extract files in ProgramData/Tableau/Tableau Server/data/tabsvc/dataengine/extract
- C. Use the Stale Content administrative view
- D. View all workbooks, and sort by the Modified date
Answer: C
Explanation:
Abandoned workbooks-those no longer actively used-can clutter Tableau Server and consume resources (e.
g., disk space for extracts). Identifying them efficiently requires leveraging built-in administrative tools rather than manual or destructive methods. Let's explore this in depth:
* Tableau Server Admin Views: Tableau provides pre-built administrative views to monitor server health, usage, and content. The Stale Content view, accessible under Server > Status > Administrative Views, is specifically designed to identify content (workbooks, data sources) that hasn' t been viewed or modified recently. It shows:
* Content name, owner, and project.
* Last viewed date and last modified date.
* View count over a period.This view uses Repository data to track usage metrics, making it ideal for spotting abandoned workbooks.
* Option A (Use the Stale Content administrative view): Correct. This is the most efficient and non- invasive method. You can filter by last viewed date (e.g., >30 days ago) to identify workbooks with large extracts that users have stopped accessing. From there, you can contact owners or delete the content if policy allows. It's a server administrator's go-to tool for content management.
* Option B (Examine extract files in ProgramData/.../extract): Incorrect and impractical. The ProgramData/Tableau/Tableau Server/data/tabsvc/dataengine/extract directory stores .hyper extract files, but:
* File names are cryptic (e.g., GUIDs), not tied directly to workbook names.
* It doesn't indicate usage or abandonment-only file presence and size.
* Manual inspection is time-consuming and error-prone compared to the Stale Content view.
* Option C (Delete all extracts and allow them to be re-generated): Incorrect and risky. Deleting extracts (e.g., via tsm maintenance cleanup) removes them without identifying usage. Regeneration only occurs if a schedule or user triggers it, potentially disrupting active users and losing historical data unnecessarily.
* Option D (View all workbooks, and sort by the Modified date): Partially effective but inefficient. In the Tableau Server UI (e.g., under Content > Workbooks), you can sort by "Last Modified," but:
* It doesn't show viewership (a workbook might be modified recently but unused).
* It's manual and doesn't scale for large deployments compared to the Stale Content view.
Why This Matters: The Stale Content view leverages Tableau's metadata to provide actionable insights, saving time and reducing risk compared to manual or destructive alternatives. It's part of Tableau's governance toolkit.
Reference: Tableau Server Documentation - "Administrative Views" (https://help.tableau.com/current/server
/en-us/adminview_stale_content.htm).
NEW QUESTION # 24
What command should you run to update the automatically-generated secrets that are created during a Tableau Server installation?
- A. tsm licenses refresh
- B. tsm security regenerate-internal-tokens
- C. tsm security validate-asset-keys
- D. tsm data-access caching set -r 1
Answer: B
Explanation:
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.
Reference: Tableau Server Documentation - "Regenerate Internal Tokens" (https://help.tableau.com/current
/server/en-us/cli_security.htm#regenerate-internal-tokens).
NEW QUESTION # 25
Which three data sources support Kerberos delegation with Tableau Server? (Choose three.)
- A. SQL Server
- B. PostgreSQL
- C. SAP HANA
- D. Teradata
Answer: A,C,D
Explanation:
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.
Reference: Tableau Server Documentation - "Kerberos Delegation" (https://help.tableau.com/current/server
/en-us/kerberos_delegation.htm), "Supported Connectors" (https://help.tableau.com/current/server/en-us
/datasource.htm).
NEW QUESTION # 26
What should you do to disable table recommendations for popular data sources and tables to users?
- A. Publish data sources only to projects with permissions locked to the project
- B. Use the command: tsm configuration set -k recommendations.enabled -v false
- C. Disable the option using the server Settings page
- D. Disable the option using the site Settings page
Answer: D
Explanation:
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.
Reference: Tableau Server Documentation - "Manage Site Settings" (https://help.tableau.com/current/server/en-us/site_settings.htm).
NEW QUESTION # 27
When you use trusted tickets in Tableau Server, users can:
- A. Access embedded views without being prompted for credentials
- B. Embed database credentials
- C. Encrypt database connections
- D. Save and edit workbooks
Answer: A
Explanation:
Trusted Tickets is an authentication method in Tableau Server for embedding views in external applications (e.g., portals) without requiring users to log in manually. Here's how it works:
* A trusted application (e.g., a web server) authenticates with Tableau Server using a trusted IP or username/password.
* Tableau Server issues a temporary ticket (a unique string).
* The ticket is embedded in a view URL (e.g., /trusted/<ticket>/views/...), granting access to the view for a short period (configurable, default 5 minutes).
* Option A (Access embedded views without being prompted for credentials): Correct. Trusted tickets enable SSO-like behavior for embedded content, bypassing the login prompt if the ticket is valid. This is ideal for seamless integration into external systems.
* Option B (Encrypt database connections): Incorrect. Encryption is handled by data source configurations (e.g., SSL), not trusted tickets, which focus on user authentication.
* Option C (Save and edit workbooks): Incorrect. Trusted tickets grant view access, not edit permissions-those depend on the user's site role and permissions.
* Option D (Embed database credentials): Incorrect. Trusted tickets authenticate users to Tableau Server, not databases-database credentials are managed separately in the data source.
Why This Matters: Trusted tickets simplify embedding Tableau content securely in custom applications, enhancing user experience.
Reference: Tableau Server Documentation - "Trusted Authentication" (https://help.tableau.com/current/server
/en-us/trusted_auth.htm).
NEW QUESTION # 28
Which three items can be contained in a project? (Choose three.)
- A. Nested Projects
- B. Data Sources
- C. Workbooks
- D. Groups
Answer: A,B,C
Explanation:
In Tableau Server, projects are containers for organizing and securing content. They help manage permissions and structure content hierarchically. Let's define what can be contained:
* Workbooks: Visualizations and dashboards published to the Server.
* Data Sources: Published connections or extracts reusable across workbooks.
* Nested Projects: Sub-projects within a parent project, introduced in later versions (e.g., 2018.2) for deeper organization.
* Option B (Workbooks): Correct. Workbooks are the primary content type in projects, containing views and dashboards.
* Option C (Nested Projects): Correct. Nested projects allow hierarchical structuring (e.g., a "Sales" project with "Q1" and "Q2" sub-projects), with inherited or custom permissions.
* Option D (Data Sources): Correct. Published data sources reside in projects, providing reusable data connections.
* Option A (Groups): Incorrect. Groups are collections of users managed at the site or server level, not stored within projects. Projects contain content, not user entities.
Why This Matters: Projects are key to content governance-knowing what they hold helps administrators organize and secure assets effectively.
Reference: Tableau Server Documentation - "Projects" (https://help.tableau.com/current/server/en-us/projects.
htm).
NEW QUESTION # 29
What are two intervals when Tableau Server verifies if data conditions for data-driven alerts are true? (Choose two.)
- A. Whenever a new extract is published
- B. Every 60 minutes
- C. Whenever extracts in the related workbook are refreshed
- D. Every 10 minutes
Answer: B,C
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).
NEW QUESTION # 30
What is the minimum required free hard disk space recommended for a Tableau Server installation in production?
- A. 64 GB
- B. 15 GB
- C. 32 GB
- D. 50 GB
Answer: D
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 # 31
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 # 32
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?
- A. An account with a Site Administrator role
- B. An account with administrative rights to the computer
- C. An account for the Tableau Server administrator
- D. An account with a Creator site role
Answer: B
Explanation:
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.
Reference: Tableau Server Documentation - "TSM Authentication" (https://help.tableau.com/current/server
/en-us/tsm_overview.htm#authentication).
NEW QUESTION # 33
A user reports that a newly-published workbook runs slowly. What should you ask the user first to investigate the problem?
- A. How many times have you opened the workbook in Tableau Server?
- B. Does it run any faster in Tableau Desktop?
- C. Did you enable caching on the workbook?
- D. Does the workbook always run slowly or does performance vary?
Answer: B
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 # 34
You use Tableau Desktop 10.5 and plan to publish a visualization to a Tableau Server that runs version
2020.1. You are assigned the Creator site role, and Publisher permissions for a project. What statement correctly describes what happens when you attempt to publish the visualization?
- A. You will see a warning message instructing you that embedded .tde extracts will be upgraded to .hyper
- B. You will see an error message instructing you that you are unable to publish the workbook to a newer version of Tableau Server
- C. You will see a warning message instructing you that the workbook will be upgraded to a new version
- D. You will successfully publish the visualization without any errors or warnings
Answer: A
Explanation:
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:
* Version Context: Tableau Desktop 10.5 was released in 2017 and used the .tde (Tableau Data Extract) format for extracts. Tableau Server 2020.1, released in 2020, introduced the .hyper extract format (starting with version 10.5, but fully standardized later). When publishing from an older Desktop version to a newer Server version, Tableau ensures backward compatibility but may upgrade certain components.
* 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.
Reference: Tableau Server Documentation - "Publish a Workbook" (https://help.tableau.com/current/server
/en-us/publish_workbook.htm) and "Hyper Extract FAQ" (https://help.tableau.com/current/server/en-us
/hyper_faq.htm).
NEW QUESTION # 35
What are two features of the Tableau Server user-based license? (Choose two.)
- A. Restricts the number of machine cores you can deploy
- B. Enables distinct user roles
- C. A perpetual license
- D. A subscription license
Answer: B,D
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).
NEW QUESTION # 36
......
Analytics-Admn-201 Real Exam Questions and Answers FREE: https://www.practicematerial.com/Analytics-Admn-201-exam-materials.html
Analytics-Admn-201 Exam Questions | Real Analytics-Admn-201 Practice Dumps: https://drive.google.com/open?id=1amTcOQmhqOcM9DI65RlAP1hRhoABb9N0
