Jan 21, 2026 Step by Step Guide to Prepare for Analytics-Admn-201 Exam BrainDumps
Salesforce Administrator Analytics-Admn-201 Real Exam Questions and Answers FREE Updated on 2026
Salesforce Analytics-Admn-201 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
NEW QUESTION # 23
What should you do to disable table recommendations for popular data sources and tables to users?
- A. Publish data sources only to projects with permissions locked to the project
- B. Disable the option using the server Settings page
- C. Use the command: tsm configuration set -k recommendations.enabled -v false
- D. Disable the option using the site Settings page
Answer: D
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 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).
NEW QUESTION # 24
If a user already exists as part of a group in Tableau Server, and Active Directory synchronization then applies a minimum site role to the group, what will happen to the existing user's site role?
- A. It will always change to the minimum site role
- B. It will never change as a result of synchronization
- C. It will change to the minimum site role only if the minimum site role provides more access
- D. It will change to the minimum site role only if the minimum site role reduces access
Answer: D
Explanation:
When Tableau Server uses Active Directory (AD) for authentication, group synchronization imports AD groups and assigns a minimum site role (e.g., Viewer, Explorer) to users in that group. This ensures users meet a baseline access level. The behavior for existing users during sync is:
* If the user's current site role provides more access than the minimum (e.g., Explorer vs. Viewer), their role remains unchanged.
* If the user's current role provides less access than the minimum (e.g., Unlicensed vs. Viewer), their role is upgraded to the minimum.
This preserves higher privileges while enforcing a floor. "Reduces access" means the minimum role is lower than the current role (e.g., Viewer vs. Explorer), in which case the existing role stays.
* Option A (It will change to the minimum site role only if the minimum site role reduces access):
Correct. The user's role changes only if the minimum increases access (e.g., Unlicensed to Viewer); otherwise, it stays higher.
* Option B (It will change only if the minimum provides more access): Incorrect wording. This is the inverse of the actual behavior-change occurs when needed to meet the minimum, not to exceed it.
* Option C (It will always change): Incorrect. Existing higher roles are preserved.
* Option D (It will never change): Incorrect. It changes if the current role is below the minimum.
Reference: Tableau Server Documentation - "Synchronize Active Directory Groups" (https://help.tableau.com
/current/server/en-us/groups_sync.htm).
NEW QUESTION # 25
What are two features of the Tableau Server user-based license? (Choose two.)
- A. A perpetual license
- B. A subscription license
- C. Enables distinct user roles
- D. Restricts the number of machine cores you can deploy
Answer: B,C
Explanation:
Tableau Server's user-based licensing model assigns licenses to individual users (Creator, Explorer, Viewer) rather than machines or cores. Key features include:
* Subscription license: Licenses are typically subscription-based, renewed annually or monthly, aligning with Tableau's pricing model.
* Distinct user roles: It supports three roles (Creator, Explorer, Viewer), each with specific capabilities, enabling granular access control.
* Option A (A subscription license): Correct. User-based licenses are subscription-based by default.
* Option B (Enables distinct user roles): Correct. The model defines Creator, Explorer, and Viewer roles.
* Option C (Restricts the number of machine cores): Incorrect. This applies to core-based licensing, not user-based.
* Option D (A perpetual license): Incorrect. Perpetual licenses were phased out; user-based licenses are subscription-based as of recent models.
Reference: Tableau Server Documentation - "Licensing Overview" (https://help.tableau.com/current/server/en- us/license_usage.htm).
NEW QUESTION # 26
When you use trusted tickets in Tableau Server, users can:
- A. Access embedded views without being prompted for credentials
- B. Encrypt database connections
- C. Embed database credentials
- D. Save and edit workbooks
Answer: A
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 # 27
What account should you use to run the Tableau Server installation program?
- A. A local user account
- B. An NT AUTHORITY\NetworkService account
- C. A domain 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 # 28
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 priority of this task to 1
- B. Set the priority of this task to 100
- C. Set the default priority of this schedule to 50
- D. Set the priority for all other tasks to 50
Answer: A
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).
NEW QUESTION # 29
You attempt to delete a user who owns content on a Tableau Server. What is the result of the delete action?
- A. The user is switched to an Unlicensed site role and is NOT deleted
- B. The user is deleted, and the user's content is reassigned to the project leader
- C. The user is deleted, and the user's content is reassigned to the server administrator
- D. The user and all of the user's content is deleted
Answer: A
Explanation:
Deleting a user in Tableau Server involves handling their owned content (workbooks, data sources)-let's analyze the process:
* Deletion Rules:
* Ownership Check: Tableau prevents deletion if the user owns content to avoid orphaning it.
* Action: Instead of deleting, the user's site role is set to Unlicensed, retaining their account and content ownership.
* Resolution: An admin must reassign ownership (e.g., via Users > Actions > Change Owner) before deletion.
* Option D (User switched to Unlicensed and NOT deleted): Correct.
* Details: Attempting deletion (e.g., Users > Select User > Actions > Delete) triggers a check. If content exists, the user becomes Unlicensed-still in the system but unable to log in.
* Why: Protects data integrity-content remains accessible for reassignment.
* Option A (Deleted, content to server admin): Incorrect.
* Why: No automatic reassignment to the server admin-manual action is required first.
* Option B (Deleted, content to project leader): Incorrect.
* Why: Project leaders don't automatically inherit content-no such mechanism exists.
* Option C (User and content deleted): Incorrect.
* Why: Tableau avoids deleting content with the user-too destructive without explicit intent.
Why This Matters: This safeguard prevents accidental data loss, ensuring admins manage ownership transitions deliberately.
Reference: Tableau Server Documentation - "Delete Users" (https://help.tableau.com/current/server/en-us
/users_delete.htm).
NEW QUESTION # 30
What should you do to disable table recommendations for popular data sources and tables to users?
- A. Publish data sources only to projects with permissions locked to the project
- B. Disable the option using the server Settings page
- C. Use the command: tsm configuration set -k recommendations.enabled -v false
- D. Disable the option using the site Settings page
Answer: D
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 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).
NEW QUESTION # 31
Several Tableau Server users published workbooks that have large extracts. After several weeks of use, the users abandoned the workbooks. What should you do to identify the abandoned workbooks?
- A. Delete all extracts and allow them to be re-generated automatically if they are still in use
- B. Use the Stale Content administrative view
- C. Examine the extract files in ProgramData/Tableau/Tableau Server/data/tabsvc/dataengine/extract
- D. View all workbooks, and sort by the Modified date
Answer: B
Explanation:
Abandoned workbooks-those no longer actively used-can clutter Tableau Server and consume resources (e.
g., disk space for extracts). Identifying them efficiently requires leveraging built-in administrative tools rather than manual or destructive methods. Let's explore this in depth:
* Tableau Server Admin Views: Tableau provides pre-built administrative views to monitor server health, usage, and content. The Stale Content view, accessible under Server > Status > Administrative Views, is specifically designed to identify content (workbooks, data sources) that hasn' t been viewed or modified recently. It shows:
* Content name, owner, and project.
* Last viewed date and last modified date.
* View count over a period.This view uses Repository data to track usage metrics, making it ideal for spotting abandoned workbooks.
* Option A (Use the Stale Content administrative view): Correct. This is the most efficient and non- invasive method. You can filter by last viewed date (e.g., >30 days ago) to identify workbooks with large extracts that users have stopped accessing. From there, you can contact owners or delete the content if policy allows. It's a server administrator's go-to tool for content management.
* Option B (Examine extract files in ProgramData/.../extract): Incorrect and impractical. The ProgramData/Tableau/Tableau Server/data/tabsvc/dataengine/extract directory stores .hyper extract files, but:
* File names are cryptic (e.g., GUIDs), not tied directly to workbook names.
* It doesn't indicate usage or abandonment-only file presence and size.
* Manual inspection is time-consuming and error-prone compared to the Stale Content view.
* Option C (Delete all extracts and allow them to be re-generated): Incorrect and risky. Deleting extracts (e.g., via tsm maintenance cleanup) removes them without identifying usage. Regeneration only occurs if a schedule or user triggers it, potentially disrupting active users and losing historical data unnecessarily.
* Option D (View all workbooks, and sort by the Modified date): Partially effective but inefficient. In the Tableau Server UI (e.g., under Content > Workbooks), you can sort by "Last Modified," but:
* It doesn't show viewership (a workbook might be modified recently but unused).
* It's manual and doesn't scale for large deployments compared to the Stale Content view.
Why This Matters: The Stale Content view leverages Tableau's metadata to provide actionable insights, saving time and reducing risk compared to manual or destructive alternatives. It's part of Tableau's governance toolkit.
Reference: Tableau Server Documentation - "Administrative Views" (https://help.tableau.com/current/server
/en-us/adminview_stale_content.htm).
NEW QUESTION # 32
Which two options can be configured by a server administrator per site? (Choose two.)
- A. Limitation on storage space
- B. Language and locale
- C. Limitation on number of users
- D. Ability to embed credentials
Answer: A,B
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 # 33
Which two commands are valid and complete commands? (Choose two.)
- A. tsm maintenance cleanup
- B. tsm maintenance backup
- C. tsm maintenance ziplogs
- D. tsm maintenance restore
Answer: A,C
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 # 34
A user receives an error after attempting to run an extract refresh on the Tableau Server. What should you review to identify the cause of the problem?
- A. Whether the project permissions are set to Locked to the project
- B. The UNC path to the extract's data source
- C. The status of the Backgrounder process, as shown by the tsm status -v command
- D. The Background Tasks for Extracts administrative view on the site status page
Answer: D
Explanation:
When an extract refresh fails on Tableau Server, troubleshooting requires identifying the root cause-e.g., connectivity issues, resource constraints, or configuration errors. The Backgrounder process handles extract refreshes, so it's a key focus, but the best diagnostic tool depends on granularity and context. Let's explore this thoroughly:
* Extract Refresh Process:
* An extract refresh pulls data from a source (e.g., database, file) into a .hyper file stored on Tableau Server.
* The Backgrounder executes these tasks based on schedules or manual triggers.
* Errors could stem from: database connectivity, credentials, file access, resource overload, or task misconfiguration.
* Option B (Background Tasks for Extracts administrative view): Correct. This is the most direct and detailed method:
* Location: In the Tableau Server web UI, go to Server > Status > Background Tasks for Extracts (or site-specific under Site > Status).
* Details Provided:
* Task name, schedule, and workbook/data source.
* Start/end times and status (e.g., Failed, Success).
* Error messages (e.g., "Cannot connect to database," "Permission denied").
* Why It's Best: It pinpoints the exact failure (e.g., "timeout," "invalid credentials") for the specific refresh, offering actionable insights without needing to dig through logs manually. Server or site administrators can access this view to diagnose issues quickly.
* Example: If the error is "Database login failed," you'd check credentials in the data source settings next.
* Option A (Status of the Backgrounder process via tsm status -v): Partially useful but insufficient:
* What It Shows: Running/stopped status of all processes (e.g., "Backgrounder: RUNNING").
* Limitation: It confirms if Backgrounder is operational but doesn't reveal why a specific task failed-no error details or task-level granularity.
* Use Case: If Backgrounder is stopped or crashed, this might indicate a broader issue, but the question implies a single refresh error, not a server-wide failure.
* Option C (The UNC path to the extract's data source): Relevant but secondary:
* Context: If the data source is a file (e.g., CSV on a network share), the UNC path (e.g.,
\\server\share\file.csv) must be accessible.
* Why Not First: The error could be unrelated (e.g., database issue, not file-based). The admin view (B) would reveal if it's a path issue first, guiding you to check the UNC path only if indicated (e.g., "File not found").
* Practical Note: Backgrounder needs share permissions and the Run As account must access it- checking this without context wastes time.
* Option D (Whether project permissions are set to Locked): Unlikely cause:
* Permissions Impact: Locked permissions restrict who can edit/view content, not whether an extract refresh runs-that's tied to the data source's connection settings and Backgrounder execution.
* Exception: If the refresh user lacks "Connect" permission to the data source, it might fail, but this is rare (owner/schedule typically has access). The admin view would flag this.
Why This Matters: The Background Tasks view is Tableau's purpose-built tool for extract diagnostics, saving time and reducing guesswork in production environments.
Reference: Tableau Server Documentation - "Administrative Views: Background Tasks for Extracts" (https://help.tableau.com/current/server/en-us/adminview_background_tasks.htm).
NEW QUESTION # 35
Which three items can be contained in a project? (Choose three.)
- A. Workbooks
- B. Data Sources
- C. Nested Projects
- D. Groups
Answer: A,B,C
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).
NEW QUESTION # 36
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).
NEW QUESTION # 37
What command should you run to update the automatically-generated secrets that are created during a Tableau Server installation?
- A. tsm security validate-asset-keys
- B. tsm data-access caching set -r 1
- C. tsm security regenerate-internal-tokens
- D. tsm licenses refresh
Answer: C
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 # 38
What type of information is stored in the tsm maintenance backup -f <filename>.tsbak command?
- A. Repository data
- B. Topology data
- C. SMTP server settings
- D. Notification settings
Answer: A
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 # 39
......
Ultimate Guide to Prepare Analytics-Admn-201 Certification Exam for Salesforce Administrator: https://www.passreview.com/Analytics-Admn-201_exam-braindumps.html
Analytics-Admn-201 Ultimate Study Guide: https://drive.google.com/open?id=1vUpCur-BJhT82kEw1hBCmgsObXxx5Jam