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

Explanation:

Why C is Correct?

A scalable deployment model (e.g., multi-node cluster for Tableau Server or Tableau Cloud) is critical for a rapidly growing retail company because it:

Handles increasing users: More stores/employees = more concurrent dashboard viewers.

Supports larger datasets: Sales, inventory, and customer data grow over time.

Adapts to seasonal spikes: Black Friday, holidays, etc.

Tableau’s Scalability Guide recommends planning for 2–3x current needs.

Why Other Options Are Incorrect?

A. Limiting users: Stifles business growth—scalability means supporting more users, not fewer.

B. Ignoring future growth: Leads to costly re-architecting later (e.g., migrating from single-node to cluster).

D. Single server: A single point of failure—cannot handle nationwide scale.

Scalable Deployment Options:

Tableau Server (Multi-Node Cluster):

Distribute workloads (VizQL, Backgrounder) across nodes.

Use load balancers for high availability.

Tableau Cloud:

Automatically scales with usage (managed by Tableau).

Hybrid (Server + Cloud):

Use Cloud for peak demand, Server for sensitive data.

Reference:

Tableau’s Enterprise Deployment Guide.

Final Note:

C is the only future-proof choice. Options A/B/D risk outages or stagnation. Always benchmark performance and plan for growth.

Explanation:

Why B is Correct?

Tableau Server includes built-in log management tools (e.g., tabadmin log, tsm maintenance ziplogs, Admin Views) designed for efficient log collection and analysis.

Targeted log review during peak issue times (e.g., slow dashboards, crashes) helps pinpoint root causes faster.

Automated tools like Tableau Server's "Log Shipper" can forward logs to centralized systems (e.g., Splunk, ELK) for deeper analysis.

Tableau’s Logging Documentation recommends this approach.

Why Other Options Are Incorrect?

A. Storing logs only for critical errors: Misses context needed to diagnose intermittent or performance-related issues.

C. Manual daily collection: Inefficient and risks missing real-time data—logs should be gathered proactively when issues arise.

D. Relying solely on third-party tools: Tableau’s native tools understand log structure best; third-party tools should complement, not replace them.

Best Practices for Log Analysis:

Use tsm maintenance ziplogs to collect all relevant logs in one bundle.

Filter logs by timestamp during reported issues (e.g., grep "ERROR" vizqlserver.log).

Monitor Admin Views (e.g., "Background Tasks" or "Performance") to correlate logs with server metrics.

Reference:

Tableau’s Troubleshooting Guide highlights log collection as step one.

Final Note:

B is the most effective strategy—leveraging built-in tools ensures accuracy and timeliness. Options A/C/D either limit data or add unnecessary complexity.

Explanation:

Why B is Correct?

Compatibility testing is critical because:

Newer Tableau versions may introduce changes that break existing dashboards (e.g., deprecated functions, rendering differences).

Data source connections (e.g., drivers, SQL syntax) might behave differently.

Tableau’s Migration Guide mandates testing to avoid post-migration failures.

Why Other Options Are Incorrect?

A. Migrating without testing: Risks unplanned downtime due to broken content.

C. Ignoring data/content: Renders the migration pointless—users need their dashboards!

D. Upgrading the old server first: Unnecessary—migrating to a new server avoids in-place upgrade risks.

Steps for a Successful Migration:

Test key dashboards in the new environment:

Verify calculations, filters, and data sources.

Check driver compatibility:

Ensure databases (e.g., SQL Server, PostgreSQL) work with the new version.

Use a staging environment:

Mirror production to validate performance.

Reference:

Tableau’s Pre-Migration Checklist.

Final Note:

B is the only method ensuring business continuity. Options A/C/D risk outages or incomplete migrations. Always document test results and train users on changes.

Explanation:

Tableau Data Management Add-On for better data preparation and governance The Tableau Data Management Add-On provides tools for effective data preparation and strong data governance, which is crucial for an organization with a large user base to maintain data integrity and compliance. Option A is incorrect as Tableau Bridge focuses on live data connections and not specifically on data management and governance. Option C is incorrect because the Tableau Mobile App Bootcamp is about mobile access, not data governance. Option D is incorrect because while Tableau Prep Conductor is part of the Data Management Add-On, it alone does not cover the full scope of data management and governance needs.

Explanation:

Why B is Correct?

The data_connections table in the Tableau repository (PostgreSQL database) logs:

Who accessed which published data source (user IDs, timestamps).

Connection details (e.g., queries, durations).

This is the primary source for tracking user interactions with data sources.

Tableau’s Repository Schema Documentation highlights this table for data source analytics.

Why Other Options Are Less Relevant?

A. users table: Lists users but doesn’t track their data source interactions.

C. background_tasks table: Only shows extract refreshes, not live queries.

D. server_usage table: Provides high-level metrics (e.g., logins) but not granular data source access.

Reference:

Tableau’s Admin Views Guide.

Final Note:

B is the only table with direct interaction data. Options A/C/D lack the granularity needed. Always join with users/datasources for context.

Explanation:

Why B is Correct?

tabadmin.log and tabsvc.log are the primary logs for Tableau Server startup issues. They record:

Service initialization errors (e.g., missing dependencies, port conflicts).

Repository connection failures (PostgreSQL/SQL Server).

Permission denials (e.g., file access, service account rights).

Tableau’s Troubleshooting Guide directs admins to these logs first.

Why Other Options Are Secondary?

A. Antivirus logs: Only check if you suspect AV blocking (rarely the root cause).

C. SQL Server logs: Relevant only if the repository uses SQL Server (default is PostgreSQL).

D. User access logs: Unrelated to startup failures.

Reference:

Tableau’s Log File Guide.

Final Note:

B is the fastest path to resolution. Options A/C/D are situational and unlikely to reveal startup failures. Always check logs before guessing.

Explanation:

Why C is Correct?

Network shared storage (e.g., NFS, SMB, or cloud storage like S3) is required for an external file store because:

All Tableau Server nodes must access the same files (e.g., extracts, backups).

Centralized storage ensures consistency across the cluster.

Tableau’s External File Store Guide mandates this setup.

Why Other Options Are Incorrect?

A. FTP access: Tableau Server cannot use FTP for its file store (only shared storage protocols).

B. SSL for Tableau Server: Secures data in transit but doesn’t enable file store access.

D. Increasing virtual memory: Unrelated—file store access depends on network permissions, not RAM.

Key Steps for External File Store Setup:

Configure shared storage:

NFS/SMB: Mount the share on all nodes at the same path (e.g., /mnt/tableau).

Cloud (S3, Azure Blob): Use Tableau’s cloud storage integration.

Set permissions:

Ensure the Tableau service account has read/write access.

Reference:

Tableau’s Cluster Storage Requirements.

Final Note:

C is the only solution that ensures cluster-wide access. Options A/B/D misrepresent technical requirements. Always test connectivity from all nodes.

Explanation:

Why A is Correct?

Proactive maintenance requires real-time alerts to:

Prevent outages: Notify admins before CPU/memory/disk thresholds are breached (e.g., 90% CPU usage).

Optimize resources: Scale nodes or adjust processes (e.g., VizQL, Backgrounder) preemptively.

Tableau’s Monitoring Guide prioritizes threshold-based alerts.

Why Other Options Are Reactive or Incomplete?

B. Monthly historical analysis: Too slow—issues must be caught before they impact users.

C. Monitoring only popular content: Misses bottlenecks in less-used but critical processes (e.g., subscriptions).

D. Manual log reviews: Inefficient and delayed—automated alerts are faster.

Key Metrics to Alert On:

CPU/memory usage (per process: VizQL, Data Server).

Disk space (for extracts, logs).

Failed tasks (extract refreshes, subscriptions).

Reference:

Tableau’s Alert Configuration Guide.

Final Note:

A is the only proactive approach. Options B/C/D are either too slow or too narrow. Always test alerts in staging first!

Explanation:

Why B is Correct?

Views per month is a direct measure of user engagement because:

It shows how often users interact with dashboards (e.g., 10,000 views = high engagement).

Helps identify popular vs. underused content for optimization.

Tableau’s Admin Insights highlights this as a key engagement metric.

Why Other Options Are Less Relevant?

A. Disk space: Tracks storage, not engagement.

C. Uptime/downtime: Measures reliability, not user activity.

D. Network traffic: Reflects data volume, not engagement quality.

Additional Engagement Metrics to Include:

Unique users: Distinguish active vs. inactive accounts.

Average session duration: Longer sessions = deeper engagement.

Subscriptions/alerts: Shows proactive usage.

How to Build the Dashboard:

Query the workbooks and views tables in Tableau’s repository.

Visualize trends:

Views by department, time of day, or dashboard type.

Reference:

Tableau’s Usage Metrics Guide.

Final Note:

B is the most actionable for engagement. Options A/C/D are operational metrics. Pair with user feedback for context.

Explanation:

Why B is Correct?

Average load time is the most critical health metric because it directly reflects:

Server performance: Slow load times indicate CPU/memory bottlenecks, inefficient queries, or network issues.

User experience: Delays frustrate users and reduce adoption.

Tableau’s Performance Monitoring Guide prioritizes this metric.

Why Other Options Are Secondary?

A. Total views: Measures engagement, not health (a fast server can have low views).

C. Login/logout frequency: Tracks activity, not performance.

D. Extract failures: Important but niche—doesn’t reflect overall health.

Key Health Metrics to Include:

Load times (per dashboard/data source).

System resources (CPU, memory, disk I/O).

Failed background jobs (extracts, subscriptions).

Implementation Steps:

Use Tableau’s Admin Views:

Navigate to Admin → Performance → View Load Times.

Set thresholds: Alert if load times exceed 5 seconds (baseline varies by complexity).

Reference:

Tableau’s Admin Insights Documentation.

Final Note:

B is the most actionable health metric. Options A/C/D are useful but don’t diagnose performance issues. Pair with error rates for full context.