Free Salesforce-Tableau-Architect Practice Test Questions (2026)

Explanation:

Why Option B is Correct:

Base DN and search filters are mandatory for LDAP authentication in Tableau Server. They:

Locate users/groups in the LDAP directory (e.g., OU=Users,DC=example,DC=com).

Filter valid users (e.g., (objectClass=user)).

Without these, Tableau cannot authenticate users.

Reference: Tableau LDAP Setup Guide.

Why Other Options Are Irrelevant:

A) Periodic sync: Tableau syncs LDAP only at login (no background sync).

C) CPU allocation: Encryption is handled by LDAP/network, not Tableau.

D) Secondary LDAP: Optional for redundancy, not authentication.

Steps to Configure LDAP (No Code):

Navigate to Tableau Server Admin > Authentication > LDAP.

Enter:

Base DN: LDAP path (e.g., OU=Employees,DC=company,DC=com).

Search Filter: Criteria to find users (e.g., (objectClass=person)).

Test with Verify LDAP

Explanation:

Why This is the Best Strategy:

Tableau Server performance depends on underlying hardware and OS health. To optimize it, you need real-time, granular data on:

CPU usage (e.g., high utilization during peak loads).

Memory (e.g., RAM exhaustion causing slow queries).

Disk I/O (e.g., slow reads/writes during extracts).

Network activity (e.g., latency between Tableau and databases).

Built-in Tableau monitoring (Admin Views) only covers application-level metrics, not OS/hardware.

Why Other Options Fail:

A) Relying only on Tableau’s tools: Misses critical OS/hardware issues.

C) Focusing only on network: Ignores CPU/memory/disk bottlenecks.

D) Manual weekly checks: Too slow to catch real-time problems.

Recommended Tools:

General Monitoring: Prometheus, Datadog, Nagios.

Cloud-Specific: AWS CloudWatch, Azure Monitor.

On-Premises: Windows Performance Monitor, Linux sar/top.

Key Benefits of Comprehensive Monitoring:

Proactive troubleshooting (e.g., alert before disk fills up).

Capacity planning (e.g., adding RAM before usage peaks)

Compliance (audit trails for healthcare/finance).

Explanation:

Why Option C is Correct:

Installation logs (e.g., tabinstall.log, tsm.log) contain error codes and descriptive messages that pinpoint:

Missing dependencies (e.g., Java, PostgreSQL).

Permission issues (e.g., unable to write to /opt/tableau).

Configuration conflicts (e.g., port 80 already in use).

Example: A ERROR: Failed to initialize PostgreSQL log entry directs you to fix the database setup.

Reference: Tableau Server Log Files Documentation.

Why Other Options Are Incorrect:

A) User access levels:

Installation is typically done by admins—user permissions are irrelevant.

B) Network bandwidth/latency:

Rarely causes installation failures (unless downloading files, but logs won’t show this).

D) Users accessing server:

Tableau Server is not live during installation—this metric is meaningless.

How to Diagnose from Logs:

Locate logs:

Linux:/var/opt/tableau/tableau_server/logs.

Windows: C:\ProgramData\Tableau\Tableau Server\logs.

Search for keywords: ERROR, FAILED, WARNING.

Use tsm logs CLI:

Explanation:

Why This is the First Step:

Intermittent connectivity issues in a multi-node Tableau Server environment are most commonly caused by network-related problems, such as:

Firewall rules blocking the required database ports (e.g., port 5432 for PostgreSQL).

Network instability (e.g., packet loss, latency spikes between nodes).

DNS or routing misconfigurations preventing consistent communication.

Before making any infrastructure changes (like adding nodes or upgrading hardware), it’s critical to rule out network issues.

Why Other Options Are Not the First Step:

A) Increasing worker nodes:

This might help with performance but won’t fix intermittent network/database connectivity.

C) Upgrading database hardware:

Hardware issues (e.g., CPU/RAM bottlenecks) typically cause consistent slowdowns, not intermittent failures.

D) Changing the database platform:

A drastic step that should only follow confirmed incompatibilities—not the first troubleshooting action.

How to Proceed:

Check firewall settings:Ensure the database port (e.g., 5432) is open between all Tableau Server nodes and the database.

Test network connectivity: Use tools like ping or traceroute to identify latency or packet loss.

Review Tableau Server logs: Look for errors like "Connection refused" or "Timeout" in the logs (e.g., tabadmincontroller.log).

Key Takeaway:
Always start with the simplest and most likely cause (network/firewalls) before escalating to complex solutions.

Explanation:

Why Option B is Correct:

Trusted authentication in Tableau Server requires explicitly whitelisting the IP address(es) of the third-party

application. This ensures:

Only authorized systems can impersonate users (preventing spoofing).

Requests from trusted hosts bypass Tableau’s normal login prompts.

Reference: Tableau Trusted Authentication Guide.

Why Other Options Are Incorrect:

A) VPN tunnel:

Overkill—trusted auth uses IP whitelisting, not VPNs.

C) Admin privileges for all users:

Major security risk; unrelated to trusted auth.

D) Enabling CORS:

CORS controls browser-based API access, not server-to-server trusted auth.

Steps to Configure Trusted Authentication:

In Tableau Server Admin > Settings > Security, add the third-party app’s IP(s) to "Trusted Hosts".

Ensure the app sends a valid username parameter in requests.

Explanation:

Why B is Correct?

Windows Task Scheduler is a native Windows tool designed for automating script execution at predefined times or intervals.

It is lightweight, reliable, and tightly integrated with Windows, making it ideal for routine Tableau Server maintenance tasks (e.g., log cleanup, backup scripts, extract refreshes).

Supports custom triggers, conditions, and logging, ensuring scripts run without manual intervention.

Why Other Options Are Incorrect?

A) Tableau Desktop is for visual analytics, not server maintenance automation.

C) Jenkins is overkill for simple maintenance tasks—it’s better suited for CI/CD pipelines.

D) Manual execution defeats the purpose of automation, increasing human error risk.

Key Takeaway:
For Windows-based Tableau Servers, Task Scheduler is the simplest, most effective way to automate maintenance scripts.

Explanation:

Why Option B is Correct:

High load on the primary node indicates that the current setup cannot handle the workload efficiently.

Adding worker nodes allows Tableau Server to

Distribute processes (e.g., VizQL, Backgrounder) across multiple machines.

Improve scalability and fault tolerance.

Reduce bottlenecks on the primary node.

Reference: Tableau Server Scalability Guide.

Why Other Options Are Incorrect:

A) Switching OS:

Unlikely to resolve performance issues caused by hardware/resource limits.

C) Increasing bandwidth:

Helps with network congestion but not CPU/memory bottlenecks on the primary node.

D) Consolidating processes:

Worsens the problem by overloading the primary node further.

Steps to Scale with Worker Nodes:

Assess load: Use Tableau Server Admin Views to identify which processes (VizQL, Backgrounder) are overloaded.

Add nodes: Use tsm topology commands to deploy additional worker nodes.

Reassign processes: Balance VizQL/Backgrounder across nodes.

Explanation:

Why Option B is Correct:

High CPU usage at specific times often correlates with scheduled tasks like:

Extract refreshes (heavy on CPU/memory).

Subscriptions (generating/viewing reports).

Automated workflows (e.g., data pipeline integrations).

First step: Check Backgrounder jobs and schedules in Tableau Server Admin to identify the cause.

Reference: Tableau Server Monitoring Guide.

Why Other Options Are Premature/Ineffective:

A) Upgrade hardware:

Costly overreaction without confirming the root cause (e.g., poorly optimized extracts).

C) Limit user access:

Disruptive—users may need access during peak times

D) Ignore spikes:

Risky if spikes indicate inefficiencies (e.g., runaway queries).

Steps to Investigate:

Check Admin > Schedules: Identify overlapping jobs.

Optimize extracts: Reduce complexity or stagger refresh times.

Explanation:

Why Option B is Correct:

The data_connections table in the Tableau PostgreSQL repository stores metadata about:

Published data sources (e.g., connection strings, query details).

Performance metrics (e.g., query execution times, refresh status).

Usage statistics (e.g., frequency of access).

Analyzing this table helps identify:

Slow-performing data sources.

Connection bottlenecks (e.g., high latency to databases).

Reference: Tableau Repository Schema Documentation.

Why Other Options Are Less Relevant:

A) users table: Tracks user accounts, not data source performance.

C) background_tasks table: Focuses on scheduled jobs (e.g., extracts), not live data source queries.

D) server_usage table: Provides aggregate server metrics, not granular data source insights.

Key Columns in data_connections for Analysis:

query_text: Identifies slow-running queries.

last_accessed_at: Shows usage patterns.

connection_failure_count: Highlights unstable connections.

Explanation:

Why B is Correct?

Tableau Server generates detailed application logs that capture errors, warnings, and crashes specific to Tableau processes.

These logs (e.g., tabadmin.log, vizqlserver.log, backgrounder.log) help identify Tableau-specific issues (e.g., service failures, memory leaks, or configuration errors).

Since the issue is intermittent crashes, Tableau logs are the first place to check for root-cause analysis.

Why Other Options Are Less Relevant?

A. Windows Event Viewer System Logs are useful for OS-level issues (e.g., hardware failures, driver crashes) but are secondary if Tableau itself is crashing.

C. IIS Logs are only applicable if Tableau is configured with IIS (default is embedded Apache/Nginx). Even then, IIS logs track web requests, not application crashes.

D. Network Logs would help with connectivity issues but are unrelated to a server crash.

Reference:

Tableau’s official documentation on Server Log Files recommends checking logs in the C:\ProgramData\Tableau\Tableau Server\data\tabsvc\logs directory for troubleshooting crashes.

Next Steps:

Check tabadmin.log for high-level server errors.

Review vizqlserver.log for rendering-related crashes.

Look for OutOfMemory errors in backgrounder.log if background tasks are failing.