[UPDATED] Workday Workday-Prism-Analytics Certification Exam Questions [Q25-Q45]

NO.25 What report can you run to edit and maintain your Prism import and publish schedules?

Scheduled Future Processes

Prism Management Console

Prism Activities Monitor

Prism Usage

NO.26 You are asked to produce a Prism data source, which is going to be used in a matrix report that should display the minimum, maximum, total, average, and the median purchase order amount by location and month. What should you do to achieve the desired result?

Publish your detail data and build the summarizations in the matrix report.

Add a Group By stage to your derived dataset.

Publish your detail data and build the summarizations in the advanced report.

Add two Group By stages to your derived dataset.

Comprehensive and Detailed Explanation From Exact Extract:
In Workday Prism Analytics, a matrix report in Workday is designed to display summarized data in a grid format, with built-in capabilities to calculate aggregations like minimum, maximum, total, average, and median. According to the official Workday Prism Analytics study path documents, to produce a Prism data source for a matrix report that needs to display the minimum, maximum, total, average, and median purchase order amount by location and month, you should publish your detail data and build the summarizations in the matrix report (option A).
Publishing the detail data (i.e., the raw purchase order data with fields like location, month, and amount) as a Prism data source allows the matrix report to access the granular data. The matrix report can then apply the required aggregations (MIN, MAX, SUM, AVG, MEDIAN) directly, grouping by location and month as specified in the report configuration. This approach leverages Workday’s reporting capabilities, reducing the need for additional transformations in Prism and ensuring flexibility for future reporting needs.
The other options are less efficient:
* B. Add a Group By stage to your derived dataset: A Group By stage in the derived dataset can compute some aggregations (e.g., SUM, AVG), but Prism does not natively support calculating the median in a Group By stage, and it would require multiple stages or calculated fields to compute all metrics, making it less practical than using the matrix report.
* C. Publish your detail data and build the summarizations in the advanced report: While an advanced report can perform some summarizations, it is not as well-suited as a matrix report for displaying multiple aggregations (like median) in a grid format by location and month.
* D. Add two Group By stages to your derived dataset: Using two Group By stages is unnecessary and still does not address the limitation of calculating the median in Prism, making this approach overly complex.
Publishing the detail data and letting the matrix report handle the summarizations is the most efficient and effective way to meet the requirements.
References:
Workday Prism Analytics Study Path Documents, Section: Publishing and Visualizing Data, Topic: Preparing Data for Matrix Reports Workday Prism Analytics Training Guide, Module: Integrating Prism with Workday Reports, Subtopic:
Leveraging Matrix Reports for Aggregations

NO.27 A Prism data administrator combined data from multiple sources down to a final derived dataset, including current worker data. There is a new requirement to append historical worker data to the dataset in a uniform layout. The historical worker data includes some, but not all, fields that align withthe current worker data.
Using current worker data as the primary pipeline, how can the historical worker data points be brought in?

Add a Join stage with a Right Outer Join.

Add a Union stage.

Add a Join stage with a Left Outer Join.

Add a Join stage with an Inner Join.

Comprehensive and Detailed Explanation From Exact Extract:
In Workday Prism Analytics, when the goal is to append data from one dataset to another in a uniform layout, such as combining current worker data with historical worker data, a Union stage is the appropriate transformation. According to the official Workday Prism Analytics study path documents, a Union stage is used to append rows from one pipeline to another, stacking the data vertically while aligning fields based on their names and types. In this scenario, the current worker data (primary pipeline) and historical worker data (secondary pipeline) share some fields, and a Union stage will combine the rows from both datasets into a single dataset. Fields that exist in one pipeline but not the other will have NULL values for the rows where they are not present, ensuring a uniform layout without losing data.
The other options are not suitable for this requirement:
* A. Add a Join stage with a Right Outer Join: A Right Outer Join would include all rows from the historical worker data and only matching rows from the current worker data, which does not align with the goal of appending all data in a uniform layout.
* C. Add a Join stage with a Left Outer Join: A Left Outer Join would include all rows from the current worker data and matching rows from the historical worker data, but this is not an append operation; it’s a matching operation based on a join condition, which isn’t specified here.
* D. Add a Join stage with an Inner Join: An Inner Join would only include rows where matches exist between the two datasets, potentially excluding non-matching historical or current worker data, which does not meet the requirement to append all data.
The Union stage is the correct approach to append historical worker data to the current worker data, ensuring all rows are included in a uniform layout, with NULLs filling in for missing fields.
References:
Workday Prism Analytics Study Path Documents, Section: Data Prep and Transformation, Topic: Using Union Stages to Append Data in Prism Analytics Workday Prism Analytics Training Guide, Module: Data Prep and Transformation, Subtopic: Combining Datasets with Union Operations

NO.28 You have published a derived dataset to build a Prism data source. For reports using this Prism data source, when is data updated?

At republish of the datasource only.

At reimport into tables and republish of the datasource.

At reimport into tables only.

At report runtime.

NO.29 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

NO.30 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

NO.31 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.

NO.32 You want your derived dataset to only show rows that meet the following criteria: Agent ID is not null AND Location is Dallas OR Location is Montreal. How can you achieve this?

By adding a Manage Fields stage.

By using Simple Filter conditions.

By using Advanced Filter conditions.

By creating a Custom Example.

Comprehensive and Detailed Explanation From Exact Extract:
In Workday Prism Analytics, filtering a derived dataset to meet specific criteria involving multiple conditions with mixed logical operators (AND, OR) requires careful configuration. The criteria here are: Agent ID is not null AND (Location is Dallas OR Location is Montreal). According to the official Workday Prism Analytics study path documents, this can be achieved by using Advanced Filter conditions (option C).
A Simple Filter in Prism Analytics allows for basic conditions with a single operator (“If All” for AND, “If Any” for OR), but it cannot handle nested logic like AND combined with OR in a single filter. For example, a Simple Filter with “If All” would require all conditions to be true (Agent ID is not null AND Location is Dallas AND Location is Montreal), which is too restrictive. A Simple Filter with “If Any” would include rows where any condition is true (Agent ID is not null OR Location is Dallas OR Location is Montreal), which is too broad. The Advanced Filter, however, allows for complex expressions with nested logic, such as ISNOTNULL(Agent_ID) AND (Location = “Dallas” OR Location = “Montreal”), ensuring the correct rows are included.
The other options are incorrect:
* A. By adding a Manage Fields stage: The Manage Fields stage modifies field properties (e.g., type, visibility) but does not filter rows based on conditions.
* B. By using Simple Filter conditions: As explained, a Simple Filter cannot handle the combination of AND and OR logic required for this criteria.
* D. By creating a Custom Example: Custom Examples are used to provide sample data for testing, not to filter rows in a dataset.
Using Advanced Filter conditions allows for the precise application of the required logic to filter the dataset accurately.
References:
Workday Prism Analytics Study Path Documents, Section: Data Prep and Transformation, Topic: Filtering Data in Derived Datasets Workday Prism Analytics Training Guide, Module: Data Prep and Transformation, Subtopic: Using Advanced Filters for Complex Conditions

NO.33 Why should you include Workday instance field types in the Workday report that you use to import data into Prism?

The final Prism datasource can support drilling into Workday objects.

Performance is improved in the final Prism datasource when published.

Unions are more easily performed with instance field types.

Joins are more easily performed with instance field types.

Comprehensive and Detailed Explanation From Exact Extract:
When importing data into Workday Prism Analytics from a Workday report, including Workday instance field types in the report is critical for enabling specific functionality in the resulting Prism data source.
According to the official Workday Prism Analytics study path documents, including instance field types allows the final Prism data source to support drilling into Workday objects. Instance field types represent references to Workday business objects (e.g., Worker, Position, or Organization), and including them in the report ensures that the Prism data source retains the ability to navigate to these objects within Workday’s reporting and analytics framework. This enables users to perform drill-down actions, such as accessing detailed object data directly from Prism visualizations or reports.
The other options do not accurately reflect the primary benefit of including instance field types:
* B. Performance is improved in the final Prism datasource when published: Instance field types do not directly impact the performance of the published data source; performance is more influenced by data volume and indexing.
* C. Unions are more easily performed with instance field types: Unions depend on schema compatibility, not instance field types, which are specific to Workday object references.
* D. Joins are more easily performed with instance field types: While instance field types can be used in joins, their primary purpose is to enable object navigation, not to simplify join operations.
By including instance field types, the Prism data source gains enhanced interactivity, allowing users to leverage Workday’s object model for deeper analysis and navigation.
References:
Workday Prism Analytics Study Path Documents, Section: Integrating Prism with Workday Reports, Topic:
Workday Report Field Types and Prism Integration
Workday Prism Analytics Training Guide, Module: Publishing and Visualizing Data, Subtopic: Enabling Drill-Down Capabilities in Prism Data Sources

NO.34 You are adding a Join stage and choose Join type of Left Outer Join, causing Workday to search for a matching row in the imported pipeline. What happens if no matching rows exist?

A duplicate row will be generated.

The row will be omitted.

Included fields from the imported pipeline will have NULL values.

Included fields from both pipelines will have NULL values.

NO.35 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

NO.36 A Prism data writer needs to create a new Prism calculated field on a derived dataset using the CASE function. When creating a calculated field, what symbol do you use to view a list of fields that you can select from in the dataset?

[

(

#

{

NO.37 What window function returns the number of rows within a window?

MAX

SUM

COUNT

AVG

NO.38 You want to remove data within a Prism data source without deleting any dependent custom reports. What task can you use to do this?

Inactivate Dataset

Delete Dataset

Unpublish Dataset

Delete Published Rows

NO.39 You want to convert each instance of a multi-instance field and convert it to a single-instance field. What transformation stage can you use to do this?

Unpivot

Explode

Manage Fields

Group By

NO.40 You have a number of Workday reports that use a Prism data source. When are the values of the Prism calculated fields in the Workday reports calculated?

At the calculated field creation time.

At report run time.

At time of publishing.

At dataset creation time.

NO.41 You have to blend two sources of data. Your matching field is Employee ID, which is a text-type field in Pipeline 1, but is numeric in Pipeline 2. How do you prepare your data for blending?

Add a Manage Fields to change the field type and then Union.

Add a Filter first and then a Manage Fields to change the field type.

Add first a Manage Fields to change the field type and then Join.

Add a Join first and then a Manage Fields to change the field type.

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

NO.42 For a Prism use case, you have two datasets: one contains daily sales data, and the other contains monthly budget allocations. Before performing a join between these datasets, what transformation stage should you apply to the sales data to ensure it matches the granularity of the budget data?

Union

Group By

Manage Fields

Filter

NO.43 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

NO.44 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

NO.45 Using three different source files, you want to load rows of data into an empty table through a Data Change task. What needs to be the same about the three source files?

Schema

Source

Naming convention

Size

Leave a Reply Cancel reply