Explanation:

Why Option D is Correct:

Role-based access control (RBAC) is critical for multinational corporations with diverse needs:

Creators: Data analysts/scientists (need full access to build/workbooks).

Explorers: Power users (edit dashboards but not data sources).

Viewers: Read-only access for stakeholders.

Custom roles (via Tableau Server/Cloud) can further restrict row-level security (RLS) or project access.

Reference: Tableau Roles and Permissions Guide.

Why Other Options Are Incorrect:

A) All "Viewers":

Too restrictive (blocks self-service analytics).

B) Only department heads as "Creators":

Bottlenecks innovation (team members may need Explorer/Creator rights).

C) Uniform "Explorers":

Over-provisions access (e.g., finance vs. marketing needs differ).

Implementation Steps:

Audit departments (e.g., Finance: "Creators" for models, "Viewers" for execs).

Leverage groups in Tableau Server/Cloud for bulk role assignments.

Apply RLS for data-level restrictions.

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?

Redirection URI mismatches are the most common cause of OpenID Connect (OIDC) failures.

The exact URI (including protocol https://, path, and trailing slashes) must match identically in:

The OIDC provider’s app registration (e.g., Azure AD, Okta).

Tableau Server’s OIDC configuration (tsm authentication oidc).

Even minor discrepancies (e.g., http:// vs. https:// or missing /) will break authentication.

Why Other Options Are Less Likely?

A. Load balancing: Relevant for general server performance but unrelated to OIDC’s authentication flow.

C. SSL encryption strength: OIDC requires HTTPS, but failures are due to configuration errors, not certificate strength.

D. Token storage capacity: Rarely an issue—Tableau Server handles token caching efficiently.

Steps to Verify the Redirection URI:

Compare with the OIDC provider’s settings:

Ensure URIs match exactly (e.g., https://tableau.example.com/oidc/callback).

Test authentication: Use browser developer tools to check for redirect_uri errors.

Reference:

Tableau’s OIDC Troubleshooting Guide lists URI mismatches as the top issue.

OpenID Connect RFC 6749 mandates exact redirect URI matching.

Final Note:

Always start with B—90% of OIDC issues stem from URI mismatches. If resolved, then check SSL (C) or provider logs.

Explanation

When Tableau Server performance is slow through a web proxy, the first troubleshooting step is to examine the proxy configuration.

Why B is correct:

1. Web proxies can impose bandwidth throttling, content filtering, or caching rules that impact performance.
2. Checking and adjusting these settings is a non-disruptive initial step and can quickly identify if the proxy is the bottleneck.
3. Disabling the proxy or reinstalling the server should be done only after confirming whether the proxy itself is responsible.

Why not the others?

A. Disabling the web proxy
This might help identify the cause, but it’s more intrusive than first checking settings. If the proxy is needed for security/compliance, disabling it might not be possible.

C. Reinstalling Tableau Server
Reinstallation is not an initial troubleshooting step. Performance issues through a proxy are rarely due to the Tableau Server installation itself.

D. Configuring Tableau Server to use an alternative port
Changing ports is not the standard first step unless the issue is clearly port-specific. This is more of a targeted fix after isolating the problem.

Reference
Tableau Help: Configure Proxies and Load Balancers

Key point from docs: "If users experience delays or slow load times when connecting through a proxy, check proxy settings such as caching, bandwidth limits, and filtering."

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.