• Home
  • Blogs
  • Feb 22, 2026 PASS Salesforce Analytics-Admn-201 EXAM WITH UPDATED DUMPS [Q34-Q50]

Feb 22, 2026 PASS Salesforce Analytics-Admn-201 EXAM WITH UPDATED DUMPS [Q34-Q50]

Share

Feb 22, 2026 PASS Salesforce Analytics-Admn-201 EXAM WITH UPDATED DUMPS

Analytics-Admn-201 Questions PDF [2026] Use Valid New dump to Clear Exam

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

Answer: C

Explanation:
Abandoned workbooks-those no longer actively used-can clutter Tableau Server and consume resources (e.
g., disk space for extracts). Identifying them efficiently requires leveraging built-in administrative tools rather than manual or destructive methods. Let's explore this in depth:
* Tableau Server Admin Views: Tableau provides pre-built administrative views to monitor server health, usage, and content. The Stale Content view, accessible under Server > Status > Administrative Views, is specifically designed to identify content (workbooks, data sources) that hasn' t been viewed or modified recently. It shows:
* Content name, owner, and project.
* Last viewed date and last modified date.
* View count over a period.This view uses Repository data to track usage metrics, making it ideal for spotting abandoned workbooks.
* Option A (Use the Stale Content administrative view): Correct. This is the most efficient and non- invasive method. You can filter by last viewed date (e.g., >30 days ago) to identify workbooks with large extracts that users have stopped accessing. From there, you can contact owners or delete the content if policy allows. It's a server administrator's go-to tool for content management.
* Option B (Examine extract files in ProgramData/.../extract): Incorrect and impractical. The ProgramData/Tableau/Tableau Server/data/tabsvc/dataengine/extract directory stores .hyper extract files, but:
* File names are cryptic (e.g., GUIDs), not tied directly to workbook names.
* It doesn't indicate usage or abandonment-only file presence and size.
* Manual inspection is time-consuming and error-prone compared to the Stale Content view.
* Option C (Delete all extracts and allow them to be re-generated): Incorrect and risky. Deleting extracts (e.g., via tsm maintenance cleanup) removes them without identifying usage. Regeneration only occurs if a schedule or user triggers it, potentially disrupting active users and losing historical data unnecessarily.
* Option D (View all workbooks, and sort by the Modified date): Partially effective but inefficient. In the Tableau Server UI (e.g., under Content > Workbooks), you can sort by "Last Modified," but:
* It doesn't show viewership (a workbook might be modified recently but unused).
* It's manual and doesn't scale for large deployments compared to the Stale Content view.
Why This Matters: The Stale Content view leverages Tableau's metadata to provide actionable insights, saving time and reducing risk compared to manual or destructive alternatives. It's part of Tableau's governance toolkit.
Reference: Tableau Server Documentation - "Administrative Views" (https://help.tableau.com/current/server
/en-us/adminview_stale_content.htm).


NEW QUESTION # 35
You need to ensure that Tableau Server requires the setup of a new administrator account the next time you attempt to log in. What should you do?

  • A. Edit tabsvc.yml
  • B. Run the tsm reset command
  • C. Run the tsm register command
  • D. Reinstall Tableau Server

Answer: B

Explanation:
To force Tableau Server to require the setup of a new administrator account (e.g., resetting the server to an initial setup state), the tsm reset command is the appropriate tool. This command resets Tableau Server's administrative configuration, including the TSM administrator account, while preserving content like workbooks and data sources.
Option B (Run the tsm reset command): Correct. Running tsm reset clears the current TSM administrator credentials and configuration settings. The next time you access TSM (e.g., via the web interface or CLI), it prompts you to set up a new administrator account, mimicking the initial setup process. Command: tsm reset -- username <new-username> --password <new-password>.
Option A (Edit tabsvc.yml): Incorrect. The tabsvc.yml file contains service configuration data, but manually editing it is not supported or recommended for resetting the administrator account. It could also corrupt the installation.
Option C (Run the tsm register command): Incorrect. The tsm register command is used to register Tableau Server with a new product key or identity store, not to reset the administrator account.
Option D (Reinstall Tableau Server): Incorrect. Reinstallation wipes the entire server, including content, and is overkill for this task. The tsm reset command achieves the goal without data loss.
Reference: Tableau Server Documentation - "TSM Reset Command" (https://help.tableau.com/current/server
/en-us/cli_reset.htm).


NEW QUESTION # 36
What are two intervals when Tableau Server verifies if data conditions for data-driven alerts are true? (Choose two.)

  • A. Every 60 minutes
  • B. Whenever a new extract is published
  • C. Whenever extracts in the related workbook are refreshed
  • D. Every 10 minutes

Answer: A,C

Explanation:
Data-driven alerts notify users when data meets conditions (e.g., sales > $10K). Let's examine when Tableau checks these:
* Alert Mechanics:
* Enabled per site (Settings > General > Data-Driven Alerts).
* Backgrounder evaluates conditions against extract data.
* Check Intervals: Configurable via tsm configuration set -k dataAlerts.checkIntervalInMinutes (default: 60 minutes).
* Refresh Trigger: Also checks post-extract refresh for immediate updates.
* Option A (Every 60 minutes): Correct.
* Details: Default interval-Backgrounder polls every hour to evaluate alert conditions.
* Config: Adjustable (e.g., -v 30 for 30 minutes).
* Option D (Whenever extracts in the related workbook are refreshed): Correct.
* Details: An extract refresh updates the data, triggering an immediate alert check to catch changes promptly.
* Why: Ensures timely notifications without waiting for the next poll.
* Option B (Every 10 minutes): Incorrect.
* Why: Not the default-possible via config, but not standard.
* Option C (Whenever a new extract is published): Incorrect.
* Why: Publishing creates the extract; alerts trigger on refreshes or polling, not initial publication.
Why This Matters: Timing affects alert responsiveness-balancing frequency and server load is key.
Reference: Tableau Server Documentation - "Data-Driven Alerts" (https://help.tableau.com/current/server/en- us/data_alerts.htm).


NEW QUESTION # 37
What should you do to disable table recommendations for popular data sources and tables to users?

  • A. Use the command: tsm configuration set -k recommendations.enabled -v false
  • B. Disable the option using the server Settings page
  • C. Disable the option using the site Settings page
  • D. Publish data sources only to projects with permissions locked to the project

Answer: C

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 # 38
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 embedded .tde extracts will be upgraded to .hyper
  • C. You will see a warning message instructing you that the workbook will be upgraded to a new version
  • D. You will successfully publish the visualization without any errors or warnings

Answer: B

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

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

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 # 40
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 # 41
A user reports that a newly-published workbook runs slowly. What should you ask the user first to investigate the problem?

  • A. Did you enable caching on the workbook?
  • B. Does the workbook always run slowly or does performance vary?
  • C. Does it run any faster in Tableau Desktop?
  • D. How many times have you opened the workbook in Tableau Server?

Answer: C

Explanation:
When a user reports slow performance for a newly-published workbook on Tableau Server, troubleshooting requires isolating the cause-e.g., data source issues, server load, workbook design, or caching. The first question should establish a baseline to narrow the scope. Let's analyze this step-by-step with depth:
* Performance Context:
* A workbook's speed depends on:
* Data Source: Query complexity, size, network latency (e.g., database vs. extract).
* Workbook Design: Filters, calculations, dashboard complexity.
* Server Resources: VizQL rendering, Backgrounder load, caching.
* "Newly-published" implies it's not yet optimized or cached on the server.
* Option A (Does it run any faster in Tableau Desktop?): Correct.
* Why First: Comparing Desktop vs. Server performance is the most foundational diagnostic step:
* Desktop Baseline: If it's slow in Desktop (local machine), the issue likely lies in the workbook (e.g., complex queries, large data) or data source (e.g., slow database)-not Server-specific.
* Server Difference: If it's fast in Desktop but slow on Server, the problem could be server- side (e.g., resource contention, network latency to the data source from Server).
* Practical Next Steps:
* Slow in Desktop: Optimize workbook (e.g., simplify calcs, use extracts).
* Fast in Desktop: Check Server (e.g., caching, VizQL load).
* Why Critical: Establishes whether the issue is inherent to the workbook/data or introduced by Server-guides all further investigation.
* Option B (Does the workbook always run slowly or does performance vary?): Useful but secondary.
* Why Not First: Variability (e.g., slow at peak times) points to server load, but without a Desktop baseline, you can't rule out workbook design. It's a follow-up question after A.
* Detail: Variability might suggest caching or concurrent user impact, but it assumes Server-side causation prematurely.
* Option C (How many times have you opened the workbook in Tableau Server?): Less relevant initially.
* Why Not First: Frequency of access might affect caching (first load is slower, subsequent loads faster), but it's too specific and doesn't isolate Desktop vs. Server. It's a niche follow-up.
* Option D (Did you enable caching on the workbook?): Misleading and incorrect.
* Why Not First: Caching is server-managed (e.g., VizQL cache settings via tsm data-access caching set), not a user-toggle per workbook. Users don't "enable" it-admins do. Plus, it's premature without a baseline.
Why This Matters: Starting with Desktop performance cuts through assumptions, pinpointing whether the root cause is client-side (workbook/data) or server-side-essential for efficient resolution in production.
Reference: Tableau Server Documentation - "Troubleshoot Performance" (https://help.tableau.com/current
/server/en-us/troubleshoot_performance.htm).


NEW QUESTION # 42
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. Kerberos with Active Directory
  • D. OpenID Connect

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 # 43
What should you do to ensure that server tasks associated with a particular schedule run one-at-a-time?

  • A. Set Default priority to 0
  • B. Set Execution to Serial
  • C. Set Frequency to Hourly
  • D. Set Execution to Parallel

Answer: B

Explanation:
In Tableau Server, schedules manage tasks such as extract refreshes and subscriptions. The execution mode of a schedule determines how tasks within that schedule are processed by the Backgrounder process:
* Parallel: Tasks run simultaneously (up to the Backgrounder's capacity), which is the default setting.
* Serial: Tasks run one-at-a-time in sequence, ensuring that one task completes before the next begins.
To ensure tasks associated with a particular schedule run one-at-a-time, you must configure the schedule's execution mode to Serial. This is done in the Tableau Server web interface:
* Go to Schedules.
* Select the schedule, click Actions > Edit Schedule.
* Under Execution, choose Serial instead of Parallel.
* Option A (Set Execution to Serial): Correct. This directly addresses the requirement by forcing tasks to execute sequentially.
* Option B (Set Default priority to 0): Incorrect. Priority (1-100) determines the order of task execution across all schedules, not whether tasks run one-at-a-time within a single schedule. Also, 0 is not a valid priority value (minimum is 1).
* Option C (Set Frequency to Hourly): Incorrect. Frequency (e.g., hourly, daily) controls when the schedule runs, not how tasks within it are executed.
* Option D (Set Execution to Parallel): Incorrect. Parallel execution allows tasks to run simultaneously, which contradicts the requirement.
Reference: Tableau Server Documentation - "Create or Modify a Schedule" (https://help.tableau.com/current
/server/en-us/schedule_manage_create.htm).


NEW QUESTION # 44
You have an installation of Tableau Server and a site that are configured to use default settings. What should you do to ensure that the users on the site can set up data-driven alerts?

  • A. Change the data-driven alerts setting on the new site's Settings page
  • B. Enable data-driven alerts on the Tableau Services Manager Configuration page
  • C. Run the tsm configuration set -k dataAlerts.checkIntervalInMinutes -v 60 command
  • D. No action is necessary: the default settings enable data-driven alerts for the site

Answer: A

Explanation:
Data-driven alerts in Tableau Server allow users to receive notifications when data in a view meets certain conditions (e.g., a sales metric exceeds a threshold). By default, this feature is disabled for a site unless explicitly enabled by an administrator.
Option C (Change the data-driven alerts setting on the new site's Settings page): This is the correct answer. In the Tableau Server web interface, a site administrator can navigate to the site's Settings > General page and enable the option "Let users create data-driven alerts." This must be done manually because the default setting for a new site is disabled. Once enabled, users with appropriate permissions (e.g., Viewer, Explorer, or Creator roles) can create alerts on views they have access to.
Option A (Enable data-driven alerts on the TSM Configuration page): This is incorrect because the TSM Configuration page (accessed via the TSM web UI or CLI) manages server-wide settings like ports, authentication, and processes, not site-specific features like data-driven alerts.
Option B (Run the tsm configuration set -k dataAlerts.checkIntervalInMinutes -v 60 command): This is incorrect. The dataAlerts.checkIntervalInMinutes key controls how frequently Tableau Server checks alert conditions (default is 60 minutes), but it does not enable the feature itself. The feature must first be turned on at the site level.
Option D (No action is necessary): This is incorrect because the default setting for data-driven alerts is off for new sites, requiring explicit action to enable it.
Reference: Tableau Server Documentation - "Configure Data-Driven Alerts" (https://help.tableau.com/current
/server/en-us/data_alerts.htm).


NEW QUESTION # 45
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: B

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 # 46
What process enables you to access Tableau Services Manager (TSM) over HTTPS?

  • A. Coordination Service
  • B. Administration Controller
  • C. License Manager
  • D. Administration Agent

Answer: B

Explanation:
TSM is Tableau Server's management layer, accessible via CLI or web UI (port 8850). HTTPS secures this access-let's identify the responsible process:
* TSM Architecture:
* Administration Controller: Core TSM process, running on the initial node, handling configuration, UI, and CLI commands.
* HTTPS: Enabled by default on port 8850 with a self-signed certificate (configurable to custom certs).
* Option B (Administration Controller): Correct.
* Details: Hosts the TSM web UI (https://<server>:8850) and processes CLI requests. It manages the HTTPS listener, serving the interface securely.
* Why: It's the central hub for TSM operations, including secure access.
* Option A (License Manager): Incorrect.
* Why: Validates licenses, not responsible for HTTPS or UI access.
* Option C (Administration Agent): Incorrect.
* Why: Runs on additional nodes in multi-node setups to relay commands to the Controller-no direct HTTPS role.
* Option D (Coordination Service): Incorrect.
* Why: ZooKeeper manages cluster state, not TSM's web interface or HTTPS.
Why This Matters: Secure TSM access protects server administration-Administration Controller is the linchpin.
Reference: Tableau Server Documentation - "TSM Overview" (https://help.tableau.com/current/server/en-us
/tsm_overview.htm).


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

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

Answer: C

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 # 49
What Tableau Server authentication method should you configure to use OpenID Connect?

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

Answer: C

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

Analytics-Admn-201 Study Guide Brilliant Analytics-Admn-201 Exam Dumps PDF: https://www.surepassexams.com/Analytics-Admn-201-exam-bootcamp.html

Passing Salesforce Analytics-Admn-201 Exam Using 2026 Practice Tests: https://drive.google.com/open?id=1_tZTtDhXrgxb5ccC008I62V0ytMcuSII

Related Blogs

more
Salesforce Analytics-Admn-201 Certification Practice Exam

Copyright © 2026 SUREPASSEXAMS.COM. All rights reserved. All trademarks are the property of their respective owners and we don't provide actual questions from any vendor.

Disclaimers:
SurePassExams doesn't offer Real Amazon Exam Questions.