When reports use Indexed Data Sources , performance issues can arise if sorting is attempted on fields that are not indexed. In the case of the Worker object, sorting directly by the Worker object field is slower. Workday best practice is to sort by text-based fields such as the “Full Name (text)” field , which improves query performance because it leverages indexed fields.

From the Workday reporting materials:

*“For indexed data sources, performance improves when sorting by text fields such as Full Name (text), instead of object fields. Sorting by object fields causes slower performance, whereas text-based fields use the

Matrix reports in Workday allow for grouping, summarization, and drill-through capabilities. To let managers dynamically refine report results at runtime , you configure Facet Filters . Facet Filters enable users to filter the report output interactively, without modifying the underlying definition.

From the Workday Reporting documentation:

“Matrix reports allow grouping and summarization of data. You can also configure facet filters so users can dynamically refine report results by selecting values such as Hiring Source or Location.”

Thus, the correct way to let the recruiting manager refine the output is D. Configure Facet Filters .

The Custom Report Exception Audit report identifies errors in custom reports, such as missing security access. If a new report owner does not have access to one or more fields on the report, it will trigger a critical error .

From the Workday Reporting documentation:

“The Custom Report Exception Audit report identifies issues such as missing field access when ownership of a report is transferred.”

Therefore, the correct answer is A. The HR Analyst does not have access to all of the fields on the report .

Duplicate prompts occur in composite reports when multiple subreports request similar or identical inputs, such as Company, Date, or Organization. The recommended and most scalable solution is to use a Prompt Set configured at the composite report level .

Prompt sets allow you to consolidate duplicate prompts into a single prompt , which is then mapped to the corresponding prompts in each subreport. This ensures a clean user experience and consistent filtering across all subreports.

From the Workday HCM Reporting documentation:

“Composite reports support prompt sets to consolidate duplicate prompts across subreports.”

“Configure prompt sets in the composite report’s Report Settings to eliminate redundant user prompts.”

The other options are not best practice: default values do not remove duplicate prompts, suppressing prompts reduces flexibility, and managing prompts individually in subreports defeats the purpose of composite-level control.

When a report is scheduled to run at a recurring interval (daily, weekly, monthly, etc.), Workday tracks this under the Scheduled Future Processes report. This task allows administrators and report owners to view when reports are set to run, the frequency of execution, and the schedule start and end dates. If a report stopped running after the new year began, the most likely cause is that the scheduling end date expired on December 31, meaning no new jobs were generated for the new year.

From the Workday Reporting binder: “Workday provides scheduling options to run reports at set frequencies. You can confirm upcoming scheduled report runs in the Scheduled Future Processes report.” This provides visibility into whether the report is still scheduled and when it is next expected to execute.

The other answers are incorrect: View Alerts relates to system notifications, Mass Operation Management is not for reporting, and Run History shows past runs but not future scheduling. The correct option is C. Scheduled Future Processes .

For a matrix report to be eligible as a subreport in a composite report , Workday requires strict alignment between the composite report’s enabled fields and the matrix report’s group-by fields . Specifically, every field enabled for filtering and grouping in the composite report must also exist as a group-by field in the matrix report .

If this alignment does not exist, Workday excludes the matrix report from the Sub Report Name selection list because the system cannot reliably aggregate or align the summarized data across reports.

Workday HCM Reporting documentation states:

“When using matrix reports as subreports in composite reports, the group-by fields must align with the composite report’s enabled grouping and filtering fields.”

“Matrix reports that do not meet grouping alignment requirements will not be available for selection as subreports.”

The other options do not control subreport eligibility:

Summarization fields affect calculations, not availability.

Filter alignment is validated later, not at selection time.

Prompt defaults do not determine whether a report appears in the Sub Report Name field.

Workday provides multiple types of data sources when creating reports. Among them, Indexed Data Sources are specifically designed for performance optimization on large data volumes. They allow faster retrieval and better scalability when working with high record counts, because they are pre-optimized for reporting and queries.

From the Workday Reporting guide:

“Indexed data sources provide optimized performance for large data volumes. These data sources are indexed on commonly used fields and are specifically designed to support high-performance queries.”

Thus, the correct choice is A. Indexed for ensuring performance with large datasets.