Download Valid Salesforce Analytics-Admn-201 Exam Dumps for Preparation 1 / 7 Exam : Analytics-Admn-201 Title : https://www.passcert.com/Analytics-Admn-201.html Salesforce Certified Tableau Server Administrator Download Valid Salesforce Analytics-Admn-201 Exam Dumps for Preparation 2 / 7 1.What should you use to set a preferred active repository? A. A tsm configuration set command B. A tabcmd set command C. The TSM browser client's Maintenance page D. The TSM browser client's Configuration Topology page Answer: A Explanation: Tableau Server uses a PostgreSQL database as its repository to store metadata, user information, and permissions. In a high-availability (HA) setup with multiple nodes, there are typically two repository instances: one active and one passive. The "preferred active repository" refers to designating which repository instance should take priority as the active one. This is managed through Tableau Services Manager (TSM). The correct method to set the preferred active repository is by using the tsm configuration set command. Specifically, you would use a command like: tsm configuration set -k pgsql.preferred_host -v <hostname> This command allows an administrator to specify the preferred host for the active repository, ensuring control over which node takes precedence in an HA environment. Option B (tabcmd set command) is incorrect because tabcmd is a command-line utility primarily used for administrative tasks like managing users, groups, and content (e.g., publishing workbooks), not for configuring server topology or repository settings. Option C (TSM browser client's Maintenance page) is incorrect because the Maintenance page in the TSM web interface is used for tasks like backups, restores, and cleanup, but it does not provide an option to set the preferred active repository. Option D (TSM browser client's Configuration Topology page) is partially relevant since the Topology page displays the current configuration of services across nodes, including the repository. However, it does not allow direct modification of the preferred active repository; this must be done via the tsm command line. Reference: Tableau Server Documentation - "Configure Tableau Server Repository" (https://help.tableau.com/current/server/en-us/repository.htm) and "TSM Command Line Reference" (https://help.tableau.com/current/server/en-us/cli_configuration_set.htm). 2.What type of information is stored in the tsm maintenance backup -f <filename>.tsbak command? A. Notification settings B. SMTP server 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). Download Valid Salesforce Analytics-Admn-201 Exam Dumps for Preparation 3 / 7 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). 3.Which two tasks always require a server administrator? (Choose two.) A. Creating a schedule B. Adding a site C. Locking project permissions D. Adding users Answer: B, D Explanation: In Tableau Server, roles and permissions dictate who can perform specific administrative tasks. A "server administrator" has full control over the entire Tableau Server deployment, while site administrators manage specific sites. Some tasks are restricted to server administrators due to their server-wide impact. Option B (Adding a site): Creating a new site in a multi-site Tableau Server environment is a server-level task that only a server administrator can perform. Sites are logical partitions within the server, and adding a site affects the overall server structure. Site administrators cannot create new sites; they can only manage existing ones. Option D (Adding users): Adding users to Tableau Server (e.g., via the TSM interface or tabcmd) is a server administrator task when it involves adding users at the server level or assigning them to the default site. While site administrators can add users to their specific site in a multi-site environment, the initial addition of users to the server requires server administrator privileges. The question ’ s phrasing ( “ always require ” ) suggests a server-wide context, making this a correct choice. Option A (Creating a schedule): This is incorrect because both server administrators and site administrators can create schedules for tasks like extract refreshes or subscriptions within their scope. It ’ s not exclusive to server administrators. Option C (Locking project permissions): This is incorrect because locking project permissions can be done by a site administrator or project leader with appropriate permissions. It ’ s a project-level action, not a server-level task requiring a server administrator. Reference: Tableau Server Documentation - "Administrative Tasks" (https://help.tableau.com/current/server/en-us/admin_tasks.htm) and "User Management" (https://help.tableau.com/current/server/en-us/users.htm). 4.You have an installation of Tableau Server and a site that are configured to use default settings. Download Valid Salesforce Analytics-Admn-201 Exam Dumps for Preparation 4 / 7 What should you do to ensure that the users on the site can set up data-driven alerts? A. Enable data-driven alerts on the Tableau Services Manager Configuration page B. Run the tsm configuration set -k dataAlerts.checkIntervalInMinutes -v 60 command C. Change the data-driven alerts setting on the new site's Settings page D. No action is necessary: the default settings enable data-driven alerts for the site Answer: C 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). 5.To which site role can you associate the Viewer user-based license level? A. Creator B. Explorer (can publish) C. Viewer D. Explorer Answer: C Explanation: Tableau Server uses a role-based licensing model with three primary license levels: Creator, Explorer, and Viewer. Each license level corresponds to specific site roles that define what users can do on the server. Viewer License: This is the most restrictive license, allowing users to view and interact with published content (e.g., dashboards and visualizations) but not to create or publish new content. Site Role: The Viewer license can only be associated with the Viewer site role. This role restricts users to viewing capabilities, aligning with the license ’ s purpose. Option A (Creator): Incorrect. The Creator license is for users who can create, edit, and publish content using Tableau Desktop and the web interface. It corresponds to the Creator site role, not Viewer. Option B (Explorer (can publish)): Incorrect. This is a variation of the Explorer license, which allows users Download Valid Salesforce Analytics-Admn-201 Exam Dumps for Preparation 5 / 7 to edit and publish content within limits. It ’ s more permissive than Viewer. Option C (Viewer): Correct. The Viewer site role matches the Viewer license level perfectly. Option D (Explorer): Incorrect. The Explorer license allows users to explore data and create content in the web interface, exceeding the Viewer license ’ s capabilities. Reference: Tableau Server Documentation - "User Site Roles and Licenses" (https://help.tableau.com/current/server/en-us/license_usage.htm). 6.Which two operating systems are supported for a Tableau Server installation? (Choose two.) A. Windows 7 B. Windows 10 C. Windows Server 2019 D. Windows Server 2016 Answer: C, D Explanation: Tableau Server is designed for production environments and is supported only on server-class operating systems, not desktop operating systems. As of the latest documentation (aligned with knowledge up to March 21, 2025), the supported operating systems for Tableau Server on Windows are: Windows Server 2016 Windows Server 2019 Windows Server 2022 (added in later versions, but relevant as of 2025). Desktop operating systems like Windows 7 or Windows 10 are not supported for production installations due to stability, security, and performance requirements. Option A (Windows 7): Incorrect. Windows 7 is a desktop OS and is not supported for Tableau Server. It ’ s also end-of-life as of January 2020. Option B (Windows 10): Incorrect. Windows 10 is a desktop OS and not supported for production Tableau Server deployments, though it may be used for testing in non-production scenarios. Option C (Windows Server 2019): Correct. This is a supported server OS for Tableau Server. Option D (Windows Server 2016): Correct. This is also a supported server OS for Tableau Server. Reference: Tableau Server Documentation - "System Requirements for Tableau Server" (https://help.tableau.com/current/server/en-us/requirements.htm). 7.You are the server administrator of a single-node Tableau Server installation. The server hosts five schedules that each execute once a day: Weekday 3:00 PM Extract Refresh, Weekday 5:00 PM Subscription, Weekday 2:00 AM Extract Refresh, Weekday 7:00 AM Extract Refresh, and Weekday 8:00 AM Subscription. The schedules are scheduled to execute during periods when Tableau Server is least active. The busiest period for your server is immediately after the workday begins at 9:00 AM. The office of the CEO reports that every morning at 9:00 AM, they access the views in a particular workbook. The data for these views is refreshed by a task associated with the 7:00 AM schedule. The CEO reports that the data in the views is only being refreshed about 70% of the time. What should you do to attempt to resolve the CEO's problem? A. Set the default priority of this schedule to 50 B. Set the priority for all other tasks to 50 C. Set the priority of this task to 1 Download Valid Salesforce Analytics-Admn-201 Exam Dumps for Preparation 6 / 7 D. Set the priority of this task to 100 Answer: C Explanation: In Tableau Server, schedules manage tasks like extract refreshes and subscriptions. Each task within a schedule has a priority value (ranging from 1 to 100, where 1 is the highest priority and 100 is the lowest). Tasks with higher priority (lower numbers) are executed before tasks with lower priority (higher numbers) when queued by the Backgrounder process. If the Backgrounder is overloaded or delayed, lower-priority tasks may not complete on time, leading to inconsistent refreshes. In this scenario: The 7:00 AM Extract Refresh task is critical for the CEO ’ s workbook, but the data is only refreshed 70% of the time by 9:00 AM. The server has a single node, meaning a single Backgrounder process handles all tasks. With five schedules (some overlapping in the early morning), contention or delays could prevent the 7:00 AM task from completing reliably before 9:00 AM. Option C (Set the priority of this task to 1): Correct. Setting the task priority to 1 ensures it has the highest priority among all queued tasks. This increases the likelihood that the Backgrounder executes it promptly at 7:00 AM, completing the refresh before the CEO accesses the workbook at 9:00 AM. You can adjust task priority in the Tableau Server web interface under Schedules > Tasks > Edit Priority. Option A (Set the default priority of this schedule to 50): Incorrect. The default priority for schedules is already 50, and this option refers to the schedule ’ s default, not the specific task. It wouldn ’ t address the contention issue. Option B (Set the priority for all other tasks to 50): Incorrect. This keeps all tasks at the default priority (50), leaving the 7:00 AM task without a relative advantage. It doesn ’ t prioritize the CEO ’ s task. Option D (Set the priority of this task to 100): Incorrect. Priority 100 is the lowest, which would deprioritize the task, making the refresh even less reliable. Reference: Tableau Server Documentation - "Manage Schedules and Tasks" (https://help.tableau.com/current/server/en-us/schedule_manage.htm). 8.What should you do to disable table recommendations for popular data sources and tables to users? A. Disable the option using the site Settings page B. Use the command: tsm configuration set -k recommendations.enabled -v false C. Publish data sources only to projects with permissions locked to the project D. Disable the option using the server Settings page Answer: A 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 Download Valid Salesforce Analytics-Admn-201 Exam Dumps for Preparation 7 / 7 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). 9.You have a server that contains 16 processor cores. What is the default number of VizQL instances configured by the installer? A. 4 B. 6 C. 10 D. 2 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).