Performance issues often occur when trending reports pull fields from related business objects instead of directly from the Trended Workers data source . This requires Workday to join across objects at runtime, slowing down report execution. To improve performance, you should add the required field to the Trended Workers data source , ensuring the data is pre-joined and optimized for trending.

From the Workday binder: “To improve performance, add commonly reported fields directly to the Trended Workers object. Using related business object fields requires additional joins and increases report runtime.”

Creating calculated fields adds complexity rather than improving speed. Purging or re-creating trending data maintains system hygiene but does not address field-level performance.

Thus, the correct solution is A. Add the field to the Trended Workers data source .

To locate the correct fields and data sources for a custom report, Workday provides the Business Object Details report . This report displays all available fields, relationships, and related business objects that can be included in reporting. It ensures report writers can confirm which fields (e.g., Learning Content, Ratings, Popularity) are accessible for use.

From the Workday Reporting documentation:

“The report data source provides the view into the primary business object. This object gives you access to class report fields as well as links to related business objects.”

“The Business Object Details report is used to view which fields are available for reporting.”

Therefore, the correct answer is B. Run the Business Object Details report .

Workday offers several custom report types: Advanced, Matrix, Composite, Search, and Trending .

Advanced Reports : Allow sorting, filtering, grouping, totals, and charts but are not designed for percentage summarizations across grouped data.

Search Reports : Show search results based on facet filters, not suited for summarization and percentages.

nBox Reports : Used for displaying workers or positions across two dimensions (e.g., performance vs. potential).

Matrix Reports : Specifically designed for grouping data, applying summarizations (count, sum, percent), and drilling

Composite reports combine multiple subreports, and their summarizations depend on the fields configured in the subreports themselves. To enable consistent grouping and summarization across the entire composite report, the Location field must be included as a Detail Data field in all the subreports . This ensures that each subreport provides the Location context required for composite-level summarization.

From the Workday binder: “Composite reports aggregate results from multiple subreports. To summarize or drill consistently on a specific field, that field must exist as a Detail Data field in all subreports included in the composite.”

If Location is only included in one subreport, summarizations in the other subreports would not align, and Location-based grouping would fail. Similarly, making Location drillable only affects drill-down options, not summary-level grouping across the composite.

Thus, the correct answer is A. Include Location as a Detail Data field in all the subreports .

When creating a custom report, filters restrict which data records are returned. Workday allows different comparison types for filters. The option “Value specified in this filter” lets you hard-code a condition (for example, Time Type = Part-Time ), so the report consistently returns only part-time employees without requiring user input.

From the Workday Reporting documentation:

“Filter – Add conditions to filter the primary business object.”

“Prompts – You can further narrow and refine your report results by having the user complete prompt fields before they run the report… or use value specified in this filter for fixed filtering.”

Therefore, the correct answer is C. Value specified in this filter .

Workday dashboards allow organizations to present multiple reports together in a consolidated, highly visual, and interactive format. For C-level executives, who require a comprehensive and regional view of annual average base pay , dashboards are preferred over individual reports or worklets because they enable grouping and comparison across multiple data sets.

From the Workday binder: “Dashboards provide an interface to view charts and sheets all in one place. This enables managers and executives to analyze key metrics and trends so they can make better decisions.” . By organizing reports by region within a dashboard, executives can quickly compare averages, identify trends, and take strategic action without needing to navigate multiple reports.

Worklets are lightweight tiles often used for single reports or quick tasks on the Home page. However, this scenario requires an organized collection of reports , making D. A dashboard, because we need information from a collection of reports, organized by region the correct answer.

Enabling a report as a worklet and assigning it to a dashboard does not automatically make it visible. The Recruiting dashboard (or any dashboard in Workday) must be configured to include the worklet explicitly. This is a common oversight—report designers assume that enabling a report as a worklet is sufficient, but the dashboard itself must be updated in configuration to display that worklet tile.

From the Workday reporting materials: “Dashboards provide an interface to view multiple worklets. Even if a report is enabled as a worklet, the dashboard configuration determines which worklets are visible to end users.”

Other options are less relevant: exceeding 100 rows only impacts loading performance, not visibility; security issues would typically block data, not hide the worklet entirely; and required setup applies to whether the worklet is optional or required, but it must still be added to the dashboard.

Thus, the correct reason is B. You need to configure the Recruiting dashboard to include the worklet .

The correct choice is Lookup Related Value , because this function allows you to retrieve a field from a related business object that is not directly stored on your primary object. In this scenario, the primary business object is Performance Review , which holds performance-related data but not job-related data such as Job Title. Since Job Title resides on the Worker business object , you need to link from Performance Review to Worker and then retrieve Job Title.

The Workday reporting guide explains: “Lookup Related Value – Returns a field from a related business object. Use this to bring data from associated objects into a report when the field is not directly available on the primary object.” . This ensures the Performance Review data can be combined with Job Title for meaningful insights.

By contrast, Aggregate Related Instances is used to roll up multiple related values, Range Band applies thresholds, and Evaluate Expression Band is used for conditional ranges, not cross-object retrieval.

To connect multiple business objects in reporting, Workday provides the Business Object Details report . The Related Business Objects tab within this report shows how different business objects are linked (e.g., Worker to Dependent). This enables report writers to identify which fields connect the primary and secondary objects.

From the Workday Reporting documentation:

“The report data source provides the view into the primary business object. This object gives you access to class report fields as well as links to related business objects .”

Therefore, the correct answer is C. The Related Business Objects tab of the Business Object Details report .

In Workday reporting, row ordering is controlled on the Sort tab of the report definition. If you want the rows in a matrix report to sort by a specific field (such as Total Count ), you must add that field to the Sort tab . Filters limit records, and summarizations define metrics, but sorting rules are explicitly defined in the Sort configuration.

From the Workday Reporting documentation:

“Sort – Control the order to present and group data. You can specify options for subtotals, grand totals, and outlines. Add a row on the Sort tab to define sorting by a particular field.”

Therefore, to sort rows by Total Count instead of Total Average Base Pay , the correct step is C. Add a new row to the grid on the Sort tab .