Explanation:

Why B is Correct?

SAML assertions are time-sensitive and typically valid for only a few minutes.

If the clocks on Tableau Server and the SAML identity provider (IdP) are not synchronized, authentication fails with errors like "Invalid timestamp" or "Assertion expired."

Tableau’s SAML Troubleshooting Guide lists this as a primary check.

Why Other Options Are Incorrect?

A. Network bandwidth: SAML exchanges are lightweight (KB-sized); latency rarely causes failures.

C. Storage capacity: Irrelevant—SAML operates via HTTP requests, not disk storage.

D. Browser version: While browsers must support SAML, mismatches usually cause clear errors (e.g., "Unsupported protocol").

Reference:

SAML 2.0 Core Specification (Section 2.3.2 on time conditions).

Final Note:

B is the most common SAML failure point. Always confirm time sync before investigating deeper (A/C/D).

Explanation

For maximum data security in a Tableau Server deployment, two encryption layers are required:

1. Encryption over the wire (in transit):
Achieved by enabling SSL/TLS for Tableau Server so all communications between clients, browsers, Tableau Desktop, and the server are encrypted.

2. Encryption at rest:
Protects stored data such as extracts, repository data, and backups.
In Tableau Server, you can enable at-rest encryption for extracts, repository, and file store (available in certain editions and versions).

Why C is correct:

It’s the only option that covers both types of encryption—this ensures compliance with strict financial data regulations (e.g., PCI-DSS, SOX, GLBA).

Why not the others?

A. Enabling only SSL/TLS → Secures transit but leaves data at rest vulnerable.

B. External file storage without encryption → Data at rest is exposed if the storage is compromised.

D. Network-level encryption only → Relies on external network controls but does not secure stored files or server-to-server comms natively.

Reference:

Tableau Help: Encrypt Extracts at Rest
Tableau Help: Configure SSL for Tableau Server
From Tableau docs: "Tableau Server supports encryption for data in transit with SSL/TLS, and encryption at rest for extracts and repository data."

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?

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 B is Correct?

Air-gapped environments are isolated from external networks (no internet access).
Tableau Server updates must be:
1. Manually downloaded from Tableau’s official site on a connected machine.
2. Vetted for security/compliance before being transferred via secure offline methods (e.g., USB, internal network).

This ensures control over updates and prevents unauthorized changes.

Reference:
Tableau’s Offline Installation Guide outlines steps for air-gapped deployments.

Why Other Options Are Incorrect?

A) Impossible—air-gapped systems cannot connect to the internet for real-time updates.
C) Automatic updates require internet access, violating air-gapped security.
D) Satellite connections defeat the purpose of air-gapping (physical isolation is mandatory for high-security environments).

Key Takeaway:
Air-gapped systems require manual, controlled update processes to maintain security and compliance.