[2026] Pass Salesforce Analytics-Admn-201 Exam in First Attempt Easily [Q13-Q38]

[2026] Pass Salesforce Analytics-Admn-201 Exam in First Attempt Easily

The Most Efficient Analytics-Admn-201 Pdf Dumps For Assured Success 

NEW QUESTION # 13
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 # 14
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 # 15
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 # 16
What process decides when a Repository failover is required?

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

Answer: C

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 # 17
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 # 18
You install Tableau Server on a server that has four processor cores. How many instances of each Tableau Server process are installed?

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

Answer: D

Explanation:
Tableau Server's installer configures process instances based on hardware and deployment type (single-node vs. multi-node). For a single-node installation with 4 cores, we need to consider the default process topology
. Let's break this down exhaustively:
* Key Processes:
* Gateway: Handles incoming requests (1 instance).
* Application Server (VizPortal): Manages UI and sessions (1 instance).
* VizQL Server: Renders visualizations (2 instances).
* Backgrounder: Runs extract refreshes, subscriptions (1 instance).
* Data Server: Manages data connections (1 instance).
* File Store: Stores extracts (1 instance).
* Repository: Metadata database (1 instance, active).
* Cluster Controller, Cache Server, etc.: Supporting processes (typically 1 each).
* Default Configuration:
* On a single-node install, Tableau sets 1 instance per process unless specified otherwise, except for VizQL, which defaults to 2.
* The installer doesn't scale instances linearly with cores (e.g., 4 cores # 4 instances). Post-install, TSM can adjust this (e.g., tsm topology set-process), but the question asks for the installed default.
* Minimum hardware (8 cores, 32 GB RAM) suggests higher defaults, but 4 cores still triggers a minimal setup.
* Option B (1): Correct with Caveat.
* Most processes (e.g., Backgrounder, Gateway, Data Server) default to 1 instance on install, regardless of 4 cores.
* VizQL defaults to 2, but the question's phrasing ("each process") implies a general rule.
Historically (and per docs), 1 is the baseline for most, with VizQL as the exception.
* Interpretation: Assuming "each" means the typical case, 1 fits most processes on a 4-core single- node setup.
* Option A (2): Incorrect. Only VizQL defaults to 2; others don't.
* Option C (8): Incorrect. Far exceeds defaults-8 cores might justify more, but not 4.
* Option D (4): Incorrect. Not tied to core count by default; manual config would be needed.
Why This Matters: Understanding defaults aids capacity planning-4 cores is below production minimum (8), so performance tuning may be needed post-install.
Reference: Tableau Server Documentation - "Server Process Settings" (https://help.tableau.com/current/server
/en-us/processes.htm).

NEW QUESTION # 19
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 # 20
Which three types of authentications can you use to implement single-sign-on (SSO) authentication to Tableau Server? (Choose three.)

• A. Local Authentication
• B. Security Assertion Markup Language (SAML)
• C. OpenID Connect
• D. Kerberos with Active Directory

Answer: B,C,D

Explanation:
Single Sign-On (SSO) allows users to authenticate once (e.g., via a corporate identity provider) and access Tableau Server without re-entering credentials. Tableau Server supports several SSO methods:
* OpenID Connect (OIDC): An OAuth 2.0-based protocol for SSO, configured via Tableau's SAML settings with an OIDC-compatible IdP (e.g., Google, Okta).
* Kerberos with Active Directory: A ticket-based SSO protocol, widely used in Windows environments with AD integration.
* SAML: A flexible SSO standard using XML assertions, supporting various IdPs (e.g., ADFS, PingFederate).
Let's evaluate:
* Option A (OpenID Connect): Correct. OIDC is an SSO method, implemented as a SAML variant in Tableau Server, enabling seamless login.
* Option C (Kerberos with Active Directory): Correct. Kerberos provides SSO in AD environments, delegating authentication to the domain controller.
* Option D (Security Assertion Markup Language - SAML): Correct. SAML is a core SSO method in Tableau, widely adopted for enterprise integrations.
* Option B (Local Authentication): Incorrect. Local Authentication uses Tableau's internal user database, requiring manual credential entry-no SSO support.
Why This Matters: SSO enhances user experience and security by leveraging existing identity systems, reducing password fatigue.
Reference: Tableau Server Documentation - "Authentication" (https://help.tableau.com/current/server/en-us
/auth_overview.htm).

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

Answer: A

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

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

Answer: A

Explanation:
Tableau Server uses a PostgreSQL database as its repository to store metadata, user information, and permissions. In a high-availability (HA) setup with multiple nodes, there are typically two repository instances: one active and one passive. The "preferred active repository" refers to designating which repository instance should take priority as the active one. This is managed through Tableau Services Manager (TSM).
The correct method to set the preferred active repository is by using the tsm configuration set command.
Specifically, you would use a command like:
tsm configuration set -k pgsql.preferred_host -v <hostname>
This command allows an administrator to specify the preferred host for the active repository, ensuring control over which node takes precedence in an HA environment.
Option B (tabcmd set command) is incorrect because tabcmd is a command-line utility primarily used for administrative tasks like managing users, groups, and content (e.g., publishing workbooks), not for configuring server topology or repository settings.
Option C (TSM browser client's Maintenance page) is incorrect because the Maintenance page in the TSM web interface is used for tasks like backups, restores, and cleanup, but it does not provide an option to set the preferred active repository.
Option D (TSM browser client's Configuration Topology page) is partially relevant since the Topology page displays the current configuration of services across nodes, including the repository. However, it does not allow direct modification of the preferred active repository; this must be done via the tsm command line.
Reference: Tableau Server Documentation - "Configure Tableau Server Repository" (https://help.tableau.com
/current/server/en-us/repository.htm) and "TSM Command Line Reference" (https://help.tableau.com/current
/server/en-us/cli_configuration_set.htm).

NEW QUESTION # 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
Which two statements are advantages of published data sources in comparison to embedded data sources?
(Choose two.)

• A. Storage space is conserved and resource usage during data refreshes is optimized
• B. Data is protected so that it is only available in one workbook
• C. Drivers are automatically installed on each client's machine
• D. Centralized data management is easier

Answer: A,D

Explanation:
In Tableau, data sources can be embedded (stored within a workbook) or published (stored separately on Tableau Server). Let's define these and analyze the advantages:
* Embedded Data Source: The connection details and any extract are bundled in the .twb or .twbx file.
Each workbook manages its own copy.
* Published Data Source: The connection or extract is hosted on Tableau Server, reusable across multiple workbooks.
Now, let's evaluate the options:
* Option C (Centralized data management is easier): Correct. Published data sources allow:
* Single source of truth: One data source can serve multiple workbooks, ensuring consistency.
* Unified updates: Refresh schedules, permissions, and metadata (e.g., calculated fields) are managed in one place via the Server UI.
* Governance: Administrators can control access and monitor usage centrally.In contrast, embedded data sources require individual updates per workbook, leading to duplication and management overhead.
* Option D (Storage space is conserved and resource usage during data refreshes is optimized):
Correct. With published data sources:
* Storage: A single extract on the Server (e.g., a .hyper file) is shared across workbooks, avoiding redundant copies stored in each embedded workbook.
* Refreshes: One refresh job updates the shared extract, reducing CPU and memory usage compared to multiple refreshes for duplicate embedded extracts.Embedded data sources replicate extracts, increasing disk space and refresh load.
* Option A (Data is protected so that it is only available in one workbook): Incorrect. This describes embedded data sources, not published ones. Published data sources are shared, not restricted to one workbook-permissions control access, not exclusivity.
* Option B (Drivers are automatically installed on each client's machine): Incorrect. Drivers (e.g., for SQL Server, PostgreSQL) must be installed on the Server hosting the published data source, not client machines. This is unrelated to the published vs. embedded distinction.
Why This Matters: Published data sources enhance scalability and efficiency in enterprise deployments, making them a cornerstone of Tableau Server's data strategy.
Reference: Tableau Server Documentation - "Published Data Sources" (https://help.tableau.com/current/server
/en-us/datasource_publish.htm).

NEW QUESTION # 27
What file format should you use to register Tableau Server from the command line?

• A. YML
• B. XML
• C. JSON
• D. HTTP

Answer: C

Explanation:
Registering Tableau Server from the command line involves providing configuration details (e.g., identity store, license) via the tsm register command. Let's explore this fully:
* Registration Process:
* Run during initial setup or to update settings (e.g., after changing AD/LDAP config).
* Uses a configuration file to pass parameters to TSM.
* Command: tsm register --file <path-to-file>.
* File Format:
* Tableau Server uses JSON for configuration files in TSM commands like tsm register.
* Example:
json
CollapseWrapCopy
{
"identityStore": {
"type": "local",
"domain": "example.com"
}
}
* JSON is structured, machine-readable, and aligns with Tableau's modern CLI design.
* Option C (JSON): Correct.
* Official format for tsm register, per documentation and practical use.
* Option A (YML): Incorrect.
* While tabsvc.yml exists internally, it's not for registration-tsm register uses JSON.
* Option B (XML): Incorrect.
* Older Tableau configs used XML (e.g., workgroup.yml pre-TSM), but TSM standardized on JSON.
* Option D (HTTP): Incorrect.
* HTTP is a protocol, not a file format-irrelevant here.
Why This Matters: Correct file format ensures seamless registration, avoiding CLI errors in setup or migrations.
Reference: Tableau Server Documentation - "tsm register" (https://help.tableau.com/current/server/en-us
/cli_register.htm).

NEW QUESTION # 28
Which three types of data should you backup to ensure that you can restore a Tableau Server? (Choose three.)

• A. Server secrets and Repository passwords
• B. Repository data
• C. Configuration data
• 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 # 29
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 # 30
You activate the same Tableau Server product key on three installations for Dev, Test, and Production. You plan to move the Test environment to new hardware. What is the recommended workflow for managing the product key?

• A. Install and activate Tableau Server on the new hardware and keep the existing Test environment as a backup
• B. Install and activate Tableau Server on the new hardware, and then run the following script in the old environment: tableau-server-obliterate.cmd -y -y -y
• C. Install and activate Tableau Server on the new hardware, and then deactivate it on the old hardware
• D. Deactivate the product key on the existing Test environment, and then install and activate Tableau Server on the new hardware

Answer: D

Explanation:
Tableau Server's licensing ties product keys to specific machines. Moving an environment requires managing activations to stay compliant. Let's break this down:
* Licensing Rules:
* A product key can be activated on multiple machines (e.g., Dev, Test, Prod), but only up to the licensed limit (typically 3 for such setups).
* Deactivation frees the key for reuse elsewhere.
* Recommended Workflow:
* Deactivate first: Use tsm licenses deactivate on the old Test machine to release the key.
* Then activate: Install on the new hardware and activate with tsm licenses activate -k <key>.
* Why: Ensures compliance and avoids activation conflicts (e.g., exceeding the key's limit).
* Option B (Deactivate on Test, then install/activate on new hardware): Correct.
* Steps:
* On old Test: tsm licenses deactivate.
* Install Tableau Server on new hardware.
* On new Test: tsm licenses activate -k <key>.
* Benefit: Clean, compliant transfer-preserves license integrity.
* Option A (Activate new, then deactivate old): Incorrect.
* Risk: If the key's limit is reached (e.g., 3 activations), the new activation fails until deactivation occurs. Order matters.
* Option C (Activate new, keep old as backup): Incorrect.
* Issue: Exceeds license limit (4 activations) and risks non-compliance. Backup requires deactivation or a separate key.
* Option D (Activate new, obliterate old): Incorrect.
* Details: tableau-server-obliterate.cmd wipes the entire install (data, config)-overkill and doesn't formally deactivate the key via TSM, potentially leaving licensing inconsistent.
Why This Matters: Proper license management prevents activation errors and ensures legal use across environments.
Reference: Tableau Server Documentation - "Manage Product Keys" (https://help.tableau.com/current/server
/en-us/license_manage.htm).

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

• A. You can change the name of a group during import, although this will not change the group's name in Active Directory
• B. 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
• C. Importing a group from Active Directory requires a .csv file that lists user IDs
• D. New users created as a result of importing a group are assigned the site role specified during the import

Answer: D

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.
* Option A (Existing users' roles change to match import): Incorrect.
* Why: Existing roles persist unless lower than the minimum-e.g., Viewer stays Viewer if import sets Explorer, but Unlicensed upgrades. Not a full overwrite.
* Option B (Requires a .csv file): Incorrect.
* Why: AD import uses live sync via LDAP-no .csv needed (that's for local auth imports).
* Option C (Change group name during import): Incorrect.
* Why: The AD group name is fixed-you can't rename it in Tableau during sync (it mirrors AD).
Post-import renaming is possible but not part of the process.
Why This Matters: Accurate AD sync ensures seamless user management-missteps can disrupt access or licensing.
Reference: Tableau Server Documentation - "Synchronize Active Directory Groups" (https://help.tableau.com
/current/server/en-us/groups_sync.htm).

NEW QUESTION # 35
Which three methods should an administrator use to create a Tableau Server group or project? (Choose three.)

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

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 # 36
......

We offers you the latest free online Analytics-Admn-201 dumps to practice: https://www.passcollection.com/Analytics-Admn-201_real-exams.html

Salesforce Analytics-Admn-201 Real Exam Questions Guaranteed Updated Dump: https://drive.google.com/open?id=1D1K-KKQCzWSPU-tzs14AsxoAq5FDopqs