Verified & Latest Analytics-Admn-201 Dump Q&As with Correct Answers

Latest Analytics-Admn-201 dumps - Instant Download PDF

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

• A. Repository data
• B. SMTP server settings
• C. Topology data
• 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 # 20
What statement correctly describes locking permissions to a project?

• A. You can lock permissions to a project by setting the appropriate Project permission role
• B. Content permissions are locked to a project by default
• C. Locking permissions to projects must be enabled on the Tableau Server Settings page
• D. You can lock permissions to a project by changing Customizable to Locked

Answer: D

Explanation:
In Tableau Server, projects organize content (workbooks, data sources) and use permissions to control access. "Locking permissions" restricts how permissions are managed within a project-let's explore this exhaustively:
* Permission Management Modes:
* Managed by Owner: Default mode. Content owners (e.g., workbook publishers) can set permissions on their items, inheriting project defaults as a starting point.
* Locked to the Project: Project-level permissions are enforced, and content owners cannot modify them. This ensures consistency across all items in the project.
* How to Lock:
* In the Tableau Server web UI:
* Go to Content > Projects.
* Select a project, click Actions > Permissions.
* In the Permissions dialog, change Permissions Management from "Customizable" (Managed by Owner) to "Locked."
* Set the desired permissions (e.g., Viewer, Editor) for users/groups, which then apply uniformly to all content.
* Via REST API: Use the updateProject endpoint with "permissionsLocked": true.
* Option B (You can lock permissions to a project by changing Customizable to Locked): Correct.
* Details: This is the precise action in the UI-switching from "Customizable" to "Locked" locks permissions at the project level.
* Impact: Owners lose the ability to override permissions on individual workbooks/data sources, enforcing governance.
* Example: Set "All Users" to Viewer (Locked)-all content in the project is view-only, regardless of owner intent.
* Option A (Locking permissions must be enabled on the Server Settings page): Incorrect.
* Why: Locking is a per-project setting, not a server-wide toggle. The Server Settings page (via TSM) controls global configs (e.g., authentication), not project permissions.
* Option C (Content permissions are locked by default): Incorrect.
* Default: New projects are "Managed by Owner" (Customizable), allowing flexibility unless explicitly locked by an admin.
* Option D (By setting the appropriate Project permission role): Incorrect.
* Confusion: "Project permission role" isn't a term-permissions are set via rules (e.g., Viewer, Editor), but locking is a separate action (Customizable # Locked).
Why This Matters: Locking permissions ensures uniform access control, critical for regulated environments or large teams where consistency trumps flexibility.
Reference: Tableau Server Documentation - "Lock Project Permissions" (https://help.tableau.com/current
/server/en-us/permissions_lock.htm).

NEW QUESTION # 21
You install Tableau Server on a server that has four processor cores. How many instances of each Tableau Server process are installed?

• A. 0
• B. 1
• C. 2
• D. 3

Answer: A

Explanation:
Tableau Server's installer configures process instances based on hardware and deployment type (single-node vs. multi-node). For a single-node installation with 4 cores, we need to consider the default process topology
. Let's break this down exhaustively:
* Key Processes:
* Gateway: Handles incoming requests (1 instance).
* Application Server (VizPortal): Manages UI and sessions (1 instance).
* VizQL Server: Renders visualizations (2 instances).
* Backgrounder: Runs extract refreshes, subscriptions (1 instance).
* Data Server: Manages data connections (1 instance).
* File Store: Stores extracts (1 instance).
* Repository: Metadata database (1 instance, active).
* Cluster Controller, Cache Server, etc.: Supporting processes (typically 1 each).
* Default Configuration:
* On a single-node install, Tableau sets 1 instance per process unless specified otherwise, except for VizQL, which defaults to 2.
* The installer doesn't scale instances linearly with cores (e.g., 4 cores # 4 instances). Post-install, TSM can adjust this (e.g., tsm topology set-process), but the question asks for the installed default.
* Minimum hardware (8 cores, 32 GB RAM) suggests higher defaults, but 4 cores still triggers a minimal setup.
* Option B (1): Correct with Caveat.
* Most processes (e.g., Backgrounder, Gateway, Data Server) default to 1 instance on install, regardless of 4 cores.
* VizQL defaults to 2, but the question's phrasing ("each process") implies a general rule.
Historically (and per docs), 1 is the baseline for most, with VizQL as the exception.
* Interpretation: Assuming "each" means the typical case, 1 fits most processes on a 4-core single- node setup.
* Option A (2): Incorrect. Only VizQL defaults to 2; others don't.
* Option C (8): Incorrect. Far exceeds defaults-8 cores might justify more, but not 4.
* Option D (4): Incorrect. Not tied to core count by default; manual config would be needed.
Why This Matters: Understanding defaults aids capacity planning-4 cores is below production minimum (8), so performance tuning may be needed post-install.
Reference: Tableau Server Documentation - "Server Process Settings" (https://help.tableau.com/current/server
/en-us/processes.htm).

NEW QUESTION # 22
A new engineer reports that he is unable to log on to Tableau Services Manager (TSM) from the initial node of a Windows test cluster. Which account credentials should you instruct the engineer to use?

• A. An account with administrative rights to the computer
• B. An account with a Creator site role
• C. An account for the Tableau Server administrator
• D. An account with a Site Administrator role

Answer: A

Explanation:
Tableau Services Manager (TSM) is the administrative tool for managing Tableau Server's configuration, processes, and topology. To log in to TSM (via the web UI at https://<server>:8850 or CLI), you need:
* TSM administrator credentials: These are distinct from site roles and are set during installation or reset via tsm reset.
* Local administrative rights: On Windows, the account used to access TSM must be in the local Administrators group on the initial node, as TSM interacts with system-level services.
In a test cluster, the engineer's inability to log in suggests they lack either the correct TSM credentials or sufficient OS-level permissions. Since the question focuses on a Windows environment and "initial node," the most immediate requirement is local administrative rights to run TSM commands or access the UI.
* Option C (An account with administrative rights to the computer): Correct. The engineer must use an account in the local Administrators group on the initial node to authenticate to TSM. After that, they' ll need the TSM admin username/password set during installation.
* Option A (An account with a Creator site role): Incorrect. Site roles (e.g., Creator) apply to content access within Tableau Server, not TSM administration.
* Option B (An account with a Site Administrator role): Incorrect. Site Administrators manage site content, not server-level TSM functions.
* Option D (An account for the Tableau Server administrator): Partially correct but incomplete. This likely refers to the TSM admin account, but without local admin rights on the machine, login will fail.
Option C is more precise.
Reference: Tableau Server Documentation - "TSM Authentication" (https://help.tableau.com/current/server
/en-us/tsm_overview.htm#authentication).

NEW QUESTION # 23
Which two tasks always require a server administrator? (Choose two.)

• A. Creating a schedule
• B. Adding a site
• C. Adding users
• D. Locking project permissions

Answer: B,C

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).

NEW QUESTION # 24
Your deployment of Tableau Server uses Active Directory authentication. What statement correctly describes the process of importing a group from Active Directory?

• A. You can change the name of a group during import, although this will not change the group's name in Active Directory
• B. New users created as a result of importing a group are assigned the site role specified during the import
• C. Importing a group from Active Directory requires a .csv file that lists user IDs
• D. If an imported group contains any users that have Tableau Server accounts, their site role will be changed to match the site role specified during the import

Answer: B

Explanation:
Importing an AD group into Tableau Server syncs user management-let's analyze the process and options:
* AD Group Import Process:
* How: In the UI (Users > Groups > Add Group > Active Directory), enter the AD group name, set a site role, and sync.
* Behavior:
* Existing Users: If a user is already in Tableau Server, their site role remains unchanged unless manually adjusted-sync applies the minimum role only if it upgrades access.
* New Users: Added to Tableau with the site role specified during import.
* Config: Requires AD authentication enabled in TSM.
* Option D (New users created are assigned the site role specified during import): Correct.
* Details: When importing (e.g., "SalesTeam" group, site role: Explorer):
* New users get Explorer.
* Existing users keep their role unless it's below Explorer (e.g., Unlicensed # Explorer).
* Why: Ensures consistent onboarding-new users align with the group's intended access.
* Option A (Existing users' roles change to match import): Incorrect.
* Why: Existing roles persist unless lower than the minimum-e.g., Viewer stays Viewer if import sets Explorer, but Unlicensed upgrades. Not a full overwrite.
* Option B (Requires a .csv file): Incorrect.
* Why: AD import uses live sync via LDAP-no .csv needed (that's for local auth imports).
* Option C (Change group name during import): Incorrect.
* Why: The AD group name is fixed-you can't rename it in Tableau during sync (it mirrors AD).
Post-import renaming is possible but not part of the process.
Why This Matters: Accurate AD sync ensures seamless user management-missteps can disrupt access or licensing.
Reference: Tableau Server Documentation - "Synchronize Active Directory Groups" (https://help.tableau.com
/current/server/en-us/groups_sync.htm).

NEW QUESTION # 25
Which three methods should an administrator use to create a Tableau Server group or project? (Choose three.)

• A. Tableau Server browser interface
• B. tsm customize
• C. REST API
• D. tabcmd

Answer: A,C,D

Explanation:
Tableau Server provides multiple methods to create groups (collections of users) and projects (content containers), catering to UI, CLI, and programmatic needs. Let's dissect each option with depth:
* Option B (Tableau Server browser interface): Correct.
* Groups: Go to Users > Groups > Add Group, name it, and optionally sync with Active Directory.
* Projects: Go to Content > Projects > New Project, set name, description, and permissions.
* Details: The web UI is intuitive, requiring server/site administrator rights. It's ideal for manual, ad-hoc creation with immediate visibility.
* Permissions: For projects, you can set default permissions or lock them here.
* Option C (tabcmd): Correct.
* Groups: tabcmd creategroup "GroupName" creates a local group. Add users with tabcmd addusers "GroupName" --users "user1,user2".
* Projects: tabcmd createproject -n "ProjectName" -d "Description" creates a project.
* Details: tabcmd is a command-line tool for batch operations or scripting (e.g., automating group
/project setup). It requires a server admin login (tabcmd login).
* Limitation: No AD sync via tabcmd-that's UI or REST API territory.
* Option D (REST API): Correct.
* Groups: Use the POST /api/api-version/sites/site-id/groups endpoint with a payload (e.g.,
{"group": {"name": "GroupName"}}). Supports AD import too.
* Projects: Use POST /api/api-version/sites/site-id/projects (e.g., {"project": {"name":
"ProjectName", "description": "Desc"}}).
* Details: The REST API is programmatic, ideal for integration with external systems or bulk automation. Requires authentication via a token and server/site admin rights.
* Power: Offers full control, including nested projects and custom permissions.
* Option A (tsm customize): Incorrect.
* Purpose: tsm customize modifies TSM UI branding (e.g., logos, colors) via commands like tsm customize --logo "path/to/logo.png".
* Why Wrong: It's unrelated to creating groups or projects-it's for cosmetic server configuration, not content/user management.
Why This Matters: Offering UI, CLI, and API options ensures flexibility-manual for small tasks, automation for scale-critical in enterprise deployments.
Reference: Tableau Server Documentation - "Manage Groups" (https://help.tableau.com/current/server/en-us
/groups_create.htm), "Manage Projects" (https://help.tableau.com/current/server/en-us/projects_create.htm),
"tabcmd Commands" (https://help.tableau.com/current/server/en-us/tabcmd_cmd.htm), "REST API Reference" (https://help.tableau.com/current/api/rest_api/en-us/REST/rest_api_ref.htm).

NEW QUESTION # 26
What should you do to configure the view URL and enable recording for a site that has recording workbook performance metrics enabled?

• A. Type :record_performance=yes& at the end of the view URL, immediately after the session ID
• B. Click the Performance link in the toolbar at the top of the view
• C. Type :record_performance=yes& at the end of the view URL, immediately before the session ID
• D. Delete the session ID in the URL and reload the view

Answer: A

Explanation:
Tableau Server can record performance metrics for workbooks to troubleshoot slow-loading views. This feature must be enabled at the site level (via Settings > General > Allow Performance Recording). Once enabled, you can trigger recording for a specific view by modifying its URL.
The correct syntax is to append :record_performance=yes& to the view URL, immediately after the session ID. For example:
* Original
URL: http://server/#/site/my-site/views/workbook/view?:iid=1
* Modified
URL: http://server/#/site/my-site/views/workbook/view?:iid=1:record_performance=yes
&
After loading the view with this parameter, a performance recording is generated and accessible via the Performance option in the toolbar.
* Option B (Type :record_performance=yes& at the end of the view URL, immediately after the session ID): Correct. This follows Tableau's documented method for enabling performance recording.
* Option A (Click the Performance link in the toolbar): Incorrect. The Performance link appears only after recording is triggered via the URL; it's not the method to enable it.
* Option C (Type :record_performance=yes& immediately before the session ID): Incorrect. The parameter must follow the session ID (e.g., :iid=1) to function correctly.
* Option D (Delete the session ID in the URL and reload the view): Incorrect. The session ID is required for the view to load properly; removing it breaks the URL.
Reference: Tableau Server Documentation - "Record Performance of a View" (https://help.tableau.com/current
/server/en-us/perf_record.htm).

NEW QUESTION # 27
A user published a workbook ten days ago. The user can see the workbook on the Server, but she is unable to find the workbook by using Search. What should you do to resolve the problem?

• A. Instruct the user to add tags to the workbook
• B. Instruct the user to re-publish the workbook with keywords
• C. Instruct the user to log out, and then log back in
• D. Run the tsm maintenance reindex-search command

Answer: D

Explanation:
Tableau Server's search functionality relies on an indexed catalog of content (workbooks, data sources, etc.) stored in the Repository. If a user can see a workbook in the UI (e.g., under Content > Workbooks) but not find it via search, the search index may be outdated or corrupted. This can happen due to:
* Indexing delays after publishing.
* Server maintenance or crashes affecting the index.
* Option D (Run the tsm maintenance reindex-search command): Correct. This command rebuilds the search index, ensuring all content (including the user's workbook) is properly cataloged and searchable. Steps:
* Stop Tableau Server (tsm stop).
* Run tsm maintenance reindex-search.
* Start Tableau Server (tsm start).This is a server administrator task and resolves systemic search issues.
* Option A (Re-publish the workbook with keywords): Incorrect. Re-publishing might update the index for that workbook, but it doesn't fix a broader indexing problem. Keywords enhance relevance, not indexing itself.
* Option B (Add tags to the workbook): Incorrect. Tags improve searchability but don't address an index failure. If the workbook isn't indexed, tags won't help.
* Option C (Log out, and then log back in): Incorrect. This refreshes the user session but doesn't affect the server-side search index.
Why This Matters: A reliable search index is critical for content discovery in large deployments-reindex- search ensures consistency.
Reference: Tableau Server Documentation - "Reindex Search" (https://help.tableau.com/current/server/en-us
/cli_maintenance_tsm.htm#reindex-search).

NEW QUESTION # 28
Which command enables an administrator to view the current values of all TSM configuration keys?

• A. tsm configuration get -k all
• B. tsm configuration list
• C. tsm configuration export
• D. tsm settings show

Answer: B

Explanation:
tsm configuration list outputs all currently configured keys and their values. tsm configuration get - k requires a specific key name (not "all" as a wildcard), and "tsm settings show" is not a valid command.

NEW QUESTION # 29
What two types of users can sign in to Tableau Server and edit the permissions for a workbook in a project, when permissions are NOT set to Locked to the project? (Choose two.)

• A. Users that have the workbook Interactor role
• B. Users that have the project and workbook Viewer role
• C. Users set to Project Leader for the workbook's project
• D. The workbook's owner

Answer: C,D

Explanation:
Editing permissions on a workbook in Tableau Server depends on the user's role and the project's permission settings. Since permissions are not locked (i.e., "Managed by Owner"), let's dissect who can edit them:
* Permission Model:
* Not Locked: Owners of content (workbooks, data sources) can set permissions, and Project Leaders can override at the project level.
* Site Roles: Define maximum capabilities (e.g., Viewer, Explorer, Creator).
* Capabilities: "Set Permissions" is explicit-only certain users get it.
* Option C (The workbook's owner): Correct.
* Details: The owner (typically the publisher) has full control over their workbook when permissions are Managed by Owner:
* How: In the UI, go to Content > Workbooks > Actions > Permissions-owners can edit rules (e.g., grant Editor to a group).
* Site Role: Minimum of Explorer (can publish) or Creator to publish, ensuring "Set Permissions" capability.
* Why: Ownership inherently includes permission management unless locked.
* Option D (Users set to Project Leader for the workbook's project): Correct.
* Details: Project Leaders are assigned via Content > Projects > Actions > Permissions > Set Project Leader:
* Power: Can edit permissions for all content in the project, even if not the owner.
* Site Role: Requires Site Administrator or Server Administrator (Creator/Explorer variants suffice).
* Why: Overrides ownership in Managed by Owner mode-ensures project-level governance.
* Option A (Users with project and workbook Viewer role): Incorrect.
* Why: Viewer role (site-level) limits users to viewing-lacks "Set Permissions" capability, regardless of project/workbook rules.
* Option B (Users with workbook Interactor role): Incorrect.
* Why: "Interactor" isn't a standard role-likely a misnomer for Explorer or Viewer with interaction permissions (e.g., Filter). No permission-editing rights exist here.
Why This Matters: Knowing who can edit permissions prevents access control gaps-crucial for collaborative or regulated environments.
Reference: Tableau Server Documentation - "Permissions" (https://help.tableau.com/current/server/en-us
/permissions.htm), "Project Leader Permissions" (https://help.tableau.com/current/server/en-us
/permissions_project_leader.htm).

NEW QUESTION # 30
What account should you use to run the Tableau Server installation program?

• A. An account in the local administrator group
• B. A domain user account
• C. A local user account
• D. An NT AUTHORITY\NetworkService account

Answer: A

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.

NEW QUESTION # 31
What is the minimum required free hard disk space recommended for a Tableau Server installation in production?

• A. 15 GB
• B. 32 GB
• C. 50 GB
• D. 64 GB

Answer: C

Explanation:
Tableau Server has specific hardware requirements for production environments to ensure stability and performance. The minimum recommended free disk space for a production installation is 50 GB.
This accounts for:
The installation itself (approximately 1-2 GB).
Space for log files, temporary files, and extracts managed by the File Store and Data Engine.
Room for backups and operational overhead.
The full minimum hardware recommendations for a single-node production deployment are:
8 CPU cores (2.0 GHz or faster).
32 GB RAM.
50 GB free disk space (on the system drive, typically C: on Windows).
Option B (50 GB): Correct. This matches Tableau's official recommendation for production environments.

NEW QUESTION # 32
Which three types of data should you backup to ensure that you can restore a Tableau Server?
(Choose three.)

• A. Repository data
• B. Topology data
• C. Server secrets and Repository passwords
• D. Configuration data

Answer: A,C,D

Explanation:
Backing up Tableau Server ensures recovery from failures or migrations. A full backup includes multiple data types--let's dissect this comprehensively:
Backup Components:
Repository Data: PostgreSQL database with metadata (users, permissions, workbooks). Backed up via tsm maintenance backup -f <filename>.tsbak.
Configuration Data: Server settings (e.g., ports, authentication) also in the .tsbak file. Server Secrets: Encryption keys, internal tokens, Repository passwords--critical for restoring functionality.
Extracts: .hyper files in File Store (optional, separate backup).
Option A (Server secrets and Repository passwords): Correct. Details: Includes encryption keys (for extracts), internal tokens (process communication), and Repository credentials. Backed up separately or stored securely (e.g., tsm security export-keys). Why Critical: Without these, restored data may be inaccessible or services may fail.
Option C (Configuration data): Correct.
Details: Ports, authentication settings, process topology--part of the .tsbak file. Why Critical:
Restores server behavior and connectivity post-recovery.
Option D (Repository data): Correct.
Details: Core metadata database--also in .tsbak.
Why Critical: Without it, all content and user data is lost.

NEW QUESTION # 33
Which two types of content can you include in comments on a visualization? (Choose two.)

• A. Images (jpg, png)
• B. @mentions
• C. Text
• D. Interactive snapshots of a view

Answer: B,C

Explanation:
Comments on Tableau Server visualizations facilitate collaboration. Let's explore what's supported:
* Comments Feature: Enabled per site (Settings > General > Allow Comments). Users with "Add Comment" permission can post on views.
* Option B (Text): Correct.
* Details: The primary content type-users type free-form text in the comment box.
* Use: Notes, questions, or feedback (e.g., "Sales spiked here-why?").
* Option C (@mentions): Correct.
* Details: Typing @username notifies the mentioned user via email or the UI (if notifications are enabled).
* Use: Directs comments to specific people (e.g., "@John, check this trend").
* Option A (Interactive snapshots of a view): Incorrect.
* Details: Snapshots (static images) aren't supported in comments-users must take screenshots externally and can't embed them interactively.
* Option D (Images - jpg, png): Incorrect.
* Details: No attachment or image embedding in comments-text and mentions only. Workaround:
Link to an image hosted elsewhere.
Why This Matters: Comments enhance teamwork, but their simplicity (text + mentions) keeps the interface lightweight and focused.
Reference: Tableau Server Documentation - "Comment on a View" (https://help.tableau.com/current/server
/en-us/comment.htm).

NEW QUESTION # 34
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. Run the tsm reset command
• B. Edit tabsvc.yml
• C. Run the tsm register command
• D. Reinstall Tableau Server

Answer: A

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).

NEW QUESTION # 35
Which two statements are advantages of published data sources in comparison to embedded data sources? (Choose two.)

• A. Centralized data management is easier
• B. Data is protected so that it is only available in one workbook
• C. Drivers are automatically installed on each client's machine
• D. Storage space is conserved and resource usage during data refreshes is optimized

Answer: A,D

Explanation:
In Tableau, data sources can be embedded (stored within a workbook) or published (stored separately on Tableau Server). Let's define these and analyze the advantages:
Embedded Data Source: The connection details and any extract are bundled in the .twb or .twbx file.
Each workbook manages its own copy.
Published Data Source: The connection or extract is hosted on Tableau Server, reusable across multiple workbooks.
Now, let's evaluate the options:
Option C (Centralized data management is easier): Correct. Published data sources allow:
Single source of truth: One data source can serve multiple workbooks, ensuring consistency.
Unified updates: Refresh schedules, permissions, and metadata (e.g., calculated fields) are managed in one place via the Server UI.
Governance: Administrators can control access and monitor usage centrally. In contrast, embedded data sources require individual updates per workbook, leading to duplication and management overhead.
Option D (Storage space is conserved and resource usage during data refreshes is optimized):
Correct. With published data sources:
Storage: A single extract on the Server (e.g., a .hyper file) is shared across workbooks, avoiding redundant copies stored in each embedded workbook.
Refreshes: One refresh job updates the shared extract, reducing CPU and memory usage compared to multiple refreshes for duplicate embedded extracts. Embedded data sources replicate extracts, increasing disk space and refresh load.

NEW QUESTION # 36
What is the minimum hardware recommendation for a single-node production installation of Tableau Server?

• A. 2-Core CPU (1.8 GHz or higher), 8 GB RAM, 15 GB free disk space
• B. 4-Core CPU (2.0 GHz or higher), 64 GB RAM, 50 GB free disk space
• C. 4-Core CPU (2.0 GHz or higher), 16 GB RAM, 50 GB free disk space
• D. 8-Core CPU (2.0 GHz or higher), 32 GB RAM, 50 GB free disk space

Answer: D

Explanation:
Tableau Server's minimum hardware recommendations for a production single-node deployment ensure reliable performance for small to medium workloads. As of the latest documentation:
CPU: 8 cores (2.0 GHz or higher) to handle concurrent users, rendering, and background tasks.
RAM: 32 GB to support in-memory processing (e.g., VizQL, Data Engine) and caching. Disk Space: 50 GB free for installation, logs, extracts, and temporary files.
Option C (8-Core CPU, 32 GB RAM, 50 GB free disk space): Correct. This matches Tableau's official minimum for production:
8 cores ensure sufficient parallelism for processes like Backgrounder and VizQL. 32 GB RAM supports multiple users and extract refreshes. 50 GB disk space accommodates growth (initial install is ~1-2 GB, but logs and extracts expand).

NEW QUESTION # 37
......

The Ultimate Salesforce Analytics-Admn-201 Dumps PDF Review: https://www.dumptorrent.com/Analytics-Admn-201-braindumps-torrent.html

Updated Verified Analytics-Admn-201 Downloadable Printable Exam Dumps: https://drive.google.com/open?id=1Ow0CHxdP_1F_oy7qKL0RcqHLr1A_Wogx