Explanation

When you sign in to a specific Tableau Server site from Tableau Desktop, the list of available published data sources is governed by two main factors: the site boundary and your user permissions. You are restricted to seeing resources (data sources, workbooks, etc.) published only to that particular site. Furthermore, you will only see those resources for which your user account has been granted at least view/connect permission.

✅ Correct Option: C
All the data sources published to the site within the folders to which you have access
This option is correct because it acknowledges both key limitations:

Published to the site:
Tableau Server/Cloud can host multiple independent sites. Signing into one site means you cannot see data sources published to other sites.

To which you have access:
Data source visibility is strictly controlled by permissions. If a data source is published to the site but your user account does not have permission to view or connect to it (often managed at the project/folder level), it will not appear in your search results.

❌ Incorrect Options

A. All the data sources published to the site
This is incorrect because it ignores the crucial factor of permissions. Even if a data source is on the site, you won't see it if you lack the necessary "Connect" or "View" permission for that data source or the folder it resides in.

B. All the data sources published to the Tableau Server
This is incorrect because it ignores the concept of sites. A single Tableau Server instance can host multiple, distinct sites. Signing into Site A does not allow you to see data sources published to Site B.

D. All the data sources published to the Tableau Server within the folders to which you have access
This is incorrect for the same reason as option B: it ignores the site boundary. You are only guaranteed to see resources within the specific site you signed into, regardless of your permissions on other sites within the same physical server.

📖 Reference
Tableau Official Documentation: Permissions and Content Access
Source: Tableau Help: Content Permissions (Search for "Tableau Server data source permissions and visibility" on the official Tableau website)

Note: The official documentation confirms that users only see content on the specific site they are logged into, and content visibility is further restricted by the explicit permissions set on that content.

Explanation

This question tests your understanding of how to perform a grouped calculation that is independent of the visual layout. The requirement is to find the first (minimum) purchase date for each customer, even when the Customer ID is not present in the view. This is a classic use case for a Level of Detail (LOD) expression in Tableau. A FIXED LOD expression computes a value using the specified dimensions (here, [Customer ID]) regardless of what is in the view, which is precisely what is needed to solve this problem .

✅ Correct Option

A. { FIXED [Customer ID] : MIN([Purchase Date]) }
This is the correct syntax for a FIXED Level of Detail expression in Tableau. The part before the colon, [Customer ID], defines the dimension at which the calculation will be performed. The part after the colon, MIN([Purchase Date]), is the aggregate calculation. Together, this expression instructs Tableau to find the earliest purchase date for each Customer ID, and this value will be available in the visualization even when the Customer ID field is removed from the view.

❌ Incorrect Options

B. MIN([Purchase Date])
This is a simple table calculation or measure aggregation. Without being grouped by [Customer ID] in the view, this function would not calculate the date per customer. Instead, it would return the single earliest [Purchase Date] found across the entire dataset, which is not the requested outcome. It lacks the grouping logic required to segment the result by each individual customer.

C. [Customer ID] : { [Purchase Date] }
This syntax is completely invalid in Tableau. It incorrectly places the dimension outside the LOD curly braces and, more critically, omits any aggregate function (like MIN, MAX, or AVG). An LOD expression must always include an aggregation to be meaningful. Tableau's calculation engine would reject this structure due to these fundamental syntax and logical errors.

D. [Customer ID] : MIN([Purchase Date])
This is not a recognized syntax for any calculation type in Tableau. While it attempts to imply a relationship between the dimension and the measure, it is missing the essential components of a valid LOD expression (the curly braces {} and a keyword like FIXED) and is also not a standard grouped calculation, which would typically be defined using the INCLUDE or EXCLUDE keywords or simply by dragging dimensions to the view.

📝 Summary
To find the first purchase date per customer independent of the view's dimensions, a FIXED LOD expression is required. Option A uses the correct syntax to compute the minimum purchase date for each customer ID, which will persist even when Customer ID is filtered out of the view.

🔗 Reference
For the definitive guide on this topic, please consult the "Create Level of Detail Expressions" section in the official Tableau Documentation.

Explanation

When the requirement is for data that is "as close to real-time as possible," a live connection is inherently superior to a scheduled extract refresh. Since the data is stored in a cloud-based database, a live connection from Tableau Cloud is feasible, provided the necessary network security (like the firewall) is correctly configured to allow the connection. This setup ensures that every dashboard interaction queries the most current data directly from the source.

✅ Correct Option: C

Create a connection to the database using Tableau Desktop. Publish the data source to Tableau Cloud using a live connection, ensuring the database firewall has been configured to allow connections from Tableau Cloud.
This option is ideal for real-time needs. A live connection is the only way to get data immediately upon being recorded, avoiding the delay of scheduled extracts. Publishing this live connection to Tableau Cloud makes it accessible to end-users. The crucial step is configuring the database firewall to explicitly authorize the specific IP addresses or domain of Tableau Cloud, ensuring a secure and reliable data flow.

❌ Incorrect Options

A. Create a connection to the database using Tableau Desktop. Publish the data source to Tableau Cloud using a live connection and disable any firewalls on the database.
This option correctly identifies the need for a live connection but suggests a highly insecure practice: disabling firewalls. While disabling a firewall would allow the connection, it severely compromises the security of the underlying database, making the entire system vulnerable. Security best practices mandate allowing connections only from specific, necessary sources (like Tableau Cloud), not disabling the firewall entirely.

B. Create a connection to the database to retrieve the data using Tableau Bridge. Schedule the refresh of the data extract to 15 minutes.
This approach uses a data extract and a 15-minute refresh schedule, which directly contradicts the "as close to real-time" requirement, as the data will be at least 15 minutes old at any given time. Furthermore, Tableau Bridge is typically used to connect Tableau Cloud to on-premise or private network data sources, not standard cloud-based databases, making its inclusion here likely unnecessary.

D. Create a connection to the database using Tableau Desktop and retrieve an extract of the data. Publish the data source from Tableau Desktop to Tableau Cloud and schedule the refresh of the extract.
Like option B, using an extract and a scheduled refresh introduces an unacceptable delay for a real-time requirement. Extracts, even if refreshed frequently, are snapshots of data and will not reflect the time log entries instantaneously. This method is best for improving dashboard performance with less real-time data needs, not for immediate data visibility.

📖 Reference
Tableau Official Documentation: Live Connections vs. Extracts
Source: Tableau Help: Live Connections vs. Extracts (Search for "Tableau Live Connections vs. Extracts" on the official Tableau website)

Note: The official documentation emphasizes that live connections should be used for scenarios requiring access to the most up-to-date data, provided the underlying data source performance is adequate. Security configuration (like firewalls) for live connections to cloud databases is a standard, required step.

Explanation

Tableau dashboards support several ways to move between views, but only one object is specifically built to let users click once and seamlessly switch to a different dashboard in the same workbook — without opening new tabs, writing URLs, or relying on worksheet actions. That object is the Navigation button.

Correct Answer: Navigation object ✔️

The Navigation object is the official, recommended way to create clickable buttons that take users to another dashboard.

➡️Drag Navigation from the Objects pane (under Dashboard) onto your canvas
➡️Click “Edit Button” (or double-click it) → choose Navigate to → select the target dashboard from the dropdown
➡️Customize appearance: change text (“Go to Executive Summary”), pick an icon, adjust colors, or even use an image as the button
➡️When published, it works perfectly on Tableau Server, Online, Reader, and mobile apps — one click instantly swaps the entire view

This keeps navigation intuitive, maintains context, and requires zero maintenance when dashboard names change.

Reference:
Tableau Official – Use a Button to Navigate Between Dashboards

Explanation

The Extract Refresh management interface on Tableau Server (or Tableau Cloud) provides control over all scheduled refresh tasks for published extracts. An analyst with appropriate permissions (Data Owner, Creator, or Administrator) can perform several actions on an existing schedule. These include running a refresh immediately ($\text{A}$), deleting the schedule entirely ($\text{C}$), and modifying the schedule's frequency (e.g., changing it from daily to weekly or adjusting the time, which is part of $\text{D}$, Change Schedule).

Options Analysis

✔️ Correct Option: [A] Run a refresh
The Run Now or Run option allows an analyst to manually initiate a full or incremental extract refresh on demand, outside of its set schedule. This is a common administrative task used for immediate data updates or for testing refresh functionality after making changes.

❌ Incorrect Option: [B] Change the refresh from full to incremental
The setting that defines an extract as Full or Incremental is configured in Tableau Desktop (or Web Authoring) before the extract is published to the server. This setting requires specifying a tracking column and cannot be changed directly from the extract refresh schedule management page on Tableau Server once published. To change the type, the analyst would need to re-publish the extract after modifying it in Tableau Desktop.

✔️ Correct Option: [C] Delete the refresh
The Delete option allows the analyst to remove an existing extract refresh schedule. This cancels all future scheduled runs of that specific refresh task, such as removing a redundant schedule or one that is no longer needed.

✔️ Correct Option: [D] Modify the frequency of the refresh
The Change Schedule option lets the analyst reassign the extract refresh task to a completely different schedule (e.g., changing from the "Morning Daily" schedule to the "Weekend Weekly" schedule). This modifies the timing and frequency of the extract refresh.

❌ Incorrect Option: [E] Change the priority of the refresh
The priority of an extract refresh task is typically set at the Schedule level (e.g., within the Schedules admin view on Tableau Server) to manage the order in which jobs run. While administrators can often change a job's priority, this action is distinct from the primary options available for managing the scheduled task itself (Run, Delete, Change Schedule) on the extract refresh page, and is often an Administrator-level function.

Reference 🔗
Tableau Help: Manage Refresh Tasks