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

Explanation:

Why B is Correct?

Tableau Server logs (e.g., tabadmin.log, tabsvc.log, backgrounder.log) are the primary source for startup issues, capturing:

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

Repository database connection failures (PostgreSQL).

Permission issues (e.g., file access, user rights).

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

Why Other Options Are Secondary?

A. Kernel logs: Only relevant for hardware/os-level crashes (rarely the cause).

C. Web server logs: Useful for post-startup web errors (e.g., vizqlserver issues), not startup.

D. Network logs: Startup failures occur before external data source connections are attempted.

Reference:

Tableau’s Log File Locations.

Final Note:

B is the fastest path to resolution. Options A/C/D are unlikely to reveal startup-specific failures. Always check logs before hardware/network.

Explanation:

Why B is Correct?

Slow queries in Tableau are most often caused by:

Complex calculations (e.g., nested IFs, LODs).

Inefficient data relationships (e.g., unnecessary joins, Cartesian products).

Optimization steps:

Simplify calculations (use Boolean logic, CASE statements).

Ensure proper indexing in the database.

Use query filters to limit data.

Tableau’s Performance Checklist recommends this as the first step.

Why Other Options Are Less Immediate?

A. Restructuring the database: Overkill unless the issue is confirmed to be database-side (e.g., missing indexes).

C. Pre-aggregated data: Useful but sacrifices granularity—optimize the original source first.

D. Increasing extract refreshes: Doesn’t fix query inefficiencies.

Reference:

Tableau’s Optimizing Data Sources Guide.

Final Note:

B is the most targeted fix. Options A/C/D are workarounds, not root-cause solutions. Always profile queries before restructuring.

Explanation:

Why B is Correct?

1. Small startups with limited IT resources need a simple, low-maintenance solution.
2. Tableau’s local identity store requires no additional infrastructure (like LDAP or SAML) and is easy to set up.
3. Admins can manage users directly in Tableau Server without dependencies on external systems.
4. Cost-effective (no need for enterprise identity providers like Okta or Azure AD).

Reference:
Tableau’s Authentication Overview recommends local identity for small deployments.

Why Other Options Are Incorrect?

A) LDAP adds unnecessary complexity for a small team (overkill for current needs).
C) Enterprise identity providers (e.g., SAML/OAuth) are expensive and require expertise.
D) Separate credentials hurt user adoption (increases friction and password fatigue).

Key Takeaway:

For startups, Tableau’s built-in authentication balances simplicity and security. Scale to LDAP/SAML later if needed.

Explanation:

Why A is Correct?

Active-active mode ensures high availability (HA) and minimal downtime by

Real-time replication: Both servers synchronize data (e.g., extracts, permissions) continuously.

Automatic failover: If the primary fails, the secondary takes over seamlessly.

Tableau’s Disaster Recovery Guide recommends this for mission-critical deployments.

Why Other Options Are Insufficient?

B. Nightly same-server backups: Risk losing a day’s data and don’t reduce downtime.

C. Manual weekly backups: Too slow—businesses need real-time recovery.

D. Cloud-only backups: Lacks failover capability—restores take hours.

Key Components of Automated DR:

Multi-node cluster:

Primary + standby nodes (configured via tsm topology).

Regular DR drills:

Test failover quarterly.

Reference:

NIST SP 800-34 on disaster recovery.

Final Note:

A is the only zero-downtime solution. Options B/C/D risk data loss or prolonged outages. Always validate failover in staging.

Explanation:

Why B is Correct?

Comprehensive testing is critical when migrating between OSes because:

Data source drivers (e.g., ODBC, JDBC) may behave differently on Linux.

Performance bottlenecks (e.g., CPU/memory usage) can vary due to OS-level optimizations.

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

Why Other Options Are Incorrect?

A. Skipping connection tests: Risks broken dashboards due to driver/network issues.

C. Migrating only popular dashboards: Leaves users without critical content.

D. Changing the database platform: Unnecessary—Tableau’s repository works on both PostgreSQL (default) and SQL Server.

Key Steps for a Stable Migration:

Test in a staging environment:

Validate all data sources (live/extracts), permissions, and schedules.

Benchmark performance:

Compare dashboard load times between Windows and Linux.

Update connection strings:

Ensure Linux-compatible paths (e.g., /opt/tableau vs. C:\Program Files).

Reference:

Tableau’s Linux Migration Checklist.

Final Note:

B is the only method ensuring stability. Options A/C/D risk disruptions or incomplete migrations. Always document test results.

Explanation:

Why B is Correct?

TabJolt simulates real-world usage to identify performance bottlenecks. Testing diverse actions (e.g., dashboard views, extracts, subscriptions) ensures:

Accurate load modeling: Mimics actual user workflows, not just peak stress.

Balanced resource assessment: Reveals issues across VizQL, Backgrounder, and Data Server processes.

Tableau’s Load Testing Guide emphasizes realistic user simulations.

Why Other Options Are Less Effective?

A. Installing on the same machine: Skews results (avoids network latency, which is part of real-user experience).

C. Testing only heavy dashboards: Overlooks systemic issues (e.g., login storms, concurrent queries).

D. Limiting to low-activity periods: Misses peak-load scenarios critical for capacity planning.

Steps for Effective TabJolt Testing:

Define user personas:

Mix of viewers, creators, and admins.

Script common actions:

Dashboard interactions, extract refreshes, publishes.

Ramp up gradually:

Start with 50 users, scale to expected peak.

Reference:

TabJolt’s GitHub Documentation.

Final Note:

B is the only method reflecting real usage. Options A/C/D distort results or miss critical scenarios. Always validate with production metrics.

Explanation:

Why C is Correct?

Mutual SSL (mTLS) requires both parties (client and server) to present trusted certificates for authentication. This ensures:

Server identity validation: Clients verify the server’s certificate.

Client identity validation: Server verifies the client’s certificate.

Without certificates on both ends, mutual authentication fails.

Tableau’s SSL Configuration Guide mandates this for mTLS.

Why Other Options Are Incorrect?

A. Port forwarding: Unrelated to SSL—it’s a network routing feature.

B. Admin privileges on devices: Irrelevant—mTLS uses certificates, not local user rights.

D. Cipher suites: Important for encryption strength but secondary to certificate setup.

Steps to Configure Mutual SSL:

Obtain certificates:

Server: From a public CA (e.g., DigiCert) or internal PKI.

Clients: Issue client certs via your CA.

Distribute client certificates:

Deploy via MDM (e.g., Intune) or manually.

Reference:

NIST SP 800-52 on TLS/SSL best practices.

Final Note:

C is the only mandatory step for mTLS. Options A/B/D address tangential concerns. Always test with a pilot group before rollout.

Explanation:

Why Option B is Correct:

Enterprise-scale deployment requires centralized control for:

Automated installations/updates (reducing IT overhead).

License management (ensuring compliance).

Security policies (e.g., enforcing TLS, disabling auto-updates).

Tools like Microsoft Intune, SCCM, or Jamf (for macOS) are industry-standard for this purpose.

Reference: Tableau Enterprise Deployment Guide.

Why Other Options Are Incorrect:

A) Individual downloads:

Unmanageable at scale (version control, security risks).

C) Emailing installers:

Security hazard (risk of tampering, version inconsistency).

D) Shared network drive:

No automation (users may skip updates or install incorrectly).

Key Steps for Automated Deployment:

Package Tableau (MSI for Windows, PKG for macOS).

Distribute via Intune/SCCM with:

Silent install flags (e.g., /quiet).

Pre-configured settings (license keys, proxies).

Enforce updates via patch management..

Explanation:

Why B is Correct?

OAuth token issues are the most common cause of Azure AD authentication failures in Tableau Server. Key checks:

Token expiration: Tokens typically expire after 1 hour (adjustable in Azure AD).

Correct scopes: Ensure tokens include openid, profile, and email.

Signature validation: Mismatched signing keys (e.g., after Azure AD certificate rotation).

Tableau’s Azure AD Troubleshooting Guide lists token validation as step one.

Why Other Options Are Secondary?

A. Network bandwidth: Rarely an issue—Azure AD auth is lightweight (KB-sized tokens).

C. Firewall settings: Only check if Azure AD endpoints (e.g., login.microsoftonline.com) are blocked.

D. Azure AD module version: Tableau Server uses standard OAuth/SAML protocols—no Azure-specific modules.

Reference:

Microsoft’s Token Validation Guide.

Final Note:

B is the fastest path to resolution. Options A/C/D are unlikely culprits unless token checks pass. Always audit token lifetimes in Azure AD.

Explanation:

Why Option B is Correct:

Cache optimization in Tableau Server balances performance (reduced query load) with data freshness.

Clearing the cache on a schedule (e.g., after ETL jobs refresh source data) ensures:

Performance benefits of cached queries.

Data consistency by invalidating stale cache entries.

Reference: Tableau Server Performance Tuning Guide.

Why Other Options Are Incorrect:

A) Refresh cache on every view load:
Defeats the purpose of caching (no performance gain).

C) Disabling caching:
Forces real-time queries, increasing server load and latency.

D) Increasing RAM:
Helps caching but doesn’t address cache invalidation logic.

Key Cache Settings in Tableau Server:

vizqlserver.session.expiry.timeout: Controls how long cached sessions persist.

Backgrounder tasks: Schedule cache clears post-data-refresh.