[Mar-2026] Salesforce Analytics-Admn-201 Exam: Basic Questions With Answers
New 2026 Realistic Free Salesforce Analytics-Admn-201 Exam Dump Questions and Answer
NEW QUESTION # 21
What is the minimum hardware recommendation for a single-node production installation of Tableau Server?
- A. 4-Core CPU (2.0 GHz or higher), 16 GB RAM, 50 GB free disk space
- B. 2-Core CPU (1.8 GHz or higher), 8 GB RAM, 15 GB free disk space
- C. 4-Core CPU (2.0 GHz or higher), 64 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.
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 # 22
What process decides when a Repository failover is required?
- A. Backgrounder
- B. Cluster Controller
- C. Coordination Service
- D. Gateway
Answer: B
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 # 23
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 Serial
- D. Set Execution to Parallel
Answer: C
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 # 24
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 regenerate-internal-tokens
- C. tsm security validate-asset-keys
- D. tsm data-access caching set -r 1
Answer: B
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 # 25
You need to verify the status of the Coordination Service ensemble in a high-availability (HA) Tableau Server cluster. What should you do?
- A. Run the command tsm maintenance ziplogs
- B. Examine the Tableau Server Status page
- C. Run the command tsm status -v
- D. Examine the Tableau Services Manager (TSM) web client Status page
Answer: C
Explanation:
In an HA Tableau Server cluster, the Coordination Service (ZooKeeper ensemble) maintains cluster state- let's find the best way to check it:
* Coordination Service:
* Runs on multiple nodes (3 or 5 in HA) to ensure quorum and failover.
* Status indicates if it's running and synced-critical for cluster health.
* Option C (Run tsm status -v): Correct.
* Details: tsm status --verbose lists all processes across nodes, including Coordination Service (e.
g., "Coordination Service: RUNNING").
* Why Best: Provides detailed, node-specific status in the CLI-e.g., "Node 1: RUNNING, Node
2: RUNNING."
* Use: Run on the initial node; -v ensures full output.
* Option A (TSM web client Status page): Incorrect.
* Why: The TSM UI (Server > Status) shows process counts (e.g., "Coordination Service: 3 instances"), but not detailed per-node status-less granular than CLI.
* Option B (tsm maintenance ziplogs): Incorrect.
* Why: Generates log archives for troubleshooting, not a real-time status check.
* Option D (Tableau Server Status page): Incorrect.
* Why: The Server Status page (Server > Status in the web UI) monitors application processes (e.
g., VizQL), not TSM's Coordination Service.
Why This Matters: Coordination Service health ensures HA stability-tsm status -v is the admin's go-to for precision.
Reference: Tableau Server Documentation - "Check Server Status" (https://help.tableau.com/current/server/en- us/tsm_status.htm).
NEW QUESTION # 26
What event is most likely to cause problems for a Tableau Server?
- A. Using a non-default installation path
- B. Separating the Backgrounder and VizQL processes to different machines
- C. Configuring the server to use a static IP address
- D. Running additional software on the server
Answer: D
Explanation:
Tableau Server's performance and stability depend on dedicated resources and proper configuration. Running additional software on the same server is the most likely to cause problems because:
* Resource contention: Tableau Server requires significant CPU, RAM, and disk I/O. Other software (e.
g., databases, web servers) can compete for these resources, leading to slowdowns, crashes, or failed tasks.
* Port conflicts: Tableau uses specific ports (e.g., 80, 443, 8850), and other applications might interfere.
* Security risks: Additional software increases the attack surface, potentially compromising Tableau Server.
Tableau recommends running the server on dedicated hardware without unrelated applications.
* Option A (Running additional software on the server): Correct. This is a common cause of performance issues and is explicitly discouraged in Tableau's best practices.
* Option B (Separating the Backgrounder and VizQL processes to different machines): Incorrect.
This is a supported multi-node configuration that can improve performance, not cause problems, if properly set up via TSM.
* Option C (Configuring the server to use a static IP address): Incorrect. A static IP is recommended for Tableau Server to ensure consistent network access, so it's unlikely to cause issues.
* Option D (Using a non-default installation path): Incorrect. While not default, a custom path is supported (via TSM or installer options) and unlikely to cause problems if permissions and disk space are adequate.
Reference: Tableau Server Documentation - "Best Practices for Installation" (https://help.tableau.com/current
/server/en-us/install_best_practices.htm).
NEW QUESTION # 27
A user named John publishes a workbook named Sales Quota to a project named Sales. The All Users group has the View and Download Workbook/Save As capabilities only to the Sales project. A user named Sandy has the Explorer (can publish) site role, on the Sales Quota workbook. No other users or groups have permissions to the Sales project. The Sales project is set to Managed by the owner. What are the effective rights for Sandy?
- A. All of the capabilities associated with the Editor rule
- B. View and Download Workbook/Save As
- C. The same rights as John
- D. No access
Answer: B
NEW QUESTION # 28
Which Tableau Server process performs the role of a database for metadata?
- A. File Store
- B. Data Engine
- C. Backgrounder
- 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 # 29
What is the maximum number of tasks that a single Backgrounder process can execute simultaneously?
- A. Three
- B. Two
- C. Unlimited (based on server resources)
- D. One
Answer: D
Explanation:
The Backgrounder process in Tableau Server handles tasks like extract refreshes and subscriptions-let's explore its concurrency:
* Backgrounder Behavior:
* Each instance is single-threaded for task execution-one task at a time per Backgrounder.
* Multiple Backgrounders (e.g., in multi-node setups) increase parallelism, but a single Backgrounder is limited to 1 concurrent task.
* Queue: Additional tasks wait in the queue, prioritized by their priority (1-100).
* Option A (One): Correct.
* Details: A single Backgrounder executes one task (e.g., an extract refresh) until completion before starting the next.
* Config: Add more Backgrounders via TSM (tsm topology set-process -n node1 -pr backgrounder
-c 2) for more concurrency.
* Option B (Two): Incorrect.
* Why: Not natively supported-a single Backgrounder doesn't multi-thread tasks.
* Option C (Three): Incorrect.
* Why: Exceeds the single-threaded design.
* Option D (Unlimited): Incorrect.
* Why: Concurrency is fixed at 1 per instance-resources affect queue processing speed, not simultaneous tasks.
Why This Matters: Understanding Backgrounder limits guides scaling-more instances mean more parallel tasks, critical for heavy workloads.
Reference: Tableau Server Documentation - "Backgrounder Process" (https://help.tableau.com/current/server
/en-us/processes.htm#backgrounder).
NEW QUESTION # 30
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 # 31
Which three data sources support Kerberos delegation with Tableau Server? (Choose three.)
- A. PostgreSQL
- B. SAP HANA
- C. SQL Server
- D. Teradata
Answer: B,C,D
Explanation:
Kerberos delegation allows Tableau Server to pass a user's Kerberos credentials to a data source for seamless authentication (SSO)-let's explore which sources support it:
* Kerberos Overview:
* Used with Active Directory (AD) for SSO in Windows environments.
* Tableau Server delegates the user's ticket to the data source, avoiding embedded credentials.
* Requires:
* Data source support for Kerberos.
* Proper configuration (e.g., SPN, constrained delegation).
* Supported Data Sources: Per Tableau's documentation:
* Option A (Teradata): Correct.
* Details: Supports Kerberos delegation-common in enterprise data warehouses.
* Config: Enable in TSM (tsm authentication kerberos configure) and set SPN for Teradata.
* Option C (SQL Server): Correct.
* Details: Fully supports Kerberos-widely used with AD-integrated SQL Server instances.
* Config: Requires AD setup and "Trustworthy" delegation in SQL Server.
* Option D (SAP HANA): Correct.
* Details: Supports Kerberos SSO via delegation-popular in SAP ecosystems.
* Config: Needs HANA Kerberos setup (e.g., keytab) and Tableau Server integration.
* Option B (PostgreSQL): Incorrect.
* Why: Supports Kerberos authentication natively, but Tableau Server doesn't enable delegation to PostgreSQL-users must embed credentials or use other methods (e.g., OAuth).
Why This Matters: Kerberos delegation enhances security by avoiding stored passwords-knowing supported sources ensures SSO feasibility.
Reference: Tableau Server Documentation - "Kerberos Delegation" (https://help.tableau.com/current/server
/en-us/kerberos_delegation.htm), "Supported Connectors" (https://help.tableau.com/current/server/en-us
/datasource.htm).
NEW QUESTION # 32
What file format should you use to register Tableau Server from the command line?
- A. HTTP
- B. JSON
- C. XML
- D. YML
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 # 33
Which two options can be configured by a server administrator per site? (Choose two.)
- A. Language and locale
- B. Ability to embed credentials
- C. Limitation on storage space
- D. Limitation on number of users
Answer: A,C
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 # 34
Which two types of content can you include in comments on a visualization? (Choose two.)
- A. Interactive snapshots of a view
- B. Images (jpg, png)
- C. Text
- D. @mentions
Answer: C,D
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 # 35
Which three items can be contained in a project? (Choose three.)
- A. Nested Projects
- B. Data Sources
- C. Workbooks
- 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
......
Guaranteed Success in Salesforce Administrator Analytics-Admn-201 Exam Dumps: https://realtest.free4torrent.com/Analytics-Admn-201-valid-dumps-torrent.html