Free Salesforce Analytics-Admn-201 Exam Questions (page: 5)

What should you use to set a preferred active repository?

  1. A tsm configuration set command
  2. A tabcmd set command
  3. The TSM browser client's Maintenance page
  4. The TSM browser client's Configuration Topology page

Answer(s): 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).



What type of information is stored in the tsm maintenance backup -f <filename>.tsbak command?

  1. Notification settings
  2. SMTP server settings
  3. Repository data
  4. Topology data

Answer(s): 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).



Which two tasks always require a server administrator? (Choose two.)

  1. Creating a schedule
  2. Adding a site
  3. Locking project permissions
  4. Adding users

Answer(s): 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).



You have an installation of Tableau Server and a site that are configured to use default settings.
What should you do to ensure that the users on the site can set up data-driven alerts?

  1. Enable data-driven alerts on the Tableau Services Manager Configuration page
  2. Run the tsm configuration set -k dataAlerts.checkIntervalInMinutes -v 60 command
  3. Change the data-driven alerts setting on the new site's Settings page
  4. No action is necessary: the default settings enable data-driven alerts for the site

Answer(s): 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).



To which site role can you associate the Viewer user-based license level?

  1. Creator
  2. Explorer (can publish)
  3. Viewer
  4. Explorer

Answer(s): 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 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).



Viewing page 5 of 12
Viewing questions 21 - 25 out of 55 questions



Post your Comments and Discuss Salesforce Analytics-Admn-201 exam prep with other Community members:

Analytics-Admn-201 Exam Discussions & Posts