Comprehensive and Detailed Explanation From Exact Extract:
In Workday Prism Analytics, a Left Outer Join in a Join stage includes all rows from the primary pipeline (the left pipeline) and attempts to match them with rows from the imported pipeline (the right pipeline) based on the join condition. According to the official Workday Prism Analytics study path documents, if no matching rows exist in the imported pipeline for a given row in the primary pipeline, the row from the primary pipeline is still included in the output, but the fields from the imported pipeline will have NULL values. This behavior ensures that all data from the primary pipeline is retained, while the absence of a match in the imported pipeline is represented by NULLs for the corresponding fields.
The other options are incorrect:
* A. A duplicate row will be generated: A Left Outer Join does not generate duplicate rows; duplicates would occur only if multiple matches exist in the imported pipeline, which is not the case here.
* B. The row will be omitted: In a Left Outer Join, rows from the primary pipeline are never omitted, even if no match is found; this behavior is specific to an Inner Join.
* D. Included fields from both pipelines will have NULL values: Only the fields from the imported pipeline will have NULL values; the fields from the primary pipeline retain their original values.
This behavior of Left Outer Join ensures that all records from the primary pipeline are preserved, with NULLs indicating the absence of matching data from the imported pipeline.
References:
Workday Prism Analytics Study Path Documents, Section: Data Prep and Transformation, Topic: Join Types and Their Behaviors in Prism Analytics Workday Prism Analytics Training Guide, Module: Data Prep and Transformation, Subtopic: Configuring Join Stages in Derived Datasets

Comprehensive and Detailed Explanation From Exact Extract:
In Workday Prism Analytics, window functions are used to perform calculations across a set of rows, such as calculating averages with a function like AVG. According to the official Workday Prism Analytics study path documents, the AVG window function, which computes the average, must operate on a fieldof type Numeric.
This is because averaging requires numerical values to perform arithmetic operations (e.g., summing the values and dividing by the count of rows). Non-numeric field types, such as Text or Date, cannot be averaged, and Boolean fields (true/false) are not suitable for this type of calculation. For example, a window function like AVG(salary) OVER (PARTITION BY department) would calculate the average salary per department, where "salary" must be a Numeric field.
The other options are incorrect:
* A. Text: Text fields cannot be used for arithmetic operations like averaging.
* B. Boolean: Boolean fields (true/false) are not suitable for calculating averages.
* D. Date: Date fields cannot be directly averaged; they require conversion to a numeric representation (e.
g., days since a reference date) first.
The requirement for a Numeric field type ensures that the AVG window function can perform the necessary mathematical computations accurately.
References:
Workday Prism Analytics Study Path Documents, Section: Data Prep and Transformation, Topic: Window Functions and Field Type Requirements Workday Prism Analytics Training Guide, Module: Data Prep and Transformation, Subtopic: Using AVG in Window Functions

Comprehensive and Detailed Explanation From Exact Extract:
In Workday Prism Analytics, a secure File Transfer Protocol (sFTP) connection can be configured as a source for a Data Change task to import data into a table. According to the official Workday Prism Analytics study path documents, a key feature of using an sFTP connection is that it can be reused across multiple Data Change tasks. Once an sFTP connection is defined in the Prism Analytics environment, it is stored and can be selected as the source connection for different Data Change tasks, promoting efficiency and consistency in data ingestion workflows. This reusability reduces the need to redefine connection parameters for each task, streamlining the configuration process.
The other options are not accurate:
* A. You can copy sFTP connections: While connections can be managed, there is no specific feature in Prism Analytics to "copy" sFTP connections as a distinct action.
* C. You can import an XLSX file from an sFTP server: While sFTP connections support various file formats (e.g., CSV), the ability to import XLSX files is not guaranteed and depends on the system's configuration, making this option less definitive.
* D. You can select multiple target tables in the data change task: A Data Change task is designed to load data into a single target table, not multiple tables simultaneously, regardless of the connection type.
The ability to reuse an sFTP connection across multiple Data Change tasks is a core feature that enhances the flexibility and scalability of data import processes in Prism Analytics.
References:
Workday Prism Analytics Study Path Documents, Section: Data Prep and Transformation, Topic: Configuring Data Change Tasks with sFTP Connections Workday Prism Analytics Training Guide, Module: Data Prep and Transformation, Subtopic: Managing Source Connections for Data Ingestion

Comprehensive and Detailed Explanation From Exact Extract:
In Workday Prism Analytics, the Data Change task is used to load data from a source file into a table, and it supports flexible field type mapping to accommodate differences between source and target field types.
According to the official Workday Prism Analytics study path documents, when the source file has a Numeric field type and the target table has a Text field type, you can map the Numeric field to the Text field in the Data Change task. Workday Prism Analytics automatically handles the conversion of Numeric values to Text during the data loading process, as Text fields can store Numeric values as strings without data loss.
The other options are not necessary or appropriate:
* A. Use a different source file, as the field types are incompatible: The field types are not incompatible; Prism supports mapping Numeric to Text, making a new source file unnecessary.
* C. Change the field type in the parsing stage from Numeric to Text: The parsing stage defines how the source file is interpreted, but changing the source field type is not required since the mapping handles the conversion.
* D. Change the connection type for the data change task: The connection type (e.g., file upload or Workday report) is unrelated to field type compatibility and does not address the issue.
By mapping the Numeric field to the Text field in the Data Change task, the data can be successfully loaded, leveraging Prism's built-in type conversion capabilities to ensure compatibility.
References:
Workday Prism Analytics Study Path Documents, Section: Data Prep and Transformation, Topic: Field Type Mapping in Data Change Tasks Workday Prism Analytics Training Guide, Module: Data Prep and Transformation, Subtopic: Handling Field Type Conversions in Data Loading

Comprehensive and Detailed Explanation From Exact Extract:
In Workday Prism Analytics, joining datasets requires that the fields used in the join condition (Match Row fields) are compatible to ensure accurate matching. According to the official Workday Prism Analytics study path documents, the field types for the Match Row fields must match (option A). For example, if the join condition is based on an Employee ID field, the field type (e.g., Text or Numeric) must be the same in both datasets. Mismatched field types (e.g., Text in one dataset and Numeric in another) can lead to join failures or incorrect results, as Prism cannot reliably compare values of different types. This often requires using a Manage Fields stage to align field types before the join.
The other options are incorrect:
* B. The number of rows in each dataset: The number of rows does not need to match; joins can handle datasets of different sizes, depending on the join type (e.g., Left Outer Join).
* C. The level of detail in each dataset: The level of detail (granularity) does not need to match; joins can combine datasets with different levels of detail as long as the Match Row fields are compatible.
* D. The field names for the Match Row fields: The field names do not need to be identical; the join condition maps fields between datasets, so different names can be used as long as the types and values are compatible.
Ensuring that the field types of the Match Row fields are the same is critical for a successful join operation in Prism Analytics.
References:
Workday Prism Analytics Study Path Documents, Section: Data Prep and Transformation, Topic:
Requirements for Joining Datasets in Prism Analytics
Workday Prism Analytics Training Guide, Module: Data Prep and Transformation, Subtopic: Configuring Join Conditions for Datasets