The Salesforce Certified Tableau Server Administrator certification validates your ability to install, configure, and manage Tableau Server within a Salesforce environment. The Analytics-Admn-201 exam tests both foundational knowledge and practical decision-making across deployment, data integration, and system administration tasks. This guide maps the exam syllabus, question formats, and study strategies to help you prepare efficiently. Whether you are advancing from Salesforce Certified Administrator or specializing in analytics infrastructure, this page provides the roadmap you need to succeed.
Use this topic map to guide your study for Salesforce Analytics-Admn-201 (Salesforce Certified Tableau Server Administrator) within the Salesforce Certified Administrator path.
The Analytics-Admn-201 exam combines multiple-choice questions and scenario-based items to assess both conceptual knowledge and applied reasoning in real-world Tableau Server administration.
Questions increase in difficulty and emphasize practical application; success depends on both memorization and hands-on familiarity with Tableau Server administration interfaces.
Build a structured study plan that allocates time to each topic, reinforces connections between concepts, and includes timed practice. Consistent, focused review over 4-6 weeks typically yields stronger results than cramming.
Explore other Salesforce certifications: view all Salesforce exams.
Strengthen your preparation with up-to-date resources from validexamdumps.com. These materials align to Analytics-Admn-201 and cover practical scenarios with clear explanations.
Visit the exam page to download the PDF, Online Practice Test, or get a Bundle Discount offer for both formats: Salesforce Certified Tableau Server Administrator.
Administration and Troubleshooting typically account for 40-50% of exam questions combined. These domains test your ability to manage users, permissions, and real-world system issues. Installation and Configuration and Migration & Upgrade are also important but often carry slightly less weight, so balance your study time accordingly.
In practice, these topics form a workflow: Installation and Configuration sets up the infrastructure, Connecting to and Preparing Data establishes data pipelines, Administration ensures ongoing access control and health, Troubleshooting resolves issues that arise, and Migration & Upgrade manages lifecycle changes. Understanding these connections helps you answer scenario-based questions and troubleshoot holistically rather than in isolation.
Hands-on experience with at least one Tableau Server deployment is valuable but not mandatory if you study actively. Prioritize labs that cover user provisioning, data source configuration, permission hierarchies, and log review. If possible, practice in a non-production environment so you can safely experiment with configuration changes and recovery procedures.
Candidates often confuse authentication methods (SAML vs. LDAP vs. local) or misunderstand permission inheritance in project hierarchies, leading to incorrect answers on Administration questions. Another frequent error is overlooking the importance of backup and rollback steps in Migration & Upgrade scenarios. Carefully read scenario details and avoid making assumptions; the exam tests precision.
Focus on high-weight domains (Administration and Troubleshooting) and review any questions you flagged during practice tests. Create a one-page summary of key configurations, common error messages, and troubleshooting decision trees. Do one final timed practice test 2-3 days before the exam, then spend the last day reviewing weak areas and getting adequate rest rather than learning new material.
What is the maximum number of tasks that a single Backgrounder process can execute simultaneously?
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.
What should you do to configure the view URL and enable recording for a site that has recording workbook performance metrics enabled?
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.
You have an existing group subscription. You add a user to the group. What statement correctly describes the result?
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.
What should you use to set a preferred active repository?
Tableau Server uses a PostgreSQL database as its repository to store metadata, user information, and permissions. In a high-availability (HA) setup with multiple nodes, there are typically two repository instances: one active and one passive. The 'preferred active repository' refers to designating which repository instance should take priority as the active one. This is managed through Tableau Services Manager (TSM).
The correct method to set the preferred active repository is by using the tsm configuration set command. Specifically, you would use a command like:
tsm configuration set -k pgsql.preferred_host -v <hostname>
This command allows an administrator to specify the preferred host for the active repository, ensuring control over which node takes precedence in an HA environment.
Option B (tabcmd set command) is incorrect because tabcmd is a command-line utility primarily used for administrative tasks like managing users, groups, and content (e.g., publishing workbooks), not for configuring server topology or repository settings.
Option C (TSM browser client's Maintenance page) is incorrect because the Maintenance page in the TSM web interface is used for tasks like backups, restores, and cleanup, but it does not provide an option to set the preferred active repository.
Option D (TSM browser client's Configuration Topology page) is partially relevant since the Topology page displays the current configuration of services across nodes, including the repository. However, it does not allow direct modification of the preferred active repository; this must be done via the tsm command line.
Which three methods should an administrator use to create a Tableau Server group or project? (Choose three.)
Tableau Server provides multiple methods to create groups (collections of users) and projects (content containers), catering to UI, CLI, and programmatic needs. Let's dissect each option with depth:
Option B (Tableau Server browser interface): Correct.
Groups: Go to Users > Groups > Add Group, name it, and optionally sync with Active Directory.
Projects: Go to Content > Projects > New Project, set name, description, and permissions.
Details: The web UI is intuitive, requiring server/site administrator rights. It's ideal for manual, ad-hoc creation with immediate visibility.
Permissions: For projects, you can set default permissions or lock them here.
Option C (tabcmd): Correct.
Groups: tabcmd creategroup 'GroupName' creates a local group. Add users with tabcmd addusers 'GroupName' --users 'user1,user2'.
Projects: tabcmd createproject -n 'ProjectName' -d 'Description' creates a project.
Details: tabcmd is a command-line tool for batch operations or scripting (e.g., automating group/project setup). It requires a server admin login (tabcmd login).
Limitation: No AD sync via tabcmd---that's UI or REST API territory.
Option D (REST API): Correct.
Groups: Use the POST /api/api-version/sites/site-id/groups endpoint with a payload (e.g., {'group': {'name': 'GroupName'}}). Supports AD import too.
Projects: Use POST /api/api-version/sites/site-id/projects (e.g., {'project': {'name': 'ProjectName', 'description': 'Desc'}}).
Details: The REST API is programmatic, ideal for integration with external systems or bulk automation. Requires authentication via a token and server/site admin rights.
Power: Offers full control, including nested projects and custom permissions.
Option A (tsm customize): Incorrect.
Purpose: tsm customize modifies TSM UI branding (e.g., logos, colors) via commands like tsm customize --logo 'path/to/logo.png'.
Why Wrong: It's unrelated to creating groups or projects---it's for cosmetic server configuration, not content/user management.
Why This Matters: Offering UI, CLI, and API options ensures flexibility---manual for small tasks, automation for scale---critical in enterprise deployments.
