[Jan-2026] Use Real Analytics-Admn-201 Dumps - 100% Free Analytics-Admn-201 Exam Dumps [Q22-Q40]

[Jan-2026] Use Real Analytics-Admn-201 Dumps - 100% Free Analytics-Admn-201 Exam Dumps

Analytics-Admn-201 PDF Dumps Exam Questions – Valid Analytics-Admn-201 Dumps

NEW QUESTION # 22
What is the minimum hardware recommendation for a single-node production installation of Tableau Server?

• A. 4-Core CPU (2.0 GHz or higher), 64 GB RAM, 50 GB free disk space
• B. 2-Core CPU (1.8 GHz or higher), 8 GB RAM, 15 GB free disk space
• C. 4-Core CPU (2.0 GHz or higher), 16 GB RAM, 50 GB free disk space
• D. 8-Core CPU (2.0 GHz or higher), 32 GB RAM, 50 GB free disk space

Answer: D

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 # 23
Which three methods should an administrator use to create a Tableau Server group or project? (Choose three.)

• A. REST API
• B. Tableau Server browser interface
• C. tsm customize
• D. tabcmd

Answer: A,B,D

Explanation:
Tableau Server provides multiple methods to create groups (collections of users) and projects (content containers), catering to UI, CLI, and programmatic needs. Let's dissect each option with depth:
* Option B (Tableau Server browser interface): Correct.
* Groups: Go to Users > Groups > Add Group, name it, and optionally sync with Active Directory.
* Projects: Go to Content > Projects > New Project, set name, description, and permissions.
* Details: The web UI is intuitive, requiring server/site administrator rights. It's ideal for manual, ad-hoc creation with immediate visibility.
* Permissions: For projects, you can set default permissions or lock them here.
* Option C (tabcmd): Correct.
* Groups: tabcmd creategroup "GroupName" creates a local group. Add users with tabcmd addusers "GroupName" --users "user1,user2".
* Projects: tabcmd createproject -n "ProjectName" -d "Description" creates a project.
* Details: tabcmd is a command-line tool for batch operations or scripting (e.g., automating group
/project setup). It requires a server admin login (tabcmd login).
* Limitation: No AD sync via tabcmd-that's UI or REST API territory.
* Option D (REST API): Correct.
* Groups: Use the POST /api/api-version/sites/site-id/groups endpoint with a payload (e.g.,
{"group": {"name": "GroupName"}}). Supports AD import too.
* Projects: Use POST /api/api-version/sites/site-id/projects (e.g., {"project": {"name":
"ProjectName", "description": "Desc"}}).
* Details: The REST API is programmatic, ideal for integration with external systems or bulk automation. Requires authentication via a token and server/site admin rights.
* Power: Offers full control, including nested projects and custom permissions.
* Option A (tsm customize): Incorrect.
* Purpose: tsm customize modifies TSM UI branding (e.g., logos, colors) via commands like tsm customize --logo "path/to/logo.png".
* Why Wrong: It's unrelated to creating groups or projects-it's for cosmetic server configuration, not content/user management.
Why This Matters: Offering UI, CLI, and API options ensures flexibility-manual for small tasks, automation for scale-critical in enterprise deployments.
Reference: Tableau Server Documentation - "Manage Groups" (https://help.tableau.com/current/server/en-us
/groups_create.htm), "Manage Projects" (https://help.tableau.com/current/server/en-us/projects_create.htm),
"tabcmd Commands" (https://help.tableau.com/current/server/en-us/tabcmd_cmd.htm), "REST API Reference" (https://help.tableau.com/current/api/rest_api/en-us/REST/rest_api_ref.htm).

NEW QUESTION # 24
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. The UNC path to the extract's data source
• B. The status of the Backgrounder process, as shown by the tsm status -v command
• C. The Background Tasks for Extracts administrative view on the site status page
• D. Whether the project permissions are set to Locked to the project

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 # 25
What should you do to configure the view URL and enable recording for a site that has recording workbook performance metrics enabled?

• A. Type :record_performance=yes& at the end of the view URL, immediately after the session ID
• B. Type :record_performance=yes& at the end of the view URL, immediately before the session ID
• C. Delete the session ID in the URL and reload the view
• D. Click the Performance link in the toolbar at the top of the view

Answer: A

Explanation:
Tableau Server can record performance metrics for workbooks to troubleshoot slow-loading views. This feature must be enabled at the site level (via Settings > General > Allow Performance Recording). Once enabled, you can trigger recording for a specific view by modifying its URL.
The correct syntax is to append :record_performance=yes& to the view URL, immediately after the session ID. For example:
* Original
URL: http://server/#/site/my-site/views/workbook/view?:iid=1
* Modified
URL: http://server/#/site/my-site/views/workbook/view?:iid=1:record_performance=yes
&
After loading the view with this parameter, a performance recording is generated and accessible via the Performance option in the toolbar.
* Option B (Type :record_performance=yes& at the end of the view URL, immediately after the session ID): Correct. This follows Tableau's documented method for enabling performance recording.
* Option A (Click the Performance link in the toolbar): Incorrect. The Performance link appears only after recording is triggered via the URL; it's not the method to enable it.
* Option C (Type :record_performance=yes& immediately before the session ID): Incorrect. The parameter must follow the session ID (e.g., :iid=1) to function correctly.
* Option D (Delete the session ID in the URL and reload the view): Incorrect. The session ID is required for the view to load properly; removing it breaks the URL.
Reference: Tableau Server Documentation - "Record Performance of a View" (https://help.tableau.com/current
/server/en-us/perf_record.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
Which three types of data should you backup to ensure that you can restore a Tableau Server? (Choose three.)

• A. Repository data
• B. Configuration data
• C. Server secrets and Repository passwords
• D. Topology data

Answer: A,B,C

Explanation:
Backing up Tableau Server ensures recovery from failures or migrations. A full backup includes multiple data types-let's dissect this comprehensively:
* Backup Components:
* Repository Data: PostgreSQL database with metadata (users, permissions, workbooks). Backed up via tsm maintenance backup -f <filename>.tsbak.
* Configuration Data: Server settings (e.g., ports, authentication) also in the .tsbak file.
* Server Secrets: Encryption keys, internal tokens, Repository passwords-critical for restoring functionality.
* Extracts: .hyper files in File Store (optional, separate backup).
* Option A (Server secrets and Repository passwords): Correct.
* Details: Includes encryption keys (for extracts), internal tokens (process communication), and Repository credentials. Backed up separately or stored securely (e.g., tsm security export-keys).
* Why Critical: Without these, restored data may be inaccessible or services may fail.
* Option C (Configuration data): Correct.
* Details: Ports, authentication settings, process topology-part of the .tsbak file.
* Why Critical: Restores server behavior and connectivity post-recovery.
* Option D (Repository data): Correct.
* Details: Core metadata database-also in .tsbak.
* Why Critical: Without it, all content and user data is lost.
* Option B (Topology data): Incorrect.
* Details: Topology (process distribution) is part of configuration data in the .tsbak, not a separate entity. It's not distinctly backed up as "topology data." Why This Matters: A complete backup (secrets, config, repository) ensures full restoration-missing any piece risks an unusable server.
Reference: Tableau Server Documentation - "Back Up Tableau Server Data" (https://help.tableau.com/current
/server/en-us/backup_restore.htm).

NEW QUESTION # 28
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. Use the Stale Content administrative view
• B. Delete all extracts and allow them to be re-generated automatically if they are still in use
• C. Examine the extract files in ProgramData/Tableau/Tableau Server/data/tabsvc/dataengine/extract
• D. View all workbooks, and sort by the Modified date

Answer: A

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 # 29
What two Tableau Services Manager (TSM) processes continue to run when Tableau Server is stopped?
(Choose two.)

• A. VizQL Server
• B. Administration Controller
• C. Backgrounder
• D. License Manager

Answer: B,D

Explanation:
Tableau Server consists of multiple processes managed by TSM. When you stop Tableau Server (e.g., via tsm stop), most application processes halt, but some TSM-specific processes remain active to manage the server's infrastructure. Let's examine each:
* TSM Processes: These include the Administration Controller, Administration Agent, and License Manager, which handle configuration, monitoring, and licensing.
* Application Processes: These include VizQL Server, Backgrounder, Data Server, etc., which deliver Tableau's core functionality and stop when the server is stopped.
When tsm stop is executed:
* The Administration Controller (port 8850) continues running to manage TSM operations (e.g., restarts, status checks).
* The License Manager remains active to validate licenses and ensure compliance, even when the server is offline.
* Application processes like VizQL Server and Backgrounder shut down, as they're tied to user-facing services.
* Option B (License Manager): Correct. It persists to handle licensing tasks, ensuring the server can restart without license issues.
* Option D (Administration Controller): Correct. It's the core TSM process, always running to accept commands and manage the server state.
* Option A (VizQL Server): Incorrect. VizQL stops, as it renders visualizations for users-an application process tied to active server operation.
* Option C (Backgrounder): Incorrect. Backgrounder stops, as it processes background tasks (e.g., extract refreshes), which halt when the server is down.
Why This Matters: Understanding which processes persist helps administrators troubleshoot and manage server lifecycle events effectively.
Reference: Tableau Server Documentation - "TSM Processes" (https://help.tableau.com/current/server/en-us
/tsm_overview.htm#processes).

NEW QUESTION # 30
You have a server that contains 16 processor cores. What is the default number of VizQL instances configured by the installer?

• A. 0
• B. 1
• C. 2
• D. 3

Answer: D

Explanation:
The VizQL Server process in Tableau Server handles rendering visualizations and processing queries for users viewing dashboards or workbooks. During installation, Tableau Server automatically configures the number of VizQL instances based on the number of processor cores on the machine, following this rule:
Default VizQL instances = 2 per node, unless manually adjusted post-installation.
In multi-node setups, additional instances may be added based on core count, but the question specifies a single server with 16 cores.
The installer does not scale VizQL instances linearly with core count by default (e.g., it doesn't set 1 instance per 4 cores). Instead:
For a single-node installation, the default is 2 VizQL instances, regardless of core count (assuming the minimum hardware requirements are met: 8 cores, 32 GB RAM).
Administrators can later adjust this using TSM (e.g., tsm topology set-process) based on performance needs, but the question asks for the default configured by the installer.
Option A (4): Incorrect. Four instances might be configured manually for a 16-core server, but it's not the default.
Option B (6): Incorrect. Six instances exceed the default for a single node.
Option C (10): Incorrect. Ten instances are far beyond the default and would require manual configuration.
Option D (2): Correct. The installer sets 2 VizQL instances by default on a single-node installation.
Reference: Tableau Server Documentation - "Server Process Settings" (https://help.tableau.com/current/server
/en-us/processes.htm).

NEW QUESTION # 31
You attempt to delete a user who owns content on a Tableau Server. What is the result of the delete action?

• A. The user is deleted, and the user's content is reassigned to the project leader
• B. The user is deleted, and the user's content is reassigned to the server administrator
• C. The user and all of the user's content is deleted
• D. The user is switched to an Unlicensed site role and is NOT deleted

Answer: D

Explanation:
Deleting a user in Tableau Server involves handling their owned content (workbooks, data sources)-let's analyze the process:
* Deletion Rules:
* Ownership Check: Tableau prevents deletion if the user owns content to avoid orphaning it.
* Action: Instead of deleting, the user's site role is set to Unlicensed, retaining their account and content ownership.
* Resolution: An admin must reassign ownership (e.g., via Users > Actions > Change Owner) before deletion.
* Option D (User switched to Unlicensed and NOT deleted): Correct.
* Details: Attempting deletion (e.g., Users > Select User > Actions > Delete) triggers a check. If content exists, the user becomes Unlicensed-still in the system but unable to log in.
* Why: Protects data integrity-content remains accessible for reassignment.
* Option A (Deleted, content to server admin): Incorrect.
* Why: No automatic reassignment to the server admin-manual action is required first.
* Option B (Deleted, content to project leader): Incorrect.
* Why: Project leaders don't automatically inherit content-no such mechanism exists.
* Option C (User and content deleted): Incorrect.
* Why: Tableau avoids deleting content with the user-too destructive without explicit intent.
Why This Matters: This safeguard prevents accidental data loss, ensuring admins manage ownership transitions deliberately.
Reference: Tableau Server Documentation - "Delete Users" (https://help.tableau.com/current/server/en-us
/users_delete.htm).

NEW QUESTION # 32
What account should you use to run the Tableau Server installation program?

• A. A domain user account
• B. An account in the local administrator group
• C. A local user account
• D. An NT AUTHORITY\NetworkService account

Answer: B

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 # 33
Which Tableau Server process performs the role of a database for metadata?

• A. Repository
• B. File Store
• C. Data Engine
• D. Backgrounder

Answer: A

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 # 34
What event is most likely to cause problems for a Tableau Server?

• A. Running additional software on the server
• B. Configuring the server to use a static IP address
• C. Separating the Backgrounder and VizQL processes to different machines
• D. Using a non-default installation path

Answer: A

Explanation:
Tableau Server's performance and stability depend on dedicated resources and proper configuration. Running additional software on the same server is the most likely to cause problems because:
* Resource contention: Tableau Server requires significant CPU, RAM, and disk I/O. Other software (e.
g., databases, web servers) can compete for these resources, leading to slowdowns, crashes, or failed tasks.
* Port conflicts: Tableau uses specific ports (e.g., 80, 443, 8850), and other applications might interfere.
* Security risks: Additional software increases the attack surface, potentially compromising Tableau Server.
Tableau recommends running the server on dedicated hardware without unrelated applications.
* Option A (Running additional software on the server): Correct. This is a common cause of performance issues and is explicitly discouraged in Tableau's best practices.
* Option B (Separating the Backgrounder and VizQL processes to different machines): Incorrect.
This is a supported multi-node configuration that can improve performance, not cause problems, if properly set up via TSM.
* Option C (Configuring the server to use a static IP address): Incorrect. A static IP is recommended for Tableau Server to ensure consistent network access, so it's unlikely to cause issues.
* Option D (Using a non-default installation path): Incorrect. While not default, a custom path is supported (via TSM or installer options) and unlikely to cause problems if permissions and disk space are adequate.
Reference: Tableau Server Documentation - "Best Practices for Installation" (https://help.tableau.com/current
/server/en-us/install_best_practices.htm).

NEW QUESTION # 35
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 data-access caching set -r 1
• C. tsm security regenerate-internal-tokens
• D. tsm security validate-asset-keys

Answer: C

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 # 36
What should you use to set a preferred active repository?

• A. A tabcmd set command
• B. A tsm configuration set command
• C. The TSM browser client's Maintenance page
• D. The TSM browser client's Configuration Topology page

Answer: B

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 # 37
Which three data sources support Kerberos delegation with Tableau Server? (Choose three.)

• A. SAP HANA
• B. Teradata
• C. PostgreSQL
• D. SQL Server

Answer: A,B,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 # 38
Which two commands are valid and complete commands? (Choose two.)

• A. tsm maintenance restore
• B. tsm maintenance cleanup
• C. tsm maintenance backup
• D. tsm maintenance ziplogs

Answer: B,D

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 # 39
You are the server administrator of a single-node Tableau Server installation. The server hosts five schedules that each execute once a day: Weekday 3:00 PM Extract Refresh, Weekday 5:00 PM Subscription, Weekday
2:00 AM Extract Refresh, Weekday 7:00 AM Extract Refresh, and Weekday 8:00 AM Subscription. The schedules are scheduled to execute during periods when Tableau Server is least active. The busiest period for your server is immediately after the workday begins at 9:00 AM. The office of the CEO reports that every morning at 9:00 AM, they access the views in a particular workbook. The data for these views is refreshed by a task associated with the 7:00 AM schedule. The CEO reports that the data in the views is only being refreshed about 70% of the time. What should you do to attempt to resolve the CEO's problem?

• A. Set the default priority of this schedule to 50
• B. Set the priority of this task to 1
• C. Set the priority of this task to 100
• D. Set the priority for all other tasks to 50

Answer: B

Explanation:
In Tableau Server, schedules manage tasks like extract refreshes and subscriptions. Each task within a schedule has a priority value (ranging from 1 to 100, where 1 is the highest priority and 100 is the lowest).
Tasks with higher priority (lower numbers) are executed before tasks with lower priority (higher numbers) when queued by the Backgrounder process. If the Backgrounder is overloaded or delayed, lower-priority tasks may not complete on time, leading to inconsistent refreshes.
In this scenario:
The 7:00 AM Extract Refresh task is critical for the CEO's workbook, but the data is only refreshed 70% of the time by 9:00 AM.
The server has a single node, meaning a single Backgrounder process handles all tasks. With five schedules (some overlapping in the early morning), contention or delays could prevent the 7:00 AM task from completing reliably before 9:00 AM.
Option C (Set the priority of this task to 1): Correct. Setting the task priority to 1 ensures it has the highest priority among all queued tasks. This increases the likelihood that the Backgrounder executes it promptly at 7:
00 AM, completing the refresh before the CEO accesses the workbook at 9:00 AM. You can adjust task priority in the Tableau Server web interface under Schedules > Tasks > Edit Priority.
Option A (Set the default priority of this schedule to 50): Incorrect. The default priority for schedules is already 50, and this option refers to the schedule's default, not the specific task. It wouldn't address the contention issue.
Option B (Set the priority for all other tasks to 50): Incorrect. This keeps all tasks at the default priority (50), leaving the 7:00 AM task without a relative advantage. It doesn't prioritize the CEO's task.
Option D (Set the priority of this task to 100): Incorrect. Priority 100 is the lowest, which would deprioritize the task, making the refresh even less reliable.
Reference: Tableau Server Documentation - "Manage Schedules and Tasks" (https://help.tableau.com/current
/server/en-us/schedule_manage.htm).

NEW QUESTION # 40
......

Ultimate Analytics-Admn-201 Guide to Prepare Free Latest Salesforce Practice Tests Dumps: https://www.realvce.com/Analytics-Admn-201_free-dumps.html

Get Top-Rated Salesforce Analytics-Admn-201 Exam Dumps Now: https://drive.google.com/open?id=1NIqp197odmkCLdDkfvDKA9fHA_cTUPFF