Verified Analytics-Admn-201 dumps Q&As - 100% Pass from GuideTorrent
Pass Analytics-Admn-201 Exam in First Attempt Guaranteed 2026 Dumps!
Salesforce Analytics-Admn-201 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
NEW QUESTION # 18
When you use trusted tickets in Tableau Server, users can:
- A. Save and edit workbooks
- B. Embed database credentials
- C. Encrypt database connections
- D. Access embedded views without being prompted for credentials
Answer: D
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 # 19
Which two commands are valid and complete commands? (Choose two.)
- A. tsm maintenance backup
- B. tsm maintenance ziplogs
- C. tsm maintenance restore
- D. tsm maintenance cleanup
Answer: B,D
Explanation:
TSM commands manage Tableau Server maintenance-let's validate their syntax:
* Command Requirements:
* Some need arguments (e.g., file paths); others are standalone.
* Valid and Complete: Must work as-is without errors.
* Option C (tsm maintenance cleanup): Correct.
* Details: Removes temporary files and old logs-no arguments required (optional flags like -l exist).
* Use: tsm maintenance cleanup-runs fully.
* Option D (tsm maintenance ziplogs): Correct.
* Details: Creates a zip of logs (e.g., tsm-logs.zip)-no arguments needed (optional -d for date range).
* Use: tsm maintenance ziplogs-complete and valid.
* Option A (tsm maintenance backup): Incorrect.
* Why: Requires -f <filename>.tsbak (e.g., tsm maintenance backup -f backup.tsbak)-incomplete without it.
* Option B (tsm maintenance restore): Incorrect.
* Why: Needs -f <filename>.tsbak (e.g., tsm maintenance restore -f backup.tsbak)-not standalone.
Why This Matters: Correct syntax ensures maintenance tasks execute without errors-critical for server health.
Reference: Tableau Server Documentation - "TSM Maintenance Commands" (https://help.tableau.com/current
/server/en-us/cli_maintenance_tsm.htm).
NEW QUESTION # 20
What command should you run to update the automatically-generated secrets that are created during a Tableau Server installation?
- A. tsm security regenerate-internal-tokens
- B. tsm data-access caching set -r 1
- C. tsm security validate-asset-keys
- D. tsm licenses refresh
Answer: A
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 # 21
A user reports that a newly-published workbook runs slowly. What should you ask the user first to investigate the problem?
- A. Does the workbook always run slowly or does performance vary?
- B. Does it run any faster in Tableau Desktop?
- C. How many times have you opened the workbook in Tableau Server?
- D. Did you enable caching on the workbook?
Answer: B
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 # 22
A new engineer reports that he is unable to log on to Tableau Services Manager (TSM) from the initial node of a Windows test cluster. Which account credentials should you instruct the engineer to use?
- A. An account for the Tableau Server administrator
- B. An account with administrative rights to the computer
- C. An account with a Site Administrator role
- D. An account with a Creator site role
Answer: B
Explanation:
Tableau Services Manager (TSM) is the administrative tool for managing Tableau Server's configuration, processes, and topology. To log in to TSM (via the web UI at https://<server>:8850 or CLI), you need:
* TSM administrator credentials: These are distinct from site roles and are set during installation or reset via tsm reset.
* Local administrative rights: On Windows, the account used to access TSM must be in the local Administrators group on the initial node, as TSM interacts with system-level services.
In a test cluster, the engineer's inability to log in suggests they lack either the correct TSM credentials or sufficient OS-level permissions. Since the question focuses on a Windows environment and "initial node," the most immediate requirement is local administrative rights to run TSM commands or access the UI.
* Option C (An account with administrative rights to the computer): Correct. The engineer must use an account in the local Administrators group on the initial node to authenticate to TSM. After that, they' ll need the TSM admin username/password set during installation.
* Option A (An account with a Creator site role): Incorrect. Site roles (e.g., Creator) apply to content access within Tableau Server, not TSM administration.
* Option B (An account with a Site Administrator role): Incorrect. Site Administrators manage site content, not server-level TSM functions.
* Option D (An account for the Tableau Server administrator): Partially correct but incomplete. This likely refers to the TSM admin account, but without local admin rights on the machine, login will fail.
Option C is more precise.
Reference: Tableau Server Documentation - "TSM Authentication" (https://help.tableau.com/current/server
/en-us/tsm_overview.htm#authentication).
NEW QUESTION # 23
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. New users created as a result of importing a group are assigned the site role specified during the import
- D. Importing a group from Active Directory requires a .csv file that lists user IDs
Answer: C
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 # 24
What account should you use to run the Tableau Server installation program?
- A. An NT AUTHORITY\NetworkService account
- B. A domain user account
- C. A local user account
- D. An account in the local administrator group
Answer: D
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 # 25
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 a warning message instructing you that embedded .tde extracts will be upgraded to .hyper
- B. You will successfully publish the visualization without any errors or warnings
- C. You will see a warning message instructing you that the workbook will be upgraded to a new version
- D. You will see an error message instructing you that you are unable to publish the workbook to a newer version of Tableau Server
Answer: A
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 # 26
Which Tableau Server process performs the role of a database for metadata?
- A. File Store
- B. Repository
- C. Backgrounder
- D. Data Engine
Answer: B
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 # 27
What is the maximum number of tasks that a single Backgrounder process can execute simultaneously?
- A. Three
- B. Unlimited (based on server resources)
- C. Two
- D. One
Answer: D
Explanation:
The Backgrounder process in Tableau Server handles tasks like extract refreshes and subscriptions-let's explore its concurrency:
* Backgrounder Behavior:
* Each instance is single-threaded for task execution-one task at a time per Backgrounder.
* Multiple Backgrounders (e.g., in multi-node setups) increase parallelism, but a single Backgrounder is limited to 1 concurrent task.
* Queue: Additional tasks wait in the queue, prioritized by their priority (1-100).
* Option A (One): Correct.
* Details: A single Backgrounder executes one task (e.g., an extract refresh) until completion before starting the next.
* Config: Add more Backgrounders via TSM (tsm topology set-process -n node1 -pr backgrounder
-c 2) for more concurrency.
* Option B (Two): Incorrect.
* Why: Not natively supported-a single Backgrounder doesn't multi-thread tasks.
* Option C (Three): Incorrect.
* Why: Exceeds the single-threaded design.
* Option D (Unlimited): Incorrect.
* Why: Concurrency is fixed at 1 per instance-resources affect queue processing speed, not simultaneous tasks.
Why This Matters: Understanding Backgrounder limits guides scaling-more instances mean more parallel tasks, critical for heavy workloads.
Reference: Tableau Server Documentation - "Backgrounder Process" (https://help.tableau.com/current/server
/en-us/processes.htm#backgrounder).
NEW QUESTION # 28
What two Tableau Services Manager (TSM) processes continue to run when Tableau Server is stopped?
(Choose two.)
- A. Administration Controller
- B. Backgrounder
- C. License Manager
- D. VizQL Server
Answer: A,C
Explanation:
Tableau Server consists of multiple processes managed by TSM. When you stop Tableau Server (e.g., via tsm stop), most application processes halt, but some TSM-specific processes remain active to manage the server's infrastructure. Let's examine each:
* TSM Processes: These include the Administration Controller, Administration Agent, and License Manager, which handle configuration, monitoring, and licensing.
* Application Processes: These include VizQL Server, Backgrounder, Data Server, etc., which deliver Tableau's core functionality and stop when the server is stopped.
When tsm stop is executed:
* The Administration Controller (port 8850) continues running to manage TSM operations (e.g., restarts, status checks).
* The License Manager remains active to validate licenses and ensure compliance, even when the server is offline.
* Application processes like VizQL Server and Backgrounder shut down, as they're tied to user-facing services.
* Option B (License Manager): Correct. It persists to handle licensing tasks, ensuring the server can restart without license issues.
* Option D (Administration Controller): Correct. It's the core TSM process, always running to accept commands and manage the server state.
* Option A (VizQL Server): Incorrect. VizQL stops, as it renders visualizations for users-an application process tied to active server operation.
* Option C (Backgrounder): Incorrect. Backgrounder stops, as it processes background tasks (e.g., extract refreshes), which halt when the server is down.
Why This Matters: Understanding which processes persist helps administrators troubleshoot and manage server lifecycle events effectively.
Reference: Tableau Server Documentation - "TSM Processes" (https://help.tableau.com/current/server/en-us
/tsm_overview.htm#processes).
NEW QUESTION # 29
What file format should you use to register Tableau Server from the command line?
- A. JSON
- B. HTTP
- C. XML
- D. YML
Answer: A
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 # 30
Which two options can be configured by a server administrator per site? (Choose two.)
- A. Limitation on storage space
- B. Limitation on number of users
- C. Ability to embed credentials
- D. Language and locale
Answer: A,D
Explanation:
Tableau Server supports multi-tenancy via sites, each with customizable settings managed by server or site administrators. Let's analyze what's configurable per site:
* Site Settings: Found in the web UI under Site > Settings > General. Server admins can override site admin settings.
* Option B (Limitation on storage space): Correct.
* Details: Server admins can set a storage quota per site (e.g., 100 GB) to cap disk usage for extracts and workbooks.
* How: In TSM or site settings (if enabled)-e.g., tsm configuration set -k site.storage.quota -v
100000.
* Impact: Prevents one site from monopolizing resources in multi-site deployments.
* Option D (Language and locale): Correct.
* Details: Each site can set its language (e.g., English, French) and locale (e.g., date/number formats).
* How: Site settings UI-e.g., "Language: French, Locale: France."
* Impact: Tailors the user experience per site's audience.
* 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 # 31
What type of information is stored in the tsm maintenance backup -f <filename>.tsbak command?
- A. SMTP server settings
- B. Notification settings
- C. Repository data
- D. Topology data
Answer: C
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 # 32
What process enables you to access Tableau Services Manager (TSM) over HTTPS?
- A. Administration Controller
- B. License Manager
- C. Administration Agent
- D. Coordination Service
Answer: A
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 # 33
......
Analytics-Admn-201 Dumps Full Questions - Exam Study Guide: https://www.guidetorrent.com/Analytics-Admn-201-pdf-free-download.html
Use Real Analytics-Admn-201 - 100% Cover Real Exam Questions: https://drive.google.com/open?id=1z14zZMtNfIEKeLMCginPbMH1QRXVTCWF