Explanation:

Why B is Correct?

Firewall blocking ports is the most common cause of Tableau Server inaccessibility after installation.

Tableau Server requires specific ports (e.g., 80/HTTP, 443/HTTPS, 8850/TSM) to be open for client connections.

Windows Firewall (or third-party firewalls) often blocks these by default.

Tableau’s Port Requirements Documentation lists critical ports to verify.

Why Other Options Are Less Likely First Steps?

A. Reinstalling network drivers: Rarely needed unless there’s evidence of driver corruption (e.g., no network access at all).

C. Upgrading client OS: Irrelevant—client OS compatibility doesn’t prevent server access.

D. Static IP address: Helpful for stability but doesn’t resolve connectivity if ports are blocked.

Reference:

Tableau’s Firewall Configuration Guide.

Final Note:

Start with B—firewall issues account for ~80% of post-install access problems. If ports are open but issues persist, then investigate IP/DNS (D) or drivers (A).

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?

The SMTP configuration is the foundational element for email functionality in Tableau Server. If emails are not being delivered, the first and most likely culprit is an incorrect SMTP setup.

Key settings to verify:

SMTP server address (e.g., smtp.company.com or smtp.gmail.com).

Port number (e.g., 25, 465 for SSL, or 587 for TLS).

Authentication credentials (username/password for the email server).

Encryption method (TLS/SSL or none, depending on the email server).

Tableau Server cannot send emails if these settings are misconfigured, even if everything else is correct.

Why Other Options Are Less Likely?

A. Email content/formatting: This affects how emails look but doesn’t prevent delivery entirely.

C. Upgrading the email server: Unless the email server is extremely outdated (rare), compatibility issues are unlikely.

D. Changing the OS: Tableau Server on Linux supports standard SMTP protocols. Switching the OS is an extreme measure and unrelated to email delivery.

Reference:

Tableau’s official documentation: Configuring Email for Tableau Server (Linux).

Final Note:

Always start with SMTP configuration (B)—it resolves 90% of email delivery issues. If emails still fail, investigate: Firewall rules blocking SMTP traffic.

DNS resolution problems.

Email server-side issues (e.g., rate limiting, blacklisting).

Explanation:

Why C is Correct?

Security and accuracy are critical when using Web Data Connectors (WDCs), as they interact with external data sources.

Secure data transfer (via HTTPS/TLS) prevents interception or tampering during transit.

Proper authentication (e.g., OAuth, API keys) ensures only authorized access to data sources.

Efficient data handling avoids performance bottlenecks or corruption during extraction.

Tableau’s WDC Security Guidelines emphasize these practices.

Why Other Options Are Incorrect?

A. Hosting WDCs on the same server: Unnecessary and restrictive—WDCs can be hosted externally if secured properly.

B. Blindly updating WDCs: Risky—updates should be tested for compatibility and stability first.

D. Prohibiting third-party connectors: Overly restrictive—many trusted third-party WDCs exist (e.g., Salesforce, Google Analytics).

Key Steps for Secure WDC Configuration:

Use HTTPS for all WDC endpoints (no HTTP).

Validate WDC code for vulnerabilities (e.g., SQL injection, excessive data exposure).

Monitor WDC performance to ensure efficient data transfer.

Restrict WDC permissions to only necessary data sources.

Reference:

Tableau’s WDC Best Practices highlights secure data handling as a priority

. Final Note:

C is the only balanced approach—security and efficiency are mandatory, while flexibility (A/B/D extremes) can compromise safety or usability. Always audit third-party WDCs before deployment.

Explanation:

Why C is Correct?

OAuth is the industry-standard protocol for secure API access, providing token-based authentication without exposing credentials.

It enables:

Fine-grained access control (scopes/permissions).

Revocable tokens (reduce risk if compromised).

Auditability (track API usage by application).

Tableau’s Metadata API Security Guide mandates OAuth for external integrations.

Why Other Options Are Incorrect?

A. Unrestricted access: A major security risk—exposes metadata to unauthorized parties.

B. Real-time updates: Not a security consideration (and not always feasible due to performance impacts).

D. Direct database access: Bypasses Tableau’s security model—never grant direct DB access for metadata.

Key Steps for Secure Metadata API Access:

Register external apps in Tableau Server’s OAuth settings.

Define scopes (e.g., read:metadata) to limit permissions.

Rotate secrets/tokens regularly.

Reference:

OAuth 2.0 Best Practices (RFC 6749).

Final Note:

C is the only secure approach. Options A/B/D either ignore security (A/D) or confuse functionality with access control (B). Always use OAuth for APIs.