Explanation:

You previously selected Ignore Actions on the "Sales over time" sheet, which means it stopped responding to dashboard actions (like filtering from the map). To make it respond again to filtering actions from the map, you need to re-enable it to participate in dashboard actions.

Why D is correct:

The Use as Filter option in the context menu of a sheet controls whether that sheet can be used as a source for dashboard actions (i.e., it can trigger filters on other sheets).

However, the Ignore Actions setting is what prevents a sheet from receiving actions (i.e., being filtered by other sheets).

To restore the "Sales over time" sheet so that it can be filtered by the map, you need to toggle the setting—selecting and then deselecting "Use as Filter" effectively resets the sheet's action participation, re-enabling it to receive filter actions from other sheets (like the map).

Why other options are incorrect:

A. From the context menu of Sales over time, select Filters and then select Enable Auto Update:
There is no "Enable Auto Update" option in the context menu of a sheet. This option does not exist.

B. From the context menu of Profits by state, deselect Use as Filter and then select Use as Filter:
This toggles the "Use as Filter" setting on the map (Profits by state). Since you want to filter both Sales over time and Detail table from the map, the map is already acting as the filter source. Toggling this setting on the map would turn off and then on its ability to act as a filter source, but it does not re-enable "Sales over time" to receive actions—which is the actual issue.

C. From the context menu of Detail table, select Ignore Actions:
This would disable the Detail table from receiving actions, which is the opposite of what you want. You want both sheets to be filtered, so this would break the Detail table's responsiveness.

Reference:

Tableau Help: Ignore Actions for Dashboard Objects – When a sheet is set to Ignore Actions, it does not respond to any dashboard actions. To re-enable it, you must deselect Ignore Actions. The "Use as Filter" toggle is found in the context menu of a sheet and controls whether it can act as a filter source. Deselecting and reselecting it can reset its action participation.

Explanation:

The goal is to dynamically switch between showing Sales and Profit values in a text table based on user selection.

Step 1: Create the Parameter
You need a parameter that allows the user to choose between "sales" and "profit". This parameter will act as the control mechanism. It must be a string list with these two values, and you must enable Show Parameter so the user can interact with it on the worksheet.

Step 2: Create the Calculated Field
The calculated field must evaluate the current value of the parameter and return the corresponding measure. The correct formula checks the parameter value: if the parameter is 'sales', it returns the [Sales] field; if it is 'profit', it returns [Profit]. This is the logic that makes the worksheet dynamic.

Why the other formula is incorrect: The formula IF ([Sales]=[Parameter 1] THEN 'sales'... would check whether the numeric values in the Sales or Profit fields match the parameter string, which is logically invalid and would not work.

Step 3: Build the Worksheet
Drag the calculated field to Text on the Marks card to display the values (the actual numbers). Add Region to the Rows shelf to create the row headers, giving you the text table shown in the requirement.

Why the other options are incorrect or misplaced:

"Drag the calculated field to Detail on the Marks card and add Region to the Columns shelf" – This is incorrect because:

You need the values displayed as Text, not just added to Detail (which would hide them).

Region should be on Rows (to match the vertical table in the requirement), not Columns.

The formula IF ([Sales]=[Parameter 1] THEN 'sales'... – This is completely wrong. It attempts to compare a numeric field (Sales/Profit) to a string parameter, which will not evaluate properly and would return a string label ("sales"/"profit") instead of the actual numeric value needed for the table.

Reference:

Tableau Help: Create Parameters
Tableau Help: Use Parameters in Calculated Fields – Demonstrates using IF statements with parameters to switch between measures.

Explanation:

In Tableau Server/Cloud, an extract background task is not restricted to a single timeline automation. A workbook or data source can have multiple independent refresh schedules assigned to it simultaneously.

The Core Logic: To retain the existing routine (every Monday at 10:00) while introducing a secondary automation ruleset (last day of the month at 18:00), you must append a completely separate extract task.

The Mechanism: Navigating to the workbook's management page inside the Tableau Server web interface, clicking on the Extract Refreshes tab, and choosing New Extract Refresh allows an administrator or workbook owner to select an additional pre-defined server schedule without overwriting or altering the primary active Monday routine.

Why Other Options Are Incorrect:

A. Changing the schedule frequency:
Modifying the frequency of the existing schedule itself will globally rewrite that specific schedule slot. Doing this would replace the Monday automation entirely, causing the workbook to only update at the end of the month.

B. Changing the priority:
Adjusting schedule priority controls the processing order in the backgrounder queue when multiple tasks conflict at the exact same moment. It does not create new schedule timestamps or change runtime rules.

D. Configuring the Publish Workbook dialog box: While you can assign an initial schedule during the primary publishing phase from Tableau Desktop, adding multiple concurrent independent schedules to a single asset is managed directly via the Tableau Server/Cloud web browser interface post-publish.

References:

Tableau Server Documentation (Manage Refresh Schedules): "You can assign multiple schedules to a single workbook or data source. In the web environment, go to the Extracts Refresh tab for the asset to add or remove additional tasks."

Explanation

To combine data from different sources in Tableau Prep, you must first bring them into the same flow canvas. Once both datasets are present, you can connect them using a Join step. The final and most critical action is to define how they are joined by selecting the specific type of join and the common field that links the records correctly.

✅ Correct Steps & Order

Add both the Excel file and the SQL Server table to the Flow.
This is the foundational first step. You must import your data sources into the Tableau Prep Builder canvas before you can perform any operations on them. You will use the "Connections" pane to add both the Microsoft Excel worksheet and the SQL Server table as input steps to your flow.

Join the two datasets using a join clause.
After both data sources are in the flow, you connect them by dragging one dataset onto the other and selecting 'Join' from the menu that appears. This action creates a new Join step in your flow, which is represented by a Venn diagram icon, and opens the join configuration panel.

Select the join type and the join fields.
This is the configuration step where you define the logic of the join. You must select the type of join (e.g., Inner, Left, Right, Full Outer) based on which records you want to keep. Crucially, you must specify the join clause by selecting the common field from each dataset—in this case, 'Employee Name' from the Excel sheet and 'Employee Name' from the SQL Server table.

📝 Summary
The process is sequential: first add data, then connect it via a join operation, and finally configure the join's logic by defining its type and the key linking field.

📚 Reference
Combine Your Data in Tableau Prep - Tableau Help

Explanation:

You need to create a calculated dimension field named Category that maps each Subject to either "Sciences" or "Humanities" as follows:

Sciences: Computer Science, Science
Humanities: English, Social Studies
Both A and D correctly implement this logic.

Why A is correct:
The IF/ELSEIF statement explicitly checks each subject value and assigns the correct category.
It covers all four subjects and returns the appropriate Category for each.
The syntax is correct and will execute without errors.

Why D is correct:
The CASE statement is a clean and efficient way to map multiple discrete values to corresponding results.
It specifies each subject and its resulting Category.

Note: The CASE statement will return NULL for any subject not listed, but since the dataset only contains these four subjects, it works perfectly.

Why other options are incorrect:

B. IIF((CONTAINS([Subject], 'Science') = TRUE), 'Humanities', 'Sciences'):
This formula is logically flawed. It checks if the subject contains the word "Science" (which would be TRUE for both "Science" and "Computer Science") and returns "Humanities" for those—which is the opposite of the requirement.
It would return "Sciences" only for subjects that do not contain "Science" (e.g., English, Social Studies), which is incorrect.

C. IF ENDSWITH([Subject], 'Computer Science') THEN 'Sciences' ELSE 'Humanities' END: This only checks for "Computer Science" and returns "Sciences" for it.
For all other subjects (including "Science"), it returns "Humanities", which misclassifies "Science" (should be "Sciences").
It also does not handle "English" and "Social Studies" specifically, though they would fall into "Humanities" by default, which is coincidentally correct for those two.

Reference:

Tableau Help: Logical Functions – IF and CASE – Both IF and CASE statements can be used to create calculated dimension fields based on discrete conditions. CASE is typically cleaner for mapping multiple discrete values to results.