Verified & Correct Analytics-Admn-201 Practice Test Reliable Source May 23, 2026 Updated
Free Salesforce Analytics-Admn-201 Exam Files Downloaded Instantly
NEW QUESTION # 15
What is the minimum required free hard disk space recommended for a Tableau Server installation in production?
- A. 50 GB
- B. 15 GB
- C. 32 GB
- D. 64 GB
Answer: A
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 A (32 GB): Incorrect. While 32 GB is the minimum RAM requirement, it's insufficient for disk space in production.
* Option B (50 GB): Correct. This matches Tableau's official recommendation for production environments.
* Option C (15 GB): Incorrect. 15 GB is the minimum for a non-production or trial installation, not production.
* Option D (64 GB): Incorrect. While 64 GB exceeds the minimum, it's not the specified requirement-
50 GB is sufficient.
Reference: Tableau Server Documentation - "Minimum Hardware Recommendations" (https://help.tableau.
com/current/server/en-us/requirements.htm).
NEW QUESTION # 16
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 for the Tableau Server administrator
- C. An account with a Creator site role
- 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 # 17
Which three types of data should you backup to ensure that you can restore a Tableau Server? (Choose three.)
- A. Repository data
- B. Server secrets and Repository passwords
- C. Topology data
- D. Configuration data
Answer: A,B,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.
* Option B (Topology data): Incorrect.
* Details: Topology (process distribution) is part of configuration data in the .tsbak, not a separate entity. It's not distinctly backed up as "topology data." Why This Matters: A complete backup (secrets, config, repository) ensures full restoration-missing any piece risks an unusable server.
Reference: Tableau Server Documentation - "Back Up Tableau Server Data" (https://help.tableau.com/current
/server/en-us/backup_restore.htm).
NEW QUESTION # 18
What should you do to configure the view URL and enable recording for a site that has recording workbook performance metrics enabled?
- A. Delete the session ID in the URL and reload the view
- B. Type :record_performance=yes& at the end of the view URL, immediately before the session ID
- C. Type :record_performance=yes& at the end of the view URL, immediately after the session ID
- D. Click the Performance link in the toolbar at the top of the view
Answer: C
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 # 19
What are two intervals when Tableau Server verifies if data conditions for data-driven alerts are true? (Choose two.)
- A. Whenever a new extract is published
- B. Whenever extracts in the related workbook are refreshed
- C. Every 60 minutes
- D. Every 10 minutes
Answer: B,C
Explanation:
Data-driven alerts notify users when data meets conditions (e.g., sales > $10K). Let's examine when Tableau checks these:
* Alert Mechanics:
* Enabled per site (Settings > General > Data-Driven Alerts).
* Backgrounder evaluates conditions against extract data.
* Check Intervals: Configurable via tsm configuration set -k dataAlerts.checkIntervalInMinutes (default: 60 minutes).
* Refresh Trigger: Also checks post-extract refresh for immediate updates.
* Option A (Every 60 minutes): Correct.
* Details: Default interval-Backgrounder polls every hour to evaluate alert conditions.
* Config: Adjustable (e.g., -v 30 for 30 minutes).
* Option D (Whenever extracts in the related workbook are refreshed): Correct.
* Details: An extract refresh updates the data, triggering an immediate alert check to catch changes promptly.
* Why: Ensures timely notifications without waiting for the next poll.
* Option B (Every 10 minutes): Incorrect.
* Why: Not the default-possible via config, but not standard.
* Option C (Whenever a new extract is published): Incorrect.
* Why: Publishing creates the extract; alerts trigger on refreshes or polling, not initial publication.
Why This Matters: Timing affects alert responsiveness-balancing frequency and server load is key.
Reference: Tableau Server Documentation - "Data-Driven Alerts" (https://help.tableau.com/current/server/en- us/data_alerts.htm).
NEW QUESTION # 20
Which two operating systems are supported for a Tableau Server installation? (Choose two.)
- A. Windows Server 2016
- B. Windows 7
- C. Windows Server 2019
- D. Windows 10
Answer: A,C
Explanation:
Tableau Server is designed for production environments and is supported only on server-class operating systems, not desktop operating systems. As of the latest documentation (aligned with knowledge up to March
21, 2025), the supported operating systems for Tableau Server on Windows are:
Windows Server 2016
Windows Server 2019
Windows Server 2022 (added in later versions, but relevant as of 2025).
Desktop operating systems like Windows 7 or Windows 10 are not supported for production installations due to stability, security, and performance requirements.
Option A (Windows 7): Incorrect. Windows 7 is a desktop OS and is not supported for Tableau Server. It's also end-of-life as of January 2020.
Option B (Windows 10): Incorrect. Windows 10 is a desktop OS and not supported for production Tableau Server deployments, though it may be used for testing in non-production scenarios.
Option C (Windows Server 2019): Correct. This is a supported server OS for Tableau Server.
Option D (Windows Server 2016): Correct. This is also a supported server OS for Tableau Server.
Reference: Tableau Server Documentation - "System Requirements for Tableau Server" (https://help.tableau.
com/current/server/en-us/requirements.htm).
NEW QUESTION # 21
What are two features of the Tableau Server user-based license? (Choose two.)
- A. A perpetual license
- B. Enables distinct user roles
- C. A subscription license
- 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 # 22
What two events must occur for Tableau Server to recompute queries for a workbook cache after a scheduled refresh? (Choose two.)
- A. The workbook was published in the last month
- B. The workbook has upcoming scheduled refresh tasks
- C. The All Users group has a permission rule allowing access to the workbook
- D. The workbook has been viewed recently
Answer: B,D
Explanation:
Tableau Server uses caching to speed up workbook loading by storing query results. After a scheduled extract refresh updates the data, the cache may need recomputing-let's dive into the mechanics:
* Caching Basics:
* VizQL Cache: Stores rendered views and query results for faster access.
* Refresh Trigger: A scheduled refresh updates the underlying extract (.hyper), but the cache isn't automatically invalidated-it's demand-driven.
* Recompute Conditions: Tableau recomputes the cache when the workbook is accessed (viewed) and its data has changed (e.g., via refresh).
* Evaluation:
* Option B (The workbook has upcoming scheduled refresh tasks): Correct.
* Why: An upcoming refresh task indicates the workbook relies on an extract with a schedule. After the refresh runs, the data changes, priming the cache for recomputation on next view. Without a schedule, no refresh occurs, so this is a prerequisite.
* Detail: Schedules are set in Schedules > Tasks-e.g., "Daily at 2 AM."
* Option D (The workbook has been viewed recently): Correct.
* Why: Viewing triggers cache recomputation if the data has changed (e.g., post-refresh).
Tableau uses a "lazy caching" model-cache updates only when a user loads the workbook, ensuring fresh results.
* Detail: "Recently" isn't strictly defined but implies post-refresh access.
* Option A (Published in the last month): Incorrect.
* Why: Publish date is irrelevant-cache recomputation ties to data changes and access, not publication timing.
* Option C (All Users group has permission rule allowing access): Incorrect.
* Why: Permissions enable viewing, but recomputation requires actual access (viewing) and a refresh event, not just potential access.
Why This Matters: Caching balances performance and freshness-understanding triggers prevents stale data surprises.
Reference: Tableau Server Documentation - "Caching and Performance" (https://help.tableau.com/current
/server/en-us/perf_cache.htm).
NEW QUESTION # 23
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. The workbook's owner
- C. Users set to Project Leader for the workbook's project
- D. Users that have the project and workbook Viewer role
Answer: B,C
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 # 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
What should you do to ensure that server tasks associated with a particular schedule run one-at-a-time?
- A. Set Frequency to Hourly
- B. Set Default priority to 0
- C. Set Execution to Parallel
- D. Set Execution to Serial
Answer: D
Explanation:
In Tableau Server, schedules manage tasks such as extract refreshes and subscriptions. The execution mode of a schedule determines how tasks within that schedule are processed by the Backgrounder process:
* Parallel: Tasks run simultaneously (up to the Backgrounder's capacity), which is the default setting.
* Serial: Tasks run one-at-a-time in sequence, ensuring that one task completes before the next begins.
To ensure tasks associated with a particular schedule run one-at-a-time, you must configure the schedule's execution mode to Serial. This is done in the Tableau Server web interface:
* Go to Schedules.
* Select the schedule, click Actions > Edit Schedule.
* Under Execution, choose Serial instead of Parallel.
* Option A (Set Execution to Serial): Correct. This directly addresses the requirement by forcing tasks to execute sequentially.
* Option B (Set Default priority to 0): Incorrect. Priority (1-100) determines the order of task execution across all schedules, not whether tasks run one-at-a-time within a single schedule. Also, 0 is not a valid priority value (minimum is 1).
* Option C (Set Frequency to Hourly): Incorrect. Frequency (e.g., hourly, daily) controls when the schedule runs, not how tasks within it are executed.
* Option D (Set Execution to Parallel): Incorrect. Parallel execution allows tasks to run simultaneously, which contradicts the requirement.
Reference: Tableau Server Documentation - "Create or Modify a Schedule" (https://help.tableau.com/current
/server/en-us/schedule_manage_create.htm).
NEW QUESTION # 26
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 Server Status page
- B. Run the command tsm maintenance ziplogs
- C. Examine the Tableau Services Manager (TSM) web client Status page
- D. Run the command tsm status -v
Answer: D
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).
NEW QUESTION # 27
Which three types of authentications can you use to implement single-sign-on (SSO) authentication to Tableau Server? (Choose three.)
- A. OpenID Connect
- B. Security Assertion Markup Language (SAML)
- C. Kerberos with Active Directory
- D. Local Authentication
Answer: A,B,C
Explanation:
Single Sign-On (SSO) allows users to authenticate once (e.g., via a corporate identity provider) and access Tableau Server without re-entering credentials. Tableau Server supports several SSO methods:
* OpenID Connect (OIDC): An OAuth 2.0-based protocol for SSO, configured via Tableau's SAML settings with an OIDC-compatible IdP (e.g., Google, Okta).
* Kerberos with Active Directory: A ticket-based SSO protocol, widely used in Windows environments with AD integration.
* SAML: A flexible SSO standard using XML assertions, supporting various IdPs (e.g., ADFS, PingFederate).
Let's evaluate:
* Option A (OpenID Connect): Correct. OIDC is an SSO method, implemented as a SAML variant in Tableau Server, enabling seamless login.
* Option C (Kerberos with Active Directory): Correct. Kerberos provides SSO in AD environments, delegating authentication to the domain controller.
* Option D (Security Assertion Markup Language - SAML): Correct. SAML is a core SSO method in Tableau, widely adopted for enterprise integrations.
* Option B (Local Authentication): Incorrect. Local Authentication uses Tableau's internal user database, requiring manual credential entry-no SSO support.
Why This Matters: SSO enhances user experience and security by leveraging existing identity systems, reducing password fatigue.
Reference: Tableau Server Documentation - "Authentication" (https://help.tableau.com/current/server/en-us
/auth_overview.htm).
NEW QUESTION # 28
What file format should you use to register Tableau Server from the command line?
- A. XML
- B. JSON
- C. YML
- D. HTTP
Answer: B
Explanation:
Registering Tableau Server from the command line involves providing configuration details (e.g., identity store, license) via the tsm register command. Let's explore this fully:
* Registration Process:
* Run during initial setup or to update settings (e.g., after changing AD/LDAP config).
* Uses a configuration file to pass parameters to TSM.
* Command: tsm register --file <path-to-file>.
* File Format:
* Tableau Server uses JSON for configuration files in TSM commands like tsm register.
* Example:
json
CollapseWrapCopy
{
"identityStore": {
"type": "local",
"domain": "example.com"
}
}
* JSON is structured, machine-readable, and aligns with Tableau's modern CLI design.
* Option C (JSON): Correct.
* Official format for tsm register, per documentation and practical use.
* Option A (YML): Incorrect.
* While tabsvc.yml exists internally, it's not for registration-tsm register uses JSON.
* Option B (XML): Incorrect.
* Older Tableau configs used XML (e.g., workgroup.yml pre-TSM), but TSM standardized on JSON.
* Option D (HTTP): Incorrect.
* HTTP is a protocol, not a file format-irrelevant here.
Why This Matters: Correct file format ensures seamless registration, avoiding CLI errors in setup or migrations.
Reference: Tableau Server Documentation - "tsm register" (https://help.tableau.com/current/server/en-us
/cli_register.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 and all of the user's content is deleted
- C. The user is deleted, and the user's content is reassigned to the project leader
- D. The user is deleted, and the user's content is reassigned to the server administrator
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 process enables you to access Tableau Services Manager (TSM) over HTTPS?
- A. Administration Controller
- B. Administration Agent
- C. Coordination Service
- D. License Manager
Answer: A
Explanation:
TSM is Tableau Server's management layer, accessible via CLI or web UI (port 8850). HTTPS secures this access-let's identify the responsible process:
* TSM Architecture:
* Administration Controller: Core TSM process, running on the initial node, handling configuration, UI, and CLI commands.
* HTTPS: Enabled by default on port 8850 with a self-signed certificate (configurable to custom certs).
* Option B (Administration Controller): Correct.
* Details: Hosts the TSM web UI (https://<server>:8850) and processes CLI requests. It manages the HTTPS listener, serving the interface securely.
* Why: It's the central hub for TSM operations, including secure access.
* Option A (License Manager): Incorrect.
* Why: Validates licenses, not responsible for HTTPS or UI access.
* Option C (Administration Agent): Incorrect.
* Why: Runs on additional nodes in multi-node setups to relay commands to the Controller-no direct HTTPS role.
* Option D (Coordination Service): Incorrect.
* Why: ZooKeeper manages cluster state, not TSM's web interface or HTTPS.
Why This Matters: Secure TSM access protects server administration-Administration Controller is the linchpin.
Reference: Tableau Server Documentation - "TSM Overview" (https://help.tableau.com/current/server/en-us
/tsm_overview.htm).
NEW QUESTION # 31
What is the minimum hardware recommendation for a single-node production installation of Tableau Server?
- A. 4-Core CPU (2.0 GHz or higher), 64 GB RAM, 50 GB free disk space
- B. 8-Core CPU (2.0 GHz or higher), 32 GB RAM, 50 GB free disk space
- C. 2-Core CPU (1.8 GHz or higher), 8 GB RAM, 15 GB free disk space
- D. 4-Core CPU (2.0 GHz or higher), 16 GB RAM, 50 GB free disk space
Answer: B
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.
Let's break it down:
* 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).
* Option A (4-Core, 16 GB RAM, 50 GB): Incorrect. Too low for production-4 cores and 16 GB RAM are below the threshold for reliable performance under load.
* Option B (2-Core, 8 GB RAM, 15 GB): Incorrect. This is for non-production (e.g., trial) setups, insufficient for production stability.
* Option D (4-Core, 64 GB RAM, 50 GB): Incorrect. 4 cores are inadequate, though 64 GB RAM exceeds the minimum (32 GB).
Why This Matters: Under-spec hardware can lead to slow performance, failed refreshes, or crashes in production-adhering to the minimum ensures stability.
Reference: Tableau Server Documentation - "Minimum Hardware Recommendations" (https://help.tableau.
com/current/server/en-us/requirements.htm).
NEW QUESTION # 32
What command should you run to update the automatically-generated secrets that are created during a Tableau Server installation?
- A. tsm licenses refresh
- B. tsm security validate-asset-keys
- C. tsm data-access caching set -r 1
- D. tsm security regenerate-internal-tokens
Answer: D
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 # 33
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. Run the tsm register command
- C. Reinstall Tableau Server
- D. Edit tabsvc.yml
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 # 34
What process decides when a Repository failover is required?
- A. Cluster Controller
- B. Backgrounder
- C. Coordination Service
- D. Gateway
Answer: A
Explanation:
In a high-availability (HA) Tableau Server setup, the Repository (PostgreSQL) has an active and passive instance. Failover occurs if the active Repository fails. Let's dive into the process:
* HA Setup:
* Two Repository instances across nodes (active/passive).
* Failover switches to the passive instance if the active one becomes unavailable (e.g., crash, network issue).
* Cluster Controller:
* Role: Monitors all processes (e.g., Repository, File Store) across nodes, detecting failures via heartbeats and status checks.
* Failover Decision: If the active Repository stops responding, Cluster Controller initiates failover, promoting the passive instance to active.
* Coordination: Works with Coordination Service (ZooKeeper) to update topology but makes the initial detection call.
* Option A (Cluster Controller): Correct.
* Why: It's the watchdog process, constantly monitoring Repository health and triggering failover when needed.
* Option B (Coordination Service): Incorrect.
* Role: ZooKeeper maintains cluster state and coordinates topology updates post-failover, but doesn't detect the failure-Cluster Controller does.
* Option C (Gateway): Incorrect.
* Role: Routes client requests-unrelated to internal process monitoring or failover.
* Option D (Backgrounder): Incorrect.
* Role: Executes background tasks-no involvement in Repository failover decisions.
Why This Matters: Understanding failover ensures HA reliability-Cluster Controller is the linchpin for resilience.
Reference: Tableau Server Documentation - "High Availability" (https://help.tableau.com/current/server/en-us
/ha.htm).
NEW QUESTION # 35
You have an existing group subscription. You add a user to the group. What statement correctly describes the result?
- A. The subscription will continue to include only the members of the group at the time the subscription was made
- B. The subscription updates automatically to include the new user
- C. The administrator receives a notice to approve or deny adding the user to the subscription
- D. The creator of the subscription receives notice of the change and must manually edit the subscription to reflect the new group membership
Answer: B
Explanation:
Subscriptions in Tableau Server deliver workbook views to users via email on a schedule. Group subscriptions apply to all group members-let's unpack this:
* Group Subscription Mechanics:
* Created via Workbooks > Actions > Subscribe > Select Group.
* Delivers content to all users in the group at the time the subscription runs (e.g., daily PDF).
* Dynamic: Membership updates (additions/removals) are reflected automatically on the next run.
* Option C (The subscription updates automatically to include the new user): Correct.
* Details: When you add a user to the group (e.g., via Users > Groups > Add Users), Tableau Server's subscription process queries the group's current membership at runtime. The new user receives the subscription on the next scheduled delivery-no manual action needed.
* Example: Group "Sales" has a 9 AM subscription. Add a user at 8 AM-they get the email tomorrow at 9 AM.
* Option A (Admin receives notice to approve/deny): Incorrect.
* Why: No approval workflow exists for group membership changes in subscriptions-it's automatic.
* Option B (Creator must manually edit): Incorrect.
* Why: Subscriptions are tied to the group, not a static user list-manual edits aren't required for membership changes.
* Option D (Only members at creation time): Incorrect.
* Why: This would be true for individual subscriptions (static list), but group subscriptions are dynamic.
Why This Matters: Dynamic group subscriptions streamline content delivery as teams evolve, reducing admin overhead.
Reference: Tableau Server Documentation - "Manage Subscriptions" (https://help.tableau.com/current/server
/en-us/subscribe.htm).
NEW QUESTION # 36
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 default priority of this schedule to 50
- C. Set the priority of this task to 100
- 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 # 37
Which Tableau Server process performs the role of a database for metadata?
- A. File Store
- B. Backgrounder
- C. Data Engine
- D. Repository
Answer: D
Explanation:
Tableau Server relies on several processes to function, each with a specific role. The Repository process (powered by PostgreSQL) serves as the database for metadata, storing critical information such as:
* User and group details.
* Permissions and site configurations.
* Workbook and data source metadata (e.g., schedules, subscriptions).
* Option B (Repository): Correct. The Repository is the centralized database that holds all metadata, making it the backbone of Tableau Server's content management. There are typically two instances in an HA setup (one active, one passive), monitored by the Cluster Controller.
* Option A (Data Engine): Incorrect. The Data Engine manages in-memory data processing and extract storage (e.g., .hyper files), not metadata. It's separate from the Repository.
* Option C (Backgrounder): Incorrect. The Backgrounder handles background tasks like extract refreshes and subscriptions, but it doesn't store metadata-it interacts with the Repository to retrieve task details.
* Option D (File Store): Incorrect. The File Store manages physical extract files and workbook assets, not metadata, which is stored in the Repository.
Reference: Tableau Server Documentation - "Tableau Server Processes" (https://help.tableau.com/current
/server/en-us/processes.htm).
NEW QUESTION # 38
......
Salesforce Analytics-Admn-201 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
Pass Salesforce Analytics-Admn-201 exam Dumps 100 Pass Guarantee With Latest Demo: https://www.exams-boost.com/Analytics-Admn-201-valid-materials.html