100% Free Workday-Prism-Analytics Files For passing the exam Quickly UPDATED Sep 11, 2025 [Q11-Q26]

NEW QUESTION 11
You explode the Language Skills multi-instance field on your derived dataset and you want to change the business object that the new Language Skills Exploded instance field is mapped to. What steps should you take?

Select from the list of suggested BO values in the Explode stage configuration.

Click on the Related Actions next to the business object in the insight panel.

Add a Manage Fields before the Explode stage and modify the business object.

Add a Manage Fields after the Explode stage and modify the business object.

Comprehensive and Detailed Explanation From Exact Extract:
In Workday Prism Analytics, the Explode stage transforms a multi-instance field (e.g., Language Skills) into multiple rows, creating a new single-instance field (e.g., Language Skills Exploded). The resulting field inherits the business object (BO) mapping from the original multi-instance field, but this mapping can be modified if needed. According to the official Workday Prism Analytics study path documents, to change the business object that the new Language Skills Exploded instance field is mapped to, you should add a Manage Fields stage after the Explode stage and modify the business object (option D).
The Manage Fields stage allows you to edit field properties, including the business object mapping, for the exploded field. After the Explode stage creates the new single-instance field, the Manage Fields stage can be used to reassign the business object by selecting a different Workday business object (e.g., changing from a generic object to a specific one like “Language”). This step ensures the field is mapped correctly for downstream reporting or integration with Workday reports.
The other options are incorrect:
* A. Select from the list of suggested BO values in the Explode stage configuration: The Explode stage does not provide an option to modify business object mappings during its configuration; it focuses on exploding the multi-instance field.
* B. Click on the Related Actions next to the business object in the insight panel: The insight panel provides metadata insights but does not allow direct modification of business object mappings for fields.
* C. Add a Manage Fields before the Explode stage and modify the business object: Modifying the business object before the Explode stage affects the original multi-instance field, but the Explode stage will still create the new field with the inherited mapping, so this does not achieve the goal.
Adding a Manage Fields stage after the Explode stage is the correct approach to modify the business object mapping of the new exploded field.
References:
Workday Prism Analytics Study Path Documents, Section: Data Prep and Transformation, Topic: Managing Field Properties After Explode Stages Workday Prism Analytics Training Guide, Module: Data Prep and Transformation, Subtopic: Modifying Business Object Mappings in Derived Datasets

NEW QUESTION 12
You had to change the imported pipeline in a Join stage and your View Dataset Lineage report shows a Stage Alert regarding the disconnected pipeline. How can you fix this and make the alert disappear?

Add a Manage Fields stage and re-attach the pipeline.

Publish the derived dataset.

Change the imported pipeline to a different one.

Delete the disconnected pipeline.

NEW QUESTION 13
You apply an Explode stage to your derived dataset that contains information on your worker benefit elections. What happens in the resulting stage?

The number of columns stays the same and the original multi-instance field doesn’t get dropped.

The number of columns exponentially increases and the original multi-instance field gets dropped.

The number of rows stays the same and the original multi-instance field does not get dropped.

The number of rows exponentially increases and the original multi-instance field gets dropped.

Comprehensive and Detailed Explanation From Exact Extract:
In Workday Prism Analytics, an Explode stage is used to transform a multi-instance field into multiple rows, creating a single-instance field for each instance. According to the official Workday Prism Analyticsstudy path documents, when an Explode stage is applied to a derived dataset containing worker benefit elections (a multi-instance field, e.g., a list of elected benefits per worker), the following occurs: the number of rows exponentially increases, and the original multi-instance field gets dropped (option D).
For example, if a worker has three benefit elections in a multi-instance field, the Explode stage will create three rows-one for each election-while the original multi-instance field (e.g., “Benefit Elections”) is replaced by a single-instance field containing one election per row. The number of rows increases based on the number of instances in the multi-instance field (e.g., a dataset with 100 workers, each with 3 elections on average, would grow from 100 rows to 300 rows). The term “exponentially” in the question reflects this potential for significant row growth, though the increase is technically linear per record based on the number of instances.
The other options are incorrect:
* A. The number of columns stays the same and the original multi-instance field doesn’t get dropped: The original multi-instance field is dropped and replaced by a single-instance field; the column count may change slightly due to this replacement.
* B. The number of columns exponentially increases and the original multi-instance field gets dropped:
The Explode stage does not increase the number of columns exponentially; it primarily affects rows, with minimal impact on columns.
* C. The number of rows stays the same and the original multi-instance field does not get dropped: The number of rows increases due to the explosion of multi-instance data, and the original field is dropped.
The Explode stage’s behavior of increasing rows and dropping the original multi-instance field aligns with its purpose of normalizing multi-instance data into a row-based structure.
References:
Workday Prism Analytics Study Path Documents, Section: Data Prep and Transformation, Topic: Using the Explode Stage in Derived Datasets Workday Prism Analytics Training Guide, Module: Data Prep and Transformation, Subtopic: Handling Multi- Instance Fields with Explode Stages

NEW QUESTION 14
What is the primary purpose of window functions in Prism?

To provide row-level access control.

To manipulate strings and dates within a query.

To filter rows based on specified conditions.

To perform calculations across a set of rows related to the current row while partitioning the data.

NEW QUESTION 15
A Prism data administrator notices that several of the Prism calculated fields on their lineage are producing nil results, so they need to revise the expressions for all of the affected calculated fields. Where can they review the expressions in bulk?

The table or dataset where the calculated field was created.

The View Dataset Lineage report.

Any table in the lineage.

Any dataset in the lineage.

NEW QUESTION 16
You just imported your table on worker compensation into a derived dataset but before adding any transformation you want to make sure you have no NULL values for the Worker ID field. How can you get this insight?

Add a Manage Fields stage.

Click on the field name and check the stage statistics.

Create a Prism calculated field.

Join on the Worker ID field.

NEW QUESTION 17
You are a new Prism customer and you want to ensure the correct set of fields is brought into a derived dataset. When should you apply a Manage Fields stage?

After the dataset is published.

At the end of the Primary Pipeline of a published dataset.

At the beginning of the Primary Pipeline of the derived dataset.

At the beginning of the primary pipeline of the Base Dataset.

Comprehensive and Detailed Explanation From Exact Extract:
In Workday Prism Analytics, a Manage Fields stage is used to control the fields in a dataset by renaming, hiding, or changing field types, among other actions. According to the official Workday Prism Analytics study path documents, to ensure the correct set of fields is brought into a derived dataset (DDS), the Manage Fields stage should be applied at the beginning of the Primary Pipeline of the derived dataset (option C).
Placing the Manage Fields stage early in the pipeline-right after the initial import stage (Stage 1)-allows you to define the field structure upfront, ensuring that subsequent transformationstages (e.g., Join, Filter, Calculate Field) operate on the desired set of fields. This approach helps maintain consistency and avoids unnecessary processing of fields that are not needed in later stages.
The other options are not optimal:
* A. After the dataset is published: You cannot add transformation stages like Manage Fields after a dataset is published; transformations must be applied during the dataset’s creation or editing.
* B. At the end of the Primary Pipeline of a published dataset: Similar to option A, you cannot modify a published dataset’s pipeline, and placing Manage Fields at the end would not prevent unnecessary fields from being processed in earlier stages.
* D. At the beginning of the primary pipeline of the Base Dataset: A Base Dataset does not have a transformation pipeline; it is a direct import of a table, so Manage Fields stages can only be applied in a Derived Dataset.
Applying the Manage Fields stage at the beginning of the derived dataset’s Primary Pipeline ensures efficient data preparation and transformation.
References:
Workday Prism Analytics Study Path Documents, Section: Data Prep and Transformation, Topic: Using Manage Fields in Derived Datasets Workday Prism Analytics Training Guide, Module: Data Prep and Transformation, Subtopic: Best Practices for Field Management in Pipelines

NEW QUESTION 18
You want to apply a Filter stage to your derived dataset to show only expense reports submitted in the current month and where the expense report total amount is higher than 2000 USD. What should you do?

Use a simple filter, two conditions, and “If All” operator.

Use a simple filter, two conditions, and “If Any” operator.

Use a simple filter, three conditions, and “If All” operator.

Use a simple filter, three conditions, and “If Any” operator.

Comprehensive and Detailed Explanation From Exact Extract:
In Workday Prism Analytics, a Filter stage in a derived dataset is used to include only rows that meet specific criteria. The requirement here is to show expense reports that satisfy two conditions: (1) submitted in the current month, and (2) total amount higher than 2000 USD. According to the official Workday Prism Analytics study path documents, this can be achieved by using a simple filter with two conditions and the “If All” operator (option A).
The first condition would check the submission date, using a function like MONTH() to compare with the current month (e.g., MONTH(submission_date) = MONTH(CURRENT_DATE())). The second condition would compare the total amount (e.g., total_amount > 2000). The “If All” operator ensures that both conditions must be true for a row to be included, which aligns with the requirement that both criteria (current month AND amount > 2000 USD) must be met. A simple filter is sufficient because the logic involves straightforward comparisons without nested conditions.
The other options are incorrect:
* B. Use a simple filter, two conditions, and “If Any” operator: The “If Any” operator would include rows where either condition is true (e.g., submitted in the current month OR amount > 2000 USD), which does not meet the requirement for both conditions to be true.
* C. Use a simple filter, three conditions, and “If All” operator: Only two conditions are needed (submission month and amount), so three conditions are unnecessary.
* D. Use a simple filter, three conditions, and “If Any” operator: This combines the issues of option B (wrong operator) and option C (too many conditions).
Using a simple filter with two conditions and the “If All” operator ensures the dataset includes only the expense reports that meet both criteria.
References:
Workday Prism Analytics Study Path Documents, Section: Data Prep and Transformation, Topic: Applying Filters in Derived Datasets Workday Prism Analytics Training Guide, Module: Data Prep and Transformation, Subtopic: Configuring Simple Filters with Multiple Conditions

NEW QUESTION 19
While viewing your lineage, you realize you have forgotten to add a description to some of your derived datasets. From the lineage, you double-click on a dataset to view the dataset details. What is the next step to add the missing descriptions?

Select the pencil icon next to the dataset name and Edit Transformations.

Select the pencil icon next to the Import stage to update the description.

Select Related Actions next to the dataset name and Edit Transformations.

Select Add Field from the dataset details to create a description.

NEW QUESTION 20
A Prism data administrator needs to add an Explode stage to a derived dataset to create a new single-instance type field. What is the only field type you can select in the Explode stage?

Numeric

Multi-Instance

Single-Instance

Text

NEW QUESTION 21
An HR analyst is tasked to create custom reports for their company’s performance reviews. The analyst uses both Workday and Prism for data analysis. What Workday-calculated field functions would the analyst be able to build off of their Prism object?

Extract Single Instance

Arithmetic Calculation

Lookup Related Value

Lookup Field with Prompts

Comprehensive and Detailed Explanation From Exact Extract:
In Workday Prism Analytics, when integrating with Workday reports, a Prism object (i.e., a published Prism data source) can be used as the basis for custom reports, and certain Workday-calculated field functions can be applied to it. According to the official Workday Prism Analytics study path documents, the Arithmetic Calculation function (option B) is a supported Workday-calculated field function that can be built off a Prism object. This function allows the analyst to perform mathematical operations (e.g., addition, subtraction, multiplication) on numeric fields within the Prism data source, such as calculatinga performance review score by combining multiple metrics. Since Prism data sources often contain pre-processed data, arithmetic calculations can be applied to enhance the data for reporting purposes.
The other options are not supported for Prism objects:
* A. Extract Single Instance: This function is used to extract a single instance from a multi-instance field in Workday, but Prism objects typically contain single-instance fields after transformations (e.g., via an Explode stage), making this function inapplicable.
* C. Lookup Related Value: This function retrieves related values from other Workday business objects, but Prism objects do not support direct lookups to Workday objects in this manner; such relationships must be pre-built in the Prism dataset.
* D. Lookup Field with Prompts: This function involves interactive prompting, which is not supported for Prism objects in Workday reports, as Prism data sources are static snapshots of data.
The Arithmetic Calculation function provides the flexibility to perform numerical computations on Prism data, making it a suitable choice for enhancing performance review reports.
References:
Workday Prism Analytics Study Path Documents, Section: Integrating Prism with Workday Reports, Topic:
Using Calculated Fields with Prism Objects
Workday Prism Analytics Training Guide, Module: Integrating Prism with Workday Reports, Subtopic:
Supported Calculated Field Functions for Prism Data Sources

NEW QUESTION 22
The Prism use case is to classify workers based on their pay. You must create a field that evaluates worker pay and returns a value that represents various pay ranges. How would you add this field for inclusion on the Prism data source?

Add the additional field to your raw data before you ingest into Prism.

Build an Evaluate Expression calculated field on your final Prism business object to evaluate workers against their pay.

Build a CASE calculated field function on the TBL directly to ease later transformation.

Create a derived dataset and build a CASE calculated field to classify workers against their pay.

Comprehensive and Detailed Explanation From Exact Extract:
In Workday Prism Analytics, classifying workers into pay ranges based on their pay requires creating a new field that evaluates the pay values and assigns them to defined ranges (e.g., “Low,” “Medium,” “High”).
According to the official Workday Prism Analytics study path documents, the recommended approach is to create a derived dataset (DDS) and build a CASE calculated field to classify workers against their pay (option B). The CASE function in a calculated field allows users to define conditional logic (e.g., CASE WHEN pay
< 50000 THEN “Low” WHEN pay < 100000 THEN “Medium” ELSE “High” END), which is ideal for creating pay range classifications. This calculated field is added within a deriveddataset, which can then be published as a Prism data source, making the new field available for reporting and analytics.
The other options are not optimal:
* A. Add the additional field to your raw data before you ingest into Prism: Modifying raw data outside Prism is unnecessary and less flexible, as Prism’s transformation capabilities (like CASE) are designed for such tasks.
* C. Build a CASE calculated field function on the TBL directly to ease later transformation: Calculated fields cannot be created directly on a table (TBL) in Prism Analytics; they must be defined in a derived dataset.
* D. Build an Evaluate Expression calculated field on your final Prism business object to evaluate workers against their pay: Prism Analytics does not use “Prism business objects” for calculated fields, and “Evaluate Expression” is not a standard function; this option is not applicable.
Using a CASE calculated field in a derived dataset provides a flexible and maintainable way to classify workers by pay ranges, ensuring the field is included in the final Prism data source.
References:
Workday Prism Analytics Study Path Documents, Section: Data Prep and Transformation, Topic: Creating Calculated Fields with CASE Functions Workday Prism Analytics Training Guide, Module: Data Prep and Transformation, Subtopic: Classifying Data Using Calculated Fields in Derived Datasets

NEW QUESTION 23
You have two tables. One with employee data from Workday and another with learner data from an external system. Both tables have an Employee ID field.
In the Employee Data TBL, Employee ID is text.

In the Learner Data TBL, Employee ID is numeric.

How can you prepare to join these tables, without the potential loss of data?

Import the Employee Data TBL into a DDS and change the field type of Employee ID from text to numeric using a Manage Fields stage.

Change the field type of Employee ID directly on the Employee Data TBL from text to numeric.

Change the field type of Employee ID directly on the Learner Data TBL from Numeric to Text.

Import the Learner Data TBL into a DDS and change the field type of Employee ID from numeric to text using a Manage Fields stage.

In Workday Prism Analytics, joining two tables requires that the fields used in the join condition have compatible data types to avoid data mismatches or loss. The Employee Data TBL has an Employee ID field as text, while the Learner Data TBL has an Employee ID field as numeric. According to the official Workday Prism Analytics study path documents, to join these tables without potential data loss, the best approach is to convert the numeric Employee ID in the Learner Data TBL to text, as text fields can safely store numeric values as strings, but converting text to numeric risks data loss if the text field contains non-numeric characters (e.g., leading zeros or special characters).
The correct method is to import the Learner Data TBL into a Derived Dataset (DDS) and use a Manage Fields stage to change the field type of Employee ID from numeric to text (option D). This ensures that the Employee ID field in both tables is text, enabling a safe and accurate join without losing data. The Manage Fields stage in a DDS allows for field type transformations, which is the recommended approach for preparing data for joins in Prism Analytics.
The other options are less suitable:
* A. Import the Employee Data TBL into a DDS and change the field type of Employee ID from text to numeric using a Manage Fields stage: Converting text to numeric risks data loss if the text field contains non-numeric values, which could lead to errors or missing records during the join.
* B. Change the field type of Employee ID directly on the Employee Data TBL from text to numeric:
Direct field type changes on tables are not supported in Prism Analytics, and even if possible, this approach risks data loss for the same reason as option A.
* C. Change the field type of Employee ID directly on the Learner Data TBL from Numeric to Text:
Direct field type changes on tables are not supported; field type transformations must be done in a DDS using a Manage Fields stage.
By converting the numeric Employee ID to text in a DDS, the join can be performed safely, preserving all data from both tables.
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 Using Manage Fields Stage

NEW QUESTION 24
A Prism data administrator is ready to create a Prism data source. As data is updated in Prism, the goal is to update the data in the Prism data source concurrently, enabling immediate incremental updates. How should the administrator create the Prism data source?

Create a table and select the Enable for Analysis checkbox.

Create a table and select Publish.

Publish a derived dataset with the Prism: Default to Dataset Access Domain.

Set Data Source Security on a derived dataset and select Publish.

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

NEW QUESTION 25
When using a window function to calculate averages in Prism, what field type must the function operate on?

Text

Boolean

Numeric

Date

NEW QUESTION 26
You accidentally delete a Prism calculated field that is used in other Prism calculated fields or conditions.
What is a possible outcome?

The system will automatically reverse the deletion because the field is referenced elsewhere.

Any calculated field referencing the deleted field defaults to zero.

Errors will result in any stage or calculated field that references the field.

The system will automatically adjust any dependencies accordingly.