Pass Your Salesforce Exam with Analytics-Admn-201 Exam Dumps (Updated 82 Questions)
Analytics-Admn-201 Exam Dumps - Salesforce Practice Test Questions
NEW QUESTION # 44
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 # 45
Which two options can be configured by a server administrator per site? (Choose two.)
- A. Limitation on storage space
- B. Language and locale
- C. Ability to embed credentials
- D. Limitation on number of users
Answer: A,B
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.
* Option A (Ability to embed credentials): Incorrect.
* Details: Embedding credentials (e.g., in data sources) is a server-wide setting (tsm data-access), not per-site. Site admins can't override it.
* Option C (Limitation on number of users): Incorrect.
* Details: User limits are tied to licenses (server-wide), not configurable per site. Site admins manage user assignments, not quotas.
Why This Matters: Site-specific settings enable tailored governance and resource allocation in multi-tenant environments.
Reference: Tableau Server Documentation - "Site Settings" (https://help.tableau.com/current/server/en-us
/site_settings.htm).
NEW QUESTION # 46
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. Whether the project permissions are set to Locked to the project
- C. The Background Tasks for Extracts administrative view on the site status page
- D. The UNC path to the extract's data source
Answer: C
Explanation:
When an extract refresh fails on Tableau Server, troubleshooting requires identifying the root cause--e.g., connectivity issues, resource constraints, or configuration errors. The Backgrounder process handles extract refreshes, so it's a key focus, but the best diagnostic tool depends on granularity and context. Let's explore this thoroughly:
Extract Refresh Process:
An extract refresh pulls data from a source (e.g., database, file) into a .hyper file stored on Tableau Server.
The Backgrounder executes these tasks based on schedules or manual triggers. Errors could stem from: database connectivity, credentials, file access, resource overload, or task misconfiguration.
Option B (Background Tasks for Extracts administrative view): Correct. This is the most direct and detailed method:
Location: In the Tableau Server web UI, go to Server > Status > Background Tasks for Extracts (or site- specific under Site > Status).
Details Provided:
Task name, schedule, and workbook/data source.
Start/end times and status (e.g., Failed, Success).
Error messages (e.g., "Cannot connect to database," "Permission denied"). Why It's Best: It pinpoints the exact failure (e.g., "timeout," "invalid credentials") for the specific refresh, offering actionable insights without needing to dig through logs manually. Server or site administrators can access this view to diagnose issues quickly.
NEW QUESTION # 47
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. Manually re-publish each workbook one at a time
- B. Export TSM settings, take a full .tsbak backup, install Tableau Server fresh at the new location, import settings, then restore the backup
- C. Use tabcmd to copy each site individually
- D. Simply copy the PostgreSQL database files to the new server
Answer: B
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 # 48
Which Tableau Server process performs the role of a database for metadata?
- A. Backgrounder
- B. File Store
- C. Repository
- D. Data Engine
Answer: C
Explanation:
Tableau Server relies on several processes to function, each with a specific role. The Repository process (powered by PostgreSQL) serves as the database for metadata, storing critical information such as:
* User and group details.
* Permissions and site configurations.
* Workbook and data source metadata (e.g., schedules, subscriptions).
* Option B (Repository): Correct. The Repository is the centralized database that holds all metadata, making it the backbone of Tableau Server's content management. There are typically two instances in an HA setup (one active, one passive), monitored by the Cluster Controller.
* Option A (Data Engine): Incorrect. The Data Engine manages in-memory data processing and extract storage (e.g., .hyper files), not metadata. It's separate from the Repository.
* Option C (Backgrounder): Incorrect. The Backgrounder handles background tasks like extract refreshes and subscriptions, but it doesn't store metadata-it interacts with the Repository to retrieve task details.
* Option D (File Store): Incorrect. The File Store manages physical extract files and workbook assets, not metadata, which is stored in the Repository.
Reference: Tableau Server Documentation - "Tableau Server Processes" (https://help.tableau.com/current
/server/en-us/processes.htm).
NEW QUESTION # 49
When you use trusted tickets in Tableau Server, users can:
- A. Embed database credentials
- B. Access embedded views without being prompted for credentials
- C. Encrypt database connections
- D. Save and edit workbooks
Answer: B
Explanation:
Trusted Tickets is an authentication method in Tableau Server for embedding views in external applications (e.g., portals) without requiring users to log in manually. Here's how it works:
* A trusted application (e.g., a web server) authenticates with Tableau Server using a trusted IP or username/password.
* Tableau Server issues a temporary ticket (a unique string).
* The ticket is embedded in a view URL (e.g., /trusted/<ticket>/views/...), granting access to the view for a short period (configurable, default 5 minutes).
* Option A (Access embedded views without being prompted for credentials): Correct. Trusted tickets enable SSO-like behavior for embedded content, bypassing the login prompt if the ticket is valid. This is ideal for seamless integration into external systems.
* Option B (Encrypt database connections): Incorrect. Encryption is handled by data source configurations (e.g., SSL), not trusted tickets, which focus on user authentication.
* Option C (Save and edit workbooks): Incorrect. Trusted tickets grant view access, not edit permissions-those depend on the user's site role and permissions.
* Option D (Embed database credentials): Incorrect. Trusted tickets authenticate users to Tableau Server, not databases-database credentials are managed separately in the data source.
Why This Matters: Trusted tickets simplify embedding Tableau content securely in custom applications, enhancing user experience.
Reference: Tableau Server Documentation - "Trusted Authentication" (https://help.tableau.com/current/server
/en-us/trusted_auth.htm).
NEW QUESTION # 50
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. 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
- D. You can change the name of a group during import, although this will not change the group's name in Active Directory
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.
* 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 # 51
What account should you use to run the Tableau Server installation program?
- A. An NT AUTHORITY\NetworkService account
- B. An account in the local administrator group
- C. A domain user account
- D. A local user account
Answer: B
Explanation:
Installing Tableau Server on Windows requires an account with sufficient privileges to configure services, write to the file system, and manage registry settings. Let's analyze this in depth:
* Installation Requirements:
* The installer creates services (e.g., Tableau Server Gateway), writes to Program Files and ProgramData, and configures TSM.
* It needs local administrative privileges on the machine to perform these tasks.
* Post-install, a "Run As" account can be set for services (e.g., NT
AUTHORITY\NetworkService), but this is separate from the install account.
* Option C (An account in the local administrator group): Correct.
* Why: The account must be in the local Administrators group to:
* Install software (UAC elevation).
* Configure services and ports.
* Write to protected directories (e.g., C:\Program Files\Tableau).
* Examples: A local admin (e.g., Administrator) or a domain user added to the Administrators group (e.g., DOMAIN\AdminUser).
* Process: Log in as this account, run the installer, and provide TSM admin credentials during setup.
* Option A (A local user account): Incorrect.
* A standard local user (not in Administrators) lacks permissions-installation would fail with
"Access Denied" errors.
* Option B (A domain user account): Incorrect unless clarified.
* A domain user without local admin rights can't install. If it's in the Administrators group, it qualifies, but C is more specific.
* Option D (NT AUTHORITY\NetworkService): Incorrect.
* This is a built-in service account for running services (default "Run As" post-install), not for executing the installer-an interactive user account is required.
Why This Matters: Using the right account prevents install failures and ensures secure configuration- critical for production setups.
Reference: Tableau Server Documentation - "Install and Configure Tableau Server" (https://help.tableau.com
/current/server/en-us/install_config.htm).
NEW QUESTION # 52
What statement correctly describes locking permissions to a project?
- A. Locking permissions to projects must be enabled on the Tableau Server Settings page
- B. Content permissions are locked to a project by default
- C. You can lock permissions to a project by setting the appropriate Project permission role
- D. You can lock permissions to a project by changing Customizable to Locked
Answer: D
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.
NEW QUESTION # 53
An organization wants extract-only data sources refreshed automatically every night. What must be configured?
- A. A Search and Browse index rebuild
- B. A live connection setting on the data source
- C. Kerberos delegation
- D. A Backgrounder process and a refresh schedule assigned to the extract
Answer: D
Explanation:
Automatic extract refreshes require both an active Backgrounder process (to execute the job) and a schedule assigned to the extract via the Server or Desktop publishing dialog. Live connections bypass extracts entirely, so that option doesn't apply.
NEW QUESTION # 54
What is the minimum required free hard disk space recommended for a Tableau Server installation in production?
- A. 32 GB
- B. 64 GB
- C. 50 GB
- D. 15 GB
Answer: C
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 # 55
What command should you run to update the automatically-generated secrets that are created during a Tableau Server installation?
- A. tsm security validate-asset-keys
- B. tsm licenses refresh
- C. tsm data-access caching set -r 1
- D. tsm security regenerate-internal-tokens
Answer: D
Explanation:
Tableau Server uses internal secrets (tokens) for secure communication between its processes (e.g., Repository, File Store). These are automatically generated during installation and can be regenerated if compromised or for security maintenance. The command to update these is:
* tsm security regenerate-internal-tokens: This regenerates the internal security tokens, ensuring all processes use the new tokens after a restart.
* Option C (tsm security regenerate-internal-tokens): Correct. This is the documented command for updating internal secrets.
* Option A (tsm data-access caching set -r 1): Incorrect. This command configures caching behavior, not security tokens.
* Option B (tsm licenses refresh): Incorrect. This refreshes license data, unrelated to internal secrets.
* Option D (tsm security validate-asset-keys): Incorrect. This validates encryption keys for assets, not internal tokens.
Reference: Tableau Server Documentation - "Regenerate Internal Tokens" (https://help.tableau.com/current/server/en-us/cli_security.htm#regenerate-internal-tokens).
NEW QUESTION # 56
What process decides when a Repository failover is required?
- A. Coordination Service
- B. Gateway
- C. Cluster Controller
- D. Backgrounder
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 # 57
Which three types of authentications can you use to implement single-sign-on (SSO) authentication to Tableau Server? (Choose three.)
- A. OpenID Connect
- B. Security Assertion Markup Language (SAML)
- C. Kerberos with Active Directory
- D. Local Authentication
Answer: A,B,C
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).
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.
NEW QUESTION # 58
Which three items can be contained in a project? (Choose three.)
- A. Groups
- B. Nested Projects
- C. Workbooks
- D. Data Sources
Answer: B,C,D
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 # 59
What happens to scheduled extract refreshes if the Backgrounder process is stopped on all nodes?
- A. Extract refresh schedules are permanently deleted
- B. Scheduled tasks queue but do not execute until Backgrounder resumes
- C. Extracts refresh using VizQL Server instead
- D. Extracts are refreshed manually via tabcmd automatically
Answer: B
Explanation:
The Backgrounder process executes scheduled and background tasks, including extract refreshes, subscriptions, and flow runs. If it is stopped everywhere, those tasks remain queued and simply wait until Backgrounder is restarted - they are not lost or rerouted to another process.
NEW QUESTION # 60
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 site Settings page
- D. Disable the option using the server Settings page
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.
NEW QUESTION # 61
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 extracts in the related workbook are refreshed
- C. Every 10 minutes
- D. Whenever a new extract is published
Answer: A,B
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.
NEW QUESTION # 62
What two types of users can sign in to Tableau Server and edit the permissions for a workbook in a project, when permissions are NOT set to Locked to the project? (Choose two.)
- A. Users that have the project and workbook Viewer role
- B. The workbook's owner
- C. Users set to Project Leader for the workbook's project
- D. Users that have the workbook Interactor role
Answer: B,C
Explanation:
Editing permissions on a workbook in Tableau Server depends on the user's role and the project's permission settings. Since permissions are not locked (i.e., "Managed by Owner"), let's dissect who can edit them:
Permission Model:
Not Locked: Owners of content (workbooks, data sources) can set permissions, and Project Leaders can override at the project level.
Site Roles: Define maximum capabilities (e.g., Viewer, Explorer, Creator). Capabilities: "Set Permissions" is explicit--only certain users get it.
Option C (The workbook's owner): Correct.
Details: The owner (typically the publisher) has full control over their workbook when permissions are Managed by Owner:
How: In the UI, go to Content > Workbooks > Actions > Permissions--owners can edit rules (e.g., grant Editor to a group).
Site Role: Minimum of Explorer (can publish) or Creator to publish, ensuring "Set Permissions" capability.
Why: Ownership inherently includes permission management unless locked.
Option D (Users set to Project Leader for the workbook's project): Correct. Details: Project Leaders are assigned via Content > Projects > Actions > Permissions > Set Project Leader:
Power: Can edit permissions for all content in the project, even if not the owner.
Site Role: Requires Site Administrator or Server Administrator (Creator/Explorer variants suffice).
Why: Overrides ownership in Managed by Owner mode--ensures project-level governance.
NEW QUESTION # 63
Which two operating systems are supported for a Tableau Server installation? (Choose two.)
- A. Windows 7
- B. Windows Server 2016
- C. Windows 10
- D. Windows Server 2019
Answer: B,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 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.
NEW QUESTION # 64
Which three types of data should you backup to ensure that you can restore a Tableau Server?
(Choose three.)
- A. Repository data
- B. Configuration data
- C. Topology data
- D. Server secrets and Repository passwords
Answer: A,B,D
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.
NEW QUESTION # 65
......
New Real Analytics-Admn-201 Exam Dumps Questions: https://drive.google.com/open?id=1Z3r_5rAJXaW0sz9SeBmvENuemhUlEF7R
Pass Your Analytics-Admn-201 Exam Easily with Accurate PDF Questions: https://www.torrentvalid.com/Analytics-Admn-201-valid-braindumps-torrent.html