Comprehensive and Detailed Explanation From Exact Extract:
In Workday Prism Analytics, when using a custom report with prompts as a source connection for a table, the custom report must be configured to ensure compatibility with the Prism data ingestion process. According to the official Workday Prism Analytics study path documents, the key requirement is that the custom report prompts have default values assigned in the report definition. This is necessary because Prism Analytics does not support interactive prompting during data ingestion. Default values ensure that the report can run automatically without requiring user input, allowing the Data Change task to retrieve the data consistently and load it into the target table.
The other options are not correct in this context:
* A. The report is built on an indexed data source: While indexed data sources can enhance performance for certain reports, they are not a requirement for using a custom report as a source for a Prism table.
* B. The prompts are mapped at the data change task level: Prompts are not mapped in the Data Change task; instead, the task relies on the report's default values to execute the data retrieval.
* D. The prompts are marked as required: Marking prompts as required does not address the need for automatic execution; default values are still needed to avoid manual intervention.
By assigning default values to prompts in the custom report definition, the report can be seamlessly integrated as a source connection for Prism Analytics, ensuring reliable data loading into the table.
References:
Workday Prism Analytics Study Path Documents, Section: Integrating Prism with Workday Reports, Topic:
Using Custom Reports as Data Sources
Workday Prism Analytics Training Guide, Module: Data Prep and Transformation, Subtopic: Configuring Custom Reports for Prism Integration

To add or update the description of a derived dataset in Workday Prism Analytics, you should access the Edit Dataset Transformations task. This can be done by selecting the Related Actions next to the dataset name and choosing Edit Transformations. This method allows you to modify various aspects of the dataset, including its description.
This process is outlined in the Workday Prism Analytics User Guide, which states:
"If you have permission to edit a dataset, you can access the Edit Dataset Transformations task using these methods:
* Right-click the dataset name on the Data Catalog report and select Edit Transformations.
* Select Edit Transformations from the Quick Actions on the View Dataset Details report.
* Access the Edit Dataset task and select the dataset name that you want to edit." Once in the Edit Dataset Transformations task, you can update the dataset's description by clicking on the configuration icon (often represented as a gear or pencil icon) and editing the description field.
Reference: Workday Prism Analytics User Guide, "Concept: Dataset Workspace" section

Comprehensive and Detailed Explanation From Exact Extract:
In Workday Prism Analytics, blending two data sources typically involves joining them on a common field, such as Employee ID in this case. However, the Employee ID field is text in Pipeline 1 and numeric in Pipeline 2, which means the field types must be aligned before a join can be performed to avoid data mismatches or errors. According to the official Workday Prism Analytics study path documents, the correct approach is to first use a Manage Fields stage to change the field type of Employee ID in one of the pipelines to match the other (e.g., convert the numeric Employee ID in Pipeline 2 to text, as text can safely store numeric values without data loss), and then perform a Join stage to blend the data (option C). Converting from numeric to text is preferred because converting text to numeric risks data loss if the text field contains non- numeric characters.
The other options are not appropriate:
* A. Add a Manage Fields to change the field type and then Union: A Union appends rows vertically and does not blend data based on a matching field like Employee ID; blending typically requires a Join.
* B. Add a Filter first and then a Manage Fields to change the field type: Adding a Filter stage is unnecessary for preparing the field types for a join and does not address the blending requirement.
* D. Add a Join first and then a Manage Fields to change the field type: Performing the Join first will fail or produce incorrect results because the field types (text and numeric) are incompatible for joining; the types must be aligned before the Join.
By using a Manage Fields stage to change the field type first and then performing a Join, the data from both pipelines can be blended accurately on the Employee ID field.
References:
Workday Prism Analytics Study Path Documents, Section: Data Prep and Transformation, Topic: Preparing Data for Joins in Prism Analytics Workday Prism Analytics Training Guide, Module: Data Prep and Transformation, Subtopic: Field Type Transformations for Data Blending

Comprehensive and Detailed Explanation From Exact Extract:
In Workday Prism Analytics, window functions are used to perform calculations over a defined set of rows (a
"window"). According to the official Workday Prism Analytics study path documents, the COUNT window function is used to return the number of rows within a specified window. When applied in a dataset transformation, the COUNT function counts the rows that fall within the window, which can be defined by partitioning (e.g., by a specific column) and ordering criteria. For example, COUNT(*) OVER (PARTITION BY department) would return the number of rows for each department in the dataset.
The other options serve different purposes:
A: MAX: Returns the maximum value within the window, not the number of rows.
B: SUM: Calculates the sum of a numeric field across the window, not the row count.
D: AVG: Computes the average of a numeric field within the window, not the row count.
The COUNT function is specifically designed to provide the row count, making it the correct choice for this purpose in Prism Analytics transformations.
References:
Workday Prism Analytics Study Path Documents, Section: Data Prep and Transformation, Topic: Window Functions and Their Applications Workday Prism Analytics Training Guide, Module: Data Prep and Transformation, Subtopic: Using COUNT in Window Functions

Comprehensive and Detailed Explanation From Exact Extract:
In Workday Prism Analytics, creating a Prism data source that supports immediate incremental updates as data is updated in Prism requires a specific configuration. According to the official Workday Prism Analytics study path documents, the administrator should create a table and select the Enable for Analysis checkbox (option A). The "Enable for Analysis" option, when selected during table creation, allows the table to be used directly as a Prism data source with real-time updates. This setting ensures that as data in the table is updated (e.g., through a Data Change task), the changes are immediately reflected in the Prism data source, enabling incremental updates without the need for republishing. This is particularly useful for scenarios requiring near- real-time data availability in reporting or analytics.
The other options do not achieve the goal of immediate incremental updates:
* B. Create a table and select Publish: Publishing a table creates a static Prism data source, but updates to the table require republishing, which does not support immediate incremental updates.
* C. Publish a derived dataset with the Prism: Default to Dataset Access Domain: Publishing a derived dataset creates a data source, but updates to the underlying data require republishing the dataset, which is not concurrent or incremental.
* D. Set Data Source Security on a derived dataset and select Publish: Setting security and publishing a derived dataset follows the same process as option C, requiring republishing for updates, which does not meet the requirement for immediate updates.
Selecting the "Enable for Analysis" checkbox when creating a table ensures the Prism data source supports concurrent, incremental updates as data changes in Prism.
References:
Workday Prism Analytics Study Path Documents, Section: Publishing and Visualizing Data, Topic: Creating Prism Data Sources with Real-Time Updates Workday Prism Analytics Training Guide, Module: Publishing and Visualizing Data, Subtopic: Configuring Tables for Incremental Updates