Comprehensive and Detailed Explanation From Exact Extract:

In Workday Prism Analytics, the ability to create a dataset is governed by specific security domains within the Prism Analytics functional area. According to the official Workday Prism Analytics study path documents, the security domain that explicitly enables users to create datasets is the "Prism Datasets: Create" domain. This domain grants users the necessary permissions to initiate the creation of both base and derived datasets within the Prism Analytics Data Catalog.

The process of creating a dataset involves defining the metadata and processing logic to manipulate data, which can include Workday or external (non-Workday) data sources. The "Prism Datasets: Create" domain ensures that only authorized users, such as Prism data analysts or administrators, can perform this task, aligning with Workday’s configurable security framework. Other domains, such as "Prism Datasets: Publish," are responsible for publishing datasets to make them available as Prism Data Sources for reporting, while "Prism: Manage Data Source" pertains to managing the data sources themselves, not creating datasets. Similarly, "Prism: Tables Create" is related to creating tables, which is a distinct entity from datasets in Prism Analytics.

This distinction is critical, as datasets and tables serve different purposes in the data management workflow. Datasets include metadata and a subset of example rows, while tables contain metadata and all data rows. The "Prism Datasets: Create" domain is specifically designed to control access to dataset creation, ensuring secure and governed data preparation.

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.

Comprehensive and Detailed Explanation From Exact Extract:

In Workday Prism Analytics, when a data writer creates an intermediary calculated field (e.g., field A) solely to derive a final calculated field (e.g., field B) in a Derived Dataset (DDS), they may want to exclude the intermediary field from the published output to keep the dataset clean and focused. According to the official Workday Prism Analytics study path documents, the recommended approach is to add a Manage Fields stage to the DDS and hide field A. The Manage Fields stage allows users to control the visibility of fields in the dataset, enabling them to hide fields that are not needed in the final output while retaining their calculations for internal use within the dataset’s transformation logic. By hiding field A, field B can still leverage field A’s calculations, and only field B will be visible in the published dataset or data source.

The other options are not suitable:

A. Mark field A as intermediate calculation: There is no specific feature in Prism Analytics to “mark” a field as an intermediate calculation; this is not a supported action.

C. Add a Manage Fields stage to the DDS and hide field B: Hiding field B would defeat the purpose, as field B is the intended output to be published.

D. Delete field A from their DDS and just leave field B: Deleting field A would break the calculation of field B, as field B depends on field A, making this option infeasible.

Using the Manage Fields stage to hide field A ensures that the dataset remains functional while presenting only the necessary fields in the final output, aligning with best practices for data transformation and publishing.