ANALYTICS-ADMN-201 Practice Questions

Tableau Server and Tableau Cloud administrators can control recommendation features on a per-site basis. The site's Settings page contains options to selectively enable or disable different types of recommendations, including those for views, data sources, and tables/databases. To disable table recommendations specifically, a site administrator would navigate to the General tab of the site's Settings page and uncheck the corresponding option under the "Recommendations" section. This provides granular control over the user discovery experience within that specific site.

B. Use the command: tsm configuration set -k recommendations.enabled -v false

This command disables all recommendation features for the entire Tableau Server instance, which is a more drastic, server-level action than disabling a specific type of recommendation for a site.

C. Publish data sources only to projects with permissions locked to the project

This is a permissions strategy that limits data source visibility. While it would indirectly affect recommendations, it does not disable the recommendation feature itself.

D. Disable the option using the server Settings page

This specific setting is configured within the settings of an individual site, not on a global server settings page within the Tableau Server user interface.

1. Tableau Server Help, "Set Up for Recommendations": This official documentation page explicitly details the procedure for managing recommendations. It states, "To show or hide recommendations on a site: Go to the Settings page for the site. On the General tab, under Recommendations, clear or select the check boxes for the types of recommendations you want to show." The types listed include "Recommended table and database connections."

Source: Tableau Server Documentation, https://help.tableau.com/current/server/en-us/recommendationsadmin.htm

2. Tableau Server Help, "tsm configuration set Options": This document lists and describes the keys available for server-wide configuration using the Tableau Services Manager (TSM). It includes the recommendations.enabled key, confirming it is a server-level setting that "Enables or disables all recommendations," which contrasts with the site-level control mentioned in the question.

Source: Tableau Server Documentation, https://help.tableau.com/current/server/en-us/configref.htm (Search for recommendations.enabled within the page).

In Tableau (a Salesforce product), projects function as containers to organize and manage content. A project can hold various types of assets, including workbooks, which contain visualizations and dashboards. It can also contain published data sources, allowing for centralized data management. Furthermore, projects support a hierarchical structure, meaning a project can contain other "nested" projects to create a more granular organization of content. This structure is fundamental to managing permissions and content access effectively on a Tableau Server or Tableau Cloud site.

A. Groups: Groups are security principals used to assign permissions to projects and other content; they are not content items that can be stored within a project.

1. Tableau Help (Official Vendor Documentation): "Use Projects to Manage Content". This document explicitly states, "Projects can contain workbooks, data sources, flows, and other projects (called nested projects)." This directly supports that Workbooks (B), Nested Projects (C), and Data Sources (D) are valid content types for a project. It also clarifies that permissions are set on projects for users and groups, but groups themselves are not content within the project.

During a standard single-node installation, Tableau Server installs one instance of each of its core processes by default. This initial configuration provides a fully functional server. The number of processor cores (in this case, four) is a critical factor for performance and scalability, but it does not alter the default count of one instance per process during the initial setup. Administrators can later manually configure additional instances of specific processes, such as the VizQL Server or Backgrounder, to optimize performance based on the server's hardware and workload, but the default is one of each.

A. 2: This is incorrect. While an administrator might add a second instance of a process like VizQL Server on a four-core machine for better performance, it is not the default count for all processes.

C. 8: This is incorrect. There is no default configuration rule that installs eight instances of each process on a four-core server.

D. 4: This is incorrect. The number of process instances does not default to matching the number of CPU cores for every process. This would be an inefficient configuration for single-instance processes like the Gateway.

1. Tableau Server Help (Official Vendor Documentation): "Tableau Server Processes". The documentation describes the function of each process. In the section on configuring nodes, it is established that the initial setup on a single machine installs a single instance of each process. For example, the "Configure Initial Node Settings" guide states: "By default, Tableau Server installs one instance of each process on the initial node..." This confirms the default behavior is to start with one of each.

Reference Location: Tableau Server Help > Administrator Guide > Configure > Configure Initial Node Settings.

2. Tableau Server Help (Official Vendor Documentation): "Performance Tuning". This section explains that administrators should adjust the number of process instances after installation based on hardware specifications like CPU cores. It states, "For most processes, we recommend running no more than one instance on a given computer... However, you can configure more than one instance of the most resource-intensive processes..." This implies the default is one, and increasing the count is a deliberate tuning action.

Reference Location: Tableau Server Help > Administrator Guide > Performance > Performance Tuning.

The tsm reset command is specifically designed to remove all configurations, content, and user data from a Tableau Server installation, effectively returning it to a pre-initialized state. After this command is executed, the server must be re-initialized. This re-initialization process requires the administrator to configure the server from scratch, which includes the mandatory step of creating a new initial administrator account. This directly addresses the requirement to set up a new administrator account upon the next login/setup attempt.

A. Edit tabsvc.yml: Manually editing the tabsvc.yml file is not the standard procedure for resetting an administrator account and is strongly discouraged unless directed by Tableau Support, as it can cause instability.

C. Run the tsm register command: The tsm register command is used exclusively for managing product keys and the registration of the Tableau Server software. It has no function related to user account management.

D. Reinstall Tableau Server: While a full reinstallation would achieve the goal, it is an unnecessarily drastic and time-consuming solution. The tsm reset command provides a more direct and efficient method to achieve the same outcome.

1. Tableau Server Help - tsm reset: "Use the tsm reset command to remove all configuration and return Tableau Server to the state it was in just after it was installed. ... After you run the tsm reset command, you must run the tsm initialize command..." The initialization process includes creating the initial administrator user.

Source: Tableau Official Documentation, tsm reset, https://help.tableau.com/current/server/en-us/clireset.htm

2. Tableau Server Help - Step 1: Install and Initialize TSM: This document outlines the initial setup process which is triggered after a fresh install or a tsm reset. Step 1.5 describes creating the initial administrator account.

Source: Tableau Official Documentation, Install and Configure Tableau Server, https://help.tableau.com/current/server/en-us/installinstall.htm (See section on initializing TSM).

3. Tableau Server Help - tsm licenses: This documentation details the commands for licensing, including register, confirming its purpose is unrelated to user accounts.

Source: Tableau Official Documentation, tsm licenses, https://help.tableau.com/current/server/en-us/clilicensestsm.htm

4. Tableau Server Help - tabsvc.yml Configuration File: This document explicitly warns against modifying the tabsvc.yml file without guidance from support.

Source: Tableau Official Documentation, Configuration File, https://help.tableau.com/current/server/en-us/configfile.htm

A user's license level determines the maximum site role they can be assigned on a Tableau site. The Viewer license is the most restrictive, designed for users who only need to view and interact with published visualizations. Consequently, a user holding a Viewer license can only be assigned the Viewer site role. Assigning them a higher role, such as Explorer or Creator, would grant capabilities that their license does not support.

A. Creator: The Creator site role requires a Creator license, as it allows for creating new data sources and publishing content, which is beyond the scope of a Viewer license.

B. Explorer (can publish): This site role requires at least an Explorer license. It grants publishing capabilities that are not included in the Viewer license level.

D. Explorer: The Explorer site role, which allows for web editing of existing content, requires a minimum of an Explorer license. A Viewer license does not permit these actions.

1. Tableau Server Help: Set Users’ Site Roles. This official documentation provides a table that explicitly maps license types to available site roles. It states, "A user with a Viewer license can have only the Viewer site role." (Accessed under the section "Site roles and license types").

2. Tableau Cloud Help: Permissions. This document outlines the capabilities associated with each license and site role. It clarifies that the Viewer license level corresponds directly to the Viewer site role, which is limited to viewing and interacting with published content. (Accessed under the section "Explore site roles and their capabilities").

The installation of Tableau Server requires elevated privileges to perform system-level changes on the Windows operating system. The account used to run the installer must have the authority to write to the C:\Program Files directory, create and modify system services, and make entries in the Windows Registry. Membership in the local Administrators group grants these necessary permissions, ensuring the setup program can complete all required tasks successfully.

A. A standard local user account lacks the required administrative permissions to install server software and modify system settings.

B. A standard domain user account, by default, does not have local administrative rights on a server, which are necessary for installation.

D. The NT AUTHORITY\NetworkService account is a built-in, non-interactive account used for running services, not for logging in and executing an installation program.

1. Tableau Server Help (Official Vendor Documentation): In the "Before you install..." guide for Tableau Server on Windows, under the "Administrator account" section, it explicitly states: "The account you are logged in as when you install Tableau Server must be a member of the local administrators group on the computer."

Source: Tableau Server on Windows Help, "Before you install...", Section: "Administrator account". (Version 2023.3, but this requirement is consistent across versions).

2. Tableau Server Help (Official Vendor Documentation): The installation process involves creating the initial administrator user for Tableau Server. The documentation specifies, "The user account that you are logged on as when you install Tableau Server will become the first user in the Tableau Server administrator account." This implies the installing account must be an interactive, administrative user.

Source: Tableau Server on Windows Help, "Step 2 - Install and Configure Tableau Server", Section: "Install Tableau Server".

The Tableau Services Manager (TSM) Administration Controller (tabadmincontroller) is the core process that handles requests for TSM. This includes managing the business logic for configuration and topology changes initiated through both the TSM command-line interface (CLI) and the TSM Web UI. Since the TSM Web UI is accessed via a web browser over HTTPS (typically on port 8850), the Administration Controller is the process that directly enables this secure access. It serves as the entry point for all TSM administrative actions.

A. License Manager: This process is solely responsible for managing and enforcing Tableau Server licensing. It does not handle web traffic or administrative UI access.

C. Administration Agent: The Administration Agent runs on each node in a cluster to execute tasks (like starting/stopping services) as directed by the Administration Controller, but it does not serve the TSM Web UI.

D. Coordination Service: This service, based on Apache ZooKeeper, is responsible for maintaining state and ensuring consistency across a multi-node Tableau Server cluster. It is not involved in user-facing administrative access.

1. Tableau Server Help, "Tableau Server Processes":

Section: TSM Administration Controller (tabadmincontroller): "The TSM Administration Controller is the process that handles the TSM CLI and TSM Web UI requests... The TSM Administration Controller handles the business logic for TSM configuration and topology management. It handles API and CLI requests." This directly links the Controller to handling TSM Web UI access.

Section: TSM Administration Agent (tabadminagent): "The TSM Administration Agent is a process that is run on each node in a cluster. The agent is responsible for performing administrative tasks on the node..." This clarifies its role as a subordinate executor, not the primary access handler.

Section: License Manager (licenseservice): "The License Manager process is responsible for licensing Tableau Server." This defines its specific, non-UI-related function.

Section: Coordination Service (zookeeper): "The Coordination Service is the 'single source of truth' for server state..." This confirms its role in cluster state management.

Source Document: Tableau Server on Windows Help, Version: 2023.3, "Server Processes". (This information is consistent across recent versions and platforms).

The most effective initial step in troubleshooting a slow workbook is to isolate the source of the problem. Asking if the workbook runs faster in Tableau Desktop versus Tableau Server/Cloud helps to quickly determine if the performance issue is inherent to the workbook's design (e.g., complex calculations, inefficient queries) or related to the server environment (e.g., server hardware, network latency, data source connectivity from the server). If it is slow in both environments, the workbook itself needs optimization. If it is only slow on the server, the investigation should focus on the server-side components.

B. Does the workbook always run slowly or does performance vary?

This is a valid diagnostic question, but it is a secondary step to determine if the issue is consistent or intermittent, which is best asked after isolating the problem's location (workbook vs. server).

C. How many times have you opened the workbook in Tableau Server?

This question probes caching behavior. While relevant, it's too specific for an initial query. The root cause might not be related to caching at all, making this a less effective starting point.

D. Did you enable caching on the workbook?

This is a configuration detail that the administrator should verify, not a question for a typical end-user who would likely not know the answer. The administrator should check server settings directly.

1. Tableau Help, "Optimize Workbook Performance": In the section "Identify the problem," the official documentation states, "The first step is to identify where the performance problem is happening. Is it slow in Tableau Desktop, or after you publish to Tableau Server or Tableau Cloud? ... By testing your workbook in both environments, you can narrow down the cause of the problem." This directly supports option A as the primary, initial troubleshooting step.

Source: Tableau Official Documentation. (Accessed via Tableau Help portal, specific article title: "Optimize Workbook Performance").

2. Tableau Blueprint, "Tableau Monitoring": The Tableau Blueprint, an official framework, emphasizes a structured approach to performance. The initial phase of any performance investigation involves understanding the scope. Comparing performance between the authoring environment (Desktop) and the published environment (Server/Cloud) is a fundamental technique for scoping the issue before diving into specific metrics like query execution or load times.

Source: Tableau Official Documentation. (Accessed via Tableau Help portal, specific section: "Tableau Blueprint - Monitoring").

To ensure that server tasks run sequentially, or "one-at-a-time," the execution mode must be set to serial. Serial execution processes tasks one after another, where a subsequent task only begins after the preceding one has completed. This is in contrast to parallel execution, where multiple tasks run concurrently. In CRM Analytics, this can be achieved by scheduling jobs to run based on an event, such as the completion of a previous data sync or recipe, effectively creating a serial chain of execution.

B. Set Default priority to 0: Priority influences which job runs first when multiple jobs are queued, but it does not prevent them from running concurrently if resources are available.

C. Set Frequency to Hourly: Frequency determines how often a schedule is initiated (e.g., hourly, daily). It does not control how the tasks within that schedule are executed (serially or in parallel).

D. Set Execution to Parallel: This is the opposite of the requirement. Parallel execution runs multiple tasks simultaneously, not one-at-a-time.

1. Salesforce Help, CRM Analytics Documentation, "Schedule Data Sync and Recipes to Run After Each Other": This document explains the concept of event-based scheduling to create dependencies. It states, "To run a recipe or dataflow after the sync for a specific connection completes, schedule them to run after the connection syncs. You can also chain jobs to run after a recipe or dataflow finishes." This chaining is the mechanism for enforcing serial execution.

2. Salesforce Help, CRM Analytics Documentation, "Schedule, Run, and Monitor Analytics Jobs": This guide details scheduling options. In the context of data sync, it mentions, "To run a connection’s sync jobs one after another, you can schedule them in serial." This directly confirms that "serial" is the correct term for "one-at-a-time" execution.

3. Salesforce Help, CRM Analytics Documentation, "Data Integration Guide", Chapter: Run Data Integration Jobs: This guide discusses job scheduling and dependencies. It notes, "To ensure that a dataflow has the latest data from a particular Salesforce object, run the dataflow after the data sync for that object is complete. You can schedule a dataflow to run after data sync." This describes a practical application of serial execution.

Locking content permissions is a specific administrative action performed at the project level in Tableau Server. When permissions are locked, all workbooks, data sources, and other content published to that project will inherit their permissions directly from the project. This ensures a consistent security model across all assets within the project. The administrator or project leader achieves this by navigating to the project's permissions settings and changing the "Content Permissions" setting from its default state of "Customizable" to "Locked".

A. Locking permissions is a per-project setting and does not require a global enablement on the Tableau Server Settings page.

C. The default setting for content permissions in a newly created project is "Customizable" (unlocked), not "Locked," to allow for granular control by content owners.

D. Locking permissions is a distinct project-level setting that governs inheritance. It is not a permission role (like Viewer or Publisher) that is assigned to a user or group.

1. Tableau Server Help, "Lock Content Permissions": This document explicitly states, "In the project's Permissions dialog box... In the Content Permissions in Project dialog, select Locked (recommended) or Customizable, and then click Save." This directly validates that the action involves changing the setting to "Locked".

2. Tableau Server Help, "Use Projects to Manage Content Access": This guide clarifies the default behavior: "When you create a new top-level project, permissions are customizable ('unlocked')." This directly refutes option C. It also describes the two models (locked vs. customizable), confirming that locking is a setting, not a role (refuting D) or a server-wide configuration (refuting A).