Analytics-Admn-201 Exam Questions - Real & Updated Questions PDF [Q43-Q68]

Analytics-Admn-201 Exam Questions - Real & Updated Questions PDF

Pass Guaranteed Quiz 2026 Realistic Verified Free Salesforce

NEW QUESTION # 43
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. Instruct the user to add tags to the workbook
B. Run the tsm maintenance reindex-search command
C. Instruct the user to log out, and then log back in
D. Instruct the user to re-publish the workbook with keywords

Answer: B

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.

NEW QUESTION # 44
Which authentication method allows users to sign in to Tableau Server using credentials from an external identity provider via SAML?

A. Single Sign-On (SSO) via SAML
B. Local authentication
C. Trusted authentication
D. Kerberos delegation

Answer: A

Explanation:
SAML-based SSO integrates Tableau Server with an external Identity Provider (IdP) so users authenticate once and gain access without separate Tableau credentials. Local authentication uses Tableau's own credential store; trusted authentication is used for embedding without prompting for login; Kerberos delegation supports single sign-on to underlying data sources, not initial server login.

NEW QUESTION # 45
What event is most likely to cause problems for a Tableau Server?

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

Answer: C

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 # 46
Your deployment of Tableau Server uses Active Directory authentication. What statement correctly describes the process of importing a group from Active Directory?

A. Importing a group from Active Directory requires a .csv file that lists user IDs
B. New users created as a result of importing a group are assigned the site role specified during the import
C. You can change the name of a group during import, although this will not change the group's name in Active Directory
D. If an imported group contains any users that have Tableau Server accounts, their site role will be changed to match the site role specified during the import

Answer: B

Explanation:
Importing an AD group into Tableau Server syncs user management--let's analyze the process and options:
AD Group Import Process:
How: In the UI (Users > Groups > Add Group > Active Directory), enter the AD group name, set a site role, and sync.
Behavior:
Existing Users: If a user is already in Tableau Server, their site role remains unchanged unless manually adjusted--sync applies the minimum role only if it upgrades access. New Users: Added to Tableau with the site role specified during import.
Config: Requires AD authentication enabled in TSM.
Option D (New users created are assigned the site role specified during import): Correct. Details:
When importing (e.g., "SalesTeam" group, site role: Explorer):
New users get Explorer.
Existing users keep their role unless it's below Explorer (e.g., Unlicensed Explorer).
Why: Ensures consistent onboarding--new users align with the group's intended access.

NEW QUESTION # 47
What statement correctly describes locking permissions to a project?

A. Content permissions are locked to a project by default
B. You can lock permissions to a project by setting the appropriate Project permission role
C. You can lock permissions to a project by changing Customizable to Locked
D. Locking permissions to projects must be enabled on the Tableau Server Settings page

Answer: C

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 # 48
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: C

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 D (2): Correct. The installer sets 2 VizQL instances by default on a single-node installation.

NEW QUESTION # 49
What two Tableau Services Manager (TSM) processes continue to run when Tableau Server is stopped? (Choose two.)

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

Answer: B,C

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.

NEW QUESTION # 50
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 switched to an Unlicensed site role and is NOT deleted
B. The user is deleted, and the user's content is reassigned to the server administrator
C. The user is deleted, and the user's content is reassigned to the project leader
D. The user and all of the user's content is deleted

Answer: A

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 # 51
Which two options can be configured by a server administrator per site? (Choose two.)

A. Ability to embed credentials
B. Limitation on number of users
C. Limitation on storage space
D. Language and locale

Answer: C,D

Explanation:
Tableau Server supports multi-tenancy via sites, each with customizable settings managed by server or site administrators. Let's analyze what's configurable per site:
Site Settings: Found in the web UI under Site > Settings > General. Server admins can override site admin settings.
Option B (Limitation on storage space): Correct.
Details: Server admins can set a storage quota per site (e.g., 100 GB) to cap disk usage for extracts and workbooks.
How: In TSM or site settings (if enabled)--e.g., tsm configuration set -k site.storage.quota -v
100000. Impact: Prevents one site from monopolizing resources in multi-site deployments.
Option D (Language and locale): Correct.
Details: Each site can set its language (e.g., English, French) and locale (e.g., date/number formats). How: Site settings UI--e.g., "Language: French, Locale: France." Impact: Tailors the user experience per site's audience.

NEW QUESTION # 52
To which site role can you associate the Viewer user-based license level?

A. Creator
B. Explorer (can publish)
C. Viewer
D. Explorer

Answer: C

Explanation:
Tableau Server uses a role-based licensing model with three primary license levels: Creator, Explorer, and Viewer. Each license level corresponds to specific site roles that define what users can do on the server.
Viewer License: This is the most restrictive license, allowing users to view and interact with published content (e.g., dashboards and visualizations) but not to create or publish new content.
Site Role: The Viewer license can only be associated with the Viewer site role. This role restricts users to viewing capabilities, aligning with the license's purpose.
Option C (Viewer): Correct. The Viewer site role matches the Viewer license level perfectly.

NEW QUESTION # 53
What Tableau Server authentication method should you configure to use OpenID Connect?

A. SAML
B. Kerberos
C. Local Authentication
D. Active Directory

Answer: A

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 # 54
What type of information is stored in the tsm maintenance backup -f <filename>.tsbak command?

A. Topology data
B. Notification settings
C. SMTP server settings
D. Repository data

Answer: D

NEW QUESTION # 55
What does locking permissions on a project accomplish?

A. It enforces the project's default permission rules on all content within it, preventing individual overrides
B. It prevents any user from viewing content in the project
C. It disables publishing to the project entirely
D. It hides the project from the site's navigation

Answer: A

Explanation:
Locking a project's permissions ensures all content inside (including in sub-projects) uses the project-level default permission rules, and publishers/owners cannot set custom permissions on individual items - useful for standardized governance.

NEW QUESTION # 56
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. 4-Core CPU (2.0 GHz or higher), 64 GB RAM, 50 GB free disk space
D. 2-Core CPU (1.8 GHz or higher), 8 GB RAM, 15 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 # 57
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 an error message instructing you that you are unable to publish the workbook to a newer version of Tableau Server
B. You will see a warning message instructing you that the workbook will be upgraded to a new version
C. You will successfully publish the visualization without any errors or warnings
D. You will see a warning message instructing you that embedded .tde extracts will be upgraded to .hyper

Answer: D

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 # 58
A site administrator wants to prevent Explorer-level users from downloading workbooks. Which permission capability should be denied?

A. Filter
B. View
C. Download/Save a Copy
D. Web Edit

Answer: C

Explanation:
The "Download/Save a Copy" capability specifically governs whether a user can export or save a local copy of a workbook. Denying it for Explorers restricts them to viewing/interacting without extracting the file, while View, Web Edit, and Filter control different interaction types.

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

Answer: D

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.

NEW QUESTION # 60
Which two operating systems are supported for a Tableau Server installation? (Choose two.)

A. Windows 10
B. Windows 7
C. Windows Server 2019
D. Windows Server 2016

Answer: C,D

Explanation:
Tableau Server is designed for production environments and is supported only on server-class operating systems, not desktop operating systems. As of the latest documentation (aligned with knowledge up to March
21, 2025), the supported operating systems for Tableau Server on Windows are:
Windows Server 2016
Windows Server 2019
Windows Server 2022 (added in later versions, but relevant as of 2025).
Desktop operating systems like Windows 7 or Windows 10 are not supported for production installations due to stability, security, and performance requirements.
Option A (Windows 7): Incorrect. Windows 7 is a desktop OS and is not supported for Tableau Server. It's also end-of-life as of January 2020.
Option B (Windows 10): Incorrect. Windows 10 is a desktop OS and not supported for production Tableau Server deployments, though it may be used for testing in non-production scenarios.
Option C (Windows Server 2019): Correct. This is a supported server OS for Tableau Server.
Option D (Windows Server 2016): Correct. This is also a supported server OS for Tableau Server.
Reference: Tableau Server Documentation - "System Requirements for Tableau Server" (https://help.tableau.
com/current/server/en-us/requirements.htm).

NEW QUESTION # 61
What event is most likely to cause problems for a Tableau Server?

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

Answer: C

NEW QUESTION # 62
Which command enables an administrator to view the current values of all TSM configuration keys?

A. tsm configuration list
B. tsm configuration get -k all
C. tsm settings show
D. tsm configuration export

Answer: A

Explanation:
tsm configuration list outputs all currently configured keys and their values. tsm configuration get - k requires a specific key name (not "all" as a wildcard), and "tsm settings show" is not a valid command.

NEW QUESTION # 63
What should you use to set a preferred active repository?

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

Answer: D

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.

NEW QUESTION # 64
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 priority of this task to 1
B. Set the priority of this task to 100
C. Set the priority for all other tasks to 50
D. Set the default priority of this schedule to 50

Answer: A

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.

NEW QUESTION # 65
Which license type must be assigned to a user who needs to build new workbooks and publish data sources?

A. Unlicensed
B. Creator
C. Viewer
D. Explorer

Answer: B

Explanation:
The Creator license is required for authoring new content in Tableau Desktop or Tableau Prep and publishing workbooks/data sources to Server. Explorer licenses allow editing of existing published content but not full authoring/publishing of new data sources; Viewer only allows consumption.

NEW QUESTION # 66
What process decides when a Repository failover is required?

A. Cluster Controller
B. Coordination Service
C. Gateway
D. Backgrounder

Answer: A

Explanation:
In a high-availability (HA) Tableau Server setup, the Repository (PostgreSQL) has an active and passive instance. Failover occurs if the active Repository fails. Let's dive into the process:
* HA Setup:
* Two Repository instances across nodes (active/passive).
* Failover switches to the passive instance if the active one becomes unavailable (e.g., crash, network issue).
* Cluster Controller:
* Role: Monitors all processes (e.g., Repository, File Store) across nodes, detecting failures via heartbeats and status checks.
* Failover Decision: If the active Repository stops responding, Cluster Controller initiates failover, promoting the passive instance to active.
* Coordination: Works with Coordination Service (ZooKeeper) to update topology but makes the initial detection call.
* Option A (Cluster Controller): Correct.
* Why: It's the watchdog process, constantly monitoring Repository health and triggering failover when needed.
* Option B (Coordination Service): Incorrect.
* Role: ZooKeeper maintains cluster state and coordinates topology updates post-failover, but doesn't detect the failure-Cluster Controller does.
* Option C (Gateway): Incorrect.
* Role: Routes client requests-unrelated to internal process monitoring or failover.
* Option D (Backgrounder): Incorrect.
* Role: Executes background tasks-no involvement in Repository failover decisions.
Why This Matters: Understanding failover ensures HA reliability-Cluster Controller is the linchpin for resilience.
Reference: Tableau Server Documentation - "High Availability" (https://help.tableau.com/current/server/en-us
/ha.htm).

NEW QUESTION # 67
An administrator needs to migrate Tableau Server from one physical datacenter to another while preserving all content, users, and settings. What is the recommended high-level approach?

A. Export TSM settings, take a full .tsbak backup, install Tableau Server fresh at the new location, import settings, then restore the backup
B. Simply copy the PostgreSQL database files to the new server
C. Manually re-publish each workbook one at a time
D. Use tabcmd to copy each site individually

Answer: A

Explanation:
Full server migration follows Tableau's documented disaster-recovery pattern: exporting configuration/topology settings, backing up the repository and file store with tsm maintenance backup, installing Server fresh on the new hardware, importing settings, and restoring the backup
-- preserving all sites, users, content, and permissions in one operation.

NEW QUESTION # 68
......

Get to the Top with Analytics-Admn-201 Practice Exam Questions: https://www.prep4sureguide.com/Analytics-Admn-201-prep4sure-exam-guide.html

Free Salesforce Administrator Analytics-Admn-201 Ultimate Study Guide: https://drive.google.com/open?id=1UadLGR_osw2ShI13ukHkT0wcO5VU-0H8

Analytics-Admn-201 Exam Questions - Real & Updated Questions PDF [Q43-Q68]

Related Articles

Contact Us