Comprehensive and Detailed Explanation From Exact Extract:
In Workday Prism Analytics, managing schedules for importing data into tables or publishing datasets as Prism data sources is a key administrative task. According to the official Workday Prism Analytics study path documents, the Scheduled Future Processes report (option A) is the tool used to edit and maintain Prism import and publish schedules. This report provides a centralized view of all scheduled processes in Workday, including Prism-related tasks such as Data Change tasks (for imports) and dataset publish schedules. Users can access this report to view, edit, or cancel scheduled processes, ensuring that data imports and publishes occur at the desired frequency and time.
The other options are incorrect:
* B. Prism Management Console: The Prism Management Console provides an overview of Prism activities and resources but does not allow for editing or maintaining schedules.
* C. Prism Activities Monitor: This report monitors the status of Prism activities (e.g., running or completed tasks) but does not manage schedules.
* D. Prism Usage: The Prism Usage report tracks usage metrics for Prism Analytics but does not handle scheduling tasks.
The Scheduled Future Processes report is the correct tool for managing Prism import and publish schedules, ensuring efficient data updates.
References:
Workday Prism Analytics Study Path Documents, Section: Publishing and Visualizing Data, Topic: Managing Import and Publish Schedules Workday Prism Analytics Training Guide, Module: Publishing and Visualizing Data, Subtopic: Using Scheduled Future Processes for Prism Tasks

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

Comprehensive and Detailed Explanation From Exact Extract:
In Workday Prism Analytics, configuring access to a published Prism data source for use in reporting and discovery boards requires managing its security settings. According to the official Workday Prism Analytics study path documents, the necessary action is to edit the data source security and select a domain (option A).
After a dataset is published as a Prism data source, access is controlled through security domains. By editing the data source security and assigning it to an appropriate security domain (e.g., a domain that grants access to specific user groups like report writers or analysts), you ensure that authorized users can access the data source for reporting and discovery boards. This aligns with Workday's configurable security framework, ensuring that only users with the appropriate permissions can view or use the data source.
The other options are incorrect:
* B. Share the dataset with appropriate users: Sharing the dataset itself does not grant access to the published Prism data source; access to the data source is controlled through its security settings, not the dataset's sharing settings.
* C. Share the imported Workday report to provide users with access to the published Prism data source:
Sharing an imported Workday report does not affect access to the Prism data source; the data source's security must be configured directly.
* D. Schedule the recurring publish process: Scheduling a recurring publish process ensures the data source is updated regularly, but it does not configure access for reporting or discovery boards.
Editing the data source security and selecting a domain is the critical step to enable access for reporting and discovery boards.
References:
Workday Prism Analytics Study Path Documents, Section: Security and Governance in Prism, Topic:
Configuring Access to Prism Data Sources
Workday Prism Analytics Training Guide, Module: Security and Governance in Prism, Subtopic: Managing Data Source Security for Reporting

Comprehensive and Detailed Explanation From Exact Extract:
In Workday Prism Analytics, unpublishing a dataset to delete a Prism data source requires removing all dependencies that reference the data source. According to the official Workday Prism Analytics study path documents, if you have already deleted Report Writer reports but are still unable to unpublish the dataset, you must also delete any discovery board visualizations that reference the Prism data source (option C). Discovery boards in Workday allow users to create visualizations based on Prism data sources, and these visualizations create a dependency on the data source. If such visualizations exist, the system prevents the dataset from being unpublished until they are removed, ensuring that no downstream dependencies are broken.
The other options are incorrect:
* A. Upstream tables: Upstream tables are the source of data for the dataset, but they are not dependencies of the published data source and do not need to be deleted to unpublish the dataset.
* B. Published rows: Published rows are part of the data source itself and are removed when the dataset is unpublished; they are not a separate dependency to delete.
* D. Upstream datasets: Upstream datasets may feed into the dataset being unpublished, but they are not dependencies of the published data source and do not prevent unpublishing.
Deleting discovery board visualizations ensures all dependencies are cleared, allowing the dataset to be unpublished and the Prism data source to be deleted.
References:
Workday Prism Analytics Study Path Documents, Section: Publishing and Visualizing Data, Topic:
Unpublishing Prism Data Sources
Workday Prism Analytics Training Guide, Module: Publishing and Visualizing Data, Subtopic: Managing Dependencies for Data Source Deletion

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