Comprehensive and Detailed Explanation From Exact Extract:

In Workday Prism Analytics, restricting access to specific rows in a Prism data source (PDS) based on a field like Location Hierarchy for users such as Expense Partners requires implementing row-level security. According to the official Workday Prism Analytics study path documents, to meet the requirement that Expense Partners only see expense reports for the locations they support, you should run the Edit Data Source Security task to update row-level security and then republish the PDS (option B).

The Location Hierarchy (instance) field in the dataset can be used to define row-level security rules, ensuring that each Expense Partner only sees data for their assigned locations. The Edit Data Source Security task allows you to configure row-level security by mapping the Location Hierarchy field to the user’s security profile (e.g., their assigned locations). After updating the security settings, republishing the Prism data source is necessary to apply the changes, ensuring the updated security rules take effect in the reports that use the data source.

The other options are incorrect:

A. Run the Edit Data Source Security task to update the Securing Entities and then republish the PDS: Securing Entities are used to control overall access to the data source (e.g., via security domains), not to restrict data at the row level based on a field like Location Hierarchy.

C. Run the Edit Data Source Security task to update row-level security: While updating row-level security is correct, the changes will not take effect in reports until the data source is republished, making this option incomplete.

D. Run the Edit Data Source Security task to update the Securing Entities: As with option A, updating Securing Entities does not address row-level security for location-based restrictions.

Updating row-level security and republishing the PDS ensures that Expense Partners only see the relevant expense reports, meeting the requirement while maintaining security governance.

Comprehensive and Detailed Explanation From Exact Extract:

In Workday Prism Analytics, filters in a derived dataset can be applied using either basic (Simple) or advanced filter logic. According to the official Workday Prism Analytics study path documents, a Prism configurator should leverage advanced filter logic over basic filter logic when the filter needs a combination of AND/OR operators (option D). Basic filter logic (Simple Filter) allows for a list of conditions with a single operator ("If All" for AND, "If Any" for OR), but it cannot handle nested or mixed logical expressions (e.g., Condition1 AND (Condition2 OR Condition3)). Advanced filter logic, on the other hand, supports complex expressions with combinations of AND and OR operators, enabling more sophisticated filtering scenarios.

The other options do not necessitate advanced filter logic:

A. The filter needs to remove NULL values: Removing NULL values (e.g., using ISNOTNULL(field)) can be done with a Simple Filter using a single condition, so advanced logic is not required.

B. The filter needs to use operators such as "equal to" or "not equal to": These operators are supported in Simple Filters, so advanced logic is not necessary.

C. The filter needs to leverage operators such as "greater than or equal to" or "less than or equal to": These comparison operators are also supported in Simple Filters, making advanced logic unnecessary for this purpose.

Advanced filter logic is specifically required when combining AND and OR operators to create complex filtering conditions, providing the flexibility needed for such scenarios.

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 field of 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.

Comprehensive and Detailed Explanation From Exact Extract:

In Workday Prism Analytics, joining datasets with different levels of granularity requires aligning their granularity to ensure a meaningful match. The sales data is at a daily level (one row per day), while the budget data is at a monthly level (one row per month). According to the official Workday Prism Analytics study path documents, to match the granularity of the monthly budget data, you should apply a Group By stage to the sales data (option B). The Group By stage aggregates the daily sales data into monthly totals (e.g., summing sales amounts by month), reducing the granularity from daily to monthly. This allows the sales data to be joined with the monthly budget data on a common key, such as the month.

For example, a Group By stage could group the sales data by a derived month field (e.g., using a function like EXTRACT(YEAR_MONTH, sale_date)) and aggregate the sales amounts using a function like SUM(sales_amount). The resulting dataset would have one row per month, matching the budget data’s granularity.

The other options are incorrect:

A. Union: A Union stage appends rows from one dataset to another but does not change granularity; it cannot aggregate daily data into monthly data.

C. Manage Fields: The Manage Fields stage modifies field properties (e.g., type, name) but does not aggregate data to change granularity.

D. Filter: A Filter stage removes rows based on conditions but does not aggregate data to align granularity levels.

The Group By stage is the appropriate transformation to align the sales data’s granularity with the monthly budget data for a successful join.

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.

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.

Comprehensive and Detailed Explanation From Exact Extract:

In Workday Prism Analytics, removing data from a Prism data source (PDS) without affecting dependent custom reports requires a careful approach to preserve the data source’s structure and dependencies. According to the official Workday Prism Analytics study path documents, the task to use is Delete Published Rows (option D). This task removes the data rows within the Prism data source while keeping the data source’s metadata (e.g., field definitions) and structure intact. Since custom reports depend on the data source’s structure rather than the specific data rows, deleting the published rows will not break the reports. After deleting the rows, you can republish the dataset with updated data, and the reports will continue to function with the new data, assuming the structure remains unchanged.

The other options are incorrect:

A. Inactivate Dataset: Inactivating a dataset disables it but does not remove data from the published data source, and it may still affect reports by making the data source inaccessible.

B. Delete Dataset: Deleting the dataset entirely will also delete the Prism data source, breaking any dependent custom reports.

C. Unpublish Dataset: Unpublishing the dataset removes the Prism data source, which will break dependent reports until the dataset is republished.

The Delete Published Rows task ensures that data is removed from the Prism data source without impacting the dependent custom reports, allowing for seamless data updates.