Practice Free Analytics-Admn-201 Exam Online Questions
Question #11
What is the maximum number of tasks that a single Backgrounder process can execute simultaneously?
- A . One
- B . Two
- C . Three
- D . Unlimited (based on server resources)
Correct Answer: A
A
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 (1C100).
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).
A
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 (1C100).
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).
Question #12
What event is most likely to cause problems for a Tableau Server?
- A . Running additional software on the server
- B . Separating the Backgrounder and VizQL processes to different machines
- C . Configuring the server to use a static IP address
- D . Using a non-default installation path
Correct Answer: A
A
Explanation:
Tableau Server’s performance and stability depend on dedicated resources and proper configuration. Running additional software on the same server is the most likely to cause problems because: Resource contention: Tableau Server requires significant CPU, RAM, and disk I/O. Other software (e.g., databases, web servers) can compete for these resources, leading to slowdowns, crashes, or failed tasks.
Port conflicts: Tableau uses specific ports (e.g., 80, 443, 8850), and other applications might interfere.
Security risks: Additional software increases the attack surface, potentially compromising Tableau Server.
Tableau recommends running the server on dedicated hardware without unrelated applications. Option A (Running additional software on the server): Correct. This is a common cause of performance issues and is explicitly discouraged in Tableau’s best practices.
Option B (Separating the Backgrounder and VizQL processes to different machines): Incorrect. This is a supported multi-node configuration that can improve performance, not cause problems, if properly set up via TSM.
Option C (Configuring the server to use a static IP address): Incorrect. A static IP is recommended for Tableau Server to ensure consistent network access, so it’s unlikely to cause issues.
Option D (Using a non-default installation path): Incorrect. While not default, a custom path is supported (via TSM or installer options) and unlikely to cause problems if permissions and disk space are adequate.
Reference: Tableau Server Documentation – "Best Practices for Installation" (https://help.tableau.com/current/server/en-us/install_best_practices.htm).
A
Explanation:
Tableau Server’s performance and stability depend on dedicated resources and proper configuration. Running additional software on the same server is the most likely to cause problems because: Resource contention: Tableau Server requires significant CPU, RAM, and disk I/O. Other software (e.g., databases, web servers) can compete for these resources, leading to slowdowns, crashes, or failed tasks.
Port conflicts: Tableau uses specific ports (e.g., 80, 443, 8850), and other applications might interfere.
Security risks: Additional software increases the attack surface, potentially compromising Tableau Server.
Tableau recommends running the server on dedicated hardware without unrelated applications. Option A (Running additional software on the server): Correct. This is a common cause of performance issues and is explicitly discouraged in Tableau’s best practices.
Option B (Separating the Backgrounder and VizQL processes to different machines): Incorrect. This is a supported multi-node configuration that can improve performance, not cause problems, if properly set up via TSM.
Option C (Configuring the server to use a static IP address): Incorrect. A static IP is recommended for Tableau Server to ensure consistent network access, so it’s unlikely to cause issues.
Option D (Using a non-default installation path): Incorrect. While not default, a custom path is supported (via TSM or installer options) and unlikely to cause problems if permissions and disk space are adequate.
Reference: Tableau Server Documentation – "Best Practices for Installation" (https://help.tableau.com/current/server/en-us/install_best_practices.htm).
Question #13
Which three items can be contained in a project? (Choose three.)
- A . Groups
- B . Workbooks
- C . Nested Projects
- D . Data Sources
Correct Answer: B, C, D
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).
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).
Question #14
You need to ensure that Tableau Server requires the setup of a new administrator account the next time you attempt to log in.
What should you do?
- A . Edit tabsvc.yml
- B . Run the tsm reset command
- C . Run the tsm register command
- D . Reinstall Tableau Server
Correct Answer: B
B
Explanation:
To force Tableau Server to require the setup of a new administrator account (e.g., resetting the server to an initial setup state), the tsm reset command is the appropriate tool. This command resets Tableau Server’s administrative configuration, including the TSM administrator account, while preserving content like workbooks and data sources.
Option B (Run the tsm reset command): Correct. Running tsm reset clears the current TSM administrator credentials and configuration settings. The next time you access TSM (e.g., via the web interface or CLI), it prompts you to set up a new administrator account, mimicking the initial setup process. Command: tsm reset –username <new-username> –password <new-password>.
Option A (Edit tabsvc.yml): Incorrect. The tabsvc.yml file contains service configuration data, but manually editing it is not supported or recommended for resetting the administrator account. It could also corrupt the installation.
Option C (Run the tsm register command): Incorrect. The tsm register command is used to register Tableau Server with a new product key or identity store, not to reset the administrator account. Option D (Reinstall Tableau Server): Incorrect. Reinstallation wipes the entire server, including content, and is overkill for this task. The tsm reset command achieves the goal without data loss.
Reference: Tableau Server Documentation – "TSM Reset Command" (https://help.tableau.com/current/server/en-us/cli_reset.htm).
B
Explanation:
To force Tableau Server to require the setup of a new administrator account (e.g., resetting the server to an initial setup state), the tsm reset command is the appropriate tool. This command resets Tableau Server’s administrative configuration, including the TSM administrator account, while preserving content like workbooks and data sources.
Option B (Run the tsm reset command): Correct. Running tsm reset clears the current TSM administrator credentials and configuration settings. The next time you access TSM (e.g., via the web interface or CLI), it prompts you to set up a new administrator account, mimicking the initial setup process. Command: tsm reset –username <new-username> –password <new-password>.
Option A (Edit tabsvc.yml): Incorrect. The tabsvc.yml file contains service configuration data, but manually editing it is not supported or recommended for resetting the administrator account. It could also corrupt the installation.
Option C (Run the tsm register command): Incorrect. The tsm register command is used to register Tableau Server with a new product key or identity store, not to reset the administrator account. Option D (Reinstall Tableau Server): Incorrect. Reinstallation wipes the entire server, including content, and is overkill for this task. The tsm reset command achieves the goal without data loss.
Reference: Tableau Server Documentation – "TSM Reset Command" (https://help.tableau.com/current/server/en-us/cli_reset.htm).
Question #15
What two Tableau Services Manager (TSM) processes continue to run when Tableau Server is stopped? (Choose two.)
- A . VizQL Server
- B . License Manager
- C . Backgrounder
- D . Administration Controller
Correct Answer: B, D
B, D
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).
B, D
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).
Question #16
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
Correct Answer: B, D
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).
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).
Question #17
You need to verify the status of the Coordination Service ensemble in a high-availability (HA) Tableau Server cluster.
What should you do?
- A . Examine the Tableau Services Manager (TSM) web client Status page
- B . Run the command tsm maintenance ziplogs
- C . Run the command tsm status -v
- D . Examine the Tableau Server Status page
Correct Answer: C
C
Explanation:
In an HA Tableau Server cluster, the Coordination Service (ZooKeeper ensemble) maintains cluster
state―let’s find the best way to check it:
Coordination Service:
Runs on multiple nodes (3 or 5 in HA) to ensure quorum and failover.
Status indicates if it’s running and synced―critical for cluster health.
Option C (Run tsm status -v): Correct.
Details: tsm status –verbose lists all processes across nodes, including Coordination Service (e.g.,
"Coordination Service: RUNNING").
Why Best: Provides detailed, node-specific status in the CLI―e.g., "Node 1: RUNNING, Node 2:
RUNNING."
Use: Run on the initial node; -v ensures full output.
Option A (TSM web client Status page): Incorrect.
Why: The TSM UI (Server > Status) shows process counts (e.g., "Coordination Service: 3 instances"), but not detailed per-node status―less granular than CLI. Option B (tsm maintenance ziplogs): Incorrect.
Why: Generates log archives for troubleshooting, not a real-time status check.
Option D (Tableau Server Status page): Incorrect.
Why: The Server Status page (Server > Status in the web UI) monitors application processes (e.g., VizQL), not TSM’s Coordination Service.
Why This Matters: Coordination Service health ensures HA stability―tsm status -v is the admin’s go-to for precision.
Reference: Tableau Server Documentation – "Check Server Status" (https://help.tableau.com/current/server/en-us/tsm_status.htm).
C
Explanation:
In an HA Tableau Server cluster, the Coordination Service (ZooKeeper ensemble) maintains cluster
state―let’s find the best way to check it:
Coordination Service:
Runs on multiple nodes (3 or 5 in HA) to ensure quorum and failover.
Status indicates if it’s running and synced―critical for cluster health.
Option C (Run tsm status -v): Correct.
Details: tsm status –verbose lists all processes across nodes, including Coordination Service (e.g.,
"Coordination Service: RUNNING").
Why Best: Provides detailed, node-specific status in the CLI―e.g., "Node 1: RUNNING, Node 2:
RUNNING."
Use: Run on the initial node; -v ensures full output.
Option A (TSM web client Status page): Incorrect.
Why: The TSM UI (Server > Status) shows process counts (e.g., "Coordination Service: 3 instances"), but not detailed per-node status―less granular than CLI. Option B (tsm maintenance ziplogs): Incorrect.
Why: Generates log archives for troubleshooting, not a real-time status check.
Option D (Tableau Server Status page): Incorrect.
Why: The Server Status page (Server > Status in the web UI) monitors application processes (e.g., VizQL), not TSM’s Coordination Service.
Why This Matters: Coordination Service health ensures HA stability―tsm status -v is the admin’s go-to for precision.
Reference: Tableau Server Documentation – "Check Server Status" (https://help.tableau.com/current/server/en-us/tsm_status.htm).
1 2