Analytics-Admn-201 Dumps (2026) Prepare Your Exam With 82 Questions
New Analytics-Admn-201 Dumps - Real Salesforce Exam Questions
Salesforce Analytics-Admn-201 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
NEW QUESTION # 48
Several Tableau Server users published workbooks that have large extracts. After several weeks of use, the users abandoned the workbooks. What should you do to identify the abandoned workbooks?
- A. Delete all extracts and allow them to be re-generated automatically if they are still in use
- B. View all workbooks, and sort by the Modified date
- C. Examine the extract files in ProgramData/Tableau/Tableau Server/data/tabsvc/dataengine/extract
- D. Use the Stale Content administrative view
Answer: D
Explanation:
Abandoned workbooks--those no longer actively used--can clutter Tableau Server and consume resources (e.g., disk space for extracts). Identifying them efficiently requires leveraging built-in administrative tools rather than manual or destructive methods. Let's explore this in depth:
Tableau Server Admin Views: Tableau provides pre-built administrative views to monitor server health, usage, and content. The Stale Content view, accessible under Server > Status > Administrative Views, is specifically designed to identify content (workbooks, data sources) that hasn't been viewed or modified recently. It shows:
Content name, owner, and project.
Last viewed date and last modified date.
View count over a period.
This view uses Repository data to track usage metrics, making it ideal for spotting abandoned workbooks.
Option A (Use the Stale Content administrative view): Correct. This is the most efficient and non- invasive method. You can filter by last viewed date (e.g., >30 days ago) to identify workbooks with large extracts that users have stopped accessing. From there, you can contact owners or delete the content if policy allows. It's a server administrator's go-to tool for content management.
NEW QUESTION # 49
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. 8-Core CPU (2.0 GHz or higher), 32 GB RAM, 50 GB free disk space
- C. 4-Core CPU (2.0 GHz or higher), 64 GB RAM, 50 GB free disk space
- D. 2-Core CPU (1.8 GHz or higher), 8 GB RAM, 15 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 # 50
Which Tableau Server process performs the role of a database for metadata?
- A. Repository
- B. Backgrounder
- C. Data Engine
- D. File Store
Answer: A
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.
NEW QUESTION # 51
Which three types of authentications can you use to implement single-sign-on (SSO) authentication to Tableau Server? (Choose three.)
- A. OpenID Connect
- B. Local Authentication
- C. Security Assertion Markup Language (SAML)
- D. Kerberos with Active Directory
Answer: A,C,D
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).
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.
NEW QUESTION # 52
What file format should you use to register Tableau Server from the command line?
- A. JSON
- B. HTTP
- C. XML
- D. YML
Answer: A
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 # 53
What should you do to ensure that server tasks associated with a particular schedule run one-at- a- time?
- A. Set Execution to Serial
- B. Set Execution to Parallel
- C. Set Default priority to 0
- D. Set Frequency to Hourly
Answer: A
NEW QUESTION # 54
Which two settings should you configure to allow users to post comments on a visualization?
(Choose two.)
- A. The relevant users must have a minimum site role of Explorer (can publish)
- B. Add Comments must be allowed in permissions for the relevant users
- C. Comments must be enabled on the site Settings page
- D. Comments must be enabled on the server Settings page
Answer: B,C
Explanation:
Comments on visualizations foster collaboration in Tableau Server--let's break down the requirements:
Commenting Prerequisites:
Site-Level Enablement: Comments must be activated for the site. Permission: Users need the
"Add Comment" capability on the content. Site Role: Minimum role of Viewer allows commenting if permissions are set.
Option B (Add Comments must be allowed in permissions): Correct. Details: In the Permissions dialog (e.g., for a workbook), set "Add Comment" to "Allowed" for users/groups. Default is
"Denied" unless explicitly enabled. How: Content > Workbooks > Actions > Permissions > Edit Rule. Why: Permissions are granular--site enablement alone isn't enough.
Option D (Comments must be enabled on the site Settings page): Correct. Details: Go to Site > Settings > General > Allow Comments--check the box. Why: This is a site-wide toggle (default:
off). Without it, no one can comment, regardless of permissions.
NEW QUESTION # 55
Which action requires a server restart or at minimum applying pending changes via TSM?
- A. Changing a TSM configuration key such as SMTP settings
- B. Adding a new user to a site
- C. Creating a new project
- D. Publishing a new workbook
Answer: A
Explanation:
Configuration changes made with tsm configuration set are staged and require tsm pending- changes apply (which may restart affected services) to take effect. Content and user- management actions like creating projects, adding users, or publishing workbooks take effect immediately without any TSM changes.
NEW QUESTION # 56
An administrator needs to restore Tableau Server to a new machine after a hardware failure.
Which two files are required? (Choose two.)
- A. The tsm settings export (JSON) file
- B. The tabcmd.exe executable
- C. The .tsbak backup file
- D. The server log archive
Answer: A,C
Explanation:
A full disaster recovery requires the .tsbak file (containing repository and file store data, created via tsm maintenance backup) and the exported configuration/topology settings file (tsm settings export), which is imported on the new server before restoring the backup. tabcmd and log archives are not part of the restore process.
NEW QUESTION # 57
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. Run the tsm maintenance reindex-search command
- C. Instruct the user to re-publish the workbook with keywords
- D. Instruct the user to log out, and then log back in
Answer: B
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.
NEW QUESTION # 58
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 All Users group has a permission rule allowing access to the workbook
- C. The workbook has upcoming scheduled refresh tasks
- D. The workbook has been viewed recently
Answer: C,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 # 59
A site has multiple projects with nested sub-projects. Where are default permission rules for content type set?
- A. At each individual project or sub-project level
- B. Only at the top-level (root) project
- C. Only through tabcmd, not the web UI
- D. Default permissions cannot be customized per project
Answer: A
Explanation:
Each project -- including nested sub-projects -- can define its own default permission rules per content type (workbooks, data sources, flows, etc.), which apply to new content published within it, independent of the parent project's settings unless "Lock" is applied.
NEW QUESTION # 60
What command should you run to update the automatically-generated secrets that are created during a Tableau Server installation?
- A. tsm security regenerate-internal-tokens
- B. tsm data-access caching set -r 1
- C. tsm security validate-asset-keys
- D. tsm licenses refresh
Answer: A
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 # 61
Which three types of authentications can you use to implement single-sign-on (SSO) authentication to Tableau Server? (Choose three.)
- A. OpenID Connect
- B. Local Authentication
- C. Security Assertion Markup Language (SAML)
- D. Kerberos with Active Directory
Answer: A,C,D
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 # 62
Which tsm command is used to change the port on which Tableau Server's Gateway process listens?
- A. tsm topology set-port -v <port>
- B. tsm gateway configure -port <port>
- C. tsm network set -k port
- D. tsm configuration set -k gateway.port -v <port>
Answer: D
Explanation:
The Gateway process's listening port is a configuration key modified with tsm configuration set -k gateway.port -v <port>, followed by tsm pending-changes apply to activate it. The other commands are not valid TSM syntax.
NEW QUESTION # 63
What should you use to set a preferred active repository?
- A. The TSM browser client's Maintenance page
- B. A tsm configuration set command
- C. The TSM browser client's Configuration Topology page
- D. A tabcmd set command
Answer: B
Explanation:
Tableau Server uses a PostgreSQL database as its repository to store metadata, user information, and permissions. In a high-availability (HA) setup with multiple nodes, there are typically two repository instances: one active and one passive. The "preferred active repository" refers to designating which repository instance should take priority as the active one. This is managed through Tableau Services Manager (TSM).
The correct method to set the preferred active repository is by using the tsm configuration set command. Specifically, you would use a command like:
tsm configuration set -k pgsql.preferred_host -v <hostname>
This command allows an administrator to specify the preferred host for the active repository, ensuring control over which node takes precedence in an HA environment.
NEW QUESTION # 64
Which two statements are advantages of published data sources in comparison to embedded data sources? (Choose two.)
- A. Data is protected so that it is only available in one workbook
- B. Drivers are automatically installed on each client's machine
- C. Centralized data management is easier
- D. Storage space is conserved and resource usage during data refreshes is optimized
Answer: C,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 # 65
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 for the Tableau Server administrator
- B. An account with administrative rights to the computer
- C. An account with a Creator site role
- D. An account with a Site Administrator role
Answer: B
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.
NEW QUESTION # 66
Which authentication method allows users to sign in to Tableau Server using credentials from an external identity provider via SAML?
- A. Single Sign-On (SSO) via SAML
- B. Local authentication
- C. Trusted authentication
- D. Kerberos delegation
Answer: A
Explanation:
SAML-based SSO integrates Tableau Server with an external Identity Provider (IdP) so users authenticate once and gain access without separate Tableau credentials. Local authentication uses Tableau's own credential store; trusted authentication is used for embedding without prompting for login; Kerberos delegation supports single sign-on to underlying data sources, not initial server login.
NEW QUESTION # 67
Which of the following is true regarding Tableau Server's default site?
- A. All server administrators must use only the default site
- B. It cannot be deleted or renamed
- C. It can be renamed but not deleted
- D. It can be deleted if another site is set as default
Answer: C
Explanation:
The Default site is created automatically during installation and cannot be deleted, though its name can be changed. This is unlike additional sites, which administrators can freely create, rename, or delete.
NEW QUESTION # 68
......
Get Ready with Analytics-Admn-201 Exam Dumps: https://www.testkingpdf.com/Analytics-Admn-201-testking-pdf-torrent.html
Dependable Analytics-Admn-201 Exam Dumps to Become Salesforce Certified: https://drive.google.com/open?id=1R5RZ6f8xrCafvEz2bs-CSl8-p7bVeNuR
